<soapbox> It's my opinion that this project is lacking focus in 2 very import areas and John touches on one of them.
First, who is the intended audience of this project? Define that and many questions will start to be answered. Second, what's its purpose? Or said another way, what is its functionality, is it going to include the kitchen sink or not? As Dana said on the forum, we're arguing over whether to use pencils or pens and we haven't even decided what we're drawing. There needs to be a project manager/project owner who helps define these questions and then has measurable milestones so such a diverse and dispersed group will even know what is/isn't being accomoplished. Maybe this is being too much of a PHB on the list here, but I think this is doomed to fail if some structure isn't put in place. And ya' know, if you don't agree with what's done, that doesn't stop others from doing their own (e.g. one completely OO and one not). </soapbox> Marty On 11/14/05, John C. Bland II <[EMAIL PROTECTED]> wrote: > > Fella's, I have to back out of working on this project (conflict of > interest; my company is building an enterprise e-comm project). Sorry. > > I do want to respond to the OO portion before I completely sign off of > this > task. > > <2cents willRespond="only if necessary"> > Making it OO will only alienate those who want to do some sort of custom > development and don't know OO. If they want to do something custom then > they > should read the docs (that should be well thought out and written). As far > as the updates they'll desire, it shouldn't be anything more than > graphical > or at best a config change. If they are revamping the entire thing or even > a > healthy portion they are only using the cart as a guide. > > If it were strict OO with a config file setup the developer would only > need > to touch the css, images, and config file. Maybe an occassional include > somewhere for a layout fix. osCommerce is a plug-n-play system. ZenCart is > a > plug-n-play system (can update just about everything from the admin so no > code knowledge is needed). All of these free systems are there for you to > drop in, customize, and launch. If you want something custom, starting > from > scratch would probably be best. I mean, using MVC would seem easier for me > to come in and customize than procedural. All you'd need to do is update > the > views and you're done, unless you're overhauling the functionality in some > way. > > I think it boils down to who this product is for. Is it for developers or > e-commerce clients? If its geared towards developers, do what's best for > them. If its geared towards clients, do what's best for them. > </2cents> > > L8r... > > On 11/14/05, dave <[EMAIL PROTECTED]> wrote: > > > > 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)" <[EMAIL PROTECTED]> > > Sent: Monday, November 14, 2005 2:49 PM > > To: CF-Talk <[email protected]> > > 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:224155 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
