Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dsdp-pmc] RE: project plan viewer

Hi Dave,
after strong arguments by the Modeling / XML experts, the Project Plan
XML format was changed to use namespace-aware XML. For details, see
I think the simplest way to convert your current plan into the
namespace-aware variant is this:
  • Replace the <plan> element on line 3 by this:
    <plan plan-format="1.0" xmlns="" xmlns:html="" name="RTSC">
  • Replace each <![CDATA[ by this:
    <html:div xmlns="">
  • Replace each ]]> by this:
  • You'll need to make sure that your HTML is valid XHTML, that is: every <p> tag closed by </p> and the like.
    The WTP XML Editor will help you with its Validator to see what HTML is invalid -- an advantage over the
    previous opaque CDATA sections.
Attached is a shellscript to make that conversion for you, as well as a converted version of your plan (the shellscript run on it).
Let me know how it goes. I'm one of the culprits making this change, and most of
the docs are from me :-)
The Wiki page has hints how to install WTP and its XML catalog properly:
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member

From: Russo, David [mailto:d-russo@xxxxxx]
Sent: Saturday, September 06, 2008 3:37 AM
To: Gaff, Doug; Oberhuber, Martin
Cc: Russo, David
Subject: project plan viewer

Doug or Martin,


When I try to view the RTSC project plan (, I get a bunch of unformatted XML.  There was a time when this showed a nice rendering of the project plan.  I've tried different browsers (IE and firefox 3.x) and even the tml project, but I don't seem to get a reasonable rendering of the project plan.


Is there something I should be doing in the RTSC project meta files to enable a good rendering?







<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="";?>
<plan plan-format="1.0" xmlns=""; xmlns:html=""; name="Project">
   <release projectid="dsdp.rtsc" version="0.1"/>
   <introduction><html:div xmlns="";>
     <p>The <a href="";><b>Real-Time Software Components (RTSC)</b></a>
project provides foundational tools and low-level runtime content to enable
component-based development using the C language targeting all embedded platforms.
While other component technologies exist for embedded systems,
RTSC is unique in that components scale down to highly resource constrained
embedded systems including DSPs and 16-bit micro-controllers and easily bridge to Rich Client Platforms.
   <release_deliverables><html:div xmlns="";>
   Until we pass the IPzilla gate, there are no deliverables.  Once this is done, we expect a 
   download largely equivalent to the 
   <a href="";>XDCtools 3.X product</a> from TI
      <preamble><html:div>Since RTSC is moving an existing TI product under active development to the eclipse infrastructure the milestones below reflect progress 
      toward this transition rather than progress on the themes below.</html:div></preamble>
      <milestone date="9/30/2008" milestone="M1"><html:div>initial source available from SVN</html:div></milestone>
      <milestone date="10/30/2008" milestone="M2"><html:div>weekly integration cycle on SVN</html:div></milestone>
      <milestone date="11/30/2008" milestone="M3"><html:div>source rebuildable outside TI</html:div></milestone>
      <milestone date="1/30/2009" milestone="0.1"><html:div>first open release</html:div></milestone>
   <target_environments><html:div xmlns="";>
   XDCtools contains a number of command line tools that compiled
against version 1.5.0 of the Java Platform APIs (i.e., Java 2 Platform,
Release 1.5.0 SE), and designed to run on version 1.5.0 of the Java
Runtime Environment, Standard Edition.
<p> In addition, these tools contain several Eclipse plugins that integrate these tools into
Eclipse Platform 3.2 and the C/C++ Development Tools (CDT) 3.2 or later.
<p>Finally, there are several portable C/C++-based utilities that are currently compiled for both  
a Windows (XP, ...) or Linux (Red Hat 3.4.6-8) platform.
   <compatibility_with_previous_releases><html:div xmlns="";>
<p>The goal of the first release of the XDCtools is to be binary backward compatible with 
the XDCtools 3.10 release from TI.</p>
<p><strong>API Contract Compatibility:</strong>.
<p><strong>Binary (plug-in) Compatibility:</strong>. 
<p><strong>Source Compatibility:</strong>  
<p><strong>Workspace Compatibility:</strong> 
     <theme name="Eclipse Integration and Infrastructure Migration">
        <description><html:div>The XDCtools 3.10 Eclipse integration relies on TI-specific modifications 
        to an older Eclipse platform.  We need to eliminate these dependencies to enable RTSC use in state-of-the-art 
        Eclipse platforms.  In addition to work on the code base, we need to transition the code base from TI internal 
        infrastructure (source change control, bug tracking, builds etc.) to eclipse infrastructure</html:div></description>
     <theme name="Ease of Use">
        <description><html:div>More docs, primers, examples, and refinement of repository management and path tools.</html:div></description>
     <theme name="Graphical Configuration">
        <description><html:div>XDCtools 3.10 has an experimental graphical configuration tool integrated into Eclipse.
        This tool needs to be polished and made robust for mass-market use.</html:div></description>
     <theme name="Real-Time Analysis">
        <description><html:div>XDCtools 3.11 has an experimental tools that monitor embedded targets in real-time to provide 
        visibility into the current state of the system.  These tools, like graphical configuration, need polishing.</html:div></description>
     <theme name="Other">
      <description><html:div xmlns="";>
Features and bugs that we plan to address in the next release that are not categorized into one of the themes above.

In order not to overload the project plan with less important items, only those marked with a <b>"plan"</b> or <b>"investigate"</b> keyword will be
added to the project plan. The pool of all known items to add to the plan can be found from the following bugzilla queries. 

Back to the top