374
« on: June 25, 2008, 12:13:39 am »
I've been thinking about this and as I said I was not able to make heads or tails of how the current system works, but as far as creating templates, it would be nice if the internal actions of LMCE were all listed in one place that could be referenced by people quickly and easily when creating templates. Possibly extending and changing the functionality of the templates slightly so that the user can check a box or something to share their custom templates to a central point where other users could then retrieve them thus eliminating the need to have them in the main trunk. For something like this to work and be efficient I'd imagine the templates would need to be tagged in some structural format like:
Category: (limited to Automation, Security, Media, Phone or something)
Device Model:
Template Name: (500ft. 200MPH name to give an idea what the template does)
Description: detailed description so users can decide if it is what they are looking for
Is there some screencasts for Ruby in the GSD available for the complete Ruby noob like Thom has put together for HADesigner?
As I understand it the actions in LMCE are mapped with numerical ID's which is quite cryptic, I might be missing something, but wouldn't it be easier to have them setup similar to how XBMC is using them in a single table where the actions are created and accessed so they could be accessible in a very streamlined fashion from HADesigner, any custom scripts, and the rest of the source? I'm sure it's probably not an easy change at this point if it's not handled similarly at all to that method currently, but on the flip side the more the code grows the harder it will be to change later.
Just a few thoughts I had...any input?