Code: Select all
-- LCB extensions are available on all platforms
put revSBAllPlatforms() into tExtension["platforms"]
Code: Select all
-- LCB extensions are available on all platforms
put revSBAllPlatforms() into tExtension["platforms"]
If that happens, then the revSBAvailableExtensions handler can check for tExtension["platforms"] being empty before populating it with revSBAllPlatforms().As an aside, the Toast library does have "Platforms: android" in the LCB source so the dictionary currently shows android in both the platform and OS filter lists.
Code: Select all
OS: mac, ios
The widget store still shows:Remember it was suppose to be "1000 widgets and extensions" by Christmas ...... 2016" hows it going?
I'm not surprised and as you say its embarrassing. I've struggled with my library and one reason is that there is no detailed documentation, even creating the documentation is difficult with seemingly minor modifications causing the dictionary to have a fit.The widget store still shows:
Big Square
Circle Progress
Clock (sic!)
My Pink circle
Which is embarrassing to the power of 10
The note is a worry: is LCB stable yet?The metadata clauses allow a set of key-values to be encoded in the compiled module. These are not used in compilation or execution, but may be used by the system loading and using the module.
At the moment, the following keys are understood:
title: a human-readable name for the module
description: a simple description of the module's purpose
version: a string in the form X.Y.Z (with X, Y and Z integers) describing the modules version
author: the name of the author of the module
os: the operating systems where the module can be used
platforms: the platforms where the module can be used
Note: The current metadata mechanism is unlikely to remain part of the language. It is intended that it will be replaced by a package description file, which will allow modules to be grouped together with other resources.