| [Neon] Theming [message #1717453] |
Mon, 14 December 2015 06:56  |
 Rene Eigenheer
Messages: 109
Registered: July 2009 |
Senior Member |
|
|
I've started to do some examples with the Neon Theming.
Trying to rebuild an existing Web application as close as possible with scout, I tried to hide some Scout standard areas. Most of them I could make disappear with CSS (display: none or visibility: hidden).
As this has only an impact on the presentation I would like to know, whether there is a Scout possibility to generally prevent the generation of the corresponding HTML code instead of just hiding the area.
The areas I'm talking about are:
- Desktop Navigation
- View Buttons
- Main Menubar - this one I couldn't make disappear as probably the automatically generated NavigationUp- and NavigationDownButton are overwriting my "display: none" directive.
Is there a possibility in the Scout Model to prevent this areas?
or
Is there a possibility to extend / overwrite the js code for this areas for a specific them as it is possible with the css? i.e. Desktop-mytheme.js
Add a Topic Description to ease the search
[Updated on: Mon, 14 December 2015 09:25] by Moderator Report message to a moderator |
|
|
|
|
|
| Re: [Neon] Theming [message #1717517 is a reply to message #1717493] |
Mon, 14 December 2015 14:24  |
|
Currently the layout of the default style is rather static. We should definitively improve it in a way, that the view and tool buttons may be optional so that these specific areas may collapse. I hope we can do some improvements in this area at the beginning of next year, but I cannot promise anything.
If you want to add a custom style you would have to extend scout.Desktop and make sure your desktop is used whenever a new desktop gets created, which would require an entry in scout.objectFactories.
|
|
|
| Re: [Neon] Theming [message #1730689 is a reply to message #1717517] |
Wed, 27 April 2016 16:28 |
|
You will be pleased to hear that we added some possibilities to modify the desktop layout.
Since M6
New property on the outline:
- navigateButtonsVisible
Since M7
New properties on the desktop:
- navigationVisible
- navigationHandleVisible
- headerVisible
- benchVisible
DesktopStyle is now called DisplayStyle and more or less controls the above properties. With displayStyle=BENCH only the bench is visible, with displayStyle=COMPACT (which is used for mobile devices) either the navigation or bench and header are visible.
Since RC1
Optional View Buttons
The view buttons on the top left are now optional, if you don't provide any, the navigation body will move up
Flexible Bench
The bench now provides 9 areas where forms may be positioned using the existing form.displayViewId
|
|
|
Powered by
FUDForum. Page generated in 0.03710 seconds
] 
Search
Help
Register
Login
Home
