RE: [CFCDev] component extends object with relative path

[Raymond Camden]

I guess this comes down to one difference of opinion. To me, it sounds like you are saying you want to take a complex application and make install be a simple unzip and run. Is this a fair expectation for a complex application? Is it common for folks on shared ISP accounts (w/o cfadmin access) to run complex applications like this? Are the examples of other complex apps (web, or non web) that this applies to? It seems like in most cases, complex pieces of software need ot have _some_ kind of setup. Sure, when I download a UDF from cflib, I expect it to just run. I don't think it would be fair to expect the same from... oh shoot, I forget the name, but the guys who make the good Forums products that Macromedia uses. That's a pretty sophisticated application. If the _only_ thing I had to do was set up one mapping and one DSN, I'd actually be surprised.   We can probably argue this back and forth all day. I certainly agree that I'd _love_ to be able to make a mapping on the fly. I just don't seem to see why requiring a cf admin trip for a complex app is even an issue. ======================================================================= Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc Member of Team Macromedia Email    : [EMAIL PROTECTED] Blog     : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Davis Sent: Wednesday, May 26, 2004 1:12 PM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] component extends object with relative path It’s not that the code to make the DSNs is “official” – it’s just the process for doing so has been sorted out and settled on.  That hasn’t happened yet for CFCs.  Allaire/Macromedia also had white papers and best practices information for hosting providers – they don’t seem to do that anymore.   Simple apps can definitely work (although you must meet some pretty severe, I think, limitations) – it’s when you’re considering larger apps for sale that things definitely get murkier.   A simple example: I’ve create (as I think many people have) a “root” component – a component that is extended by all other components in my systems.  I want to package each system separately but still have access to that root component.  I also have several utility components that I want to use across systems.  There are also database-specific DAO components to find.  My directory might look like this (plus sign indicate directory names):