Bringing Evo back to life again

☆ A M B ☆
24,524 Posts

sottwell Reply #191, 14 years, 5 months ago

Yeah, I didn't think you meant it that way either; just that we keep rolling along, and thanks for moving to the proper section of the forum.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

1,098 Posts

microcipcip Reply #192, 14 years, 5 months ago

Quote from: sottwell at Apr 05, 2012, 11:27 AM

I liked that dramatic dark one somebody had a few weeks ago.

Lol you mean this: http://www.jertix.org/assets/images/blog/modx/manager-theme-darkgrey/login.jpg ?

Jertix.org -> Web Design & Development, Motion Graphics | Follow me on Twitter | MODx Tutorials (in Italiano) | MODx Snippets (English)

☆ A M B ☆
1,231 Posts

yama Reply #193, 14 years, 5 months ago

http://www.jertix.org/assets/images/blog/modx/manager-theme-darkgrey/login.jpg
Nice!

222 Posts

Stefanie Reply #194, 14 years, 5 months ago

@sharkbyte: I apologize, but for me, that meant ghost town

But hey, this kept it moving on

Gone away and found a better place to stay

2,314 Posts

anonymized-26931 Reply #195, 14 years, 5 months ago

hehe, no worries, just wanted to give the thread a little push, so someone would notice and move it like Susan asked ...thus, not becoming a ghost town with tumbleweed (you were right with that though wink

)

222 Posts

Stefanie Reply #196, 14 years, 5 months ago

I've just finished unit tests for MySQL in the complete rewritten ezSQL classes. You'll find them on github at https://github.com/sjstoelting/ezSQL/tree/PHP5.dev

The next steps are doing unit tests for PostgreSQL, SQLite, and PDO.

What I do not have available are MS SQL Server, Oracle 8 or 9, and Sybase ASE. Is someone out here, to help me with them, by running the tests and chatting or phoning, until they work?

Gone away and found a better place to stay

MODX Staff
10,725 Posts

opengeek Reply #197, 14 years, 5 months ago

Quote from: sottwell at Mar 31, 2012, 11:04 AM

We're dealing with two different desires here. Personally, I want a light, quick CMS. The MODx development team has gone in a different direction, and I have no quarrel with that, I just have made a personal decision to continue with what has made my life a pleasure for the last 6 years or more. You like driving a bus and I like driving a sports convertible. If I ever need to develop a heavy web application that will run on its own dedicated server, Revo would most certainly be my choice. As long as I'm building relatively simple sites, it's just massive overkill.

I see no reason why there can't be room for both. Why try to kill Evo and force everybody onto the bus?

I think we have the same end-result in mind; the desires are in fact the same. We have not intentionally taken any direction away from what brought us here. Have some mistakes been made? Sure. Has Revolution made the manager experience as easy to customize as Evolution? No. Nor has the baseline performance of Revolution matched that of Evolution.

But I hope you trust we are absolutely committed to making a light, quick CMS, and to continue improving upon what we started together.

No one is trying to kill Evolution. We continue providing security patches and integrating quality PRs that make sense for the direction of the MODX brand. But splitting this community on core feature development is a pretty good way to destabilize both products. The risks of having parallel efforts reduce our focus is the reason why I believe we should unify under one platform—to maximize our adoption and awareness and to remain relevant.

United we stand, divided we fall. We have a lot of future challenges and competition from both the existing big players and new, up and coming projects. And they have been taking notes from the best and brightest in this industry.

Keeping MODX viable, flexible, light weight, and powerful via extensibility are and always have been my goals when leading core development of this project. All I'm asking is for this great community to pool it's resources together in a concerted, focused effort to protect and strengthen what already makes this project amazing.

Both Evolution and Revolution each have some great strengths and incredible weaknesses of their own. Just imagine if we could take what works best in both, remove the weaknesses, and present the best offering as an allied community...

Sincerely,

Jason Coward
Chief Architect @ MODX

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

222 Posts

Stefanie Reply #198, 14 years, 5 months ago

When I take a tour through the code of Evo and Revo, we might end up in Post as good as they match. The differences calling snippets is an other example, which will cause problems, or we need both syntaxes.

Have I missed a discussion, to move away from ExtJS?

For me, the discussion was never to split the community or create fork, it was from the beginning to work with a system, that I really do like. I wanted PostgreSQL for example for years now, but I had no time to work on this. And wanted this as a choice.

I understood, that there was - and now is - a lot of work to do, to bring up Evo, and that it might be easier to go to a new code base. The problems with cache on big sites is something, that I didn't understand on Evo, because the easiest solution is to bring the database into RAM and stop caching inside Evo. You've got a rocket with that, I did it for example with some shop pages (round about 250,000 pages answering time less than a second included price calculation for B2B).

Why not going with lightweight and running with shared hosting, and the one, that does need a server for its own?

If going to one solution, what will be the timeline, until we see something? Where to start with?

ezSQL Update: Pushed the unit tests for PostgreSQL and PDO, all of them are working.

Btw, wouldn't it be funny, to see MODX running on SQLite, which is next on the unit test list?

Gone away and found a better place to stay

5,888 Posts

Bruno17 Reply #199, 14 years, 5 months ago

Quote from: opengeek at Apr 05, 2012, 01:47 PM

United we stand, divided we fall.

+1

wouldn't it be wiser to put all efforts into one system?
Revo has such a great, genius core.
Why not create a lite-manager for those, who find the default Revo-Manager with extjs too bloated, before trying to create a complete new manager for EVO?

BTW: I'm a Revo-Lover. Would never go back to EVO for new projects.

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

222 Posts

Stefanie Reply #200, 14 years, 5 months ago

For it is Evo that fitted all the time. I tested Revo where often, but was never pleased with it, Where should I start? With missing shared parameters, or no real modules?

Here we are again, people who like Revo more then Evo for their work, and the opposite.

The biggest problem by now is, that both are diverted in so many behaviours and programming for one of them, that bringing them together might end up with users on both sides, that don't like the consequential result.

For me it is OK, that people like Revo, I've no problems with this, but please, there are also people that have problems with Revo. By now I wouldn't even think about using Revo for high load websites, because I can't tell people to work with a system, that I wouldn't work with on my own. And I respect the work, that was done for Revo, also that there was no time left to work on Evo.

I haven't seen any good reason using Revo, or coding on Revo, for me. I can't see any fun in working on something in my spare time, that I wouldn't use in the job. But I would not force someone to use Evo because it is the best system, it is only the better one for me.

Why not keeping both solutions, letting people decide, which one they like? I know, that two solutions are not to follow the line of least resistance. But it is possible.

Gone away and found a better place to stay