The best way is to test it is on your own machine.  Do you have access
to the server?

In /home/squeakmap is the server image -- Squeak3.8-6665-sm.image.
Grab it and the changes as well as  "start.st" boots the server in the
same directory (note a classic VM is required).  Running it on your
localhost so can actually step through debugger in the server to make
sure the change works.

This is how I did the 2011 enhancements for the Release Editor and CSP
improvements.

Doing this will also bring to light how badly we really need to
improve or replace SqueakMap's implementation, particularly on the
server side.  :(   The domain model itself is actually pretty nice,
but the machinery needs improvement.



On Wed, Jan 9, 2013 at 6:56 AM, Frank Shearar <frank.shearar at gmail.com> wrote:
> On 9 January 2013 12:55,  <commits at source.squeak.org> wrote:
>> Frank Shearar uploaded a new version of SMLoader to project The Inbox:
>> http://source.squeak.org/inbox/SMLoader-fbs.78.mcz
>>
>> ==================== Summary ====================
>>
>> Name: SMLoader-fbs.78
>> Author: fbs
>> Time: 9 January 2013, 12:55:26.488 pm
>> UUID: affd02cf-4ff4-4bd1-a33f-89ce0d974bf5
>> Ancestors: SMLoader-cmm.77
>>
>> The UI part of supporting multiple Squeak versions in an SM release.
>>
>> Todo: POSTing the multiple versions.
>>
>> =============== Diff against SMLoader-cmm.77 ===============
>
> I would love to know what I need to do to implement POSTing a release
> with multiple Squeak versions. SqueakMap gurus?
>
> frank
>