Re: Libraries and effiency
Re: Libraries and effiency
- Subject: Re: Libraries and effiency
- From: Tommy Bollman <email@hidden>
- Date: Sat, 7 Aug 2010 13:22:45 +0200
Hello.
I don't think you can regard a ScriptServer with a version number as its name, and library scripts in its contents/resources/scripts folder
as a bad policy, If apple did that, then there would have been no possibilities for application bundles at all. And this is the only strategy I know of where you can be totally sure that your product will work, and which is the easiest solution for the user as well. As a matter of fact and (disregarding bloat), this is an advantage AppleScript has of many other languages on Mac Os X.
On 7 Aug 2010, at 11:05, Philip Aker wrote:
> On 2010-08-06, at 09:55:24, Tommy Bollman wrote:
>
>>> Hey Tommy, it's a logical non-sequitur to equate 10 year old billy-box bugs with a modern Mac system.
>
>> Well, it really should have been like that, but it aint! This is basically what happens when say your download some python code, or Tcl, or Perl, or Java for that matter, just to realize, (hopefully within an hour), that it doesn't work because what you downloaded assumed that your frameworks and libraries were in the same state as the developer. (That is how it is.) Then if you update your frameworks to support what you newly installed, then you are at risk of braking something else that relied on what you had from before. It can be a pesky, and annoying issue to solve this tasks. Everything would have been a lot easier if everybody used version numbers in the file names.
>
> Actually, there used to be a slot for file versions in file records on prehistoric Mac systems (might be Technote #204). For whatever reason, it never gained a lot of traction.
>
>
>> AppleScript Users comes in several flavors. Some just want to use the functionality of some code, without a single idea and clue about what is going on. That user is a whole kind of different user to someone that downloads some java, pearl or python source, in order to use.
>
>> I find the ideal solution to those problems to ship the code either within what you distribute, or embedded in a script library server which is a far more practical approach.
>
> It's not appropriate to ship applications with modifiable subfolders. This is the policy on Mac OS X. For applications, the normal way to handle this situation is to create a folder in the "Application Support" folder (path to application support folder from user domain). For specific areas, other folders such as Audio, Screen Savers, Scripts, Sounds, etc. are already provided.
>
>
> 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