Tally List : mailing list management, archiving, and analysis
click for archive home
 
Archive of:
Fusebox
Cold Fusion Fuse Box List
 
home
24 hour view
quick stats
weekly updates
 
all tallylists
corporate solutions
archive your favorite
help / feedback


Search the Tallylist search by keyword:

About CF Fusebox Methods :
product's home
product's list home
 
  Archived TallyList / Fusebox: 
Subject: RE: Porting Old Site
Bill King (7p/+0r)     Posted: Thursday 10 May 2001
This post: 49 views, +0 rating

I think it is great that you have this opportunity now: to make this decision while you still can.

I have faced this decision scores of times. I think that there are always useful code in the sites that others have built. The most common problem is that the kind of development you mentioned is always built on a shaky foundation with little convention and a wrenched code base [one that the developer(s) built based on a moving target.]

I think that you will find that if you can build the structure of the site, easily, with fusebox now then you will be able to dissect the components (i.e. queries, forms, business rules, etc.) and transplant them in the process.

I think the previous posts have the right things to say, but my answer would be: something like the Bionic Woman...take the metallic computerized pieces from the current site and insert them into your new body.

Signed,

Bill King HostWorks INC http://www.hostworks.com

-----Original Message----- From: Jay Jennings [mailto:jennings@elltel.net] Sent: Thursday, May 10, 2001 11:27 AM To: Fusebox Subject: Porting Old Site

I'd like some advice from the FB crowd...

I'm reworking a site that was kind of built in fits and starts over the past few years. The thought at first was that I'd just change code that is affected by the new data integrity restraints in the database, but as I get into it I'm starting to think that rewriting from the ground up might be the better option.

Here's some details...the current site was NOT done with fusebox but eventually we'd like to port it that way. We're not changing any of the screens at this point -- it's all behind the scenes changes.

So, since we have a new database, and we have a prototype (the current working site), I'm thinking we'll have fewer headaches if we just build the new fused site now, instead of tweaking this one and porting it to fusebox later.

Has anyone done this kind of thing? Am I correct in thinking it won't take longer to build from the ground up -- especially since the current site can be used as a spec?

Thanks.

..jj..

- - - - - Get your free email account: you@alakazam.com Sign up at http://www.alakazam.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists


Similar Subject Line Posts (+/- two weeks of this post)
Re: Porting Old Site  10 May 2001   (76 v/ +0 r)
RE: Porting Old Site  10 May 2001   (68 v/ +0 r)
Re: Porting Old Site  10 May 2001   (55 v/ +0 r)
RE: Porting Old Site  10 May 2001 (this post)   (49 v/ +0 r)
RE: Porting Old Site  10 May 2001   (59 v/ +0 r)
Re: Porting Old Site  10 May 2001   (57 v/ +0 r)
Re: Porting Old Site  10 May 2001   (52 v/ +0 r)
Porting Old Site  10 May 2001   (60 v/ +0 r)
 

Send a reply to the Fusebox list!
click to send a reply! NOTE: Many lists will reject your post unless you have already registered with them. Also - don't forget the right account to send from (for those with multiple emails!)

Feedback: If this post was exceptionally helpful, please help by giving this post a positive review.

 

TallyList : copyright Ububik - 2000