Write CSS to external files [Feature Request]

Q&A about the latest versions
Post Reply
sparrow
Posts: 63
Joined: Thu Aug 04, 2016 12:44 pm

Wed Aug 19, 2020 12:07 pm

Hi Martin

Can we put in a feature request to write all Pano2VR CSS to a standalone CSS file. IE not inlined in the HEAD.

We do have an option for 'Create files for external embedding' but it doesn't seem to apply to CSS.

The reason is, some of us like to edit our CSS outside of the Pano2VR application and sometimes it's not convenient or possible to open Pano2VR, generate the project and upload etc.

IMHO this would make a huge difference to my workflow and improve my speed for developing custom skins.


If this is a big task, it could be done with 2 phases

Phase1: Just write the default, simpler CSS to a standalone file

Code: Select all

<style type="text/css" title="Default">
			body, div, h1, h2, h3, span, p {
				font-family: Verdana,Arial,Helvetica,sans-serif;
			}
			/* fullscreen */
			html {
				height:100%;
			}
			body {
				height:100%;
				margin: 0px;
				overflow:hidden; /* disable scrollbars */
				font-size: 10pt;
				-webkit-tap-highlight-color: rgba(0, 0, 0, 0); /* remove highlight on tab for iOS/Android */
			}
			/* fix for scroll bars on webkit & >=Mac OS X Lion */ 
			::-webkit-scrollbar {
				background-color: rgba(0,0,0,0.5);
				width: 0.75em;
			}
			::-webkit-scrollbar-thumb {
    			background-color:  rgba(255,255,255,0.5);
			}
		</style>
Phase2: Write ALL CSS to a standalone file. IE everything that is normally inlined.
Neal
Posts: 177
Joined: Thu Dec 12, 2013 11:14 am
Contact:

Wed Aug 19, 2020 2:19 pm

I am seconding this request. There is a great deal of inline styling that could be written into a CSS file. This would allow for the browser to cache the general layout, reducing loading time and bandwidth.
sparrow
Posts: 63
Joined: Thu Aug 04, 2016 12:44 pm

Wed Aug 19, 2020 2:57 pm

That's a good point too. I'm building a list...
  • Better caching of the general layout, reducing loading time and bandwidth
  • Better separation of presentation and content
  • Easier over-ride of CSS styles with either our own CSS or CSS frameworks
  • Ability to quickly make CSS changes outside of the App
  • Quicker testing of ideas and prototyping CSS changes
Post Reply