Hi I'd like to check my Apache Taverna server URL plz
Hi there I'm Park, S.Korean noob hand-worker trying to implement workflow on Web. i'd request to check my Url on Apache Taverna server ver-2.5.4 and ask several questions In short, How do I get the Taverna server UUID, running for service? and also wonder How to write a Url structure I've already set up the server in CentOs7, following a manual; this (http://dev.mygrid.org.uk/wiki/display/tav250/Installation+Guide) Then, restarted the apache-tomcat and confirmed perfectly that '5 Minute Guide to Using the REST API' on my screen. but, running the Url; IP:PORT/taverna/rest/runs/ + uuid, it said me 'unknown run UUID'. I have no idea why it can not figure out my UUID. I've got the UUID from 'id' xml tag in 'IP:PORT/taverna/feed' service. and kept it change when server restart. FYI, Full Url is 'IP:PORT/taverna/rest/runs/7cbda4a8-21ca-4d22-83d5-9d0959ab1e5b' is that something wrong? or some mistakes? it has different way to get the UUID? I don't know anything :( Plz Plz let me know asap. As that trouble, i waste my time like silly today. i trust u answer my question So plz... Thank u for ur reading Sincely 12.03.2018 Ted Park
[GitHub] incubator-taverna-mobile pull request #66: Adds tutorial screens on first st...
Github user saketkumar95 commented on a diff in the pull request: https://github.com/apache/incubator-taverna-mobile/pull/66#discussion_r173773226 --- Diff: app/src/main/AndroidManifest.xml --- @@ -37,14 +37,18 @@ limitations under the License. android:label="@string/app_name"> +android:name=".ui.tutorial.TutorialActivity" --- End diff -- I have used the preference which checks if the app is first time launched or not. ---
[GitHub] incubator-taverna-mobile pull request #66: Adds tutorial screens on first st...
Github user saketkumar95 commented on a diff in the pull request:
https://github.com/apache/incubator-taverna-mobile/pull/66#discussion_r173773188
--- Diff:
app/src/main/java/org/apache/taverna/mobile/ui/tutorial/TutorialActivity.java
---
@@ -0,0 +1,161 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.taverna.mobile.ui.tutorial;
+
+import android.content.Intent;
+import android.os.Build;
+import android.os.Bundle;
+import android.support.v4.view.ViewPager;
+import android.support.v7.app.AppCompatActivity;
+import android.text.Html;
+import android.view.View;
+import android.widget.Button;
+import android.widget.LinearLayout;
+import android.widget.TextView;
+
+import org.apache.taverna.mobile.R;
+import org.apache.taverna.mobile.data.local.PreferencesHelper;
+import org.apache.taverna.mobile.ui.FlashScreenActivity;
+import org.apache.taverna.mobile.ui.adapter.TutorialSliderAdapter;
+
+import butterknife.BindView;
+import butterknife.ButterKnife;
+import butterknife.OnClick;
+
+
+public class TutorialActivity extends AppCompatActivity implements
ViewPager.OnPageChangeListener {
+
+@BindView(R.id.slide_pager)
+ViewPager slidePager;
+
+@BindView(R.id.layoutDots)
+LinearLayout dotsLayout;
+
+@BindView(R.id.btn_skip)
+Button bSkip;
+
+@BindView(R.id.btn_next)
+Button bNext;
+
+int[] layouts;
+private PreferencesHelper preferencesHelper;
+
+@Override
+protected void onCreate(Bundle savedInstanceState) {
+super.onCreate(savedInstanceState);
+preferencesHelper = new PreferencesHelper(this);
+if (!preferencesHelper.isFirstTimeLaunch()) {
+launchFlashScreen();
--- End diff --
@sagar15795 Check this!
---
[GitHub] incubator-taverna-mobile pull request #66: Adds tutorial screens on first st...
Github user saketkumar95 commented on a diff in the pull request: https://github.com/apache/incubator-taverna-mobile/pull/66#discussion_r173773510 --- Diff: app/src/main/AndroidManifest.xml --- @@ -37,14 +37,18 @@ limitations under the License. android:label="@string/app_name"> +android:name=".ui.tutorial.TutorialActivity" --- End diff -- I have used the preference which checks if the app is first time launched or not. ---
Re: GSOC: Add Common Workflow Language support to Taverna
Hi all, I hope you're doing well. Please find in the link below the not finished proposal. https://docs.google.com/document/d/1nwq1A_BUiXX8lKxwWg8-n-IuI_1F4dX7ZrmGOliTrXs/edit?usp=sharing I am not sure how the proposal needs to be in terms of length, details and content. I am sending you the proposal so far so you can have an idea and you can correct me if I made mistakes or if I need to elaborate more on certain parts. Any remarks are welcome. Thank you for your time. Best regards, Majdi On Mon, Mar 5, 2018 at 10:21 AM, Majdi Haouech wrote: > Hi Stian, > > Thank you so much for your reply. > I am really sorry for my late reply. > > Thank you for the information you provided. I strongly agree with what you > said. > > I am seeing the tutorials and reading the doc. Soon I will start preparing > the proposal and I will keep you in touch. > Thank you once again for your message. > > Best regards, > Majdi > > On Wed, Feb 21, 2018 at 12:57 PM, Stian Soiland-Reyes > wrote: > >> Hi, Majdi, thank you for your intest in GSOC and Apache Taverna! >> Apologies for late reply. >> >> On Thu, 15 Feb 2018 05:08:55 +0100, Majdi Haouech < >> majdi.haou...@gmail.com> wrote: >> > I have worked with different languages and technologies, to name a few: >> > Java, C, C++, Python, JS, Git, OWL, JavaEE, RabbitMQ, Maven. >> > I am also contributing to a Mozilla open source project which required >> > working with existing code and delivering a full working and completely >> > tested contribution. >> >> This is a strong background! It's good you have experience with both >> OWL, Python and Java. As you might have noticed the cwltool reference >> implementation is written in Python, while Taverna is (largely) in Java. >> >> >> > > First, I need to be familiar with the CWL specification in order to >> be able >> > > to convert YAML files to Taverna workflows. >> > > Next, I'll need to do the opposite work by transforming a Taverna >> workflow >> > > into YAML files following the CWL specification as well. >> > > Finally, if there will be enough time, I can contribute to Taverna's >> Tool >> > > Activity by completing the TAVERNA-878 issue. >> > > I understand that the contribution will be to the Taverna Language >> API and >> > > any other remarks are welcome. >> >> Yes, this can be a good way to start. I am a bit worried about going >> for both CWL import and export at the same time - although trying to >> have some kind of round-trip support would be wonderful! >> >> I think what you are proposing is to keep the translation structural at >> first, that is Taverna can import the CWL workflow and get the >> correct boxes/arrows connected, but would not know >> how to execute the CWL tools (pending TAVERNA-878). >> >> So this could for instance be that you import CWL tools into the dummy >> CWL activity we already have >> https://github.com/apache/incubator-taverna-common-activitie >> s/tree/cwl-browse/taverna-cwl-activity >> where it would just keep a JSON tree of the CWL Tool configuration >> without knowing how to execute it. That should make it easier to do a >> round-trip save out again. >> >> TAVERNA-878 could easily also be the most time-consuming part of the >> effort, so it might be good to not risk all on that. You may have a go >> at doing just simple CWL command line tools (e.g. just arguments and >> stdin/out without files) which should be easier to map to the existing >> Tool activity. >> >> >> Export of Taverna Workflows to CWL can seem challenging because in >> Taverna we have many types of activities which are not supported by >> other CWL engines: >> https://taverna.incubator.apache.org/javadoc/taverna-common-activities/ >> >> So again it could be a structural export where the CWL side just has >> "TavernaActivity" and includes the Taverna Activity JSON for opposite >> round-trip, but would not be executable on other CWL engines. >> >> (They should however work on http://view.commonwl.org/) >> >> If you then towards the end want to move beyond structural/skeleton >> export of Taverna workflows into CWL you can progress to export the >> Taverna's Command Tool activity as CWL command line tools. Again there >> might be features in the Taverna side that don't match exactly to CWL, >> which you can say is not supported. >> >> >> > > I am used to work with different technologies and dealing with >> different >> > > specifications. >> >> Great, yes, that is perhaps also the greatest challenge of this >> particular GSOC project, in that you will be integrating between several >> existing technologies and specifications! >> >> >> > > I am also used to work with existing code and extending it. >> > > Also, I am really motivated for contributing to an Apache project and >> this >> > > opportunity is perfect for me to dive right in with the right support. >> >> Thank you, we very much welcome your effort! >> >> What I think you could do next is to have a go with the different >> technologies, see the tutorials -
[GitHub] incubator-taverna-mobile pull request #66: Adds tutorial screens on first st...
Github user sagar15795 commented on a diff in the pull request: https://github.com/apache/incubator-taverna-mobile/pull/66#discussion_r173862548 --- Diff: app/src/main/AndroidManifest.xml --- @@ -37,14 +37,18 @@ limitations under the License. android:label="@string/app_name"> +android:name=".ui.tutorial.TutorialActivity" --- End diff -- But first show flash screen then tutorial. And manage first time launch in flash screen. ---
