Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 87870 - [Intro] Enhance usability of authoring Intro pages
Summary: [Intro] Enhance usability of authoring Intro pages
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M6   Edit
Assignee: Mazen Faraj CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 80139
  Show dependency tree
 
Reported: 2005-03-13 04:15 EST by Mazen Faraj CLA
Modified: 2005-10-03 11:47 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mazen Faraj CLA 2005-03-13 04:15:16 EST 
Enhance usability of authoring Intro pages by supporting XHTML as content to a 
page, in the case of HTML rendering. 
As for the case of UI forms, we need a fallback plan. Maybe we can support 
relying on the custom Intro markup as the fallbacl plan. ie:, a page can 
define both content="pageContent.xhtml" and also have old style custom markup. 
In the HTML case, XHTML content is used. In the UI forms, the old markup.
Comment 1 Mazen Faraj CLA 2005-03-22 23:33:43 EST 
proposal was posted here:

http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-
home/proposals/xhtml/index.htm
Comment 2 Mazen Faraj CLA 2005-03-22 23:42:50 EST 
The fallback mechanism for this new XHTML support is the UI forms support in 
3.0. That is, if you contribute an XHTML page, and intro framework fails to 
instantiate a browser, UI forms presentation is used to render content. In 
that case, content would be what is included in the page using the Intro 
content markup. 

eg:
<page id="page1" content="page1.xhtml" alt-style="swt.properties">
        <title>Welcome to Eclipse 3.1</title>
        <text>Some text that needs to be displayed.</text>
</page> 

in the above example, page1.xhtml will be displayed in the case when an SWT 
Browser can be used, while the title and text elements will be displayed in 
the case of downgrading to Ui forms. swt.properties would control this UI 
forms presentation.
Comment 3 Mazen Faraj CLA 2005-03-28 17:01:15 EST 
code in M6.
Will be double checking/testing design in M7.