On Jun 16, 2009, at 10:10 PM, Nicolas Cellier wrote:
http://code.google.com/p/pharo/issues/list?updated=890 ready for inclusion Use SLICES described in my last comment
Sorry I left some garbage in the PharoInbox, but it's quite unhandy to manage incremental dependency (when order of changes DOES matter).
I will clean it up. And yes this is not really satisfactory.
Wouldn't atomic loading be an easy solution for such problems?
in theory it would and I would love to. Now I need a week without students, emails, papers and I want to have a look at MC1.5 but so far I could not find the time.
I usually don't complain, but here are my feelings: <rant> Monticello is quite a drag,
I think that monticello is really cool compare to cs. Now with atomic loading and other speed up it should be really better
and pharo feels globally unresponsive (even the core image).
I'm planning to replace package info by some real packages but it takes times
I still experiment some lost keystroke and menus are sometimes gooey.
this is strange because on mac we do not have that behavior
It's not rare I click on the wrong item. If 3GHz Intel core2 duo 64 bits really becomes a requirement, I will give Cuis a ride to get some fresh air ;)
It should not. But really we are really paying attention to go faster on the UI level So I hope that the morphic cleaning + sensor will pay off.
To me UI feel is mitigating all the good job made so far.
we are doing our best. But we accept speed up proposal at the scrollbar level If somebody wants to integrate the speed up made on cuis for the UI then feel free. I think that once 1.0 is out of the door the first thing we should do as a community is to take time to rethink our tools. Stef