On Wed, Mar 29, 2006 at 07:25:58PM +0200, Christian Boos wrote: > 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
Ah, interesting. For my 2c I think everything that can be Wiki formatted should be. That way users aren't left wondering "is this thing formatted or not?". Reduce ambiguity. Generated fields like drop-downs may be a different case (but I don't think they should be ;)). But, it's simple enough to change. I can just add a "plaintext=True" arg to any of the fields in [1]. Another alternative is to make this customisable. Thoughts? It would be very useful to have a Wiki formatted component display on TracHacks. > ... 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) Aha yes, this is much more intuitive IMO. The only minor nit is that changes to the ticket applied by the action controller don't get reflected, as the action is not applied until after preview. Not a big deal, but one to be aware of. > Also, what do you think of my suggested "Search for similar tickets" > feature (#1069) ? I think this sounds very, very interesting. I think I saw you mention it a while back, but had subsequently forgotten. I'll take a look today :) As an aside, the proposed ticket spam control could easily be implemented using ITicketManipulator.validate_ticket(). Alec [1] http://projects.edgewall.com/trac/browser/sandbox/workflow/trac/ticket/api.py#L281 -- Evolution: Taking care of those too stupid to take care of themselves. _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
