On Sat April 8 2006 13:49, Christian Lohmaier wrote:
> Hi *,
>
> On Sat, Apr 08, 2006 at 10:14:38AM +0100, CPHennessy wrote:
> > On Fri April 7 2006 16:54, Christian Lohmaier wrote:
> > > On Thu, Apr 06, 2006 at 11:52:54PM +0100, CPHennessy wrote:
> >
> > [...]
> >
> > > > 1) choose from : installation, writer, calc, impress, database,
> > > > printing, upgrading, other (e.g. web, other langs, ... ? )
> > > >
> > > > 2) choose version ( latest version being the default - with links to
> > > > download it).
> > >
> > > maintaining that in javascript would be a nightmare anyway.
> >
> > Not necessarily. You could have a script which checks out the file from
> > CVS and updates it if a new release is available, and checks the code
> > back in.
>
> What file would you check out? You cannot get IZ-information from cvs.

But you could write a script to retrieve the HTML of the advance page where 
the component has been preselected.

> > > [...]
> > > would require a way to get a list of valid subcomponents and to choose
> > > a default. While the first part is already not possible, the second one
> > > is even more difficult. Given that there are efforts to add more
> > > subcomponents to ease dispatching of issues to the right developer,
> > > hiding this field would be a step in the opposite direction.
> >
> > Maybe adding a new subcomponent "unknown" is not unreasonable.
>
> It is. It puts more burden on QA. QA can barely cope with the issues
> filed currently. Having more issues that need more time to dispatch is
> counter-productive.

And this I understand. But what is the percentage of issues coming from novice 
users today where the subcomponent is incorrect ?
My guess is that it is reasonably high.

-- 
CPH : openoffice.org contributor

Maybe your question has been answered already?
                                http://user-faq.openoffice.org/#FAQ

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to