airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanchit Aggarwal <>
Subject Re: Integrating GSoC Master project building blocks
Date Tue, 13 Aug 2013 08:18:31 GMT
Hi Shameera

Well It is good if we have a native JS API which is not bound to any
framework,but I am not sure whether we can use the JS API directly in
Angular service due to angular constraints, else we have to replicate the
Can we have a hangout sometime this weekend ? please reply with a suitable

Sanchit Aggarwal

On Sun, Aug 11, 2013 at 9:03 PM, Shameera Rathnayaka <
> wrote:

> Hi All,
> As everybody agreed, this is the time for $Subject. As a first step we can
> plug registry with front-end web UI. For this we can have one or few
> hangout calls and work together to make it functioning. Please suggest if
> you have a different approach for this. Please refer this wiki page<>for
airavata JS registry client API.
> @Sanchit,
> We were talking about writing a registry API as an angular service, But if
> we do that then this registry api gets strictly bind to the angular. IMO it
> is not good. If we provide this as a native JS API which we currently have,
> then we are not bound to any framework and others can also use this API and
> write their own UI. What if we write a Angular service which use this API
> and use that Angular service for your implementation. We can do it , isn't
> it?
> @Subho,
> As you had asked i have added about how we can locally deploy and test our
> master project in local machine, into above wiki page under "Deploy
> JavaScript Registry" section. As this is not the correct way to deploy our
> final service i have stroked out the content. Later we can remove that.
> Thanks,
> Shameera.
> --
> Best Regards,
> Shameera Rathnayaka.
> email: shameera AT , shameerainfo AT
> Blog :

View raw message