Hi,
is it possible to have some common stuff for cetain devices in a common directory and specific things for a part of these devices in another directory? If yes, how has to look like such a jungle file?
Hi,
is it possible to have some common stuff for cetain devices in a common directory and specific things for a part of these devices in another directory? If yes, how has to look like such a jungle file?
You mean like this?
srcBase=source resBase=resources #no maps base.sourcePath=$(srcBase);source-nomaps base.resourcePath=$(resBase) #maps fenix5x.sourcePath = $(srcBase);source-maps fenix5x.resourcePath = $(resBase);resources-maps
Common code is in "source"
code for devices without native maps is in source-nomaps, and for those with native maps in source-maps. Extra resources for devices with maps is in resources-maps
Hi Jim,
after thinking about this, this is not what I need. I have some code valid for all devices. Then I have code e. g. for 240x240 devices. Finally I have some code for the newer 240x240 devices e. g. the fr945 since they have more memory. But I don't want to duplicate the code in the 240x240 directory since then I have to maintain duplicates.
In a nutshell, I want to reuse for the fr945 the code of the 240x240 devices as well as all other devices. How is this possible?
combine inheritance and jungles, I wrote a blog post about this: https://developer.garmin.com/index.php/blog/post/pro-tip-tackling-connect-iq-versions-screen-shapes-and-memory-limitations
Hi Peter,
this is the article all my apps with a jungle file are based on. But to be honest I have in every widget I used this just one extension ending up with an easy to handle jungle file. In your article the jungle file shows also just one layer. Could you share please how a jungle file looks like if you are using the 4 hardcore layers? Would be nice. Thanks for sharing in advance.
the last part of the article "Connect IQ Version Compatibility" demonstrates how to do it with 3 layers