-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[widget metadata]can we do introspection to get widget metadata #25
Comments
This doesn't answer your question, but the above code is not correct. That else clause is totally unnecessary. Unless you choose to save the version, the stack won't have any knowledge of what version was used stored. The version metadata is a part of the widget itself and not the data stored in the stack file. This is something that you, as a widget developer, would need to handle. As long as there are just properties being added, using a new version shouldn't pose a problem. For all of the changes that I proposed, the defaults ( |
That is from the navBar, by the way. |
roundabout way, using lcs: that is populated in called by called by just grabbing the keys of one extension:
|
You can do introspection from the script side:
which uses the extension utilities library to parse the Widgets manifest XML from Extension Builder I think you should be able to do something like: |
OT but... I wish there was a way to re-'kind' all placed widgets of a specific 'kind' after you've changed the reverse-domain identifier (ie com.livecode..), a real pain it seems there's no way to update 'kind' for already placed widgets. I've had to do this for Widget demo stacks quite a few times now. I even tried to modify the all-widgets 'kind' property in its .tsv file to make 'kind' editable to no avail (the property just reverts to previous after setting it). |
some of the properties in some of the widgets have code similar to
which could be avoided if we could check the version metadata, and if it is under a certain value, assign those initial default values
The text was updated successfully, but these errors were encountered: