Is MODx Revolution right for someone who wants to build full-on custom web apps?

I’ve been using MODx since the beginning. I’ve used it to manage a variety of basically static html sites. About six months ago I started learning PHP and now I would like to start building web applications. I started some tutorials on CakePHP and so far, so good. It makes sense.

Now I see that MODx Revolution is out and people are talking about it as a "PHP framework." In the Revolution Docs, I found this quote "It’s not a PHP Application Framework like CodeIgnitor or Symfony, nor does it purport to be one."

Searching through the forums, I’ve seen many people ask how it’s different. I’ve read the answers, but I don’t understand 100%.

How is MODx Revolution different? Why would one use MODx Revolution instead of Cake or CodeIgnitor for custom web applications? For "simpler sites" I see the benefits in using MODx, but how about for full-on custom web apps? Would MODx Revolution limit the possibilities of what could be done? Would it be a good idea to use MODx Revolution to build web apps like Freshbooks, Basecamp, or any other web service?

I would just like to understand before I dive into MODx Revolution.

How is MODx Revolution different than CakePHP and other PHP frameworks? Are there any limitations? Would MODx Revolution be a good starting point for building full-on web apps?

Cheers!

Sammy

Quote from: snowflip at Nov 05, 2009, 08:30 AM

How is MODx Revolution different? Why would one use MODx Revolution instead of Cake or CodeIgnitor for custom web applications? For "simpler sites" I see the benefits in using MODx, but how about for full-on custom web apps? Would MODx Revolution limit the possibilities of what could be done? Would it be a good idea to use MODx Revolution to build web apps like Freshbooks, Basecamp, or any other web service?

First off, it’s important to note that primarily at this time, Revolution is not a PHP Application Framework, as much as a Content Management Framework. There’s a difference. PHP AFs come with all kinds of tools to get you programming immediately, but offer no end-user support or content management tools. They expect you to create them. However, they offer easier integration with SVN, scaffolding, and such.

Revolution, on the other hand, is meant for building websites and web apps that are used in tandem with a website. For example, I’ve built (or am building) the following in Revolution:

• A dynamic online course system, complete with chapters/modules/quizzes/exams, online signup, payment processing, reporting, manager previews, etc.
• A threaded, complete forum solution that can rival SMF
• SSO Integration with the Atlassian stack
• modxcms.com/extras/ - the online repository, that hooks directly into MODx Revolution
• The modxcms.com Showcase
• Integration into Amazon Web Services for a Gallery module
• Integration into Zendesk via REST, providing a full externalized, web-based UI on our own servers
• And more...

Basically, you name it, I could build it in Revolution. Why? Because Revo comes with the following:

• A complete, robust database ORM in xPDO, that can rival most other ORMs in ease of use and scalability
• A powerful and proper OOP-driven model layer, built in MVC/C - the second C being "connectors", which act as secure gateways to the Model layer, and allow for easy AJAX processing
• Multiple dynamic templating systems, either through the built-in Chunk-driven system for MODx, or through the service layer that can utilize Smarty or any templating class of choice
• i18n integration with Lexicons
• Context-driven support, meaning that multiple subdomains, web services, and other domain layers are easy on only one install
• Tighter security via movable core/ and connectors/ directories
• Easy dev-staging-production development process for 3rd Party Components (or your webapp) via Transport Packages, which can be versioned, rolled back, installed anywhere, etc
• Easy customization for the end-user via the MODx system of Snippets, Property Sets, custom User/Context/System Settings, and more.

And of course, many more reasons...

Are there any limitations?

It’s hard to list limitations because for most all limitations, a solution could easily be found. Maybe you could list some of what you had in mind?

Would MODx Revolution be a good starting point for building full-on web apps?

I certainly think so.

snowflip: I think you kind of read the text you quote backwards (it could probably be clearer).

The point of it was that for simple sites, Cake and CodeIgniter are more appropriate for some users because they make it easy for novices to create a site quickly. They do this by limiting your choices and constaining the site design.

MODx Revolution, OTOH, scarcely limits you at all, but doesn’t hold your hand while you create your web site. So for "full-on" web development, MODx is, by far, the better choice.

A huge thanks to both Shaun and BobRay! What you both just told me really helps.

A question for Shaun:

A dynamic online course system, complete with chapters/modules/quizzes/exams, online signup, payment processing, reporting, manager previews, etc.

Is your course system available for purchase in one way or another?

Sammy

Quote from: snowflip at Nov 05, 2009, 12:08 PM

Is your course system available for purchase in one way or another?

No, not at this time.

Is it like Moodle?

Quote from: charliez at Nov 05, 2009, 05:46 PM

Is it like Moodle?

Let’s hope with all our hearts that it is not.

Quote from: OpenGeek at Nov 08, 2009, 01:08 PM

Quote from: charliez at Nov 05, 2009, 05:46 PM

Is it like Moodle?

Let’s hope with all our hearts that it is not.

So, so true. ;-) I’ve never fallen in love with Dokeos. Shaun, Shaun, Shaun...I am just dying to see your MODx LMS. Pretty please with extra cheese? ;-)