I honestly don't think you really mentioned anything that can't be done with FarCry. For instance, look at this article on FuseTalk integration:
http://farcry.daemon.com.au/go/objectid/2921E271-D0B7-4CD6-F9F6EB49EF72E7F5 My main point is that you should take advantage of what's out there, rather than starting from scratch. If FarCry lacks the certain interoperability characteristics you are looking for, why not first attempt to add them in rather than building an entire CMS from the ground up? -Dave >>> [EMAIL PROTECTED] 9/16/2004 10:45:37 AM >>> Hi Dave, That is a very good question -- and I hope I have a very good answer for you. For one, I haven't seen any open source CMS systems for CFMX that I'm interested in. If there are some that I've missed, please let me know. FarCry is nice, but I have a different goal for what I'm trying to build. The main reason is the "Content Management Systems" -- especially the open source ones -- are often silos of information that don't play well with others. You put your data in here, and it goes on the website -- if you want to integrate with any other applications then use a hyperlink. The goal of SmartCMS, which I hope is different than that of similar software, is to integrate very tightly with other applications whether they're CFMX or not, open source or not. And, the goal is to integrate both ways, so that each package both contributes and benefits from the relationship. For example, we have just posted a sample integration with CF_Nuke, which will eventually make all of the functions of that application embeddable into a SmartCMS content tree. Next, we will publish SmartCMS content as a module in CF_Nuke. I'm currently working on connectors for Fusebox and Mach-II, so that any application can be included into a SmartCMS website, and will still inherit all of the goodness from the CMS, like common templating, dynamic navigation, and embedding additional content. SmartCMS was originally designed to be a virtual server farm, and will support as many different website domains as you can squeeze on the hardware. In addition, it is built from the ground up to be very modular. It's easy to create new packages of functionality, and to include different feature sets on different virtual servers. Of course, without writing a book I can only scratch the surface. Re-inventing the wheel is a rightful question to ask of any new project. I hope I've answered some of your questions. If not, let's keep talking. -- Ben http://smartcms.tigris.org > this has to be asked... why re-invent the wheel? > > -Dave ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
