However also, there is a lot of setup involved as a new fuseboxer to create each application, if that can be simplified or automated that would really help.
However what this class is introducing me to, is the real necessity for frameworks or methodologies in coldfusion...
Jared is damn smart, I may ask a lot of stupid questions, because I want to get a full understand, and having only worked on 1 fusebox application, in terms of incorporating it in an existing non-fusebox application, it can be difficult to grasp.
I find that fusebox can be a great doorway to learning more of frameworks and getting more polish into your professional skill set.
I find that very vital...
Here are my afternoon class notes for my fellow classmates in MCTC. And we had a great lunch at Davanni's oh man that was filling.
------------------------Afternoon Class Notes --------------------------------
Installed CFMX 7
Installed Dreamweaver 8 YUCK!
-Controller - xml files, configuration of all fuse actions????
-Model - CFM Files
-parsed - parses xmls and compiles directives and cfml template and executes
-plugins -fusebox plugins cfm templates, referrenced from the xml file
-view -interface files, form tags, table tags
-Controller Circuit main.prodlist
-Model query select * from tblProds - getallprodsqry.cfm
-View -/include dsp_prodlist.cfm Include layout.main.cfm name=body
layout.cfm looks like this
Saves whole app to the parsed folder -- Worth investigating
For each fusebox application, you have to reconfigure, drop skeletalMVC folder/files
precedenceFormOrUrl either do form or url grabbing...which takes precedence...
password - force fusebox to reload a file in the parsed folder
mode - development vs production
This is the configuration file fusebox.xml.cfm
Each application would get it's own configuration file.
enumerate what does that mean?
-a symantic improvement
scope prioritization, scope variable searching...
page context level for each variable scope
1. Plan it out
2. Create model
3. Create views
4. Create XML behind two
Nifty circuit aliases, to reference functionality in different parts of the application
circuit access="public" vs access="internal"
internal mode is kind of interesting...
Fusebox can be fun to play with, I am not sure about it's scalability or index.cfm?fuseaction issue, how it appears the developer does matter, and I am fine with that. If the two main issues are dealt with i am fine.
I am curious about the process of the compiling into parsed files...
Why not have the database do it's parsing of content and then in a stored procedure get the call of what content to display. Point being why not have the database do all the work instead of having coldfusion do it.
Controller gets the request and passes the work on to model then displays results via view.
use fusebox tags rarely unless necessary...
Where we loop thru each fuseaction and create a physical file for each that actually calls the fuseaction,but how does that deal with form or action pages. Unless it was done via a cfinclude.