Even further than that. Some people will want to do something with it that nobody else in the world does with a shopping cart. That's why it's important to make it using the most easily extendable and modfication-friendly codebase as possilbe. Also, you leave the door open for others to easily add modules that aren't really "store" modules, but that a store owner may require. I hate buzz-words and so I'm not going to get into OO or not OO or anything like that, but when you build something like this, it's a good idea to make it as modular as possible so that it is as useful as possible to more people.
--Ferg >From: "Snake" <[EMAIL PROTECTED]> >Sent: Tuesday, November 15, 2005 3:11 PM >To: CF-Talk <[email protected]> >Subject: RE: Open source shopping cart > >If a cart is properly written, you shouldn't need to understand or change >the code to use, it should work out of the box. >So whetehr or not it uses CFC's should be neithe rhere nor there. As I state >dpreviously, most people who us ethe cart will want to use it out of the box >and and wont even want to look at the code. Those who want to get dirty in >the code and change it are most likley going to be capable of doing so. >Good documentation should also make it posisble for anyone to make minor >modifications. > >Russ > >-----Original Message----- >From: dave [mailto:[EMAIL PROTECTED] >Sent: 14 November 2005 23:22 >To: CF-Talk >Subject: Re: Open source shopping cart > >Personally, I don't think that it would be good to go 00 at all. >After all there are very few people who ACTUALLY use 00 and I see this as a >2 fold project, one to get us a good cart system and two to help get a few >people over to cfm and lets be real, probably 95% of the people who would >use this couldn't write their own cfc and sure it's easy to tell them to go >learn but reality says they won't and they will go over to php and use a >freebie over there. > >Hell if it was strict 00 I probably wouldn't even use it!! > >I agree it would be cool but I don't see a point in making it so 5% of the >people could use it. >If you do that then might as well make it only operate on computes that are >using 2 monitors. > >If it's made decently then the "eletists" can spend a few hours on thier own >and make it 00. > >I think the important parts are that it should look good, be safe (form >cleaning up and such), be secure and be able to plug it right in and have it >work within a few minutes and have the ability for the programmer to >customize it how they want without having to learn anything major and yes 00 >is a major thing. > >Cartweaver is a good example, you can plug it in and in a few minutes have >it working but it's also $250 and not in cfcs and there are some security >concerns but the example is good because you can just "use" it or customize >it without learning 00 or fusebox or whatever. > >And in these times where if the programmer has to spend a ton of time >learning it or whatever they will just go to yahoo stores or miva merchant >or some crap like that. > >~Dave the disruptor~ >good sites - make money getting rid of ie :) http://explorerdestroyer.com/ >http://www.killbillsbrowser.com/ > >---------------------------------------- >From: "Cutter (CF-Talk)" >Sent: Monday, November 14, 2005 2:49 PM >To: CF-Talk >Subject: Re: Open source shopping cart > >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 > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224247 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
