Improve Orchard.Layouts UX#8721
Conversation
…to improve usability
reintroduce less variable
|
Can you share some screenshots before/after to understand the changes? |
|
@sebastienros |
(cherry picked from commit ba0daf3) # Conflicts: # src/Orchard.Web/Modules/Orchard.Layouts/Scripts/LayoutEditor.min.js # src/Orchard.Web/Modules/Orchard.Layouts/Styles/LayoutEditor.css # src/Orchard.Web/Modules/Orchard.Layouts/Styles/LayoutEditor.min.css
|
@HermesSbicego-Laser I'm working on #8773 now and there were some merge conflicts between 1.10.x and dev regarding some of the client-side assets. Recompilation works fine (which I find a positive surprise considering how outdated the compilation pipeline is) with Node v7 in the Task Runner Explorer. I ran it first just on 1.10.x to validate the output and got the following results:
Layouts still works great, but the layout editor toolbox became very restricted in terms of its height due to this specific line: Can you please check what happens if you do a full recompilation of client-side assets with the |
|
@BenedekFarkas Could you please clarify what do you need us to check? What branch do you need us to try and rebuild the assets on? |
|
I've moved on from this for a while, so I recompiled everything and resolved the issues already, but the issue was present on this PR's branch, as well as 1.10.x and dev. |






Improve UX of the LayoutPart Editor