archive-fr.com » FR » O » OPUS-PROJECT.FR

Total: 702

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • TracReports – Opus Project
    Formats Aside from the default HTML view reports can also be exported in a number of alternative formats At the bottom of the report page you will find a list of available data formats Click the desired link to download the alternative report format Comma delimited CSV Comma Separated Values Export the report as plain text each row on its own line columns separated by a single comma Note Carriage returns line feeds and commas are stripped from column data to preserve the CSV structure Tab delimited Like above but uses tabs t instead of comma RSS XML Content Syndication All reports support syndication using XML RSS 2 0 To subscribe to an RSS feed click the orange XML icon at the bottom of the page See TracRss for general information on RSS support in Trac Creating Custom Reports Creating a custom report requires a comfortable knowledge of SQL A report is basically a single named SQL query executed and presented by Trac Reports can be viewed and created from a custom SQL expression directly in from the web interface Typically a report consists of a SELECT expression from the ticket table using the available columns and sorting the way you want it Ticket columns The ticket table has the following columns id type time changetime component severity priority owner reporter cc version milestone status resolution summary description keywords See TracTickets for a detailed description of the column fields all active tickets sorted by priority and time Example All active tickets sorted by priority and time SELECT id AS ticket status severity priority owner time as created summary FROM ticket WHERE status IN new assigned reopened ORDER BY priority time Advanced Reports Dynamic Variables For more flexible reports Trac supports the use of dynamic variables in report SQL statements In short dynamic variables are special strings that are replaced by custom data before query execution Using Variables in a Query The syntax for dynamic variables is simple any upper case word beginning with is considered a variable Example SELECT id AS ticket summary FROM ticket WHERE priority PRIORITY To assign a value to Example http trac edgewall org reports 14 PRIORITY high To use multiple variables separate them with an Example http trac edgewall org reports 14 PRIORITY high SEVERITY critical Special Constant Variables There is one magic dynamic variable to allow practical reports its value automatically set without having to change the URL USER Username of logged in user Example List all tickets assigned to me SELECT id AS ticket summary FROM ticket WHERE owner USER Advanced Reports Custom Formatting Trac is also capable of more advanced reports including custom layouts result grouping and user defined CSS styles To create such reports we ll use specialized SQL statements to control the output of the Trac report engine Special Columns To format reports TracReports looks for magic column names in the query result These magic names are processed and affect the layout and style of the final report Automatically formatted

    Original URL path: http://www.opus-project.fr/trac/wiki/TracReports?version=1 (2016-01-11)
    Open archived version from archive

  • TracNavigation – Opus Project
    to access the default page of the main modules enabled in Trac and accessible for the current user metanav corresponds to the meta navigation bar by default positioned above the main navigation bar and below the Search box It contains the Log in Logout Help Guide etc entries This navigation bar is meant to access some global information about the Trac project and the current user Note that it is

    Original URL path: http://www.opus-project.fr/trac/wiki/TracNavigation?version=1 (2016-01-11)
    Open archived version from archive

  • TracIni – Opus Project
    of additional MIME types known by Enscript For each a tuple mimetype mode quality has to be specified where mimetype is the MIME type mode is the corresponding Enscript mode to be used for the conversion and quality is the quality ratio associated to this conversion That can also be used to override the default quality ratio used by the Enscript render which is 2 since 0 10 enscript path Path to the Enscript executable max preview size Maximum file size for HTML preview since 0 9 mime map List of additional MIME types and keyword mappings Mappings are comma separated and for each MIME type there s a colon separated list of associated keywords or file extensions since 0 10 php path Path to the PHP executable since 0 9 tab width Displayed tab width in file preview since 0 9 notification admit domains Comma separated list of domains that should be considered as valid for email addresses such as localdomain always notify owner Always send notifications to the ticket owner since 0 9 always notify reporter Always send notifications to any address in the reporter field always notify updater Always send notifications to the person who causes the ticket property change ignore domains Comma separated list of domains that should not be considered part of email addresses for usernames with Kerberos domains mime encoding Specifies the MIME encoding scheme for emails Valid options are base64 for Base64 encoding qp for Quoted Printable and none for no encoding Note that the no encoding means that non ASCII characters in text are going to cause problems with notifications since 0 10 smtp always bcc Email address es to always send notifications to addresses do not appear publicly Bcc since 0 10 smtp always cc Email address es to always send notifications to addresses can be seen by all recipients Cc smtp default domain Default host domain to append to address that do not specify one smtp enabled Enable SMTP email notification smtp from Sender address to use in notification emails smtp from name Sender name to use in notification emails smtp password Password for SMTP server since 0 9 smtp port SMTP server port to use for email notification smtp replyto Reply To address to use in notification emails smtp server SMTP server hostname to use for email notifications smtp subject prefix Text to prepend to subject line of notification emails If the setting is not defined then the project name prefix If no prefix is desired then specifying an empty option will disable it since 0 10 1 smtp user Username for SMTP server since 0 9 ticket subject template A Genshi text template snippet used to get the notification subject since 0 11 use public cc Recipients can see email addresses of other CC ed recipients If this option is disabled the default recipients are put on BCC since 0 10 use short addr Permit email address without a host domain i e username only The SMTP server should accept those addresses and either append a FQDN or use local delivery since 0 10 use tls Use SSL TLS to send notifications since 0 10 project admin E Mail address of the project s administrator admin trac url Base URL of a Trac instance where errors in this Trac should be reported This can be an absolute or relative URL or to reference this Trac instance An empty value will disable the reporting buttons since 0 11 3 descr Short description of the project footer Page footer text right aligned icon URL of the icon of the project name Name of the project url URL of the main project web site usually the website in which the base url resides query default anonymous query The default query for anonymous users The query is either in query language syntax or a URL query string starting with as used in query Trac links since 0 11 2 default query The default query for authenticated users The query is either in query language syntax or a URL query string starting with as used in query Trac links since 0 11 2 items per page Number of tickets displayed per page in ticket queries by default since 0 11 report items per page Number of tickets displayed per page in ticket reports by default since 0 11 items per page rss Number of tickets displayed in the rss feeds for reports since 0 11 revisionlog default log limit Default value for the limit argument in the TracRevisionLog since 0 11 roadmap stats provider Name of the component implementing ITicketGroupStatsProvider which is used to collect statistics on groups of tickets for display in the roadmap views search min query length Minimum length of query string allowed when performing a search svn branches List of paths categorized as branches If a path ends with then all the directory entries found below that path will be included tags List of paths categorized as tags If a path ends with then all the directory entries found below that path will be included ticket default cc Default cc list for newly created tickets default component Default component for newly created tickets default description Default description for newly created tickets default keywords Default keywords for newly created tickets default milestone Default milestone for newly created tickets default owner Default owner for newly created tickets default priority Default priority for newly created tickets default resolution Default resolution for resolving closing tickets since 0 11 default severity Default severity for newly created tickets default summary Default summary title for newly created tickets default type Default type for newly created tickets since 0 9 default version Default version for newly created tickets max comment size Don t accept tickets with a too big comment since 0 11 2 max description size Don t accept tickets with a too big description since 0 11 preserve newlines Whether Wiki formatter should respect the new lines present in the Wiki text If set to

    Original URL path: http://www.opus-project.fr/trac/wiki/TracIni?version=1 (2016-01-11)
    Open archived version from archive

  • TracSyntaxColoring – Opus Project
    and isn t executed in an external process About SilverCity SilverCity uses the lexer from Scintilla Scintilla supports more languages than SilverCity implements If you want to add a language to SilverCity supported by Scintilla it s not very difficult See SilverCityAddLanguage for some information how About Pygments Starting with trac 0 11 pygments will be the new default highlighter It s a highlighting library implemented in pure python very fast easy to extend and well documented While it does not support as many languages as Enscript or Scintilla the overall output quality is much better To use pygments in trac 0 11 you just have to install pygments 0 6 or higher pygments default style colorful under mimeviewer options has to be added If you want to use it in trac 0 10 too you have to install the TracPygmentsPlugin from trac hacks If you encounter any bugs please file tickets regarding Pygments in the pygments trac It s very likely that the list below is outdated because the list of supported pygments lexers is growing weekly Just have a look at the page of supported lexers on the pygments webpage Syntax Coloring Support SilverCity Enscript Pygments Ada X Asm X Apache Conf htaccess X ASP X X C X X X C X 2 X C X X X Java X 4 X X Awk X Boo X CSS X X Python Doctests X Diff X X Eiffel X Elisp X Fortran X 3 Haskell X X Genshi X HTML X X X IDL X INI X Javascript X X X Lua X m4 X Makefile X X Mako X Matlab X 5 Mygthy X Objective C X OCaml X Pascal X X Perl X X X PHP X X PSP X Pyrex X Python X X X

    Original URL path: http://www.opus-project.fr/trac/wiki/TracSyntaxColoring?version=1 (2016-01-11)
    Open archived version from archive

  • WikiNewPage – Opus Project
    page See WikiPageNames for naming conventions Edit an existing page or any other resources that support WikiFormatting and add a link to your new page Save your changes Follow the link you created to take you to the new page Trac will display a describe PageName here message Click the Edit this page button to edit and add content to your new page Save your changes All done Your new

    Original URL path: http://www.opus-project.fr/trac/wiki/WikiNewPage?version=1 (2016-01-11)
    Open archived version from archive

  • TracWiki – Opus Project
    Tickets Workflow Roadmap Ticket Queries Reports RSS Support Notification Trac has a built in wiki engine used for text and documentation throughout the system WikiFormatting is used in wiki pages tickets and check in log messages This allows for formatted text and hyperlinks in and between all Trac modules Editing wiki text is easy using any web browser and a simple formatting system rather than more complex markup languages like HTML The reasoning behind its design is that HTML with its large collection of nestable tags is too complicated to allow fast paced editing and distracts from the actual content of the pages Note though that Trac also supports HTML reStructuredText and Textile as alternative markup formats The main goal of the wiki is to make editing text easier and encourage people to contribute and annotate text content for a project The wiki itself does not enforce any structure but rather resembles a stack of empty sheets of paper where you can organize information and documentation as you see fit and later reorganize if necessary For more help on editing wiki text see these pages WikiFormatting WikiPageNames WikiNewPage TracLinks WikiMacros WikiProcessors PageTemplates If you want to practice editing please use

    Original URL path: http://www.opus-project.fr/trac/wiki/TracWiki?version=1 (2016-01-11)
    Open archived version from archive

  • WikiMacros – Opus Project
    configuration options whose section and name start with the filters are output TracGuideToc This macro shows a quick and dirty way to make a table of contents for a set of wiki pages TicketQuery Macro that lists tickets that match certain criteria This macro accepts a comma separated list of keyed parameters in the form key value If the key is the name of a field the value must use the syntax of a filter specifier as defined in TracQuery QueryLanguage Note that this is not the same as the simplified URL syntax used for query links starting with a character In addition to filters several other named parameters can be used to control how the results are presented All of them are optional The format parameter determines how the list of tickets is presented list the default presentation is to list the ticket ID next to the summary with each ticket on a separate line compact the tickets are presented as a comma separated list of ticket IDs count only the count of matching tickets is displayed table a view similar to the custom query view but without the controls The max parameter can be used to limit the number of tickets shown defaults to 0 i e no maximum The order parameter sets the field used for ordering tickets defaults to id The desc parameter indicates whether the order of the tickets should be reversed defaults to false The group parameter sets the field used for grouping tickets defaults to not being set The groupdesc parameter indicates whether the natural display order of the groups should be reversed defaults to false The verbose parameter can be set to a true value in order to get the description for the listed tickets For table format only deprecated in favor of the rows parameter The rows parameter can be used to specify which field s should be viewed as a row e g rows description summary For compatibility with Trac 0 10 if there s a second positional parameter given to the macro it will be used to specify the format Also using as a field separator still works but is deprecated TracAdminHelp Displays help for trac admin commands Examples TracAdminHelp all commands TracAdminHelp wiki all wiki commands TracAdminHelp wiki export the wiki export command TracAdminHelp upgrade the upgrade command WikiCalendar Inserts a small calendar where each day links to a wiki page whose name matches wiki page format The current day is highlighted and days with Milestones are marked in bold This version makes heavy use of CSS for formatting Tested in Firefox 2 0 only Usage WikiCalendar year month show buttons wiki page format Arguments year 4 digit year defaults to current year month 2 digit month defaults to current month show buttons boolean defaults to true wiki page format string defaults to Y m d Examples WikiCalendar 2006 07 WikiCalendar 2006 07 false WikiCalendar true Meeting Y m d WikiCalendar 2006 07 false Meeting Y m d

    Original URL path: http://www.opus-project.fr/trac/wiki/WikiMacros?version=1 (2016-01-11)
    Open archived version from archive

  • TracWorkflow – Opus Project
    in which the actions are displayed is determined by this value The action with the highest default value is listed first and is selected by default The rest of the actions are listed in order of decreasing default values If not specified for an action default is 0 The value may be negative There are a couple of hard coded constraints to the workflow In particular tickets are created with status new and tickets are expected to have a closed state Further the default reports queries treat any state other than closed as an open state While creating or modifying a ticket workfow contrib workflow workflow parser py may be useful It can create dot files that GraphViz understands to provide a visual description of the workflow This can be done as follows your install path may be different cd var local trac devel contrib workflow sudo showworkflow srv trac PlannerSuite conf trac ini And then open up the resulting trac pdf file created by the script it will be in the same directory as the trac ini file After you have changed a workflow you need to restart apache for the changes to take effect This is important because the changes will still show up when you run your script but all the old workflow steps will still be there until the server is restarted Example Adding optional Testing with Workflow By adding the following to your ticket workflow section of trac ini you get optional testing When the ticket is in new accepted or needs work status you can choose to submit it for testing When it s in the testing status the user gets the option to reject it and send it back to needs work or pass the testing and send it along to closed If they accept it then it gets automatically marked as closed and the resolution is set to fixed Since all the old work flow remains a ticket can skip this entire section testing new accepted needs work assigned reopened testing testing name Submit to reporter for testing testing permissions TICKET MODIFY reject testing needs work reject name Failed testing return to developer pass testing closed pass name Passes Testing pass operations set resolution pass set resolution fixed Example Add simple optional generic review state Sometimes Trac is used in situations where testing can mean different things to different people so you may want to create an optional workflow state that is between the default workflow s assigned and closed states but does not impose implementation specific details The only new state you need to add for this is a reviewing state A ticket may then be submitted for review from any state that it can be reassigned If a review passes you can re use the resolve action to close the ticket and if it fails you can re use the reassign action to push it back into the normal workflow The new reviewing state along with its associated review action

    Original URL path: http://www.opus-project.fr/trac/wiki/TracWorkflow?version=1 (2016-01-11)
    Open archived version from archive