forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Updated: (FOR-162) Add ability to generate Eclipse Help Plug-in compliant sites
Date Wed, 02 Mar 2005 17:43:43 GMT
The following issue has been updated:

    Updater: Dave Brondsema (mailto:brondsem@apache.org)
       Date: Wed, 2 Mar 2005 11:43 AM
    Changes:
             Component changed to Plugins (general issues)
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-162?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-162

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-162
    Summary: Add ability to generate Eclipse Help Plug-in compliant sites
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Plugins (general issues)
   Versions:
             0.6

   Assignee: 
   Reporter: Geoff Longman

    Created: Fri, 4 Jun 2004 3:18 PM
    Updated: Wed, 2 Mar 2005 11:43 AM
Environment: ALL

Description:
It would be nice to be able to generate a site that can be embedded into an Eclipse help plugin.

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:

http://help.eclipse.org/help21/topic/org.eclipse.platform.doc.isv/guide/help_plugin_toc.htm

P.S. I left the priority for this issue at it default setting for no particular reason.

Geoff


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message