Hi, Mike... I see from the source on afpwebworks.com that you're using CSS as your layout method. Looks nice.
So you've tackled OO development and CSS, too? I'm impressed...the CSS just looks so aggravating to make work. I'm on one of the main css lists and I see those folks spending vasts amount of time just trying to make a layout work, when tables always work...and across browsers, too... I just wonder if "tableless" design is worth the effort. Also, what's your toolset for doing your development (OO) and design (CSS) work? And anything else you use... Thanks for the comments... Rick -----Original Message----- From: Mike Kear [mailto:[EMAIL PROTECTED] Sent: Saturday, April 08, 2006 12:20 PM To: CF-Talk Subject: Re: Newbie Model Glue Questions My 0.02c on this is that separating business logic from style and display has revolutionised my life. Since January I have been building five sites simultaneously. They have similar but not identical needs. I have taken the parts of the sites that are the same on all, and used an OO approach to make them They're all done (I built all five with the one set of code- i could have built a hundred of them and got them 90% finished in one go if had the orders for them!) At the time i started, I didnt think using OO was necessary, but since everyone was talking about it, I decided it was something I needed to know more about, so I persevered. As the project went along I started to see the benefits. I'd finish a function, start to test it, find that there was a tweak or a change that was needed and making the change was a breeze. What would have taken me hours the old way took me minutes this way. Far fewer 'variable not defined" errors (in fact that kind of error is almost unheard of now) - more things worked first time than I have ever seen in my life. I am certain that as life goes along and clients need changes to these sites, accomplishing the changes they want is going to be far easier than it would have been. I work on other programmers pages now as part of my contracting work, and I find it very frustrating. I can spend far more time looking for the line of code I need ot work on than actually doing the work. Separating logic from presentation, by using OO techniques and CFCs has meant that code is reusable. I have been able to copy 90% of one site to four others ***AND HAVE THEM WORK JUST LIKE THAT - FIRST TIME!!*** thus reducing the development time on each of those four other sites from weeks to a day or so. That day or so is spent writing the last 10% for the specific stuff they wanted and testing the site. Want to have a look at one of these sites? (Only one has been launched so far) - see http://afpwebworks.com Another is http://bluegrass.org.au. They are fairly straightforward but fully dynamic and I spend my time nowdays being FAR more productive than i have EVER been. I can take on FAR more work than I would have DARED to do before. I even have written a couple of simple code generation programs (in CF) to make it all happen even faster! I'm preparing an article for http://afpwebworks.com about OO techniques written for people like I was - who dont 'get it' yet and find the language used by OO afficianados difficult to fathom. But trust me, It's worth the effort to learn. Really. Even for simple apps. Cheers Mike Kear Windsor, NSW, Australia Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 4/9/06, Matt Williams <[EMAIL PROTECTED]> wrote: > Be careful Joe, you may be speaking over Russ' head. Acronyms like 'API' are > foriegn to the 'open a page in DreamWeaver/HomeSite and edit it' type of > people. > > I think the main point is that Joe and Russ agree on the idea that > frameworks are overkill for a simple web site. However, I would make the > argument that the code re-usability that frameworks encourage may make even > simple websites worth doing in an OO/Framework style. It seems more than one > client wants an event calendar, an email/contact database, etc. And of > course an admin to control these and other content. Building stand-alone > service layers for each of these types of things can make life easier and > code reuse more accessible. > > As for the frustrated designer, I would have to wonder what Russ' view pages > actually looked like. I find changing the css and layout to be easier with a > framework as I'm not wading through a bunch of queries or switch statements > or what not. And I'm able to reuse partial-page views more easily, so a > change to something in one place affects all - this is a good thing. > > > My 2 cents. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:237242 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
