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".
  • TracSupport (diff) – Opus Project
    Added Removed Modified TracSupport v1 v1 1 Trac Support 2 3 Like in most http www opensource org open source projects free Trac support is available primarily through the community itself mainly through the trac MailingList mailing list and the project wiki 4 5 There is also an trac IrcChannel IRC channel where people might be able to help out Much of the live development discussions also happen there 6 7 Before you start a new support query make sure you ve done the appropriate searching 8 in the project s trac TracFaq FAQ 9 in past messages to the Trac http blog gmane org gmane comp version control subversion trac general set user css http 3A 2F 2Fwww edgewall com 2Fcss 2Fgmane css do set user css t Mailing List 10 in the Trac ticket system using either a http trac edgewall org search q ticket on wiki on full search or a http trac edgewall org query summary keywords ticket query 11 12 Please don t create a ticket in this Trac for asking a support question about Trac Only use it when you face a real and new bug in Trac and do so only after having

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


  • TracSyntaxColoring (diff) – Opus Project
    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 http trac edgewall org wiki SilverCityAddLanguage SilverCityAddLanguage for some information how 24 25 About Pygments 26 27 Starting with trac 0 11 http pygments org pygments will be the new default highlighter It s a highlighting library implemented in pure python very fast easy to extend and http pygments org docs well documented While it does not support as many languages as Enscript or Scintilla the overall output quality is much better 28 29 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 http trac hacks org wiki TracPygmentsPlugin TracPygmentsPlugin from trac hacks If you encounter any bugs please file tickets regarding Pygments in http dev pocoo org projects pygments the pygments trac 30 31 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 http pygments org docs lexers supported lexers on the pygments webpage 32 33 34 Syntax Coloring Support 35 36 SilverCity Enscript Pygments 37 Ada X 38 Asm X 39 Apache Conf htaccess X 40 ASP X X 41 C X X X 42 C X 2 X 43 C X X X 44 Java X 4 X X 45 Awk X 46 Boo X 47 CSS X X 48 Python Doctests X 49 Diff X X 50 Eiffel X 51 Elisp X 52 Fortran X 3 53 Haskell X X 54 Genshi X 55 HTML X

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

  • TracTickets (diff) – Opus Project
    to the point 33 34 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 wiki TracAdmin trac admin 35 36 Note the trac TicketTypes type trac TicketComponent component version priority and severity fields can be managed with wiki TracAdmin trac admin or with the trac WebAdmin WebAdmin plugin 37 38 Note Description of the builtin priority values is available at trac TicketTypes Whyistheseverityfieldgone TicketTypes 39 40 Changing and Commenting Tickets 41 42 Once a ticket has been entered into Trac you can at any time change the 43 information by annotating the bug This means changes and comments to 44 the ticket are logged as a part of the ticket itself 45 46 When viewing a ticket the history of changes will appear below the main ticket area 47 48 In the Trac project we use ticket comments to discuss issues and tasks This makes 49 understanding the motivation behind a design or implementation choice easier 50 when returning to it later 51 52 Note An important feature is being able to use TracLinks and 53 WikiFormatting in ticket descriptions and comments Use TracLinks to refer to 54 other issues changesets or files to make your ticket more specific and easier 55 to understand 56 57 Note See TracNotification for how to configure email notifications of ticket changes 58 59 Note See TracWorkflow for information about the state transitions ticket lifecycle and how this workflow can be customized 60 61 Default Values for Drop Down Fields 62 63 The option selected by default for the various drop down fields can be set in wiki TracIni trac ini in the ticket section 64 65 66 67 68 default component Name of the component selected by default 69 default milestone Name of the default milestone 70 default priority Default priority value 71 default severity Default severity value 72 default type Default ticket type 73 default version Name of the default version 74 75 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 76 77 78 Hiding Fields and Adding Custom Fields 79 80 Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through wiki TracAdmin trac admin This of course only applies to drop down fields such as type priority severity component version and milestone 81 82 Trac also lets you add your own custom ticket fields See TracTicketsCustomFields for more information

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

  • TracTicketsCustomFields (diff) – Opus Project
    of the values from options 34 order Sort order placement 35 textarea Multi line text area 36 label Descriptive label 37 value Default text 38 cols Width in columns 39 rows Height in lines 40 order Sort order placement 41 format Either plain for plain text or wiki to interpret the content as WikiFormatting since 0 11 3 42 43 Sample Config 44 45 ticket custom 46 47 test one text 48 test one label Just a text box 49 50 test two text 51 test two label Another text box 52 test two value Default mailto joe nospam com owner 53 test two format wiki 54 55 test three checkbox 56 test three label Some checkbox 57 test three value 1 58 59 test four select 60 test four label My selectbox 61 test four options one two third option four 62 test four value two 63 64 test five radio 65 test five label Radio buttons are fun 66 test five options uno dos tres cuatro cinco 67 test five value dos 68 69 test six textarea 70 test six label This is a large textarea 71 test six value Default text 72 test six cols 60 73 test six rows 30 74 75 76 Note To make entering an option for a select type field optional specify a leading in the fieldname options option 77 78 Reports Involving Custom Fields 79 80 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 81 82 83 sql 84 SELECT p value AS color 85 id AS ticket summary owner c value AS progress 86 FROM ticket t enum p ticket custom c 87 WHERE status IN assigned AND t id c ticket AND c name progress 88 AND p name t priority AND p type priority 89 ORDER BY p value 90 91 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 92 93 However if you want to show all ticket entries with progress defined and without you need to use a JOIN for every custom field that is in the query 94 95 sql 96 SELECT p value AS color 97 id AS ticket summary component version milestone severity 98 CASE status WHEN assigned THEN owner ELSE owner END AS owner 99 time AS created 100 changetime AS changetime description AS description 101 reporter AS

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

  • TracUnicode (diff) – Opus Project
    15 You can use http www gnu org software libiconv documentation libiconv iconv 1 html iconv to convert the dump 16 17 18 Examples 19 20 Arabic 21 تراك يقوم بحفظ كل الكلمات باستخدام صيغة UTF 8 بما في ذلك الكلمات المستخدمة في صفحات التيكت والويكي 22 23 Bulgarian 24 Българският език работи ли 25 26 Česky 27 Čeština v kódování UTF 8 žádný problém 28 29 Chinese 30 Traditional 繁體中文 漢字測試 Simplified 简体中文 汉字测试 31 32 Croatian 33 Ako podržava srpski i slovenski mora podržavati i Hrvatski čćžšđ ČĆŽŠĐ 34 35 English 36 Yes indeed Trac supports English Fully 37 38 Français 39 Il est possible d écrire en Français à ç û 40 41 German 42 Trac Wiki muß auch deutsche Umlaute richtig anzeigen ö ä ü Ä Ö Ü und das scharfe ß 43 44 Greek 45 Τα Ελληνικά υποστηρίζονται επαρκώς επίσης 46 47 Hebrew 48 אני יכול לאכול זכוכית וזה לא מזיק לי 49 50 Hindi 51 अब ह न द म 52 53 Hungarian 54 Árvíztűrő tükörfúrógép 55 56 Icelandic 57 Ævar sagði við ömmu sína Sjáðu hvað ég er stór 58 59 Japanese 60 漢字 ひらがな カタカナ ハンカクカナ 日本語試験 61 62 Korean 63 이번에는 한글로 써보겠습니다 잘 보이나요 한글 64 65 Latvian 66 67 Latviešu valoda arī strādā 68 69 Lithuanian 70 Sudalyvaukime ir mes Ar veikia lietuviškos raidės ąčęėįšųūž ĄČĘĖĮŠŲŪŽ Žinoma kad veikia 71 Kas tie mes 72 73 Persian Farsi 74 این یک متن فارسی است ولی امکان نوشتن مستقیم فارسی نیست چون حالت متن از راست به چپ و جود ندارد برای فارسی نوشتن باید از HTML استفاده کنید 75 76 html 77 div dir rtl 78 79 این نمونه یک متن از راست به چپ فارسی است که در HTML نوشته شده تا اعداد 12345 و حروف لاتین ABCDEF در

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

  • TracUpgrade (diff) – Opus Project
    found in a directory called share trac the exact location depends on your platform 25 26 This cleanup is not mandatory but it makes it easier to troubleshoot issues later on as you won t waste your time looking at code or templates from a previous release that are not being used anymore As usual make a backup before actually deleting things 27 28 If you had the webadmin plugin installed you can now uninstall it as it is now part of the Trac code base 29 30 Upgrade the Trac Environment 31 32 After restarting Trac should show the instances which need a manual upgrade via the automated upgrade scripts to ease the pain These scripts are run via TracAdmin trac admin 33 34 trac admin path to projenv upgrade 35 36 37 This command will do nothing if the environment is already up to date 38 39 Note that if you are using a PostgreSQL database this command will fail with the message that the environment can only be backed up when you use an SQLite database This means that you will have to backup the repository and the database manually Then to perform the actual upgrade run 40 41 trac admin path to projenv upgrade no backup 42 43 44 If you are using custom CSS styles or modified templates in the templates directory of the TracEnvironment you will need to convert them to the Genshi way of doing things To continue to use your style sheet follow the instructions at TracInterfaceCustomization SiteAppearance 45 46 Update the Trac Documentation 47 48 Every TracEnvironment Trac environment includes a copy of the Trac documentation for the installed version As you probably want to keep the included documentation in sync with the installed version of Trac TracAdmin trac admin provides a command to upgrade the documentation 49 50 trac admin path to projenv wiki upgrade 51 52 53 Note that this procedure will of course leave your WikiStart page intact 54 55 Site Templates 56 The templating engine has changed in 0 11 please look at TracInterfaceCustomization for more information 57 58 Trac Macros Plugins 59 The Trac macros will need to be adapted as the old style wiki macros are not supported anymore due to the drop of trac ClearSilver ClearSilver and the HDF they need to be converted to the new style macros see WikiMacros When they are converted to the new style they need to be placed into the plugins directory instead and not wiki macros which is no longer scanned for macros or plugins 60 61 For CGI users 62 63 For those who run Trac under the CGI environment run this command in order to obtain the trac cgi file 64 65 trac admin path to env deploy deploy directory path 66 67 68 This will create a deploy directory with the following two subdirectories cgi bin and htdocs Then update your Apache configuration file httpd conf with this new trac cgi location and htdocs

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

  • TracWiki (diff) – Opus Project
    built in wiki engine used for text and documentation throughout the system WikiFormatting is used in wiki TitleIndex wiki pages wiki TracTickets tickets and wiki TracChangeset check in log messages This allows for formatted text and hyperlinks in and between all Trac modules 5 6 Editing wiki text is easy using any web browser and a simple WikiFormatting 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 wiki WikiHtml HTML wiki WikiRestructuredText reStructuredText and http www textism com tools textile Textile as alternative markup formats 7 8 The main goal of the wiki is to make editing text easier and encourage people to contribute and annotate text content for a project 9 10 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 11 12 For more help on editing wiki text see these pages 13 WikiFormatting

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

  • TracWorkflow (diff) – Opus Project
    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 83 If not specified for an action default is 0 The value may be negative 84 85 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 86 87 While creating or modifying a ticket workfow contrib workflow workflow parser py may be useful It can create dot files that http www graphviz org GraphViz understands to provide a visual description of the workflow 88 89 This can be done as follows your install path may be different 90 91 cd var local trac devel contrib workflow 92 sudo showworkflow srv trac PlannerSuite conf trac ini 93 94 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 95 96 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 97 98 Example Adding optional Testing with Workflow 99 100 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 101 102 103 testing new accepted needs work assigned reopened testing 104 testing name Submit to reporter for testing 105 testing permissions TICKET MODIFY 106 107 reject testing needs work 108 reject name Failed testing return to developer 109 110 pass testing closed 111 pass name Passes Testing 112 pass operations set resolution 113 pass set resolution fixed 114 115 116 Example Add simple optional generic review state 117 118 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

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