Re: Libraries and effiency
Re: Libraries and effiency
- Subject: Re: Libraries and effiency
- From: Tommy Bollman <email@hidden>
- Date: Sat, 7 Aug 2010 19:20:38 +0200
Hello. I'll look into it, and think about it.
Currently there are no such thing as collaborating loader systems on the Mac Os x. But I think your idea is generally good and supports it.
I'll come back on this.
On 7 Aug 2010, at 16:39, Philip Aker wrote:
> On 2010-08-07, at 04:17:11, Tommy Bollman wrote:
>
>> Hello Phillip
>>
>> This looks very good, I had figured I would use a property list like this with the Library Loader script I am working, and can be found at MacScripter.net <http://www.macscripter.net/viewtopic.php?id=33487 > : It is very user centric, you have full access to all the files within the editor of your preference. This is centered around hardcoded paths, since the paths are predefined within the script like the properties list does. You then really just select the library category, then choose the file you want to create a loader statement for, -the correct loader statement will then be pasted onto the clipboard.
>
>> -I was about to implement creation of a property list like yours, during installation /reconfiguration this weekend, -and may still manage that!.
>
> A test application which sets up the shared property list is available here: <http://www.vcn.bc.ca/~philip/osa/dl/OSAScriptLibraryInfo.zip>.
> It creates the default property list if it doesn't exist or resets it if it does.
>
> It's not the final version (only good for Intel 32/64, 10.5 or later). I should be able to compile for a 10.4 target at some point. The final will be freely available for library loader applications to include in their released products (commercial or otherwise).
>
> One label was changed: DisabledSuffixes -> DisabledSubstrings
>
>
> [...]
>
> More on the rest of your post as it applies to the shared property list notion later, however:
>
>> I would like to add a whole sub section to your property list which held collections of functionality, both files and directories
>
> As previously mentioned, the concept has some required sections but is otherwise open to entries by loader applications so feel free to add your own entries. The basic idea is that users don't have to move their scripts around in order to accommodate different library loaders. The "required" entries set properties for library folders only -- they don't deal with individual scripts -- that task is left up to the individual library loaders.
>
> You should add your application entries keyed by a unique bundle identifier. Something like:
>
> <key>com.bollman.library.loader</key>
> <dict>
> <key>Version</key>
> <string>1.2.3</string>
> <key>SomeKey</key>
> <string>some value</string>
> …
> </dict>
>
>
> Philip Aker
> echo email@hidden@nl | tr a-z@. p-za-o.@
>
> Democracy: Two wolves and a sheep voting on lunch.
>
>
Best regards
Tommy Bollman
--------------------------------------------------------------------------------------------------
Mollison's Bureaucracy Hypothesis:
If an idea can survive a bureaucratic review
and be implemented it wasn't worth doing.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden