Management screen in 2.3.0

I guess this is as good a place as any to post:

https://github.com/pdincubus/MODX-Revolution-Responsive-Manager-Theme

I tried out a couple of GitHub builds of the upcoming 2.3 release and everything on that repo is ideas and thoughts about it, what I like, what I think can be improved and some actual mock ups of things to show how they might work.

I'd love to hear everyone's constructive feedback!

@pdincubus,

Your mockups are brilliant looking. The challenge is how easily it could be executed with the requisite ExtJS3.x (which is responsible for the tag soup (inline injection). As it cannot be removed until MODX 3 in order to maintain backward compatibility. I am not saying it can't be done but it would require a crazy amount of effort from a whole lot of folks.

I am excited by your proposed changes and would love to see it happen, personally. Thanks so much for this effort.

Quote from: smashingred at Nov 12, 2013, 08:46 AM

@pdincubus,

Your mockups are brilliant looking. The challenge is how easily it could be executed with the requisite ExtJS3.x (which is responsible for the tag soup (inline injection). As it cannot be removed until MODX 3 in order to maintain backward compatibility. I am not saying it can't be done but it would require a crazy amount of effort from a whole lot of folks.

I am excited by your proposed changes and would love to see it happen, personally. Thanks so much for this effort.

Thanks for the feedback

Of course I'm aware a straight jQuery/html/css Manager is but a pipe dream with current restrictions. I'm curious what the style/ideas are for MODX 3.x - how far down the line is it, when will it be around?

I know the ExtJS stuff isn't going away soon - which is a shame - a lot of the ideas on that mock up are trying to pull together ideas for consistency and layout. I guess a lot of that could be implemented in the current setup? I'd love to help if I could!

MODX 3 is at this time a set of concepts and ideals. We have no fixed roadmap.

Much of the layout and alignment changes and obviously the more consistent color and display elements you propose are more than doable. Getting rid of tag soup may not be so doable as it's a direct result of the way ExtJS works in the 3.x.

I am personally uncertain of the possibility of some of the responsive changes and therefore can't comment but would love to see progress in that direction.

Lets see how far we could take this.

Quote from: smashingred at Nov 12, 2013, 09:06 AM

MODX 3 is at this time a set of concepts and ideals. We have no fixed roadmap.

Much of the layout and alignment changes and obviously the more consistent color and display elements you propose are more than doable. Getting rid of tag soup may not be so doable as it's a direct result of the way ExtJS works in the 3.x.

I am personally uncertain of the possibility of some of the responsive changes and therefore can't comment but would love to see progress in that direction.

Lets see how far we could take this.

Will 3.x be still using ExtJS, albeit a newer (hopefully faster and shinier) version? Or is this something else open to debate across the board?

have to say, I was very pleased with the 'awesome bar' in the dev build. That will save me and lots of CMS users a lot of headaches... we're not always all organised!

Quote from: pdincubus at Nov 12, 2013, 09:13 AM

Will 3.x be still using ExtJS, albeit a newer (hopefully faster and shinier) version? Or is this something else open to debate across the board?

Debate away. ExtJS being under the hood of 3.0 is in the ultra-extreme, probably-not-going-to-happen, ever, category. Speed, lightness and the ability to be able to build custom components without having to learn some other layer beyond the MODX API, would be ideal.

Definitely not ExtJS.

AmpleSDK seems like an interesting project & possible alternative to ExtJS:

http://www.amplesdk.com/

Everyone probably has their favourite framework/tool, but I don't think "alternative to ExtJS" is what we should be looking for as that keeps the (IMO) troubled mindset that one tool should do it all and that the DOM is not important. I do have some new thoughts on the subject myself that I'll blog about in the next week hopefully that to me looks like the perfect balance between developer, dom and user-friendly..

Please no ExtJS.

It's a massive barrier to entry for developers and they jump ship fast as it's just another proprietary format to learn. Use the DOM, and maybe Backbone/Angular/raw etc when needed.