forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoff Longman (JIRA)" <>
Subject [jira] Commented: (FOR-162) Add ability to generate Eclipse Help Plug-in compliant sites
Date Mon, 09 Jan 2006 06:36:40 GMT
    [ ] 

Geoff Longman commented on FOR-162:

seeing as forrest itself now has an Eclipse plugin this feature request should carry some
more weight, no?

> Add ability to generate Eclipse Help Plug-in compliant sites
> ------------------------------------------------------------
>          Key: FOR-162
>          URL:
>      Project: Forrest
>         Type: New Feature
>   Components: Plugins (general issues)
>     Versions: 0.6
>  Environment: ALL
>     Reporter: Geoff Longman

> It would be nice to be able to generate a site that can be embedded into an Eclipse help
> The criteria would be as such:
> 1. Generate more compact html. i.e. with less header info. The Eclipse help center is
typically sized small on a user's screen and the less cruft the better. The workaround decribed
in #2 below can get around this with the current way things are generated, but its kludgey.
> 2. Generate html that does not contain the menus as Eclipse uses an xml files called
a toc file to generate its own menus. A current workaround is to generate the site using a
modified the forrest-css skin. The css is modified to hide the menus and compress the header
portion of the page. Although you have to specify a 1px image in skinconf.xml for the mandatory
project logo in order for this to work.
> 3. Generate an Eclipse toc file that is basically a transformation of the site.xml.
> Note - I have been using forrest fo exactly 1 day so buyer beware.
> Reference material:
> A link to a page decribing the format of the Eclipse toc file:
> P.S. I left the priority for this issue at it default setting for no particular reason.
> Geoff

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message