7.0 Issues
Peter Haworth
pete at lcsql.com
Sun Mar 23 18:05:35 EDT 2014
Perhaps Jacque's suggestion of preserving the stack file version when a
plugin is saved is the best solution.
Jacque - did you enter a feature request?
Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
On Sun, Mar 23, 2014 at 2:23 PM, Richard Gaskin
<ambassador at fourthworld.com>wrote:
> Peter Haworth wrote:
>
>> As for the plugin settings, wouldn't storing them in the prefs file be the
>> appropriate place?
>>
>
> What happens when a plugin is moved or renamed, or updated, or any number
> of other things that can happen.
>
> Binding the data to the file is useful, but since it requires saving the
> file it's a problem.
>
> But managing a list of plugin files and keeping it sync is another
> problem. Not necessarily intractable, perhaps even necessary, but not code
> I'd enjoy writing. ;)
>
>
> --
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> ____________________________________________________________________
> Ambassador at FourthWorld.com http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
More information about the use-livecode
mailing list