in theory, keeping the javascript objects directly in the cache is a good thing. any instances of, for example, portals on the map, will share the data objects with those in the cache, limiting the overheads for cached items in use however, in practice - relatively large and complex data structures for cached data. and as some items expired from the cache may have data in live portals, etc, complex for garbage collection to clean up. strings, on the other hand - one single object to clean, zero references from anything else - the cache is used as an alternative to network requests. therefore the extra time to encode/parse the strings is no real issue - lower memory overheads? it's liekly a single string is more efficient on RAM use, even taking into account that some objects will be both encoded in the string, and duplicated in live entities on the map time will tell if this is better or worse than direct object storage...
ingress intel total conversion (IITC)
Since the breunigs IITC branch was deleted, I've created this one to continue some development.
Users
Just want to download/install IITC? Go to http://iitc.jonatkins.com/
For keeping up with the latest news, release announcements, etc, Follow IITC on G+ https://plus.google.com/105383756361375410867/posts
If you have questions, need help or advice with IITC, the Google+ community is a good place to start. https://plus.google.com/communities/105647403088015055797
Want to report a bug? Post it to the issues page https://github.com/jonatkins/ingress-intel-total-conversion/issues
Developers
This Github page is for those interested in developing IITC further.
Quickstart
To build the browser scripts from source you will need Python (either a late version 2.x, or 3.0+). It should build correctly on Linux and Windows (and, probably, Macs, FreeBSD, etc)
Fork this project, clone to your local machine.
Run the build.py local
script to build the code.
If all goes well, output of the build will end up in build/local
subfolder.
You can create a custom build settings file, localbuildsettings.py
- look in the supplied
buildsettings.py
for details.
Mobile
To build the mobile app, along with python, you will need
- The Java JDK (development kit - the runtime JRE is not enough)
- The Android SDK
Run ``build.py mobile``` to build IITC Mobile in debug mode.
Note that part of the build.py process includes copying the IITC script files into the mobile/res
subfolder.
If this isn't done (e.g. you build IITC Mobile directly from Eclipse) you will end up with a broken build.