Automation module development

[maros]

I'm currently working on a set of automation modules for the zway smarhome UI. (eg. https://github.com/maros/Zway-Astronomy, https://github.com/maros/Zway-RaspberryCam, ...) and I do have a couple of questions regarding best practices.

1. Is there any structured way of publishing extensions for the smarthome ui, so that they can be easily reused? (like the Vera app store)
2. What is the preferred way of including third-party libraries that may be reused by multiple modules? (ie a sha1 calculation library)
3. What is the preferred way of expressing dependencies between extensions? Ie. An advanced blind controller extension that needs data from a weather module and an astronomy module?
4. Is there any way of creating custom UI widget (eg. a four way toggle button to switch between presence/away/vavation/night states)

[PoltoS]

1. Will come soon
2. Modules can intercommunicate via events. Look on Cron module as an example.
3. No, since all UIs needs to implement it. We are thinking of a "select" widget, but it is not yet implemented.