[etoys-dev] Category for user objects

[Bert Freudenberg]

Then maybe UserObjects-Etoys and UserObjects-Kedama? Or lump them together? There are already some Kedama players in the existing "UserObjects" category.

If it were up to me I probably would just put everything under "UserObjects" for simplicity.

"#cleanUpEtoys" of course removes all projects. To make a release image you should use, which includes the cleanup call:

ReleaseBuilderSqueakland new prepareReleaseImage

- Bert -

On 27.05.2011, at 12:40, karl ramberg wrote:

> A distinct package name would be nice
> I got confuced when Morphic package got changed
> 
> EtoysUserScripts would be quite descriptive
>  
> Karl
>  
> On Fri, May 27, 2011 at 12:02 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> We might also want to change the category for Kedama players.
> 
> declareAndPossiblyRename: only checks for #Player as superclass name. Since Kedama uses a different Player class, this falls back to the 'Morphic-Imported' category. At least that's what I think is happening.
> 
> IMHO we should change those categories to not collide with the MC package names. Either put everything into "Object categoryForUniclasses", or have multiple categories as previously, but use a distinct name. E.g. 'UserObjects-Morphic', 'UserObjects-Etoys', 'UserObjects-Balloon3D'.
> 
> Opinions?
> 
> - Bert -
> 
> On 27.05.2011, at 00:38, karl ramberg wrote:
> 
> > Found it:
> > ReleaseBuilder new cleanUpEtoys
> >
> > Karl
> >
> > On Fri, May 27, 2011 at 12:36 AM, karl ramberg <karlramberg at gmail.com> wrote:
> >> I have a issue with Monticello and Kedama.
> >> I updated project Particle dye in water, but noticed that this adds Kedama players in a category: 'Morphic-Imported'
> >>
> >> Should I just ignore this ?
> >>
> >> I'm not quite sure how to fix it...
> >>
> >> Karl
> >>
> >
> _______________________________________________
> etoys-dev mailing list
> etoys-dev at squeakland.org
> http://lists.squeakland.org/mailman/listinfo/etoys-dev
>