Thank you Lukas, I will look at this. Laurent
On Mon, Dec 26, 2011 at 11:52 AM, Lukas Renggli <[email protected]> wrote: > For Seaside 2.x this is the global variable SeasidePlatformSupport > that has to be bound to some implementation (this was a bit hacky). > > For Seaside 3.x this is the abstract class GRPlatform, and the Pharo > implementation is GRPharoPlatform. There are countless *-Pharo > packages that add Pharo specific code (mostly to GRPharoPlatform). > > For OmniBrowser this is the abstract class OBPlatform, and the Pharo > implementation in OBPharoPlatform. It redirects some of the preference > code. For the UI differences this is the abstract class OBInterface, > and the Pharo implementation OBPolymorphInterface. Again the code is > in platform specific packages, so you typically won't see the code for > other platforms. > > Lukas > > On 26 December 2011 11:38, laurent laffont <[email protected]> > wrote: > > On Mon, Dec 26, 2011 at 11:31 AM, Lukas Renggli <[email protected]> > wrote: > >> > >> > I do not get why Seaside should provide a package to deal with > >> > Preferences a la squeak? > >> > I imagine that Seaside does not rely on Preferences so. > >> > >> Indeed, Seaside does not deal with Preferences, but the question was > >> about how to deal with differences in general. > > > > > > Yes. > > > > Lukas, do you have some Seaside / OB class names in mind so I can find > > faster ? Thanks > > > > Laurent > > > > > > > >> > >> > >> Lukas > >> > >> -- > >> Lukas Renggli > >> www.lukas-renggli.ch > >> > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >
