Thread: Skin iGO Nextgen from WANDEL™ - author's theme

Skin by WANDEL™

[Only registered and activated users can see links. ]

25.11.2024

Spoiler: LINK

This post requires you to click the "LIKE this post" button and hit F5 to read this content.

Spoiler: AS IS

"As is" means that the author offers and the user uses the product in any condition that currently exists, and that the user accepts the product "with all defects", regardless of whether they are noticeable or not.

Spoiler: Skin Description

• Spoiler: Navigation - as it is

  
  

  General principles for building a navigation system

  
  

  1. Navigation exists primarily as a visual driving guide...not as a couch toy!!!
  2. The driver LOOKES AT THE ROAD while driving, and navigation by voice or sound draws his attention to changes in:
     
     • direction of travel (maneuver)
     • road conditions
     • compliance with the speed limit
     • warns of dangers on the road
     • informs about points of interest
     • and so on
     
     
  3. After a sound alert, the driver "throws" a look at the screen and sees what he needs in the usual place.
     Finger manipulation should be kept to a minimum due to the risk of being distracted from the road.

  
  SO: NAVIGATION SHOULD PREDICTABLY AND INDEPENDENTLY INFORM YOU ABOUT EVERYTHING...OR ALMOST EVERYTHING YOU NEED!!!
  
  Hence the summary:
  

  1. Screen size must be sufficient to accommodate the visual information required at the moment (at least 7 inches)
  2. Sound volume is sufficient to hear alerts.
  3. The location is optimal to see and recognize visual information.
  4. The performance of the tablet should be sufficient to adequately respond and provide all of the above.

  
  
  
• Spoiler: Extra functionality configuration

  
  To work, you will need to install an application LuaInterpreter_v1.3.0_apkpurePlus.com.apk from my set and make initial configuration.
  Once installed, go to the settings of this app in Android settings and give it all permissions.
  
  The iGO.lua file must be configured separately.
  
  

  open Lua folder
  copy iGO.lua to your device
  open it with ES Explore or similar file manager
  open Lua Interpretator
  vertical ellipsis at the top right and open Scripts
  right bottom click add file and create iGO.lua
  copy the contents of the iGO.lua file to ES Explore
  go to Lua Interpretator
  paste the contents into the iGO.lua file created in Lua Interpretator
  save iGO.lua file
  long tap on the file mark it as runable at startup

  Then everything is automatic.
  
  Works with the following packages:
  

  ["com.nng.igoprimoisrael.javaclient"] = "iGO_Israel",
  ["jp.pioneer.mbg.avicsync"] = "iGO_Avic",
  ["za.co.tracks4africa.nng.africa"] = "iGO_Africa",
  ["com.nng.igo.primong.palestine"] = "iGO_Pal",
  ["com.basarsoft.igonextgen.javaclient"] = "iGO_Basar",
  ["com.nng.igo.primong.igoworld"] = "iGO_World",
  ["com.nng.igoprimoluna.javaclient"] = "iGO_Luna",
  ["com.nng.igoprimong.gift"] = "iGO_Gift",
  ["com.nng.igoprimong.nextgen"] = "iGO_NextGen",
• Spoiler: SysChanger.zip

  
  It is allowed to change any sys.txt parameter through the menu.
  Modes by and large TWO:
  Low-level: change anything for anything ... but you are responsible for everything. It goes without saying that you should know the purpose of the parameters... or at least guess what they mean.
  High-level: with hints in the menu. Will be supplemented in the future.
  
• Spoiler: SkinChanger.zip

  
  Skins are placed in the main folder (where the 'ux' folder is located). The folder name is arbitrary. The main thing is that it starts with 'ux', and then your imagination, but without fanaticism
  The name of the main plugin should have the following structure: the_skin<_some alias> (Must be created by the skin author)
  Do not use in the name. ( ) % + - * ? [ ] ^ $
  The best option is ux_wandel, ux_pongo, ux_arimi (of course one of them will be just ux). In the process of work, they will acquire their legal names.
  In all these folders (except mine) you should copy three files from my skin: LuaJava.zip, SkinChanger.zip and SetFileList.zip. They won't hurt the skins.
  
  For each skin, a save will be automatically created and populated.
  sys.txt is shared by everyone, so removing the content in my skin will result in a change for each subsequent one.
  Same thing with the parameters in sys.txt.
  
• Spoiler: ContentChanger.zip

  
  For the utility to work, you will need to create a folder structure in your main content folder (wherever it is located) according to the model from the kit.
  Then you need to either know the parameter assignments in each add.txt, or don't touch anything!!!
  

  1. place in the content/map folder of the HERE map
  2. place in the content/mapTomTom/map folder of the TomTom map
  3. place in the content/mapCarteBlanche/map folder of the CarteBlanche map

  
  
  mapTomTom - as an example, but the folder name structure is exactly the same
  

  • map
  • building
  • poi
  • ...(meaning, etc.)
  • add.txt - configuration file. You can easily recognize its purpose by opening it.

  
  By filling in the content, you get a fully completed content of a specific provider.
  
• Spoiler: Screen mode WITHOUT BUTTONS

  
  This property is adjustable and manifests itself when a certain speed is reached. Then all the buttons disappear on the screen and appear briefly by tapping on their location or automatically when an additional one occurs. information on a button. You can turn off this mode from the cockpit either with a long tap on the button area ... or on the speed at the bottom left.
  
• Spoiler: PANIC button

  
  Please do not do any manipulations with the parameters ... everything is done or will be done programmatically !!! Do not poke anything from the previously described in SYS
  PANIC button:
  If one of the cameras is active and in the field at the bottom left (where the speeds are) the camera button is active ... you can simply long press on it. Same with the left big speedcam button (wandering reward with this later)
  In QUICK_TIP you can display the panic button itself and use it.
  
  The algorithm itself:
  When you press the button, the country of presence turns into a country with a ban on the use of cameras.
  The navigator will reboot with new parameters - no cameras, no buttons ... you're just like a saint ... but driving))
  This means that you will disappear from the screen ... from the configuration ... from the warnings ... only cameras and only for THIS country
  
  You can only return everything manually: go to sys with the editor and delete the tail .... you will recognize it)))
  The code:
  

  Code:

  Please Login or Register to see the links

  
  
• Spoiler: route_from_list.zip

  
  The utility builds a route based on the list copied to the clipboard.
  The route can be built either all at once using all elements...or step by step.
  All this through a button in the cockpit!!!
  A long tap on the corresponding button takes you to instructions
  It is enough to PRELIMINARY somewhere... from any source... select and copy information about Geocoordinates to the clipboard.
  Unfortunately, all this works until version 9 of Android (OS limitations)
  It should look like this:
  
  

  Code:

  Please Login or Register to see the links

  or like this:
  
  

  Code:

  Please Login or Register to see the links

  Google map style coordinates are also possible: "(-?%d+[.,]%d+),%s?(-?%d+[.,]%d+)"
  
  Due to the inability to programmatically use copy/paste for versions of Android 8 and later, I added the ability to use a file for the coordinates of intermediate points and build a route from a list.
  The file should be located in the root of your navigator folder (iGO_Israel) with the name route.txt.
  
  
  

This is an author's theme. You can ask a question or comment on content exclusively related to the changes themselves
Everything else will be sanctioned