On 27 Feb 2013, at 17:07, Paul DeBruicker <[email protected]> wrote:

> And I thought 'Untrusted' was going to be renamed 'Community Supported'
> or some such.  Did that decision get changed or just slide through the
> cracks?

Yes, I think that should be done, untrusted is a bit negative.

The configuration browser is also too minimal right now, and a bit confusing.

We should try to come up with more user friendly phrases on the menu.

It would also be quite useful if the CB knew if a config was present and/or 
loaded. 

A way to browse the config code would also be welcome.

> On 02/27/2013 08:00 AM, Torsten Bergmann wrote:
>> Janko wrote:
>>> One-click load of Aida from Configuration Browser is now possibl
>> 
>> 
>> We manually make a copy of configs that are know to work for a specific
>> Pharo version into a specific "/MetaRepoForPharoXX". This will be automated 
>> in the future
>> with automatic validation, etc.
>> 
>> So if Aida is really working in Pharo 2.0 then please make a copy of the 
>> sepcific
>> ConfigurationOfAida mcz into ss3.gemstone.com/ss/MetaRepoForPharo20
>> using the "Copy" button of the Monticello repo browser.
>> 
>> This way it will appear in "Configurations" tab in configuration browser
>> (containing the configs that are know to work).
>> 
>> Currently Aidi is only in "Untrusted" since this is the repo for all configs
>> (squeaksource.com/MetacelloRepository) 
>> 
>> 
>> I also think it would be nice if you also
>> 
>> - add a beginners workspace with "SwazooAida start."
>>   You can use 
>> 
>>           spec postLoadDoIt: #postloadForCore:package:
>> 
>>   with
>>          postloadForCore: loader package: packageSpec
>>      
>>              Workspace openContents: 'SwazooAida start.'
>> 
>> - or you add a menu entry and server start panel, have a look at 
>> ConfigurationOfPharoOnlineHelp for an example
>> 
>> This way even a complete beginner can easily start just by
>> loading Aida using the config browser in 2.0 and then "jump start" into the 
>> browser.
>> 
>> Bye
>> T.
>> 
> 
> 


Reply via email to