If the goal is to make the project structure (and associated change sets)
easier to understand in the image, then I would suggest leaving the
spaces. Why? Unix users are quite capable of escaping the spaces when they
work in a shell, and any Squeak user who uses change sets to save code
will (hopefully) want to give sensible names and preambles and postscripts
to those change sets anyway.

If the goal is to have a nicer naming convention for user change sets,
then we should first look at the excellent naming conventions used in Cuis
(after the release of course).

If we are not certain of the goal, then do nothing :-)

Dave


> Then maybe "the-root-project" and "the-home-project" ? Or
> "the.root.project" and "the.home.project"?
>
> Best,
> Marcel
> Am 26.02.2020 14:12:24 schrieb Thiede, Christoph
> <christoph.thiede at student.hpi.uni-potsdam.de>:
>>Â > It might be better if the home project change set to be named 'The
>> home project' rather than 'Unnamed1'. 
>>Â 
>>Â Let's try that! Makes the label button in the world main docking bar
>> more readable.
>
> On the other hand, if you file out your changeset, the name will contain
> spaces. Some operating systems don't like such paths (harder to enter in
> bash/cmd) ...
>
> Best,
> Christoph
>
>
> Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag
> von Taeumel, Marcel
> Gesendet: Mittwoch, 26. Februar 2020 11:13 Uhr
> An: John Pfersich via Squeak-dev
> Betreff: Re: [squeak-dev] [ANN] Squeak 5.3 RC1
> Â 
> Hi all!
>
>>Â The Guardians game does not run in the 64bit version - it
>> crashes immediately.
>
> That's unfortunate. We should look into it. Maybe this points to a bigger
> issue in the VM?
>
>>Â this is probably not an issue for 5.3, but can we sign the executable
>> files for the next time?
>
> Already signed for macOS. We did look into signing Windows binaries in the
> past. Wasn't that easy; too many different things to sign for (code,
> binary, etc.). Maybe it got better? Squeak e.V. Germany would be happy to
> help if we need an organization behind such certification.
>
>>Â Attempting to go fullscreen (by clicking button in top right corner of
>> squeak header menu) completely freezes the system on OSX 10.15.1 Catalina
>
> Whoops! Should not happen! We will look into it.
>
>>Â Is it necessary that the fresh image has a changeset that includes
>> loads of reorganizations?
>>Â I am a bit annoyed every time I start a fresh image to make a minimum
>> change and cannot directly fileout the changeset because of the mess.
>>Â ReleaseBuilder-dtl.206 would be great for 5.3.
>
> ;-) Calm down. Take a deep breath. ;-)Â  Â ------Â  This is obviously not
> intended and we will fix it. The issue was in ReleaseBuilder class >>
> #cleanCaches and ClassOrganizer class >> #cleanUp: not being silent
> regarding the SystemChangeNotifier. I fixed it and will commit the changes
> as part of RC2 asap. ---- I will move ReleaseBuilder-dtl.206 to
> "treated".
>
>>Â Furthermore, we have two empty changesets:Â 
>> The third change set is called 'Autogenerated-unload' and is empty. I
>> don't know where this change set came from, but it does not need to be
>> in the release image.
>
> Fixed. Will be part of RC2. The issue was in ReleaseBuilder class >>
> #cleanCaches.
>
>> It might be better if the home project change set to be named 'The
>> home project' rather than 'Unnamed1'. 
>
> Let's try that! Makes the label button in the world main docking bar more
> readable.
>
> Best,
> Marcel
> Am 26.02.2020 10:35:34 schrieb Stéphane Rollandin
> <lecteur at zogotounga.net>:
>> http://files.squeak.org/5.3rc1/Squeak5.3rc1-19414-64bit/
>> Please give them a try and report any issues here on the mailing list.
> The Guardians game does not run in the 64bit version - it crashes
> immediately.
>
> Guardians:
> http://www.zogotounga.net/comp/guardians.htm
>
> Code:
> http://www.zogotounga.net/comp/squeak/guardians/Guardians-builder-0.94.sar
>
> (to see the crash, just install the above sar and follow the
> instructions for starting the game)
>
>
> Stef
>
>
>