>From >http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/Extension-showing-VM-status-td2955.html
After looking deeper at extensions and looking at this mess of a discussion, it seems that the definition of Extension you guys at guacamole dev are using is wrong. What I see is like making new software all together - not an extension. If you made some path one application can interact with another - it is not extension - it is API at best if not BS Close to proper understanding - extension should use internal framework of the software with ability to make changes stay when software framework changes. it is crazy to ask people make everything on the side - css, html, sql and everything else. And even more silly to expect someone to use this so called extension way of things you present with such scope. No wonders there are no extensions. Again. What would be consider extension for guacamole is ability to create ONE - in caps ONE - file, which, for example, will have extra DB fields user want, and list of changes to files and/or variables for guacamole, which will in turn, being parsed by guacamole, will produce changes to whatever part or variable was changed. There should be list of variables, and all and every single thing which happens and shows is taken from those. Ask the guys from Apache foundation - they will teach you. When one writes software which extends functionality of your software - it is different type of extension. The ability to use Extensions for software Guacamole should be what I described in previous paragraph or very close to it.
