House of Fusion
Search over 2,500 ColdFusion resources here
  
Home of the ColdFusion Community

Mailing Lists
Home /  Groups /  Fusebox

Community input for Fusebox 6!

  << Previous Post |  RSS |  Subscribe to this Group Next >> 

Community input for Fusebox 6!

Yes, we've only just released Fusebox 5.1 but we're already looking   Sean Corfield 02/09/2007 02:05 PM

02/09/2007 02:05 PM
Author: Sean Corfield Short Link: http://www.houseoffusion.com/groups/fusebox/thread.cfm/threadid:1312#6898 Yes, we've only just released Fusebox 5.1 but we're already looking   into the future and we want your feedback! Fusebox is a very stable, mature application framework. The basic   (XML) syntax hasn't changed much since Fusebox 4 was introduced   almost four years ago and pretty much every single Fusebox 4.0 and   4.1 application still runs unchanged on Fusebox 5.0 and Fusebox 5.1. Backward compatibility is extremely important to protect everyone's   investment in Fusebox so you can be assured that Fusebox 6 will also   run all those existing applications. So what can we do to make Fusebox a better framework? We've heard a lot of calls to keep it simple (or even make it   simpler) but we also hear requests to add new features. The recent   Fusebox survey provided a lot of useful information and we're still   analyzing that input. It's a fine line to tread to keep the framework   true to it's vision while we try to address all of that input! http://trac.fuseboxframework.org/fusebox/wiki/FuseboxFrameworkVision A couple of things have been discussed as "themes" for Fusebox 6 and   we'd like your input on these: 1. Lower the barrier to entry by introducing some default conventions   that help remove the need for XML configuration. For example, in the   absence of fusebox.xml / circuit.xml files, a request for   fuseaction=home.welcome should still understand a circuit called   "home" and a fuseaction called "welcome" and be able to "do the right   thing". Determining the right conventions is not trivial - we might   look to Ruby on Rails, for example. 2. Keep the core stable, i.e., don't add new features directly to the   core, but leverage the extensibility points (plugins, lexicons) to   provide optional packages of additional functionality. The Fusebox   5.1 skeleton hints at this with additional lexicons and I'm just   about to release an assertions plugin as an official extension.   Fusebox 6 could then become a suite of official downloads, perhaps   incorporating some sort of community-contributed "Fusebox Exchange".   Scaffolding is a specific example of something that has been   discussed as a possible extension for Fusebox 6. Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
<< Previous Thread Today's Threads Next Thread >>

Search fusebox

May 21, 2013

<<   <   Today   >   >>
Su Mo Tu We Th Fr Sa
       1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31   

Designer, Developer and mobile workflow conference