MODX3 first impressions

Quote from: donshakespeare at Jul 15, 2018, 06:27 AM

@mrhaw that github thread is really scary ... a major discussion about something that should not even exist - an overwhelming new resource layout.

EXCELLENT answer over there!!
[ed. note: mrhaw last edited this post 5 years, 9 months ago.]

Pic attached

Exactly! unfortunate that the Extra is not advertised all over MODX website/forum/slack.

That new user has already pointed out the massive hole we've all been staring at.
Hopefully MODX3 will cover it up by integrating that Extra into its core, or at least making the Extra more public

It was discussed a lot to have the upgrade in the core. Conclusion always was to have it not in the core. The profit is to have a more maintainable core. As it is with different other extras, it would be helpful for new users if they know about them. I see the startpage after succesfull installation as a possible place to give users a hint about them.

@donshakespeare

Exactly! unfortunate that the Extra is not advertised all over MODX website/forum/slack.

That new user has already pointed out the massive hole we've all been staring at.
Hopefully MODX3 will cover it up by integrating that Extra into its core, or at least making the Extra more public

I remember seeing some early designs of the new MODX dashboard that had an "Update MODX" widget built in. We should ask @gpsietzema why this idea was dropped.

https://modx3.org/uploads/images/updates/week-9/modx3.png

New Resource Layout

I've been testing MODX 3 as much as time permits using both the regular build available from https://modx3.org/project-statement and from the 3.x branch on github.

I'm happy and excited apart from where MODX 3 presumes you use MODX in a particular way. Such as the new resource layout I posted about here: https://github.com/modxcms/revolution/issues/13968

We love MODX because it's agnostic (it doesn't dictate how to manage content) and gives you the freedom to change what you want - this particular design update to resources goes against those founding principles.

As an example, I customise the manager so that all unnecessary clutter and fuzz is removed from content editors, so that they can focus on what they do best...generating and editing content.

So in this scenario, when looking at the 3 new side panel regions, I would only have 2 bits of data displayed ("published" and "hide from menus") out of the 9 pieces of new functionality on display, this seems like a great waste of space I can't get rid of.

I don't want to be branded as holding the project back, or not wanting a new modern manager. I'm simply providing feedback and some solutions. I'm all for the new layout if that appeals to the masses, but please give us the tools, through form customisation, to change the layout back if we need todo so. For example;

1. Allow us to move the content field out of the document summary into it's own space
2. Allow us to move publishing, template, behaviour in menu panels into tabs or different regions
3. Allow the document summary to go full width if we hide publishing, template, behaviour in menu panels into tabs

If you have an opinion about this, I encourage you to leave a comment with a solution:
https://github.com/modxcms/revolution/issues/13968 [ed. note: jonleverrier last edited this post 5 years, 9 months ago.]

Quote from: raffenberg at Jul 16, 2018, 08:12 AM

It was discussed a lot to have the upgrade in the core. Conclusion always was to have it not in the core. The profit is to have a more maintainable core. As it is with different other extras, it would be helpful for new users if they know about them. I see the startpage after succesfull installation as a possible place to give users a hint about them.

This could be done with a self-contained widget. Yes, it would have to be modified if and when MODX changes the location of the downloads or stops tagging versions at GitHub, but that's no reason to make users do a manual upgrade in 2018 (especially with a moved/renamed core). There's also no excuse for Setup asking you where the core is during an update -- there are three different config.core.php files it could check. In fact, what UpgradeMODX does now is just copy the root config.core.php file to the setup directory (with a small mod to keep setup happy).

Quote from: jonleverrier at Jul 16, 2018, 09:36 AM

...
We love MODX because it's agnostic (it doesn't dictate how to manage content) and gives you the freedom to change what you want - this particular design update to resources goes against those founding principles.

As an example, I customise the manager so that all unnecessary clutter and fuzz is removed from content editors, so that they can focus on what they do best...generating and editing content.

So in this scenario, when looking at the 3 new side panel regions, I would only have 2 bits of data displayed ("published" and "hide from menus") out of the 9 pieces of new functionality on display, this seems like a great waste of space I can't get rid of.

I don't want to be branded as holding the project back, or not wanting a new modern manager. I'm simply providing feedback and some solutions. I'm all for the new layout if that appeals to the masses, but please give us the tools, through form customisation, to change the layout back if we need todo so. For example;

1. Allow us to move the content field out of the document summary into it's own space
2. Allow us to move publishing, template, behaviour in menu panels into tabs or different regions
3. Allow the document summary to go full width if we hide publishing, template, behaviour in menu panels into tabs

If you have an opinion about this, I encourage you to leave a comment with a solution:
https://github.com/modxcms/revolution/issues/13968

I love this! Thanks for describing Creative Freedom.

Quote from: BobRay at Jul 16, 2018, 08:30 PM

This could be done with a self-contained widget. Yes, it would have to be modified if and when MODX changes the location of the downloads or stops tagging versions at GitHub, but that's no reason to make users do a manual upgrade in 2018 (especially with a moved/renamed core). There's also no excuse for Setup asking you where the core is during an update -- there are three different config.core.php files it could check. In fact, what UpgradeMODX does now is just copy the root config.core.php file to the setup directory (with a small mod to keep setup happy).

Don't get me wrong, i just repeated the conclusion from several discussions over on slack.

Sorry, I didn't mean to sound like I was blaming you.

Somehow, WordPress has managed to do it for years.

Regarding ExtJS, I think this is the long term path to get away from that. Would be nice to make that come to life soon. https://github.com/modxcms/mab-recommendations/blob/master/06-restful-api-move-from-extjs.md