Any application where you have data (or content, as the CMS folks call it) that you want to create, edit, delete, have version control over, control access to, and search against is a candidate for the platform, because it allows you to handle all of those typical tasks with minimal programming. Say you want to build an application that manages personal health records, since we've been on that topic. This would be a typical worflow:
1. Add users and groups. 2. Add any custom system roles (optional). 3. Assign system roles by user and group as needed. 4. Add content types as needed, e.g. prescriptions, medical procedures, and checkups (a PHR might contain these other things) 5. Assign create, edit, delete, own permissions (plus any custom permissions you want) to the content types. e.g. allow only doctors and nurses to add, edit, and delete prescription information on a personal health record. At that point, you have lots of options. 6. Build any custom workflows you need, e.g. patients might be able to allow/deny access by others to their doctors appointments but not their prescription information. 7. Add data manamagent screens, e.g. a set of screens to manage prescriptions for a patient. At that point, you are possibly done and ready to deploy a live application. You could also: 8. Customize the search by extending the basic SearchManager CFC, changing the Solr XML schema, and implementing any custom search and result display code. 9. Create any custom resources (CFC methods, UI components, or other arbitrary resource types that you want to secure, and assign permissions to them. Steps 1-5 and 9 are done without any programming, and there is a robust API used to access all of the information in steps 1-5 that you use to complete steps 6-8. We are abstracting away more and more steps into tasks anyone can be trained to manage, freeing developers to focus on higher level, higher value-added tasks. Flex integration is coming - working with Java objects between CF and Flex turns out to be a little tricky, we're working on that. Mark Mandel has a BlazeDS adapter for CF called Conduit that might be the answer. There are only a couple of other things left to finish for the feature complete baseline, and there are many directions the platform can go from here. I have more details, email me offlist if you want to know more. Rob On Wed, Feb 25, 2009 at 8:36 PM, Michael Grant <[email protected]> wrote: > > Do you have some examples of when and why it would come in handy or be > faster than what cf8 does already? > It sounds interesting. > > On Wed, Feb 25, 2009 at 11:06 PM, Robert Munn <[email protected]> wrote: > > > > > I am getting ready to release an open source application platform built > on > > CF 8 using Model-Glue and Coldspring that handles: > > > > - arbitrary complex data types, including nested data types > > - role-based security and identity management > > - enterprise search > > - integration with Flex and AJAX > > - security on data types and data objects > > - data object versioning > > - easy implementation of extensions to the core without modification to > the > > core > > > > > > I don't have a name for it yet. I started with RoseCMS (actually Rose > > Canyon, which is the canyon behind my house), but this is not a CMS, it's > > an > > application platform. RoseCMS is a small open-source CMS that is an > > implementation of the platform, but I see the platform as something > > separate. > > > > Thoughts? > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:289829 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5
