Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [phoenix-dev] Phoenix Meeting minutes - Sept 2/2005 11:00am

Denis,

XML is not just useful for rendering the content to multiple output formats. It is also very useful for reusing the same information in multiple places, e.g. to roll up milestone plans. We actually use XML in two main ways. First, we use well-formed XHTML to support styling. Second, we use XML to represent structured data. This is much easier to do than setting up a relational database.

Most developers do not need to understand anything about XSLT or XPath, just as they do not need to understand CSS, _javascript_, or PHP. For XML based authoring, authors just need to know the tags, which are usually the same as HTML. For data oriented XML, we provide a schema which our XML editors read to provide content assist.


Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx


Denis Roy <denis.roy@xxxxxxxxxxx>
Sent by: phoenix-dev-bounces@xxxxxxxxxxx

09/13/2005 07:39 AM

Please respond to
"For developers on the new Eclipse.org website project."
To
"For developers on the new Eclipse.org website project." <phoenix-dev@xxxxxxxxxxx>
cc
Subject
Re: [phoenix-dev] Phoenix Meeting minutes - Sept 2/2005 11:00am





I was senior developer working on a commercial XML/XSLT-driven web
application back in 2001.

IMHO the beauty and strength of XML content and XSLT is for rendering
the same content different ways. For instance, a database recordset in
XML can be transformed to html, csv, rtf, pdf, plaintext and many more
using different XSLT stylesheets.

However, our website will basically be a 1:1 content to layout ratio, so
I don't think there are any clear advantages that warrant the added
overhead of running an XSL transformer engine, plus the added complexity
of teaching web designers all about XML, XSLT, XPath, and so-forth.

For basic html templating ("put top portion here", "put some generic
footer here", "put a navigation bar here") PHP can do everything XSLT
can, and more.


D.




Arthur Ryman wrote:
>
> FYI,
>
> WTP uses XML for content and XSLT for styling, not PHP. I believe PHP
> can apply XSLT, correct?
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: http://ryman.eclipsedevelopersjournal.com/
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
>
>
> *Denis Roy <denis.roy@xxxxxxxxxxx>*
> Sent by: phoenix-dev-bounces@xxxxxxxxxxx
>
> 09/08/2005 11:25 AM
>
> Please respond to
> "For developers on the new Eclipse.org website project."
>
>
>                  
>
> To
>
>                  "For developers on the new Eclipse.org website project."
> <phoenix-dev@xxxxxxxxxxx>
>
> cc
>
>                  
>
> Subject
>
>                  [phoenix-dev] Phoenix Meeting minutes - Sept 2/2005 11:00am
>
>
>                  
>
>
>
>
>
> Phoenix Meeting minutes - Sept 2/2005 11:00am
>
> 1. Phoenix will no longer rely on a Content Management System (CMS)
>
> The CMS' we tried either didn't have the flexibility we think our
> projects require or would have required a serious resource investment in
> customizing them to meet the requirements
>
> The agreed alternative is to use the tools our projects are already
> using for website development: Eclipse and PHP plugins, and CVS.
>
> In order to achieve the Phoenix goals, a series of Cascading Stylesheets
> will be used and PHP templates will be created to aid in migrating
> pages. The PHP tempate will be responsible for setting up common page
> elements, such as a top banner, menubars, navigation sections, all
> without the help of carefully crafted CSS (no html tables or frames).
>
> However, this methodology makes hierarchical navigation difficult to
> achieve (i.e., collapsing, tree-based nav bar, or breadcrumbs)
>
>
> 2. Theme/Template selection
>
> The new Eclipse theme (skin) will be selected Wednesday, at 8:00am
> Eastern by examining the Bugzilla votes for the (currently) three
> templates.  Anyone wishing to create new templates is encouraged to do
> so by following the guidelines at
> http://www.eclipse.org/phoenix/whatsnew/looking_for_templates.html
>
>
> 3. Three action items have been defined as blocking the current progress
> of Phoenix:
>
> - Creation of positional and visual CSS (Denis with web designers)
> - Documentation of Eclipse environment setup for authoring pages (Mike)
> - Documentation of Commit process to connect to CVS, checkin and
> checkout pages (Denis)
>
>
> 4. Tagging
>
> The project members agreed that tagging was an feature worth looking into
>
>
> 5. Denis to open a Bug for stylesheet requirements for projects
>
>
> If I've left something out....
>
>
> --
> Denis Roy
> Manager, IT Infrastructure
> Eclipse Foundation, Inc.
> Office: 613.224.9461 x224
> Cell: 819.210.6481
> denis.roy@xxxxxxxxxxx
>
> _______________________________________________
> phoenix-dev mailing list
> phoenix-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/phoenix-dev
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> phoenix-dev mailing list
> phoenix-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/phoenix-dev

--
Denis Roy
Manager, IT Infrastructure
Eclipse Foundation, Inc.
Office: 613.224.9461 x224
Cell: 819.210.6481
denis.roy@xxxxxxxxxxx
_______________________________________________
phoenix-dev mailing list
phoenix-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/phoenix-dev

Back to the top