Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 422012

Summary: Update plug-in html
Product: [ECD] Orion Reporter: Curtis Windatt <curtis.windatt.public>
Component: JS ToolsAssignee: Curtis Windatt <curtis.windatt.public>
Status: RESOLVED FIXED QA Contact:
Severity: trivial    
Priority: P3 CC: mamacdon, Michael_Rennie
Version: 5.0   
Target Milestone: 5.0 M1   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Curtis Windatt CLA 2013-11-18 17:15:48 EST 
The plug-in page for JS Tools should always have access to the settings/ide css so we should use it for a consistent look and feel.
Comment 1 Curtis Windatt CLA 2013-11-18 17:18:20 EST 
This also gives me a chance to confirm my gerrit setup is working
https://git.eclipse.org/r/#/c/18530/
Comment 2 Mark Macdonald CLA 2013-11-18 17:19:41 EST 
Plugin pages aren't really meant to be seen by users... they're more like an about.html for an Eclipse plugin.
Comment 3 Curtis Windatt CLA 2013-11-19 10:03:18 EST 
(In reply to Mark Macdonald from comment #2)
> Plugin pages aren't really meant to be seen by users... they're more like an
> about.html for an Eclipse plugin.

You can still access them from the settings page.  The table is gratuitous, but it all looks fine without the css being available too.
Comment 4 Michael Rennie CLA 2013-11-19 10:27:50 EST 
(In reply to Mark Macdonald from comment #2)
> Plugin pages aren't really meant to be seen by users... they're more like an
> about.html for an Eclipse plugin.

Those *are* meant to be seen by users, but are just ignored :)

For what its worth, I like the page having the same LAF as a 'normal' Orion page, its a good place for providers to put some information about the plug-in as well as it being an entry-point for the plug-in.