|Re: [NEON] Overriding org.eclipse.scout.rt.ui.html [message #1755287 is a reply to message #1755247]
||Thu, 02 March 2017 07:44
| Urs Beeli
Registered: October 2012
Location: Bern, Switzerland
I'll try to outline our approach, if you need more details somewhere, don't hesitate to ask:|
- get hold of the org.eclipse.scout.rt.ui.html-<version>.jar file and unpack it somewhere as a reference to the "original" setup
- set your own ui-theme using the following line in your config.properties file:
scout.ui.theme=<your theme name>
- find the css or js file you want to customize
- in your own ui.html project recreate the structure the corresponding original file can be found at under src/main/java, create a file that has the same name as the original, extended by "-<your theme name>"
- in your own file, include the original file, then modify whatever it is you want to modify
For example, we wanted to reduce the white space between table lines and our theme name is "cisi", so we have
@import (less) "scout/table/Table.css";
I hope this helps you get started.
|Re: [NEON] Overriding org.eclipse.scout.rt.ui.html [message #1755298 is a reply to message #1755287]
||Thu, 02 March 2017 08:46
| Benjamin Schulte
Registered: December 2016
Thank you. |
Changing CSS example is included in the Scout Contacts demo app.
What I really miss is a short documentation of how to modify the "real client" (browser) behaviour besides of the CSS style. There is a BeanField class... with no documentation. I suspect it is for modeling own widgets, but further investigation is needed because no documentation is given. If the BeanField is not for that purpose, then I would really appreciate an example of how to make own widgets or changing/extending the existing ones.
I think that topic is important for other users, too. Some days ago someone ask how to get a close button on the form title tabs. That is a really good question and I have no idea how to achieve that. I am even not sure if it is possible at all.
Sure, you can use just a normal button to close the form. That is totally okay for me. I even see that it has advantages to use a normal button when using the frontend from a mobile device. But unfortunately, not always the users and bosses can be convinced by pragmatic solutions. Sometimes the boss wants a close button on the tab, and if Scout cannot do this, then the boss don't want you to use Scout.
Any help to this task would be really appreciated and again, I think also it would be interesting for other users to. Thank you.
Powered by FUDForum
. Page generated in 0.02738 seconds