Indeed I have a configuration, that is the only thing that my startup script 
does in fact. 

However I know that people prefer automatic stuffs (i.e., put the script once 
in the folder and forget about it).
Concerning the configuration browser, I have no idea how to put my 
configuration in it.

Roby



> On 09 Feb 2015, at 16:41, Sven Van Caekenberghe <[email protected]> wrote:
> 
> 
>> On 09 Feb 2015, at 16:37, Roberto Minelli <[email protected]> wrote:
>> 
>> Hi Sean,
>> 
>> On the one side, I see (and agreed) what you said. But suppose you want to 
>> provide users with a script that loads your package and you want for them 
>> minimal effort, i.e., copy the script file in the correct folder on their 
>> PC. Then you cannot really use your approach.
> 
> Robert,
> 
> What is wrong with a simple configuration that users can load with one-click 
> using the configuration browser ? It can't get much simpler than that, IMHO, 
> and you can do everything you want (post load actions, ..).
> 
> Sven
> 
>> However, thanks for sharing your automagic way of initializing your image ;)
>> 
>> Cheers,
>> R
>> 
>> 
>>> On 09 Feb 2015, at 15:50, Sean P. DeNigris <[email protected]> wrote:
>>> 
>>> Roberto Minelli-3 wrote
>>>> Is there any way to specify an order or priority of StartupAction?
>>> 
>>> The startup action framework is an awesome tool to set up one's images
>>> automagically. And... working with script files sucks!
>>> 
>>> I use a minimal script to load a Metacello project with my actual startup
>>> logic. It never changes, so instead of hand-editing scripts, I do all that
>>> work in the image with the full power of the environment. This is the whole
>>> script:
>>> 
>>>  StartupLoader default executeAtomicItems: {
>>>     StartupAction name: 'Load DeNigrisPreferences' code: [
>>>             Gofer it
>>>                     url: 
>>> 'http://smalltalkhub.com/mc/SeanDeNigris/DeNigrisPreferences/main';
>>>                     package: 'DeNigrisPreferences-Core';
>>>                     load.
>>>     ] runOnce: true.
>>>  }.
>>> 
>>> The code is public. While it's fairly specific to my workflow, it may serve
>>> as inspiration. The trickiest part was that the code couldn't depend on
>>> Metacello (I don't remember why. This may have been when not all platforms
>>> had Metacello pre-installed. Actually, I think I'll try using Metacello
>>> now!).
>>> 
>>> HTH.
>>> 
>>> 
>>> 
>>> -----
>>> Cheers,
>>> Sean
>>> --
>>> View this message in context: 
>>> http://forum.world.st/Order-priority-of-StartupAction-tp4804596p4804645.html
>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>>> 
>> 
>> 
> 
> 


Reply via email to