Switch the 'modify' code of admin/field.php to use templates
[bugdar.git] / docs / dev_phases_2-0.txt
1 Bugdar PHASES OF DEVELOPMENT
2 ================================================================================
3
4 Because Bugdar 2.0 is a substantial development effort, its progress will be
5 broken into unique, defined stages. No time will be allotted to these stages
6 because this is only to group different phases of development.
7
8 PHASE 1: ISSO CONVERSION
9 ###########################################
10 - Upgrade the infrastructure of Bugdar to use ISSO3
11 - Straight swap-out of ISSO2 components to v3
12 - The 1.2.x series running under ISSO3
13 - Exception of the Admin CP, because the BSPrinter modules are being removed
14
15
16 PHASE 2: PRINTER MODULE SPRINT DEVELOPMENT
17 ###########################################
18 - Remove the ISSO3 Printer modules
19 - Replace with CSS stylesheets that use extremely-semenatic markup
20 - Rewrite the Admin CP to use templates with new stylesheets
21
22
23 PHASE 3: REWRITE LANGUAGE SYSTEM
24 ###########################################
25 - Switch from using Gettext MO files to a database-phrase system
26 - Database system will enable translation of dynamic data (help system, field
27 names, statuses, etc.)
28 - Use phrase groups to prevent loading of all phrases into memory
29 - XML export system
30
31
32 PHASE 4: CORE REFACTORING
33 ###########################################
34 - Refactor core code components to use more API functions to reduce controller
35 code
36 - Make projects more independent, allowing for product-specific custom fields,
37 etc.
38 - Re-envision Bugdar
39
40
41 PHASE 5: NEW FEATURES
42 ###########################################
43 - Add new features from the bug database and planning_2_0.txt
44
45
46 PHASE 6: INTERFACE REDESIGN
47 ###########################################
48 - Redesign interface
49 - AJAX where possible
50