Shawn, I will provide my 2 cents on this, but ultimately it's about choice.
IMO: Frameworks are a way to enforce some aspects of good OO design in a repeatable and consistent way so that other members of a team, or you yourself in two years when this is a distant memory, can rely upon code being constructed in a consistent manner which is easily re- found and hopefully understood. A framework puts a lot of good OO practices on the field and people can use them successfully if they understand why these pieces exist. The problem, to me, is that many people try to use frameworks *instead* of learning good OO practices (as opposed to *with* learning good OO practices). The result is some of the worst code I have ever had the pleasure of untangling. So, from the beginning, I think you are going to wrong way. If you are relatively new to coding then it seems unlikely that you have the requisite knowledge to create a viable framework that will really stand the test of time or enforce consistent patterns. Further, others (many others) have done this work for you. If you think, however, that you will be able to either create a framework or correctly use one without getting your head around a large number of OO concepts, then I think you are wrong. Honestly, examples are great, but unless you understand at least some of the 'why' and not just the 'what', you are going to run into different variations of the same problems. For what it's worth, Mike --- In [email protected], "shawn.gibson" <[EMAIL PROTECTED]> wrote: > > > read up on your options. There are many good > resources and opinions about frameworks online. > > Am I barking up the wrong tree by trying to discover places on the web > that would help me build a framework based on Flex 2.0.1 or Moxie > using ColdFusion (no fds/lcds) and MySQL/MSSQL? As an artsy guy, I am > better at creating things, than for example trying to take something > complex like Cairngorm and force my brain to work within its constraints. > > Services seem so critical that splitting it up with a full > model/view/controller/services design makes sense to me (the app I'm > building is currently almost entirely HTTPServices for the front end, > the e4x/xml files for which are built from CF scripts that pull the > data from a SQL db and generate the xml files - i.e., CF builds the > the backend/admin area data for use as the front end--client--xml > files). There are also aspects (like blog-type entries) that make much > more sense to use remoting over HTTPService in the front end. The > reason for this approach is that not everyone has CF, and I want to > offer (this will be for free, open source to all) at least the gallery > to people who can go and manually recreate the xml files in notepad if > necessary...no CF required. > > Philosophies/examples using MCVS with straight Flex 2.0.1 and CF7.0.2 > are what I think I need to use as my entry point into all this. > > Shawn >
