Yep. At some point it might be good to put add a general filtering
parameter.
On Wed, Jan 10, 2018 at 10:50 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 01/10/2018 01:52 PM, Ali Lloyd via use-livecode wrote:
> > revIDEExtensions gives info on all the installed exte
On 01/10/2018 01:52 PM, Ali Lloyd via use-livecode wrote:
revIDEExtensions gives info on all the installed extensions, user or
otherwise (I guess it's the revIDE prefix that makes it sound like it
doesn't).
Yeah, I got thrown off by that and didn't dig down far enough to see the
user extension
revIDEExtensions gives info on all the installed extensions, user or
otherwise (I guess it's the revIDE prefix that makes it sound like it
doesn't).
Yes, it is going to be documented some day! Hopefully when there are more
resources available to sort out documenting the IDE.
On Wed, Jan 10, 2018
On 01/10/2018 12:37 PM, Ali Lloyd via use-livecode wrote:
Brian is correct, this is a temporary use of the lcdoc stuff for script
libraries to contain info that would be contained in its manifest.
Rather than worrying about what information comes from where, it would
probably be best to use the
Brian is correct, this is a temporary use of the lcdoc stuff for script
libraries to contain info that would be contained in its manifest.
Rather than worrying about what information comes from where, it would
probably be best to use the revIDEExtensions function which returns all the
'metadata' a
My guess is that will be for livecodescript libraries since they do not end
up with a manifest file.
On Wed, Jan 10, 2018 at 12:09 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 01/10/2018 09:56 AM, Mark Waddingham via use-livecode wrote:
>
> > Are you sure you didn't
I have to admit, having parsed the results of revIDEPropertiesInfo and
looked at , it took me more than a few tries at:
set the timeZone of widget "clock" to 1
set the timeZone of widget "clock" to 5
set the timeZone of widget "clock" to 9
...etc. before I noticed that the second hand was glitc
On 01/10/2018 09:56 AM, Mark Waddingham via use-livecode wrote:
Are you sure you didn't confuse 'source file' with 'manifest' - its
dealing with no source file in extensions that commit sorts out (also
why protected extensions need their docs extracted at build time -
there's no source file in
On 01/10/2018 09:44 AM, Mark Waddingham via use-livecode wrote:
I can't guarantee there will be a separate file in the future
necessarily, nor something human-readable (the manifest.xml is actually
generated mechanically from the data in the compiled module file and
combined with the metadata
On Wed, Jan 10, 2018 at 12:54 PM, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> The info will be that required by the property inspector - which is
> probably suitable for Navigator (which I'm assuming is what you are looking
> to update :)).
>
Get out of my head! ;
On 2018-01-10 18:34, Mark Wieder via use-livecode wrote:
On 01/10/2018 12:57 AM, Mark Waddingham via use-livecode wrote:
Why would 'commercial locked widgets' not have a manifest? (Or some
other means to describe their public interface...)
Dunno. It's a mystery to me. I'm just working off Ali
On 2018-01-10 18:49, Geoff Canyon via use-livecode wrote:
On Wed, Jan 10, 2018 at 12:44 PM, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
There is an API which does it in a form suitable for the property
inspector, but that's not quite as succinct.
Is this script-
On Wed, Jan 10, 2018 at 12:44 PM, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> There is an API which does it in a form suitable for the property
> inspector, but that's not quite as succinct.
>
Is this script-accessible, or just engine-accessible?
_
On 2018-01-10 18:34, Mark Wieder via use-livecode wrote:
Dunno. It's a mystery to me. I'm just working off Ali's comments in
the PR. Can you guarantee then that widgets must always be distributed
with a manifest.xml file? Or equivalent?
https://github.com/livecode/livecode-ide/commit/397deb26d7c
On 01/10/2018 12:57 AM, Mark Waddingham via use-livecode wrote:
Why would 'commercial locked widgets' not have a manifest? (Or some
other means to describe their public interface...)
Dunno. It's a mystery to me. I'm just working off Ali's comments in the
PR. Can you guarantee then that widget
On 2018-01-10 08:52, Mark Wieder via use-livecode wrote:
On 01/09/2018 09:45 PM, Geoff Canyon via use-livecode wrote:
Do the built-in widgets come with manifests?
Yes. Even the built-in widgets. At least for now, until we get
commercial locked widgets.
Why would 'commercial locked widgets' n
On 01/09/2018 09:45 PM, Geoff Canyon via use-livecode wrote:
Do the built-in widgets come with manifests?
Yes. Even the built-in widgets. At least for now, until we get
commercial locked widgets.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livec
Do the built-in widgets come with manifests?
On Tue, Jan 9, 2018 at 11:36 PM, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> Might be easier to examine the manifest.xml file for the properties.
> At least via a script.
___
use-l
On 01/09/2018 08:25 PM, hh via use-livecode wrote:
G.C. wrote:
Is there a way, given a widget, to find out programmatically what the
relevant properties of the widget are?
Only the documented ones.
Even the property inspector shows only the "user_visible" ones.
The only possibility I can see is
> G.C. wrote:
> Is there a way, given a widget, to find out programmatically what the
> relevant properties of the widget are?
Only the documented ones.
Even the property inspector shows only the "user_visible" ones.
The only possibility I can see is to scan the lcb file (if it is available).
So,
Is there a way, given a widget, to find out programmatically what the
relevant properties of the widget are?
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferen
21 matches
Mail list logo
