Home » Archived » Eclipse SmartHome » Editable sitemaps through REST
|
| Re: Editable sitemaps through REST [message #1690583 is a reply to message #1688821] |
Sun, 29 March 2015 13:13   |
 Chris Jackson
Messages: 256
Registered: December 2013 |
Senior Member |
|
|
Hi Kai,
In HABmin there are a few features relating to this that I thought I'd mention... Firstly, in HABmin 1, there was a graphical drag and drop designer for sitemaps, and I had a POST interface that does pretty much exactly what you suggest and writes the sitemap back to the system. For the current sitemap system, this is probably fine, although in some respect, being able to write a single page might be nice...
However, for a more general, forward looking view, I think a bit of a revamp is needed. In HABmin 2 I support sitemaps, although not with too many widgets at the moment. However, I also intend to move more towards a dashboard system where widgets can be placed on the screen. This is currently focussed on charting type dashboards (there's a picture below of what this looks like - sorry - localisation was in French when I took the image) but in the longer term I want to add more widgets to support more of the functionality that sitemaps provide - buttons, video, etc.
So, if we were to have something like this as part of OH, that would be great. Currently, other than the widgets being different, I need to save positioning information (currently, col/row/sizeX, sizeY), although again the plan is to add more metadata to allow common attributes on widgets (eg borders or whatever). This isn't currently implemented so is a blank page in the setup dialog at the moment 
I guess it depends on how you see sitemaps as to how you proceed. In one respect you say sitemaps are a common layout mechanism, but then you say they don't have to make sense to all UIs. If I understand this correctly, then you're moving away from a rigid list of widgets to something more flexible, and the sitemap REST interface is simply a place to store this information and the widgets themselves are up to the UI designer?
If that's correct, then my view would be to try and stick to a core set of widgets, but allow UIs to add widgets without having to add to the core code, and also to enhance core widgets. Again, using an example here in HABmin, the HABmin dashboard, and hopefully soon the HABmin sitemap, doesn't use the chart servlet - I use the inbuilt charting system which allows nice pinch to zoom and swipe to scroll type interaction. However, it would nice to still use the same chart definition so that static charts can still be used within the same sitemap in other UIs. Currently this isn't directly possible without a bit of creative reuse of the available fields since the chart widget doesn't pass information to the UI on the items/groups being charted in a nice way. My current intention is to use the label field to store this information, but it would be nice to have something a bit more uniform - maybe allowing UIs to store additional metadata within the widgets?
Things like hyperlinking to other sitemaps would be good - then we can build sitemaps as individual pages and link them together as we like...
Anyway, just some thoughts from me (sorry - my second long email today  ).
If you wanted to look at the HABmin dashboard designer, take a peek here (http://cdjackson.github.io/HABmin2/#/dashboard/). It should hopefully work, but as it's static, you can't save and anything that links to the server will cause an error...
Cheers
Chris
[Updated on: Sun, 29 March 2015 13:14] Report message to a moderator |
|
| | |
Goto Forum:
Current Time: Thu Apr 25 05:04:20 GMT 2024
Powered by FUDForum. Page generated in 0.02893 seconds |
] 
Search
Help
Register
Login
Home
