https://development.agtek.com/dokuwiki/ 2026-08-10T09:51:10+0000 https://development.agtek.com/dokuwiki/ https://development.agtek.com/dokuwiki/lib/tpl/dokuwiki/images/favicon.ico text/html 2019-10-21T16:00:30+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:agtek_lib_location_manager_architecture&rev=1571673630&do=diff Overview The following pseudo-UML diagram details the basic structure of the LocationManager framework. The LocationManager framework is composed of the following classes: * LocationManager - The main class used by the application/activity * LocationDevice - The abstract class which represents all device descriptors text/html 2013-09-13T15:55:42+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:alignment_flow_diagram&rev=1379087742&do=diff Alignment Flow Diagram This page documents the flow diagram for doing alignments in the Android apps. The BLUE paths are for any app. The GREEN path is for SmartDirt and SmartPlan. The WHITE paths are for SmartGrade and depend on the context: text/html 2013-01-16T00:46:28+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:alignment_methods&rev=1358297188&do=diff Alignment Methods Within the AGTEK Android ecosystem the apps need to provide a means for converting the GPS coordinates Latitude,Longitude,Altitude (LLA) triplet into a Northing,Easting,Elevation (NEZ) Cartesian Coordinates triplet. (Coordinate transformation). text/html 2012-10-10T16:49:17+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_agtek_access_story&rev=1349887757&do=diff Story 1 AGTEK Access has proven so useful that it deserves its own app. Premise AGTEK Access for Android should have all the functionality of the desktop app. (This needs to be qualified some because I'm not sure how practical the upload functionality is independent of an AGTEK program.) The main usage is to download other data like plans, reports, etc. in the field that don't necessarily correspond to AGTEK usage or programs. text/html 2012-10-10T15:53:42+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_agtek_directory_use&rev=1349884422&do=diff On each Android phone,within the SDCARD (regardless of actual root path), the AGTEK SmartSuite set of programs stores data and ACCESS cache files. Also stored are license key encrypted files, the LocationManager list of known device and other pieces of state. This is a short description of the contents of the AGTEK directory: text/html 2012-10-10T07:16:17+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_agtek_lib&rev=1349853377&do=diff Introduction AGTEK Lib (henceforth called “Lib” for keyboard convenience) is a library of code to provide a repository of common functionality for Android and Java applications. While the potential exists for generic Java applications, the focus is currently Android, so using this Library in a generic Java application may require some effort (particularly repackaging, building proper build scripts, etc.) It's also possible that a generic Java platform library needs to exist separately from the … text/html 2019-08-19T18:35:22+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_build_configuration&rev=1566239722&do=diff Android Build Configuration This discusses the process for getting an Android application built for release. It is very cryptic right now, but I wanted to get some of the latest changes to the build process documented somewhere. Android APKs' require versioning and build number information. Each new APK on the Play Store must have a newer build number than previous APK's. This process attempts to somewhat automate this process. It has yet to be completely tested in reality, but it does see… text/html 2019-02-22T18:58:15+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_integration_environment&rev=1550861895&do=diff Android Integration Environment Android uses the Jenkins continuous integration environment to generate all of the builds. Jenkins is configured to watch the Git repositories for changes that trigger new builds in the system. Each product has multiple projects in Jenkins. The projects are grouped into two categories: Development and Release. text/html 2019-09-04T21:46:20+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_project&rev=1567633580&do=diff This page is home for development discussions on the AGTEK Android phone project. The following pages are of interest to developers: SmartDirt SmartDirt Stories Android Architecture SmartDirt Tasks SmartDirt 1.0 Summary SmartDirt Test Plan SmartDirt RTK SmartDirt Stories SmartDirt Test Plan SmartDrone RTK SmartDrone Stories SmartDrone Test Plan SmartGrade SmartGrade (RTK Grade only) SmartGrade Completed Stories SmartGradeTasks SmartGrade Test Plans AGTEK SmartPlan … text/html 2015-03-31T19:08:26+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_studio&rev=1427828906&do=diff Setup Android Studio Development at AGTEK for Android is done using the Android Studio IDE and the Android SDK/NDK packages. You need to download and install the following packages: * Android Studio (current version is 1.10) * Android Native Development Kit, e.g. NDK (current version is 10d) text/html 2018-12-14T01:51:06+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:android_translation_files&rev=1544752266&do=diff Android Translation Files SmartDirt SmartPlan SmartTrack text/html 2017-06-12T18:19:09+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:code_modernization&rev=1497291549&do=diff Code Modernization and NDK refresh Tasks Open Issues Task Number Owner Estimate Actual Status Description Notes 1 text/html 2017-05-05T18:29:25+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:code_modernizaton&rev=1494008965&do=diff Code Modernization and NDK refresh Tasks Open Issues Task Number Owner Estimate Actual Status Description Notes text/html 2018-04-23T18:40:29+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:development_environment&rev=1524508829&do=diff THIS PAGE IS OBSOLETE. MODERN DEVELOPMENT IS RUNNING VIA ANDROID STUDIO, and GIT For development of the Android phone project developers need the following tools: * Eclipse 3.6.1 * Android SDK 2.2 * SVN (on AGTEK machine) * SVN client Development standards text/html 2017-05-09T20:11:40+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:hardware_benchmarking&rev=1494360700&do=diff With the plethora of new devices the ability to benchmark them for numeric comparison seems to be useful. It will also help us document any future optimizations to code like multi-core utilization. Summary Time in seconds, lower is better Phones text/html 2015-12-19T00:52:05+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:hardware_screensizes&rev=1450486325&do=diff It's been difficult to determine how to size various screen elements. As of 2015-12-18 AppBaseActivity.java includes some code to debug log (and set via the crashHelper) the measured, device independent pixel, size of the screen. This page captures those values for future use in determining what screen sized resources should be created. text/html 2016-10-18T14:56:19+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:layer_generalization&rev=1476802579&do=diff Layer Generalization discussion (8-11-16) The Problem * Original layers are line and point oriented (only). -> Base Layer type is insufficiently abstract * Subtyping carries too much base functionality for other types. * Layer identification (AKA LayerEnum) currently SmartSuite/ADF centric. text/html 2017-05-10T16:37:00+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:lpermission_model&rev=1494434220&do=diff Android Permission model (API 23+) The Android permission model changed in API 23. Permissions were divided into Dangerous and Normal. Normal are as before, but Dangerous permissions must be accepted/rejected by the user when the program is first run. Also any Dangerous permission can be revoked at anytime by the user going to the app settings and removing the permission. text/html 2013-05-02T15:08:46+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:progress_topo_flow_diagram&rev=1367507326&do=diff Progress Topo Flow Diagram This page documents the flow diagram for the ProgressTopo mode within SmartGrade. Below is the Flow Diagram: Note: the empty rectangles in the top right represent just a return from the state. They exist as a result of a limitation in the graphical tool used to create the image. text/html 2017-03-02T23:38:15+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:project_class_refactoring&rev=1488497895&do=diff 2017-03-02 Not starting the project, but capturing frustrations for future discussion: * Loading is assumed to be done once, with corresponding alignment. SmartTrack needs to do partial loads, with loads of background file later. * Too much cruft from other applications (SG stuff visible to SmartAnythng else) text/html 2018-04-23T18:41:11+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:setting_up_ndk_to_build_the_library&rev=1524508871&do=diff THIS PAGE IS OBSOLETE, MODERN NDK BUILD IS DONE IN ANDROID STUDIO. The AGTEK Lib project contains native code for the TriMesh. In order to compile and test the library you must add a native “builder” to your Eclipse project. The following instructions are from this web site: text/html 2018-04-23T18:39:30+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:smartdirt_autobuild&rev=1524508770&do=diff THIS PAGE IS OBSOLETE. THE ANDROID BUILD IS MANAGED BY JENKINS RUNNING UNDER USER “build” on dev.agtek.com SmartDirt is built automatically each night on the build machine (dev.agtek.com). These instructions describe the build system as it pertains to the SmartDirt project. Currently the build runs under the account text/html 2013-08-30T19:02:20+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=android:smartsuite_4.0_migration&rev=1377889340&do=diff Migrating 2.3 applications like SmartDirt and SmartGrade require a different interface and the example below attempt to solve the issues of migration and provide an interface pattern for future products. SmartDirt 4.0 Migration screenshots The example below use more optimized layouts for portrait and landscape than 2.3 versions. These are for the phone (Galaxy III). Tablets may require different layouts as well.