On Mar 23, 8:38 am, Dan Wilson <[email protected]> wrote: > The Status Of Model Glue 3: Gesture
First, Dan, thanks for taking this on and delivering. Much appreciated. > Model Glue 3 (MG3) has been under development since Early 2008. The product > first debuted at CFObjective 08 and listed a number of productivity > improvements and an event driven core to the existing Model Glue platform. Take my feedback here understanding that I have not experimented with MG3. I have been unable to find a complete description of if/how to migrate and what's new to invest the time in it so far (particularly without any guidance on the status of the code - no known bugs is a useful update). The fact that MG3, which appears to be an evolution rather than a leap, has been in quasi-development for well over 12 months is a problem from my perspective. This can be partially mitigated by having a reasonable roadmap of releases and goals for the future to help confirm that the framework is not dead in the water and then fully mitigated by delivering on that roadmap. The royal "we" of the community are not (too) greedy, so long as expectations are set properly I think we'll all be happy as clams. > 1) Scaffolding > MG3 has no scaffolding engine in it. There was discussion about removing > it for MG3 but this would break backwards compatibility. We've not yet come > to a conclusion of whether to just port the Scaffolding engine from MG2, or > to work on a new and improved Scaffolding engine. There are some highly > qualified folks offering to take this on. I think preserving backwards compatibility is reasonable (in which case a port is perfectly fine). I don't use it, but I think it's worthwhile to keep the majority of people on the latest release. > 2) Documentation > The documentation for MG3 is non-existant. Some cursory documentation > exists for the new features. Normally, we would simply edit the MG2 > documentation with the new MG3 features. Practically, the source docs for > MG2 are AWOL and this necessitates a complete documentation rewrite. As > expected, no one really wants to take this on. There was an offer from Rick > Stone - RoboHelp ACE that might be of help. I'm due to follow up with him. > (see the Friday > Puzzler:http://www.coldfusionjedi.com/index.cfm/2009/3/13/Friday-Puzzler--Hel...) I really like how Mandel is doing Transfer documentation with CodexWiki. I guess the MG3 wiki can't be a Coldbox application :) , but I find the content approachable and it's updatable. When you say the source docs are unavailable, what do you mean? Docs.model- glue.com still exists and while kind of thin on content, it covered the basics. The #1 most important document in my mind for the Beta is a simple Migration guide with a "What has changed" and "What's new to try". I'm happy to do testing on my (fairly complex) app. If someone takes a little bit of time to write this guide, the rest of us can leverage that work and very quickly try out MG3. > 3) Example Applications > We want to ship the product with several example applications. I have > some I'll submit and others on the team will contribute as well. I'd rather see the two other things prioritized over this. I consider example apps "nice to have" and they require a pretty significant amount of work. Remember how actionpacks really never materialized? Thanks again for the update, Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
