Were I not in the process of transitioning out of one position, relocating, and into a new position, then I would be offering my assistance immediately. However, as I won't have an internet connection for a while (much less the packing, moving, unpacking, etc.) I'll have to wait until I'm settled. I did want to take a moment to throw in my $.02.
My daddy always told me if you're going to do a job then you should do it right the first time. Although the initial planning may take longer it is definitely worth while to make this an OO application. It is actually easier (by far) to modify and extend a well documented OO app over a procedural app. It is easier to design and apply extension modules/components. It is easier to track your program flow. Using DAO CFC's will allow you to extend the app from a multitude of database platforms. A complete separation of the business logic from you control and presentation layers will force a developer to concentrate on the data to be presented rather than the presentation (which could then be output in HTML, XHTML, XML, or even Flash). And, since you are already planning on using CFC's, a loosely coupled MVC OO approach will break down the project into easily defined subprojects. This type of approach would also make it very easy to port into most existing frameworks (Mach II, Fusebox, Model-Glue, etc.) Would an OO approach alienate a majority of users? I don't think so. If you offer a superior product, with the features they want, then the users will take the time to read documentation to make it work for them. These aren't advanced programming concepts, they're good programming practices. Those of you looking to turn this into a learning experience will gain a much better learning experience by moving forward from an OO standpoint. My two $.02. Hope it helps. Cutter dave wrote: >most of that sounds good but some of it is a bit over the top. >If you make it 00 then it will alienate a good majority of users, needs to be >simple enough that the average user can modify it. >Some of the xml stuff is over most peoples heads, maybe we could end up with 2 >versions and the 2nd can be a paid version with all that stuff. >I know a lot of people will want to show off their skills but i think it needs >to be user friendly enough for beginners to use it since they will be using it >probably the most and for those ppl we try to get from php and such it will be >an easier conversion. > >Have you noticed the ppl (including myself) that are volenteering aren't the >"experts" on here? If it's gunna be 00 then you lose those helpers and since >most of the higher end coders on here won't be helping so who's gunna go in >and make all our stuff 00? > >other than that good plan. >While you are doing that I will start on the base code and css. >What are your opinions on that? >I personally am using xhtml strict and mostly cssp on my current stuff, I >don't mind being in charge of the base code stuff but lets agree on what to >start with. I'll be more than happy to take each persons code and make it >validate and all that good cross browser stuff. > >~Dave the disruptor~ >"Some people just don't appreciate how difficult it is to dispense wisdom and >abuse at the same time." > >---------------------------------------- >From: "Andy" <[EMAIL PROTECTED]> >Sent: Thursday, November 10, 2005 12:12 AM >To: CF-Talk <[email protected]> >Subject: RE: Open source shopping cart > >Here are my thoughts: >1. OO >2. Design to be extended without taking out of upgrade path(pre & post >processing steps) >3. Provide DLL's >4. XML in and out with appropriate XSD's >5. Sample HTML and/or XSLT with CSS that can be used as a base > >Starting with someone elses data model is like starting coding without >requirements. If we want to do this right, we need to start at the >beginning. If we all chip in with the IC that we have this shouldn't take >too much time to get through the documentation phase. At each stage, we >create a forum for the individual parts, each of use signs up for those that >they can contribute to, someone takes lead for each...We finish then move to >the next step of the design. Continue until done, then move to Detailed >Design. While Use Cases are being created, the Archeticts can start >creating the framework within which detailed design and coding will operate >within. > >Bottom line, this needs to be run like a large scale development project. > >Andy > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224121 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
