the advantage of a roadmap is that allows people that can agree on principle on a specific kind of approach can work together as a team towards a common goal under the same project. Yes! For example, with event handling, it's not so much that I didn't want to offer a cool alternative, but that in the limited time I have to work on it, I'd prefer to benefit from the extensive research and design decisions that no doubt have already been done as others have looked at the problem, instead of starting from scratch. Plus, there are plenty of other areas to occupy me that are not being worked on AFAIK.
Also, it would also be a great way to document design decisions, both to align us now, and also for the future. One of the things that I often feel holding me back is that I have no idea what the design decisions were, and so fear that something important (e.g. flexibility, future extension, etc) may be lost by cleaning and simplifying. For example, when we created distinct WorldMorphs vs. PasteUpMorphs, we lost the ability to promote PasteUps to act as the world. How important was that? IDK. But I only realized after because the design was IMHO a bit unclear and AFAICT undocumented. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Improving-communication-and-roadmap-tp4815705p4815790.... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.