Alec Thomas wrote:
Hi all,
This is a mail in two parts. Firstly, a request that anybody using
workflow [1] update to the latest version to test the new unified ticket
module (see below for more info). There are still a few kinks to work
out and testers would be invaluable. If you have inserted custom ticket
states into the 'enum' table you will have to remove them before the
upgrade.
The second part of this mail is an update on the current state. There
has been a lot of progress over the last week or so, here's a quick
summary of what has been changed/added:
- web_ui.TicketModule and web_ui.NewticketModule have both been merged
into web_ui.UnifiedTicketModule. Consequently, ticket.cs is used
both when creating and when modifying tickets. Additionally, this
means that when you preview during ticket creation, you get an
actual preview. newticket.cs will disappear soon.
Superb job here!
Time to remove the web_ui.TicketModule and web_ui.NewticketModule ?
Just for the sake of this simplification, I'd like to have the WorkFlow
merged :)
- Inline field validation errors are displayed. Best shown with an
image [2].
Also very cool.
- Added the ITicketEnumContributor interface. This lets plugins
provide additional ticket states, versions, etc. without having to
modify the database. The reasoning behind this is that it is
relatively easy to add new states, versions, etc. by adding them
during environment setup/upgrade, but then they exist even if the
plugin is removed. This allows the enumerated values to exist only
for the lifetime of the plugin.
- Most field controls, values and labels are rendered by
trac.ticket.field.Field subclasses. There are still some static
fields defined in ticket.cs, but I hope to remove this soon.
About field rendering: the summary is not a plaintext field.
While I personally feel it's better like that (you know my Wiki
everywhere bias :) ),
be aware that this is not (yet?) the consensus... See #1888
- Added api.BuiltinFieldProvider and api.CustomFieldProvider. These
classes provide the builtin and custom fields and field types, via
the new API.
- Ticket states defined via [ticket-status] [3] are now automatically
added via ITicketEnumContributor. This lets queries work correctly,
but will require anybody who added values manually to the enum table
to remove them. It also closes #2898 and #2941.
... and something I wanted to request was actually implemented
before I had a chance to write this mail (#2460)
(except I noticed the owner or status or resolution property changes
are not previewed like the other properties are)
Also, what do you think of my suggested "Search for similar tickets"
feature (#1069) ?
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
