publishing 3rd party developed UIZE compliant widgets in a hosted environment

[Mahesh Venkat]

Hi,

I am a newbie to UIZE.  I browsed through the widget documentation and the various examples.  It is a very impressive JS framework to manage UI components.

I have a question relating to 3rd party developed widgets:

I would like to I host a UIZE compliant web site (similar to zazzle) with some native widgets and some server side REST APIs.  I would like to encourage 3rd party developers to develop UIZE compliant Widgets that consume the REST APIs and publish them to my site.  How can it done?

If I  provide an upload link where the 3rd party developers can upload their UIZE compliant widgets, how can we make them available in the main site immediately?

If I like the Widget Adoption mechanism using JSON syntax.  Is this something I should explore?
Do you have examples of page widget with slot management where we can be add/update one widget with another widget?

Thanks
--Mahesh

[cvr]

Hi Mahesh,

Sorry it's taken a while to respond. Been quite busy writing
documentation and implementing a CSV parser for an Illustrator
scripting project (yes, UIZE can also be used inside Adobe's Photoshop
and Illustrator applications).

I'm glad you can appreciate the power of the UIZE JavaScript
framework. And we're making it stronger all the time. Regarding your
question about the third party UIZE compliant widgets - sounds like a
great idea to me, and we'll give you all the support we can. I
couldn't gather enough specifics from your question to be able to
offer more concrete advice. At a high level, at least, it seems like
it should all be doable.

Given code that is uploaded to a server, it should be possible to
instantiate those widgets on a page dynamically. Where the HTML and
CSS come from are questions you'll have to find answers to /
approaches for. If there needs to be a configurator interface for each
widget, then the developer would have to register a widget's interface
so a configurator interface can be driven off of that information.
This sounds to me like a layer built on top of the framework - a
specific system with its own constraints / standards.