Changeset 59 for site/xdocs
- Timestamp:
- 10/07/08 13:40:05 (5 years ago)
- Location:
- site/xdocs
- Files:
-
- 15 modified
-
api_landing.xml (modified) (4 diffs)
-
blackberry/landing.xml (modified) (2 diffs)
-
decisions.xml (modified) (1 diff)
-
discussion.xml (modified) (1 diff)
-
downloads.xml (modified) (1 diff)
-
howtos.xml (modified) (2 diffs)
-
index.xml (modified) (1 diff)
-
iphone/landing.xml (modified) (1 diff)
-
maintain_code.xml (modified) (1 diff)
-
security.xml (modified) (2 diffs)
-
site.xml (modified) (1 diff)
-
stylesheets/site.xsl (modified) (1 diff)
-
tools.xml (modified) (3 diffs)
-
winmobile/landing.xml (modified) (2 diffs)
-
winoutlook/landing.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
site/xdocs/api_landing.xml
r8 r59 17 17 <th>Name</th> 18 18 <th>Description</th> 19 <th width=" 9%">Link</th>20 <th width=" 9%">Schemas</th>19 <th width="10%">Link</th> 20 <th width="10%">Schemas</th> 21 21 </tr> 22 22 … … 27 27 client .tel applications and TelHosting Software</td> 28 28 <td class="right"><a href="/api/client-soap/index.html" target="_blank"><img src="/pages/images/icon_ie.gif"/></a><a href="/api/client-soap/ClientSoapAPI.pdf" target="_blank"><img src="/pages/images/icon_pdf2.gif"/></a></td> 29 <td class="right">30 <a href="/api/client-soap/schemas.zip" target="_blank"><img src="/pages/images/icon_zip.gif"/></a>29 <td> 30      <a href="/api/client-soap/schemas.zip" target="_blank"><img src="/pages/images/icon_zip.gif"/></a> 31 31 </td> 32 32 </tr> … … 39 39 <a href="/api/admin-soap/AdminSoapAPI.pdf" target="_blank"><img src="/pages/images/icon_pdf2.gif"/></a></td> 40 40 <td class="right"> 41 <a href="/api/admin-soap/schemas.zip" target="_blank"><img src="/pages/images/icon_zip.gif"/></a>41      <a href="/api/admin-soap/schemas.zip" target="_blank"><img src="/pages/images/icon_zip.gif"/></a> 42 42 </td> 43 43 </tr> … … 48 48 services: SO member database, encryption key store, and others</td> 49 49 <td class="right"><a href="/api/so-soap/index.html" target="_blank"><img src="/pages/images/icon_ie.gif"/></a> 50 <a href="/api/so-soap/SOSoapAPI.pdf" target="_blank"><img src="/pages/images/icon_pdf2.gif"/></a>50 <a href="/api/so-soap/SOSoapAPI.pdf" target="_blank"><img src="/pages/images/icon_pdf2.gif"/></a> 51 51 </td> 52 52 <td class="right"> 53 <a href="/api/so-soap/schemas.zip" target="_blank"><img src="/pages/images/icon_zip.gif"/></a>53      <a href="/api/so-soap/schemas.zip" target="_blank"><img src="/pages/images/icon_zip.gif"/></a> 54 54 </td> 55 55 </tr> -
site/xdocs/blackberry/landing.xml
r49 r59 10 10 <body> 11 11 12 <section name=".tel Blackberry ®Application ">12 <section name=".tel Blackberry Application "> 13 13 14 14 <table class="tblresel" cellpadding="0" cellspacing="0" border="0"> … … 83 83 <tr> 84 84 <td class="left">Known Limitations</td> 85 <td class="right">See the <a href="/trac/wiki/BlackberryApplication">wiki page</a>.85 <td class="right">See the <a href="/trac/wiki/BlackberryApplication">wiki</a>. 86 86 </td> 87 87 </tr> -
site/xdocs/decisions.xml
r8 r59 25 25 26 26 <ul type="none"> 27 <li>< span class="orangetext">+1</span> is a positive vote.</li>28 <li>< span class="orangetext">+/-0</span> means you abstain or have no opinion.27 <li><b>+1</b> is a positive vote.</li> 28 <li><b>+/-0</b> means you abstain or have no opinion. 29 29 This vote makes little sense, because you appear to have no opinion. However, 30 30 too many abstaining committers and contributors means the discussed matter 31 31 needs more investigation, so the vote will be postponed. </li> 32 <li>< span class="orangetext">-1</span> is a negative vote.</li>32 <li><b>-1</b> is a negative vote.</li> 33 33 </ul> 34 34 <p>When voting, please provide arguments or concerns, especially in the case of a zero or -
site/xdocs/discussion.xml
r39 r59 29 29 <tr> 30 30 <td class="left">RSS feed</td> 31 <td class="right">Community news in a handyformat</td>31 <td class="right">Community news in a real-time format</td> 32 32 <td class="right"><a href="/trac/wiki/RssFeed"><img src="/pages/images/icon_ie.gif"/></a></td> 33 33 </tr> 34 34 <tr class="alt"> 35 35 <td class="left">Submit a bug</td> 36 <td class="right"> How to log a request or issue to the issue tracking system</td>36 <td class="right">Log a request or issue to the tracking system</td> 37 37 <td class="right"><a href="/trac/wiki/BugTracker"><img src="/pages/images/icon_ie.gif"/></a></td> 38 38 </tr> -
site/xdocs/downloads.xml
r54 r59 25 25 <p>Click the links below to download the latest versions of currently available applications.</p> 26 26 <ul> 27 <li><a href="/pages/blackberry/landing.html">.tel Blackberry <sup>®</sup>Application</a></li>28 <li><a href="/pages/winmobile/landing.html">.tel Windows Mobile <sup>®</sup>Client</a> </li>29 <li><a href="/pages/winoutlook/landing.html">.tel Outlook <sup>®</sup>Plug-in</a> </li>30 <li><a href="/pages/iphone/landing.html">.tel iPhone <sup>®</sup>Application</a></li>27 <li><a href="/pages/blackberry/landing.html">.tel Blackberry Application</a></li> 28 <li><a href="/pages/winmobile/landing.html">.tel Windows Mobile Client</a> </li> 29 <li><a href="/pages/winoutlook/landing.html">.tel Outlook Plug-in</a> </li> 30 <li><a href="/pages/iphone/landing.html">.tel iPhone Application</a></li> 31 31 </ul> 32 32 <p><b>Note:</b> Please remember that these are not official releases of these applications; all -
site/xdocs/howtos.xml
r8 r59 36 36 </tr> 37 37 <tr class="alt"> 38 <td class="left">Building Outlook plug-in</td>38 <td class="left">Building Outlook<br/> plug-in</td> 39 39 <td class="right">Step-by-step instructions on checking out and building source code 40 40 of the <a href="/pages/winoutlook/landing.html">Microsoft Office® Outlook® plug-in</a> </td> … … 42 42 </tr> 43 43 <tr> 44 <td class="left">Building Pocket Outlook®plug-in</td>44 <td class="left">Building Windows Mobile plug-in</td> 45 45 <td class="right">Step-by-step instructions on checking out and building source code 46 46 of the <a href="/pages/winmobile/landing.html">Pocket Outlook® plug-in</a> </td> -
site/xdocs/index.xml
r54 r59 7 7 <section name="Developers"> 8 8 <p> Welcome to the .tel Developer Community, home of client applications for .tel domains. 9 Here you can find <b>free open -source applications</b> providing .tel service for10 <a href="/pages/winoutlook/landing.html">Microsoft Outlook< sup>®</sup></a>,11 <a href="/pages/winmobile/landing.html">Windows Mobile< sup>®</sup></a>,12 <a href="/pages/iphone/landing.html">iPhone< sup>®</sup></a>13 and <a href="/pages/blackberry/landing.html">BlackBerry< sup>®</sup></a> devices. You can download ready applications, browse and9 Here you can find <b>free opensource applications</b> providing .tel service for 10 <a href="/pages/winoutlook/landing.html">Microsoft Outlook</a>, 11 <a href="/pages/winmobile/landing.html">Windows Mobile</a>, 12 <a href="/pages/iphone/landing.html">iPhone</a> 13 and <a href="/pages/blackberry/landing.html">BlackBerry</a> devices. You can download ready applications, browse and 14 14 edit their source code, share impressions at our forums, or even write your 15 15 own application for a new platform or software application! </p> -
site/xdocs/iphone/landing.xml
r54 r59 10 10 <body> 11 11 12 <section name=".tel iPhone ®Application ">12 <section name=".tel iPhone Application "> 13 13 14 14 <table class="tblresel" cellpadding="0" cellspacing="0" border="0"> -
site/xdocs/maintain_code.xml
r8 r59 18 18 please include maximum information into your report, such as version numbers, 19 19 OS environment, error log, configuration settings, etc. Ideally, a bug should come with 20 a test that reproduces it, but this might be too much to ask for. 21 <br/>It is also crucial that you give your patches meaningful 20 a test that reproduces the error. It is also crucial that you give your patches meaningful 22 21 names; for instance, instead of "1.patch", you can name the patch 23 22 "708-web-brokenlinks.patch", which would associate the patch with bug ID 708 and 24 23 hint that the patch fixes broken links on the website. 25 24 </li> 26 <li><b>Patches</b>: A patch 27 is a diff demonstrating a code change. 25 <li><b>Patches</b>: A patch is a diff demonstrating a code change. 28 26 Code changes related to one problem should come in one patch. The patch should follow 29 the unified syntax and, preferably, be run against the latest code version. Merging 30 parallel code changes can be tedious. 31 <br/>Once your patch is ready, create a new ticket in the tracker or attach the patch 32 to an existing related ticket. </li> 33 <li><b>Commits</b>: When committing a patch, please indicate the bug ID in the commit message. 34 Trivial changes can be committed without 35 pre-commit checks, at the committer's risk. All other changes are subject to pre-commit 36 testing to ensure stability of code. Subprojects can choose to override these rules for 37 development branches. </li> 38 <li><b>Reverting changes</b>: Any commit that breaks 39 the build or has been vetoed by a committer must be reversed. </li> 27 the unified syntax and, preferably, be run against the latest code version. Once your 28 patch is ready, create a new <a href="/trac/newticket">ticket</a> in the tracker or attach the patch 29 to an existing related ticket. When committing a patch, please indicate the bug ID in the commit message. 30 </li> 40 31 <li><b>Large-scale development</b>: Before 41 32 starting on a big chunk of functionality, check the forum and Wiki for a list of 42 33 active assignments. This can help you avoid 43 duplication of effort and/or find teammates to work with. Large-scale changes,34 duplication of effort and/or find teammates with whom you may work. Large-scale changes, 44 35 new features, and doubtful fixes 45 36 should be discussed on the forum before the commit. </li> 46 <li><b>Branches</b>: Subprojects and groups can create branches 47 in the repository for release cycles and parallel development. Merge of the branch with 48 the main trunk should be performed after the independent development cycle completes. 49 Documenting each branch by a short STATUS file is highly advisable.</li> 50 <li> <b>Licensing</b>: Any data committed to the .tel repository is considered 51 donated to the .tel community. Any code, document or binary not intended 52 for community use or not subject for the community license is 53 must be clearly marked as such. 54 </li> 37 <li><b>Branches</b>: The applications repository has tags and branches to 38 allow parallel development. Please use those for individual work on an existing application. We shall help 39 you merge the changes periodically. </li> 55 40 </ul> 56 41 </section> -
site/xdocs/security.xml
r8 r59 30 30 can be stored in a NAPTR record without containing special characters.</li> 31 31 </ol> 32 <p class="note"><span class="header">Note:</span> We do NOT recommend storing sensitive32 <p><b>Note:</b> We do NOT recommend storing sensitive 33 33 personal information such as credit card numbers inside a .tel domain. This is 34 34 not the purpose of the .tel. </p> … … 38 38 </p> 39 39 <p>For more information on the .tel security model, please read our whitepaper 40 <a href="/docs/privacy.pdf">Pr ivacy in .tel</a>.</p>40 <a href="/docs/privacy.pdf">Protecting .tel Contact Data</a>.</p> 41 41 </section> 42 42 -
site/xdocs/site.xml
r23 r59 10 10 <body> 11 11 12 <section name=" Updating the Website">12 <section name="Website Updates"> 13 13 <p>The .tel developer website consists of a number of Wiki pages, which 14 14 can be edited directly in a browser, and static HTML pages, which are generated -
site/xdocs/stylesheets/site.xsl
r55 r59 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 2 3 <!--4 *****************************5 6 N.B. any tags with more than one attribute need to be coded using xsl:attribute7 for all but the first attribute.8 9 This is to ensure that JDK 1.4 and 1.5 generate the attributes in the same order,10 and thus avoid huge numbers of irrelevant differences when the JDK changes.11 12 For example:13 14 <img alt="Alt">15 <xsl:attribute name="border">0</xsl:attribute>16 <xsl:attribute name="src">xxx.gif</xsl:attribute>17 </img>18 19 *****************************20 -->21 3 <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> 22 4 <xsl:import href="common.xsl"/> -
site/xdocs/tools.xml
r54 r59 13 13 14 14 <tr> 15 <th >Name</th>15 <th width="20%">Name</th> 16 16 <th>Description</th> 17 17 <th>Link</th> … … 19 19 20 20 <tr> 21 <td class="left">Java <sup>®</sup>Utilities</td>22 <td class="right">Set of Java classes and libraries from TelHosting Software21 <td class="left">Java Utilities</td> 22 <td class="right">Set of Java<sup>®</sup> classes and libraries from TelHosting Software 23 23 to simplify development of Java applications</td> 24 24 <td class="right"><a href="/downloads/tools/telnic-util-1.0.zip"><img src="/pages/images/icon_zip.gif"/></a></td> 25 25 </tr> 26 26 <tr class="alt"> 27 <td class="left">iPhone <sup>®</sup>SDK</td>28 <td class="right">An SDK for quick development of iPhone applications27 <td class="left">iPhone SDK</td> 28 <td class="right">An SDK for quick development of iPhone<sup>®</sup> applications 29 29 that need access to .tel data from DNS servers.</td> 30 30 <td class="right"><a href="/downloads/tools/iphone_sdk.zip"><img src="/pages/images/icon_zip.gif"/></a> … … 49 49 50 50 <tr> 51 <th >Name</th>51 <th width="20%">Name</th> 52 52 <th>Description</th> 53 53 <th>Link</th> -
site/xdocs/winmobile/landing.xml
r49 r59 9 9 <body> 10 10 11 <section name=".tel Windows Mobile ®Client">11 <section name=".tel Windows Mobile Client"> 12 12 <table class="tblresel" cellpadding="0" cellspacing="0" border="0"> 13 13 <tr> … … 73 73 <tr> 74 74 <td class="left">Known Limitations</td> 75 <td class="right"> None identified.75 <td class="right">See the <a href="/trac/wiki/WinMobileClient">wiki</a>. 76 76 </td> 77 77 </tr> -
site/xdocs/winoutlook/landing.xml
r54 r59 79 79 <tr> 80 80 <td class="left">Known Limitations</td> 81 <td class="right"> None identified.81 <td class="right">See the <a href="/trac/wiki/OutlookPlugin">wiki</a>. 82 82 </td> 83 83 </tr>








