cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

create/read variables to the ctrlX Data Layer with Python

yannic
Established Member

create/read variables to the ctrlX Data Layer with Python

EDIT by CodeShepherd: Post was moved to own topic from this thread.

Hey CodeShepherd,

thanks for your solution! But how does it work with the python wheel in the SDK you´ve said?

Greetings 

Yannic

3 REPLIES 3
CodeShepherd
Community Moderator

Re: create/read variables to the ctrlX Data Layer with Python

You will have to build your own app and install it on the ctrlX CORE. This app then can be provider and client of data. Please have a look in the documentation of the SDK for ctrlX AUTOMATION. It will be available on GitHub soon.

aFouraker
Long-established Member

Re: create/read variables to the ctrlX Data Layer with Python

@CodeShepherd, is it possible to load a pacake into a python instance without building it into a snap? If a root user installs a package is it availble to all python instances on the core? If a snap is created that has the required packages and installs them for the snap to run, are those packages now available for other scripts?

I am imagining an app that only serves to load packages for my python instances I run from the core independent of an app. 

CodeShepherd
Community Moderator

Re: create/read variables to the ctrlX Data Layer with Python

The best way would always be to pack everything together in one app. If you have more than one application that use the same packages also this is the way to go. You can add several in one single app.

You cannot extend the standard python interpreter that is part of the ctrlX CORE - Python Runtime App. Also there is no mechanism to install a package globally on the ctrlX CORE.

There are two cases where you create dependencies that would dissent to the idea of the snap technology. (Snaps are app packages for desktop, cloud and IoT that are easy to install, secure, cross-platform and dependency-free.):

  • Like mentioned in this thread, you could unpack a wheel and load the folders to the ctrlX CORE where an instance can access it.
  • When you pack your own app you can open an interface (e.g. via plug and slot mechanism) where you can then pack several packages into several apps to provide the functionality (worst architecture possible).
Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist