Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6743F75C for ; Tue, 13 Aug 2013 11:25:40 +0000 (UTC) Received: (qmail 30673 invoked by uid 500); 13 Aug 2013 11:25:40 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 30571 invoked by uid 500); 13 Aug 2013 11:25:37 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 30564 invoked by uid 99); 13 Aug 2013 11:25:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Aug 2013 11:25:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shameerainfo@gmail.com designates 209.85.220.181 as permitted sender) Received: from [209.85.220.181] (HELO mail-vc0-f181.google.com) (209.85.220.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Aug 2013 11:25:30 +0000 Received: by mail-vc0-f181.google.com with SMTP id hz10so3662750vcb.40 for ; Tue, 13 Aug 2013 04:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GDd1MhqGrzueMVf3mLWxwJ2zNjOnbukhAejNGDDKHV4=; b=wrV7HkIbP5G4Dqvm1ExbP7eswCNR+q0jNquYBuRIaBlk1q5m5W6ji3SS0R3dYDJhUn 2U8Jw//2ihB5Xg/ub9buX5wTAdGgzdonOQ6y9fvnUdOMDp2leQv/GS3d4DxCmYacW3Kr hGdlTAF9Wm5PZEm0IFyL/omXxMkcHhNUphe/EOt2DQJrZVsAGGN9aIDl7ripp/RpcITX 0tW+qElHpBIJtSMxE/fXJaVQsX3EOGKUhQ+eB4K+bHocIKxBxdO1nZGdKNDcFnR7Cmrb dYhmftujAlH1UUYlasqoSA2GzbtPn6qkUlL7YGedwL7l4Q1n70iC+xmYPlL0apCf5eqL hugg== X-Received: by 10.220.183.2 with SMTP id ce2mr71900vcb.58.1376393109118; Tue, 13 Aug 2013 04:25:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.228.41 with HTTP; Tue, 13 Aug 2013 04:24:49 -0700 (PDT) In-Reply-To: References: From: Shameera Rathnayaka Date: Tue, 13 Aug 2013 16:54:49 +0530 Message-ID: Subject: Re: Integrating GSoC Master project building blocks To: dev Cc: Lahiru Gunathilake Content-Type: multipart/alternative; boundary=089e0115ea065726e904e3d27e4f X-Virus-Checked: Checked by ClamAV on apache.org --089e0115ea065726e904e3d27e4f Content-Type: text/plain; charset=ISO-8859-1 Hi Sanchit, On Tue, Aug 13, 2013 at 1:48 PM, Sanchit Aggarwal < sanchitagarwal108@gmail.com> 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 < > shameerainfo@gmail.com> 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 pagefor 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/ --089e0115ea065726e904e3d27e4f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi = Sanchit,

On Tue, Aug 13, 2013 at 1:48 PM, Sanchit Aggarwal <sanchitagarw= al108@gmail.com> wrote:
Hi Shameera

<= div>Well It is good if we have a native JS API which is not bound to any fr= amework,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 suit= able time?
yes sure lets have a hangout, Dhanushka could you arrange this hangout?. Wh= at 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 l= ittle documentation on UI part would be good.

Thanks,
Shameera.=A0


=A0

Regards<= span class=3D"HOEnZb">
Sanchit Aggarwal

=



On Sun, Aug 11, 2013 a= t 9:03 PM, Shameera Rathnayaka <shameerainfo@gmail.com>= wrote:
Hi All,

As everybody agreed, this is the t= ime for $Subject. As a first step we can plug registry with front-end web U= I. 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. P= lease refer this wiki page for airav= ata JS registry client API.

@Sanchit,
We were talking about writin= g a registry API as an angular service, But if we do that then this registr= y 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 a= ny 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 servi= ce for your implementation. We can do it , isn't it?

@Subho,
As you had asked i have added a= bout 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.




--
<= span style=3D"font-family:comic sans ms,sans-serif">Best Regards,Shameera Rathnayaka= .

email: shameer= a AT apache.org , shame= erainfo AT gmail.com
Blog : http://shameerarathna= yaka.blogspot.com/
--089e0115ea065726e904e3d27e4f--