|
| 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
Messages: 573
Registered: October 2012
Location: Bern, Switzerland |
Senior Member |
|
|
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
our.domain.ui.html/src/main/js/scout/table/Table-cisi.css
which contains:
@import (less) "scout/table/Table.css";
@table-row-padding-y: 3px;
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
Messages: 34
Registered: December 2016 |
Member |
|
|
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.
The topic is especially important for me, because my employer is at the moment in the state of evaluating different platforms for a modern HTML UI for our entire software. I was and I am evaluating Scout, and I'm with the OP that so far what I have seen Scout is the best framework I know and that I really learned a lot by just evaluating it. And that is exactly what I stated to the superiors. But they have doubts of using a framework because some think that this means being trapped in its abilities and using plain JavaScript and doing all the work ourselves would be more flexible. Me, I know that we will not be able to achieve what Scout provides in years. But unfortunately I am not the one who will decide. At some point of time in the future, I will have to convince them and for that I will at least have to to show that it is possible to write your own JS widgets in Scout. Showing to modify the existing ones would be even better.
Any help to this task would be really appreciated and again, I think also it would be interesting for other users to. Thank you. 
|
|
|
| Re: [NEON] Overriding org.eclipse.scout.rt.ui.html [message #1755302 is a reply to message #1755298] |
Thu, 02 March 2017 09:07 |
A N
Messages: 25
Registered: July 2014 |
Junior Member |
|
|
Urs Beeli wrote on Thu, 02 March 2017 07:44
I hope this helps you get started.
Yes, thats the kind of thing I have been looking for. Thank you!
Benjamin Schulte wrote on Thu, 02 March 2017 08:46The topic is especially important for me, because my employer is at the moment in the state of evaluating different platforms for a modern HTML UI for our entire software. I was and I am evaluating Scout, and I'm with the OP that so far what I have seen Scout is the best framework I know and that I really learned a lot by just evaluating it. And that is exactly what I stated to the superiors.
This is essentially my situation. The decision to re-implement our UI in HTML5 has been made and Scout has been declared the desired framework. We have outsourced the task to do so to a company specialized in usability concepts and UI design. Those folks are naturally not coming from a Java background and raised the question to what extend they can customize Scout leveraging HTML/CSS/JS.
Scout has been picked by us since it would allow us to reuse the knowledge we have on Java instead of having to invest a lot of resources in implementing a plain HTML/CSS/JS solution.
[Updated on: Thu, 02 March 2017 09:09] Report message to a moderator |
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06166 seconds
] 
Search
Help
Register
Login
Home
