• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.
it would be nice if the bug form made more efficient use of screen realestate. the attached sample is one idea about how to do that (it combine values and explanations into single rows)
Other WBNIF enhancements using css (not shown in example):
  • set background colour of mandatory inputs
  • set width of inputs in left column to match each other
  • vartical align the bold heading text in each cell (to match inputs)

MW

I suggest to remove the "Details" from the form and put it into the main text body. The diffs do not work nice with multiline form fields since they are stored as single lines. Text in the main body is better for diffs and can be edited in WYSIWYG.

I also find it hard to read the tiny font in the form. Why not use the same size as the default text?

PTh

Text being better in the body that in a text area in a form is a bug. there is not supposed to be a difference between the two as far as the user is concerned (there were reasons why I did it, but i'll have to go back to my design notes to elaborate.

so please, don't change the data store because you have a valid UI issue.

SD

There are bigger things that need to change. The Codev and Bugs web duality is an issue that needs to be resolved. I find the Bugs web a nice tracking feature, but this duality is messy.

PTh

yes, we agree there is a problem wrt the web duality. Codev has too many dead topics, and the Bugs web has too many discussion points. we need to figure ou the discuplins necessary to use the Bugs system only for definate work items that can then be actioned, while Codev is the place to discuss ideas. (which means that this bug should be closed/defered and pushed to Codev).

one problem is that this web has been very useful as a test of the new codebase - we need to have a reason for developers to activly use the new code together, while twiki.org needs to be a showcase for the existing release.

SD


deferred to TWiki:Codev.EdinburghRelease as one of the first things to do in each release is to review previous development practices. -- WN

Undeferred, post Dakar CC


Reckon the form is OK now. Closing.

CC

ItemTemplate
Summary towards a nicer bug form
ReportedBy MattWilkie
Codebase

SVN Range

AppliesTo Engine
Component BugDatabase
Priority Enhancement
CurrentState Closed
WaitingFor

Checkins

TargetRelease major
ReleasedIn

Topic attachments
I Attachment History Action Size Date Who Comment
HTMLhtm edit-bug-form.htm r0 manage 21.8 K 2005-10-06 - 00:06 MattWilkie example of redesigned form
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 2007-04-23 - CrawfordCurrie
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback