Hi Sanchit, On Tue, Aug 13, 2013 at 1:48 PM, Sanchit Aggarwal < [email protected]> wrote:
> 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 > code. > Can we have a hangout sometime this weekend ? please reply with a suitable > time? > yes sure lets have a hangout, Dhanushka could you arrange this hangout?. What about this Saturday 7.30 pm (IST) , 10.00 am (EST)? we can complete the parts that need to fix for this integration these days. @Dhanushka +1, yes little documentation on UI part would be good. Thanks, Shameera. > > Regards > Sanchit Aggarwal > > > > > On Sun, Aug 11, 2013 at 9:03 PM, Shameera Rathnayaka < > [email protected]> 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<https://cwiki.apache.org/confluence/display/AIRAVATA/JavaScript+Regsitry+Client>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 apache.org , shameerainfo AT gmail.com >> Blog : http://shameerarathnayaka.blogspot.com/ >> > > -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
