ANN: Already Working on Mach-II 1.8 'Simplicity' - New Feature Specs Ready
Peter J. Farrell
gearing up for Mach-II 1.8 -- code named "Simplicity". We have a lot of
exciting features we want to add. We have two M2SFP specification
documents finished already and they have been published on the Mach-II
wik at trac.mach-ii.com in the documentation section.
View-loaders allow you to load page-views by convention (no more
manually adding entries to your config XML) and the call-method command
lets people who are using ColdSpring call simple service layer methods
directly from your XML without any listener code in between. For a
brief overview of these new features, please read our blog post on the
subject:
http://tinyurl.com/6l5ke9
The blog post contains the links to the *complete specifications* that
we have published. Be sure to check out the specifications on the
exciting new features we detailed in the blog post and remember that
your comments go along way in keeping the project going in the direction
that the community wants -- so feel free to share your thoughts with us.
Best,
Peter, Kurt, Matt, Brian and Kyle
Team Mach-II
P.s. There has been some problems with the Captcha on the blog so we
have turned it off so people can make comments easier.
Dave Shuck
Nice job in the innovation department. :)
~Dave
Splice
Hey is there still a plan to add conditional processing to the mach-ii
config file? Similar to how modelglue allows "listeners" to post event
args, and then the framework can check for a value and take action
accordingly, instead of having to have the listener itself broadcast a
new event.
ModelGlue:
<event-handler name="do.process_login">
<broadcasts>
<message name="process_login" />
</broadcasts>
<results>
<result name="InvalidLogin" do="view.login_failed"
redirect="true" />
<result name="ValidLogin" do="view.home" redirect="true" />
</results>
</event-handler>
Essentially if the listener sets a special kind of event-arg (called a
result in this case), it acts as a flag for the framework to choose to
run a particular view. I am not sure if it's conditional processing
is more involved, but that is what I have used it for in the past. I
much rather would handle the announcing of all of my events from
definitions in the mach-ii.xml, instead of announce() method inside of
my listeners. Personal preference.
I know that you were working on something like this.
Cheers, Brian.
Peter J. Farrell
There's not much difference in what you are requesting and M2's event-mapping command. Results in MG are basically announcing a new event with the results section mapping a "generic" action to an event-handler.
This can be accomplished in M2 using event mappings in your even-handler xml. The only difference is in 1.6 event mappings don't have the redirect flag. We're going to addres redirect enhancements in 1.8.
I'd check out using event mappings as that will accomplish what you are asking.
.Pjf
-----Original Message-----
From: Splice <bhe...@gmail.com>
Date: Fri, 21 Nov 2008 08:56:21
To: Mach-II for CFML<mach-ii-for...@googlegroups.com>
Subject: [Mach-II] Re: ANN: Already Working on Mach-II 1.8 'Simplicity' - New
Feature Specs Ready
Splice
Enjoy your Vacation Peter, and get off these forums!!
-Brian