Making an important design decision
Making an important design decision
- Subject: Making an important design decision
- From: Gustavo Pizano <email@hidden>
- Date: Tue, 11 Aug 2009 09:49:08 +0200
Hello all.
Well, today my new assigment came, I need to create a Bug report system, as the name implies, to report bugs view "tickets" and to display the responses from the admins. We know there is something out there that does this already, but here they want to have their propertary application.
Anyway, the thing is that right now I have to do it for a specific area of reports, but in the future they want to extend it to more areas and companies, which have diferent requests, or bugs, ..
So Im thinking in how to achieve this,.. I want it be as modular as possible, so I can reuse my components in any "bug reporter" project. So I was thinking maybe a framework with the basic operation? knowing that normally al the reports have the same structure, like date, name, area, and so on. (I must sit down and design that), so when implementing for another area, I just need to make another layout, (html) /..
So i dunno what's your advise?
thanks
Gustavo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden