saussact / openhab

Automatically exported from code.google.com/p/openhab
0 stars 0 forks source link

Suggestion: images folder per sitemap (optional) #41

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
It would be nice to have several images folders, one for each sitemap. For 
example there may be a default images folder located at 
configurations/images/default that would be used in case there isn't found own 
images folder for a given sitemap. If the user wants to use a separate image 
set for the demo sitemap for example, he could copy the 
configurations/images/default folder to configurations/images/demo and make his 
changes (rename images to match item states, add own images, etc.). Any other 
sitemap will continue to use the default images folder.

Original issue reported on code.google.com by mishoboss on 2 Aug 2011 at 2:04

GoogleCodeExporter commented 9 years ago
I'll appreciate any comment about these ideas :)
I find them useful as they prevents images rewriting on openHAB update that 
could be customized and opens a way to some kind of theming. Also the current 
location of the "images" folder in "webapps" is illogical to me for 2 reasons:
1. For me the images are configurables and need to be inside the 
"configurations" folder. Personally I use my own images and image-sets.
2. You say that openHAB is designed to have many interfaces - web-based, native 
mobile clients, TV apps and so on. The "webapps" folder sounds somehow 
restrictive to only web-based clients.

Original comment by mishoboss on 7 Dec 2011 at 1:37

GoogleCodeExporter commented 9 years ago
Sorry, but I do not really see the need to change anything here for the moment.
Regarding 1.: For me, icons are resources, not configurations. If the user does 
not like the standard resources, he is free to change them. To avoid having 
custom icons overwritten by updates, you can simply create icons with ne w 
names and reference these from your sitemaps. I would suggest this as a best 
practice here.
Regarding 2.: The webapps folder is THE way to have these resources served 
through the embedded Jetty - without having this folder to include or configure 
in any specific UI. Native clients thus have the possibility as well to access 
these icons directly from the server (so that they do not have to be built-in).

Original comment by kai.openhab on 11 Dec 2011 at 10:29