Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kuksa-dev] kuksa ide - che vs vscode
For example, in [4], is the logic of connecting to hono, embedded in W3CClinet?

[4]. https://github.com/eclipse/kuksa.apps/blob/master/invehicle-apps/sensoris.invehicle/sensoris/src/main.cpp

On Tue, Mar 17, 2020 at 11:57 AM Soheila Dehghanzadeh <sally.de@xxxxxxxxx> wrote:
Hi Philipp,

Thanks for your reply. According to Robert, RAML is mainly for modeling API communication between AGL applications "in vehicle". Could you please elaborate it with an example?
Following the temperature sensor example in [1], (the application scenario [2] is missing btw), RAML2AGL will generate client (I suppose AGL service to read from sensor? Is that right?) and server source code for receiving sensor data (Does that apply hono logic-i.e., curl command with tenant and device info- for updating device data?), which means client/server communication and is against "in vehicle".
I am missing such a scenario for vscode page [3]. I wonder, how do you model communication of a sensor in vscode with cloud?


Thanks alot,

Best regards
Soheila


On Tue, Mar 17, 2020 at 9:28 AM Philipp Heisig <philipp.heisig@xxxxxxxxxxxxxx> wrote:

Hi Soheila,

the current version of the vs plugin for Che 7 is mainly focussing on the integration of kuksa-ready docker images within the kuksa ecosystem by supporting the generation of according docker images for in-vehicle apps (cf. https://github.com/eclipse/kuksa.ide/blob/master/VSCode-Extensions/kuksa/build.sh) and their publishment in the app store/hawkbit (cf. https://github.com/eclipse/kuksa.ide/blob/master/VSCode-Extensions/kuksa/kuksa-publisher.py).

We do not consider any explicitly modeling languages at this point as this would be somehow specific to the used OS/application. Thus, the developement process is up to the developer and (yet) abstracted in the plugin. The same applies for the configuration of Kubernetes and the operation of a cloud environment, this is out of scope. I wonder what you wanna configure and for what purpose you want to use kubernetes in this context. Setting up the Kuksa Cloud envrionment is more in the focus of https://github.com/eclipse/kuksa.cloud

Best regards
Philipp

Am 16.03.2020 um 14:34 schrieb Soheila Dehghanzadeh:
Dear Robert,

Thanks for your reply, which modeling language are you using for vscode? configuration of Kubernetes?

Best regards
Soheila

On Mon, Mar 16, 2020 at 9:41 AM Robert Höttger <robert.hoettger@xxxxxxxxxxxxxx> wrote:
Dear Sohelia,

RAML2AGL only generates the (communication) skeleton for AGL applications. 
We did not migrate RAML2AGL to VSCode (which should be possible in general though), since we switched from considering AGL only to using docker for covering a wider set of operating systems.

Best regards,
Robert


On Mar 12, 2020, at 11:06, SOHEILA DEHGHANZADEH <s.dehghanzadeh@xxxxxxxxxxxxx> wrote:

Dear All,

In kuksa IDE there is 2 ways to generate code, the che extension is using the RAML2AGL which converts API definition from  RAML into AGL code, I wonder, does RAML also supports actual implementation of the REST service or is it just a configuration file which pulls the rest service from a docker registry?

Does vscode approach also uses a modeling language like RAML? In the description here[1]and here [2] is it not clear where the function of the API is coming from.

I appreciate any comments.
[1]. https://github.com/eclipse/kuksa.ide/tree/master/che-6
[2]. https://github.com/eclipse/kuksa.ide/tree/master/VSCode-Extensions
Best regards
Soheila





_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/kuksa-dev

_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/kuksa-dev

_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/kuksa-dev
--

Fachhochschule Dortmund
University of Applied Sciences and Arts

M.Sc. Philipp Heisig
Institut für die Digitalisierung von Arbeits- und Lebens­welten (IDiAL)
Otto-Hahn-Str. 27 - 44227 Dortmund

Raum OHS 27 OG 2.04
Tel     0231 9112-9561
philipp.heisig@xxxxxxxxxxxxxx
www.fh-dortmund.de

_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/kuksa-dev

Back to the top