Re: Widget structure questions

Mark Waddingham wrote: On 2015-10-11 08:12, Mark Wieder wrote: On 10/10/2015 12:47 PM, Peter Haworth wrote: Yes, I've been using them for a long time now and also wonder why they aren't in the dictionary. I think I might have filed a bug report about that a long while ago but don;t remember

Re: Widget structure questions

Mark Waddingham writes: > Well we can certainly come up with a list of the handlers which are definitely > part of the API used by the palettes. In spite of appearances I'm really not trying to make yet more work for the team. -- Mark Wieder ahsoftw...@gmail.com

Re: Widget structure questions

Monte Goulding wrote: >> On 13 Oct 2015, at 4:16 am, Richard Gaskin wrote: >> >> The savingStandalone and standaloneSaved messages, along with >> their mobile equivalents, are in the Dictionary. There may be >> others if I gave it some thought. > > Those are slightly different in that they are

Re: Widget structure questions

> On 13 Oct 2015, at 4:16 am, Richard Gaskin wrote: > > The savingStandalone and standaloneSaved messages, along with their mobile > equivalents, are in the Dictionary. There may be others if I gave it some > thought. Those are slightly different in that they are

Re: Widget structure questions

Well we can certainly come up with a list of the handlers which are definitely part of the API used by the palettes. I'd point out that the format on disk of the extensions folder and the metadata file hadn't been 'officially sanctioned' as not going to change either... Hence why the IDE

Re: Widget structure questions

On 2015-10-11 08:12, Mark Wieder wrote: On 10/10/2015 12:47 PM, Peter Haworth wrote: Yes, I've been using them for a long time now and also wonder why they aren't in the dictionary. I think I might have filed a bug report about that a long while ago but don;t remember for sure. Filed 16189

Re: Widget structure questions

On 10/10/2015 05:54 PM, Mark Waddingham wrote: I don't think I expressed myself very well in the bug report you filed... The examples for syntax shouldn't use undocumented / ide functions - as it is misleading. The ide functions as yet aren't documented but at some point will be as a 'how to

Re: Widget structure questions

On 10/10/2015 12:47 PM, Peter Haworth wrote: Yes, I've been using them for a long time now and also wonder why they aren't in the dictionary. I think I might have filed a bug report about that a long while ago but don;t remember for sure. Filed 16189 and 16190. -- Mark Wieder

Re: Widget structure questions

On 10/11/2015 01:36 AM, Mark Waddingham wrote: I agree, however, that it is important for the tool writers that this kind of reference be available. Add to that the fact that I haven't even been able to find which ide library those functions live in, so unless you already know about them

Re: Widget structure questions

Thanks Mark. Do you happen to know if there are any handlers which return these paths or even the information about each widget from its manifest.xml file? It's easy enough to go through all the files myself and parse the xml myself but probably safer to use official handlers if they exist.

Re: Widget structure questions

Great, thanks Mark, that's very useful. Like you, I'm parsing the manifest.xml files myself right now but will check into the revIDEExtensionProperty and revIDEExtensionsFetchMetadata() handlers. I'm getting the path to the user extensions folder the same way as you. Strange that they'd advise

Re: Widget structure questions

On 10/10/2015 12:36 PM, Mark Wieder wrote: put revEnvironmentUserPluginsPath() into tPath I should also point out that the 'revEnvironment...' functions aren't in the dictionary but are listed in the Rev V5 release notes. -- Mark Wieder ahsoftw...@gmail.com

Re: Widget structure questions

On 10/10/2015 10:52 AM, Peter Haworth wrote: It appears that the files that define the widgets supplied with LC are kept in Contents/Tools/Extensions folder of the application bundle (on a Mac), with each widget having its own folder named com.livecode.extensions.livecode.. Are widgets created

Widget structure questions

It appears that the files that define the widgets supplied with LC are kept in Contents/Tools/Extensions folder of the application bundle (on a Mac), with each widget having its own folder named com.livecode.extensions.livecode.. Are widgets created by users kept in the same place? There's a

Re: Widget structure questions

On 10/10/2015 11:49 AM, Peter Haworth wrote: Thanks Mark. Do you happen to know if there are any handlers which return these paths or even the information about each widget from its manifest.xml file? It's easy enough to go through all the files myself and parse the xml myself but probably

Re: Widget structure questions

Yes, I've been using them for a long time now and also wonder why they aren't in the dictionary. I think I might have filed a bug report about that a long while ago but don;t remember for sure. Pete lcSQL Software Home of lcStackBrowser

Re: Widget structure questions

On 10/10/2015 12:44 PM, Peter Haworth wrote: I'm getting the path to the user extensions folder the same way as you. Strange that they'd advise you not to use the official way to get those paths, especially the system extensions since it will be different on each platform. Ah. No, sorry, I

Re: Widget structure questions

I don't think I expressed myself very well in the bug report you filed... The examples for syntax shouldn't use undocumented / ide functions - as it is misleading. The ide functions as yet aren't documented but at some point will be as a 'how to write ide components' reference. However, that