I would love a quick and easy refactor in which we add a FLSmalltalkPlatform with some utility methods such as #globals. Then concrete subclasses like FLPharoPlatform which implements #globals in our current way. That refactor would be quite easy and useful. I don't want to add Grease or whatever layer.. but just very concrete examples like this one. Thoughts?
On Sat, Nov 2, 2013 at 12:46 PM, Max Leske <[email protected]> wrote: > Thanks Nicolas, we’ll take a look at it. > > Max > > > On 02.11.2013, at 14:43, Nicolas Cellier < > [email protected]> wrote: > > I've opened https://code.google.com/p/fuel/issues/detail?id=204 with an > attachment > > Also note > https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteger-up-to-32bits-magnitude > > > 2013/11/2 Max Leske <[email protected]> > >> So far we don’t have a public inbox and I’m not too familiar with STHub >> and read/write permissions. Concerning your suggestion from the other >> thread a public inbox would certainly make sense though. >> I’ll let you know what we can come up with (STHub seems to be down right >> now so I can’t even give you access right now. But you can send me your fix >> through mail). >> >> Max >> >> On 02.11.2013, at 09:46, Nicolas Cellier < >> [email protected]> wrote: >> >> Thanks, and is there a public .mcz inbox, or does it require special >> rights? >> >> >> 2013/11/2 Max Leske <[email protected]> >> >>> The Fuel bug tracker is hosted by Google: >>> https://code.google.com/p/fuel/ >>> >>> On 01.11.2013, at 22:42, Nicolas Cellier < >>> [email protected]> wrote: >>> >>> > I have an easy fix for Fuel on Squeak trunk. >>> > It concerns the FuelCompatibility layer, so I hesitate to publish on >>> Pharo fogbugz... >>> > Is there a dedicated bug tracker? >>> > What is the preferred procedure? >>> > >>> > Nicolas >>> >>> >>> >> >> > > -- Mariano http://marianopeck.wordpress.com
