The action pack sample application has not been developed past the "experimental" stage, and it shows. To quote Douglas Adams, its fundamental design flaws are completely hidden by its superficial design flaws.
I can see many problems with keeping a sample application in that kind of state in the official Model-Glue distribution. If the community can get a separate action pack project off the ground I'd be more than happy to push for migrating the action pack sample (along with the two action packs which are not used by anything else) over to that project and dropping it from the Model-Glue distribution. We could always bring it all back in again once its in a usable state. Cheers, -- Dennis On Thu, Mar 4, 2010 at 2:25 PM, Fernando Lopez <[email protected]> wrote: > I can start going through the Hello World and see what I can do from there. > > The Action Packs Sample app had a small issue with database table names and > Primary Key columns that were not defined as auto increment and that was > causing problems on the DAOs. So I could work on that one next. > > Any other that is of particular interest to the group? > if you were a completely novice in MG what kind of application would like > to see ( from the sample ones we have available) work from beginning to end? > > Fernando. > > > On Thu, Mar 4, 2010 at 11:43 AM, Dan Wilson <[email protected]> wrote: > >> Hi Fernando, >> >> We'd love some help on updating the sample applications. Which one would >> you like to help us with first? >> >> >> DW >> >> >> On Thu, Mar 4, 2010 at 11:30 AM, Fernando Lopez <[email protected]> wrote: >> >>> That explains it. >>> >>> Thanks Ezra. >>> >>> Is there a group or committee that works on the sample apps? it is a >>> bit frustrating to jump on MG all excited about new features and such >>> and then have the sample apps bomb on you. >>> >>> I'm not complaining (too much), but if there's an entity like that I'd >>> like to see how I can help to keep those samples apps in sync with >>> what the framework offers. >>> >>> Fernando >>> >>> >>> On Mar 3, 12:20 pm, Ezra Parker <[email protected]> wrote: >>> > Hi Fernando, >>> > >>> > In their earliest incarnation, event types were created via CFCs >>> > rather than defined in the MG XML, and the sample actionpacks both >>> > contain examples of this implementation. (As a side note, this is >>> > something that I personally would like to deprecate and ultimately >>> > remove in favor of always specifying event types in XML). >>> > >>> > So the MainTemplateEvent CFC is indeed defining an event type for the >>> > actionpack -- in XML, it would look like this: >>> > >>> > <event-types> >>> > <event-type name="MainTemplateEvent"> >>> > <after> >>> > <results> >>> > <result do="template.main" /> >>> > </results> >>> > </after> >>> > </event-type> >>> > </event-types> >>> > >>> > HTH, >>> > >>> > -- >>> > Ezra Parker >>> > >>> > On Wed, Mar 3, 2010 at 7:40 AM, Fernando Lopez <[email protected]> >>> wrote: >>> > > I started looking into MG3 and Action Packs recently and I went >>> > > through the installation of the ActionPacks Sample app. After finding >>> > > a couple issues that I'll explain in a separate entry I got the >>> sample >>> > > application to work. >>> > >>> > > Now I'm going through the code and the first thing I see under / >>> > > modelgluesamples/actionpacks/config/modelglue.xml >>> > >>> > > is this >>> > > <event-handler name="page.index" >>> > > type="modelglueactionpacks.common.event.MainTemplateEvent"> >>> > > <views> >>> > > <include name="body" >>> template="pages/index.cfm" /> >>> > > </views> >>> > > </event-handler> >>> > >>> > > I thought that the attribute "type" in an event-handler would have a >>> > > value from the <event-Types> section of the XML. but I looked >>> > > under the /modelglueactionpacks/common and /modelglueactionpacks/ >>> > > usermanagement and I cannot see any event-type defined as >>> > > "modelglueactionpacks.common.event.MainTemplateEvent" I do however >>> see >>> > > a MainTemplateEvent.cfc defined at that location. >>> > >>> > > Contents of that CFC are below. >>> > >>> > > Could anybody explain what is happening and why the event handler >>> type >>> > > is pointing to a CFC instead of a event-type?? >>> > >>> > > If I'm missing something I'd be grateful to whoever can explain what >>> > > it is that I'm missing. >>> > >>> > > Fernando >>> > >>> > > -------------------------- >>> > > modelglueactionpacks/common/event/MainTemplateEvent >>> > > -------------------------- >>> > >>> > > <cfcomponent extends="ModelGlue.gesture.eventhandler.EventHandler"> >>> > >>> > > <cffunction name="afterConfiguration" access="public" >>> > > returntype="void" output="false" hint="Called after configuring the >>> > > event handler. Subclasses can use this to add messages, results, or >>> > > views after they're added by something like a ModelGlue XML file."> >>> > > <cfset var result = createObject("component", >>> > > "ModelGlue.gesture.eventhandler.Result") /> >>> > >>> > > <cfset result.event = "template.main" /> >>> > >>> > > <cfset addResult(result) /> >>> > > </cffunction> >>> > >>> > > </cfcomponent> >>> > >>> > > -- >>> > > Model-Glue Sites: >>> > > Home Page:http://www.model-glue.com >>> > > Documentation:http://docs.model-glue.com >>> > > Bug Tracker:http://bugs.model-glue.com >>> > > Blog:http://www.model-glue.com/blog >>> > >>> > > 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]<model-glue%[email protected]> >>> > > For more options, visit this group at >>> > >http://groups.google.com/group/model-glue?hl=en >>> >>> -- >>> Model-Glue Sites: >>> Home Page: http://www.model-glue.com >>> Documentation: http://docs.model-glue.com >>> Bug Tracker: http://bugs.model-glue.com >>> Blog: http://www.model-glue.com/blog >>> >>> 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]<model-glue%[email protected]> >>> For more options, visit this group at >>> http://groups.google.com/group/model-glue?hl=en >>> >> >> >> >> -- >> “Come to the edge, he said. They said: We are afraid. Come to the edge, he >> said. They came. He pushed them and they flew.” >> >> Guillaume Apollinaire quotes >> >> -- >> Model-Glue Sites: >> Home Page: http://www.model-glue.com >> Documentation: http://docs.model-glue.com >> Bug Tracker: http://bugs.model-glue.com >> Blog: http://www.model-glue.com/blog >> >> 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]<model-glue%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/model-glue?hl=en >> > > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > 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]<model-glue%[email protected]> > For more options, visit this group at > http://groups.google.com/group/model-glue?hl=en > -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog 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
