Heya Sonny, What kind of plugins would this be? I like the idea of being able to extend the ui dynamically, but I fail to see the use case here. Could you give some examples of what kind of plugins would end up using this system?
Cheers, Hugo > -----Original Message----- > From: Donal Lafferty [mailto:donal.laffe...@citrix.com] > Sent: Friday, December 14, 2012 12:59 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: '[PROPOSAL]' Third party plugins > > Okay, but I'd like a way of distinguishing in speech and text this new way of > extending CloudStack from the existing way. > > -----Original Message----- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: 14 December 2012 2:05 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: '[PROPOSAL]' Third party plugins > > Isn't there a use case for a plugin that has both server and GUI components? > May be we should keep the name generic. > > Thanks > Animesh > > On Dec 13, 2012, at 5:08 PM, "Pranav Saxena" <pranav.sax...@citrix.com> > wrote: > > > Yeah , we can pick different names for each plugin . I am not sure if we'll > keep a specific format for the naming . All what is required is mapping to a > unique ID associated with that plugin which would take care of adding a third > party plugin to the cloudstack dashboard. > > > > Regards, > > Pranav > > > > -----Original Message----- > > From: Donal Lafferty [mailto:donal.laffe...@citrix.com] > > Sent: Thursday, December 13, 2012 3:53 PM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: '[PROPOSAL]' Third party plugins > > > > I've a question on terminology. > > > > Are these 'GUI plugins' going to use the same component.xml class loader > as existing plugins? If not, can we pick different names for each approach to > providing a plugin? E.g. 'GUI plugins' and 'driver plugins'? > > > > DL > > > > > > -----Original Message----- > > From: Pranav Saxena [mailto:pranav.sax...@citrix.com] > > Sent: 13 December 2012 10:22 PM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: '[PROPOSAL]' Third party plugins > > > > Currently , we haven't discussed access based scenario for a plugin . But > > yes > , this won't be a tough thing to incorporate. We can enable /disable a UI > plugin based on admin or a normal user . > > > > Regards, > > Pranav > > > > -----Original Message----- > > From: Fang Wang [mailto:fang.w...@citrix.com] > > Sent: Thursday, December 13, 2012 11:46 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: '[PROPOSAL]' Third party plugins > > > > This is a silly question, Do we allow all plugins to have same access role? > > OR some plugins have admin access, and some plugins for users only? > > > > Thanks, > > -Fang > > > > -----Original Message----- > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > > Sent: Thursday, December 13, 2012 10:52 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: '[PROPOSAL]' Third party plugins > > > > Sonny > > > > How does administrator enable/ disable the plugin if it is misbehaving > because of bug or let's say after upgrade? > > > >> -----Original Message----- > >> From: Fang Wang [mailto:fang.w...@citrix.com] > >> Sent: Thursday, December 13, 2012 10:11 AM > >> To: cloudstack-dev@incubator.apache.org > >> Subject: RE: '[PROPOSAL]' Third party plugins > >> > >> I like the idea of the plugin button so users can see all the plugins. > >> > >> -----Original Message----- > >> From: Sonny Chhen [mailto:sonny.ch...@citrix.com] > >> Sent: Wednesday, December 12, 2012 4:01 PM > >> To: cloudstack-dev@incubator.apache.org > >> Cc: Brian Federle; Pranav Saxena > >> Subject: '[PROPOSAL]' Third party plugins > >> > >> Hello All, > >> > >> I would like to discuss a new feature that is being worked on for the > >> next release of CloudStack. It is the ability to add third party > >> plugins into CloudStack while still utilizing the current ui. The > >> procedure in which this would occur is as follows: > >> > >> > >> 1. The developer will write a plugin that they would like to add > >> into > >> CloudStack > >> > >> 2. Using a predetermined file hierarchy we create, the developer > >> will > >> place their plugin within the folder structure and fill out a > >> plugin.js file > >> > >> 3. The admin will then place this folder into the existing CloudStack > >> "plugin" > >> > >> 4. The admin will then add this new listing onto the plugin.js file > >> that > lies > >> within that folder > >> > >> 5. The user then just has to refresh the browser and the plugin will > >> be > >> available to use. > >> > >> We will be toying with the idea of adding a plugin button to the > >> navigation so that the user can see what plugins have been installed > >> and click on them to access them. > >> > >> Please see the link below for more information. > >> > >> > https://cwiki.apache.org/confluence/download/attachments/30744936/plu > >> g > >> in.jpg > >> > >> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plug > >> i > >> n > >> > >> Thoughts, comments, suggestions? > >> > >> Thanks You and Best Regards, > >> > >> Sonny H. Chhen > >> Manager of User Interface & User Experience | Citrix Systems - > >> CloudPlatform > >> 4988 Great America Parkway, Santa Clara, CA 95054, USA > >
