Awesome work to whoever is doing the Revolution UI

Just installed the latest svn revolution (rev6371) and am so stoked with where the UI is heading. From having doubts a few months ago, things are coming along really well. Congrats

I have a few suggestions... perhaps they will be beneficial, perhaps not.

a] index.css (line 614) The opacity:0.97 in the dropdown menus should probably be removed as it causes text rendering problems in a few browsers. I don’t think it adds anything to the design, and since you can see the text behind, detracts from what you’re trying to look at.

b] Suggest having a delay on the menu dropdowns to catch rogue mousework something along the lines of Brian Cherne "hoverIntent" plugin for jquery, there must be something similar for prototype.

c] Left hand side, resources tab : would suggest the "show sorting options" button become a "Menu Button > Icon only" from http://www.extjs.com/deploy/dev/examples/button/buttons.html to save having to push the content down, and become a bit cleaner.

d] Would also suggest to speed up initial loading times for the manager, something like http://code.google.com/p/minify/ to collect and serve up the jababajillion javascript files. if you did use this, you *could* use the groups config, just altering the config everytime you add or remove a file... config is something like :



And then in the head, you would only import the group... pathto/min/g=css or for the javascript pathto/min/g=js .. they come down minified, and gzipped if your browser can accept.

Grin, i’m not going to say anything about the multitude of font sizes through the manager, I’m sure you chaps are working on those. Again, thanks for the hard yards you’re putting in, and it’s looking super tasty.

Quote from: humptygrumpty at Feb 16, 2010, 05:52 PM

Just installed the latest svn revolution (rev6371) and am so stoked with where the UI is heading. From having doubts a few months ago, things are coming along really well. Congrats

Thanks! We’re definitely open to and working on improvements.

a] index.css (line 614) The opacity:0.97 in the dropdown menus should probably be removed as it causes text rendering problems in a few browsers. I don’t think it adds anything to the design, and since you can see the text behind, detracts from what you’re trying to look at.

Good suggestion. Can you post that in JIRA? http://bugs.modxcms.com

c] Left hand side, resources tab : would suggest the "show sorting options" button become a "Menu Button > Icon only" from http://www.extjs.com/deploy/dev/examples/button/buttons.html to save having to push the content down, and become a bit cleaner.

Great suggestion; this probably wont make it out for rc1, but if you file it in JIRA we might be able to sneak it into rc2.

d] Would also suggest to speed up initial loading times for the manager, something like http://code.google.com/p/minify/ to collect and serve up the jababajillion javascript files. if you did use this, you *could* use the groups config, just altering the config everytime you add or remove a file... config is something like :

Minimization is already done; however, concatenation is proving difficult because of the specific order we need to concat the files in. We’ll definitely be researching this in the RC stages, and would welcome code and/or suggestions on how. I hesitate from using an outside service, because we would want Revo to work without an Internet connection ideally (localhost server).

Grin, i’m not going to say anything about the multitude of font sizes through the manager, I’m sure you chaps are working on those. Again, thanks for the hard yards you’re putting in, and it’s looking super tasty.

We definitely need help and will be working on cleaning up the CSS prior to GA. Thanks for your input!

Quote from: splittingred at Feb 16, 2010, 07:01 PM

Minimization is already done; however, concatenation is proving difficult because of the specific order we need to concat the files in. We’ll definitely be researching this in the RC stages, and would welcome code and/or suggestions on how. I hesitate from using an outside service, because we would want Revo to work without an Internet connection ideally (localhost server).

Sorry, grin! I should have said more - It’s just a very small standalone ’app’ written in php, ported from the javascript jsmin. I’m sure they would be open to letting you distribute them in the build of MODx, I guess much the same way as you use libraries from extjs. The concatenation is defined in the config file as an array, and definately seems to be keeping the ordering correctly, at least for some of the sites we’ve been working on. The compressed files are cached in a folder as both gzip and normal, which we found to be a plus. I was just thinking that it might save you chaps writing your own.

Having said that, if you do need to write your own, since they’re all minified it probably wouldn’t be that much work I think it will help with first impressions in the new modx manager, that’s for sure.

And I will file the others in Jira. Regarding the CSS, extjs makes a bit of a mess, haha, you can be nested twenty levels in and have 19 overwritten declarations, and finding the right one can be a bit difficult, with four classes on that very div... eep.

Quote from: humptygrumpty at Feb 16, 2010, 07:58 PM

Sorry, grin! I should have said more - It’s just a very small standalone ’app’ written in php, ported from the javascript jsmin. I’m sure they would be open to letting you distribute them in the build of MODx, I guess much the same way as you use libraries from extjs. The concatenation is defined in the config file as an array, and definately seems to be keeping the ordering correctly, at least for some of the sites we’ve been working on. The compressed files are cached in a folder as both gzip and normal, which we found to be a plus. I was just thinking that it might save you chaps writing your own.

Great! We’ll definitely look into it.

I think it will help with first impressions in the new modx manager, that’s for sure.

100% agree.

And I will file the others in Jira. Regarding the CSS, extjs makes a bit of a mess, haha, you can be nested twenty levels in and have 19 overwritten declarations, and finding the right one can be a bit difficult, with four classes on that very div... eep.

Tell me about it.

ExtJS is a trade-off, that’s for sure. We just decided to go with it because of the immense power it provides from a UI standpoint. Try drag/dropping a Snippet into the content pane or using Package Management and you’ll see what I mean.

That said, we can definitely be doing more optimizations. Thanks for your thoughts and help.