If you look into it, you see there are several breakpoints that get loaded. All definitions are stored in projects/style/style with ui.scss as root file creating the final stylesheet. Modifying the stylesheet is quite simple if you only need some colors or want other fonts/sizes. To compile with sourcemap for easy debugging compile withh app-dev and all-dev instead! Modify Stylesheet All following compile commands need to be executed in a terminal inside the RSTouchscreenNG folder.Ĭompile only the touchscreen sources: > gulp app-prod Once you have new files, you need to provide updates to them with any server update or your users may not get fixes or improvements. Files you can add with this library are the css and the touchscreen apps for registration and controlling the printer. The sources contain an empty directory shadow – this will be your shadow directory that you use to overwrite the servers default content. After that is done you have all required modules and the gulp + angular cli installed, so you can start. > npm install -g some OS you might need to add sudo at the beginning for the last 2 install lines. First install all required packages: > pnpm install To help building the different parts we now rely on gulp and some preset scripts, so all you need to do is call gulp with the wanted action. Also the build system was completely replaced by the current ng builder for angular. The code was updated from Angular 2 to Angular 7. Starting with release 0.91.0 we did a big update to touchscreen frontend code and structure. Then download and unzip them.ĭownload the sources for 0.91.1 and 0.91.2ĭownload the sources for 0.86.2 Compile Version 0.91.0 or newer Make sure they are installed in reachable over your path variable. The build system uses NodeJS and pnpm (yarn up to 1.4.4) / ng / gulp to compile the sources. To change download info for updates, shadow directory and name it would To achieve this add your custom config override script.įor linux this would be /var/lib/RepetierServer/database/RepetierServer.xmlįor other os use the according storage directory. This encapsulated version installs first you adapted shadow system data and then runs the original installer from our server. So you should not deliver the original server version to client but an encapsulated version. With every update from us there is the possibility that we introduce new features or css rules that are required. Copy the modified version into the shadow Also this is possible you should be aware or one drawback of this concept. To allow vendors to deliver printers with their own ideas on what a frontend should contain and look like we publish these original sources.
0 Comments
Leave a Reply. |