Bringing Evo back to life again

2,314 Posts

anonymized-26931 Reply #21, 12 years, 1 month ago

"How to revert MODx Evo to operation in PHP 5.4" http://setpro.pl/software/modx-evo-and-php-5.4

2,314 Posts

anonymized-26931 Reply #22, 12 years, 1 month ago

Then I'll have a better idea of what neat features I'd like to backport into Evo. Like property sets.

as far as i can remember, AHHP http://forums.modx.com/u/AHHP had an addon with that kind of functionality (at least it was compared to property sets in the thread which I'm not able to find anymore)

☆ A M B ☆
24,524 Posts

sottwell Reply #23, 12 years, 1 month ago

To be honest, I'm perfectly happy with an external config file and only the one property in the snippet call. But having an obvious way to edit this in the Manager makes life easier for the user, I suppose. I'd probably do something like a module to allow creating/editing an external config file.

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

☆ A M B ☆
24,524 Posts

sottwell Reply #24, 12 years, 1 month ago

It applies to those portions of MODx Evo code where methods are called statically (as a class members, without instantiating, i.e. classname::methodname(...)) — in such a case MODx Evo site throws „PHP Parse error”.

I knew I wasn't all that fond of OOP. Why have such a thing when you can simply include a function library file that doesn't need all the overhead of class meta data?

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

222 Posts

Stefanie Reply #25, 12 years, 1 month ago

Quote from: sottwell at Mar 05, 2012, 06:01 PM

I knew I wasn't all that fond of OOP. Why have such a thing when you can simply include a function library file that doesn't need all the overhead of class meta data?

in the end, object orientation is much easier and much smarter. Maybe it is because I like my "old" Smalltalk world, where everything is an object

I was thinking about getting rid of the config.inc.php and switch to use a XML file for the configuration. The XML classes of Zend Framework does this very ease. I never liked to include code by including files, there is no real chance to reuse such a code. If it sticks in a class, it is very easy to access and extend it.

Gone away and found a better place to stay

793 Posts

ottogal Reply #26, 12 years, 1 month ago

I am very pleased about this thread - seeing that there are people who want to take efforts for an improvement of the weaknesses of Evo while keeping it slim and user friendly.

For a long time I have been hesitating to try out Revo and just started several months ago. Some nuisance with the UI obviously got better with the Release 2.2.0-pl2, but there remained a lot.
(F.i. the unnecessary collapsing and unfolding of the resources tree is driving me nuts. Or, the Package Management hardly ever works.)
Admitting not to be very familiar with JS, my impression is that all these annoyances are due to the use of ExtJS.

Developing the core of Revo, the team has really done a great work. But the choice of ExtJS obviously was the most unlucky moment in the history of this project.

My dream is a MODX with the core of Revo and a newly made UI for the manager, without the use of ExtJS.

But the ideas discussed here for Evo are a silver stripe at the horizon... (let's say, at a different compass point). Thank you, Stefanie, for your initiative.

65 Posts

randall Reply #27, 12 years, 1 month ago

I was thinking about getting rid of the config.inc.php and switch to use a XML file for the configuration. The XML classes of Zend Framework does this very ease. I never liked to include code by including files, there is no real chance to reuse such a code. If it sticks in a class, it is very easy to access and extend it.

I'm sure what you say is correct, however doesn't that take away from the appeal of Evo? You don't need to be proficient in programming to able to make changes in Evo with a fair deal of confidence.

There is an excellent article at http://www.webdesignerdepot.com/2009/01/how-to-choose-the-right-cms/ which says it is a mistake to choose a geek friendly CMS. I'm in total agreement with that, and its importance is lost on programmers sometimes. That's not to say I'm against changes but it is important to remember the end user; many of whom are more interested in new Add-ons. [ed. note: randall last edited this post 12 years, 1 month ago.]

222 Posts

Stefanie Reply #28, 12 years, 1 month ago

Do you really think, that normal users can work with the current configuration file?

I want to keep it easy and even make it easier, than it is right now. XML is human readable and it is easy, to implement a human readable interface. This means, you as an end user get the possibility to read and change the content from the backend of Evo.
As said before, there is a need to change some behaviour in Evo to get it ready for PHP 5.4. If this is not the time to do it, when?

PS.: I forgot to mention, also geeky programmers need be satisfied

[ed. note: Stefanie last edited this post 12 years, 1 month ago.]

Gone away and found a better place to stay

5,888 Posts

Bruno17 Reply #29, 12 years, 1 month ago

I was thinking about getting rid of the config.inc.php and switch to use a XML

The advantage of php-config-files is, they can be dynamic. XMLs not.

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

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

222 Posts

Stefanie Reply #30, 12 years, 1 month ago

Quote from: Bruno17 at Mar 06, 2012, 06:22 AM

The advantage of php-config-files is, they can be dynamic. XMLs not.

Dynamic in what? Injecting code?

With any XML tool, even a something like the crude notepad on Windows you are able to change the content. With a good XML library you handle XML as it where records on a database, adding columns, adding records, changing content.

Gone away and found a better place to stay