[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: Re: [equinox-dev] Incubator commit rights for Kim Horne
|
To Virtual Team,
If we turn OSGi/Equinox into a pile of bloatware, we should all be ashamed.
To all, please keep a focus on the non-functional requirements that have
made OSGi a success. small, limited pre-reqs, etc. Think "cell phone"
as a base.
jim.
________________________________________
Jim Colson, Chief Architect - IBM Client Software
Distinguished Engineer
IBM Academy of Technology
Board Member - IT Architect Certification
11501 Burnet Rd. Austin, TX 78758
Ph 512-823-7357, Fax 512-838-0962
email: jccolson@xxxxxxxxxx
Admin: Christine Willis 512-838-3667
email: Christine_Willis@xxxxxxxxxx
"Alex Blewitt"
<alex.blewitt@gma
il.com> To
Sent by: "Equinox development mailing list"
equinox-dev-bounc <equinox-dev@xxxxxxxxxxx>
es@xxxxxxxxxxx cc
Subject
10/26/2006 04:04 Re: Re: [equinox-dev] Incubator
PM commit rights for Kim Horne
Please respond to
Equinox
development
mailing list
<equinox-dev@ecli
pse.org>
On 25/10/06, BJ Hargrave <hargrave@xxxxxxxxxx> wrote:
>
> But I find the use of XSLT to be stomach turning. XSLT programming is not
> easy. I support Peter's thoughts on having a programmatic way of
> transforming metadata.
I think XSLT is *exactly* the kind of thing to use here. XPath is an
incredibly flexible way of being able to filter and transpose XML
documents, and is definitely the right choice.
A dumb programmatic API might be able to generate simple XPath
expressions for those that prefer writing in code, but don't turn a
great solution into a weak one just so that it can be written in a way
unsuited to the task.
Alex.
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
