Thoughts on PlanView architecture

This page is not yet a definitive architecture reference on PlanView. As such it is a stream of consciousness about the architecture. Possible work items are identified for all platforms.

• Pull in minimal AGTEK_Lib stuff, avoid SmartSuite package
• Avoid Android features which are deprecated in Android 4.0
• Access API must be identical (if possible) to all existing C++ implementation.
• Source project (Android and IOS) to be tracked in SVN.

• AGTEK_Lib will require some refactorization
  • Refactor graphics, be more app family agnostics (no com.agtek.smartsuite)
  • Remove layer objects from AGTEK_Lib: direct from memory model to OpenGLGraphicCachedObject lists
  • ADF Reader/Writer need to be isolated from Smartsuite (particularly com.agtek.smartsuite.model.Project)
• Native trimesh needed to support measure mode.
• May be able to maintain more than one image in memory.
• Action bar at top, new widget, can it handle vertical aspect ratio?

• Google protobuf can be integrated, see here: http://stackoverflow.com/questions/10277576/google-protocol-buffers-on-ios
• AI: Find SVN plug in for XCode.
• AT: Discover how to intermingle C++ and Objective C.
• Native trimesh code to be included in IOS app. (share source???)
• AI: Discuss upload issues, need deferred style of connection management, how to do?