[ovirt-devel] Question about plan/work for javascript SDK

[Vojtech Szocs]

Hi Yair,

indeed, oVirt JS binding & oVirt.js library are meant to be used not
only by our GWT-based UI (WebAdmin, UserPortal), but also by any 3rd
party JS-based application/tool, be it a UI plugin, a totally custom
UserPortal, or even Node.js-powered custom service talking with Engine.

This is the reason for going with JavaScript-first approach, escaping
the GWT/Java box and putting emphasis on JavaScript language/runtime.
oVirt.js for JavaScript is meant to be what oVirt Java SDK is for Java,
however oVirt.js should be usable from both client (i.e. browser) and
server (i.e. Node.js) environment by providing reasonable abstractions.

Some more comments below.

Regards,
Vojtech

PS: the MEAN stack looks cool!


----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Greg Sheremeta" <gshereme at redhat.com>, "Yair Zaslavsky" <yzaslavs at redhat.com>
> Cc: devel at ovirt.org
> Sent: Thursday, April 10, 2014 8:15:32 AM
> Subject: Re: [ovirt-devel] Question about plan/work for javascript SDK
> 
> On 04/10/2014 04:52 AM, Greg Sheremeta wrote:
> > Hey,
> >
> > Plain old UI Plugins can, in theory, use any backend they would like to. (I
> > don't know MEAN, so not sure if this helps answer your question.)

+1

Generally speaking, UI plugin feature makes no assumptions of backend.
But it's a (very) common requirement to integrate with oVirt Engine,
so using oVirt.js within your UI plugin sounds like a common use case.

> >
> > But the real power of oVirt.js is that it allows any type of JavaScript
> > frontend to access ovirt-engine. Perhaps you want to write a super-light
> > version of webadmin. You can do that with oVirt.js.
> >
> > Of course, Vojtech will have a way better answer than mine :)

You gave a very good answer, I have no comments :)

> 
> just remember you need it to be stable/maintain backward compatibility
> if it is to be used by anyone other than webadmin/userportal

Yes, we are aware of this.

Before we go from PoC to stable, we will spend some time for discussing
the final design (and possibly try to anticipate future changes that
would reflect into API design/implementation).

> 
> >
> > Greg
> >
> > ----- Original Message -----
> >> From: "Yair Zaslavsky" <yzaslavs at redhat.com>
> >> To: devel at ovirt.org
> >> Sent: Wednesday, April 9, 2014 8:03:16 PM
> >> Subject: [ovirt-devel] Question about plan/work for javascript SDK
> >>
> >> Hi,
> >> Unfortunately I could not attend the tech talk Vojtech presented this week
> >> (I
> >> did attend the 2nd one about UI-Plugins and Anjular JS).
> >> I was wondering if 3rd party developers will be able to use the ovirt.js
> >> library/framework for developing JS-based tools around oVirt (let's say -
> >> using the MEAN stack).
> >> Not sure how much we gave thought to this, so I'm asking here
> >>
> >> Thanks for any insights on this,
> >>
> >> Yair
> >> _______________________________________________
> >> Devel mailing list
> >> Devel at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> >>
> > _______________________________________________
> > Devel mailing list
> > Devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> 
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>