Hi Jatin,

Yes eventually. So you can have the first milestone to develop this 
independently, then you can have subsequent milestones to integrate with PGA. 
That way you are leveraging PGA to take care of authentication, authorization 
and other functionality. There is of course usability. So for your gsoc, start 
with taks you can manage and build on them.

Suresh

> On Mar 18, 2016, at 4:37 PM, Jatin Balodhi <[email protected]> wrote:
> 
> Sir, is it good to integrate airavata with PGA?
> 
> Jatin
> 
> On Saturday 19 March 2016 01:58 AM, Suresh Marru wrote:
>> Jatin, here is the doc link - 
>> http://airavata.staging.apache.org/documentation/api-docs/0.16/ 
>> <http://airavata.staging.apache.org/documentation/api-docs/0.16/>
>> 
>> Always your best source is look at the Airavata API itself, thrift is pretty 
>> readable - 
>> https://github.com/apache/airavata/tree/master/thrift-interface-descriptions 
>> <https://github.com/apache/airavata/tree/master/thrift-interface-descriptions>
>> 
>> Suresh
>> 
>> 
>>> On Mar 18, 2016, at 4:07 PM, Jatin Balodhi <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Are there documentation about airavata-api in php?
>>> if there is Please send the link.
>>> 
>>> Jatin
>>> 
>>> On Saturday 19 March 2016 01:12 AM, Suresh Marru wrote:
>>>> Yes the though is support both Rich Client (in Java FX or Apache Pivot) 
>>>> and web, so users can pick what they like and integrate into their client 
>>>> tools. Airavata supports both web based and desktop application downstream 
>>>> projects. 
>>>> 
>>>> Suresh
>>>> 
>>>>> On Mar 18, 2016, at 3:40 PM, Jatin Balodhi <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> 
>>>>> So, i was reading Bikramjeets discussions about making xbaya work for 
>>>>> airavata 0.16 and delivering json output, so would it be better for 
>>>>> making web application and xbaya able to read and generate same json 
>>>>> format?
>>>>> 
>>>>> Jatin  
>>>>> 
>>>>> On Saturday 19 March 2016 01:00 AM, Suresh Marru wrote:
>>>>>> Hi Jatin,
>>>>>> 
>>>>>> Yes the idea is to mimic the same as drag and drop functionality. 
>>>>>> 
>>>>>> Airavata workflow script moved from XML to JSON based. You can see an 
>>>>>> example in the google doc linked form the JIRA -  
>>>>>> <https://issues.apache.org/jira/browse/AIRAVATA-1894>https://issues.apache.org/jira/browse/AIRAVATA-1894
>>>>>>  <https://issues.apache.org/jira/browse/AIRAVATA-1894>
>>>>>> 
>>>>>> You might find this discussion also useful -  
>>>>>> <http://markmail.org/thread/tkpbj3sr4jhg6o6z>http://markmail.org/thread/tkpbj3sr4jhg6o6z
>>>>>>  <http://markmail.org/thread/tkpbj3sr4jhg6o6z> 
>>>>>> 
>>>>>> Suresh
>>>>>> 
>>>>>>  
>>>>>>> On Mar 18, 2016, at 3:25 PM, Jatin Balodhi < 
>>>>>>> <mailto:[email protected]>[email protected] 
>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>> 
>>>>>>> sir, it about web based workflow editor,
>>>>>>> 1.The components should be same as components components of xbaya 
>>>>>>> (dragable and dropable)?
>>>>>>> 2.Is XML used for describing a workflow in Xbaya?
>>>>>>> 
>>>>>>> Jatin
>>>>>>> 
>>>>>>> 
>>>>>>> -------- Forwarded Message --------
>>>>>>> Subject:        Re:
>>>>>>> Date:   Fri, 18 Mar 2016 15:17:29 -0400
>>>>>>> From:   Suresh Marru  <mailto:[email protected]><[email protected]> 
>>>>>>> <mailto:[email protected]>
>>>>>>> Reply-To:        
>>>>>>> <mailto:[email protected]>[email protected] 
>>>>>>> <mailto:[email protected]>
>>>>>>> To:     Airavata Dev  
>>>>>>> <mailto:[email protected]><[email protected]> 
>>>>>>> <mailto:[email protected]>
>>>>>>> 
>>>>>>> Which query are you referring you Jatin?
>>>>>>> 
>>>>>>> Suresh
>>>>>>> 
>>>>>>> > On Mar 18, 2016, at 3:02 PM, Jatin Balodhi <[email protected]> 
>>>>>>> > <mailto:[email protected]> wrote:
>>>>>>> > 
>>>>>>> > Hi
>>>>>>> > 
>>>>>>> > I'm going to write a proposal for GSOC 2016, but I have some queries 
>>>>>>> > about airavata and working of workflow editor, please if someone can 
>>>>>>> > follow up with me for resolving my queries.
>>>>>>> > 
>>>>>>> > Thanks
>>>>>>> > Jatin
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 

Reply via email to