On 8 October 2011 02:08, sebb <seb...@gmail.com> wrote:
> On 8 October 2011 00:47, Donald Whytock <dwhyt...@gmail.com> wrote:
>> On Fri, Oct 7, 2011 at 6:48 PM, sebb <seb...@gmail.com> wrote:
>>> I'm now thinking it might be better to convert some of the tags to
>>> attributes, for example:
>>>
>>>    <podling name="Accumulo" resource="accumulo" status="current">
>>>
>>> These are all relatively short fields and I think it would make the
>>> file shorter and easier to read.
>>> I used "resource" rather than "id" because that seems to be what clutch 
>>> uses.
>>
>> <podlings>
>>  <podling
>>    name="name"
>>    resource="resource"
>>    status="status"
>>    startdate="startdate"
>>    [enddate="enddate"]>
>>    <description>
>>      description
>>    </description>
>>    <mentors>
>>      <mentor>mentor</mentor>
>>    </mentors>
>      <sponsor>Sponsor (might be failrly long)</sponsor>
>>  </podling>
>> <podlings>
>>
>> Look good?
>
> It would be easier to edit and navigate if the attributes were all on
> the same line as the <podling> tag
>
> What do we do with projects such as "Manifold Connector Framework
> (ManifoldCF)" ?
>
> That name is too long for a navigation list and probably some other places.
>
> Perhaps we need two types of name.
> Probably better to use the short name by default, and allow the long
> name to be used in some places.
>
> In that case, we would need to add an optional longName or fullName attribute.
>
> BTW, I've created an XSL stylesheet that can generate project-menu.ent
> (which is how I found that Oozie was missing).
> It uses the original podlings.xml format (except I converted <website>
> into <resource>), but should be easy to change to use attributes
> instead.
> I'll commit it shortly.

Updated to use new format and committed.

Output is to project-menu.tmp file currently; edit build.xml
generate-menu target to change this to .ent once podlings.xml is
updated.

> I've not started looking at generating projects/index.xml yet.

And I won't now have time until Sunday earliest.

>
>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to