• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

[INCORPORATED] Custom styling without modifying the valence.css

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [INCORPORATED] Custom styling without modifying the valence.css

    Is it possible to apply a specific (css) styling to a Valence portal, without modifying the valence.css so it is clearer for users to see the difference between a test and production environment?

  • #2
    Any news on this issue (suggestions or planning)?

    Comment


    • #3
      One choice is to modify a copy of the valence.css file, and include it in your file after the default.

      Alternatively, you could create your own css file which just overrides some items of the properties and maybe adds some of your own unique items. As long as that CSS class is brought in after the valence.css file. (and some item marked as important where it is the case in valence)


      Perhaps we can explore the idea of displaying, in the portal, a front-end configurable icon or background near the name of the environment on the toolbar. Would that be something like what your original question was looking for?

      Comment


      • #4
        Thanks for your reply. Yes I prefer not to modify any Valence sources (css / js / html). So your first two suggestions are not an option (already did this in the past). Actually we used aliases on vvresources in the past, but since Valence 3.x load the portal sources dynamically this does not work anymore. The problem about this solution was that our (overridden) Valence sources where not compatible with the new versions.

        What I would like is maybe that the portal would load in a custom css after the valence.css. Which can be specified somewhere in the Valence configuration. For performance this is not a perfect option, because the source is loaded in dynamically. Statis loading is faster but in that case the file name should be fixed. Maybe this custom css can always be loaded refering to a default empty ccs file that will never be overwritten by the Valence install. I that case we can fill this file with our own custom styling.

        Thanks again!

        Comment


        • #5
          We will consider the benefits of adding something like this in, but for now you can just add a css include in your desktop_portal.html file.

          Comment


          • #6
            Ok thanks. You mean portal_desktop.html (for anyone who wants to change this). Path: html/portal/core.

            Comment

            Working...
            X