On Wed, Jun 8, 2016 at 3:31 PM, Manuranga Perera <[email protected]> wrote:
> Hi Tanya, Sinthuja, > > 1) We had a chat about how we can use gadget parameters instead of > generation, have you guys considered that approach? > > We have cases like database credentials which should not be shown to the user and should not be editable from the gadget properties. Further we also need a model that gadget should be greeted by some privileged user and used by others, so the gadget generation is the appropriate model to handle this. > Edit/ Re-generate function is not supported yet. > > 2) The issues is, with this model it will be harder to support that even > in the future. At least we should serialize all the parameters with the > generated gadget. > > Editing is something we can achieve with very little effort, if we store all the properties that we have passed in the UI in a config file within the gadget then we can simply load that to the gadget generation wizard when we need to modify the gadget. Regards Suho > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *S. Suhothayan* Technical Lead & Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
