Bug Field Scheme Templates

[Tosh, Michael J]

While I can't speak for the developers, I'd like to suggest that you
look at it like a full template skin.

template/<lang>/skins/<skinname>/<template_struct>

Where if the product uses a skin, attempt to load the skin's template
first, and if it isn't there, use the
template/<lang>/default/<template_struct> instead.

 

-----Original Message-----
From: dev-apps-bugzilla-bounces at lists.mozilla.org
[mailto:dev-apps-bugzilla-bounces at lists.mozilla.org] On Behalf Of
Benton, Kevin
Sent: Thursday, November 15, 2007 12:46 PM
To: developers at bugzilla.org
Subject: Bug Field Scheme Templates

In order to ask my question, I need to give a little background:

 

AMD is in the process of coding "bug field schemes" - the ability to
make a list of fields that are available by product.  An installation
will have the ability to have several field schemes, each of which can
be used by multiple products allowing product owners to determine the
set of fields that make the most sense for that product.  To facilitate
that, we're looking into how we extend the templating system so that it
knows where to find the appropriate template for the given product.

 

The question is, what is the best way to add field schemes into the
template directory structure?  We're considering the following:

 

template/en/default/bug/fs_<id>/...

 

or

 

template/en/field_scheme/fs_<id>/...

 

Considering that this code may get contributed back to the community
(notwithstanding what others may already be doing), what is most likely
to be accepted at this point?  I ask because we are committed to
completing our own field scheme implementation before month end and I'd
like it to be as close to "acceptable" to the community at large as
possible.

 

Kevin


Kevin Benton
MySQL DBA #5739
Senior Software Developer
CAD Global Infrastructure Flow Services
Advanced Micro Devices
2950 E Harmony Rd
Fort Collins, CO  80528

 

The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

 

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla