[phpBT-dev] MODULES FOR 0.9.0

[Jirka P. <fi...@us...>]

I want to add table for modules, where will stay project_id as primary key =
and columns for use_oses, use_databases, use_environments. These columns wi=
ll stay as options when creating a project.

Maybe it will be better to have only four columns (except primary key) (in =
two tables): project_id, module, module_table_name and module_key_name. We =
will then check every row with corresponing project_id and use modules in t=
hese rows. I'm not sure now, but I think it will be better for future, if w=
e want users to easily create their's own modules. It's easier to add a row=
 than a column to table (and table doesn't have to be off-line when adding =
a row).

Porbably it should be per component not per project, I'm not sure now. I ca=
n easily imagine sombody, who only wants database and environment tracking =
for one component and OS and environment tracking for second component. Wha=
t do you think?

I will give one simple example of TBL_MODULE_OPTIONS and TBL_MODULE:

TBL_MODULE_OPTIONS
------------------
module id; module name; where string
1; 'OS tracking'; '(TBL_OS.os_id =3D TBL_BUG.os_id)'
2; 'Environemnt tracking'; '(TBL_ENVIRONMENT.environment_id =3D TBL_BUG.env=
ironment_id)'
3; Database tracking; '(TBL_DATABASE.database_id =3D TBL_BUG.database_id)'

TBL_MODULE
----------
primary key; component id; module used
1; 4; 1
2; 4; 2
3; 6; 1
4; 6; 3

When we will have table like this one, we will then add at least these chec=
ks:
1. When adding component
2. When editing component
3. When submitting bug
4. When printing out bug list
5. When searching through bugs

We will also need to create an interface for creating new tables with avail=
able value for module and adding rows to TBL_MODULE_OPTIONS.

Imagine that admin will have checkboxes for all of these modules, so (s)he =
will check e.g. use_oses only, when adding a project. Then each bug submitt=
ed by user for this project will have to have OS filled. Otherwise not. And=
 admin will be also able to add new module by simply adding one table (fill=
ed with available values) and one row to TBL_MODULE_OPTIONS.

I don't know if my idea can be realized with templates and if it can be, I =
don't know exactly how. Most probably, I will need your helping hand, Ben, =
because we will probably need to create an ultimate interface, eh ...

Please, think about it deeply, imagine it everything thoroughly and tell me=
 if I'm "too forward thinking" or if we can do it some other way, because I=
'm sometimes thinking at least two steps prior to the Epoch.

Jirka

P.S.: Sorry for my english, it's not good, but I'm working on learning it b=
etter. Please tell me when I'm saying something wrong.