[Pharo-project] [Seaside] Re: [Metacello] What is the plan with Pharo changes?
Mariano Martinez Peck
marianopeck at gmail.com
Sat Aug 4 11:21:27 CEST 2012
Hi all. I am answering to all together:
Stef: Yes, I imported and loaded the Pier of DBX website in Pharo 2.0 with
seaside and magritte. With 5 minutes of opening debuggers and change things
I was able to correctly make it work (at least, my app, I didn't run all
tests to see).
Dale: We don't want to just help you with "hacks", that why I send this
email and several others, to see what others think so that can find better
and non-hacky solutions. So, let's try to find good solutions:
1) does it help if we put back FildeDirectory and we remove it later ? so
that you have time to update Metacello and that we can still use Metacello
2) for the SystemChangeNotifier does it make sense to delegate to the
closures? [ xx ] valueWithoutSystemNotifications. Or we add a
#doSilently: and we add a MetacelloPharo20Platform that overrides the
3) as Janko said, what about improving/using Grease/Sport for this purpose?
do they provide something for this? could this be added?
4) Should we integrate Metacello in the image with our changes until you
have time and find a good solution that works everywhere? Maybe if we do 1)
it is not very necessary.
Thanks for considering this a friendly and positive thread.
On Sat, Aug 4, 2012 at 9:16 AM, Janko Mivšek <janko.mivsek at eranova.si>wrote:
> Hi Dale,
> Dne 04. 08. 2012 07:31, piše Dale Henrichs:
> > The bigger problem is that I have to have a code base that runs on
> multiple platforms while being maintainable, so a "port" to Pharo-2.0 is
> only a starting point. In the case of FileTree, which is the real
> bottleneck there's a lot code that is written against the FileDirectory
> API, so there will need to be significant work to find a way to keep a
> common code base .... a much tougher problem, than "just getting it
> working", it can be solved with time, but I didn't budget time for an
> emergency rewrite of FileTree ... today.
> Just FYI, there is a Sport portability library and by using Sport's
> SpFilename you have an instantly portable file support over quite a
> dozen Smalltalks. So, if someone adapt Sport to a new Pharo 2.0
> filesystem first ..
> Best regards
> Janko Mivšek
> Smalltalk Web Application Server
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-project