MODX Evolution: Manager Restyle Project

Even mootools has some interesting ui elements http://ui.moolego.org/laboratory/working-demos/window/

I did not say, that this will not come, but we are going to end nowhere, when we do not go step by step.

It is not only about the tree, where we've seen some possible solutions.

There is also the iFrame hell for modules, that do not resize in all browsers. And without iFrames, we run into modules, that won't work any more without changing their code.

Please, no mootools again, I've them at my job and I'm glad, that there is a developer, who has to work on them, but I fear, I end to work with that code. OK, I will get money for that pain, but...

Btw, there is a beta of http://modx.com/extras/package/elrte for Revo. Haven't you, Susan, said, you want it? Though it should be easier, to get it for Evo with the knowledge of the Revo implemantion

I agree with Stefanie here, a drastic change could break modules and many other things. It's better to do it step by step.

Heh. I was just commenting on the mootools library after running across that page with those pretty draggable "windows". I definitely much prefer working with JQuery.

Indeed, I do wish to see elRTE and elFinder options for Evo. While I'm OK at showing/hiding form segments, configuring galleries, rotators and sliders, and even setting up eForm or WebLoginPE as an AJAX processor to provide popup contact forms and login forms, I don't know if I am up to this sort of thing. I suppose I won't know unless I try.

understood microcipcip re backend ajax being more complex than frontend.

The only reason why backend AJAX is more complex is that the "action" files are mixed HTML with inline PHP and big sections of javascript code in the page. If they were all proper PHP code that returned the desired HTML (forms or lists or whatever), then AJAX or direct loading would make no difference, just as you can use eForm to make AJAX forms as easily as using the snippet directly on a page.

The javascript for the action pages should all be properly done with unobtrusive javascript loaded as external js files; no inline javascript and no blocks of javascript in the pages. Each action page can have its own external .js file to contain all the javascript functions necessary for that page.

It's all in the database; retrieving the desired data and generating the lists and forms, and again saving form data to the database. The javascript is just to make fancier interfaces.

Thanks for explaining that so eloquently Sottwell, I can see what you guys are talking about now.
Keep up the great work everyone.

OK, Susan. I understood too.

What browsers must be supported by MODX Evo (Back End)? I have tested the Theme with the latest version of Firefox, Chrome, Opera, Safari and Internet Explorer. it seems to be working fine in all of them, except for some strange bugs on Internet Explorer 9.0.

On Internet Explorer 8.0 I can see the manager fine except in some places where I have heavily used CSS3 (now is almost ok).

On Internet Explorer 7.0 the manager is messed up. [ed. note: microcipcip last edited this post 14 years, 4 months ago.]

What do you think is the best way to integrate grids/tables? I would like to make the tables in the Manager Theme with this excellent jQuery script (it can be integrated with Themeroller for jQuery UI): http://datatables.net/