UbiquiTalk running in Pharo 1.1

>
> I haven't done much with it, and there are some deprecation warnings, but
> it's running.  In the attached screenshot, the "host 2" entry in the
> "Detected Hosts" window is the Squeak 4.1 image running on the right.
> http://forum.world.st/file/n2400767/Screen_shot_2010-08-30_at_August_30%2C_2010_5.47.42_PM.png
> Screen_shot_2010-08-30_at_August_30%2C_2010_5.47.42_PM.png
>
> Load it with:
> Gofer new
>      squeaksource: 'KomHttpServer';
>      package: 'DynamicBindings';
> load.
>
> Gofer new
>      squeaksource: 'KomHttpServer';
>      package: 'KomServices';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'rST';
> load.
>
> Gofer new
>      squeaksource: 'OSProcess';
>      package: 'OSProcess';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Platform.pharo';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Cache';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-GUI';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Utilities';
> load.
>
> "requires Utilities"
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Kernel';
> load.
>
> "requires Kernel"
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Plugins';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-PDA';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Property Editors';
> load.
>
> Gofer new
>      squeaksource: 'SPDProjectUpdates';
>      package: 'UbiquiTalk-Tests';
> load.
>
> "requires platform"
> Gofer new
>     squeaksource: 'UbiquiTalk';
>     package: 'UTAllServices';
> load.
>
> Sean
> --
> View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2400767.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> The updated rST and UbiquiTalk versions now live in their main repos (thanks
> to Noury for access).  The installation script is now:
>
> Gofer new
> squeaksource: 'KomHttpServer';
> package: 'DynamicBindings';
> package: 'KomServices';
> load.
>        
> Gofer new
> squeaksource: 'rST';
> package: 'rST';
> load.
>
> Gofer new
>       squeaksource: 'OSProcess';
> package: 'OSProcess';
> load.
>
> Gofer new
>       squeaksource: 'UbiquiTalk';
> package: 'UbiquiTalk-Platform.pharo';
> package: 'UbiquiTalk-Utilities';  "depends on Platform"
> package: 'UbiquiTalk-Kernel'; "depends on Utilities"
> package: 'UbiquiTalk-Cache'; "depends on Kernel"
> package: 'UbiquiTalk-GUI'; "depends on Kernel"
> package: 'UbiquiTalk-Plugins'; "depends on Kernel"
> package: 'UbiquiTalk-PDA';
> package: 'UbiquiTalk-Property Editors';
> package: 'UbiquiTalk-Tests';
> package: 'UTAllServices';
> load.
>
> Sean

>
> Miguel Enrique Cobá Martínez-2 wrote:
> >
> > This begs for a ConfigurationOfUbiquiTalk :)
> >
>
> Yes, I didn't want to "take the time" to make one, and it probably took
> longer to list it all out, lol.
>
> One of the complications is that Squeak 4.1, which I also work in, does not
> include Metacello by default, so I have to write an Installer script.

>
> Sean
> --
> View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2528894.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> The updated rST and UbiquiTalk versions now live in their main repos (thanks
> to Noury for access).  The installation script is now:
>
> Gofer new
> squeaksource: 'KomHttpServer';
> package: 'DynamicBindings';
> package: 'KomServices';
> load.
>
> Gofer new
> squeaksource: 'rST';
> package: 'rST';
> load.
>
> Gofer new
>      squeaksource: 'OSProcess';
> package: 'OSProcess';
> load.
>
> Gofer new
>      squeaksource: 'UbiquiTalk';
> package: 'UbiquiTalk-Platform.pharo';
> package: 'UbiquiTalk-Utilities';  "depends on Platform"
> package: 'UbiquiTalk-Kernel'; "depends on Utilities"
> package: 'UbiquiTalk-Cache'; "depends on Kernel"
> package: 'UbiquiTalk-GUI'; "depends on Kernel"
> package: 'UbiquiTalk-Plugins'; "depends on Kernel"
> package: 'UbiquiTalk-PDA';
> package: 'UbiquiTalk-Property Editors';
> package: 'UbiquiTalk-Tests';
> package: 'UTAllServices';
> load.
>
> Sean
> --
> View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2528879.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> Miguel Enrique Cobá Martínez-2 wrote:
>>
>> This begs for a ConfigurationOfUbiquiTalk :)
>>
>
> Yes, I didn't want to "take the time" to make one, and it probably took
> longer to list it all out, lol.
>
> One of the complications is that Squeak 4.1, which I also work in, does not
> include Metacello by default, so I have to write an Installer script.  I
> still find it confusing and frustrating that there are both Gofer and
> Installer.  Why don't we standardize on one or merge them?
>

