On 01 May 2014, at 21:32, GOUBIER Thierry <[email protected]> wrote:
> > De : Pharo-dev [[email protected]] de la part de Esteban > Lorenzano [[email protected]] > > > >> By the way, I have added a PharoExtras UIThemes project to Smalltalkhub, >> right in time it seems ;) > > yeah, the problem is that currently there are a lot of changes happening to > make the dark theme possible (I removed hardcoded colors everywhere, > re-direct default colors to theme everywhere, modified without any > contemplation packages like Morphic*, Spec* and Nautilus*… along with > Polymorph* packages, of course. > > Yes, I had a look in the Pharo3DarkTheme package :) well… I said it was a hack :P > > This is the only thing which dissuades me from using it right now :( The time > for the merge to happen on my netbook is just too long... And I have to do > screenshots for PharoForTheEnterprise :) > > So… I need to work a lot more in polishing, ensure all continues working, > make appropriate SLICES, etc. > I see this as part of the “tool oriented” direction of Pharo 4. > I shared because I think the result is good enough and people can take > benefit of having it (also, then people can help on making the work, he). > But in any case, is not close at all of being integrable to core image, or to > a standard theme project :( > But it will be, it has to :) > You've given us something to dream about, and to start to use to boot :) > > >> >> About a morphic redesign, I just had a look at Cuis to see how was their >> Morphic. > > yeah, not sure that I want to follow that path, but we need to start > discussing it :) > I know Alain Plaintec started to work on a new morphic, and I suppose best > scenario is all community joining efforts to achieve the goal, but for that > we first need to discuss/agree on a design. > I've seen Alain's effort the last time I went to Brest, but I never took the > time to try it. I think it's probably a good base; as it is use-driven, it is > important to exercise it with the most complex Morphic / Spec GUIs we can > build, which means community support. > > What happens now is that every morph is a HUGE ball of mud, with mixed > responsibilities and many dependencies to other “layers”: is very famous the > dependency of HandMorph with the event dispatcher (now cleaned), but that was > just an example. Now it is mixed with Polymorph in a very dirty way, etc. etc. > As it's easy for me to see that, it's also frightening to see how many > protocols in Morphic are extensions for packages which do not exist anymore. > And the complexity of all the PluggableXXX is frightening, and it introduces > serious performance problems. > > In a ver corse grained way, I imagine a future morphic well split in his > different concerns: graphic “atoms”, skins and widgets. > And with a more understandable layout API, and with simpler widgets to > connect to models, and with working caching so that we don't busy lock Pharo > when exploring long collections, and that Moose doesn't have to use that ugly > paging tree/list morph, and ... > > While still keeping what made Morphic so great in the first place :) > > Thierry > > cheers, > Esteban > >> >> Thierry
