Re: [stp-dev] I've had pretty much enough of Eclipse web site editing :)

[Nick Boldt <nickboldt@xxxxxxxxx>]

Using the Phoenix PHP templates is easy. Just create a nav file 
(_projectCommon.php) and include it in all your pages. Wrap your HTML 
content with a header and footer and bob's your uncle, Phoenix pages.

<?php // header
require_once($_SERVER['DOCUMENT_ROOT'] . 
"/eclipse.org-common/system/app.class.php"); 
require_once($_SERVER['DOCUMENT_ROOT'] . 
"/eclipse.org-common/system/nav.class.php"); 
require_once($_SERVER['DOCUMENT_ROOT'] . 
"/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = 
new Nav(); $Menu = new Menu(); include($App->getProjectCommon());
ob_start(); ?>

<!-- html content here -->

<?php // footer
$html = ob_get_contents();
ob_end_clean();
$App->generatePage("Nova", $Menu, $Nav, "Authors Names", "", "Page 
Title", $html);
?>

Here's a sample _projectCommon.php which defines the nav for the 
Modeling homepage (www.eclipse.org/modeling):

http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/_projectCommon.php?root=Eclipse_Website&content-type=text%2Fplain&view=co

And like that, you have Phoenix-skinned pages. It's so easy, even a Java 
developer could do it. :P

N

Oisin Hurley wrote:
> Doing some more work on this today, I've decided that
> enough is enough. I'm just not going to deal with the
> Eclipse PHP website mess anymore.
>
> I'm looking for some feedback from committers who
> might be interested in going down this route too.
>
> I'm taking a quick look at frameworks like
>
> http://webby.rubyforge.org/
> http://liftweb.net/
>
> as an alternative. Looking for more input on choices.
>
> Don't mention PHP to me!
>
>  --oh
> _______________________________________________
> stp-dev mailing list
> stp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/stp-dev

--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena