Changeset 37661 for wiki


Ignore:
Timestamp:
06/07/16 23:07:11 (7 years ago)
Author:
aafsvn
Message:

[titan] autoupdate wiki files

Location:
wiki/pages
Files:
906 edited

Legend:

Unmodified
Added
Removed

  • wiki/pages/CamelCase

    r37343 r37661  
    1 = !CamelCase
    2 New wiki links are automatically created when concatenating capitalized words, such that for example the word 'Camel' and the word 'Case' concatenated form a link to this CamelCase page.
    3 
    4 !CamelCase is the original wiki convention for creating hyperlinks, with the additional requirement that the capitals are followed by a lower-case letter; hence “AlabamA” and “ABc” will not be links.
    5 
    6 == Customizing the Wiki behavior
    7 
    8 While Trac remains faithful to the original Wiki style, it provides a number of ways to accommodate users with different preferences:
    9  * To prevent the creation of a new link of a camel-cased word, prefix with '!': `!CamelCase`.
    10  * To ignore links to missing pages when the link is written using the CamelCase style, that word can instead be replaced by a gray link followed by a question mark. This is useful in cases when CamelCase style is used to name code artifacts like class names and there's no corresponding page for them. This option can be set in `ignore_missing_pages` in the [wiki:TracIni#wiki-section "[wiki]"] section of TracIni.
    11  * There's an option (`split_page_names` in the  [wiki:TracIni#wiki-section "[wiki]"] section of TracIni) to automatically insert space characters between the words of a CamelCase link when rendering the link.
    12  * Creation of explicit Wiki links is also easy, see WikiPageNames for details.
    13  * Wiki formatting can be disabled completely in some places, for example when rendering commit log messages. See `wiki_format_messages` in the [wiki:TracIni#changeset-section "[changeset]"] section of TracIni.
    14 
    15 See TracIni for more information on the available options.
    16 
    17 == More information on !CamelCase
    18 
    19  * http://c2.com/cgi/wiki?WikiCase
    20  * http://en.wikipedia.org/wiki/CamelCase
    21 
    22 ----
    23 See also: WikiPageNames, WikiNewPage, WikiFormatting, TracWiki

  • wiki/pages/TracGuide

    r37567 r37661  
    1 = The Trac User and Administration Guide =
    2 [[TracGuideToc]]
    3 {{{#!span style="font-size:90%"
    4 //The TracGuide is 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 [http://trac.edgewall.org Trac Project] itself.//
    5 }}}
    6 
    7 == Introduction
    8 
    9 Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. It strives to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.
    10 
    11 It provides an interface to Subversion (and other version control systems), an integrated Wiki and convenient reporting facilities.
    12 
    13 Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all current and past project events in order, making the acquisition of an overview of the project and tracking progress very easy. The roadmap shows the road ahead, listing the upcoming milestones.
    14 == User Guide
    15    * Using the Wiki subsystem
    16      * TracWiki — How to use the built-in Wiki.
    17      * WikiFormatting — Reference to the wiki syntax used throughout.
    18    * Using the Version Control subsystem
    19      * TracBrowser — Browsing source code with Trac.
    20      * TracChangeset — Viewing changes to source code.
    21      * TracRevisionLog — Viewing change history.
    22    * Using the Ticket subsystem
    23      * TracTickets — Using the issue tracker.
    24      * TracRoadmap — The roadmap helps tracking project progress.
    25      * TracReports — Writing and using reports.
    26      * TracQuery — Executing custom ticket queries.
    27      * TracBatchModify - Modifying a batch of tickets in one request.
    28    * Other modules and general topics
    29      * TracSearch — Full text search in all content.
    30      * TracTimeline — The timeline provides a historic perspective on a project.
    31      * TracRss — RSS content syndication in Trac.
    32      * TracAccessibility — Accessibility keys support
    33 
    34 
    35 == Administrator Guide
    36    * Installation and upgrade
    37      * TracInstall — How to install and run Trac.
    38      * TracUpgrade — How to upgrade existing installations.
    39      * TracImport — Importing tickets from other bug databases.
    40      * TracPlugins — Installing and managing Trac extensions.
    41    * Configuration and customization
    42      * TracIni — Trac configuration file reference.
    43      * TracPermissions — Access control and permissions.
    44      * TracNavigation — Customize main navigation menus.
    45      * TracInterfaceCustomization — Customizing the Trac interface.
    46      * TracLogging — The Trac logging facility.
    47    * Administering the Version Control subsystem
    48      * TracRepositoryAdmin — Management of Source Code Repositories.
    49    * Administering the Ticket subsystem
    50      * TracTicketsCustomFields — Expanding tickets with customized fields.
    51      * TracNotification — Email notification.
    52      * TracWorkflow — Configurable Ticket Workflow.
    53    * Reference
    54      * TracEnvironment — All you need to know about Trac environments
    55      * TracAdmin — Administering a Trac project via the command-line.
    56 
    57 == Support and Other Sources of Information ==
    58 
    59  * [trac:TracFaq Trac FAQ] — A collection of Frequently Asked Questions (on the project website).
    60  * [trac:TracDev] and [trac:TracDev/ApiDocs API docs] — Trac Developer documentation
    61  * TracSupport — How to get more information
    62 
    63 If you are looking for a good place to ask a question about Trac, look no further than the [trac:MailingList MailingList]. It provides a friendly environment to discuss openly among Trac users and developers.

  • wiki/pages/TracInterfaceCustomization

    r37567 r37661  
    1 = Customizing the Trac Interface
    2 [[TracGuideToc]]
    3 [[PageOutline]]
    4 
    5 == Introduction
    6 This page gives suggestions on how to customize the look of Trac. Topics include editing the HTML templates and CSS files, but not the program code itself. The topics show users how they can modify the look of Trac to meet their specific needs. Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page.
    7 
    8 == Project Logo and Icon
    9 The easiest parts of the Trac interface to customize are the logo and the site icon. Both of these can be configured with settings in [wiki:TracIni trac.ini].
    10 
    11 The logo or icon image should be put in a folder named "htdocs" in your project's environment folder. ''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder''.
    12 
    13  '''Note''': you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.
    14 
    15 Now configure the appropriate section of your [wiki:TracIni trac.ini]:
    16 
    17 === Logo
    18 Change the `src` setting to `site/` followed by the name of your image file. The `width` and `height` settings should be modified to match your image's dimensions. The Trac chrome handler uses "`site/`" for files within the project directory `htdocs`, and "`common/`" for the common `htdocs` directory belonging to a Trac installation. Note that 'site/' is not a placeholder for your project name, it is the literal prefix that should be used. For example, if your project is named 'sandbox', and the image file is 'red_logo.gif' then the 'src' setting would be 'site/red_logo.gif', not 'sandbox/red_logo.gif'.
    19 
    20 {{{#!ini
    21 [header_logo]
    22 src = site/my_logo.gif
    23 alt = My Project
    24 width = 300
    25 height = 100
    26 }}}
    27 
    28 === Icon
    29 Icons are small images displayed by your web browser next to the site's URL and in the `Bookmarks` menu. Icons should be a 32x32 image in `.gif` or `.ico` format. Change the `icon` setting to `site/` followed by the name of your icon file:
    30 
    31 {{{#!ini
    32 [project]
    33 icon = site/my_icon.ico
    34 }}}
    35 
    36 == Custom Navigation Entries
    37 The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them, but not for adding new ones.
    38 
    39 In the following example, we rename the link to the Wiki start "Home", and hide the "!Help/Guide". We also make the "View Tickets" entry link to a specific report:
    40 {{{#!ini
    41 [mainnav]
    42 wiki.label = Home
    43 tickets.href = /report/24
    44 
    45 [metanav]
    46 help = disabled
    47 }}}
    48 
    49 See also TracNavigation for a more detailed explanation of the mainnav and metanav terms.
    50 
    51 == Site Appearance == #SiteAppearance
    52 
    53 Trac is using [http://genshi.edgewall.org Genshi] as the templating engine. Say you want to add a link to a custom stylesheet, and then your own header and footer. Save the following content as `site.html` inside your projects `templates/` directory (each Trac project can have their own `site.html`), eg `/path/to/env/templates/site.html`:
    54 
    55 {{{#!xml
    56 <html xmlns="http://www.w3.org/1999/xhtml"
    57       xmlns:py="http://genshi.edgewall.org/"
    58       py:strip="">
    59 
    60   <!--! Add site-specific style sheet -->
    61   <head py:match="head" py:attrs="select('@*')">
    62     ${select('*|comment()|text()')}
    63     <link rel="stylesheet" href="${href.chrome('site/style.css')}" />
    64   </head>
    65 
    66   <body py:match="body" py:attrs="select('@*')">
    67     <!--! Add site-specific header -->
    68     <div id="siteheader">
    69       <!--! Place your header content here... -->
    70     </div>
    71 
    72     ${select('*|text()')}
    73 
    74     <!--! Add site-specific footer -->
    75     <div id="sitefooter">
    76       <!--! Place your footer content here... -->
    77     </div>
    78   </body>
    79 </html>
    80 }}}
    81 
    82 Notice that XSLT bears some similarities with Genshi templates. However, there are some Trac specific features, for example the `${href.chrome('site/style.css')}` attribute references `style.css` in the environment's `htdocs/` directory. In a similar fashion `${chrome.htdocs_location}` is used to specify the common `htdocs/` directory belonging to a Trac installation. That latter location can however be overriden using the [[TracIni#trac-section|[trac] htdocs_location]] configuration setting.
    83 
    84 `site.html` is one file to contain all your modifications. It usually works using the `py:match` directive (element or attribute), and it allows you to modify the page as it renders. The matches hook onto specific sections depending on what it tries to find and modify them.
    85 See [http://groups.google.com/group/trac-users/browse_thread/thread/70487fb2c406c937/ this thread] for a detailed explanation of the above example `site.html`.
    86 A `site.html` can contain any number of such `py:match` sections for whatever you need to modify. This is all Genshi, so the [http://genshi.edgewall.org/wiki/Documentation/xml-templates.html docs on the exact syntax] can be found there.
    87 
    88 Example snippet of adding introduction text to the new ticket form (but not shown during preview):
    89 
    90 {{{#!xml
    91 <form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')">
    92   <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
    93     <p>Please make sure to search for existing tickets before reporting a new one!</p>
    94   </py:if>
    95   ${select('*')}
    96 </form>
    97 }}}
    98 
    99 This example illustrates a technique of using `req.environ['PATH_INFO']` to limit scope of changes to one view only. For instance, to make changes in `site.html` only for timeline and avoid modifying other sections - use  `req.environ['PATH_INFO'] == '/timeline'` condition in `<py:if>` test.
    100 
    101 More examples snippets for `site.html` can be found at [trac:wiki:CookBook/SiteHtml CookBook/SiteHtml].
    102 
    103 Example snippets for `style.css` can be found at [trac:wiki:CookBook/SiteStyleCss CookBook/SiteStyleCss].
    104 
    105 Note that the `site.html`, despite its name, can be put in a shared templates directory, see the [[TracIni#inherit-section|[inherit] templates_dir]] option. This could provide easier maintainence (and a migration path from 0.10 for larger installations) as one new global `site.html` file can be made to include any existing header, footer and newticket snippets.
    106 
    107 == Project List == #ProjectList
    108 
    109 You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects. 
    110 
    111 The following is the basic template used by Trac to display a list of links to the projects. For projects that could not be loaded, it displays an error message. You can use this as a starting point for your own index template:
    112 
    113 {{{#!text/html
    114 <!DOCTYPE html
    115     PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    116     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    117 <html xmlns="http://www.w3.org/1999/xhtml"
    118       xmlns:py="http://genshi.edgewall.org/"
    119       xmlns:xi="http://www.w3.org/2001/XInclude">
    120   <head>
    121     <title>Available Projects</title>
    122   </head>
    123   <body>
    124     <h1>Available Projects</h1>
    125     <ul>
    126       <li py:for="project in projects" py:choose="">
    127         <a py:when="project.href" href="$project.href"
    128            title="$project.description">$project.name</a>
    129         <py:otherwise>
    130           <small>$project.name: <em>Error</em> <br /> ($project.description)</small>
    131         </py:otherwise>
    132       </li>
    133     </ul>
    134   </body>
    135 </html>
    136 }}}
    137 
    138 Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located (pls verify ... not yet changed to 0.11):
    139 
    140 For [wiki:TracModWSGI mod_wsgi]:
    141 {{{#!python
    142 os.environ['TRAC_ENV_INDEX_TEMPLATE'] = '/path/to/template.html'
    143 }}}
    144 
    145 For [wiki:TracFastCgi FastCGI]:
    146 {{{#!apache
    147 FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \
    148               -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template
    149 }}}
    150 
    151 For [wiki:TracModPython mod_python]:
    152 {{{#!apache
    153 PythonOption TracEnvParentDir /parent/dir/of/projects
    154 PythonOption TracEnvIndexTemplate /path/to/template
    155 }}}
    156 
    157 For [wiki:TracCgi CGI]:
    158 {{{#!apache
    159 SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template
    160 }}}
    161 
    162 For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd:
    163  - Unix
    164    {{{#!sh
    165 $ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template
    166    }}}
    167  - Windows
    168    {{{#!sh
    169 $ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template
    170    }}}
    171 
    172 == Project Templates
    173 
    174 The appearance of each individual Trac environment, ie instance of a project, can be customized independently of other projects, even those hosted on the same server. The recommended way is to use a `site.html` template (see [#SiteAppearance]) whenever possible. Using `site.html` means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of `theme.html` or any other Trac template, you need to migrate your modifiations to the newer version. If not, new Trac features or bug fixes may not work as expected.
    175 
    176 With that word of caution, any Trac template may be copied and customized. The default Trac templates are located inside the installed Trac egg (`/usr/lib/pythonVERSION/site-packages/Trac-VERSION.egg/trac/templates, .../trac/ticket/templates, .../trac/wiki/templates, ...`). The [#ProjectList] template file is called `index.html`, while the template responsible for main layout is called `theme.html`. Page assets such as images and CSS style sheets are located in the egg's `trac/htdocs` directory.
    177 
    178 However, do not edit templates or site resources inside the Trac egg. Reinstalling Trac overwrites your modifications. Instead use one of these alternatives:
    179  * For a modification to one project only, copy the template to project `templates` directory.
    180  * For a modification shared by several projects, copy the template to a shared location and have each project point to this location using the `[inherit] templates_dir` trac.ini option.
    181 
    182 Trac resolves requests for a template by first looking inside the project, then in any inherited templates location, and finally inside the Trac egg.
    183 
    184 Trac caches templates in memory by default to improve performance. To apply a template you need to restart the web server.
    185 
    186 ----
    187 See also TracGuide, TracIni

  • wiki/pages/TracLanguages

    r37567 r37661  
    1 ||=Code=||=Name=||=English name=||=Language title=||
    2 ||Ar||العربية||Arabic||لغات أخرى||
    3 ||Ast||asturianu||Asturian||Otres llingües||
    4 ||Az||azərbaycanca||Azeri||Başqa dillərdə||
    5 ||Be||беларуская||Belarusian||Іншыя мовы||
    6 ||Bg||български||Bulgarian||Други езици||
    7 ||Bn||বাংলা||Bengali||অন্যান্য ভাষাসমূহ||
    8 ||Bs||bosanski||Bosnian||Drugim jezicima||
    9 ||Ca||català||Catalan||Altres llengües||
    10 ||Ca-Valencia||valencià||Valencian||Altres llengües||
    11 ||Cs||čeština||Czech||Další jazyky||
    12 ||Da||dansk||Danish||Andre sprog||
    13 ||de||Deutsch||German||Andere Sprachen||
    14 ||gr||Ελληνικά||Greek||Άλλες γλώσσες||
    15 ||en||English||(American) English||Languages||
    16 ||En_AU||Australian||Australian English||Languages||
    17 ||En_GB||British||British||Languages||
    18 ||Es||español||Spanish||Altres idiomas||
    19 ||Et||eesti||Estonian||Teistes keeltes||
    20 ||Eu||euskara||Basque||Beste hizkuntzak||
    21 ||Fa||فارسی||Persian||زبانهای دیگر||
    22 ||Fi||suomi||Finnish||Muilla kielillä||
    23 ||fr||français||French||Autres langues||
    24 ||Gl||galego||Galician||Outras linguas||
    25 ||He||עברית||Hebrew||שפות אחרות||
    26 ||Hi||हिन्दी||Hindi||अन्य भाषाओं||
    27 ||Hr||hrvatski||Croatian||Drugi jezici||
    28 ||Hu||magyar||Hungarian||Más nyelveken||
    29 ||Hy||Հայերեն||Armenian||այլ լեզուներ||
    30 ||Id||Bahasa Indonesia||Indonesian||Bahasa lain||
    31 ||Is||Íslenska||Icelandic||Á öðrum tungumálum||
    32 ||it||italiano||Italian||Altre lingue||
    33 ||Ja||日本語||Japanese||他の言語||
    34 ||Ka||ქართული||Georgian||სხვა ენებზე||
    35 ||Ko||한국어||Korean||다른 언어||
    36 ||Km||ភាសាខ្មែរ||Khmer||ភាសាផ្សេងទៀត||
    37 ||Lt||lietuvių||Lithuanian||Kitomis kalbomis||
    38 ||Lv||latviešu||Latvian||Pārējās valodas||
    39 ||Mk||македонски||Macedonian||Други јазици||
    40 ||Nb||norsk bokmål||Norwegian (Bokmal)||Andre språk||
    41 ||nl||Nederlands||Dutch||Andere talen||
    42 ||pl||polski||Polish||Inne języki||
    43 ||Pt||português||Portuguese||Outras línguas||
    44 ||Pt_BR||português brasileiro||Brazilian Portuguese||Outras línguas||
    45 ||Ro||Română||Romanian||Alte limbi||
    46 ||ru||русский||Russian||Другие языки||
    47 ||Sq||shqip||Albanian||Gjuhët e tjera||
    48 ||Sk||slovenčina||Slovak||Ďalšie jazyky||
    49 ||Sl||slovenščina||Slovenian||Drugi jeziki||
    50 ||Sr||српски||Serbian||Остали језици||
    51 ||Sv||svenska||Swedish||Andra språk||
    52 ||Th||ไทย||Thai||ภาษาอื่น ๆ||
    53 ||Tr||Türkçe||Turkish||Diğer diller||
    54 ||Uk||українська||Ukrainian||Інші мови||
    55 ||Uz||ўзбек тили||Uzbek||Boshqa tillarda||
    56 ||vn||Tiếng Việt||Vietnamese||Ngôn ngữ khác||
    57 ||Zh_CN||简体中文||Chinese (Simplified)||其他语言||
    58 ||Zh_TW||正體中文||Chinese (Traditional)||其他語言||

  • wiki/pages/TracLogging

    r37567 r37661  
    1 = Trac Logging
    2 [[TracGuideToc]]
    3 
    4 Trac supports logging of system messages using the standard [http://docs.python.org/library/logging.html logging module] that comes with Python.
    5 
    6 Logging is configured in the `[logging]` section in [wiki:TracIni#logging-section trac.ini].
    7 
    8 == Supported Logging Methods
    9 
    10 The log method is set using the `log_type` option in [wiki:TracIni#logging-section trac.ini], which takes any of the following values:
    11 
    12  '''none'':: Suppress all log messages.
    13  '''file''':: Log messages to a file, specified with the `log_file` option in [wiki:TracIni#logging-section trac.ini]. Relative paths in `log_file` are resolved relative to the `log` directory of the environment.
    14  '''stderr''':: Output all log entries to console ([wiki:TracStandalone tracd] only).
    15  '''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.
    16  '''eventlog''':: (Windows) Use the system's NT Event Log for Trac logging.
    17 
    18 == Log Levels
    19 
    20 The verbosity level of logged messages can be set using the `log_level` option in [wiki:TracIni#logging-section trac.ini]. The log level defines the minimum level of urgency required for a message to be logged, and those levels are:
    21 
    22  '''CRITICAL''':: Log only the most critical (typically fatal) errors.
    23  '''ERROR''':: Log failures, bugs and errors.
    24  '''WARN''':: Log warnings, non-interrupting events.
    25  '''INFO''':: Diagnostic information, log information about all processing.
    26  '''DEBUG''':: Trace messages, profiling, etc.
    27 
    28 Additionally, you can  enable logging of SQL statements at debug level. This is turned off by default, as it's very verbose. Set `[trac] debug_sql = yes` in TracIni to activate.
    29 
    30 == Log Format
    31 
    32 The output format for log entries can be specified through the `log_format` option in [wiki:TracIni#logging-section trac.ini]. The format is a string which can contain any of the [http://docs.python.org/library/logging.html#logrecord-attributes Python logging Formatter variables]. Additonally, the following Trac-specific variables can be used:
    33  '''$(basename)s''':: The last path component of the current environment.
    34  '''$(path)s''':: The absolute path for the current environment.
    35  '''$(project)s''':: The originating project's name.
    36 
    37 Note that variables are identified using a dollar sign (`$(...)s`) instead of percent sign (`%(...)s`).
    38 
    39 The default format is:
    40 {{{#!ini
    41 log_format = Trac[$(module)s] $(levelname)s: $(message)s
    42 }}}
    43 
    44 In a multi-project environment where all logs are sent to the same place (e.g. `syslog`), it makes sense to add the project name. In this example we use `basename` since that can generally be used to identify a project:
    45 {{{#!ini
    46 log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s
    47 }}}
    48 
    49 ----
    50 See also: TracIni, TracGuide, TracEnvironment

  • wiki/pages/TracNotification

    r37567 r37661  
    1 = Email Notification of Ticket Changes
    2 [[TracGuideToc]]
    3 
    4 Trac supports notification of ticket changes via email.
    5 
    6 Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list. For example, this is how the [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list is set up.
    7 
    8 Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini].
    9 
    10 == Receiving Notification Mails
    11 When reporting a new ticket or adding a comment, enter a valid email address or your Trac username in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket, depending on how notification is configured.
    12 
    13 === How to use your username to receive notification mails
    14 
    15 To receive notification mails, you can either enter a full email address or your Trac username. To get notified with a simple username or login, you need to specify a valid email address in the ''Preferences'' page.
    16 
    17 Alternatively, a default domain name ('''`smtp_default_domain`''') can be set in the TracIni file, see [#ConfigurationOptions Configuration Options] below. In this case, the default domain will be appended to the username, which can be useful for an "Intranet" kind of installation.
    18 
    19 When using apache and mod_kerb for authentication against Kerberos / Active Directory, usernames take the form ('''`username@EXAMPLE.LOCAL`'''). To avoid this being interpreted as an email address, add the Kerberos domain to  ('''`ignore_domains`''').
    20 
    21 === Ticket attachment notifications
    22 
    23 Since 1.0.3 Trac will send notifications when a ticket attachment is added or deleted. Usually attachment notifications will be enabled in an environment by default. To disable the attachment notifications for an environment the `TicketAttachmentNotifier` component must be disabled:
    24 {{{#!ini
    25 [components]
    26 trac.ticket.notification.TicketAttachmentNotifier = disabled
    27 }}}
    28 
    29 == Configuring SMTP Notification
    30 
    31 '''Important:''' For TracNotification to work correctly, the `[trac] base_url` option must be set in [wiki:TracIni trac.ini].
    32 
    33 === Configuration Options
    34 These are the available options for the `[notification]` section in trac.ini:
    35 
    36 [[TracIni(notification)]]
    37 
    38 === Example Configuration (SMTP)
    39 {{{#!ini
    40 [notification]
    41 smtp_enabled = true
    42 smtp_server = mail.example.com
    43 smtp_from = notifier@example.com
    44 smtp_replyto = myproj@projects.example.com
    45 smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
    46 }}}
    47 
    48 === Example Configuration (`sendmail`)
    49 {{{#!ini
    50 [notification]
    51 smtp_enabled = true
    52 email_sender = SendmailEmailSender
    53 sendmail_path = /usr/sbin/sendmail
    54 smtp_from = notifier@example.com
    55 smtp_replyto = myproj@projects.example.com
    56 smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
    57 }}}
    58 
    59 === Subscriber Configuration
    60 The default subscriptions are configured in the `[notification-subscriber]` section in trac.ini:
    61 
    62 [[TracIni(notification-subscriber)]]
    63 
    64 Each user can override these defaults in his ''Notifications'' preferences.
    65 
    66 For example to unsubscribe from notifications for one's own changes and comments, the rule "Never notify: I update a ticket" should be added above other subscription rules.
    67 
    68 === Customizing the e-mail subject
    69 The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet. The default value is:
    70 {{{#!genshi
    71 $prefix #$ticket.id: $summary
    72 }}}
    73 The following variables are available in the template:
    74 
    75  * `env`: The project environment (see [trac:source:/trunk/trac/env.py env.py]).
    76  * `prefix`: The prefix defined in `smtp_subject_prefix`.
    77  * `summary`: The ticket summary, with the old value if the summary was edited.
    78  * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, eg `$ticket.milestone`.
    79 
    80 === Customizing the e-mail content
    81 
    82 The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/ticket/templates`. You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this:
    83 
    84 {{{#!genshi
    85 $ticket_body_hdr
    86 $ticket_props
    87 {% choose ticket.new %}\
    88 {%   when True %}\
    89 $ticket.description
    90 {%   end %}\
    91 {%   otherwise %}\
    92 {%     if changes_body %}\
    93 ${_('Changes (by %(author)s):', author=change.author)}
    94 
    95 $changes_body
    96 {%     end %}\
    97 {%     if changes_descr %}\
    98 {%       if not changes_body and not change.comment and change.author %}\
    99 ${_('Description changed by %(author)s:', author=change.author)}
    100 {%       end %}\
    101 $changes_descr
    102 --
    103 {%     end %}\
    104 {%     if change.comment %}\
    105 
    106 ${changes_body and _('Comment:') or _('Comment (by %(author)s):', author=change.author)}
    107 
    108 $change.comment
    109 {%     end %}\
    110 {%   end %}\
    111 {% end %}\
    112 
    113 --
    114 ${_('Ticket URL: <%(link)s>', link=ticket.link)}
    115 $project.name <${project.url or abs_href()}>
    116 $project.descr
    117 }}}
    118 
    119 == Sample Email
    120 {{{
    121 #42: testing
    122 ---------------------------+------------------------------------------------
    123        Id:  42             |      Status:  assigned               
    124 Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
    125  Severity:  major          |   Milestone:  0.9                     
    126  Priority:  lowest         |     Version:  0.6                     
    127     Owner:  anonymous      |    Reporter:  jonas@example.com               
    128 ---------------------------+------------------------------------------------
    129 Changes:
    130   * component:  changeset view => search system
    131   * priority:  low => highest
    132   * owner:  jonas => anonymous
    133   * cc:  daniel@example.com =>
    134          daniel@example.com, jonas@example.com
    135   * status:  new => assigned
    136 
    137 Comment:
    138 I'm interested too!
    139 
    140 --
    141 Ticket URL: <http://example.com/trac/ticket/42>
    142 My Project <http://myproj.example.com/>
    143 }}}
    144 
    145 == Customizing e-mail content for MS Outlook
    146 
    147 MS Outlook normally presents plain text e-mails with a variable-width font, and as a result the ticket properties table will most certainly look like a mess in MS Outlook. This can be fixed with some customization of the [#Customizingthee-mailcontent e-mail template].
    148 
    149 Replace the following second row in the template:
    150 {{{
    151 $ticket_props
    152 }}}
    153 
    154 with this (requires Python 2.6 or later):
    155 {{{
    156 --------------------------------------------------------------------------
    157 {% with
    158    pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in
    159          [c.strip() for c in
    160           ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]];
    161    sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone',
    162           'Component', 'Severity', 'Resolution', 'Keywords'] %}\
    163 ${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)}
    164 {% end %}\
    165 --------------------------------------------------------------------------
    166 }}}
    167 
    168 The table of ticket properties is replaced with a list of a selection of the properties. A tab character separates the name and value in such a way that most people should find this more pleasing than the default table when using MS Outlook.
    169 {{{#!div style="margin: 1em 1.75em; border:1px dotted"
    170 {{{#!html
    171 #42: testing<br />
    172 --------------------------------------------------------------------------<br />
    173 <table cellpadding=0>
    174 <tr><td>Reporter:</td><td>jonas@example.com</td></tr>
    175 <tr><td>Owner:</td><td>anonymous</td></tr>
    176 <tr><td>Type:</td><td>defect</td></tr>
    177 <tr><td>Status:</td><td>assigned</td></tr>
    178 <tr><td>Priority:</td><td>lowest</td></tr>
    179 <tr><td>Milestone:</td><td>0.9</td></tr>
    180 <tr><td>Component:</td><td>report system</td></tr>
    181 <tr><td>Severity:</td><td>major</td></tr>
    182 <tr><td>Resolution:</td><td> </td></tr>
    183 <tr><td>Keywords:</td><td> </td></tr>
    184 </table>
    185 --------------------------------------------------------------------------<br />
    186 Changes:<br />
    187 <br />
    188 &nbsp;&nbsp;* component: &nbsp;changeset view =&gt; search system<br />
    189 &nbsp;&nbsp;* priority: &nbsp;low =&gt; highest<br />
    190 &nbsp;&nbsp;* owner: &nbsp;jonas =&gt; anonymous<br />
    191 &nbsp;&nbsp;* cc: &nbsp;daniel@example.com =&gt;<br />
    192 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;daniel@example.com, jonas@example.com<br />
    193 &nbsp;&nbsp;* status: &nbsp;new =&gt; assigned<br />
    194 <br />
    195 Comment:<br />
    196 I'm interested too!<br />
    197 <br />
    198 --<br />
    199 Ticket URL: &lt;http://example.com/trac/ticket/42&gt;<br />
    200 My Project &lt;http://myproj.example.com/&gt;<br />
    201 }}}
    202 }}}
    203 
    204 **Important**: Only those ticket fields that are listed in `sel` are part of the HTML mail. If you have defined custom ticket fields which are to be part of the mail, then they have to be added to `sel`. Example:
    205 {{{
    206    sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2']
    207 }}}
    208 
    209 However, the solution is still a workaround to an automatically HTML-formatted e-mail.
    210 
    211 == Using GMail as the SMTP relay host
    212 
    213 Use the following configuration snippet:
    214 {{{#!ini
    215 [notification]
    216 smtp_enabled = true
    217 use_tls = true
    218 mime_encoding = base64
    219 smtp_server = smtp.gmail.com
    220 smtp_port = 587
    221 smtp_user = user
    222 smtp_password = password
    223 }}}
    224 
    225 where ''user'' and ''password'' match an existing GMail account, ie the ones you use to log in on [http://gmail.com].
    226 
    227 Alternatively, you can use `smtp_port = 25`.[[br]]
    228 You should not use `smtp_port = 465`. Doing so may deadlock your ticket submission. Port 465 is reserved for the SMTPS protocol, which is not supported by Trac. See [trac:comment:2:ticket:7107 #7107] for details.
    229 
    230 == Troubleshooting
    231 
    232 If you cannot get the notification working, first make sure the log is activated and have a look at the log to find if an error message has been logged. See TracLogging for help about the log feature.
    233 
    234 Notification errors are not reported through the web interface, so the user who submits a change or a new ticket never gets notified about a notification failure. The Trac administrator needs to look at the log to find the error trace.
    235 
    236 === ''Permission denied'' error
    237 
    238 Typical error message:
    239 {{{#!sh
    240   ...
    241   File ".../smtplib.py", line 303, in connect
    242     raise socket.error, msg
    243   error: (13, 'Permission denied')
    244 }}}
    245 
    246 This error usually comes from a security settings on the server: many Linux distributions do not allow the web server (Apache, ...) to post email messages to the local SMTP server.
    247 
    248 Many users get confused when their manual attempts to contact the SMTP server succeed:
    249 {{{#!sh
    250 telnet localhost 25
    251 }}}
    252 This is because a regular user may connect to the SMTP server, but the web server cannot:
    253 {{{#!sh
    254 sudo -u www-data telnet localhost 25
    255 }}}
    256 
    257 In such a case, you need to configure your server so that the web server is authorized to post to the SMTP server. The actual settings depend on your Linux distribution and current security policy. You may find help in the Trac [trac:MailingList MailingList] archive.
    258 
    259 Relevant ML threads:
    260  * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518
    261 
    262 For SELinux in Fedora 10:
    263 {{{#!sh
    264 $ setsebool -P httpd_can_sendmail 1
    265 }}}
    266 
    267 === ''Suspected spam'' error
    268 
    269 Some SMTP servers may reject the notification email sent by Trac.
    270 
    271 The default Trac configuration uses Base64 encoding to send emails to the recipients. The whole body of the email is encoded, which sometimes trigger ''false positive'' spam detection on sensitive email servers. In such an event, change the default encoding to "quoted-printable" using the `mime_encoding` option.
    272 
    273 Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, stick with the Base64 encoding.
    274 
    275 ----
    276 See also: TracTickets, TracIni, TracGuide, [trac:TracDev/NotificationApi]

  • wiki/pages/TracRevisionLog

    r37567 r37661  
    1 = Viewing Revision Logs =
    2 [[TracGuideToc]]
    3 
    4 When you browse the repository, it is always possible to view the ''Revision Log'' that corresponds to the repository path. This displays a list of the most recent changesets in which the current path or any other path below it has been modified.
    5 
    6 == The Revision Log Form ==
    7 
    8 It is possible to set the revision at which the revision log should start, using the ''View log starting at'' field. An empty value or a value of ''head'' is interpreted as the newest changeset.
    9 
    10 It is also possible to specify the revision at which the log should stop, using the ''Back to'' field. By default it is empty,
    11 which means the revision log will show the latest 100 revisions.
    12 
    13 Also, there are three modes of operation of the revision log.
    14 
    15 By default, the revision log ''stops on copy'', which means that whenever an ''Add'', ''Copy'' or ''Rename'' operation is detected, no older revision will be shown. That's very convenient when working with branches, as one only sees the history corresponding to what has been done on the branch.
    16 
    17 It is also possible to indicate that one wants to see what happened before a ''Copy'' or ''Rename'' change, by selecting the
    18 ''Follow copies'' mode. This will cross all copies or renames changes.
    19 Each time the name of the path changes, there will be an additional indentation level. That way, the changes on the different paths are easily grouped together visually.
    20 
    21 It is even possible to go past an ''Add'' change, in order to see if there has been a ''Delete'' change on that path, before
    22 that ''Add''. This mode corresponds to the mode called ''Show only adds, moves and deletes''. This operation can be quite resource intensive and therefore take some time to be shown on screen.
    23 
    24 Finally, there's also a checkbox ''Show full log messages'', which controls whether the full content of the commit log message
    25 should be displayed for each change, or only a shortened version of it.
    26 
    27 == The Revision Log Information ==
    28 
    29 For each revision log entry, the following columns are displayed:
    30  1. The first column contains a pair of radio buttons and should be used
    31     for selecting the ''old'' and the ''new'' revisions that will be
    32     used for [wiki:TracRevisionLog#viewingtheactualchanges viewing the actual changes].
    33  1. A color code (similar to the one used for the
    34     [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change.
    35     Clicking on this column refreshes the revision log so that it restarts
    36     with this change.
    37  1. The '''Revision''' number, displayed as `@xyz`.
    38     This is a link to the TracBrowser, using the displayed revision as the base line.
    39  Next to it, you can see a little "wheel" icon [[Image(htdocs:../common/changeset.png)]],  which is clickable and leads to the TracChangeset view for that revision.
    40  1. The '''Date''' at which the change was made.
    41     The date is displayed as the time elapsed from the date of the revision. The time
    42     elapsed is displayed as the number of hours, days, weeks, months, or years.
    43  1. The '''Author''' of the change.
    44  1. The '''Log Message''', which contains either the truncated or full commit
    45     log message, depending on the value of the ''Show full log messages''
    46     checkbox in the form above.
    47    
    48 
    49 == Inspecting Changes Between Revisions ==
    50 
    51 The ''View changes...'' buttons (placed above and below the list of changes, on the left side) will show the set of differences
    52 corresponding to the aggregated changes starting from the ''old'' revision (first radio-button) to the ''new'' revision (second
    53 radio-button), in the TracChangeset view.
    54 
    55 Note that the ''old'' revision doesn't need to be actually ''older'' than the ''new'' revision: it simply gives a base
    56 for the diff. It's therefore entirely possible to easily generate a ''reverse diff'', for reverting what has been done
    57 in the given range of revisions.
    58 
    59 Finally, if the two revisions are identical, the corresponding changeset will be shown. This has the same effect as clicking on the !ChangeSet number.
    60 
    61 == Alternative Formats ==
    62 
    63 === The !ChangeLog Text ===
    64 
    65 At the bottom of the page, there's a ''!ChangeLog'' link that will show the range of revisions as currently shown, but as a simple text, matching the usual conventions for !ChangeLog files.
    66 
    67 === RSS Support ===
    68 
    69 The revision log also provides a RSS feed to monitor the changes. To subscribe to a RSS feed for a file or directory, open its
    70 revision log in the browser and click the orange 'XML' icon at the bottom of the page. For more information on RSS support in Trac, see TracRss.
    71 
    72 ----
    73 See also: TracBrowser, TracChangeset, TracGuide

  • wiki/pages/TracRoadmap

    r37567 r37661  
    1 = The Trac Roadmap
    2 [[TracGuideToc]]
    3 
    4 The roadmap provides a view on the [wiki:TracTickets ticket system] that helps planning and managing the future development of a project.
    5 
    6 == The Roadmap View
    7 
    8 A roadmap is a list of future milestones. The roadmap can be filtered to show or hide ''completed milestones'' and ''milestones with no due date''. In the case that both ''show completed milestones'' and ''hide milestones with no due date'' are selected, ''completed'' milestones with no due date will be shown.
    9 
    10 == The Milestone View
    11 
    12 A milestone is a future timeframe in which tickets are expected to be solved. You can add a description to milestones (using WikiFormatting) describing main objectives, for example. In addition, tickets targeted for a milestone are aggregated, and the ratio between active and resolved tickets is displayed as a milestone progress bar. It is possible to further [trac:TracRoadmapCustomGroups customise the ticket grouping] and have multiple ticket statuses shown on the progress bar.
    13 
    14 It is possible to drill down into this simple statistic by viewing the individual milestone pages. By default, the active/resolved ratio will be grouped and displayed by component. You can also regroup the status by other criteria, such as ticket owner or severity. Ticket numbers are linked to [wiki:TracQuery custom queries] listing corresponding tickets.
    15 
    16 == Roadmap Administration
    17 
    18 With appropriate permissions it is possible to add, modify and remove milestones using either the web interface (roadmap and milestone pages), web administration interface or by using `trac-admin`.
    19 
    20 '''Note:''' Milestone descriptions can not currently be edited using 'trac-admin'.
    21 
    22 == iCalendar Support
    23 
    24 The Roadmap supports the [http://www.ietf.org/rfc/rfc2445.txt iCalendar] format to keep track of planned milestones and related tickets from your favorite calendar software. Many calendar applications support the iCalendar specification including
    25  * [http://www.apple.com/ical/ Apple iCal] for Mac OS X
    26  * the cross-platform [http://www.mozilla.org/projects/calendar/ Mozilla Calendar]
    27  * [http://chandlerproject.org Chandler]
    28  * [http://kontact.kde.org/korganizer/ Korganizer], the calendar application of the [http://www.kde.org/ KDE] project
    29  * [https://wiki.gnome.org/Apps/Evolution Evolution]
    30  * [http://office.microsoft.com/en-us/outlook/ Microsoft Outlook] can also read iCalendar files and appears as a new static calendar in Outlook
    31  * [https://www.google.com/calendar/ Google Calendar]
    32 
    33 To subscribe to the roadmap, copy the iCalendar link from the roadmap (found at the bottom of the page) and choose the "Subscribe to remote calendar" action (or similar) of your calendar application, and insert the URL just copied.
    34 
    35 '''Note:''' For tickets to be included in the calendar as tasks, you need to be logged in when copying the link. You will only see tickets assigned to yourself and associated with a milestone.
    36 
    37 '''Note:''' To include the milestones in Google Calendar you might need to rewrite the URL.
    38 {{{
    39 RewriteEngine on
    40 RewriteRule ([^/.]+)/roadmap/([^/.]+)/ics /$1/roadmap?user=$2&format=ics
    41 }}}
    42 
    43 More information about iCalendar can be found at [http://en.wikipedia.org/wiki/ICalendar Wikipedia].
    44 ----
    45 See also: TracTickets, TracReports, TracQuery, [trac:TracRoadmapCustomGroups]

  • wiki/pages/TracSearch

    r37567 r37661  
    1 = Using Search
    2 
    3 Trac has built-in search functionality to search for occurrences of keywords and substrings in wiki pages, tickets and changeset properties, such as author, revision and log messages.
    4 
    5 Apart from the [search: Search module], you will also find a small search field above the navigation bar at all time. It provides convenient access to the search module from all pages.
    6 
    7 The search results show the most recent modifications ranked first rather than the most relevant result.
    8 
    9 == Quick searches
    10 For quick access to project resources, the quick-search field at the top of every page can be used to enter a [TracLinks wiki link], which will take you directly to the resource identified by that link:
    11 
    12  * ![42] -- Opens change set 42
    13  * !#42 -- Opens ticket number 42
    14  * !{1} -- Opens report 1
    15  * /trunk -- Opens the browser for the `trunk` directory in the default repository
    16  * /repos1/trunk -- Opens the browser for the `trunk` directory in the `repos1` repository
    17 
    18 == Advanced
    19 
    20 === Disabling Quickjump
    21 To disable the Quickjump feature for a keyword start the query with an exclamation mark (`!`): use `!TracGuide` to search for occurrences of the literal word !TracGuide.
    22 
    23 === Search Links
    24 From the Wiki, it is possible to link to a specific search, using `search:` links:
    25  * `search:?q=crash` will search for the string "crash"
    26  * `search:?q=trac+link&wiki=on` will search for "trac" and "link" in wiki pages only
    27 
    28 ----
    29 See also: TracGuide, TracLinks, TracQuery

  • wiki/pages/TracTickets

    r37567 r37661  
    1 = The Trac Ticket System =
    2 [[TracGuideToc]]
    3 
    4 The Trac ticket database provides simple but effective way to track issues and software bugs within a project.
    5 
    6 As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''', '''software support issues''' among others.
    7 
    8 As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible.
    9 
    10 An issue is assigned to a person who must resolve it or reassign the ticket to someone else. All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
    11 
    12 [=#edit-permissions]
    13 However, a Trac installation may place restrictions on who can change what. For example, the default installation doesn't permit to non-authenticated users ("anonymous" users) to change anything, even to comment on an issue, for obvious spam prevention reasons. Check the local contributing policy, which you can usually find on the front page WikiStart, or contact your local Trac administrator.
    14 
    15 == Ticket Fields ==
    16 
    17 A ticket contains the following information:
    18  
    19  * '''Reporter''' — The author of the ticket.
    20  * '''Type''' — The category of the ticket. The default types are `defect`,  `enhancement` and `task`.
    21  * '''Component''' — The project module or subsystem this ticket concerns.
    22  * '''Version''' — Version of the project that this ticket pertains to.
    23  * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation.
    24  * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined.
    25  * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones.
    26  * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
    27  * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.''
    28  * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    29  * '''Status''' — What is the current status? The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`.
    30  * '''Summary''' — A description summarizing the issue. Simple text without WikiFormatting.
    31  * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point. Accepts WikiFormatting.
    32 
    33 '''Notes:'''
    34  - 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  - 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  - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
    39 
    40 == Changing and Commenting Tickets ==
    41 
    42 With appropriate permissions, as already mentioned [#edit-permissions above], a ticket entered into Trac can at any time be modified by '''annotating'''.
    43 
    44 Then, annotations like 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.
    45 
    46 Comment editing (available since 0.12) is meant to be used to make small corrections to comments, like fixing formatting, forgotten WikiFormatting or spelling errors, not major edits. For longer edits, you should be adding a new comment instead. Editing a comment will not produce a new entry on [/timeline] while entering a new comment or other changes will do.
    47 
    48 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
    49 
    50 
    51 '''Notes:'''
    52  - 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.
    53 
    54  - See TracNotification for how to configure email notifications of ticket changes.
    55 
    56  - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
    57 
    58 == Default Values for Drop-Down Fields ==
    59 
    60 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    61 
    62  * `default_component`: Name of the component selected by default
    63  * `default_milestone`: Name of the default milestone
    64  * `default_priority`: Default priority value
    65  * `default_severity`: Default severity value
    66  * `default_type`: Default ticket type
    67  * `default_version`: Name of the default version
    68  * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
    69 
    70 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.  Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section, others can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`.
    71 
    72 
    73 == Hiding Fields and Adding Custom Fields ==
    74 
    75 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''.
    76 
    77 Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.
    78 
    79 
    80 == Assign-to as Drop-Down List ==
    81 
    82 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 done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to `true`. In that case, Trac will populate the list with all users who have authenticated with the project and possess the  `TICKET_MODIFY` [TracPermissions permissions].
    83 
    84 You may find the dropdown list is //overpopulated// with users that are no longer active in the project. Revoking authentication privileges will not remove the session data that is used to populate the dropdown list. The [wiki:TracAdmin trac-admin] command can be used to list and remove sessions:
    85 
    86  - List all sessions:
    87 {{{#!sh
    88 trac-admin /path/to/projenv session list
    89 }}}
    90  - Remove a session:
    91 {{{#!sh
    92 trac-admin /path/to/projenv session delete SID
    93 }}}
    94 
    95 Alternatively, you can just revoke `TICKET_MODIFY` from users that you don't want to be included in the list. However, that will not be possible if you've granted `TICKET_MODIFY` to all //anonymous// or //authenticated// users.
    96 
    97 '''Notes:'''
    98  - If you need serious flexibility and aren't afraid of a little plugin coding of your own, see [http://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo].
    99 
    100  -  Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
    101 
    102 == Preset Values for New Tickets ==
    103 
    104 To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with `variable=value` separated by `&`. Possible variables are:
    105 
    106  * '''type''' — The type droplist
    107  * '''reporter''' — Name or email of the reporter
    108  * '''summary''' — Summary line for the ticket
    109  * '''description''' — Long description of the ticket
    110  * '''component''' — The component droplist
    111  * '''version''' — The version droplist
    112  * '''severity''' — The severity droplist
    113  * '''keywords''' — The keywords
    114  * '''priority''' — The priority droplist
    115  * '''milestone''' — The milestone droplist
    116  * '''owner''' — The person responsible for the ticket
    117  * '''cc''' — The list of emails for notifying about the ticket change
    118 
    119 Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''
    120 
    121 ----
    122 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery

  • wiki/pages/TracWorkflow

    r37567 r37661  
    1 = The Trac Ticket Workflow System
    2 
    3 [[PageOutline(2-5,Contents,pullout)]]
    4 [[TracGuideToc]]
    5 The Trac ticket system provides a configurable workflow.
    6 
    7 == The Default Ticket Workflow
    8 
    9 When a new environment is created, a default workflow is configured in your trac.ini. This workflow is the basic workflow, such as specified in [trac:source:/trunk/trac/ticket/workflows/basic-workflow.ini basic-workflow.ini]:
    10 
    11 {{{#!Workflow width=700 height=300
    12 leave = * -> *
    13 leave.operations = leave_status
    14 leave.default = 1
    15 
    16 create = <none> -> new
    17 create.default = 1
    18 
    19 create_and_assign = <none> -> assigned
    20 create_and_assign.label = assign
    21 create_and_assign.permissions = TICKET_MODIFY
    22 create_and_assign.operations = may_set_owner
    23 
    24 accept = new,assigned,accepted,reopened -> accepted
    25 accept.permissions = TICKET_MODIFY
    26 accept.operations = set_owner_to_self
    27 
    28 resolve = new,assigned,accepted,reopened -> closed
    29 resolve.permissions = TICKET_MODIFY
    30 resolve.operations = set_resolution
    31 
    32 reassign = new,assigned,accepted,reopened -> assigned
    33 reassign.permissions = TICKET_MODIFY
    34 reassign.operations = set_owner
    35 
    36 reopen = closed -> reopened
    37 reopen.permissions = TICKET_CREATE
    38 reopen.operations = del_resolution
    39 }}}
    40 
    41 == Additional Ticket Workflows
    42 
    43 There are example workflows provided in the Trac source tree, see [trac:source:trunk/contrib/workflow contrib/workflow] for `.ini` config sections. One of those may be a good match for what you want. They can be pasted into the `[ticket-workflow]` section of your `trac.ini` file. However, if you have existing tickets then there may be issues if those tickets have states that are not in the new workflow.
    44 
    45 Here are some [trac:WorkFlow/Examples diagrams] of the above examples.
    46 
    47 == Basic Ticket Workflow Customization
    48 
    49 '''Note''': Ticket "statuses" or "states" are not separately defined. The states a ticket can be in are automatically generated by the transitions defined in a workflow. Therefore, creating a new ticket state simply requires defining a state transition in the workflow that starts or ends with that state.
    50 
    51 Create a `[ticket-workflow]` section in `trac.ini`.
    52 Within this section, each entry is an action that may be taken on a ticket.
    53 For example, consider the `accept` action from `simple-workflow.ini`:
    54 
    55 {{{#!ini
    56 accept = new,accepted -> accepted
    57 accept.permissions = TICKET_MODIFY
    58 accept.operations = set_owner_to_self
    59 }}}
    60 
    61 The first line in this example defines the `accept` action, along with the states the action is valid in (`new` and `accepted`), and the new state of the ticket when the action is taken (`accepted`).
    62 The `accept.permissions` line specifies what permissions the user must have to use this action.
    63 The `accept.operations` line specifies changes that will be made to the ticket in addition to the status change when this action is taken.  In this case, when a user clicks on `accept`, the ticket owner field is updated to the logged in user.  Multiple operations may be specified in a comma separated list.
    64 
    65 The available operations are:
    66 - **del_owner** -- Clear the owner field.
    67 - **set_owner** -- Sets the owner to the selected or entered owner. Defaults to the current user. When `[ticket] restrict_owner = true`, the select will be populated with users that have `TICKET_MODIFY` permission and an authenticated session.
    68  - ''actionname''`.set_owner` may optionally be set to a comma delimited list of users that will be used to populate the select, or a single user. Groups and permissions may also be included in the list //(Since 1.1.3)//. When groups or permissions are specified the select is populated with all members of the group or all users that possess the permission.
    69 - **set_owner_to_self** -- Sets the owner to the logged in user.
    70 - **may_set_owner** -- Sets the owner to the selected or entered owner. Defaults to the existing owner. //(Since 1.1.2)//.
    71 - **del_resolution** -- Clears the resolution field.
    72 - **set_resolution** -- Sets the resolution to the selected value.
    73  - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. Example:
    74  {{{#!ini
    75 resolve_new = new -> closed
    76 resolve_new.label = resolve
    77 resolve_new.operations = set_resolution
    78 resolve_new.permissions = TICKET_MODIFY
    79 resolve_new.set_resolution = invalid,wontfix
    80 }}}
    81 - **leave_status** -- Displays "leave as <current status>" and makes no change to the ticket.
    82 - **reset_workflow** -- Resets the status of tickets that are in states no longer defined.
    83 '''Note:''' Specifying conflicting operations, such as `set_owner` and `del_owner`, has unspecified results.
    84 
    85 In this example, we see the `.label` attribute used. The action here is `resolve_accepted`, but it will be presented to the user as `resolve`:
    86 
    87 {{{#!ini
    88 resolve_accepted = accepted -> closed
    89 resolve_accepted.label = resolve
    90 resolve_accepted.permissions = TICKET_MODIFY
    91 resolve_accepted.operations = set_resolution
    92 }}}
    93 
    94 In this example, we see the `.label` attribute used.  The action here is `resolve_accepted`, but it will be presented to the user as `resolve`. The `.label` attribute is new in Trac 1.1.3 and is functionally the same as the `.name` attribute, which is now deprecated. If neither `.label` or `.name` is specified, the action will be presented to the user as //resolve accepted//, the underscores having been replaced by whitespace (//Since 1.1.3//).
    95 
    96 For actions that should be available in all states, `*` may be used in place of the state. The obvious example is the `leave` action:
    97 {{{#!ini
    98 leave = * -> *
    99 leave.operations = leave_status
    100 leave.default = 1
    101 }}}
    102 
    103 This also shows the use of the `.default` attribute. This value is expected to be an integer, and the order 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.
    104 If not specified for an action, `.default` is 0. The value may be negative.
    105 
    106 The ticket create actions are specified by a transition from the special `<none>` state. At least one create action must be available to the user in order for tickets to be created. The create actions defined in the default workflow are:
    107 {{{#!ini
    108 create = <none> -> new
    109 create.default = 1
    110 
    111 create_and_assign = <none> -> assigned
    112 create_and_assign.label = assign
    113 create_and_assign.permissions = TICKET_MODIFY
    114 create_and_assign.operations = may_set_owner
    115 }}}
    116 
    117 
    118 There is one hard-coded constraints to the workflow: tickets are expected to have a `closed` state. The default reports/queries treat any state other than `closed` as an open state.
    119 
    120 The special `_reset` action is added by default for tickets that are in states that are no longer defined. This allows tickets to be individually "repaired" after the workflow is changed, although it's recommended that the administrator perform the action by batch modifying the affected tickets. By default the `_reset` action is available to users with the `TICKET_ADMIN` permission and reset tickets are put in the //new// state. The default `_reset` action is equivalent to the following `[ticket-workflow]` action definition:
    121 
    122 {{{#!ini
    123 _reset = -> new
    124 _reset.label = reset
    125 _reset.operations = reset_workflow
    126 _reset.permissions = TICKET_ADMIN
    127 _reset.default = 0
    128 }}}
    129 
    130 Since [trac:milestone:1.0.3] the `_reset` action can be customized by redefining the implicit action. For example, to allow anyone with `TICKET_MODIFY` to perform the `_reset` action, the workflow action would need to be defined:
    131 
    132 {{{#!ini
    133 _reset = -> new
    134 _reset.label = reset
    135 _reset.operations = reset_workflow
    136 _reset.permissions = TICKET_MODIFY
    137 _reset.default = 0
    138 }}}
    139 
    140 == Workflow Visualization
    141 
    142 Workflows can be visualized by rendering them on the wiki using the [WikiMacros#Workflow-macro Workflow macro].
    143 
    144 Workflows can also be visualized using the `contrib/workflow/workflow_parser.py` script. The script outputs `.dot` files that [http://www.graphviz.org GraphViz] understands. The script can be used as follows (your install path may be different):
    145 
    146 {{{#!sh
    147 cd /var/local/trac_devel/contrib/workflow/
    148 sudo ./showworkflow /srv/trac/PlannerSuite/conf/trac.ini
    149 }}}
    150 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.
    151 
    152 After you have changed a workflow, you need to restart your webserver for the changes to take effect.
    153 
    154 == Example: Adding optional Testing with Workflow
    155 
    156 By adding the following to your [ticket-workflow] section of trac.ini you get optional testing. When the ticket has status `new`, `accepted` or `needs_work`, 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 is 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.
    157 
    158 {{{#!ini
    159 testing = new,accepted,needs_work,assigned,reopened -> testing
    160 testing.label = Submit to reporter for testing
    161 testing.permissions = TICKET_MODIFY
    162 
    163 reject = testing -> needs_work
    164 reject.label = Failed testing, return to developer
    165 
    166 pass = testing -> closed
    167 pass.label = Passes Testing
    168 pass.operations = set_resolution
    169 pass.set_resolution = fixed
    170 }}}
    171 
    172 === How to combine the `tracopt.ticket.commit_updater` with the testing workflow
    173 
    174 The [[trac:source:trunk/tracopt/ticket/commit_updater.py|tracopt.ticket.commit_updater]] is the optional component that [[TracRepositoryAdmin#trac-post-commit-hook|replaces the old trac-post-commit-hook]], in Trac 0.12.
    175 
    176 By default it reacts on some keywords found in changeset message logs like ''close'', ''fix'' etc. and performs the corresponding workflow action.
    177 
    178 If you have a more complex workflow, like the testing stage described above and you want the ''closes'' keyword to move the ticket to the ''testing'' status instead of the ''closed'' status, you need to adapt the code a bit.
    179 
    180 Have a look at the [[trac:wiki:0.11/TracWorkflow#How-ToCombineSVNtrac-post-commit-hookWithTestWorkflow|Trac 0.11 recipe]] for the `trac-post-commit-hook`, this will give you some ideas about how to modify the component.
    181 
    182 == Example: Add simple optional generic review state
    183 
    184 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.
    185 
    186 The new `reviewing` state along with its associated `review` action looks like this:
    187 
    188 {{{#!ini
    189 review = new,assigned,reopened -> reviewing
    190 review.operations = set_owner
    191 review.permissions = TICKET_MODIFY
    192 }}}
    193 
    194 Then, to integrate this with the default Trac 0.11 workflow, you also need to add the `reviewing` state to the `accept` and `resolve` actions:
    195 
    196 {{{#!ini
    197 accept = new,reviewing -> assigned
    198 […]
    199 resolve = new,assigned,reopened,reviewing -> closed
    200 }}}
    201 
    202 Optionally, you can also add a new action that allows you to change the ticket's owner without moving the ticket out of the `reviewing` state. This enables you to reassign review work without pushing the ticket back to the `new` status:
    203 
    204 {{{#!ini
    205 reassign_reviewing = reviewing -> *
    206 reassign_reviewing.label = reassign review
    207 reassign_reviewing.operations = set_owner
    208 reassign_reviewing.permissions = TICKET_MODIFY
    209 }}}
    210 
    211 The full `[ticket-workflow]` configuration will thus look like this:
    212 
    213 {{{#!ini
    214 [ticket-workflow]
    215 create = <none> -> new
    216 create.default = 1
    217 create_and_assign = <none> -> assigned
    218 create_and_assign.label = assign
    219 create_and_assign.permissions = TICKET_MODIFY
    220 create_and_assign.operations = may_set_owner
    221 accept = new,reviewing -> assigned
    222 accept.operations = set_owner_to_self
    223 accept.permissions = TICKET_MODIFY
    224 leave = * -> *
    225 leave.default = 1
    226 leave.operations = leave_status
    227 reassign = new,assigned,accepted,reopened -> assigned
    228 reassign.operations = set_owner
    229 reassign.permissions = TICKET_MODIFY
    230 reopen = closed -> reopened
    231 reopen.operations = del_resolution
    232 reopen.permissions = TICKET_CREATE
    233 resolve = new,assigned,reopened,reviewing -> closed
    234 resolve.operations = set_resolution
    235 resolve.permissions = TICKET_MODIFY
    236 review = new,assigned,reopened -> reviewing
    237 review.operations = set_owner
    238 review.permissions = TICKET_MODIFY
    239 reassign_reviewing = reviewing -> *
    240 reassign_reviewing.operations = set_owner
    241 reassign_reviewing.label = reassign review
    242 reassign_reviewing.permissions = TICKET_MODIFY
    243 }}}
    244 
    245 == Example: Limit the resolution options for a new ticket
    246 
    247 The above `resolve_new` operation allows you to set the possible resolutions for a new ticket. By modifying the existing resolve action and removing the new status from before the `->` we then get two resolve actions. One with limited resolutions for new tickets, and then the regular one once a ticket is accepted.
    248 
    249 {{{#!ini
    250 resolve_new = new -> closed
    251 resolve_new.label = resolve
    252 resolve_new.operations = set_resolution
    253 resolve_new.permissions = TICKET_MODIFY
    254 resolve_new.set_resolution = invalid,wontfix,duplicate
    255 
    256 resolve = assigned,accepted,reopened -> closed
    257 resolve.operations = set_resolution
    258 resolve.permissions = TICKET_MODIFY
    259 }}}
    260 
    261 == Advanced Ticket Workflow Customization
    262 
    263 If the customizations above do not meet your needs, you can extend the workflow with plugins. Plugins can provide additional operations for the workflow, like code_review, or implement side-effects for an action, such as triggering a build, that may not be merely simple state changes. Look at [trac:source:trunk/sample-plugins/workflow sample-plugins/workflow] for a few examples to get started.
    264 
    265 But if even that is not enough, you can disable the !ConfigurableTicketWorkflow component and create a plugin that completely replaces it.
    266 
    267 == Adding Workflow States to Milestone Progress Bars
    268 
    269 If you add additional states to your workflow, you may want to customize your milestone progress bars as well. See [TracIni#milestone-groups-section TracIni].
    270 
    271 == Ideas for next steps
    272 
    273 Enhancement ideas for the workflow system should be filed as enhancement tickets against the [trac:query:?status=assigned&status=new&status=reopened&keywords=~workflow&component=ticket+system ticket system] component.  You can also document ideas on the [trac:TracIdeas/TracWorkflow TracIdeas/TracWorkflow] page. Also look at the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] as it provides experimental operations.

  • wiki/pages/WikiHtml

    r37567 r37661  
    1 = Using HTML in Wiki Text =
    2 
    3 Trac supports the display of HTML in any wiki context, by using the `#!html` [wiki:WikiProcessors WikiProcessor].
    4 
    5 However, this HTML has to be [http://en.wikipedia.org/wiki/Well-formed_element well-formed].
    6 In particular, you can't insert a start tag in an `#!html` block, resume normal wiki text and insert the corresponding end tag in a second `#!html` block.
    7 
    8 Fortunately, for creating styled <div>s, <span>s  or even complex tables containing arbitrary Wiki text, there is a powerful alternative: `#!div`, `#!span` and `#!table`, `#!tr`, `#!td` and `#!th` blocks. Those Wiki processors are built-in and do not require additional packages to be installed.
    9 
    10 == How to use `#!html` == #HowtoUseHTML
    11 To inform the wiki engine that a block of text should be treated as HTML, use the ''html'' processor:
    12 
    13 ||= Wiki Markup =||= Display =||
    14 {{{#!td
    15   {{{
    16   {{{
    17   #!html
    18   <h1 style="text-align: right; color: blue">HTML Test</h1>
    19   }}}
    20   }}}
    21 }}}
    22 {{{#!td style="padding-left: 2em"
    23   {{{
    24   #!html
    25   <h1 style="text-align: right; color: blue">HTML Test</h1>
    26   }}}
    27 }}}
    28 
    29 Note that Trac sanitizes your HTML code before displaying it. That means that potentially dangerous constructs, such as Javascript event handlers, will be removed from the output.
    30 
    31 The filtering is done by [http://genshi.edgewall.org/ Genshi] and the output will be a well-formed fragment of HTML. This means that you can no longer use two HTML blocks, one for opening a <div> and another for closing it, in order to wrap arbitrary wiki text.
    32 The new way to wrap any wiki content inside a <div> is to use the `#!div` Wiki processor.
    33 
    34 == How to use `#!div` and `#!span` == #HowtoUseDivSpan
    35 
    36 ||= Wiki Markup =||= Display =||
    37 {{{#!td
    38   {{{
    39   {{{
    40   #!div class="important"
    41   **important** is a predefined class.
    42   }}}
    43   }}}
    44   {{{
    45   {{{
    46   #!div style="border: 1pt dotted; margin: 1em"
    47   **wikipage** is another predefined class that will
    48   be used when no class is specified.
    49   }}}
    50   }}}
    51   {{{
    52   {{{
    53   #!div class="compact" style="border: 1pt dotted; margin: 1em"
    54   **compact** is another predefined class reducing
    55   the padding within the `<div>` to a minimum.
    56   }}}
    57   }}}
    58   {{{
    59   {{{
    60   #!div class="wikipage compact" style="border: 1pt dotted"
    61   Classes can be combined (here **wikipage** and **compact**)
    62   which results in this case in reduced //vertical//
    63   padding but there's still some horizontal space for coping
    64   with headings.
    65   }}}
    66   }}}
    67   {{{
    68   {{{
    69   #!div class="" style="border: 1pt dotted; margin: 1em"
    70   Explicitly specifying no classes is //not// the same
    71   as specifying no class attribute, as this will remove
    72   the //wikipage// default class.
    73   }}}
    74   }}}
    75 }}}
    76 {{{#!td style="padding-left: 2em"
    77 
    78   {{{
    79   #!div class="important"
    80   **important** is a predefined class.
    81   }}}
    82 
    83   {{{
    84   #!div style="border: 1pt dotted; margin: 1em"
    85   **wikipage** is another predefined class that will
    86   be used when no class is specified.
    87   }}}
    88 
    89   {{{
    90   #!div class="compact" style="border: 1pt dotted; margin: 1em"
    91   **compact** is another predefined class reducing
    92   the padding within the `<div>` to a minimum.
    93   }}}
    94 
    95   {{{
    96   #!div class="wikipage compact" style="border: 1pt dotted"
    97   Classes can be combined (here **wikipage** and **compact**)
    98   which results in this case in reduced //vertical//
    99   padding but there's still some horizontal space for coping
    100   with headings.
    101   }}}
    102 
    103   {{{
    104   #!div class="" style="border: 1pt dotted; margin: 1em"
    105   Explicitly specifying no classes is //not// the same
    106   as specifying no class attribute, as this will remove
    107   the //wikipage// default class.
    108   }}}
    109 
    110 }}}
    111 
    112 Note that the contents of a `#!div` block are contained in one or more paragraphs, which have a non-zero top and bottom margin. This leads to the top and bottom padding in the example above. To remove the top and bottom margin of the content, add the `compact` class to the `#!div`. Another predefined class besides `wikipage` and `compact` is `important`, which can be used to make a paragraph stand out. Extra CSS classes can be defined via the `site/style.css` file for example, see TracInterfaceCustomization#SiteAppearance.
    113 
    114 For spans, you should use the Macro call syntax:
    115 ||= Wiki Markup =||
    116 {{{#!td
    117   {{{
    118   Hello
    119   [[span(''WORLD'' (click [#anchor here]), style=color: green; font-size: 120%, id=anchor)]]!
    120   }}}
    121 }}}
    122 |---------------------------------------------------------------------------------
    123 ||= Display =||
    124 {{{#!td style="padding-left: 2em"
    125   Hello
    126   [[span(''WORLD'' (click [#anchor here]), style=color: green; font-size: 120%, id=anchor)]]!
    127 }}}
    128 
    129 == How to use `#!td` and other table related processors == #Tables
    130 
    131 The `#!td` or `#!th` processors should be used to create table data and table header cells, respectively. The other processors `#!table` and `#!tr` are not required for introducing a table structure, as `#!td` and `#!th` will do this automatically. The `|-` row separator can be used to start a new row when needed, but some may prefer to use a `#!tr` block for that, as this introduces a more formal grouping and offers the possibility to use an extra level of indentation. The main purpose of the `#!table` and `#!tr` is to give the possibility to specify HTML attributes, like ''style'' or ''valign'' to these elements.
    132 
    133 ||= Wiki Markup =||= Display =||
    134 {{{#!td
    135  {{{
    136  Simple 2x2 table with rich content:
    137  {{{#!th align=left
    138   - Left
    139   - Header
    140  }}}
    141  {{{#!th align=left
    142   - Right
    143   - Header
    144  }}}
    145  |----------------------------------
    146  {{{#!td style="background: #ffd"
    147   - Left
    148   - Content
    149  }}}
    150  {{{#!td style="vertical-align: top"
    151  !RightContent
    152  }}}
    153  |----------------------------------
    154  || ... and this can be mixed||\
    155  ||with pipe-based cells ||
    156  {{{#!td colspan=2
    157  Pick the style the more appropriate
    158  to your content
    159  
    160  See WikiFormatting#Tables for details
    161  on the pipe-based table syntax.
    162  }}}
    163  
    164  If one needs to add some
    165  attributes to the table itself...
    166  
    167  {{{
    168  #!table style="border:none;text-align:center;margin:auto"
    169    {{{#!tr ====================================
    170      {{{#!th style="border: none"
    171      Left header
    172      }}}
    173      {{{#!th style="border: none"
    174      Right header
    175      }}}
    176    }}}
    177    {{{#!tr ==== style="border: 1px dotted grey"
    178      {{{#!td style="border: none"
    179      1.1
    180      }}}
    181      {{{#!td style="border: none"
    182      1.2
    183      }}}
    184    }}}
    185    {{{#!tr ====================================
    186      {{{#!td style="border: none"
    187      2.1
    188      }}}
    189      {{{#!td
    190      2.2
    191      }}}
    192    }}}
    193  }}}
    194 
    195 
    196  }}}
    197 }}}
    198 {{{#!td valign=top
    199 Simple 2x2 table with rich content:
    200 {{{#!th align=left
    201  - Left
    202  - Header
    203 }}}
    204 {{{#!th align=left
    205  - Right
    206  - Header
    207 }}}
    208 |----------------------------------
    209 {{{#!td style="background: #ffd"
    210  - Left
    211  - Content
    212 }}}
    213 {{{#!td style="vertical-align: top"
    214 !RightContent
    215 }}}
    216 |----------------------------------
    217 || ... and this can be mixed||\
    218 ||with pipe-based cells ||
    219 {{{#!td colspan=2
    220 Pick the style the more appropriate
    221 to your content
    222 
    223 See WikiFormatting#Tables for details
    224 on the pipe-based table syntax.
    225 }}}
    226 
    227 If one needs to add some
    228 attributes to the table itself...
    229 
    230 {{{
    231 #!table style="border:none;text-align:center;margin:auto"
    232   {{{#!tr ====================================
    233     {{{#!th style="border: none"
    234     Left header
    235     }}}
    236     {{{#!th style="border: none"
    237     Right header
    238     }}}
    239   }}}
    240   {{{#!tr ==== style="border: 1px dotted grey"
    241     {{{#!td style="border: none"
    242     1.1
    243     }}}
    244     {{{#!td style="border: none"
    245     1.2
    246     }}}
    247   }}}
    248   {{{#!tr ====================================
    249     {{{#!td style="border: none"
    250     2.1
    251     }}}
    252     {{{#!td
    253     2.2
    254     }}}
    255   }}}
    256 }}}
    257 }}}
    258 
    259 Note that by default tables are assigned the "wiki" CSS class, which gives a distinctive look to the header cells and a default border to the table and cells, as can be seen for the tables on this page. By removing this class (`#!table class=""`), one regains complete control on the table presentation. In particular, neither the table nor the rows nor the cells will have a border, so this is a more effective way to get such an effect rather than having to specify a `style="border: no"` parameter everywhere.
    260 
    261 {{{#!table class=""
    262 ||= Wiki Markup =||= Display =||
    263  {{{#!td
    264   {{{
    265   {{{#!table class=""
    266   ||  0||  1||  2||
    267   || 10|| 20|| 30||
    268   || 11|| 22|| 33||
    269   ||||||=  numbers  =||
    270   }}}
    271   }}}
    272  }}}
    273  {{{#!td
    274   {{{#!table class=""
    275   ||  0||  1||  2||
    276   || 10|| 20|| 30||
    277   || 11|| 22|| 33||
    278   ||||||=  numbers  =||
    279   }}}
    280  }}}
    281 }}}
    282 
    283 Other classes can be specified as alternatives (remember that you can define your own in [TracInterfaceCustomization#SiteAppearance site/style.css]).
    284 
    285 ||= Wiki Markup =||= Display =||
    286 {{{#!td
    287   {{{
    288   {{{#!table class="listing"
    289   ||  0||  1||  2||
    290   || 10|| 20|| 30||
    291   || 11|| 22|| 33||
    292   ||||||=  numbers  =||
    293   }}}
    294   }}}
    295 }}}
    296 {{{#!td
    297   {{{#!table class="listing"
    298   ||  0||  1||  2||
    299   || 10|| 20|| 30||
    300   || 11|| 22|| 33||
    301   ||||||=  numbers  =||
    302   }}}
    303 }}}
    304 
    305 == HTML comments ==
    306 HTML comments are stripped from the output of the `html` processor. To add an HTML comment to a wiki page, use the `htmlcomment` processor, available since Trac 0.12:
    307 ||= Wiki Markup =||
    308 {{{#!td
    309   {{{
    310   {{{
    311   #!htmlcomment
    312   This block is translated to an HTML comment.
    313   It can contain <tags> and &entities; that will not be escaped in the output.
    314   }}}
    315   }}}
    316 }}}
    317 |---------------------------------------------------------------------------------
    318 ||= Display =||
    319 {{{#!td
    320   {{{
    321   <!--
    322   This block is translated to an HTML comment.
    323   It can contain <tags> and &entities; that will not be escaped in the output.
    324   -->
    325   }}}
    326 }}}
    327 
    328 Please note that the character sequence "`--`" is not allowed in HTML comments, and will generate a rendering error.
    329 
    330 
    331 == More Information ==
    332 
    333  * http://www.w3.org/ -- World Wide Web Consortium
    334  * http://www.w3.org/MarkUp/ -- HTML Markup Home Page
    335 
    336 ----
    337 See also:  WikiProcessors, WikiFormatting, WikiRestructuredText

  • wiki/pages/WikiMacros

    r37567 r37661  
    1 = Trac Macros
    2 
    3 [[PageOutline]]
    4 
    5 Trac macros are plugins to extend the Trac engine with custom 'functions' written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting. Its syntax is `[[macro-name(optional-arguments)]]`.
    6 
    7 The WikiProcessors are another kind of macros. They typically deal with alternate markup formats and transformation of larger "blocks" of information, like source code highlighting. They are used for processing the multiline `{{{#!wiki-processor-name ... }}}` blocks.
    8 
    9 == Using Macros
    10 
    11 Macro calls are enclosed in two ''square brackets'' `[[..]]`. Like Python functions, macros can also have arguments, a comma separated list within parentheses `[[..(,)]]`.
    12 
    13 === Getting Detailed Help
    14 
    15 The list of available macros and the full help can be obtained using the !MacroList macro, as seen [#AvailableMacros below].
    16 
    17 A brief list can be obtained via `[[MacroList(*)]]` or `[[?]]`.
    18 
    19 Detailed help on a specific macro can be obtained by passing it as an argument to !MacroList, e.g. `[[MacroList(MacroList)]]`, or, more conveniently, by appending a question mark (`?`) to the macro's name, like in `[[MacroList?]]`.
    20 
    21 === Example
    22 
    23 A list of the 3 most recently changed wiki pages starting with 'Trac':
    24 
    25 ||= Wiki Markup =||= Display =||
    26 {{{#!td
    27   {{{
    28   [[RecentChanges(Trac,3)]]
    29   }}}
    30 }}}
    31 {{{#!td style="padding-left: 2em;"
    32 [[RecentChanges(Trac,3)]]
    33 }}}
    34 |-----------------------------------
    35 {{{#!td
    36   {{{
    37   [[RecentChanges?(Trac,3)]]
    38   }}}
    39 }}}
    40 {{{#!td style="padding-left: 2em;"
    41 [[RecentChanges?(Trac,3)]]
    42 }}}
    43 |-----------------------------------
    44 {{{#!td
    45   {{{
    46   [[?]]
    47   }}}
    48 }}}
    49 {{{#!td style="padding-left: 2em"
    50 {{{#!html
    51 <div style="font-size: 80%" class="trac-macrolist">
    52 <h3><code>[[Image]]</code></h3>Embed an image in wiki-formatted text.
    53 
    54 The first argument is the file …
    55 <h3><code>[[InterTrac]]</code></h3>Provide a list of known <a class="wiki" href="/wiki/InterTrac">InterTrac</a> prefixes.
    56 <h3><code>[[InterWiki]]</code></h3>Provide a description list for the known <a class="wiki" href="/wiki/InterWiki">InterWiki</a> prefixes.
    57 <h3><code>[[KnownMimeTypes]]</code></h3>List all known mime-types which can be used as <a class="wiki" href="/wiki/WikiProcessors">WikiProcessors</a>.
    58 Can be …</div>
    59 }}}
    60 etc.
    61 }}}
    62 
    63 == Available Macros
    64 
    65 ''Note that the following list will only contain the macro documentation if you've not enabled `-OO` optimizations, or not set the `PythonOptimize` option for [wiki:TracModPython mod_python].''
    66 
    67 [[MacroList]]
    68 
    69 == Macros from around the world
    70 
    71 The [http://trac-hacks.org/ Trac Hacks] site provides a wide collection of macros and other Trac [TracPlugins plugins] contributed by the Trac community. If you are looking for new macros, or have written one that you would like to share with the world, don't hesitate to visit that site.
    72 
    73 == Developing Custom Macros
    74 
    75 Macros, like Trac itself, are written in the [http://python.org/ Python programming language] and are developed as part of TracPlugins.
    76 
    77 For more information about developing macros, see the [trac:TracDev development resources] on the main project site.
    78 
    79 Here are 2 simple examples showing how to create a Macro. Also, have a look at [trac:source:tags/trac-1.0.2/sample-plugins/Timestamp.py Timestamp.py] for an example that shows the difference between old style and new style macros and at the [trac:source:tags/trac-0.11/wiki-macros/README macros/README] which provides a little more insight about the transition.
    80 
    81 === Macro without arguments
    82 
    83 To test the following code, you should saved it in a `timestamp_sample.py` file located in the TracEnvironment's `plugins/` directory.
    84 {{{
    85 #!python
    86 from datetime import datetime
    87 # Note: since Trac 0.11, datetime objects are used internally
    88 
    89 from genshi.builder import tag
    90 
    91 from trac.util.datefmt import format_datetime, utc
    92 from trac.wiki.macros import WikiMacroBase
    93 
    94 class TimeStampMacro(WikiMacroBase):
    95     """Inserts the current time (in seconds) into the wiki page."""
    96 
    97     revision = "$Rev$"
    98     url = "$URL$"
    99 
    100     def expand_macro(self, formatter, name, text):
    101         t = datetime.now(utc)
    102         return tag.strong(format_datetime(t, '%c'))
    103 }}}
    104 
    105 === Macro with arguments
    106 
    107 To test the following code, you should save it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory.
    108 {{{
    109 #!python
    110 from genshi.core import Markup
    111 
    112 from trac.wiki.macros import WikiMacroBase
    113 
    114 class HelloWorldMacro(WikiMacroBase):
    115     """Simple HelloWorld macro.
    116 
    117     Note that the name of the class is meaningful:
    118      - it must end with "Macro"
    119      - what comes before "Macro" ends up being the macro name
    120 
    121     The documentation of the class (i.e. what you're reading)
    122     will become the documentation of the macro, as shown by
    123     the !MacroList macro (usually used in the WikiMacros page).
    124     """
    125 
    126     revision = "$Rev$"
    127     url = "$URL$"
    128 
    129     def expand_macro(self, formatter, name, text, args):
    130         """Return some output that will be displayed in the Wiki content.
    131 
    132         `name` is the actual name of the macro (no surprise, here it'll be
    133         `'HelloWorld'`),
    134         `text` is the text enclosed in parenthesis at the call of the macro.
    135           Note that if there are ''no'' parenthesis (like in, e.g.
    136           [[HelloWorld]]), then `text` is `None`.
    137         `args` are the arguments passed when HelloWorld is called using a
    138         `#!HelloWorld` code block.
    139         """
    140         return 'Hello World, text = %s, args = %s' % \
    141             (Markup.escape(text), Markup.escape(repr(args)))
    142 
    143 }}}
    144 
    145 Note that `expand_macro` optionally takes a 4^th^ parameter ''`args`''. When the macro is called as a [WikiProcessors WikiProcessor], it's also possible to pass `key=value` [WikiProcessors#UsingProcessors processor parameters]. If given, those are stored in a dictionary and passed in this extra `args` parameter. On the contrary, when called as a macro, `args` is  `None`. (''since 0.12'').
    146 
    147 For example, when writing:
    148 {{{
    149 {{{#!HelloWorld style="polite" -silent verbose
    150 <Hello World!>
    151 }}}
    152 
    153 {{{#!HelloWorld
    154 <Hello World!>
    155 }}}
    156 
    157 [[HelloWorld(<Hello World!>)]]
    158 }}}
    159 One should get:
    160 {{{
    161 Hello World, text = <Hello World!> , args = {'style': u'polite', 'silent': False, 'verbose': True}
    162 Hello World, text = <Hello World!> , args = {}
    163 Hello World, text = <Hello World!> , args = None
    164 }}}
    165 
    166 Note that the return value of `expand_macro` is '''not''' HTML escaped. Depending on the expected result, you should escape it by yourself (using `return Markup.escape(result)`) or, if this is indeed HTML, wrap it in a Markup object (`return Markup(result)`) with `Markup` coming from Genshi, (`from genshi.core import Markup`). 
    167 
    168 You can also recursively use a wiki Formatter (`from trac.wiki import Formatter`) to process the `text` as wiki markup:
    169 
    170 {{{
    171 #!python
    172 from genshi.core import Markup
    173 from trac.wiki.macros import WikiMacroBase
    174 from trac.wiki import Formatter
    175 import StringIO
    176 
    177 class HelloWorldMacro(WikiMacroBase):
    178     def expand_macro(self, formatter, name, text, args):
    179         text = "whatever '''wiki''' markup you want, even containing other macros"
    180         # Convert Wiki markup to HTML, new style
    181         out = StringIO.StringIO()
    182         Formatter(self.env, formatter.context).format(text, out)
    183         return Markup(out.getvalue())
    184 }}}

  • wiki/pages/de/CPU

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.7.8.6.1 CPU''' [=#point3.7.8.6.1] ([wiki:System-Infos#point3.7.8.6 System Infos (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can view the detailed cpu info.
    10 
    11 [[br]]
    12 
    13 
    14 [[br]]

  • wiki/pages/de/Channel-Service

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.1 Channel Service''' [=#point3.5.1] ([wiki:Interface-Operation#point3.5 zurück)])
    4 >
    5 >[[Image(source:/wiki/Wiki-Pictures/DE/system-Channel_Service.jpg)]][[BR]]
    6 >
    7 Hier werden die Tuner eingestellt und ein Programmsuchlauf durchgeführt
    8 [[br]]
    9 
    10  * ([wiki:Tuner-Configuration#point3.5.1.1 Tuner Konfiguration])
    11  * ([wiki:Automatic-Search#point3.5.1.2 Automatische Suche])
    12  * ([wiki:Manual-Search#point3.5.1.3 Manuelle Suche])
    13  * ([wiki:Rotor-Settings#point3.5.1.4 Rotor])
    14  * ([wiki:Sat-Finder#point3.5.1.5 Sat Finder])
    15  * ([wiki:Blind-Scan-Settings#point3.5.1.6 Blind Scan])
    16  * ([wiki:Create-Transponder-List#point3.5.1.7 Create Transponder List])
    17  * ([wiki:Create-Default-Favorites#point3.5.1.8 Create Default Favorites])
    18 
    19 
    20 [[br]]
    21 

  • wiki/pages/de/Child-Protection

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.6.12 Child Protection''' [=#point3.6.12] ([#point3.6 Settings (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/Child_Protection.jpg)]][[BR]]
    8 >
    9 > here you can setup your key lock and child portection settings.
    10 
    11 [[br]]
    12 
    13 
    14  ||'''Pin Code Menu''' ||Select the pin code used in the menu.||
    15  ||'''Pin Code Channel:''' || select the pin code used to lock TV Channels.||
    16  ||'''Protect Channels:''' || Do you wish to enable the locking of protected channels.||
    17  ||'''Age Protect:''' || do you wish to protect channels based on age restrictions.||
    18  ||'''Protect Channel Freetime (min''' || After a specific time do you wish to re-enable the lock  on protected channels if it is currently beign displayed.||
    19  ||'''Protect menu:''' || Do you wish to place a lock on the menu of the reciever.||
    20  
    21  To __"Store"__ the settings Exit from the Child Protection Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    22  
    23 [[br]]
    24 ----
    25 
    26  '''Coloured Button's Functions"
    27 
    28  The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the cchild protection settings menu
    29  please see below for more info on the functions of these buttons:.
    30  
    31  ||'''Red Button: (Menu Protect)''' ||pressing this button will bring up a list of menu items that a lock may be placed on to limit access to those areas, below is a list of all the menu items displayed in this menu.||
    32 
    33  * Soft Cam Pannel
    34  * Records and EPG
    35  * Media Center
    36  * Media Player
    37  * Extentions
    38  * System
    39  * Settigs
    40  * Information
    41  * Standby/ Poweroff
    42  * Main Menu
    43  * Media Center
    44  * GUI Restart
    45  * Power Off
    46  * Network Restart
    47  * A/V Settings
    48  * Adjust
    49  * Skin
    50  * Plugins
    51  * Records
    52  * EPG Search
    53  * Common Interface
    54  * Smart Card Reader
    55  * Flash Update Online
    56  * Child Protection
    57  * Service
    58  * Sat Finder
    59  * Epg Short View
    60  * Single Epg
    61  * Multi Epg
    62  * Graphic Epg
    63  * EPG Search
    64  * Records
    65  * Plugins
    66  * Change Feed
    67  * TPK Upgrade (Online)
    68  * TPK Install (Online)
    69  * TPK Tmp (tmp)
    70  * TPK Media (media)
    71  * TPK (remove
    72  * Channel Service...
    73  * Common Interface
    74  * Smart Card Reader
    75  * Network
    76  * Harddisk
    77  * VFDisplay
    78  * Fancontrol
    79  * System Update
    80  * Backup
    81  * Settings Backup Restore
    82  * Receiver Unlock
    83  * A/V Settings
    84  * Language
    85  * Timezone
    86  * Red Button
    87  * Blue Button
    88  * Plugin Button
    89  * Adjust
    90  * Skin Adjust
    91  * Screensaver adjust
    92  * Timeshift Settings
    93  * Record Path
    94  * EPG Settings
    95  * Child Protection
    96  * Restore Default Settings
    97  * Video Settings
    98  * Channel Edit
    99  * MediaDB Settings
    100  * Autostart Settings
    101  * Overclocking Settings
    102  * Save Settings
    103  * Service
    104  * Newsletter
    105  * About
    106  * Streaming
    107  * Atemio (hotline)
    108  * Titan Changelog
    109  * GIT Changelog
    110  * System Info
    111  * Log
    112  * System_Status
    113  * Free Space
    114  * kernel
    115  * Mounts
    116  * Network
    117  * Ram
    118  * System Infos
    119  * Cpu
    120  * Memory
    121  * MTD
    122  * Module
    123  * Devices
    124  * Swap
    125  * Top
    126  * Prozesslist
    127  * USB
    128  * Flashupdate (online)
    129  * Flashupdate (tmp)
    130  * USBupdate (online)
    131  * USBupdate (tmp)
    132  * Power off
    133  * Standby
    134  * Restart
    135  * GUI Restart
    136  * Power Off Timer
    137  * Tuner Configuration
    138  * Automatic Search
    139  * Manual Search
    140  * Manual Search Cable
    141  * Manual Search Terrestrial
    142  * Rotor Settings
    143  * Sat Config
    144  * Sat Finder
    145  * Blind scan settings
    146  * Formatt HDD
    147  * Filesystem Check
    148  * Configure
    149  * Time to Sleep
    150  * Adapter Settings
    151  * WLAN Settings

  • wiki/pages/de/Child-Safety

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.18.5 Jugendschutz''' [=#point3.5.18.5] ([wiki:Auto-Start-Settings#point3.5.18 zurück])
    4 >
    5 >
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/Autostart_Settings-child_safety.jpg)]][[br]]
    8 >
    9 
    10 [[br]]
    11 
    12  ||'''Jugendschutz:''' ||aktiviert den Jugendschutz PIN beim Systemstart .||
    13  ||'''Pin:''' ||bestimmt den Schutzkode beim Sytemstart.||
    14  
    15  um die Einstellungen zu speichern und das Menü zu verlassen drücken Sie __"OK"__ oder __"Exit"__ um die Änderungen zu verwerfen.
    16  
    17 [[br]]

  • wiki/pages/de/Common-Interface

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.2 Common Interface''' [=#point3.5.2] ([wiki:Interface-Operation#point3.5 System (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/system-Common_Interface.jpg)]][[BR]]
    8 >
    9 >here you can set up your installed cam devices.
    10 
    11 [[br]]
    12 
    13  Picture:
    14  ||'''Module Type:''' ||Set the module service type (multiple/ Single Service).||
    15 
    16   To __"Store"__ the settings Exit from the Common Interface Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    17  
    18 [[br]]
    19 ----
    20 
    21  '''Coloured Button's Functions"
    22 
    23  The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the Commom Interface menu.
    24  please see below for more info on the functions of these buttons:.
    25  
    26  ||'''Red Button: (Reset)''' ||This will reset the selected Common Interface Module.||
    27  ||'''Green Button: (Menu)''' ||This will Bring up the advanced Common Interface menu.||
    28  ||'''Yellow Button: (CAID)''' ||???.||
    29  ||'''Blue Button: (Channel)''' ||Select the channels the selected CA Module will Decode.||
    30  ||'''Menu Button: (Setting)''' ||This will show the settings for the selected CA Module.||
    31 
    32 

  • wiki/pages/de/Community

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''14 Community''' [=#point14] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 ----
    5 Hilfe und Unterstützung können Sie in unserem AAF Digital HD Forum erhalten.
    6 
    7 ||= '''[http://www.aaf-digital.info/forum/forum.php AAF Digital Forum]''' =||
    8 ||= [[Image(http://www.aaf-digital.info/images/logo.jpg,400,link=http://www.aaf-digital.info/forum/forum.php)]] =||
    9 
    10 Download locations[http://atemio.dyndns.tv/nightly-images/ Index of /nightly-images][[br]] [http://www.aaf-digital.info/forum/downloads.php?do=cat&id=2 Stable Images] [http://www.aaf-digital.info/forum/pages.php?pageid=12 Nightly Images][[br]] 
    11 [[br]]
    12 
    13 Historie AAF Board
    14 
    15     Das AAF Board ging am 10 Juni 2007 online und wurde durch Spendengelder aus dem Team und später zusätzlich durch deren Member mit finanziert.
    16 
    17    
    18     Hier eine kleine Historie wie sich ab Früjahr 2005 -2007 Images entwickelt haben.
    19 
    20     Jedes Image ist auf Basis eines aktuellen CVS aufgebaut. Ab dem Racing2 wurde verstärkt auf Online-Updatefähigkeit Wert gelegt und intensiv weiter entwickelt!
    21 
    22     Übersicht der Images:
    23 
    24     - 13.04.2005 andys camd3 Image
    25     - 05.05.2005 Beginner Image
    26     - 07.07.2005 Andy and Friends1 Image inclusive Frontprozessor 1.6
    27     - 15.07.2005 Andy and Friends2 Image
    28     - 24.11.2005 Andy and Friends3 Image Einführung des Webinterface SHQ
    29     - 24.12.2005 Weihnachtsimage
    30     - 01.02.2006 Italia Image
    31     - 11.03.2006 Andy and Friends4 Image
    32     - 31.03.2006 Olympia Image Webinterface
    33     - 16.04.2006 Osterimage Neueinführung Installer für Scripte
    34     - 23.04.2006 Racing 2 Einführung Addon-Manager und Downloadserver für Plugins
    35     - 19.06.2006 WM Image
    36     - 07.10.2006 Buli Image Einführung makeaaf und Softwareaktualisierung
    37     - 24.12.2006 Merry Christmas Erweiterung Addon-Manager, Bootlogos, Skinvorschau
    38     - 12.03.2007 Serverimage wegen Boardwechsel
    39     - 10.06.2007 Serverimage wegen Boardwechsel
    40     - 21.07.2007 aaf SciFi Image ( Dreambox 7020), Cryptanzeige, EMUanzeige und vieles mehr.
    41 
    42 
    43 
    44     Hier eine Übersicht aus Joshuas Skins:
    45 
    46     - 14.04.2006 Osterskin
    47     - 26.04.2006 Formel1 Skin
    48     - 20.04.2006 AAF Basis Skin
    49     - 30.04.2006 Joshua 3D Skin
    50     - 26.05.2006 WM Skin
    51     - 19.08.2006 Buli Skin
    52     - 01.12.2006 Weihnachstskin
    53     - 21.07.2007 SciFi Skin
    54 
    55     Weitere Ereignisse:
    56     - 21.10.2006 Handbuch AAF Image
    57     - 18.06.2006 AAF Webseite
    58 
    59 
    60     - Webinterface
    61     - AAF ADDON Manager ( extra Historie)
    62     - AAF Installer
    63     - Switchemu mod ren_hoeck Prinz
    64     - EMU Installer
    65     - AAF Infoanzeige
    66     - Mp3 Radio Liste jesko
    67     - AAF Bouquets Speaker
    68     - Satellites_XML (SES-XML) 27.06.07 Reinh@rd
    69     - Satellites Online Updater 31.08.07 Bauernbub
    70     - AAF-FORUM Skin 180807 MBoy
    71     - Full Gold ein Skin zwei Versionen 310807 MBoy
    72     - AAF-DreamBox7000S Skin Sonderversion 07.09.07 MBoy
    73     - Neues Dreambox Tool aus der Soft und Skinfabrik 12.10.07 MBoy
    74     - UPDATE ALL SKIN EXE V1.05 181007 MBoy
    75     - AAF Animations Weihnachts und Silvester Skin 22.11.07 MBoy
    76     - AAF X-Mas Skin 2007 18.12.07 Joshua
    77     - AAF Xmas 500 Image2007 22.12.07
    78 
    79 
    80 
    81     Historie 2008 - 2010:
    82 
    83 
    84     - AAF Kathrein Image 1.3 = 27.01.2008 16:46
    85     - AAF-Image 1.4a für UFS910 = 16.03.2008 14:45
    86     - AAF Kathrein Image 1.5 = 11.05.2008 23:51
    87     - AAF2.0 EM Edition 2008 = 19.06.2008 20:40
    88     - All In One 1.0
    89     - AAF 2.0d-1W/14W fix2 = 31.08.2008 20:38
    90     - AAF Kathrein Image 2.0e all Version = am: 05.10.2008 19:24
    91     - AAF 3.0 Kathrein Image = 14.05.2009 19:06
    92     - AAF 3.0 Beta ver.1.07 Ba = 16.05.2009 20:51
    93 
    94     Bei über 5000 Downloads vom All In One Paket 1.0:
    95     - 2093 mal Kathrein1.06 All In One 1.0 Paket
    96     - 532 mal AAF2.0d 14W All In One 1.0 Paket
    97     - 2689 mal AAF2.0d 1W All In One 1.0 Paket
    98 
    99     nach dem e2 TDT
    100     - Enigma 2 Alpha = am: 27.07.2008 07:34
    101 
    102 
    103     04.09.2008
    104     - rev210 bild bleibt nach 60min stehen, ufs hängt sich auf (gelöst)
    105 
    106     kam das hier:
    107 
    108     - AAF_NEW_YEAR_2009_Flash-Image = 02.01.2009 19:22
    109     - AAF Sussex 5.384 Flash Image = 08.03.2009 23:02
    110     - AAF Black Pearl E2 Flash Image m569 = 13.04.2009 23:11
    111     - AAF Enterprise Flashimage = 25.05.2009 19:42
    112     - AAF Enterprise - The Next Generation E2 Flash = 11.06.2009 23:14
    113     - AAF Summer Dream E2 Flash Image = 23.08.2009 23:56
    114     - AAF_RISING_SUN_UFS910 = 05.07.2009 19:00
    115     - AAF_Last_Summer_Dream = am: 03.10.2009 14:31
    116     - AAF Indian Summer E2 = am: 08.11.2009 22:20
    117     - AAF Weihnachtsimage = am: 23.12.2009 06:54
    118     - AAF Winterimage = am: 18.01.2010 01:57
    119     - AAF_Olympiaimage = am: 12.02.2010 23:54
    120     - AAF Formel1 Image = am: 14.03.2010 01:24
    121     - AAF Osterimage = am: 05.04.2010 22:59
    122     - AAF Osterimage V2 = am: 11.04.2010 00:55
    123     - AAF_The_Spirit_of_Spring = am: 13.05.2010 02:24
    124     - AAF WM 2010 Image = am: 09.06.2010 19:36
    125     - AAF WM-ImageV2 = am: 03.07.2010 13:47
    126     - AAF_Hot_Summer = am: 11.08.2010 15:59
    127     - AAF Hot Summer-V2 = am: 05.09.2010 21:10
    128     - AAF_MME = am: 24.12.2010 17:54
    129 
    130     Am Anfang wurden hier im Board Dream Multimedia und deren Dreamboxen mit unserem AAF - Images unterstützt.
    131     Im neuem Zeitalter von HD Inhalten, konnte Dream Multimedia keine eigene HD Box rechtzeitig auf den Markt bringen und wir entschieden uns die Kathrein UFS 910 Box zu unterstützen mit einigen AAF Erweiterungen.
    132 
    133     Historie 2011 - 2014:
    134 
    135     - AAF WM Image V2 M352x rev109x am 11.02.2011
    136     - AAF Hot Summer Image V2 M3927 rev1172 am 11.02.2011
    137     - AAF Multimedia Edition Image 25 am 11.02.2011
    138     - AAF MultiMedia Edition V2 M5881 GIT 18870 am 25.02.2011
    139     - AAF MediaCenter Spring Edition M7347 rev2038 am 25.04.2011
    140     - AAF Enigma2 Summer Image M9052 g2671 am 28.08.2011
    141     - AAF Serverwechsel Image am 07.11.2011
    142     - AAF Serverwechsel Image V2 M12340 g3273 am 12.01.2012
    143     - AAF Don't Cry Image M15000 g3650 am 15.04.2012
    144 
    145     - tiTan_pre_Alpha AAF am 03.10.2011
    146     - tiTan pre Alpha v1.2a am 10.10.2011
    147     - TitanNit für UFS-910 Release am 10.09.2012
    148     - u.s.w. aktuelles Image
    149     - TitanNit Image Edition M30082 Version 1.55
    150 
    151     Angefangen mit Titan hat es im April 2011 mit unserem Developer Nit, der still und heimlich Wochen lang am Grundstein für Titan gearbeitet hatte.
    152     Nach der Vorstellung von Titan ist Obi und der Rest vom Team dazu gekommen. Viele halfen bei der Entwicklung von Titan mit und brachten sich mit ein.
    153     Als im Dezember 2011 dann eine halbjährige Vereinbarung mit dem Hersteller Atemio getroffen wurde, trennten sich zum 2.mal einige vom AAF Board. Nach der Trennung vom BPather im Juli 2011 und deren Boardgründung das BPanther Neutrino Forum, entstand aus einigen AAF Teammitgliedern am 03.05.2012 das HDMU Board die weiterhin an einem e2 Image für die sh4 Boxen arbeiten.
    154     2012 gab es zusätzlich zu der TitanNit Firmware das OPEN AAF Images für 21 Mipsel Receiver. Auf Wunsch vom Open AAF Team trennten sich die Wege am 03.04.2013 und es entstand das open atv Team mit einem eigenem Board OPEN ATV.
    155 
    156     TitanNit gibt es mittlerweile für fast alle sh4 Boxen die wir damals im AAF Board mit e2 angeboten hatten.
    157     Nur die Topfield 7700 fehlt noch, da sie nicht genügend Flashspeicher besitzt.
    158     Dann sind jede Menge neue Boxen dazu gekommen, Atemio Nemesis, UFS913, Atemio 520, Atemio 5200 und auch bald die Atemio 6000.
    159     Diese Boxen unterstützen DVB-C, DVB-T und DVB-S(2). Die neueren Modelle auch die mipsel Architektur.
    160 
    161     Die TitanNit Firmware läuft auf folgende Boxen:
    162     UFS 910, UFS 922, UFS 912, UFS 913, Atevio 700, Atevio 7000, Atevio 7500,
    163     Atemio 7600, Atemio 500, Atemio 510, Atemio 520, Atemio 5200, Atemio NEMESIS,
    164     IP Box 91, IP Box 910, IP Box 900, IP Box 9000, Atemio 6000, Atemio 6100, Atemio 6200
    165     und auf baugleiche Boxen wo eine Freischaltung vorliegt bzw. angeboten wird.
    166 
    167     Unser Board ist wie eine Stammkneipe, Stammrestaurant oder Stammcafé.
    168     Hier ist immer was los, positiv wie auch negativ gesehen, eben wie im wahren Leben.
    169     Es gibt Tipps, Tricks, Beistand, Hilfe, Unterhaltung, Freude, Freundschaften, Aktionen, einfach nur Zeitvertreib und vieles mehr.
    170 
    171     So soll es bleiben, schaut mal wieder rein.
    172    
    173     Euer AAF Team [http://www.aaf-digital.info/forum/forum.php AAF Digital HD Forum]
    174 
    175 
    176 
    177 
    178 
    179 [[br]]

  • wiki/pages/de/Configure

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''File system Check''' [=#point3.50.5.3] ([wiki:Hard-Disk#point3.5.5 hard disk (Back)])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can configure your harddisk select an item and follow tht onscreen prompts.
    10 Note that you must enable ([wiki:Adjust#point3.6.7 Expertmode]) to show all available configure options in this display.
    11 [[br]]
    12 
    13 [[br]]
    14 
    15  ||'''Use as recordings-device''' ||Prepair the storage device for use as a recording medium.||
    16  ||'''Remove recordings-device''' ||disable the use of the storage device as a recording medium.||
    17  ||'''Use as plugins-device''' ||Prepair the storage device for use as a plugins medium.||
    18  ||'''Remove extentions-device''' ||disable the use of the storage device as a extentions medium.||
    19  ||'''Use as swap-device''' ||Prepair the storage device for use as a swap medium.||
    20  ||'''Remove swap-device''' ||disable the use of the storage device as a swap medium.||
    21  ||'''Use as backup-device''' ||Prepair the storage device for use as a backup medium.||
    22  ||'''Remove backup-device''' ||disable the use of the storage device as a backup medium.||
    23 
    24 
    25 
    26  
    27  To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    28  
    29 
    30 
    31 [[br]]

  • wiki/pages/de/Contact

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''15 Kontakt''' [=#point15] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 ----
    5 
    6 Interessierte Externe Developer oder Tester können sich gerne via Skype bei uns melden.
    7 
    8  * Skype Chat: "TitanNit Dev Chat"
    9  * Skype Ansprechpartner: obiwan1976
    10 [[br]]
    11 [[br]]

  • wiki/pages/de/Create-Default-Favorites

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.1.8 Create Default Favorites[=#point3.5.1.8] ([wiki:Channel-Service#point3.5.1 Channel-Service (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 >
    5 >
    6 >[[Image(source:/wiki/Wiki-Pictures/DE/Create-Default-Favorites.jpg)]][[br]]
    7 >
    8 By selecting this option it will setup the default german favourites lists.
    9 
    10 Please note that selecting this button will remove all the user pre programmed in favourites.
    11 
    12 in future it may be able to set up favourite lists from the satellites/ providers programed into the tuner.
    13 
    14    
    15  To __"Store"__ the settings by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    16 

  • wiki/pages/de/Create-Transponder-List

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.1.7 Create Transponder List''' [=#point3.5.1.7] ([wiki:Channel-Service#point3.5.1 Channel-Service (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 >
    5 >
    6 >[[Image(source:/wiki/Wiki-Pictures/de/Create-Transponder-List.jpg)]][[br]]
    7 >
    8 Here you can automatically set up transponders for various services from the TitanNit online repo this will save you from having to manually create these lists from your pc or from a satellite xml generator, this will greatly simpifly channel and tuner setup.
    9 
    10 please note that these lists may be out dated and not contain a complete list of transponders for every service.
    11 
    12 [[br]]
    13 
    14  ||'''Create Transponder (Sat) ''' ||Downloads a list of current transponders from the online repo for all available satellites services. ||
    15  ||'''Create Transponder (Cable) ''' ||Downloads a list of current transponders from the online repo for all available cable services. ||
    16  ||'''Create Transponder (Terrestrial) ''' ||Downloads a list of current transponders from the online repo for all available Terrestrial services. ||
    17  ||'''Create Transponder (All) ''' ||Downloads a list of current transponders from the online repo for all available services. ||
    18 
    19 Please note that selecting one of the above options will remove all the transponders from the current channel data and may remove any custom satellite configs and tuner settings.
    20 
    21 in future it may merge the current programmed in user assigned transponders.
    22 
    23 A rescan will need to be preformed after preforming an option be sure to make a backup before proforming this action to be safe.
    24  
    25    
    26  To __"Store"__ the settings by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    27 

  • wiki/pages/de/DYNDNS-Settings

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.4.7 DYNDNS Settings''' [=#point3.5.4.7] ([wiki:Network#point3.5.4 network (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can setup your DYNDNS interface.
    10 
    11 [[br]]
    12 
    13  ||'''Start on Boot:''' ||Start the DYNDNS server on startup.||
    14  ||'''User:''' ||setup the username for DYNDNS.||
    15  ||'''Password:''' ||Set the password for DYNDNS.||
    16  ||'''DNS NAME:''' ||set the dns name.||
    17  ||'''DNS Syatem:''' ||???.||
    18  
    19  To __"Store"__ the settings Exit from the Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    20  
    21 [[br]]
    22 ----
    23 
    24  '''Coloured Button's Functions"
    25 
    26  The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
    27  please see below for more info on the functions of these buttons:.
    28  
    29  ||'''Text Button: (Keyboard)''' ||This will will bring up editor to edit a value or text string.||
    30  ||'''Green Button: (Start)''' ||Start the DYNDNS server.||
    31  ||'''Yellow Button: (Stop)''' ||Stop the DYNDNS server.|| ||

  • wiki/pages/de/Default-Autostart

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.18.1 Allgemein''' [=#point3.5.18.1] ([wiki:Auto-Start-Settings#point3.5.18 zurück)])
    4 >
    5 >
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/Autostart_Settings-default_Autostart.jpg)]][[br]]
    8 >
    9 
    10 [[br]]
    11 
    12  ||'''Startabbruch:''' ||???.||
    13  ||'''Debug:''' ||Hier wird der Debug Modus und die Debug Art aktiviert um Fehler besser eingrenzen zu können.||
    14  ||'''Zeige IP Adresse:''' || ??? ||
    15  ||'''Update Liste:''' ||??.||
    16  
    17 Um die gemachten Einstellungen zu speichern und das Menü zu verlassen drücken Sie __"OK"__ oder __"Exit"__ um die Änderungen zu verwerfen.
    18  

  • wiki/pages/de/Development

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''11 Entwicklung''' [=#point11] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([wiki:WikiStart#point0 Sprachauswahl])
    4 
    5 ----
    6 
    7 
    8 == Skins Bauen am PC ==
    9 
    10 Um den skinnern das leben zu erleichtern habe ich mal das aktuelle titan als VMWARE image zusammen gestellt.
    11 
    12 
    13 ''' Vorschau Video '''
    14 
    15 [http://beta.dyndns.tv/dev-tools/play_titan_ubuntu_fb.htm Ubuntu TitanNit mit aktivierten Framebuffer]
    16 [http://beta.dyndns.tv/dev-tools/play_titan_ubuntu_nofb.htm Ubuntu TitanNit ohne Framebuffer]
    17 
    18 
    19 ''' Download '''
    20 
    21 [http://beta.dyndns.tv/dev-tools/TitanNit_r31365_titandev_VMware_Player_Ubuntu_14.04_mini_32bit.rar TitanNit_r31365_titandev_VMware_Player_Ubuntu_14.0 4_mini_32bit]
    22 
    23 
    24 ''' User Daten '''
    25 
    26 {{{
    27 user: titandev
    28 pass: titandev
    29 }}}
    30 
    31 
    32 ''' Benutzung '''
    33 
    34 {{{
    35 1. vmware player installieren
    36 2. image laden
    37 3. image starten
    38 4. am ubuntu anmelden user: titandev pass: titandev
    39 5. titan starten mit befehl: start.sh
    40 6. passwort eingeben
    41 }}}
    42 
    43 
    44 ''' Steuerung '''
    45 
    46 {{{
    47 ok = enter
    48 exit = esc
    49 tvradio= c
    50 up= <pfeil hoch>
    51 down= <pfeil runter>
    52 left= <pfeil links>
    53 right= <pfeil rechts>
    54 menu= m
    55 ff=  .
    56 fr= ,
    57 volup= +
    58 voldown= -
    59 mute= s
    60 red= <f1>
    61 green= <f2>
    62 yellow= <f3>
    63 blue= <F4>
    64 play= p
    65 record= r
    66 info= i
    67 text= t
    68 power= x
    69 chup= <Bild runter>
    70 chdown= <Bild hoch>
    71 epg= g
    72 1= 1
    73 2= 2
    74 3= 3
    75 4= 4
    76 5= 5
    77 6= 6
    78 7= 7
    79 8= 8
    80 9= 9
    81 0= 0
    82 }}}
    83 
    84 
    85 
    86 == Plugins Bauen ==
    87 
    88 ''' Vorbereitung '''
    89 
    90 Im aktuellen tdt git http://gitorious.org/open-duckbox-project-sh4 kann man nun TitanNit Plugins bauen. Ich habe mal 2 Plugins eingebaut, die als Beispiel dienen sollen. Man kann sich dann seinen Stand lokal erweitern und eigene Plugins bauen.
    91 
    92 wer ein frisches git benutzt muss einmal
    93 
    94 {{{
    95 make yaud-enigma2-nightly
    96 }}}
    97 durchlaufen lassen, danach reicht dann immer ein
    98 
    99 {{{
    100 make titan-plugins
    101 }}}

  • wiki/pages/de/Devices

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.7.8.6.5 Devices''' [=#point3.7.8.6.5] ([wiki:System-Infos#point3.7.8.6 System Infos (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can view the detailed loaded devices info.
    10 
    11 [[br]]
    12 
    13 
    14 [[br]]

  • wiki/pages/de/EPG-Search

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.1.4 EPG Suche''' [=#point3.1.4] ([wiki:Interface-Operation#point3.1 Timer und EPG (zurück])   
    4 >
    5 >
    6 >[[Image(source:/wiki/Wiki-Pictures/DE/Epg_Search.jpg)]][[BR]]
    7 >
    8 Hier können Sie nach Sendung suchen.[[BR]]
    9 Mit der '''roten Taste''' können Sie das Timer Menü aufrufen. [[BR]]
    10 Mit der '''Grünen Taste''' können Sie nach einem Sendungs- / Filmtitel suchen. [[BR]]
    11 Mit der '''gelben Taste''' durchsuchen Sie die Beschreibung der Sendungs- Filminformation [[BR]]
    12 und mit der '''Blauen Tasten''' durchsuchen sie beides. [[BR]]
    13 Die '''Menü Taste''' durchsucht die Genre Sparte des EPG.[[br]]
    14 
    15 Für Informationen wie Sie eine Aufnahme programmieren drücken Sie ([wiki:Records#point3.10.5  Aufnahmen])
    16 
    17 
    18 
    19 

  • wiki/pages/de/EPG-Settings

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.6.11 EPG Settings''' [=#point3.6.11] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/EPG_Settings.jpg)]][[BR]]
    8 >
    9 >Here you can change your epg settings.
    10 
    11 [[br]]
    12 
    13  
    14  ||'''EPG Path''' ||Set to any Path you want where the EPG File should be stored (on Receivers with little Memory it is strongly recommended to extend it by using a USB Pen-Drive or Harddisk)||
    15  ||'''How Many Days:''' ||The Number of Days in Advance of the EPG to store (I recommend no higher than 8 Days)||
    16  ||'''Delete EPG after read:''' ||Do you want the EPG file to be deleted after being read.||
    17  ||'''EPG Save Mode:''' ||When should the EPG Data be stored to the storage medium. Caution: Should you not use a Pen Drive or Harddisk for EPG Storage set to Never, as Receivers with little Memory on Board tend to crash due to Insufficient free space.||
    18  ||'''Show EPG Screen (EPG Button):''' ||Which EPG format should be shown on EPG Key-press on the Remote.||
    19  ||'''EPG Free Space (kb):''' ||Total of minimal Free Memory that should be kept on the medium where the epg is stored to aviod free space errors.||
    20  ||'''EPG List Mode:''' ||What Channels should be scanned in the background (Only for twin Receivers) for EPG (scan)(whitelist) (scanlist and whitelist) (deactivate (disable scan)).||
    21  ||'''EPG Scan Time:''' ||Here you can set the time of the automatic EPG scan. The Scan will be performed every Day at that set time. Should the Receiver be in Deep Stand-by it will "wake up" aprox. 5 Minutes before the scan is due to start.||
    22  ||'''EPG Button in EPG:''' ||Behavior of the EPG Button during EPG display.||
    23  ||'''Grafic EPG Zoom:''' ||Sets the zoom level of the EPG to show more or less of a time span of the shown programs.||
    24  ||'''Grafic EPG Picons:''' ||Set to yes to use picons or the alternative Picon sets in the infobar and EPG stored in /var/media/autofs/sda1/swapextensions/usr/local/share/titan/picons/ directory.||
    25  ||'''Delete EPG Before Scan:''' ||Should the EPG be deleted before a the timed scan.||
    26  ||'''After EPG Scan:''' ||Behavior after the EPG scan is completed EPG scan: Nothing (Stand-By) or Switch Off (Deep Stand-By).||
    27  ||'''MHW EPG:''' ||Scan for a Media Highway EPG stream during EPG scan.||
    28  ||'''MHW2 EPG:''' ||Scan for a Media Highway version 2 EPG stream during  EPG scan.||
    29  ||'''OpenTV EPG:''' ||Scan for an OpenTV EPG stream during EPG scan.||
    30  
    31  To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    32  
    33 [[br]]
    34 ----
    35 
    36  '''Coloured Button's Functions"
    37 
    38  The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
    39  please see below for more info on the functions of these buttons:.
    40  
    41  ||'''Red Button: (EPG Reset)''' ||This will reset the saved epg removing all program data.||
    42  ||'''Green Button: (Edit)''' ||On a customisable item this will bring up editor to edit a value or text string.||
    43  ||'''Yellow Button: (Scanlist)''' ||Brings up the epg scan list and you may from there add aditional boquets to be scaned during an epg scan.||
    44  ||'''Blue Button: (log)''' ||This will show you the past scan log history for the epg.||
    45 

  • wiki/pages/de/EPG-Short-View

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''EPG-Kurzübersicht''' [=#point3.1.1] ([wiki:Interface-Operation#point3.1 Records and EPG(Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 >
    5 >
    6 >[[Image(source:/wiki/Wiki-Pictures/DE/EPG_Short_View.jpg)]][[BR]]
    7 >
    8 
    9 Vollständige EPG Übersicht aller verfügbaren Nachfolgesendungen auf dem aktuellen Sender.  [[BR]]

  • wiki/pages/de/External-Software

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9 External Software''' [=#point9] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 ----
    5 
    6 External Software is a collection of tools to supplement TitanNit.
    7 
    8 This is a list of applications that can be use with or for to manipulate or control your Receiver.
    9 [[br]]
    10 Below is a list of external applications please select a link below for more information.
    11 
    12 
    13 
    14 {{{#!div style="width: 1100px; margin: auto"
    15  {{{#!table style="border: none"
    16   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    17   {{{#!div style="float: left"
    18 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TiMote.png,align=left,link=[wiki:External-Software-TiMote#point9.1 9.1 TiMote (Android)])]]
    19   }}}
    20   '''[wiki:External-Software-TiMote#point9.1 9.1 TiMote (Android)]'''[[br]]
    21   {{{#!div style="float: left
    22 Timote is an andriod application for streaming and control of TitanNit
    23   }}}
    24   }}}
    25   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    26   {{{#!div style="float: left"
    27 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TiView.png,align=left,link=[wiki:External-Software-TiView#point9.2 9.2 TiView (PC)])]]
    28   }}}
    29   '''[wiki:External-Software-TiView#point9.2 9.2 TiView (PC)]'''[[br]]
    30   {{{#!div style="float: left
    31 TiView is an PC application for streaming and control of TitanNit
    32   }}}
    33   }}}
    34   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    35   {{{#!div style="float: left"
    36 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/SatChannelListEditor.png,align=left,link=[wiki:External-Software-SatChannelListEditor#point9.3 9.3 SatChannelListEditor])]]
    37   }}}
    38   '''[wiki:External-Software-SatChannelListEditor#point9.3 9.3 SatChannelListEditor]'''[[br]]
    39   {{{#!div style="float: left
    40 SatChannelListEditor is an PC application for manipulation of your TitanNit channel data.
    41   }}}
    42   }}}
    43   |----
    44   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    45   {{{#!div style="float: left"
    46 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/E2WebIFAPI.png,align=left,link=[wiki:External-Software-E2WebIfAPI#point9.4 9.4 E2WebIfAPI])]]
    47   }}}
    48   '''[wiki:External-Software-E2WebIfAPI#point9.4 9.4 E2WebIfAPI]'''[[br]]
    49   {{{#!div style="float: left
    50 E2WebIfAPI is an console application to support the dreambox xml web interface commands.
    51   }}}
    52   }}}
    53   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    54   {{{#!div style="float: left"
    55 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TitanEditor.png,align=left,link=[wiki:External-Software-TitanEditor#point9.5 9.5 TitanEditor])]]
    56   }}}
    57   '''[wiki:External-Software-TitanEditor#point9.5 9.5 TitanEditor]'''[[br]]
    58   {{{#!div style="float: left
    59 TitanEditor is an PC application for manipulation of dreambox channel data to work on of your TitanNit Receiver.
    60   }}}
    61   }}}
    62   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    63   {{{#!div style="float: left"
    64 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TitanNitLanguageEditor.png,align=left,link=[wiki:External-Software-TitanNitLanguageEditor#point9.6 9.6 TitanNitLanguageEditor])]]
    65   }}}
    66   '''[wiki:External-Software-TitanNitLanguageEditor#point9.6 9.6 TitanNitLanguageEditor]'''[[br]]
    67   {{{#!div style="float: left
    68 TitanLanguageEditor is an PC application for editing GUI language translations.
    69   }}}
    70   }}}
    71 }}}
    72 }}}

  • wiki/pages/de/External-Software-E2WebIfAPI

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9.4 E2WebIfAPI''' [=#point9.4] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 ----
    5 
    6 == Einführung ==
    7 Enigma2 Webinterface (WebIf) API wurde für Dreambox definiert.
    8 Es ist ein Protokoll, welches die Steuerung von Dreambox mittels HTTP-Anfragen erlaubt.
    9 
    10 Typische Steuerungsaufgaben sind:
    11 
    12 * Programmierung (Timer) und Wiedergabe von Aufnahmen
    13 * Live-Streaming (TV und Radio)
    14 * EPG-Funktionen (Anzeige, Suche)
    15 * Fernbedienung (Remote Control)
    16 
    17 Einen guten Überblick zum Protokoll findet Ihr im [http://dream.reichholf.net/wiki/Enigma2:WebInterface DreamboxWIKI].
    18 
    19 == Motivation ==
    20 
    21 Für TitanNit wurde die Android-App [TiMote#point9.1 tiMote] entwickelt. Mit dieser App steht die oben beschriebene Funktionalität zur Verfügung. D.h. jeder der ein Android-Handy bzw. -Tablett besitzt, kann den TitanNit-Receiver steuern und sogar auf dem Handy fernsehen. Das ist eine coole Sache, oder?
    22 
    23 Dieses Glück hat jedoch der Besitzer eines iOS-Geräts (iPhone, iPad) nicht mehr.
    24 Man kann zwar auch mit einem Web-Browser plattformunabhängig (Windows, Linux, Android, iOS) den Receiver steuern, dies ist aber nicht so komfortabel wie mit tiMote.
    25 
    26 Anderseits gibt es sowohl für iOS als auch Android schon fertige Apps für Dreambox-Receiver. Diese Apps basieren auf dem E2-WebIf-Protokoll. Könnte man nicht diese Apps ebenfalls für TitanNit-Receiver verwenden statt eine neue App für iOS zu entwickeln?
    27 
    28 == Die Lösung ==
    29 TitanNit besitzt schon ein eigenes Protokoll, welches jedoch mit Enigma2 WebIf nicht kompatibel ist.
    30 Nach kurzer Analyse wurde festgestellt, dass eine Konvertierung der E2-Anfragen auf TitanNit-Anfragen nicht so schwer ist.
    31 Deswegen wurde ein E2-Web-Server (e2webserv) entwickelt, welches das Enigma2 WebIf implementiert. Dieser Server empfängt die E2-Anfragen, delegiert die Aufrufe zum lokalen TitanNit Web-Server und die TiatnNit-Antworten wandelt zurück ins XML-Format, welches vom E2-Client erwartet wird.
    32 
    33 Auf diese Weise wird die TitanNit-Box jetzt offen für die vorhandene E2-Clientsoftware.
    34 
    35 
    36 == Voraussetzungen ==
    37 
    38 * Web-Server muss auf dem Receiver aktiviert werden
    39 * e2webserv muss auf dem Receiver installiert werden
    40 
    41 == iOS-Apps ==
    42 
    43 Folgende Apps habe ich auf meinem iPad2:
    44 * dreaMote
    45 * dreaMote Lite
    46 * e2RemoteHD
    47 * Dreambox Live
    48 
    49 Falls Ihr im App-Store nichts kaufen wollt, dann kann ich dreaMote Lite empfehlen.
    50 
    51 Zusätzlich zu der App benötigt Ihr einen Player.
    52 
    53 Ich habe folgende Player ausprobiert, welche bei mir gut funktionieren:
    54 * GoodPlayer
    55 * BUZZ Player
    56 * OPlayerHD Lite
    57 * VLC Player
    58 
    59 VLC und OPlayerHD Lite sind frei.
    60 
    61 == XBMC ==
    62 
    63 Falls Ihr die Media-Center-Software [http://xbmc.org/ XBMC] im Einsatz habt, so könnt Ihr mittels Live-TV-Plugin VU+ Euren TitanNit-Receiver direkt einbinden.
    64 XBMC läuft auf einem PC sowohl unter Windows als auch Linux, ist aber auch für Raspberry Pi verfügbar.
    65 
    66 == VLC ==
    67 Mit dem installierten e2webserv könnt Ihr Live-Streaming nur mittels [http://www.videolan.org/vlc/ VLC] (ohne extra Software) auf einem PC (Windows oder Linux) genießen.
    68 
    69 Ihr braucht dafür nicht die Kanäle manuell umschalten, es passiert alles automatisch. Damit dies möglich wird, braucht Ihr eine M3U-Playliste. Solche Playliste könnt Ihr pro Favorit generieren lassen und auf dem PC speichern. Danach einfach M3U-Datei mit VLC öffnen und das gewünschte Programm anklicken.
    70 
    71 Wie exportiert man die M3U-Datei für eine bestimmte Favoritenliste?
    72 
    73 In einem Web-Browser einfach die gewünschte Adresse angeben.
    74 
    75 Beispiel (Favorit heißt "Polish"):
    76 
    77 [http://192.168.1.1:8080/web/services.m3u?bRef=Polish]
    78 
    79 Bei dem Link muss nur die eigene IP-Adresse angegeben werden und bei Namen mit Leerzeichen sollte man "%20" statt des Leerzeichen nehmen.
    80 
    81 Beispiel (Favorit heißt "Mein TV", Receiver-IP: 192.168.0.10):
    82 
    83 [http://192.168.0.10:8080/web/services.m3u?bRef=Mein%20TV]
    84 
    85 == Client-Konfiguration ==
    86 Bitte bei dem E2-Client folgendes konfigurieren:
    87 * IP-Adresse des Receivers
    88 * Port: 8080
    89 * Streaming Port: 8001
    90 
    91 Zu beachten ist, dass SSL nicht unterstützt wird.
    92 
    93 Unten sieht man eine Beispielkonfiguration für dreaMote.
    94 
    95 [[Image(DreaMote.png, 384px)]]
    96 
    97 == e2webserv.conf ==
    98 
    99 Die Konfiguration für den Server muss man bei Bedarf manuell anpassen.
    100 Bei Standard-TitanNit-Konfiguration sollten keine Änderungen in e2webserv.conf notwendig sein.
    101 
    102 Bei einer Flash-Installation liegt die Konfigurationsdatei '''e2webserv.conf''' in dem Verzeichnis '''/mnt/swapextensions/etc'''
    103 
    104 Hier ist der Inhalt:
    105 {{{
    106 # e2 web port
    107 port=8080
    108 # e2 data port
    109 dataPort=8001
    110 # titan web port
    111 titanPort=80
    112 # titan data port
    113 titanDataPort=22222
    114 # titan host (change it if e2webserv is not running locally on the receiver)
    115 titanHost=127.0.0.1
    116 # automatic switching of channels
    117 # It is useful if you don't want manually switch a channel on receiver with a single tuner.
    118 # If it is set to false and you have a single tuner the you can stream only channels located
    119 # on the same transponder as the current channel active on the receiver.
    120 autoZap=true
    121 # log output file
    122 logFile=/tmp/e2webserv.log
    123 # maximal log file size in KB. Set it to 0 (default 10KB) to disable logging (maximal allowed value is 1024).
    124 # When the file limit is reached a backup of the current file is created.
    125 # It means maximally 2 x maxLogSize KB will be used.
    126 maxLogSize=10
    127 # thread pool size (1..8)
    128 threadPool=2
    129 # Directory where the transponder and bouquet files are located.
    130 # You don't need to specify it, it will be automatically discovered.
    131 # But if you you start e2webserv not on the receiver (but e.g. on your Linux server or Windows computer) then you
    132 # should copy the settings (channel, transponder, provider and all bouquets file) and specify here the location on the local computer.
    133 titanDir=/mnt/settings
    134 }}}
    135 == Links ==
    136 
    137 * Enigma2 Web-API im [http://www.aaf-digital.info/forum/showthread.php?90948-Enigma2-Web-API-f%FCr-Titan AAF-Forum]
    138 * Sources auf [https://github.com/gswiatek/e2api4titan GitHub]
    139  
    140 [[br]]
    141 [[br]]

  • wiki/pages/de/External-Software-SatChannelListEditor

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9.3 SatChannelListEditor''' [=#point9.3] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 ----
    5 Diese Anleitung bezieht sich auf die Version 5.0 von SatChannelListEditor. In zukünftigen Versionen werden evtl. neue Features hinzugefügt, wodurch sich die Ansicht des Programms ändern kann und nicht mehr den Screenshots in dieser Anleitung entspricht.
    6 
    7 == Voraussetzungen ==
    8 SatChannelListEditor wurde für die Laufzeitumgebung „Microsoft .NET Framework“ programmiert. Aktuell wird mindestens .NET Framework 2.0 benötigt.
    9 
    10 (siehe auch [http://de.wikipedia.org/wiki/.NET_Framework Wikipedia-Artikel zu .NET Framework])
    11 
    12 == Windows ==
    13 * Bei Windows XP muss .NET Framework in der Version 2.0, 3.0 oder 3.5 installiert werden. (3.0 und 3.5 sind erweiterte Versionen und beinhalten 2.0)
    14 * Bei Windows Vista und Windows 7 ist das .NET Framework bereits in der richtigen Version vorhanden und muss nicht nachinstalliert werden.
    15 * Bei Windows 8 muss das .NET Framework 3.5 installiert werden, da Windows 8 standardmäßig nur das .NET Framework 4.5 enthält, welches nicht mehr kompatibel zu SatChannelListEditor ist
    16 
    17 == Linux ==
    18 Bei Linux ist das Mono-Framework erforderlich (siehe [http://de.wikipedia.org/wiki/Mono-Projekt Wikipedia-Artikel zu Mono-Projekt]).
    19 [[BR]] Evtl. müssen WinForms libraries nachinstalliert werden mit "apt-get install libmono-winforms*"
    20 [[BR]] Gestartet wird das Programm dann auf der Kommandozeile mit dem Befehl „mono SatChannelListEditor.exe“.
    21 
    22 == Mac OS ==
    23 Bei Mac OS ist, wie bei Linux, das Mono-Framework erforderlich, damit SatChannelListEditor funktioniert.
    24 
    25 == Der erste Start ==
    26 Nach dem ersten Start ist SatChannelListEditor auf Englisch eingestellt und hat den Receiver „UFS-821“ ausgewählt.
    27 Nun muss als erstes die richtige Sprache und anschließend der richtige Receiver ausgewählt werden.
    28 
    29 == Einstellen der Sprache ==
    30 Wählen Sie im Menu unter dem Punkt „Options“ den Punkt „Language“:
    31 
    32 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/1.png)]]
    33 
    34 Darauf erscheint ein neues Fenster, wo Sie die Sprache auswählen und mit „OK“ bestätigen müssen:
    35 
    36 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/2.png)]]
    37 
    38 == Einstellen des Receiver-Typs bzw. Receiver-Betriebssystems ==
    39 Wählen Sie im Menu unter dem Punkt „Optionen“ den Punkt „Einstellungen“:
    40 
    41 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/3.png)]]
    42 
    43 Wählen Sie im darauf erscheinenden Fenster als Receiver „Titan“ aus:
    44 
    45 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/4.png)]]
    46 
    47 Wechseln Sie anschließend noch auf die Registerkarte „Titan“ und stellen dort die IP-Adresse ihres Receivers ein, bevor Sie das Fenster mit dem OK-Knopf wieder schließen. Die anderen Einstellungen auf dieser Seite müssen nicht verändert werden.
    48 
    49 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/5.png)]]
    50 
    51 == Download und Upload der Kanalliste ==
    52 Nachdem der Receiver-Typ und die IP-Adresse festgelegt wurden, können Sie die Kanalliste von ihrem Receiver herunter laden (Download) und nach Bearbeitung wieder an den Receiver schicken (Upload).
    53 [[BR]] Benutzen Sie dafür die beiden Knöpfe in der Werkzeugleiste oder im Menu:
    54 
    55 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/6.png)]]
    56 
    57 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/7.png)]]
    58 
    59 Wenn Sie einen Upload oder Download starten wird automatisch auf das Meldungs-Fenster gewechselt, wo Statusmeldungen zum Datei-Transfer angezeigt werden.
    60 
    61 == Bearbeiten der Kanalliste ==
    62 
    63 === Favoriten ===
    64 Alle TV- und Radio-Kanäle werden in den Registerkarten „TV“ und „Radio“ im Hauptfenster von SatChannelListEditor angezeigt. Normalerweise befinden sich mehrere hundert oder tausend Kanäle in dieser Liste.
    65 [[BR]] Um die Navigation auf dem Receiver zu erleichtern, kann man die Kanäle einem oder mehreren Favoriten (auch Bouquets genannt) zuordnen.
    66 Die Favoriten bestimmen auch die Nummer der Kanäle, mit der Sie die Kanäle direkt über die Fernbedienung anwählen können.
    67 [[BR]] Erstellen Sie einen neuen Favoriten, indem Sie mit der rechten Maustaste im Baum der Favoriten klicken:
    68 
    69 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/8.png)]]
    70 
    71 Vergeben Sie anschließend den gewünschten Namen:
    72 
    73 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/9.png)]]
    74 
    75 Sie können nun Kanäle zu diesem Favoriten hinzufügen, indem Sie die Kanäle per Drag&Drop auf den neu erzeugten Favoriten schieben oder indem Sie auf dem Kanal mit der rechten Maustaste klicken und im Menu „Zu Favorit hinzufügen“ wählen:
    76 
    77 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/10.png)]]
    78 
    79 Nachdem ein Kanal zu einem Favoriten hinzugefügt wurde, erhält er auch eine Kanalnummer. Der erste Kanal im ersten Favoriten erhält die Nummer 1:
    80 
    81 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/11.png)]]
    82 
    83 Wenn ein Kanal mehreren Favoriten zugeordnet ist, bekommt er auch mehrere Kanalnummern:
    84 
    85 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/12.png)]]
    86 
    87 === Der Favorit „EPG Scan“ ===
    88 Für TV-Kanäle gibt es einen speziellen Favoriten namens „EPG Scan“. Fügen Sie alle Kanäle, für die TitanNit automatisch den EPG laden soll, zu diesem Favoriten hinzu.
    89 
    90 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/13.png)]]
    91 
    92 === Anlegen und Bearbeiten von Satelliten ===
    93 Wechseln Sie auf die Registerkarte „Satelliten“. Nach einem Klick auf die rechte Maustaste erscheint Menu, wo Sie einen neuen Satelliten anlegen oder einen bestehenden bearbeiten können. Doppel-Klick auf einen bestehenden Satelliten öffnet diesen ebenfalls zur Bearbeitung.
    94 
    95 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/14.png)]]
    96 
    97 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/15.png)]]
    98 
    99 === Anlegen und Bearbeiten von Transpondern ===
    100 Wechseln Sie auf die Registerkarte „Transponder“. Nach einem Klick auf die rechte Maustaste erscheint ein Menu, wo Sie einen neuen Transponder anlegen oder einen bestehenden bearbeiten können. Doppel-Klick auf einen bestehenden Transponder öffnet diesen ebenfalls zur Bearbeitung.
    101 
    102 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/16.png)]]
    103 
    104 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/17.png)]]
    105 
    106 === Anlegen und Bearbeiten von Kanälen ===
    107 Wechseln Sie auf die Registerkarte „TV“ oder auf die Registerkarte „Radio“. Nach einem Klick auf die rechte Maustaste erscheint Menu, wo Sie einen neuen Kanal anlegen oder einen bestehenden bearbeiten können. Doppel-Klick auf einen bestehenden Kanal öffnet diesen ebenfalls zur Bearbeitung.
    108 
    109 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/18.png)]]
    110 
    111 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/19.png)]]
    112 
    113 == Arbeiten mit Receiver-Profilen ==
    114 Wenn Sie mehrere Receiver besitzen empfiehlt es sich, mit Profilen zu arbeiten. Gehen Sie dazu zu den Einstellungen und aktivieren das Häkchen bei „Receiver Profile verwenden“:
    115 
    116 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/20.png)]]
    117 
    118 Geben sie anschließend einen Namen für das Profil ein und klicken auf den Knopf „Speichern“. Das Profil wird nun mit den aktuell auf der Registerkarte „Titan“ festgelegten Einstellungen erzeugt.
    119 [[BR]] Um ein Profil für einen zweiten Titan-Receiver zu erzeugen wechseln Sie auf die Registerkarte „Titan“, geben dort die IP-Adresse des zweiten Receiver ein, wechseln zurück auf die Registerkarte „Allgemein“, geben einen neuen Profilnamen an und klicken erneut auf „Speichern“.
    120 
    121 Wenn sie das Einstellungs-Fenster nun über den OK-Knopf schließen, befindet sich im Hauptfenster eine neue Auswahlbox, wo Sie zwischen den Profilen umschalten können:
    122 
    123 [[Image(source:/wiki/Wiki-Pictures/DE/SCLE/21.png)]]

  • wiki/pages/de/External-Software-TiMote

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9.1 TiMote''' [=#point9.1] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 
    5 ----
    6 [[br]]
    7 Timote ist eine Universalfernbedienung für linux basierte Receiver.
    8 Aktuell werden (Atemio) Titannit, Enigma2 und Neutrino unterstützt.
    9 
    10 Features:
    11 - Bouquets / Favoriten anzeigen
    12 - EPG anzeigen
    13 - EPG durchsuchen (*)
    14 - aktuellen Sender anzeigen
    15 - Aufnahmen anzeigen, streamen und löschen (*)
    16 - Timer erstellen, editieren und löschen
    17 - Satfinder (*)
    18 - Powercontrol
    19 - virtuelle Fernbedienung
    20 - Nachrichten
    21 (*) Titannit/E2 only
    22 
    23 Für das Streaming sollte ein geeigneter Player, z.B. MX Player, VPlayer oder BSPlayer (lite) installiert sein.
    24 Wenn die App abstürzt aktivieren sie bitte "automatisches Fehlerbericht senden" in den Einstellungen. Sie können
    25 dadurch helfen die Software zu verbessern und dem Entwickler die Fehlersuche entscheidend erleichtern.
    26 Kommentare, Fragen, Anregungen oder Wünsche? Schreiben mir eine Email oder hinterlasst auf der Homepage einen Kommentar!
    27 
    28 
    29 [[Image(http://www.android.com/images/brand/get_it_on_play_logo_large.png)]]
    30 [[br]]
    31 [https://play.google.com/store/apps/details?id=eu.azato.timote PlayStore]

  • wiki/pages/de/External-Software-TiView

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9.2 TiView''' [=#point9.2] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 ----
    5 Die TiView ist eine Software für Windows im Zusammenhang mit dem Titan und E2-Images.[[br]]
    6 Das Tool nutzt die HTTP-RAW-Api von TitanNit bzw die HTTP-XLM-Api von Enigma2.[[br]]
    7 Es ist als 32bit und 64bit Version verfügbar.[[br]]
    8 [[br]]
    9 ''Highlights von TiView''
    10 
    11 - *Wiedergabe des TV-Bildes am PC
    12 - *Wiedergabe von Aufnahmen am PC
    13 - *PiP Funktion für gleichzeitige Wiedergabe von 2 Streams/Aufnahmen am PC
    14 - *Proxy Funktion für den Zugriff einer Remote TiView und Streaming per runtergerechneten Stream
    15 - Verwaltung der Aufnahmetimer
    16 - Infobar zum laufenden Programm mit Fortschrittanzeige
    17 - Picon-Anzeige in der Infobar(dazu die TiView_picons.zip in das TiView Verzeichniss entpacken)
    18 - SenderEPG
    19 - MultiEPG
    20 - grafisches MultiEPG
    21 - EPG Suche
    22 - Übersicht der Aufnahmen
    23 - Profilverwaltung bei Verwendung mehrere Boxen
    24 - Signal-Monitor
    25 - Nachrichtenversand zur Box
    26 - OSD-Screenshot erstellen
    27 '''*Für die Wiedergabe am PC wird ein installierter VLC Player in der ensprechenden Version(32/64bit) wie der TiView benötigt.'''[[br]]
    28 (Alternativ kann auch die libvlc.dll, libvlccore.dll, libgcc_s_seh-1.dll(nur bei 64bit) und der Plugins Ordner von VLC in den TiView Ordner kopiert werden)
    29 
    30 [[br]]

  • wiki/pages/de/External-Software-TitanEditor

    r37411 r37661  
    1 [[TranslatedPages]]
    2 '''9.5 TitanEditor''' [=#point9.5] ([wiki:Wiki#point0 Inhalt]) ([WikiStart#point0 Sprachauswahl])
    3 
    4 Titan Editor ist ein einfaches Programm für Windows um Enigma2 Senderlisten in ein für Titan verwendbares Format zu konvertieren.[[br]]
    5 Eine Funktion erlaubt auch das Konvertieren von Senderlogos (Picons) im Enigma2 Format nach Titan-Picons.
    6 
    7 Dieses Programm befindet sich noch in einem Beta Status, aber die Grundfunktionen funktionieren.
    8  
    9  - konvertiert E2 channel Listen inkl. der Favoriten
    10  - hinzufügen, bearbeiten und löschen von Titan Sendern
    11  - konvertieren von E2 picons nach Titan Picons
    12  - Favoriten verwalten
    13 
    14 Die derzeitige Version des TitanEditor ist Version 0.15 und es kann hier geladen werden: [http://www.aaf-digital.info/forum/showthread.php?78014-TitanEditor-V0-15&p=802005&viewfull=1#post802005 titanEditor]
    15 
    16  

  • wiki/pages/de/External-Software-TitanMote

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9.7 TitanMote''' [=#point9.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 ----
    5 
    6 [[br]]
    7 
    8 Titanmote is a universal remote control for Linux-based receivers.
    9 Currently there is a little information we can provide reguarding this from the developer jagabongo.
    10 
    11 ''Words from the developer:''
    12 ----
    13 I'm currently working on an iOS app for TitanNit . For this I would need a few beta testers .
    14 
    15 The app will cost money later when development is finished and will be able to be purchased from the store, I will not releace it free because I have specially bought for this purpose a developer account and will take many hours of development, I also do not want the app to feature advertising.
    16 
    17 requirements:
    18  - IPhone or iPad with iOS > = 7.0
    19  - A bit of technical understanding
    20  - Lust for testing
    21 
    22 A few recent screenshots :
    23  https://www.dropbox.com/sh/armi0c3q72i350h/vm3szZDzvK
    24 
    25 
    26 So in Version 1 I should be able to:
    27  
    28  - Browse by bouquets / channel lists + See Epg info and switch Channels.
    29  - Add timers on an event with the epg data.
    30  - List all timer
    31  - Delete Timer
    32  - easy remote copy with touch buttons
    33  - 2 profiles
    34  - Everywhere pull to refresh .
    35  - [ EDIT] Forgot , it will be multilingual or , DE, FR, IT and rest English. But languages ​​are all relatively retrofitted without hazzle
    36 
    37 Future features:
    38 
    39  - User: Password WebIf Auth . ( hopefully not often used)
    40 
    41  - Https support. ( Was I already am going to test with self-signed stuff but totally in the pants ... )
    42 
    43  - The stream to an iOS device is just not as easy as on Android that is why they first moved to the rear.
    44  
    45 
    46 BETA testing runs like this:
    47  
    48  * 1 You send with your UUID ( google iOS Device UUID to find out )
    49 
    50  * 2 Your you created an account at https://build.phonegap.com ( Free is sufficient).
    51 
    52  * 3 You share me with your UUID and email phonegap.build accounts.
    53  
    54 When that's done you can you log on your mobile Safari in build.phonegap.com and always install it there through the browser to the latest build. (OTA Installation).
    55  
    56 This is perfectly legal and possible even without jailbreak.
    57 
    58 
    59 if you are intreseed in becomming a better tester please leave a message in the [[http://www.aaf-digital.info/forum/showthread.php?100699-iOS-TitanNit-iOS-App-!-titanMote-!-Tester-gesucht!&p=974748#post974748 | forum]].

  • wiki/pages/de/External-Software-TitanNitLanguageEditor

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''9.6 TitanNit Language Editor''' [=#point9.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    4 ----
    5 
    6 The TitanNit Language Editor tool is used to provide translations files for devs to implement translations into the TitanNit gui.
    7 
    8 === Made by Karlo ===
    9 
    10 German and English languages have been made and have been merged into svn.
    11 To support future languages you can use this program to download  the language base files from the svn for conversion it supports UTF-8 so special
    12 chracters from various languages can be implemented.
    13 
    14 Please check the main thread for the latest version:
    15 
    16 [http://www.aaf-digital.info/forum/showthread.php?98565-TitanNitLanguageEditor forum Link]
    17 
    18 This program requires microsoft visual basic runtime files to operate.
    19 
    20 Once you have made a Translation you may upload the translation po files to the aaf forum for implementation into TitanNit.
    21 
    22 If you think you can help with a translation please do so at the end of this page there is information on ([#point9.6.5 Submission]).
    23 
    24 [[br]]
    25 
    26 ----
    27 '''Features''' ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    28 ----
    29  
    30 * load po file from svn __"File/ Open Source (svn)"__
    31 * Import po file from svn or local as source __"File/ Import Titan.po"__
    32 * open local file as target__"File/ Open target (local)"__
    33 * save target file __"File/ Save Target"__
    34 * save target file as titan.po __"File/ Save titan.po"__
    35 * export msg string for external use __"File/ Export msgstr as Titan.po"__
    36 * Build reciever translation file __"File/ Build Titan.mo"__
    37 * export sourcefile to target __"Edit/ target.po -> target"__
    38 * view source target differences __"Edit/ diff target - titan.po"__
    39 
    40 [[br]]
    41 
    42 ----
    43 '''Functions'''  ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    44 ----
    45 
    46 ''Select an item to view more info:''
    47 
    48 * ([#point9.6.1 Loading a translation from svn])
    49 * ([#point9.6.2 Loading a Translation from a local directory])
    50 * ([#point9.6.3 Import Translation from svn or local (Source/ Target Mode)])
    51 * ([#point9.6.4 Edit Translation])
    52 * ([#point9.6.5 Submission])
    53 * ([#point9.6.6 Local Testing])
    54 
    55 
    56 
    57 ----
    58 '''Loading a translation from svn''' [=#point9.6.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    59 ----
    60 
    61 To load a translation from the server SVN repo select the translation file from the menu: [[br]]
    62 
    63 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/open_server.jpg)]] [[br]]
    64 
    65 it will then start downloading from the internet.[[br]]
    66 
    67 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/loading_server.jpg)]] [[br]]
    68 
    69 [[br]]
    70 ([#point9.6 Top of Page])
    71 [[br]]
    72 
    73 ----
    74 '''Loading a Translation from a local directory''' [=#point9.6.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    75 ----
    76 
    77 To load a translation from the local directory select the translation file from the menu: [[br]]
    78 
    79 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/open_local.jpg)]] [[br]]
    80 
    81 [[br]]
    82 ([#point9.6 Top of Page])
    83 [[br]]
    84 
    85 ----
    86 '''Import Translation from svn or local (Source/ Target Mode)'''[=#point9.6.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    87 ----
    88 
    89 To import a translation from svn or the local directory select the translation file from the menu: [[br]]
    90 Note: for this to work a source file must be loaded first [[br]]
    91 
    92 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/import_file.jpg)]] [[br]]
    93 
    94 [[br]]
    95 
    96 you will then be dispalyed with this view to view the two po files along side each other:
    97 
    98 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/import_list_view.jpg)]] [[br]]
    99 
    100 [[br]]
    101 
    102 you can then select __"Edit/ diff target - titan.po"__ to view the source and target differences.
    103 
    104 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/diff_target.jpg)]] [[br]]
    105 
    106 [[br]]
    107 
    108 you can also automatically merge the source files to the target file  by selecting __"Edit/ target.po -> target"__
    109 
    110 [[br]]
    111 ([#point9.6 Top of Page])
    112 [[br]]
    113 
    114 ----
    115 '''Edit Translation''' [=#point9.6.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    116 ----
    117 
    118 
    119 Now that it is loaded you may edit the msgid strings to suit your language and upload to the aaf forum.
    120 you may use the buttons on the lower taskbar to search for strings you wish to edit.[[br]]
    121 
    122 [[Image(source:/wiki/Wiki-Pictures/DE/TLE/edit.jpg)]]
    123 
    124 [[br]]
    125 ([#point9.6 Top of Page])
    126 [[br]]
    127  
    128 ----
    129 '''Submission'''[=#point9.6.5]  ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    130 ----
    131 
    132 If you could submit your completed translation file into the thread below for comitting by the devs into svn.
    133  
    134 please note that some translations may no be able to be imported into some receivers due to memory constarints.
    135 
    136 [http://www.aaf-digital.info/forum/showthread.php?98565-TitanNitLanguageEditor forum Link]
    137 
    138 [[br]]
    139 ([#point9.6 Top of Page])
    140 [[br]]
    141 
    142 ----
    143 '''Local Testing''' [=#point9.6.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    144 ----
    145 
    146 If you wish to install your modified language files into your reciever for testing you can so by exporting you file an a titan.mo file you can do this by selecting __"File/ Build Titan.mo"__ for this to work you need to install some aditional components  in to the program directory.
    147 
    148 To do this create a folder in the program directory called __"gettext"__ and extract the below files into that directory:
    149 
    150 
    151 [http://ftp.informatik.rwth-aachen.de/ftp/pub/gnu/gettext/gettext-runtime-0.13.1.bin.woe32.zip gettext-runtime] [[br]]
    152 [http://ftp.informatik.rwth-aachen.de/ftp/pub/gnu/libiconv/libiconv-1.9.1.bin.woe32.zip libiconv] [[br]]
    153 [http://ftp.informatik.rwth-aachen.de/ftp/pub/gnu/gettext/gettext-tools-0.13.1.bin.woe32.zip gettext-tools] [[br]]
    154 
    155 Once you have exported your titan.mo file you may ftp or manually copy it onto your Receiver to test it.
    156 
    157 The file needs to go into the directory and a reboot neede to be proformed afterwards:  '''/var/usr/local/share/titan/po/__??__/LC_MESSAGES/titan.mo)''' where __??__ is the language file you are editing.
    158 
    159 ''Note: if you have trouble exporting the translation to a mo file place the program directory on the root of your harddisk it can some times fail if the program it too deep in the file system''
    160 
    161 [[br]]
    162 ([#point9.6 Top of Page])
    163 [[br]]

  • wiki/pages/de/File-Browser

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.2.5 File Browser''' [=#point3.2.5] ([#point3.2 Media center (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 >Here you can browse files from any source available from your decoder (local or network)
    10 > you may do such things as copy delete and move.
    11 
    12 
    13 [[br]]

  • wiki/pages/de/Filesystem-Check

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.5.1 File system Check''' [=#point3.5.5.1] ([WikiStart#point3.5 System (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can format your harddisk select an item and follow tth onscreen prompts.
    10 
    11 [[br]]
    12 
    13 
    14  
    15 
    16 [[BR]]

  • wiki/pages/de/Format-Hdd

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.5 Hard Disk''' [=#point3.5.5] ([wiki:Interface-Operation#point3.5 system (Back)])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can format your harddisk select an item and follow tth onscreen prompts.
    10 Note that you must enable ([wiki:Adjust#point3.6.7 Expertmode]) to show all available format options in this display.
    11 
    12 [[br]]
    13 
    14 
    15  
    16 
    17 [[BR]]

  • wiki/pages/de/Free-Space

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.7.8.2 Free Space''' [=#point3.7.8.2] (([wiki:System-Info#point3.7.8 System Info (Back])
    4 >
    5 >
    6 >[[Image(source:/wiki/Wiki-Pictures/DE/System-Info-Free-Space.jpg)]][[br]]
    7 >
    8 Here you can view the free space of all the file systems acessable from the decoder.
    9 
    10 [[br]]
    11 
    12 
    13 [[br]]

  • wiki/pages/de/Functions

    r37355 r37661  
    1 [[TranslatedPages]]
    2 
    3 ----
    4 '''2 Interface Elements''' [=#point2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    5 ----
    6 [[br]]
    7 This section will show the functions and controls of the various elements in the gui within TitanNit and discriptions to the various
    8 items and their functions aswell as helpfull information and tricks to get the most possible experience with your Receiver.
    9 
    10 Note: pictures in this area only apply to the default skin used in Titan.
    11 If you do not see a specific menu item on the display please select the default skin from the menu as follows all the functions displayed below are implemented in all skins but some elements may be omitted from the display in some skins:
    12 
    13  Press the __"Menu"__ button and select __"Settings"__ scroll down to __"Skin"__ and select the __"Default"__ Skin from the menu.
    14  The decoder will then reboot with the new selected __Default__ skin.
    15 
    16 ----
    17 {{{#!div style="width: 1100px; margin: auto"
    18  {{{#!table style="border: none"
    19   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    20   {{{#!div style="float: left"
    21 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Infobar.png,align=left,link=[#point2.1])]]
    22   }}}
    23   '''[#point2.1 infobar]'''[[br]]
    24   {{{#!div style="float: left
    25 Default display when pressing the __Info__ button while watching TV.
    26   }}}
    27   }}}
    28   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    29   {{{#!div style="float: left"
    30 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/playback_infobar.png,align=left,link=[wiki:History#point2.2 TitanNit Info])]]
    31   }}}
    32   '''[#point2.2 Playback infobar]'''[[br]]
    33   {{{#!div style="float: left
    34 Default display when pressing the __Info__ button while watching A recording or Media using the default player.
    35   }}}
    36   }}}
    37   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    38   {{{#!div style="float: left"
    39 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/AudioTracks_infobar.png,align=left,link=[#point2.3])]]
    40   }}}
    41   '''[#point2.3 Audiotracks infobar]'''[[br]]
    42   {{{#!div style="float: left
    43 Default display when pressing the __Audio__ button while watching TV, A recording or Media using the default player.
    44   }}}
    45   }}}
    46   |----
    47   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    48   {{{#!div style="float: left"
    49 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Channel History.png,align=left,link=[#point2.4])]]
    50   }}}
    51   '''[#point2.4 Channel History]'''[[br]]
    52   {{{#!div style="float: left
    53 Default display when pressing the __Recall__ button while watching A recording or Media using the default player.
    54   }}}
    55   }}}
    56   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    57   {{{#!div style="float: left"
    58 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Sleep_Timer.png,align=left,link=[#point2.5])]]
    59   }}}
    60   '''[#point2.5 Sleep Timer]'''[[br]]
    61   {{{#!div style="float: left
    62 Default display when pressing the __Sleep_ button while the decoder is in operation.
    63   }}}
    64   }}}
    65   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    66   {{{#!div style="float: left"
    67 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Subtitle.png,align=left,link=[#point2.6])]]
    68   }}}
    69   '''[#point2.6  Subtitle]'''[[br]]
    70   {{{#!div style="float: left
    71 Default display when pressing the __Subtitle__ button while watching TV, A recording or Media using the default player.
    72   }}}
    73   }}}
    74   |----
    75   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    76   {{{#!div style="float: left"
    77 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/EPG.png,align=left,link=[#point2.7])]]
    78   }}}
    79   '''[#point2.7 EPG]'''[[br]]
    80  {{{#!div style="float: left
    81 Default display when pressing the __EPG__ button while watching TV.
    82   }}}
    83   }}}
    84   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    85   {{{#!div style="float: left"
    86 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/program_info.png,align=left,link=[#point2.8])]]
    87   }}}
    88   '''[#point2.8 Program Info]'''[[br]]
    89    {{{#!div style="float: left
    90 Default display when pressing the __Info__ button while viewing the EPG.
    91   }}}
    92   }}}
    93   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    94   {{{#!div style="float: left"
    95 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/player.png,align=left,link=[#point2.9])]]
    96   }}}
    97   '''[#point2.9 Player]'''[[br]]
    98   {{{#!div style="float: left
    99 Default display when pressing the __Play_ button.
    100   }}}
    101   }}}
    102   |----
    103   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    104   {{{#!div style="float: left"
    105 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/favourite.png,align=left,link=[#point2.10])]]
    106   }}}
    107   '''[#point2.10 Favourite]'''[[br]]
    108   {{{#!div style="float: left
    109 Default display when pressing the __FAV__ button.
    110   }}}
    111   }}}
    112   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    113   {{{#!div style="float: left"
    114 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/record.png,align=left,link=[#point2.11])]]
    115   }}}
    116   '''[#point2.11 Record]'''[[br]]
    117   {{{#!div style="float: left
    118 Default display when pressing the __REC__ button while watching TV.
    119   }}}
    120   }}}
    121 
    122 
    123  }}}
    124 }}}
    125 ----
    126 [[BR]]
    127 
    128 
    129 
    130 
    131 
    132 '''Infobar''' [=#point2.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    133 
    134 [[Image(source:/wiki/Wiki-Pictures/DE/Info-OSD.jpg)]] [[br]]
    135 This overlay display shows when you press the __"INFO"__ button when viewing a tv channel. [[br]]
    136 It shows actual and next program information
    137 
    138 [[br]]
    139 '''Playback Infobar''' [=#point2.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    140 
    141 [[Image(source:/wiki/Wiki-Pictures/DE/Playback-OSD.jpg)]] [[br]]
    142 This overlay shows when you press the __"INFO"__ button when playing back a program or time shift is in operation. [[br]]
    143 It shows a list of the available buttons to use when in playbac/timeshift to do various things.
    144 
    145 [[br]]
    146 '''Audio Track''' [=#point2.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    147 
    148 [[Image(source:/wiki/Wiki-Pictures/DE/Audio-OSD.jpg)]] [[br]]
    149 This overlay shows when you press the __"AUDIO""__ button when viewing a tv channel. [[br]]
    150 It allows you to adjust the audio track on the current stream if an alternative audio source exists.
    151 
    152 [[br]]
    153 '''History''' [=#point2.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    154 
    155 [[Image(source:/wiki/Wiki-Pictures/DE/History-OSD.jpg)]] [[br]]
    156 This overlay shows when you press the __"RECALL"__ button when viewing a tv channel. [[br]]
    157 It allows you to recall the past viewed channels for fast zapping between them.
    158 
    159 [[br]]
    160 '''Sleep Timer''' [=#point2.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    161 
    162 [[Image(source:/wiki/Wiki-Pictures/DE/Sleep-OSD.jpg)]] [[br]]
    163 This overlay shows when you press the __"SLEEP"__ button. [[br]]
    164 It allows you to set the shutdown timer to automatically shutdown the receiver.
    165 
    166 [[br]]
    167 '''Subtitle''' [=#point2.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    168 
    169 [[Image(source:/wiki/Wiki-Pictures/DE/Subtitle-OSD.jpg)]] [[br]]
    170 This overlay shows when you press the __"SUBTITLE"__ button. [[br]]
    171 It allows you to select/enable a subtitle during playback.
    172 
    173 [[br]]
    174 '''EPG''' [=#point2.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    175 
    176 [[Image(source:/wiki/Wiki-Pictures/DE/EPG-OSD.jpg)]] [[br]]
    177 This overlay shows when you press the __"EPG"__ button. [[br]]
    178 It shows a list of the program information from here you can setup a timer or search the EPG.
    179 
    180 [[br]]
    181 '''Program Info''' [=#point2.8] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    182 
    183 [[Image(source:/wiki/Wiki-Pictures/DE/Program-Info-OSD.jpg)]] [[br]]
    184 This Overlay shows when you press the __"INFO"__ button when in the EPG display. [[br]]
    185 This shows the current selected program information.
    186 
    187 [[br]]
    188 '''Player''' [=#point2.9] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    189 
    190 [[Image(source:/wiki/Wiki-Pictures/DE/Internal-Player-OSD.jpg)]] [[br]]
    191 This overlay shows when you press the __"PLAY"__ button. [[br]]
    192 It allows you to select a movie or recording to play it also has a basic file manager.
    193 
    194 [[br]]
    195 '''Favourite''' [=#point2.10] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    196 
    197 [[Image(source:/wiki/Wiki-Pictures/DE/Favourite-OSD.jpg)]] [[br]]
    198 This overlay shows when you press the __"FAV"__ button. [[br]]
    199 It allows you to brouse through your favourits lists.
    200 
    201 [[br]]
    202 '''Record''' [=#point2.11] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    203 
    204 [[Image(source:/wiki/Wiki-Pictures/DE/Record-OSD.jpg)]] [[br]]
    205 This overlay shows when you press the __"RECORD"__ button. [[br]]
    206 It allows you to set the record function on the current tv channel.
    207 
    208 [[br]]

  • wiki/pages/de/Git-Changelog

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.7.7 GIT Changelog''' [=#point3.7.7] ([Interface-Operation-en#point3.7 Information (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/Git_Changelog.jpg)]][[BR]]
    8 >
    9 > here you can git information.
    10 
    11 [[br]]
    12 

  • wiki/pages/de/Graphic-EPG

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.1.3 Graphischer EPG''' [=#point3.1.3] ([wiki:Interface-Operation#point3.1 Timer und EPG (zurück])   
    4 >
    5 >
    6 >[[Image(source:/wiki/Wiki-Pictures/DE/Graphical_EPG.jpg)]][[BR]]
    7 >
    8 Dieser zeigt das Programm mehrerer Sender gleichzeitig anhand eines Zeitstrahls an, [[BR]]
    9 um einen schnellen Überblick erhalten zu können, was wann wie lange läuft [[BR]]
    10 und was parallel dazu auf einem anderen Sender läuft.
    11 
    12 
    13 [[br]]
    14 
    15  '''Farb- und Extra Tasten Funktionen"
    16 
    17  
    18  ||'''rote Taste: (Timer)''' ||öffnet das Timer Menü um eine programmmierte Aufnahme zu erstellen||
    19  ||'''grüne Taste: (EPG)''' ||öffnet die ([wiki:EPG-Short-View#point3.10.1 EPG Kurzübersicht])||
    20  ||'''gelbe Taste: (einfach EPG)''' ||öffnet das ([wiki:Single-EPG#point3.10.2 Einfach EPG])||
    21  ||'''blaue Taste: (Multi EPG)''' ||öffnet das ([wiki:Multi-EPG#point3.10.3 Multi EPG])
    22  ||'''Taste 0 (EPG Suche):''' ||ruft die EPG Suchfunktion auf.||
    23  ||'''FAV Taste: (Favoriten)''' ||öffnet das Favoriten Menü um diese zu wechseln.||
    24  ||'''Info Taste: (Info)''' ||Zeigt die EPG Informationen zur aktuell ausgewählten Sendung.||
    25  
    26 
    27 Für Informationen wie Sie eine Aufnahme programmieren drücken Sie ([wiki:Records#point3.10.5  Aufnahmen])
    28 
    29 Für Informationen wie Sie eine EPG Suche mit der Taste '''0''' machen drücken Sie ([wiki:EPG-Search#point3.10.4 EPG Suche])

  • wiki/pages/de/HTTP-Settings

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.4.6 HTTP Settings''' [=#point3.5.4.6] ([wiki:Interface-Operation#point3.5.1 network (Back])
    4 >
    5 >Menu Picture place holder:
    6 >
    7 >[[Image(http://i.imgur.com/3TwQr.jpg, 400)]][[br]]
    8 >
    9 Here you can setup your HTTP interface.
    10 
    11 [[br]]
    12 
    13 ||'''Start HTTPD:''' ||Start the webserver.||
    14  ||'''User:''' ||Sets the zoom level of the EPG to show more or less of a time span of the shown programs.||
    15  ||'''Password:''' ||Set to yes to use picons or the alternative Picon sets in the infobar and EPG stored in /var/media/autofs/sda1/swapextensions/usr/local/share/titan/picons/ directory.||
    16  ||'''HTTPD Port:''' ||Should the EPG be deleted before a the timed scan.||
    17  ||'''IP for Stream:''' ||Behavior after the EPG scan is completed EPG scan: Nothing (Stand-By) or Switch Off (Deep Stand-By).||
    18  ||'''Stream Port:''' ||Scan for a Media Highway EPG stream during EPG scan.||
    19  ||'''Start RGUID:''' ||Scan for a Media Highway version 2 EPG stream during  EPG scan.||
    20  ||'''RGUID Port''' ||Scan for an OpenTV EPG stream during EPG scan.||
    21  
    22  To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
    23  
    24 [[br]]
    25 ----
    26 
    27  '''Coloured Button's Functions"
    28 
    29  The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
    30  please see below for more info on the functions of these buttons:.
    31  
    32  ||'''Text Button: (Keyboard)''' ||This will bring up the onscreen keyboard to edit the currently selected test string.||
    33 
    34 

  • wiki/pages/de/Hard-Disk

    r37411 r37661  
    1 [[TranslatedPages]]
    2 >----
    3 >'''3.5.5 Festplatte''' [=#point3.5.5] ([wiki:Interface-Operation#point3.5 zurück)])
    4 >
    5 >
    6 >
    7 >[[Image(source:/wiki/Wiki-Pictures/DE/system-Hard_Disk.jpg)]][[BR]]
    8 >
    9 Hier wird die Festplatte eingerichtet.[[BR]]
    10 
    11 [[br]]
    12 
    13  * ([wiki:Format-Hdd#point3.5.5.1 Festplatte formatieren])
    14  * ([wiki:Filesystem-Check#point3.5.5.2 Dateisystem prüfen])
    15  * ([wiki:Configure#point3.5.5.3 Festplatte konfigurieren])
    16  * ([wiki:Time-to-sleep#point3.5.5.4 Zeit bis Standby])
    17 
    18 [[BR]]

  • wiki/pages/de/History

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''1 TitanNit Info Inhaltsverzeichnis''' [=#point1] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 ----
    5 [[br]]
    6 This section conatins information on TitanNit and frequently asked questions about it.
    7 Please choose an item below to find more information.
    8 
    9 You may select a skip to a specific setup topic or scroll down to read the complete guide.
    10 {{{#!div style="width: 1100px; margin: auto"
    11  {{{#!table style="border: none"
    12   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    13   {{{#!div style="float: left"
    14 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/About.png,align=left,link=[#point1.1])]]
    15   }}}
    16   '''([#point1.1 Über])'''[[br]]
    17   {{{#!div style="float: left
    18 click here to find info about TitanNit
    19   }}}
    20   }}}
    21   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    22   {{{#!div style="float: left"
    23 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/History.png,align=left,link=[#point1.2])]]
    24   }}}
    25   '''([#point1.2 Geschichte])'''[[br]]
    26   {{{#!div style="float: left
    27 click here to find info on the beginnings of TitanNit
    28   }}}
    29   }}}
    30   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    31   {{{#!div style="float: left"
    32 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/Features.png,align=left,link=[#point1.3])]]
    33   }}}
    34   '''([#point1.3 Funktionsumfang])'''[[br]]
    35   {{{#!div style="float: left
    36 click here to find info on the various features of TitanNit
    37   }}}
    38   }}}
    39 }}}
    40 }}}
    41 
    42 {{{#!div style="width: 1100px; margin: auto"
    43  {{{#!table style="border: none"
    44   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    45   {{{#!div style="float: left"
    46 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/Frequnetly_Asked_Questions.png,align=left,link=[#point1.4])]]
    47   }}}
    48   '''([#point1.4 Frequently Asked Questions])'''[[br]]
    49   {{{#!div style="float: left
    50 Apendixcies/ references [[br]]to other setup related topics.
    51   }}}
    52   }}}
    53 }}}
    54 }}}
    55 [[br]]
    56 [[br]]
    57 
    58 ----
    59 '''1 Über''' [=#point1.1] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    60 ----
    61 TitanNit ist ein Betriebssystem für einige Kathrein und Atemio/Atevio Digital Satelliten Receiver. [[br]]
    62 [[br]]
    63 [[br]]
    64 
    65 ----
    66 '''1.1 Geschichte''' [=#point1.2]([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    67 ----
    68  * Angefangen hat es im April 2011. Unser Developer Nit hat still und heimlich drei Wochen lang am Grundstein für Titan gearbeitet. Nach der Vorstellung ist Obi mit an Bord gekommen und der Rest vom Team auch. Alle waren begeistert wie schnell so etwas entstehen kann.
    69  * Die Entwicklung war von Anfang an nonpublic Source, es war noch nicht klar in welche Richtung es gehen würde.
    70  * nach einer 6 monatigen Entwicklungszeit wurde unser Hardware Unterstützer Atemio auf dieses Projekt aufmerksam und hat Interesse gemeldet. Durch die jahrelange Enigma2 Zusammenarbeit hatte sie dadurch den Vorrang bekommen.
    71  * im Dezember 2011 wurde dann eine halbjährige Vereinbarung mit dem Hersteller Atemio getroffen.
    72  * nach der guten Zusammenarbeit wurde diese Vereinbarung dann bis jetzt verlängert.
    73  * die Grundidee für diese Projekt entstand aus mehreren Gründen:
    74   * die sh4 Receiver hatten schon immer durch den fehlenden Python Chip und fehlender Cpu Leistung immer ihre Probleme mit Enigma2
    75   * ständige Enigma2 Anpassungsvorgänge im TDT Git waren sehr umfangreich und haben viel Zeit gekostet
    76   * als andere Gui Alternative gab es noch Neutrino, diese Oberfläche hatte zu dieser Zeit keinen Twinsupport
    77   * statt diese dort einzubauen hat Nit für sich beschlossen, eine komplett neue Gui zu erstellen, die beide Gui Vorteile vereint.
    78   * Neutrinos Vorteil war eh und je die Geschwindigkeit
    79   * Enigma2s Vorteil war die einfache Einbindung von Skins und den Erweiterungen
    80   * diese beiden in Verbindung ist der Grundgedanke von Titan gewesen und wurde in sehr kurzer und zeitintensiver Entwicklungsphase realisiert.
    81 
    82 ----
    83 '''1.2 Funktionsumfang''' [=#point1.3] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    84 ----
    85 [[br]]
    86 '' Highlights von TitanNit ''
    87 
    88     - Leistungsstarkes Linux Betriebsystem
    89     - Schneller Systemstart
    90         - ca. 1 Sekunde aus dem Standby-Modus
    91         - ca. 25 Sekunden aus dem Deep-Standby-Modus
    92     - Schnelle Umschaltzeiten (unter 1 Sekunde)
    93     - Verschiedene Menüoberflächen (Skins) inkl. Anpassungsmöglichkeiten
    94     - Viele Einstellungsmöglichkeiten um das System auf die eigenen Bedürfnisse anzupassen
    95     - Backup / Restore Funktion
    96     - Übersichtliche Kanalliste mit Favoriten und anzeige der nachfolgenden Sendungen
    97     - Multi-Tuner
    98     - Plugin-Verwaltung
    99     - Unterstützung von vielen Medienformaten
    100     - Große Auswahl an Plugins
    101     - PC Programme zum konvertieren und ändern der Senderliste
    102     - Bildschirmschoner im Radio Modus
    103     - Fernbedienungstasten frei belegbar
    104     - Onlineupdate der Firmware
    105     - Geringer Speicherverbrauch
    106     - 24h Forum-Support
    107     - Wachsende Community
    108     - Webinterface
    109     - Android App "tiMote"
    110     - Windows App "tiView"
    111     - Bouquets Editor "SatchannelListEditor"
    112 
    113 [[br]]
    114 
    115 
    116 
    117 ----
    118 '''Frequently Asked Questions''' [=#point1.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
    119 ----
    120 [[br]]
    121 
    122 '''What is Titan?'''[[br]]TitanNit is a semi closed source replacement operating system for kathrein and Atemio/Atevio digital set top receivers designed to completly replace the factory software.
    123 [[br]]
    124 
    125 '''What can Titan do?'''[[br]]Titan was primarally designed to play/view and record live tv services from tresterial, cable and satellite, it can also be used to play/view the most popular video, audio, and picture formats, and many more lesser-known formats, including:
    126  Video - DVD-Video, VCD/SVCD, MPEG-1/2/4, DivX, XviD, Matroska
    127 Audio - MP3, AAC.
    128 Picture - JPG, GIF, PNG.
    129 
    130 
    131 These can all be played directly from the hard-drive or from a computer over a local network (LAN) internet IPTV services and media streams hosted by the [[wiki:Plugins-Player#point10.11 TiThek]] plugin.
    132 
    133  TitanNit can play DVD-Video movies (with and without menus) from ISO/IMG images and even ZIP/RAR-archives with the use of the [[wiki:Plugins-Player#point10.11 dvd-player plugin]].
    134  TitanNit has a simple user interface that's pleasant and easy to use.
    135 
    136 All these features enable your device to function as a full multimedia entertainment system for your tv for the whole family to enjoy.
    137 [[br]]
    138 [[br]]
    139 
    140 '''What features does TitanNit have?'''[[br]]See the complete list of supported features in the [[wiki:Versions#point6 software versions changelog]] for information of the offically supported features.
    141 [[br]]
    142 [[br]]
    143  
    144 '''Where can I suggest/request a new feature or function to be implemented into TitanNit?'''[[br]]You can log a NEW feature/function request in our tracker. Just make sure that you first remember to search for existing "Feature Requests" before logging a new request/ticket! (see [wiki:Troubleshooting#point12.1 12.1 Bug Reporting] for information on submitting a ticket).
    145 
    146 You may also post a copy of your suggestion in the feature-suggestion section of our [http://www.aaf-digital.info/forum/forum.php AAF Digital Forum] if you want it open for discussion,
    147 Please respect that your request only counts as a suggestion, there' s no guarantee that it will implemented soon or ever.
    148 
    149 Almost all users think their own ideas is the most important, and a very common comment is: "if you only add these features then TitanNit will be perfect for me".
    150 
    151 You could try bribing the devs with elaborate gifts :-) flattery will get you every where and agorant requests will most likely get your posts deleted or get you banned from the forum please follow the rules of the forum [http://www.aaf-digital.info/ here].
    152 [[br]]
    153 [[br]]
    154  
    155 '''When will this and that feature or function be supported by TitanNit?'''[[br]]TitanNit development is driven by the tasks that are important to the individual developers and to the hardware sponsors Atemio, if you have a funky idea or feature you wish implemented submit a request ticket (see [wiki:Troubleshooting#point12.1 12.1 Bug Reporting], but make an extensive search of the forum and tickets before requesting it as it has probally been sugested before.
    156 [[br]]
    157 [[br]]
    158 
    159 '''Is TitanNit, or the AAFTeam affiliated with Fortis, katherin or ..... or the hardware manufacturer of my Reciever?'''[[br]]No, TitanNit and its members are not in any way affiliated with the manufactures in any way. TitanNit is a third party operating system designed to replace the manufactures original operating system.
    160 [[br]]
    161 [[br]]
    162 
    163 '''Will the instalation of Titan Void my Warranty?'''[[br]]Yes probally but this software is tested to ensure it won't dammage your reciever and can be reverted at any time to a factory condition. please see [wiki:Supported-Receivers#point7 Supported Receivers] for a list of suspected supported receivers, If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated and verified.
    164 
    165 If the factory software was so feature packed and bugless there would be no need for software like TitanNit but sadly this is a world where software is driven by sales and purchases by the big players who request features, but TitanNit is a little different it was started just because the users/ devs wanted something better than what was handed to them by the manufacturer.
    166 [[br]]
    167 [[br]]
    168 
    169 '''Why is TitanNit Not available for my receiver model XXX?'''[[br]]TitanNit is funded by Atemio who supplys hardware to the devs in return for developing software for use on these devices.
    170 In future TitanNit may be available for your receiver as support in increaced, at this time Titan in in development for the Broadcom Mips Archeture for the upcomming release of the Atemio 5200 which will be the first non SH4 based reciever supported by TitanNit.
    171 [[br]]
    172 [[br]]
    173 
    174 '''How do I ...'''[[br]] I don't know I suggest you read the [wiki:Quick-Start-Guide#point0 Quick Start Guide], manual, check the rest of the wiki or proform a [http://www.aaf-digital.info/forum/search.php?search_type=1 search] on the forum, as it has most likely been asked before and you will find the answer, as a last resort post a question on the [http://www.aaf-digital.info/forum/forum.php AAF Digital Forum].
    175 [[br]]
    176 [[br]]
    177 
    178 '''Where should I put videos/music and pictures so that Titan can read it?''' [[br]]Anywhere you like. TitanNit can read off the local harddisk,usb sticks, or from network sources. Simply press "Add a Source" using the network Browser and browse away.
    179 >[[Image(source:/wiki/Wiki-Pictures/DE/Network-Browser.jpg, 25%)]][[br]]
    180 [[br]]
    181 [[br]]
    182 
    183 '''What is the default username and password to the built-in FTP server and telnet server?'''Both the default password and the user name is “root” (in lower case) as with many linux instalations.
    184 [[br]]
    185 [[br]]
    186 
    187 '''Can I watch recordings from my decoder when on holiday?'''[[br]]yes you can you will need to set up either a static ip on your home network or set up a dynadns server, from there you can log onto the web interface and use video lan to watch tv or your recordings.
    188 [[br]]
    189 [[br]]
    190 
    191 '''Can I thank and or Chat the TitanNit team?''[[br]]Yes sure you can jump on the [[http://www.aaf-digital.info/forum/ AAFforum]]  and leave a post and or stop by [wiki:Contact#point15 Skype] and request a invite the majority of us speak german, some of us speak english also.
    192 
    193 '''Do you accept donations?'''[[br]] the team is currently fully funded and no donations are nesessary but if you have some device that may be of use with titan feel free to contact us.
    194 
    195 '''How come the Wiki does not show how to operate feature or function.....?'''[[br]]Titan Is in development and is updated almost daily some features plugins or informations have yet to be merged in, this forum is open to editing by the community feel free to log in and add said feature's informatation to the wiki.
    196 [[br]]
    197 [[br]]
    198 
    199 ([#point1 Top of Page])
    200  
    201  
    202 
    203 

  • wiki/pages/de/Installation-Recovery

    r37411 r37661  
    1 [[TranslatedPages]]
    2 ----
    3 '''8 Installation / Recovery Inhaltsverzeichnis''' [=#point8] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    4 
    5 ----
    6 
    7 This section contains information on installation and removal of TitanNit from your receiver
    8 {{{#!div style="width: 1100px; margin: auto"
    9  {{{#!table style="border: none"
    10   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    11   {{{#!div style="float: left"
    12 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Atemio.png, 60px,align=left,link=http://www.atemio.de Atemio homepage)]]
    13   }}}
    14   '''SH4 Atemio'''[[br]]
    15   {{{#!div style="float: left
    16  [http://www.atemio.de Atemio homepage]
    17  * [#point8.001 8.001 Atemio510]
    18  * [#point8.002 8.002 Atemio520]
    19  * [#point8.003 8.003 Atemio530]
    20  * [#point8.004 8.004 Atemio7600]
    21  * [#point8.005 8.005 Atemio700]
    22  * [#point8.006 8.006 Atemio7000]
    23   }}}
    24   }}}
    25   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    26   {{{#!div style="float: left"
    27 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Fortis.png, 60px,align=left,link=http://www.fortis.co.kr Fortis homepage)]]
    28   }}}
    29   '''SH4 Fortis'''[[br]]
    30    {{{#!div style="float: left
    31  [http://www.fortis.co.kr Fortis homepage]
    32  * [#point8.011 8.011 Fortis Clone]
    33  * [#point8.012 8.012 Bootloader Installation]
    34  * [#point8.013 8.013 Fortis FS-9000]
    35  * [#point8.014 8.014 Fortis FS-9200]
    36  * [#point8.015 8.015 Fortis HS-9510]
    37  * [#point8.016 8.016 Fortis HX-8200]
    38  * [#point8.017 8.017 Fortis HS-7810]
    39   }}}
    40   }}}
    41  {{{#!td align=center valign=top style="border: none; font-size: 115%"
    42   {{{#!div style="float: left"
    43 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/homecast.png, 60px,align=left,link=http://www.myhomecast.nl Homecast homepage)]]
    44   }}}
    45   '''SH4 Homecast'''[[br]]
    46  {{{#!div style="float: left
    47  [http://www.myhomecast.nl Homecast homepage]
    48  * [#point8.021 8.021 Homecast Pro]
    49   }}}
    50   }}}
    51   |----
    52   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    53   {{{#!div style="float: left"
    54 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/IPBox.png, 60px,align=left,link=http://www.abipbox.com/ AB IPBox homepage)]]
    55   }}}
    56   '''SH4 IPBox'''[[br]]
    57   {{{#!div style="float: left
    58  [http://www.abipbox.com/ AB IPBox homepage]
    59  * [#point8.031 8.031 Ipbox91]
    60  * [#point8.032 8.032 Ipbox900]
    61  * [#point8.033 8.033 Ipbox910]
    62  * [#point8.034 8.034 Ipbox9000]
    63   }}}
    64   }}}
    65   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    66   {{{#!div style="float: left"
    67 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/kathrein.png, 60px,align=left,link=http://www.kathrein-gmbh.at kathrein homepage)]]
    68   }}}
    69   '''SH4 Kathrein'''[[br]]
    70   {{{#!div style="float: left
    71  [http://www.kathrein-gmbh.at kathrein homepage]
    72  * [#point8.041 8.041 Ufs910]
    73  * [#point8.042 8.042 Ufs912]
    74  * [#point8.043 8.043 Ufs913]
    75  * [#point8.044 8.044 Ufs922]
    76  * [#point8.045 8.045 Ufc960]
    77   }}}
    78   }}}
    79   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    80   {{{#!div style="float: left"
    81 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Spark.png, 60px,align=left,link=http://www.spark-tv.com Spark homepage)]]
    82   }}}
    83   '''SH4 Spark'''[[br]]
    84   {{{#!div style="float: left
    85  [http://www.spark-tv.com Spark homepage]
    86  * [#point8.051 8.051 Spark7111]
    87  * [#point8.052 8.052 Spark7162]
    88   }}}
    89   }}}
    90   |----
    91  {{{#!td align=center valign=top style="border: none; font-size: 115%"
    92   {{{#!div style="float: left"
    93 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Atemio.png, 60px,align=left,link=http://www.atemio.de Atemio homepage)]]
    94   }}}
    95   '''Mips Atemio'''[[br]]
    96   {{{#!div style="float: left
    97  [http://www.atemio.de Atemio homepage]
    98  * [#point8.061 8.061 Atemio5000 AKA Nemesis]
    99  * [#point8.062 8.062 Atemio5200]
    100  * [#point8.063 8.063 Atemio6000]
    101  * [#point8.064 8.064 Atemio6100]
    102  * [#point8.065 8.065 Atemio6200]
    103   }}}
    104   }}}
    105   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    106   {{{#!div style="float: left"
    107 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/beyonwiz.png, 60px,align=left,link=http://www.beyonwiz.com.au Beyonwiz homepage)]]
    108   }}}
    109   '''Mips Beyonwiz'''[[br]]
    110  {{{#!div style="float: left
    111  [http://www.beyonwiz.com.au Beyonwiz homepage]
    112  * [#point8.071 8.071 BeyonwizT4]
    113   }}}
    114   }}}
    115   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    116   {{{#!div style="float: left"
    117 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Goldern_Interstar.png, 60px,align=left,link=http://www.golden-interstar.pl Golden Interstar homepage)]]
    118   }}}
    119   '''Mips Golden Interstar'''[[br]]
    120   {{{#!div style="float: left
    121  [http://www.golden-interstar.pl Golden Interstar homepage]
    122  * [#point8.081 8.081 Xpeedlx1/2]
    123  * [#point8.082 8.082 Xpeedlx3]
    124   }}}
    125   }}}
    126   |----
    127   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    128   {{{#!div style="float: left"
    129 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Miraclebox.png, 60px,align=left,link=http://www.miraclebox.se miraclebox homepage)]]
    130   }}}
    131   '''Mips Miraclebox[[br]]
    132   {{{#!div style="float: left
    133  [http://www.miraclebox.se Miraclebox homepage]
    134  * [#point8.091 8.091 MBUltra]
    135  * [#point8.092 8.092 MBMini]
    136 }}}
    137 }}}
    138   {{{#!td align=center valign=top style="border: none; font-size: 115%"
    139   {{{#!div style="float: left"
    140 [[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Sezam.png, 60px,align=left,link=http://www.sezam-club.ru/ homepage)]]
    141   }}}
    142   '''Mips Sezam'''[[br]]
    143  {{{#!div style="float: left
    144  [http://www.sezam-club.ru/ homepage]
    145  * [#point8.101 8.101 Sezam-Marvel]
    146  * [#point8.102 8.102 Sezam-1000HD]
    147   }}}
    148   }}}
    149 }}}
    150 }}}
    151 
    152 
    153 
    154 '''SH4 Models'''
    155 ----
    156 '''8.1 Atemio510 and Fortis HS-7810''' [=#point8.001]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    157 ----
    158 '' Wie installiere ich ein Atemio 510 IRD Image? ''
    159  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    160  * Entpacken Sie die ZIP-Datei
    161  * Kopieren Sie nun die entpackte IRD-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    162      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    163      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    164  * USB Stick mit der IRD-Datei anschließen
    165  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die die CH+ am Gerät (1 Taste von rechts) solange gedrückt halten (ca. 15 Sekunden), bis „search IRD File…“ erscheint,
    166    anschließend beginnt die Installation. Erst danach die Taste loslassen
    167      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    168  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    169 
    170 [[br]]
    171   '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
    172 * [http://sbnc.dyndns.tv/trac/wiki/de/Remote-Device-Control#point4.6  iboot sh4 flashen and recovery ][[br]] 
    173 
    174 [#point8 Top of Page]
    175 [[br]]
    176 ----
    177 '''8.2 Atemio520''' [=#point8.002]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    178 ----
    179 '' Wie installiere ich ein Atemio 520 IRD Image? ''
    180  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    181  * Entpacken Sie die ZIP-Datei
    182  * Kopieren Sie nun die entpackte IRD-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    183      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    184      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    185  * Schalten Sie das Gerät aus.
    186  * USB Stick mit der IRD-Datei anschließen
    187  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Power Taste vorne am Gerät (die Taste in der Mitte) solange gedrückt halten (ca. 15 Sekunden), bis „search IRD File…“ erscheint,
    188    anschließend beginnt die Installation. Erst danach die Taste loslassen
    189      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    190  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    191 [[br]]
    192   '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
    193 * [http://sbnc.dyndns.tv/trac/wiki/de/Remote-Device-Control#point4.6  iboot sh4 flashen and recovery ][[br]] 
    194 
    195 [[br]]
    196 [#point8 Top of Page]
    197 [[br]]
    198 ----
    199 '''8.3 Atemio530''' [=#point8.003]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    200 ----
    201 '' Wie installiere ich ein Atemio 530 IRD Image? ''
    202  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    203  * Entpacken Sie die ZIP-Datei
    204  * Kopieren Sie nun die entpackte IRD-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    205      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    206      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    207  * Schalten Sie das Gerät aus.
    208  * USB Stick mit der IRD-Datei anschließen
    209  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die CH+ am Gerät (1 Taste von rechts) solange gedrückt halten (ca. 15 Sekunden), bis „search IRD File…“ erscheint,
    210    anschließend beginnt die Installation. Erst danach die Taste loslassen
    211      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    212  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    213 
    214 [[br]]
    215 [#point8 Top of Page]
    216 [[br]]
    217 ----
    218 '''8.4 Atemio7600 and Fortis HX-8200''' [=#point8.004]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    219 ----
    220 '' Wie installiere ich ein Atemio 7600 IRD Image? ''
    221  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.15 IRD Download Locations])
    222  * Entpacken Sie die ZIP-Datei
    223  * Kopieren Sie nun die entpackte IRD-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    224      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    225      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    226  * Schalten Sie das Gerät aus.
    227  * USB Stick mit der IRD-Datei anschließen
    228  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die CH+ am Gerät (1 Taste von rechts) solange gedrückt halten (ca. 15 Sekunden), bis „search IRD File…“ erscheint,
    229    anschließend beginnt die Installation. Erst danach die Taste loslassen
    230      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    231  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    232 [[br]]
    233   '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
    234 * [http://sbnc.dyndns.tv/trac/wiki/de/Remote-Device-Control#point4.6  iboot sh4 flashen and recovery ][[br]] 
    235 
    236 [[br]]
    237 [#point8 Top of Page]
    238 [[br]]
    239 ----
    240 '''8.5 Atevio700''' [=#point8.005]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    241 ----
    242 '' Wie installiere ich ein Atevio 700 IRD Image? ''
    243  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    244  * Entpacken Sie die ZIP-Datei
    245  * Kopieren Sie nun die entpackte IRD-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    246      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    247      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    248  * Schalten Sie das Gerät aus.
    249  * USB Stick mit der IRD-Datei anschließen
    250  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die die CH+ am Gerät (1 Taste von rechts) solange gedrückt halten (ca. 15 Sekunden), bis „search IRD File…“ erscheint,
    251    anschließend beginnt die Installation. Erst danach die Taste loslassen
    252      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    253  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    254 [[br]]
    255   '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
    256 * [http://sbnc.dyndns.tv/trac/wiki/de/Remote-Device-Control#point4.6  iboot sh4 flashen and recovery ][[br]] 
    257 
    258 [#point8 Top of Page]
    259 [[br]]
    260 ----
    261 '''8.6 Atevio7000 and Fortis FS-9000/9200''' [=#point8.006]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    262 ----
    263 '' Wie installiere ich ein Atevio 7000 IRD Image? ''
    264  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich aktuellest TitanNit Firmware. ([#point8.33 Download Locations])
    265  * Entpacken Sie die ZIP-Datei
    266  * Kopieren Sie nun die entpackte IRD-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    267      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    268      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    269  * Schalten Sie das Gerät aus.
    270  * USB Stick mit der IRD-Datei anschließen
    271  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die CH+ am Gerät (1 Taste von rechts) solange gedrückt halten (ca. 15 Sekunden), bis „search IRD File…“ erscheint,
    272    anschließend beginnt die Installation. Erst danach die Taste loslassen
    273      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    274  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    275 [[br]]
    276   '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
    277 * [http://sbnc.dyndns.tv/trac/wiki/de/Remote-Device-Control#point4.6  iboot sh4 flashen and recovery ][[br]] 
    278 [#point8 Top of Page]
    279 [[br]]
    280 ----
    281 '''SH4 Fortis based clone receiver detection (hardware profile)'''[=#point8.011]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    282 ----
    283 
    284 As it is virtually impossible to list every fortis clone box on this wiki and data would be repeated over and over again it is broken up into harware revisions to compair that to the atevio model of that box.
    285 This list will help you select the correct image and bootloader for your clone reciever below is a specifications list check the back of your manual included with your receiver and look at the table below to select the correct hardware model.
    286 See here for a full list of known Fortis ([wiki:Wiki#Supported-Receivers#point7 Clone Supported Recievers])
    287 
    288 {{{#!div style="width: 1000px; margin: auto"
    289 ||'''Model System'''||'''Tuner'''||'''CPU'''||'''RAM'''||'''ROM (Flash)'''||'''USB'''||'''PVR Funktion'''||'''CardReader'''||'''Common interface'''||'''Display'''||'''Width'''||'''features'''||
    290 ||[#point8.6 Fortis FS-9000 HD PVR]||DVB-S/S2 2||STI_7101 266 Mhz||192MB||32MB||2||Internal 2.5 or 3.5 SATA, external via USB||1 (*2)||2||12-digit 5x7matrix||43 cm|| ||
    291 ||[#point8.6 Fortis FS-9200 HD PVR]||DVB-S/S2 2||STI_7101 266 Mhz||192MB||32MB||2||eSATA & USB||1 (*2)||2||12-digit 5x7matrix||34 cm|| ||
    292 ||[#point8.5 Fortis HS-9510]||DVB-S/S2 1||STI_7101 266 Mhz||192MB||32MB||1||USB||1 (*2)||2||8-digit 14segment||34 cm|| ||
    293 ||[#point8.4 Fortis HX-8200 HD PVR]||DVB-S/S2, DVB-T2, DVB-C 1/2||STI_7105 450 Mhz||256MB||64MB||3||Internal 2,5´´SATA-HDD external via eSATA + USB||2||2||12-digit 5x7matrix||34 cm||Plug&Play Tuner, Youtube, Browser, FreeTV+||
    294 ||[#point8.1 Fortis HS-7810 HD PVR]||DVB-S/S2 1||STI_7110 450 Mhz||256MB||32MB||2||USB||1||2||4-digit 7segment||26 cm||YouTube, Browser, FreeTV+||
    295 }}}
    296 
    297 '''NOTE:'''[[BR]]
    298  * The Fortis HS-7810 is a clone of the Atemio510/520 Models[[BR]]
    299  * The Fortis HX-8200 is a clone of the Atemio7600 Model[[BR]]
    300  * The Fortis HS-9510 is a clone of the Atemio700 clone Model[[BR]]
    301  * The Fortis FS-9000/Fortis FS-9200 is a clone of the Atemio7000 Models
    302 
    303 
    304 '''Aditional Info'''
    305  
    306  * [#point8.012 8.012 Bootloader Installation] (required for a fortis/clone reciever to accept atemio software)
    307  * [#point8.111 8.111 Uninstallation On other Fortis Receivers]
    308  * [#point8.112 8.112 Update TitanNit]
    309  * [#point8.113 8.113 IRD Download Location]
    310 [[br]]
    311 [#point8 Top of Page]
    312 [[br]]
    313 ----
    314 '''8.021 Homecast''' [=#point8.021]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    315 ----
    316 '' How do I install an Homecast UPDATEUSB Image? ''
    317  * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
    318  * Extract the zip file
    319  * Now copy the unzipped IMG firmware file to a formatted FAT32 USB stick.
    320      Note: The USB stick should not be formatted with windows. Use a separate program, such as the
    321      " HP USB Disk Storage Format Tool" (freeware program).
    322      Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
    323  * Turn off the Receiver and disconnect all USB devices.
    324  * Connect the USB stick with the IMG file to your Receiver
    325 * Switch on (mains plug) while holding in the Power button on the unit (one button from the left) hold it down (about 3 seconds) until "LOAD SW" appears,
    326     then the installation starts. Only then release the button
    327      Note: If installation does not start, use a different USB stick.
    328  * The installation is finished when DONE appears on the receiver.
    329  * Restart the machine after by the main switch again to .
    330 [[br]]
    331 [#point8 Top of Page]
    332 [[br]]
    333 ----
    334 '''8.031 Ipbox91''' [=#point8.031]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    335 ----
    336 '' Wie installiere ich ein Ipbox 91 UPDATEUSB Image? ''
    337  * Besuchen Sie die AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    338  * Entpacken Sie die ZIP-Datei
    339  * Kopieren Sie nun die entpackte IMG-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    340      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    341      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    342  * Schalten Sie das Gerät aus.
    343  * USB Stick mit der IMG-Datei anschließen
    344  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Power Taste am Gerät (1 Taste von links) solange gedrückt halten (ca. 3 Sekunden), bis „LOAD SW“ erscheint,
    345    anschließend beginnt die Installation. Erst danach die Taste loslassen
    346      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    347  * Die Installation ist beended wenn DONE am Receiver erscheint.
    348  * Starten Sie das Gerät danach am Hauptschalter neu.
    349 [[br]]
    350 [#point8 Top of Page]
    351 [[br]]
    352 ----
    353 '''8.032 Ipbox900''' [=#point8.032]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    354 ----
    355 '' Wie installiere ich ein Ipbox 900 UPDATEUSB Image? ''
    356  * Besuchen Sie die AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    357  * Entpacken Sie die ZIP-Datei
    358  * Kopieren Sie nun die entpackte IMG-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    359      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    360      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    361  * Schalten Sie das Gerät aus.
    362  * USB Stick mit der IMG-Datei anschließen
    363  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Power Taste am Gerät (1 Taste von links) solange gedrückt halten (ca. 3 Sekunden), bis „LOAD SW“ erscheint,
    364    anschließend beginnt die Installation. Erst danach die Taste loslassen
    365      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    366  * Die Installation ist beended wenn DONE am Receiver erscheint.
    367  * Starten Sie das Gerät danach am Hauptschalter neu.
    368 [[br]]
    369 [#point8 Top of Page]
    370 [[br]]
    371 ----
    372 '''8.033 Ipbox910''' [=#point8.033]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    373 ----
    374 '' Wie installiere ich ein Ipbox 910 UPDATEUSB Image? ''
    375  * Besuchen Sie die AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    376  * Entpacken Sie die ZIP-Datei
    377  * Kopieren Sie nun die entpackte IMG-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    378      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    379      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    380  * Schalten Sie das Gerät aus.
    381  * USB Stick mit der IMG-Datei anschließen
    382  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Power Taste am Gerät (1 Taste von links) solange gedrückt halten (ca. 3 Sekunden), bis „LOAD SW“ erscheint,
    383    anschließend beginnt die Installation. Erst danach die Taste loslassen
    384      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    385  * Die Installation ist beended wenn DONE am Receiver erscheint.
    386  * Starten Sie das Gerät danach am Hauptschalter neu.
    387 [[br]]
    388 [#point8 Top of Page]
    389 [[br]]
    390 ----
    391 '''8.034 Ipbox9000''' [=#point8.034]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    392 ----
    393 '' Wie installiere ich ein Ipbox 9000 UPDATEUSB Image? ''
    394  * Besuchen Sie die AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    395  * Entpacken Sie die ZIP-Datei
    396  * Kopieren Sie nun die entpackte IMG-Firmware-Datei auf einen in FAT32 formatierten USB-Stick.
    397      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    398      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    399  * Schalten Sie das Gerät aus.
    400  * USB Stick mit der IMG-Datei anschließen
    401  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Power Taste am Gerät (1 Taste von links) solange gedrückt halten (ca. 3 Sekunden), bis „LOAD SW“ erscheint,
    402    anschließend beginnt die Installation. Erst danach die Taste loslassen
    403      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    404  * Die Installation ist beended wenn DONE am Receiver erscheint.
    405  * Starten Sie das Gerät danach am Hauptschalter neu.
    406 [[br]]
    407 [#point8 Top of Page]
    408 [[br]]
    409 ----
    410 '''8.041 Kathrein Ufs910''' [=#point8.041]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    411 ----
    412 '' Wie installiere ich ein Kathrein UFS910 Update Image? ''
    413  * Beim Installieren per usb wird der MNT Bereich im Image gelöscht das ist gleichzusetzen wie ein (Recovery-Image), beim Onlineupdate bleibt der Bereich erhalten.
    414  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    415  * Entpacken Sie die ZIP-Datei.
    416  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und nennen Sie in miniFLASH.img um.
    417      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    418      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    419  * Schalten Sie das Gerät aus.
    420  * USB Stick mit der Update-Datei anschließen
    421  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig mit der Fernbedinung 5 sekunden auf die Record Taste drücken bis „miniFlash search“ erscheint,
    422    anschließend beginnt die Installation. Erst danach die Taste loslassen
    423      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    424  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    425 [[br]]
    426 [#point8 Top of Page]
    427 [[br]]
    428 ----
    429 '''8.042 Kathrein UFS912''' [=#point8.042]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    430 ----
    431 '' Wie installiere ich ein Kathrein UFS912 Update Image? ''
    432  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    433  * Entpacken Sie die ZIP-Datei.
    434  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und platzieren sie die Datei im /kathrein/ufs912 Ordner
    435      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    436      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    437  * Schalten Sie das Gerät aus.
    438  * USB Stick mit der Update-Datei anschließen
    439  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Radio-Taste am Gerät solange gedrückt halten (ca. 5 Sekunden), bis „emergency boot“ erscheint,
    440    anschließend beginnt die Installation. Erst danach die Taste loslassen
    441      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    442  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    443 [[br]]
    444 [#point8.1 Top of Page]
    445 [[br]]
    446 ----
    447 '''8.043 Kathrein UFS913''' [=#point8.043]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    448 ----
    449 '' Wie installiere ich ein Kathrein UFS913 Update Image? ''
    450  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    451  * Entpacken Sie die ZIP-Datei.
    452  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und platzieren sie die Datei im /kathrein/ufs913 Ordner
    453      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    454      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    455  * Schalten Sie das Gerät aus.
    456  * USB Stick mit der Update-Datei anschließen
    457  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Radio-Taste am Gerät solange gedrückt halten (ca. 5 Sekunden), bis „emergency boot“ erscheint,
    458    anschließend beginnt die Installation. Erst danach die Taste loslassen
    459      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    460  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    461 
    462 [[br]]
    463 [#point8.1 Top of Page]
    464 [[br]]
    465 ----
    466 '''8.044 Kathrein UFS922''' [=#point8.044]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    467 ----
    468 '' Wie installiere ich ein Kathrein UFS922 Update Image? ''
    469  * Beim Installieren per usb wird der MNT Bereich im Image gelöscht das ist gleichzusetzen wie ein (Recovery-Image), beim Onlineupdate bleibt der Bereich erhalten.
    470  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    471  * Entpacken Sie die ZIP-Datei.
    472  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und platzieren sie die Datei im /kathrein/ufs922 Ordner
    473      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    474      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    475  * Schalten Sie das Gerät aus.
    476  * USB Stick mit der Update-Datei anschließen
    477  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Radio-Taste am Gerät solange gedrückt halten (ca. 5 Sekunden), bis „emergency boot“ erscheint,
    478    anschließend beginnt die Installation. Erst danach die Taste loslassen
    479      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    480  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    481 [[br]]
    482 [#point8 Top of Page]
    483 [[br]]
    484 ----
    485 '''8.045 Kathrein UFC960''' [=#point8.045]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    486 ----
    487 '' Wie installiere ich ein Kathrein UFC960 Update Image? ''
    488  * Beim Installieren per usb wird der MNT Bereich im Image gelöscht das ist gleichzusetzen wie ein (Recovery-Image), beim Onlineupdate bleibt der Bereich erhalten.
    489  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    490  * Entpacken Sie die ZIP-Datei.
    491  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und platzieren sie die Datei im /kathrein/ufc960 Ordner
    492      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    493      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    494  * Schalten Sie das Gerät aus.
    495  * USB Stick mit der Update-Datei anschließen
    496  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Radio-Taste am Gerät solange gedrückt halten (ca. 5 Sekunden), bis „emergency boot“ erscheint,
    497    anschließend beginnt die Installation. Erst danach die Taste loslassen
    498      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    499  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    500 [[br]]
    501 [#point8 Top of Page]
    502 [[br]]
    503 ----
    504 '''8.051 SPARK (7111)''' [=#point8.051]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    505 ----
    506 '' Wie installiere ich ein Spark (7111) Update Image? ''
    507  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    508  * Entpacken Sie die ZIP-Datei.
    509  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und platzieren sie die Dateien e2jffs2.img und uImage im /enigma2 Ordner
    510      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    511      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    512  * Schalten Sie das Gerät aus.
    513  * USB Stick mit der Update-Datei anschließen
    514  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Ok-Taste am Gerät solange gedrückt halten (ca. 5 Sekunden), bis „Forc“ erscheint,
    515    anschließend beginnt die Installation es erscheint "U LD" im Vfd. Erst danach die Taste loslassen
    516      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    517  * Nach der Installation es erscheint "SUCC" im Vfd bootet der Receiver neu und das Sendebild sollte erscheinen
    518 [[br]]
    519 [#point8 Top of Page]
    520 [[br]]
    521 ----
    522 '''8.052 SPARK7162''' [=#point8.052]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    523 ----
    524 '' Wie installiere ich ein Spark 7111 Update Image? ''
    525  * Besuchen Sie die das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    526  * Entpacken Sie die ZIP-Datei.
    527  * Kopieren Sie nun die entpackte Update-Firmware-Datei auf einen in FAT32 formatierten USB-Stick und platzieren sie die Dateien e2jffs2.img und uImage im /enigma2 Ordner
    528      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    529      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    530  * Schalten Sie das Gerät aus.
    531  * USB Stick mit der Update-Datei anschließen
    532  * Gerät einschalten (Netzstecker anschließen) und gleichzeitig die Ok-Taste am Gerät solange gedrückt halten (ca. 5 Sekunden), bis „Forc“ erscheint,
    533    anschließend beginnt die Installation es erscheint "U LD" im Vfd. Erst danach die Taste loslassen
    534      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    535  * Nach der Installation es erscheint "SUCC" im Vfd bootet der Receiver neu und das Sendebild sollte erscheinen
    536 [[br]]
    537 [#point8 Top of Page]
    538 [[br]]
    539 
    540 '''Mips Models'''
    541 ----
    542 '''8.061 Atemio-Nemesis''' [=#point8.061]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    543 ----
    544 '' Wie installiere ich ein Atemio Nemesis Update Image? ''
    545  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 Firmware Download Locations])
    546  * Entpacken Sie die ZIP-Datei auf ihr PC
    547  * Kopieren Sie den kompletten Ordner "atemio" auf auf einen in FAT32 formatierten USB-Stick.
    548      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    549      Des Weiteren empfehlen wir günstige USB Sticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    550  * Schalten Sie das Gerät aus.
    551  * USB Stick mit den zuvor kopierten "atemio" Ordner anschließen
    552  * Gerät einschalten (Netzstecker anschließen), das Image wir automatisch erkannt und mit dem Drücken Vol-Up Taste (dritte von links) wird die Installation des Image bestätigt,
    553    anschließend beginnt die Installation. Bitte warten bis die Installation vollständig abgeschlossen wurde.
    554      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    555  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen. Den USB Stick vorher entfernen.
    556 [[br]]
    557 [#point8 Top of Page]
    558 [[br]]
    559 ----
    560 '''8.062 Atemio5200''' [=#point8.062]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    561 ----
    562 '' Wie installiere ich ein Atemio 5200 Update Image? ''
    563  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    564  * Entpacken Sie die ZIP-Datei
    565  * Kopieren Sie nun die Firmware-Datei auf einen in FAT32 formatierten USB-Stick und entpacken Sie diese direkt auf dem USB-STick.
    566      Hinweis: Nach dem auspacken werden zwei Unterordner atemio/5x00 erstellt. Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    567      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    568  * Schalten Sie das Gerät aus.
    569  * USB Stick mit der Ausgepackten Firmware-Datei anschließen
    570  * Gerät einschalten (Netzstecker anschließen) und drücken Sie die CH+ am Gerät (1 Taste von rechts) wenn es im Vfd (Lcd Display) des Gerätes angezeigt wird solange bis „Flashing...bzw.U-rf“ erscheint,
    571    anschließend beginnt die Installation. Erst danach die Taste loslassen
    572      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    573  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    574 [[br]]
    575 [#point8 Top of Page]
    576 [[br]]
    577 ----
    578 '''8.063 Atemio6000''' [=#point8.063]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    579 ----
    580 '' Wie installiere ich ein Atemio 6000 Update Image? ''
    581  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    582  * Entpacken Sie die ZIP-Datei
    583  * Kopieren Sie nun die Firmware-Datei auf einen in FAT32 formatierten USB-Stick und entpacken Sie diese direkt auf dem USB-STick.
    584      Hinweis: Nach dem auspacken werden zwei Unterordner atemio/6000 erstellt. Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    585      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    586  * Schalten Sie das Gerät aus.
    587  * USB Stick mit der Ausgepackten Firmware-Datei anschließen
    588  * Gerät einschalten (Netzstecker anschließen) und drücken Sie die CH+ am Gerät (1 Taste von rechts) wenn es im Vfd (Lcd Display) des Gerätes angezeigt wird solange bis „Flashing...bzw.U-rf“ erscheint,
    589    anschließend beginnt die Installation. Erst danach die Taste loslassen
    590      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    591  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    592 [[br]]
    593 [#point8 Top of Page]
    594 [[br]]
    595 ----
    596 '''8.064 Atemio6100''' [=#point8.064]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    597 ----
    598 '' Wie installiere ich ein Atemio 6100 Update Image? ''
    599  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    600  * Entpacken Sie die ZIP-Datei
    601  * Kopieren Sie nun die Firmware-Datei auf einen in FAT32 formatierten USB-Stick und entpacken Sie diese direkt auf dem USB-STick.
    602      Hinweis: Nach dem auspacken werden zwei Unterordner atemio/6100 erstellt. Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    603      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    604  * Schalten Sie das Gerät aus.
    605  * USB Stick mit der Ausgepackten Firmware-Datei anschließen
    606  * Gerät einschalten (Netzstecker anschließen) und drücken Sie die CH+ am Gerät (1 Taste von rechts) wenn es im Vfd (Lcd Display) des Gerätes angezeigt wird solange bis „Flashing...bzw.U-rf“ erscheint,
    607    anschließend beginnt die Installation. Erst danach die Taste loslassen
    608      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    609  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    610 [[br]]
    611 [#point8 Top of Page]
    612 [[br]]
    613 ----
    614 '''8.065 Atemio6200''' [=#point8.065]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    615 ----
    616 '' Wie installiere ich ein Atemio 6200 Update Image? ''
    617  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 IRD Download Locations])
    618  * Entpacken Sie die ZIP-Datei
    619  * Kopieren Sie nun die Firmware-Datei auf einen in FAT32 formatierten USB-Stick und entpacken Sie diese direkt auf dem USB-STick.
    620      Hinweis: Nach dem auspacken werden zwei Unterordner atemio/6200 erstellt. Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    621      Des Weiteren empfehlen wir günstige USBSticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    622  * Schalten Sie das Gerät aus.
    623  * USB Stick mit der Ausgepackten Firmware-Datei anschließen
    624  * Gerät einschalten (Netzstecker anschließen) und drücken Sie die CH+ am Gerät (1 Taste von rechts) wenn es im Vfd (Lcd Display) des Gerätes angezeigt wird solange bis „Flashing...bzw.U-rf"“ erscheint,
    625    anschließend beginnt die Installation. Erst danach die Taste loslassen
    626      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    627  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen
    628 [[br]]
    629 [#point8 Top of Page]
    630 [[br]]
    631 ----
    632 '''8.071 Beyonwiz T4''' [=#point8.071]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    633 ----
    634 '' Wie installiere ich ein Atemio Nemesis Update Image? ''
    635  * Besuchen Sie die Atemio Homepage oder das AAF Digital Forum und laden Sie sich die aktuellste TitanNit Firmware. ([#point8.33 Firmware Download Locations])
    636  * Entpacken Sie die ZIP-Datei auf ihr PC
    637  * Kopieren Sie den kompletten Ordner "atemio" auf auf einen in FAT32 formatierten USB-Stick.
    638      Hinweis: Der USB Stick sollte nicht über Windows, sondern über ein separates Programm wie z.B. das "HP USB Disk Storage Format Tool" (Freeware Programm) formatiert werden.
    639      Des Weiteren empfehlen wir günstige USB Sticks mit einer geringen Speicherkapazität sowie Lese- und Schreibgeschwindigkeit.
    640  * Schalten Sie das Gerät aus.
    641  * USB Stick mit den zuvor kopierten "atemio" Ordner anschließen
    642  * Gerät einschalten (Netzstecker anschließen), das Image wir automatisch erkannt und mit dem Drücken Vol-Up Taste (dritte von links) wird die Installation des Image bestätigt,
    643    anschließend beginnt die Installation. Bitte warten bis die Installation vollständig abgeschlossen wurde.
    644      Hinweis: Sollte die Installation nicht starten, verwenden Sie einen anderen USB Stick.
    645  * Nach der Installation bootet der Receiver neu und das Sendebild sollte erscheinen. Den USB Stick vorher entfernen.
    646 [[br]]
    647 [#point8 Top of Page]
    648 [[br]]
    649 ----
    650 '''8.081 Goldern interstar Xpeedlx1/2''' [=#point8.081]  ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
    651 ----
    652 ''How do I install a Xpeedlx1/2 update image? ''
    653  * Visit the AAF digital forum and download the latest TitanNit firmware . ([#point8.33 IRD Download Locations])
    654  * Extract the zip file
    655  * Now copy the unzipped firmware folder "xpeedlx3"  to a formatted FAT32 USB stick.
    656     Note: The USB stick should not be formatted with windows, but a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program). Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
    657  * Turn off the Receiver and disconnect all USB devices.
    658  * Connect the USB stick with the update image file
    659  * Switch on (mains switch) and and when prompted on the vfd press the __Volume up__ button on the unit, then the installation begins. after the update starts release the __volume up__ button.
    660 
    661 Note: If installation does not start, use a different USB stick.
    662 •After successfully installing the receiver will reboot and the installed image should start-up
    663 [[br]]
    664 [#point8 Top of Page]