EVO -> REVO -> CLOUD ...what is the future?

I've been reading carefully, on MODx Cloud,
and I think that really will surely be an optimal co-worker for future projects.

Especially in my case I work with Cloud for embedded industrial and now I have to do a lot of dirty work on the server to make things right.

So far my only co-workers have been MODx and ZK.

And in every version of Revo, MODx environment has proven to live up to their role and in many cases completely replacing java-based projects.

But I wonder:
Revo will continue, an independent path,
or will be replaced shortly by MODx Cloud?


In a few months I have to start a new project of a network of PaaS,
and I wonder:
Is the case to await the arrival of the new "MODx Cloud"?


I can design a new SaaS in MODx Revo?


My product will be obsolete in a few months?


Thanks.

MODX Cloud is hosting infrastructure (PaaS) built around MODX Revolution, adding some unique value-propositions to the content management framework as you know it in the process. But it IS definitely MODX Revolution which will absolutely continue as the flagship MODX product.

You do not need to wait, and your product will not be obsolete if built on MODX Revolution.

Thank you very much for your reply.

I will keep your advice.

Regards.

Quote from: opengeek at Jun 11, 2012, 01:18 PM

it IS definitely MODX Revolution which will absolutely continue as the flagship MODX product.

Not according to Ryan Thrash - his blog post from May 25, 2012 states:

In 2013 we will release MODX 3.0. Note the distinct lack of any word between “MODX” and the version number. The MODX 3 release will also mark the official deprecation of both Evo and Revo, bringing the confusion as to what's the official recommendation to a close.

Which in my eyes means that EVO & REVO are being replaced with MODX 3 [ed. note: iusemodx last edited this post 14 years, 4 months ago.]

Quote from: iusemodx at Jun 11, 2012, 01:54 PM

Quote from: opengeek at Jun 11, 2012, 01:18 PM

it IS definitely MODX Revolution which will absolutely continue as the flagship MODX product.

Not according to Ryan Thrash - his blog post from May 25, 2012 states:

In 2013 we will release MODX 3.0. Note the distinct lack of any word between “MODX” and the version number. The MODX 3 release will also mark the official deprecation of both Evo and Revo, bringing the confusion as to what's the official recommendation to a close.

Which in my eyes means that EVO & REVO are being replaced with MODX 3

Yes. We found this confusing. The blog post talks about clarity but it only confused us. We have effectively frozen development of a number of things if there is another MODX on the way. We are going to release a number of extensions that are complete now (just have to schedule time for documentation) but until we know otherwise, we're not going to continue work on new ones if ExtJS is no longer valid or being replaced (by version 4 which was, I believe, on the old roadmap but we'd have to be sure) or the permissions system is getting a complete overhaul.

We sort of assumed it was just a a marketing name and MODX 3 would be Revo with an updated ExtJS and welcome permissions changes but the blog post lacks clarity in that regard and in the comments it's clear that we're not going to know the answers until a later date.

The original poster asked if Cloud was a replacement for Evo/Revo. As Jason clarified, it's not. MODX Cloud is a full development and site maintenance platform of which Revo is a small part.

MODX 3 will follow on the development work pioneered in Revolution and incorporate the best attributes of both Evo and Revo—mostly a shift toward a single software platform. The best part of Revo is the core architecture and ability to do things that simply are not feasible with Evo, and Evo has raw speed and customizability of the Manager, and front end performance for smaller sites. (Of course there's more on both fronts, but that's the TL; DR.)

The reason to be clear about the deprecation of both is that focusing around a single codebase is the smart thing to do, mostly borrowing from Revo but addressing some performance and usability issues. There may be some breaking changes—this is no different than if we had called it MODX Revolution 3.0 by the way—but we are loathe to obsolete everything we've done for the last few years or MODX Cloud which enters private beta soon with Revo as a small but critical piece. [ed. note: rethrash last edited this post 14 years, 4 months ago.]

Quote from: rx2 at Jun 11, 2012, 03:29 PM

We have effectively frozen development of a number of things if there is another MODX on the way. We are going to release a number of extensions that are complete now (just have to schedule time for documentation) but until we know otherwise, we're not going to continue work on new ones if ExtJS is no longer valid or being replaced (by version 4 which was, I believe, on the old roadmap but we'd have to be sure) or the permissions system is getting a complete overhaul.

We sort of assumed it was just a a marketing name and MODX 3 would be Revo with an updated ExtJS and welcome permissions changes but the blog post lacks clarity in that regard and in the comments it's clear that we're not going to know the answers until a later date.

I can say it's highly unlikely that MODX 3 will use Ext 3.x as Revo does today. Ext 4.x has some great enhancements, but a lot of people would love to see jQuery too.

If you have some great Add-ons almost ready to go, then by all means release them! If there's a way we can make MODX 3 fully API compatible with Revo, then we will (not making any promises on that topic—that said you shouldn't have to rewrite them from scratch). If we have to make changes to how any custom manager pages are built, then we'll put some examples up of how to transition them as part of the new release. With the end of 2013 being ~18 months off, we've got time and will add staff to do so as needed!

We're big fans of jQuery as well and it may have what it didn't back in the early days of Revo's birth such as site trees and the like. We've done some work with the Yii framework and it uses jQuery for all of it's interface elements.

The work we'd pause on is interface and permission heavy. We'll work on getting out what we have asap. I'll probably have some time, at last this week. Looking forward to giving back to the community,

Regarding jQuery/ExtJs question...
Few months ago I was strongly for jQuery. Then, I took some time and dived into ExtJs and bottom line is: ExtJs beats jQuery (for this kind of purpose) on any given day. It's no contents. I almost feel that I have to apologize for pushing jQuery, especially since I didn't (at that time) give ExtJs a decent amount of learning time.
I would really encourage everyone, take some time, learn ExtJs (within few weeks you will know enough to build CMPs) - you will never push for JQuery - I promise.

Ryan,
I really feel that future MODX path, especially regarding technology used must be clear. I know that it is hard to do that, but if we don't have "long time plans" clear it is hard to put most/all your guns into MODX. Learning takes time, and although fun and best part of this job, it is kinda expensive.
So please, if anyhow possible, be clear about tech that will be used in future few years (or even more). if my opinion means anything, I think that this kind of thing is essential for MODX success.

Regards,
Antonio

We will most likely be using ExtJS as the future for 3.0. The MODX 3 API will likely be a bit more streamlined, making CMP development easier, but the concepts will remain similar to MODX Revolution (think of it like Revo 2). I don't currently see a benefit of switching off of ExtJS, as we have invested a lot of time and effort into education and extension of the framework, and switching would mean a complete restart of that - not to mention having to completely rewrite all the Extras out there.

As a developer of MODX CMPs, you can safely assume we'll stay with ExtJS - the roadmap has stated we'd try and get ExtJS4 (or 5 if it's out by then) into MODX3; Ext3 is a bit outdated, but we can't upgrade to Ext4 without breaking changes, so we'll likely wait till MODX3 to do so.

Again, not a certainty, because we don't want to lock ourselves into any technology in the long term, but rather make strategic decisions that benefit the community, the product and the development of tools around the product. But I would say Ext is the direction we have been heading, and most likely will be heading in the future. That said - CMP development will be easier (even with parts of it starting so in MODX 2.3 due to refactoring there).