Re: [Pharo-dev] Loading scripts vs. configs with #stable and config browser (was: [ann] snapshotcello)

Stéphane Ducasse Wed, 24 Jul 2013 05:03:26 -0700

+ 1 :)
This is why I'm working on the PackageCatalog :)
here is an example

Title: Truc

Pharo Catalog

This is the Pharo project catalog. It is automatically generated based on projects published on http://ss3.gemstone.com/ss/MetaRepoForPharo20. We encourage project developers to describe their configurations so that their project will nicely displayed in the catalog.

Title: Truc

1. OSC

OSC is an implementation of the Open Sound Control protocol.

1.1. Keywords

transmission format sound

1.2. Implementation notes

It is composed of some keys classes:

OSCServer is a simple server listening on a given port for messages (instance of OSCMessage).

OSCParser is a message parser.

OSCMessage represents messages in the OSC protocol format.

The best way to get started is to get a soup of html elements using OSCMessage and OSCServer.

| server |
server := OSCServer listenOnPort: 5432.
[OSCMessage example1 sendTo: NetNameResolver localHostAddress port: 5432.
(Delay forDuration: (Duration milliSeconds: 30)) wait.


server hasMessage.
server nextMessage = #('/example1' 100 )

1.3. Main repository

The main repository is: http://smalltalkhub.com/mc/StephaneDucasse/OSC/main

MCHttpRepository
	location: http://smalltalkhub.com/mc/StephaneDucasse/OSC/main
	user: ''
	password: ''

1.4. Main Versions

stable: spec 
	<symbolicVersion: #stable>
	
	spec for: #'pharo1.4.x' version: '1.0'. 
	spec for: #'pharo2.0.x' version: '1.0'.

(ConfigurationOfOSC project version: #stable) load

1.5. Catalog Card MetaData

Generated 15 July 2013 Here we will get the repository from which the information was gathered as well as the configuration file version


Stef

On Jul 24, 2013, at 10:04 AM, Torsten Bergmann <[email protected]> wrote:

> Tudor wrote:
>> You can get the code at:
>> Gofer new
>>    smalltalkhubUser: 'girba' project: 'Snapshotcello';
>>    package: 'ConfigurationOfSnapshotcello';
>>    load.
>> (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment
> 
> Sorry about the rant in advance (which is more general and not only specific 
> to snapshotcello), but:
> 
> Next time someone wants this (or another) nice little Pharo tool:
> 
> - one has to remember this load script or have to find the announcement mail 
> again
> - one has to a lot of typing the expression or copying to a workspace to load 
> it. 
> 
> Just with the posted load script he does dont know if Pharo 1.4, 2.0 or 3.0 
> was used to develop it, 
> so how does he know the Pharo version to use it without failures? A pharo 
> version where it is not broken. 
> Maybe the user is still using Pharo 2.0 but maybe the tool requires at least 
> Pharo 3.0 ...
> 
> What about a new user who starts tomorrow with Pharo and never read this 
> announcement.
> Since he entered the mailinglist very late he missed the mail with the script.
> How can he now about this super cool package? Why cant it be more accessible?
> 
> I propose: PLEASE define a #stable for the working versions and place an 
> additional copy in: 
> 
> - "ss3.gemtalksystems.com/ss/MetaRepoForPharo20"             (Pharo 2.0) or 
> - "http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main"; (Pharo 3.0) 
> 
> when you know it runs in the according pharo version. It will then appear in 
> the config browser.
> 
> If it is not in the config browser of the current pharo version for easy 
> loading 
> then it does not really exist.  ;)
> It only exists for the people who read about it in the mailinglist. Think of 
> a first 
> time user who downloads Pharo 2.0. He may never stumble over the load script 
> or
> the tool in Smalltalkhub. 
> 
> I know: it may not yet be the best mechanism to provide packages to users (we 
> need more infos
> on the configs, hence catalog and automatic verification in the future) - but 
> still it
> is better than the "load scripts" and possible confusion.
> 
> So please CARE ABOUT YOUR USERS and make your packages available like this so 
> it can 
> be easily accessible and loadable right from the according image! 
> 
> Same for Roassal, Moose, ... and all the nice packages that now appear in the 
> Pharo universe...
> 
> Thanks
> T.
>