hi all please forgive this basic-level request for an overview about Fusebox, but I'm just trying to get a better understanding on the big question "why".
the last month or so has been my first real use of Fusebox. Sadly, it's an FB3 app of a couple of years old that I'm extending/maintaining. In it there's bugger-all business processes abstracted into functions (just heaps of qry_, act_ and dsp_ files) and what CFC's that have been added are full of display code (HTML/JS for pete's sake! - someone before me obviously got the wrong idea with CFC's...). Also, cardinal sins of having too much logic embedded within the fbx_switch files makes it a bit of a challenge to appreciate what Fusebox does (and why). I really miss having the controllers I'm used to and sometimes it feels like FB is getting in the way or making things more complicated than it needs to be. that and being annoyed by the lack of abstraction like variables, queries, etc, created in one cfinclude but referred to in another within the same switch. it just seems to make it harder to get a good (quick) top-level grasp of each business process. it may just be this old version or how it's used, but FB feels like it's suited to easily build only one type of app - common head/footers, common nav, menues, etc, but with changing "guts". The use of Remoting, Ajax calls and self-posting forms are do-able but not quite as straight-foward to what I'm used to. is this a fair summary or have I got a dog of an example to be underwhelmed by? Sure this is FB3 and FB5.1 is now out there, but as far as the core features of cascading fbx_switch and fbx_settings files, what pain do these actually solve? any advice, opinons most welcome thanx You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
