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".
  • TracSyntaxColoring – Opus Project
    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 Ruby X X 1 X Scheme

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


  • TracTickets – Opus Project
    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 a drop down list This is

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

  • TracTicketsCustomFields – Opus Project
    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 you need to use a JOIN

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

  • TracUnicode – Opus Project
    UTF 8 otherwise strange things will happen To convert your database to UTF 8 the easiest way is to dump the database convert the dump into UTF 8 and then import the converted dump back into the database You can use iconv to convert the dump Examples Arabic تراك يقوم بحفظ كل الكلمات باستخدام صيغة UTF 8 بما في ذلك الكلمات المستخدمة في صفحات التيكت والويكي Bulgarian Българският език работи ли Česky Čeština v kódování UTF 8 žádný problém Chinese Traditional 繁體中文 漢字測試 Simplified 简体中文 汉字测试 Croatian Ako podržava srpski i slovenski mora podržavati i Hrvatski čćžšđ ČĆŽŠĐ English Yes indeed Trac supports English Fully Français Il est possible d écrire en Français à ç û German Trac Wiki muß auch deutsche Umlaute richtig anzeigen ö ä ü Ä Ö Ü und das scharfe ß Greek Τα Ελληνικά υποστηρίζονται επαρκώς επίσης Hebrew אני יכול לאכול זכוכית וזה לא מזיק לי Hindi अब ह न द म Hungarian Árvíztűrő tükörfúrógép Icelandic Ævar sagði við ömmu sína Sjáðu hvað ég er stór Japanese 漢字 ひらがな カタカナ ハンカクカナ 日本語試験 Korean 이번에는 한글로 써보겠습니다 잘 보이나요 한글 Latvian Latviešu valoda arī strādā Lithuanian Sudalyvaukime ir mes Ar veikia lietuviškos raidės ąčęėįšųūž ĄČĘĖĮŠŲŪŽ Žinoma kad veikia Kas tie mes Persian Farsi این یک متن فارسی است ولی امکان نوشتن مستقیم فارسی نیست چون حالت متن از راست به چپ و جود ندارد برای فارسی نوشتن باید از HTML استفاده کنید این نمونه یک متن از راست به چپ فارسی است که در HTML نوشته شده تا اعداد 12345 و حروف لاتین ABCDEF در محل خودشان نمایش داده شوند Polish Pchnąć w tę łódź jeża lub osiem skrzyń fig Nocna gżegżółka zawsze dzienną przekuka Portuguese É possível guardar caracteres especias da língua portuguesa incluindo o símbolo da moeda européia trema ü crase à agudos áéíóú circunflexos

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

  • TracUpgrade – Opus Project
    Trac code base Upgrade the Trac Environment 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 trac admin trac admin path to projenv upgrade This command will do nothing if the environment is already up to date 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 trac admin path to projenv upgrade no backup 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 Update the Trac Documentation Every 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 trac admin provides a command to upgrade the documentation trac admin path to projenv wiki upgrade Note that this procedure will of course leave your WikiStart page intact Site Templates The templating engine has changed in 0 11 please look at TracInterfaceCustomization for more information Trac Macros Plugins The Trac macros will need to be adapted as the old style wiki macros are not supported anymore due to the drop of 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

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

  • TracWiki – Opus Project
    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 the SandBox Some more information

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

  • TracWorkflow – Opus Project
    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 looks like this review new

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

  • WP2_1 – Opus Project
    solution qui s impose Les deux approches proposées dans ce WP sont ainsi complémentaires et permettront de proposer au futur utilisateur de la plate forme un choix des solutions Une réflexion profonde dans le domaine d application de chacune solution permettra également le guider vers une solution la plus adaptée à sa problématique Il est important de noter que la construction d un méta modèle bien qu une étape importante n est pas dans la plupart des cas une fin en soi d une étude d incertitude Analyse de sensibilité WP 2 1 2 propagation à l aide de meta modèles WP 2 1 4 incertitudes dans des couplages hétérogènes WP 2 2 2 et estimation robuste des quantiles WP 2 2 1 en sont des bénéficiaires directs Comment l utilisation d un méta modèle substituant le modèle lourd d un composant se répercuteratelle sur le résultat de l étude multi physique Dans quelle mesure dépende t elle de la quantité d intérêt de l étude Voilà les questions auxquelles ce WP répondra en prenant le pari de formalisme probabiliste L objectif ici est de proposer un cadre générique de considération de ce type de problèmes Puis d en proposer des solutions répondant aux critères industriels contradictoires de robustesse et conservatisme contrôlé Actuellement les solutions proposant de modéliser les interactions entre les sous systèmes commencent à immerger Processus Gaussiens Réseaux Bayesiens il reste toutefois à valider les résultats obtenus sur des exemples isolés pour le cas général et à asseoir un apport que ces approches ont par rapport à des méthodes plus classiques comme la propagation par Monte Carlo Analyse de sensibilité WP 2 1 2 incertitudes dans des couplages hétérogènes WP 2 2 2 et estimation robuste des quantiles WP 2 2 1 sont des bénéficiaires directs de travaux de ce WP WP 2 1 2 Analyse de sensibilité Probablement le deuxième objectif le plus fréquemment rencontré dans les études d incertitude après l estimation robuste des quantiles probabilité de défaillance est l étude de la sensibilité En effet si le système ne satisfait pas le critère quelle est l action à entreprendre Celle qui élèvera à moindre coût les performances au niveau requis Une étude de sensibilité montre dans quelle mesure la variable d intérêt et la quantité d intérêt sont influencée par chaque source variable d entrée du modèle Ainsi en augmentant la connaissance en réduisant l erreur de mesure en affinant la modélisation etc des sources les plus importantes on optimise les efforts L étude de sensibilité peut aussi être vue comme un moyen mathématique de mettre en lumière les propriétés physiques du modèle devenant ainsi partie intégrante de la modélisation Quelles sont les variables les plus importantes influençant la variable d intérêt étudiée Les interactions entre les variables existent elles sont elles importantes Quel est le lien entre le phénomène étudié et les variables Dans le cas des modèles linéaires ou quasi linéaires les solutions robustes existent Dans un cas général évidemment établir cette relation

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