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".
  • RecentChanges – Opus Project
    09 Wp4 Wp3 WP2 2 diff WP2 1 Wp2 diff Wp1 Wp0 FurtherObjectives diff ValueGeneration diff CarnetAdresses GuideUtilisation diff Contact diff OT diff R Scos diff Scilab Salome diff Objectifs diff Softia diff UP7 diff UJF diff SUPELEC diff INRIA diff ECP diff EDF diff EADS diff Dassault diff CEA diff 2009 09 28 09 28 09 TracUnicode TracBrowser SandBox TracRevisionLog TitleIndex WikiRestructuredText TracFineGrainedPermissions TracImport TracAccessibility TracBackup TracModPython TracGuide TracTicketsCustomFields

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


  • WikiDeletePage – Opus Project
    at the bottom of the wiki page These buttons are only visible for users with WIKI DELETE permissions Note Deleting a wiki page is an irreversible operation In general it is recommended to create redirection pages instead of completely deleting an old page as to not frustrate the visitor with broken links when coming to the site from a search engine A redirection page is a short page that contains

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

  • WikiProcessors – Opus Project
    style color orange This is raw HTML h1 Results in This is raw HTML Note that since 0 11 such blocks of HTML have to be self contained i e you can t start an HTML element in one block and close it later in a second block Use div or span processors for achieving similar effect see WikiHtml Example 2 inserting Restructured Text in wiki text rst A header This is some text with a footnote This is the footnote Results in A header This is some text with a footnote This is the footnote Example 3 inserting a block of C source code in wiki text c int main int argc char argv printf Hello World n return 0 Results in int main int argc char argv printf Hello World n return 0 Available Processors The following processors are included in the Trac distribution html Insert custom HTML in a wiki page See WikiHtml div Wrap an arbitrary Wiki content in a div element since 0 11 See WikiHtml span Wrap an arbitrary Wiki content in a span element since 0 11 See also WikiHtml rst Trac support for Restructured Text See WikiRestructuredText textile Supported if Textile is installed See a Textile reference comment Do not process the text in this section i e contents exist only in the plain text not in the rendered page Code Highlighting Support Trac includes processors to provide inline syntax highlighting for the following languages c C cpp C python Python perl Perl ruby Ruby php PHP asp ASP java Java js Javascript sql SQL xml XML sh Bourne Bash shell Note Trac relies on external software packages for syntax coloring See TracSyntaxColoring for more info By using the MIME type as processor it is possible to syntax highlight the same languages

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

  • TracLogging – Opus Project
    file specified with the log file option in trac ini stderr Output all log entries to console tracd only syslog UNIX Send all log messages to the local syslogd via named pipe dev log By default syslog will write them to the file var log messages eventlog Windows Use the system s NT Event Log for Trac logging Log Levels The verbosity level of logged messages can be set using the log level option in trac ini The log level defines the minimum level of urgency required for a message to be logged and those levels are CRITICAL Log only the most critical typically fatal errors ERROR Log failures bugs and errors WARN Log warnings non interrupting events INFO Diagnostic information log information about all processing DEBUG Trace messages profiling etc Log Format Starting with Trac 0 10 4 see 2844 it is possible to set the output format for log entries This can be done through the log format option in trac ini The format is a string which can contain any of the Python logging Formatter variables Additonally the following Trac specific variables can be used basename s The last path component of the current environment path s

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

  • TracRss – Opus Project
    results Be notified about important and relevant issue tickets TracBrowser and TracRevisionLog Syndication of file changes Stay up to date with changes to a specific file or directory How to access RSS data Anywhere in Trac where RSS is available you should find a small orange XML icon typically placed at the bottom of the page Clicking the icon will access the RSS feed for that specific resource Note Different modules provide different data in their RSS feeds Usually the syndicated information corresponds to the current view For example if you click the RSS link on a report page the feed will be based on that report It might be explained by thinking of the RSS feeds as an alternate view of the data currently displayed Links http blogs law harvard edu tech rss RSS 2 0 Specification http www mozilla org products firefox Mozilla Firefox supports live bookmarks using RSS http sage mozdev org Sage RSS and Atom feed aggregator for Mozilla Firefox http pim kde org users php KDE RSS Reader for Linux BSD n x systems http www rssreader com Free and powerful RSS Reader for Windows http liferea sourceforge net Open source GTK2 RSS Reader for

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

  • TracTicketsCustomFields – Opus Project
    com owner test two format wiki test three checkbox test three label Some checkbox test three value 1 test four select test four label My selectbox test four options one two third option four test four value two test five radio test five label Radio buttons are fun test five options uno dos tres cuatro cinco test five value dos test six textarea test six label This is a large textarea test six value Default text test six cols 60 test six rows 30 Note To make entering an option for a select type field optional specify a leading in the fieldname options option Reports Involving Custom Fields Custom ticket fields are stored in the ticket custom table not in the ticket table So to display the values from custom fields in a report you will need a join on the 2 tables Let s use an example with a custom ticket field called progress SELECT p value AS color id AS ticket summary owner c value AS progress FROM ticket t enum p ticket custom c WHERE status IN assigned AND t id c ticket AND c name progress AND p name t priority AND p type priority ORDER BY p value Note that this will only show tickets that have progress set in them which is not the same as showing all tickets If you created this custom ticket field after you have already created some tickets they will not have that field defined and thus they will never show up on this ticket query If you go back and modify those tickets the field will be defined and they will appear in the query If that s all you want you re set However if you want to show all ticket entries with progress defined and without

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

  • TracGuide – Opus Project
    meant to serve as a starting point for all documentation regarding Trac usage and development The guide is a free document a collaborative effort and a part of the Trac Project itself Table of Contents Currently available documentation TracGuide This page Documentation starting point Administrator Guide TracInstall How to install and run Trac TracUpgrade How to upgrade existing installations TracAdmin Administering a Trac project TracImport Importing tickets from other bug databases TracIni Trac configuration file reference TracPermissions Access control and permissions TracInterfaceCustomization Customizing the Trac interface TracPlugins Installing and managing Trac extensions TracLogging The Trac logging facility TracNotification Email notification TracWorkflow Configurable Ticket Workflow User Guide TracWiki How to use the built in Wiki TracTimeline The timeline provides a historic perspective on a project TracRss RSS content syndication in Trac The Version Control Subsystem TracBrowser Browsing source code with Trac TracChangeset Viewing changes to source code TracRevisionLog Viewing change history The Ticket Subsystem TracTickets Using the issue tracker TracReports Writing and using reports TracQuery Executing custom ticket queries TracRoadmap The roadmap helps tracking project progress Trac FAQ A collection of Frequently Asked Questions on the project website Support and Other Sources of Information If you are looking for a good

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

  • TracTickets – Opus Project
    invalid wontfix duplicate worksforme Status What is the current status One of new assigned closed reopened Summary A brief description summarizing the problem or issue Description The body of the ticket A good description should be specific descriptive and to the point Note Versions of Trac prior to 0 9 did not have the type field but instead provided a severity field and different default values for the priority field This change was done to simplify the ticket model by removing the somewhat blurry distinction between priority and severity However the old model is still available if you prefer it just add modify the default values of the priority and severity and optionally hide the type field by removing all the possible values through trac admin Note the type component version priority and severity fields can be managed with trac admin or with the WebAdmin plugin Note Description of the builtin priority values is available at TicketTypes Changing and Commenting Tickets Once a ticket has been entered into Trac you can at any time change the information by annotating the bug This means changes and comments to the ticket are logged as a part of the ticket itself When viewing a ticket the history of changes will appear below the main ticket area In the Trac project we use ticket comments to discuss issues and tasks This makes understanding the motivation behind a design or implementation choice easier when returning to it later Note An important feature is being able to use TracLinks and WikiFormatting in ticket descriptions and comments Use TracLinks to refer to other issues changesets or files to make your ticket more specific and easier to understand Note See TracNotification for how to configure email notifications of ticket changes Note See TracWorkflow for information about the state transitions ticket lifecycle and how this workflow can be customized Default Values for Drop Down Fields The option selected by default for the various drop down fields can be set in trac ini in the ticket section default component Name of the component selected by default default milestone Name of the default milestone default priority Default priority value default severity Default severity value default type Default ticket type default version Name of the default version If any of these options are omitted the default value will either be the first in the list or an empty value depending on whether the field in question is required to be set Hiding Fields and Adding Custom Fields Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through trac admin This of course only applies to drop down fields such as type priority severity component version and milestone Trac also lets you add your own custom ticket fields See TracTicketsCustomFields for more information Assign to as Drop Down List If the list of possible ticket owners is finite you can change the assign to ticket field from a text input to

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