Edgewall Software

Changes between Version 10 and Version 11 of TracIdeas


Ignore:
Timestamp:
Jan 11, 2015, 3:30:04 PM (7 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracIdeas

    v10 v11  
    33Organized by topics, this is a new //free for all// discussion area in the Trac wiki. Typically, these pages should collect **short**, **precise** and **actionable** items, a bit like a giant structured !TODO list.
    44
    5 If you notice typos in the code, a glitch in the CSS, an annoying behavior ... but don't feel this is worth creating a ticket, then this is the place!
     5If you notice typos in the code, a glitch in the CSS, an annoying behavior, but don't feel this is worth creating a ticket, then this is the place!
    66
    77 - [./DefaultTheme] -- all things about the CSS and the default layout
    88 - [./TracAttachments] -- how to improve the attachments feature
    99 - [./TracBrowser] -- how to improve the Trac source browser
    10  - [./TracChangeset] -- ... the changeset view, diffs, etc.
     10 - [./TracChangeset] -- how to improve the changeset view, diffs, etc.
    1111 - [./TracTickets] -- ideas for the single ticket view and edit
    12  - [./TracQuery] -- ideas for the custom query view, batch edit, TicketQuery macro...
     12 - [./TracQuery] -- ideas for the custom query view, batch edit, TicketQuery macro, etc.
    1313 - [./TracWiki] -- ideas for the Wiki, WikiFormatting, TracLinks
    1414 - [./TracSearch] -- ideas for improving the search
     
    1717\\\\
    1818----
    19 Note: //the TracDev/ScratchPad pages are similar in intent in such that they try to address sub-systems as a whole instead of focusing on a particular issue like we usually do in a single ticket, but they are more **developer** oriented. They are better used for discussing technicalities, how to refactor the code for greater flexibility or performance, or write API proposals, etc.//
     19Note: //the TracDev/ScratchPad pages are similar in such that they try to address sub-systems as a whole instead of focusing on a particular issue like we usually do in a single ticket, but they are more **developer** oriented. They are better used for discussing technicalities, how to refactor the code for greater flexibility or performance, or write API proposals, etc.//
    2020
    21 //By contrast, the present !TracIdeas/ pages are really meant to collect constructive feedback **from the users** (or from the developers with their user hat on!)//
     21//By contrast, the present !TracIdeas/ pages are meant to collect constructive feedback **from the users** or from the developers with their user hat on!//