[Glass] FileSystem ported to GemStone yet?

[Dale Henrichs via Glass]

The methods and classes that are identical/compatible between Squeak and
Pharo should be in GsSqueakCommon (currently part of the default for
glass/GsDevKit).

The GsPharo and GsSqueak packages should be reserved for only those methods
and classes that diverge ...

Dale

On Fri, Nov 21, 2014 at 12:38 AM, Tobias Pape <Das.Linux at gmx.de> wrote:

> Hey Dale, Johan
>
>
> On 20.11.2014, at 18:37, Dale Henrichs via Glass <
> glass at lists.gemtalksystems.com> wrote:
>
> > Johan,
> >
> > I agree that it should be part of GsDevKit, but I think it needs to be
> conditionally loaded, since I am interested in maintaining Squeak
> compatibility as well ....
> >
>
> I glanced over the PharoCompatibility packages.
>
> GsPharo-Core:
>                 I don't see a problem. It is a superset of Squeak behavior
>                 and when there's overlap, the implementation of this
> package
>                 either is identical to Squeak's or equivalent in outcome
> and
>                 side effects.
>
> Multilingual-TextConversion:
>                 A bit tricky. This is some increment and refactorings to
> the
>                 classes already in Squeak, and they might be incompatible
> in their
>                 implementation. I think in practise this is not much of a
> problem,
>                 since these classes are typically used for their effect
> (Text conversion)
>                 and the TextConverter API is a strict subset of Squeak's
> TextConverter
>                 with IMHO all sensible methods.
> MultiByteBinaryOrTextStream is a lot
>                 slimmer than Squeak's but I don't know what this would
> mean.
>
>
>                 PS: TextConverter class>>default is missing, it is sent in
>                 MultiByteBinaryOrTextStream class>>on:encoding:
>
>
> HTH
>
> Best
>         -Tobias
>
> > Dale
> >
> > On Thu, Nov 20, 2014 at 12:12 AM, Johan Brichau via Glass <
> glass at lists.gemtalksystems.com> wrote:
> >
> >> On 19 Nov 2014, at 22:08, Paul DeBruicker via Glass <
> glass at lists.gemtalksystems.com> wrote:
> >>
> >>> Or is there some other library that helps with maintaining portability
> of
> >>> Pharo Seaside code (which uses FileReferences) vs GemStone code (which
> >>> still uses FileDirectories)?
> >
> > There is this guy: https://github.com/glassdb/PharoCompatibility
> >
> > But I would argue we merge it into GsDevkit, which is somehere on my
> road-mind-map if others agree ;)
> >
> > Johan
> >
> > _______________________________________________
> > Glass mailing list
> > Glass at lists.gemtalksystems.com
> > http://lists.gemtalksystems.com/mailman/listinfo/glass
> >
> >
> > _______________________________________________
> > Glass mailing list
> > Glass at lists.gemtalksystems.com
> > http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20141121/d10e51a0/attachment.html>