Thanks thanks thanks for asking!! Building a group of people on that would be excellent. What would be good is - have a look at the EventModel package because we cleaned the low level event raised by the vm not the morphic management of them - reduce the direct use of sensor in the morphic world and probably other (lower package than morphic) - clean a bit the event handling - look how to integrate fernando modeling of event handling: state pattern + distribute responsibilities of HandMorph into several classes because HandMorph is doing too much - we want to remove DependentFields from Object and we should probably follow what CUIS did: i.e. reexpresse changed/update using the EventManager - look in MC and make sure that MC classes are subclasses of Model - reduce the API of the event Manager on Object: probably just couple of methods is enough. - Ideally we should remove the changed:/update protocol because it broadcasts and replace that with something around on:send:to: - Remove as much as possible of respondsTo: for UI widget. - Adding Anchor layout developed by Igor so that we can specify that a widget is attached to a border. - rewriting all the drawOn: methods into drawOnAsAthens: so that we can remove the old canvas - Integrate the CUIS layout that fernando integrated. Doing that would be already a good achievement! So let us know if one is exciting for you. Stef
Stéphane Ducasse wrote
Open a bug entry and propose a solution like that we get itâ¦. ;)
I've submitted little improvements as I've come up with them, but in general, I'm unclear what to do about Morphic. Also, I don't want to overlap with existing efforts. For example, I started to clean the event handling and then found out you were already working on it. If you have any ideas, I'd be willing to try. Is there a Morphic roadmap?
Sean
-- View this message in context: http://forum.world.st/Pharo-project-ANN-Spotlight-like-morph-for-pharo-tp458... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.