I wasn't suggesting forking (I had another post in this thread talking
about Grease).

But even Seaside exists both in SqueakSource and in the Cincom Public
Store. I was merely asking if the the appropriate project name
couldn't be used in SqueakSource. Using a slight variation (and having
two projects in the one repo) is just confusing.

Julian

On Mon, Oct 11, 2010 at 12:29 PM, Hannes Hirzel <hannes.hirzel at gmail.com> wrote:
> I think it should go the way Seaside is handled. Something like
> 'Grease' and 'Sport' *** on top of Squeak and the go to the original
> code base. Not a fork of the code for the library.
>
> Maybe Grease and Sport are good enough to have compatibility?
>
> --Hannes
>
>
> Sport and Grease cover different areas with their portability APIs.
> Sport covers Sockets, Files, Time, Exception handling and utilities
> such as being able to explicitly test in which Smalltalk dialect code
> is being run in. Grease covers utilities for parsing, printing,
> encoding & decoding strings, delayed sends, common exceptions,
> utilities such as secure hash. There is some overlap, but not much.
> For example, Seaside expects the underlying HTTP server to deal with
> socket issues so Grease does not deal with sockets. Sport in turn does
> not have the extensive parsing and printing facilities found in
> Grease.
>
> On 10/11/10, Julian Fitzell <jfitzell at gmail.com> wrote:
>> This still seems confusing. Could we just have a new SqueakSource
>> project called "Xtreams" (small T + an S)? It's not like projects are
>> expensive to create...
>>
>> Julian
>>
>> On Sat, Oct 9, 2010 at 11:33 PM, Nicolas Cellier
>> <nicolas.cellier.aka.nice at gmail.com> wrote:
>>> So, I started a quick port of VW Xtreams to Squeak this evening.
>>> Only the Xtreams-Core and the trivial Xtreams-Terminals (no
>>> file/pipe/socket/pointer).
>>> You'll find code at http://www.squeaksource.com/XTream.
>>> My previous experimental Xtream project has been renamed SqueaXTream
>>> to reduce confusion, but still sits in the same project.
>>> Please find my report below.
>>
>>
>
>