The modx backend. A living nightmare?

Also for reference Evo 1.0 will have a different theme that’s not been used/shipped previously. I think the Carbon add on is a great starting point to consider on this point.

@pepebe, looking good!

That tabs keeps in with the 2.0.6 Revolution release. Or if you put all the options in one scroll page could you not add hide/close Prototype | MooTools, header sections with a hide all [ ] or show all [ ] at the top of the page.. It’ll be nice to see some organisation to backend presentation.

- just remembered in Revolutions System settings it’s using a hide/show option.

I have cut’ n’ pasted my additions to both stylesheets and apart from some minor issues I don’t see a problem. Consider it done.

How about condensing all color, border and background-related style information in one block? This would blow up the stylesheet a bit, but would have the benefit of easier adjusting the basic layout properties.

Quote from: pepebe at Feb 24, 2009, 06:10 AM

I have cut’ n’ pasted my additions to both stylesheets and apart from some minor issues I don’t see a problem. Consider it done.

How about condensing all color, border and background-related style information in one block? This would blow up the stylesheet a bit, but would have the benefit of easier adjusting the basic layout properties.

This was the first thing I was thinking about, but as I’m "not the brightest bulb on the tree" (I read that idiom somewhere in this forum and fell in love with it. There are just so many things they never teach you at school...) regarding javascript, I stuck to the solutions already present.

Generally, what makes me a bit worried is the flood of java script frameworks arround MODx. You’ll find mootools, jquery and other stuff all over the place. I don’t have a good feeling about this. Question: What’s considered to be the official default framework for MODx in this build? Let’s stich to that one.

For front end sites, there is no standard. For the manager in Evo, that’s up for debate. Needs to probably be either the latest Mootools, or jQuery might be nice as well.

I vote for jQuery simply because I understand it, but it plays well with others so it is no biggy.

Great progress on this, I was out for a few days and look at all that has been done. Great work

I would vote for Jquery too since it more easier than mootols for the designers.

But mootools is not a bad choice either. Just more difficult as non "native" javascript develloper.

Another vote for jQuery, it’s perfect for quickly accessing document objects and bending them to your will - hence the success of ManagerManager. And all the cool people are using it

Quote from: therebechips at Feb 24, 2009, 10:13 AM

Another vote for jQuery

+1 (Does that mean I’m cool? Or does it cast your previous statement into grave doubt?)

Plus another for jquery, but I’m definately not cool, never have been :’(