https://development.agtek.com/dokuwiki/ 2026-08-09T06:57:27+0000 https://development.agtek.com/dokuwiki/ https://development.agtek.com/dokuwiki/lib/tpl/dokuwiki/images/favicon.ico text/html 2012-10-10T22:38:00+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=programming:agtek_bug_life_cycle&rev=1349908680&do=diff AGTEK Bug Life Cycle This is a proposal for the life cycle of defects in the JTrac system. The following image is a state diagram showing the tracker's lifecycle. It encompasses defects as well as feature suggestions. If we think this is a good idea, all JTrace spaces will be normalilzed to this state diagram. text/html 2017-05-05T18:31:15+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=programming:android_rearchitecture_2016&rev=1494009075&do=diff Areas of concern for rearchitecture discussions Android Object Design Guidelines Android Source Format Guidelines Prio is (mja/bc) * Layer Generalization ( 2 / 1 ) -> 1.5 * Done 2016 * Old model had few instances based on LayerEnum (compile time tags) * Newer model (SmartPlan/TrackManager) needs layers distinguished by runtime tags (names?) text/html 2012-10-10T16:47:04+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=programming:object_oriented_rules_of_thumb&rev=1349887624&do=diff Designing an implementing successful object oriented code is tough because of the variety of situations with which a programmer will find themselves. Often when a coder is trying to code a solution to a problem the question is asked, “what pattern should I use, or what object scheme should I use?