The following are great starting points, but I would like to see something more actionable. For example an issue for each with enough info and clear goal for a community member to start coding straight away... stepharo wrote
Now there is a risk that alain does not deliver so we should - look at what he is doing - we try to document the classes - I'm trying to move some cleans/ideas from bloc to Morphic (introducing Margin, cleaning layoutFrame is a way to improve) - Since bloc runs inside morphic, cleaning morphic reduces the morphic behavior that creeps in Bloc
Here are some ideas to help - for example, if you want to make bloc use Athens transformation - write more tests - write stupid examples
- I'm cleaning menumorph and rewriting a menuMorph for Morphic with the hope that we can blocify the code so that I can propose some simple MenuMorph to Bloc. I'm busy with project proposal writing and other duties but if you want you can join.
- I'm doing the same with theme and basic widgets. - Can we do a simple button in Bloc? - clean the one we have in Morphic
Alain would like to use Athens for the rendering of Bloc elements .... so this is another nice project to help.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-Development-Robustness-was-Why-Bloc-tp4774980p47... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.