Opened 9 years ago

Last modified 9 years ago

#1157 new defect/bug

split up xml for easy development for multiple screen sizes

Reported by: ah be Owned by: KaZeR
Priority: major Milestone: version 0.6.0
Component: core Version: git master
Severity: Keywords: xml, style, osd, map, i18n, setup, install, openmoko


I currently have a freerunner 640x480, a Archos G9 1024x768 and a Galaxy Duos with 320x240 screen sizes. so each and everyone has a best fitted layout for all the buttons (and in the future maybe even the road width rendering).

What would be easiest for layout + map development would be to do this all locally on a desktop computer and then transfer the final optimized layout as an navit.xml to the phone. The problem is that the standard android xml doensn't run on my desktop as it requires android libraries.

therefore my suggestion: split up the navit.xml into a

  • libraries part
  • a menu part
  • a speech part
  • a gps vehicle part
  • a map part

in this way I could only grab the menu + the map part and adjust each one on my desktop before uploading to the specific devices.

the hope would be that in this way we gain more people developing skins and map layouts to make navit even more attractive

ps: please keep up the builds for the freerunner, it is very much appreciated!!!

Change History (2)

comment:1 Changed 9 years ago by usul

  • Keywords xml style osd map i18n setup install openmoko added
  • Milestone set to version 0.6.0

I think this is a dupe as it was requested multiple times before, but I don't find any active ticket anymore :/

So we currently discuss the way how we can splitup and merge this sections again. This isn't trivial, as some settings should be able to inherite and other needs to be patched in minor settings (for example for localized map styles). Would be great to see your opinions in the forum :)

Concerning the display dimensions, we think about more dynamical resize features for OSD (as containers like most layout managers use). In the long run, Navit should be able to detect your platform and apply wise defaults.

To attract artists, we need some more comfort features (packaging incl. ressources, in-app download manager, template repository, ...) so I guess this is possible only in the (very) long run.

So this will take some more time and as it will somehow break the compatibility, I schedule it for the next major release.

BTW: We need maintainers for every port. This includes developments but also maintaining packages and doing testing.

comment:2 Changed 9 years ago by ah be

navit for armv4t is being tested every two days ;-) and works like a charme!

Note: See TracTickets for help on using tickets.