> On Mon, 6 Sep 2010, Miguel Enrique Cobá Martínez wrote:
>
> >
>
> snip
>
> "Installer AFAIK does a lot of things, so in a way it was bloated, that
> was the reason for gofer showing up (also the fact that installer didn't
> unload packages and gofer does, I think)."
>
> Installer can unload Monticello packages (besides being able to load stuff
> from sources which are not used by Pharo users) and I'm pretty sure it
> does it the same way as Gofer does (this is a feature of MC).

>
> Miguel Enrique Cobá Martínez-2 wrote:
> >
> > Exactly, that is the reason that I put AFAIK, and the reason I said it
> > was bloated. The fact that you can download from a Mantis, squeakmap,
> > GOODs, a magma repo, universes or a ftp repo has little impact if 99% of
> > the times you are downloading from http repos squeaksource and
> > gemstone. :)
> >
>
> [thinking out loud] This sounds like a great reason to clean and modularize,
> but why a whole new thing.

>
>
> Miguel Enrique Cobá Martínez-2 wrote:
>>
>> Exactly, that is the reason that I put AFAIK, and the reason I said it
>> was bloated. The fact that you can download from a Mantis, squeakmap,
>> GOODs, a magma repo, universes or a ftp repo has little impact if 99% of
>> the times you are downloading from http repos squeaksource and
>> gemstone. :)
>>
>
> [thinking out loud] This sounds like a great reason to clean and modularize,
> but why a whole new thing.
> --
> View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2530693.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> sean I do not know your computer but mine does not have a 5 inches floppy, 3.5 floppy, serial port, RS2332.
> Does it answer your question?
> Side remark: lukas probably write gofer because he needed something
> - well written
> - robust
> - small with only the code he needs
> - with tests
> so he did it and instead of keeping it for himself he accepted the **hassle**
> - to get pointed as a bad guy,
> - merge our changes....
> And we all thank him for that!
> Lukas and other continue to rewrite everything you want :)
> I have a long list in my pocket (changelist, messageset, ...)
>
> So changes is good, non backward compatibility is good (look at apple).

> Let us face it and learn.
>
> Stef
>
>
> >
> >
> > Miguel Enrique Cobá Martínez-2 wrote:
> >>
> >> Exactly, that is the reason that I put AFAIK, and the reason I said it
> >> was bloated. The fact that you can download from a Mantis, squeakmap,
> >> GOODs, a magma repo, universes or a ftp repo has little impact if 99% of
> >> the times you are downloading from http repos squeaksource and
> >> gemstone. :)
> >>
> >
> > [thinking out loud] This sounds like a great reason to clean and modularize,
> > but why a whole new thing.
> > --
> > View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2530693.html
> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [hidden email]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> Stéphane Ducasse wrote:
>>
>> Side remark: lukas probably write gofer because he needed something
>> - well written
>> - robust
>> - small with only the code he needs
>> - with tests
>> so he did it and instead of keeping it for himself he accepted the
>> **hassle**
>> - to get pointed as a bad guy,
>> - merge our changes....
>> And we all thank him for that!
>> <snip>
>> So changes is good, non backward compatibility is good (look at apple).
>> Let us face it and learn.
>>
>
> Okay, thank you for the explanation.  And thank you Lukas for doing that
> work.  See you at ESUG!!!
>
> Sean
> --
> View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2531477.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project