Home » Eclipse Projects » Eclipse Platform » how to implement an intro page?
| how to implement an intro page? [message #243397] |
Fri, 21 May 2004 21:29  |
Eclipse User |
|
|
|
I am working on a plugin that extends eclipse.
Here is what I would like to happen.
1. When the plugin is first installed the next start should surface an
introduction.
2. The same content should also be linked to from the
Help/Introduction/Overview.
My plugin.xml contains this:
<extension
point="org.eclipse.ui.intro.configExtension">
<configExtension
configId="org.eclipse.platform.introConfig"
content="overviewExtensionContent.xml"/>
</extension>
I also copied overviewExtensionContent.xml from the PDE. To this end
things work as expected, the contribution shows up after going into
Help/Introduction/Overview however it still invokes a PDE help topic.
From Help/Introduction/Overview I would like to show a page FOO that is
based on HTML but would like to stay in the same window.
I tried getting a first version of that page defined in
overviewExtensionContent.xml but that didn't work. Here is the content
of the file:
<?xml version="1.0" encoding="UTF-8" ?>
<introContent>
<!-- Extension to the SDK Overview Page. -->
<extensionContent
alt-style="css/swt.properties"
style="css/overview.css"
path="overview/page-content/overview-links">
<link
label="XXX guidance"
url="http://org.eclipse.ui.intro/showPage?id=xxx-intro"
id="Foo">
<text>TBD</text>
</link>
<page
style="css/overview.css"
alt-style="css/swt.properties"
title="Getting started with TBD"
id="xxx-intro">
<text>TBD</text>
</page>
</extensionContent>
</introContent>
However eclipse doesn't show a page with TBD when I click on the link.
The same page Foo should be shown to the user after install. How would I
tell eclipse to do this?
Also I am wondering whether there are any tricks that make
authoring/debugging pages in the IntroContentFile XML Format more efficient?
|
|
|
| Re: how to implement an intro page? [message #243859 is a reply to message #243397] |
Sun, 23 May 2004 01:09  |
| Eclipse User |
|
|
|
Originally posted by: xxx.ca.ibm.com
This is a multi-part message in MIME format.
------=_NextPart_000_0010_01C44062.8E31FD70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
you're 99% there. =20
You included the Page element as a child of in your extensionContent =
element. This is not the correct syntax, apologies for lack of =
documentation. (BTW, M9 has the schema for the content of the =
IntroContent xml file.)
All you have to do is make the Page element a sibling, not a child of, =
the extensionContent element, and all works. =20
<introContent>
<extensionContent alt-style=3D"css/swt.properties" =
style=3D"css/overview.css" =
path=3D"overview/page-content/overview-links/pdeAnchor">
<link label=3D"XXX guidance" =
url=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro" id=3D"Foo">
<text>TBD</text>
</link>
</extensionContent>
<page style=3D"css/overview.css" alt-style=3D"css/swt.properties" =
title=3D"Getting started with TBD" id=3D"xxx-intro">
<text>TBD</text>
</page>
</introContent>=20
As fyi, the deign of the introContent xml file is as follows:=20
a.. When used as content for a configuration, all the following can be =
children of introContent: page, group, link, html, title, text, include, =
head, img, and anchor (<-- note this is new in M9. You contribution in =
M9 would be the same, you only have to replace =
path=3D"overview/page-content/overview-links" with =
path=3D"overview/page-content/overview-links/pdeAnchor".
b.. When used as content for a configuration extension, all the above =
elemets are still valid, in there same hierarchy, plus the =
extensionContent element. The reason for this is simplicity. The same =
content file can be used as content to a configuration, and can be =
referenced from a configuration extension. =20
hope this helps..
Mazen...
"news.eclipse.org" <henrich.kraemer@us.ibm.com> wrote in message =
news:c8ma0g$4aq$1@eclipse.org...
> I am working on a plugin that extends eclipse.
> Here is what I would like to happen.
> 1. When the plugin is first installed the next start should surface an =
> introduction.
> 2. The same content should also be linked to from the=20
> Help/Introduction/Overview.
>=20
> My plugin.xml contains this:
> <extension
> point=3D"org.eclipse.ui.intro.configExtension">
> <configExtension
> configId=3D"org.eclipse.platform.introConfig"
> content=3D"overviewExtensionContent.xml"/>
> </extension>
>=20
> I also copied overviewExtensionContent.xml from the PDE. To this end=20
> things work as expected, the contribution shows up after going into=20
> Help/Introduction/Overview however it still invokes a PDE help topic.
>=20
> From Help/Introduction/Overview I would like to show a page FOO that =
is=20
> based on HTML but would like to stay in the same window.
>=20
> I tried getting a first version of that page defined in=20
> overviewExtensionContent.xml but that didn't work. Here is the content =
> of the file:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8" ?>
> <introContent>
>=20
> <!-- Extension to the SDK Overview Page. -->
> <extensionContent
> alt-style=3D"css/swt.properties"
> style=3D"css/overview.css"
> path=3D"overview/page-content/overview-links">
> <link
> label=3D"XXX guidance"
> =
url=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"
> id=3D"Foo">
> <text>TBD</text>
> </link>
> <page
> style=3D"css/overview.css"
> alt-style=3D"css/swt.properties"
> title=3D"Getting started with TBD"
> id=3D"xxx-intro">
> <text>TBD</text>
> </page>
> </extensionContent>
> </introContent>
>=20
> However eclipse doesn't show a page with TBD when I click on the link.
>=20
> The same page Foo should be shown to the user after install. How would =
I=20
> tell eclipse to do this?
>=20
> Also I am wondering whether there are any tricks that make=20
> authoring/debugging pages in the IntroContentFile XML Format more =
efficient?
>
------=_NextPart_000_0010_01C44062.8E31FD70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>you're 99% =
there. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>You included the Page element as a =
child of in your=20
extensionContent element. This is not the correct syntax, apologies for =
lack of=20
documentation. (</FONT><FONT face=3DArial size=3D2>BTW, M9 has the =
schema for=20
the content of the IntroContent xml file.)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>All you have to do is make the Page =
element a=20
sibling, not a child of, the extensionContent element, and all =
works.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
size=3D2><introContent><BR> <STRONG ><extensionContent</STRO=
NG>=20
alt-style=3D"css/swt.properties" style=3D"css/overview.css"=20
path=3D"overview/page-content/overview-links/pdeAnchor"> <BR> &nbs=
p;<link=20
label=3D"XXX guidance" url=3D"</FONT><A=20
href=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"><FONT =
face=3DArial=20
size=3D2>http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro</FONT></A><F=
ONT=20
face=3DArial size=3D2>"=20
id=3D"Foo"><BR> <text>TBD< ;/text> <BR> =
; </link><BR> <STRONG></extensionContent> <BR></STRO=
NG> <STRONG><page</STRONG>=20
style=3D"css/overview.css" alt-style=3D"css/swt.properties" =
title=3D"Getting started=20
with TBD"=20
id=3D"xxx-intro"><BR> <text>TBD</text& ;gt; <BR><STRO=
NG> </page><BR></STRONG></introContent> </FONT></DI=
V>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>As fyi, the deign of =
the introContent xml=20
file is as follows: </FONT></DIV>
<UL>
<LI><FONT face=3DArial size=3D2>When used as content for a =
configuration, all=20
the following can be children of introContent: page, group, link, =
html, title,=20
text, include, head, img, and anchor (<-- note this is new in M9. =
You=20
contribution in M9 would be the same, you only have to =
replace =20
path=3D"overview/page-content/overview-links" with =20
=
path=3D"overview/page-content/overview-links/<STRONG>pdeAnchor </STRONG>".=
</FONT></LI>
<LI><FONT face=3DArial size=3D2>When used as content for a =
configuration=20
extension, all the above elemets are still valid, in there same=20
hierarchy, plus the extensionContent element. The reason for this=20
is simplicity. The same content file can be used as content =
to a=20
configuration, and can be referenced from a configuration extension.=20
</FONT></LI></UL>
<DIV><FONT face=3DArial size=3D2>hope this helps..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mazen...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"news.eclipse.org" <</FONT><A=20
href=3D"mailto:henrich.kraemer@us.ibm.com"><FONT face=3DArial=20
size=3D2>henrich.kraemer@us.ibm.com</FONT></A><FONT face=3DArial =
size=3D2>> wrote=20
in message </FONT><A href=3D"news:c8ma0g$4aq$1@eclipse.org"><FONT =
face=3DArial=20
size=3D2>news:c8ma0g$4aq$1@eclipse.org</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> I am working =
on a plugin=20
that extends eclipse.<BR>> Here is what I would like to =
happen.<BR>> 1.=20
When the plugin is first installed the next start should surface an =
<BR>>=20
introduction.<BR>> 2. The same content should also be linked to from =
the=20
<BR>> Help/Introduction/Overview.<BR>> <BR>> My plugin.xml =
contains=20
this:<BR>> <extension<BR>>=20
=20
point=3D"org.eclipse.ui.intro.configExtension"><BR >>=20
<configExtension<BR>>=20
=
configId=3D"org.eclipse.platform.introConfig"<BR>>=20
=
content=3D"overviewExtensionContent.xml"/><BR>> =
</extension><BR>> <BR>> I also copied =
overviewExtensionContent.xml=20
from the PDE. To this end <BR>> things work as expected, the =
contribution=20
shows up after going into <BR>> Help/Introduction/Overview however it =
still=20
invokes a PDE help topic.<BR>> <BR>> From =
Help/Introduction/Overview=20
I would like to show a page FOO that is <BR>> based on HTML but would =
like to=20
stay in the same window.<BR>> <BR>> I tried getting a first =
version of=20
that page defined in <BR>> overviewExtensionContent.xml but that =
didn't work.=20
Here is the content <BR>> of the file:<BR>> <BR>> <?xml=20
version=3D"1.0" encoding=3D"UTF-8" ?><BR>> =
<introContent><BR>>=20
<BR>> <!-- Extension to the SDK Overview Page. --><BR>>=20
=20
<extensionContent<BR>>=20
&=
nbsp; =20
alt-style=3D"css/swt.properties"<BR>>=20
&=
nbsp; =20
style=3D"css/overview.css"<BR>>=20
&=
nbsp; =20
path=3D"overview/page-content/overview-links"><BR>>=20
=
<link<BR>>=20
&=
nbsp; =20
label=3D"XXX guidance"<BR>>=20
&=
nbsp; =20
url=3D"</FONT><A =
href=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"><FONT=20
face=3DArial=20
size=3D2>http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro</FONT></A><F=
ONT=20
face=3DArial size=3D2>"<BR>>=20
&=
nbsp; =20
id=3D"Foo"><BR>>=20
&=
nbsp; =20
<text>TBD</text><BR>>=20
=
</link><BR>>=20
=
<page<BR>> style=3D"css/overview.css"<BR>>=20
alt-style=3D"css/swt.properties"<BR>> title=3D"Getting started with =
TBD"<BR>>=20
id=3D"xxx-intro"><BR>>=20
=
<text>TBD</text><BR>>=20
=
</page><BR>> =
=20
</extensionContent><BR>> </introContent><BR>> <BR>> =
However=20
eclipse doesn't show a page with TBD when I click on the link.<BR>> =
<BR>>=20
The same page Foo should be shown to the user after install. How would I =
<BR>> tell eclipse to do this?<BR>> <BR>> Also I am wondering =
whether=20
there are any tricks that make <BR>> authoring/debugging pages in the =
IntroContentFile XML Format more efficient?<BR>> =
</FONT></BODY></HTML>
------=_NextPart_000_0010_01C44062.8E31FD70--
|
|
|
| Re: how to implement an intro page? [message #244326 is a reply to message #243859] |
Mon, 24 May 2004 12:16 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------020804070902090200040103
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Thanks that worked.
I am still not sure how to address issue 1.
> 1. When the plugin is first installed the next start should surface an
> introduction.
If I was building a product, I think I know where to start but in the
scenario of workbench extensions I am unsure whether there is a way to
do this?
Mazen Faraj wrote:
> you're 99% there.
> You included the Page element as a child of in your extensionContent
> element. This is not the correct syntax, apologies for lack of
> documentation. (BTW, M9 has the schema for the content of the
> IntroContent xml file.)
> All you have to do is make the Page element a sibling, not a child of,
> the extensionContent element, and all works.
>
> <introContent>
> *<extensionContent* alt-style="css/swt.properties"
> style="css/overview.css"
> path="overview/page-content/overview-links/pdeAnchor">
> <link label="XXX guidance"
> url="http://org.eclipse.ui.intro/showPage?id=xxx-intro" id="Foo">
> <text>TBD</text>
> </link>
> *</extensionContent>
> * *<page* style="css/overview.css" alt-style="css/swt.properties"
> title="Getting started with TBD" id="xxx-intro">
> <text>TBD</text>
> * </page>
> *</introContent>
>
>
> As fyi, the deign of the introContent xml file is as follows:
>
> * When used as content for a configuration, all the following can
> be children of introContent: page, group, link, html, title,
> text, include, head, img, and anchor (<-- note this is new in
> M9. You contribution in M9 would be the same, you only have to
> replace path="overview/page-content/overview-links" with
> path="overview/page-content/overview-links/*pdeAnchor*".
> * When used as content for a configuration extension, all
> the above elemets are still valid, in there same hierarchy, plus
> the extensionContent element. The reason for this is simplicity.
> The same content file can be used as content to a configuration,
> and can be referenced from a configuration extension.
>
> hope this helps..
> Mazen...
>
>
>
>
> "news.eclipse.org" <henrich.kraemer@us.ibm.com
> <mailto:henrich.kraemer@us.ibm.com>> wrote in message
> news:c8ma0g$4aq$1@eclipse.org...
> > I am working on a plugin that extends eclipse.
> > Here is what I would like to happen.
> > 1. When the plugin is first installed the next start should surface an
> > introduction.
> > 2. The same content should also be linked to from the
> > Help/Introduction/Overview.
> >
> > My plugin.xml contains this:
> > <extension
> > point="org.eclipse.ui.intro.configExtension">
> > <configExtension
> > configId="org.eclipse.platform.introConfig"
> > content="overviewExtensionContent.xml"/>
> > </extension>
> >
> > I also copied overviewExtensionContent.xml from the PDE. To this end
> > things work as expected, the contribution shows up after going into
> > Help/Introduction/Overview however it still invokes a PDE help topic.
> >
> > From Help/Introduction/Overview I would like to show a page FOO
> that is
> > based on HTML but would like to stay in the same window.
> >
> > I tried getting a first version of that page defined in
> > overviewExtensionContent.xml but that didn't work. Here is the content
> > of the file:
> >
> > <?xml version="1.0" encoding="UTF-8" ?>
> > <introContent>
> >
> > <!-- Extension to the SDK Overview Page. -->
> > <extensionContent
> > alt-style="css/swt.properties"
> > style="css/overview.css"
> > path="overview/page-content/overview-links">
> > <link
> > label="XXX guidance"
> >
> url="http://org.eclipse.ui.intro/showPage?id=xxx-intro"
> > id="Foo">
> > <text>TBD</text>
> > </link>
> > <page
> > style="css/overview.css"
> > alt-style="css/swt.properties"
> > title="Getting started with TBD"
> > id="xxx-intro">
> > <text>TBD</text>
> > </page>
> > </extensionContent>
> > </introContent>
> >
> > However eclipse doesn't show a page with TBD when I click on the link.
> >
> > The same page Foo should be shown to the user after install. How
> would I
> > tell eclipse to do this?
> >
> > Also I am wondering whether there are any tricks that make
> > authoring/debugging pages in the IntroContentFile XML Format more
> efficient?
> >
--------------020804070902090200040103
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks that worked. <br>
I am still not sure how to address issue 1. <br>
<font face="Arial" size="2">> 1. When the plugin is first installed
the next start should surface an <br>
> introduction.<br>
<br>
</font>If I was building a product, I think I know where to start but
in the scenario of workbench extensions I am unsure whether there is a
way to do this?<br>
<br>
Mazen Faraj wrote:
<blockquote cite="midc8pbh3$vig$1@eclipse.org" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2800.1400" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">you're 99% there. </font></div>
<div><font face="Arial" size="2">You included the Page element as a
child of in your extensionContent element. This is not the correct
syntax, apologies for lack of documentation. (</font><font face="Arial"
size="2">BTW, M9 has the schema for the content of the IntroContent
xml file.)</font></div>
<div><font face="Arial" size="2">All you have to do is make the Page
element a sibling, not a child of, the extensionContent element,
and all works. </font></div>
<div> </div>
<div><font face="Arial" size="2"><introContent><br>
<strong><extensionContent</strong> alt-style="css/swt.properties"
style="css/overview.css"
path="overview/page-content/overview-links/pdeAnchor"> <br>
<link label="XXX guidance" url="</font><a
href="http://org.eclipse.ui.intro/showPage?id=xxx-intro"><font
face="Arial" size="2">http://org.eclipse.ui.intro/showPage?id=xxx-intro</font></a><font
face="Arial" size="2">" id="Foo"><br>
<text>TBD< ;/text> <br>
</link><br>
<strong></extensionContent><br>
</strong> <strong><page</strong> style="css/overview.css"
alt-style="css/swt.properties" title="Getting started with TBD"
id="xxx-intro"><br>
<text>TBD</text& ;gt; <br>
<strong> </page><br>
</strong></introContent> </font></div >
<div> </div>
<div> </div>
<div><font face="Arial" size="2">As fyi, the deign of
the introContent xml file is as follows: </font></div>
<ul>
<li><font face="Arial" size="2">When used as content for a
configuration, all the following can be children of introContent: page,
group, link, html, title, text, include, head, img, and anchor (<--
note this is new in M9. You contribution in M9 would be the same, you
only have to replace path="overview/page-content/overview-links" with
path="overview/page-content/overview-links/<strong>pdeAnchor </strong>".</font></li>
<li><font face="Arial" size="2">When used as content for a
configuration extension, all the above elemets are still valid, in
there same hierarchy, plus the extensionContent element. The reason for
this is simplicity. The same content file can be used as content to a
configuration, and can be referenced from a configuration extension. </font></li>
</ul>
<div><font face="Arial" size="2">hope this helps..</font></div>
<div><font face="Arial" size="2">Mazen...</font></div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div><font face="Arial" size="2">"news.eclipse.org" <</font><a
href="mailto:henrich.kraemer@us.ibm.com"><font face="Arial" size="2">henrich.kraemer@us.ibm.com</font></a><font
face="Arial" size="2">> wrote in message </font><a
href="news:c8ma0g$4aq$1@eclipse.org"><font face="Arial" size="2">news:c8ma0g$4aq$1@eclipse.org</font></a><font
face="Arial" size="2">...</font></div>
<font face="Arial" size="2">> I am working on a plugin that
extends eclipse.<br>
> Here is what I would like to happen.<br>
> 1. When the plugin is first installed the next start should
surface an <br>
> introduction.<br>
> 2. The same content should also be linked to from the <br>
> Help/Introduction/Overview.<br>
> <br>
> My plugin.xml contains this:<br>
> <extension<br>
> point="org.eclipse.ui.intro.configExtension"><br>
> <configExtension<br>
> configId="org.eclipse.platform.introConfig"<br>
> content="overviewExtensionContent.xml"/><br>
> </extension><br>
> <br>
> I also copied overviewExtensionContent.xml from the PDE. To this
end <br>
> things work as expected, the contribution shows up after going
into <br>
> Help/Introduction/Overview however it still invokes a PDE help
topic.<br>
> <br>
> From Help/Introduction/Overview I would like to show a page FOO
that is <br>
> based on HTML but would like to stay in the same window.<br>
> <br>
> I tried getting a first version of that page defined in <br>
> overviewExtensionContent.xml but that didn't work. Here is the
content <br>
> of the file:<br>
> <br>
> <?xml version="1.0" encoding="UTF-8" ?><br>
> <introContent><br>
> <br>
> <!-- Extension to the SDK Overview Page. --><br>
> <extensionContent<br>
> alt-style="css/swt.properties"<br>
> style="css/overview.css"<br>
> path="overview/page-content/overview-links"><br>
> <link<br>
> label="XXX guidance"<br>
> url="</font><a
href="http://org.eclipse.ui.intro/showPage?id=xxx-intro"><font
face="Arial" size="2">http://org.eclipse.ui.intro/showPage?id=xxx-intro</font></a><font
face="Arial" size="2">"<br>
> id="Foo"><br>
> <text>TBD</text><br>
> </link><br>
> <page<br>
> style="css/overview.css"<br>
> alt-style="css/swt.properties"<br>
> title="Getting started with TBD"<br>
> id="xxx-intro"><br>
> <text>TBD</text><br>
> </page><br>
> </extensionContent><br>
> </introContent><br>
> <br>
> However eclipse doesn't show a page with TBD when I click on the
link.<br>
> <br>
> The same page Foo should be shown to the user after install. How
would I <br>
> tell eclipse to do this?<br>
> <br>
> Also I am wondering whether there are any tricks that make <br>
> authoring/debugging pages in the IntroContentFile XML Format more
efficient?<br>
> </font></blockquote>
<br>
</body>
</html>
--------------020804070902090200040103--
|
|
|
| Re: how to implement an intro page? [message #244860 is a reply to message #244326] |
Tue, 25 May 2004 10:36 |
| Eclipse User |
|
|
|
Originally posted by: xxx.ca.ibm.com
This is a multi-part message in MIME format.
------=_NextPart_000_0014_01C44244.310691E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
If I understand u correctly, u want a user to install your plugin, and =
then on a restart u want Intro to be shown.=20
U cant accomplish this, and its by design. U can certainly open feature =
request if u strongly see a need.
Here is the reason: Intro has a life cycle, dictated by the user. On =
clean install (never ran workbench before), u will always get intro. =
Then state is remembered. U close with intro, you open with intro. In =
your case, you dont know what state your user left his workbench in and =
u cant change it. In fact, with the new OSGI support, there may not be a =
need for a restart, a plugin is doewnloaded and installed live, so why =
would u want to shock your users with a maximazed intro?=20
In your plugin documentation u can mention that if installing your =
plugin on a used workspace, open Welcome to see intro for your =
component.=20
hope this helps...
Mazen. =20
"news.eclipse.org" <henrich.kraemer@us.ibm.com> wrote in message =
news:c8t6mb$ruv$1@eclipse.org...
Thanks that worked.=20
I am still not sure how to address issue 1.=20
> 1. When the plugin is first installed the next start should surface =
an=20
> introduction.
If I was building a product, I think I know where to start but in the =
scenario of workbench extensions I am unsure whether there is a way to =
do this?
Mazen Faraj wrote:=20
you're 99% there. =20
You included the Page element as a child of in your extensionContent =
element. This is not the correct syntax, apologies for lack of =
documentation. (BTW, M9 has the schema for the content of the =
IntroContent xml file.)
All you have to do is make the Page element a sibling, not a child =
of, the extensionContent element, and all works. =20
<introContent>
<extensionContent alt-style=3D"css/swt.properties" =
style=3D"css/overview.css" =
path=3D"overview/page-content/overview-links/pdeAnchor">
<link label=3D"XXX guidance" =
url=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro" id=3D"Foo">
<text>TBD</text>
</link>
</extensionContent>
<page style=3D"css/overview.css" alt-style=3D"css/swt.properties" =
title=3D"Getting started with TBD" id=3D"xxx-intro">
<text>TBD</text>
</page>
</introContent>=20
As fyi, the deign of the introContent xml file is as follows:=20
a.. When used as content for a configuration, all the following =
can be children of introContent: page, group, link, html, title, text, =
include, head, img, and anchor (<-- note this is new in M9. You =
contribution in M9 would be the same, you only have to replace =
path=3D"overview/page-content/overview-links" with =
path=3D"overview/page-content/overview-links/pdeAnchor".=20
b.. When used as content for a configuration extension, all the =
above elemets are still valid, in there same hierarchy, plus the =
extensionContent element. The reason for this is simplicity. The same =
content file can be used as content to a configuration, and can be =
referenced from a configuration extension. =20
hope this helps..
Mazen...
"news.eclipse.org" <henrich.kraemer@us.ibm.com> wrote in message =
news:c8ma0g$4aq$1@eclipse.org...
> I am working on a plugin that extends eclipse.
> Here is what I would like to happen.
> 1. When the plugin is first installed the next start should =
surface an=20
> introduction.
> 2. The same content should also be linked to from the=20
> Help/Introduction/Overview.
>=20
> My plugin.xml contains this:
> <extension
> point=3D"org.eclipse.ui.intro.configExtension">
> <configExtension
> configId=3D"org.eclipse.platform.introConfig"
> content=3D"overviewExtensionContent.xml"/>
> </extension>
>=20
> I also copied overviewExtensionContent.xml from the PDE. To this =
end=20
> things work as expected, the contribution shows up after going =
into=20
> Help/Introduction/Overview however it still invokes a PDE help =
topic.
>=20
> From Help/Introduction/Overview I would like to show a page FOO =
that is=20
> based on HTML but would like to stay in the same window.
>=20
> I tried getting a first version of that page defined in=20
> overviewExtensionContent.xml but that didn't work. Here is the =
content=20
> of the file:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8" ?>
> <introContent>
>=20
> <!-- Extension to the SDK Overview Page. -->
> <extensionContent
> alt-style=3D"css/swt.properties"
> style=3D"css/overview.css"
> path=3D"overview/page-content/overview-links">
> <link
> label=3D"XXX guidance"
> =
url=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"
> id=3D"Foo">
> <text>TBD</text>
> </link>
> <page
> style=3D"css/overview.css"
> alt-style=3D"css/swt.properties"
> title=3D"Getting started with TBD"
> id=3D"xxx-intro">
> <text>TBD</text>
> </page>
> </extensionContent>
> </introContent>
>=20
> However eclipse doesn't show a page with TBD when I click on the =
link.
>=20
> The same page Foo should be shown to the user after install. How =
would I=20
> tell eclipse to do this?
>=20
> Also I am wondering whether there are any tricks that make=20
> authoring/debugging pages in the IntroContentFile XML Format more =
efficient?
>=20
------=_NextPart_000_0014_01C44244.310691E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>If I understand u correctly, u want a =
user to=20
install your plugin, and then on a restart u want Intro to be shown.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>U cant accomplish this, and its by =
design. U can=20
certainly open feature request if u strongly see a need.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Here is the reason: Intro has a life =
cycle,=20
dictated by the user. On clean install (never ran workbench before), u =
will=20
always get intro. Then state is remembered. U close with intro, you =
open=20
with intro. In your case, you dont know what state your =
user left=20
his workbench in and u cant change it. In fact, with the new OSGI=20
support, there may not be a need for a restart, a plugin =
is=20
doewnloaded and installed live, so why would u want to shock your =
users=20
with a maximazed intro? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>In your plugin documentation u =
can mention=20
that if installing your plugin on a used workspace, open Welcome to see =
intro=20
for your component. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>hope this helps...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mazen.</FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"news.eclipse.org" <<A=20
=
href=3D"mailto:henrich.kraemer@us.ibm.com">henrich.kraemer@us.ibm.com</A>=
>=20
wrote in message <A=20
=
href=3D"news:c8t6mb$ruv$1@eclipse.org">news:c8t6mb$ruv$1@eclipse.org</A>.=
...</DIV>Thanks=20
that worked. <BR>I am still not sure how to address issue 1. <BR><FONT =
face=3DArial size=3D2>> 1. When the plugin is first installed the =
next start=20
should surface an <BR>> introduction.<BR><BR></FONT>If I was =
building a=20
product, I think I know where to start but in the scenario of =
workbench=20
extensions I am unsure whether there is a way to do this?<BR><BR>Mazen =
Faraj=20
wrote:=20
<BLOCKQUOTE cite=3Dmidc8pbh3$vig$1@eclipse.org type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
<DIV><FONT face=3DArial size=3D2>you're 99% =
there. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>You included the Page element as a =
child of in=20
your extensionContent element. This is not the correct syntax, =
apologies for=20
lack of documentation. (</FONT><FONT face=3DArial size=3D2>BTW, =
M9 has the=20
schema for the content of the IntroContent xml file.)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>All you have to do is make the Page =
element a=20
sibling, not a child of, the extensionContent element, and all =
works.=20
</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial=20
=
size=3D2><introContent><BR> <STRONG ><extensionContent</STRO=
NG>=20
alt-style=3D"css/swt.properties" style=3D"css/overview.css"=20
=
path=3D"overview/page-content/overview-links/pdeAnchor"> <BR> &nbs=
p;<link=20
label=3D"XXX guidance" url=3D"</FONT><A=20
href=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"><FONT =
face=3DArial=20
=
size=3D2>http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro</FONT></A><F=
ONT=20
face=3DArial size=3D2>"=20
=
id=3D"Foo"><BR> <text>TBD< ;/text> <BR> =
; </link><BR> <STRONG></extensionContent> <BR></STRO=
NG> <STRONG><page</STRONG>=20
style=3D"css/overview.css" alt-style=3D"css/swt.properties" =
title=3D"Getting=20
started with TBD"=20
=
id=3D"xxx-intro"><BR> <text>TBD</text& ;gt; <BR><STRO=
NG> </page><BR></STRONG></introContent> </FONT></DI=
V>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>As fyi, the deign of=20
the introContent xml file is as follows: =
</FONT></DIV>
<UL>
<LI><FONT face=3DArial size=3D2>When used as content for a =
configuration,=20
all the following can be children of introContent: page, group, =
link,=20
html, title, text, include, head, img, and anchor (<-- note =
this is new=20
in M9. You contribution in M9 would be the same, you =
only have=20
to replace path=3D"overview/page-content/overview-links" =
with =20
=
path=3D"overview/page-content/overview-links/<STRONG>pdeAnchor </STRONG>".=
</FONT>=20
<LI><FONT face=3DArial size=3D2>When used as content for a =
configuration=20
extension, all the above elemets are still valid, in there =
same=20
hierarchy, plus the extensionContent element. The reason for this=20
is simplicity. The same content file can be used as content =
to a=20
configuration, and can be referenced from a configuration =
extension.=20
</FONT> </LI></UL>
<DIV><FONT face=3DArial size=3D2>hope this helps..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mazen...</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>"news.eclipse.org" <</FONT><A=20
href=3D"mailto:henrich.kraemer@us.ibm.com"><FONT face=3DArial=20
size=3D2>henrich.kraemer@us.ibm.com</FONT></A><FONT face=3DArial =
size=3D2>>=20
wrote in message </FONT><A =
href=3D"news:c8ma0g$4aq$1@eclipse.org"><FONT=20
face=3DArial size=3D2>news:c8ma0g$4aq$1@eclipse.org</FONT></A><FONT =
face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> I am =
working on a plugin=20
that extends eclipse.<BR>> Here is what I would like to =
happen.<BR>>=20
1. When the plugin is first installed the next start should surface =
an=20
<BR>> introduction.<BR>> 2. The same content should also be =
linked to=20
from the <BR>> Help/Introduction/Overview.<BR>> <BR>> My =
plugin.xml=20
contains this:<BR>> <extension<BR>>=20
=20
point=3D"org.eclipse.ui.intro.configExtension"><BR >>=20
<configExtension<BR>>=20
=
=
configId=3D"org.eclipse.platform.introConfig"<BR>>=20
=
=
content=3D"overviewExtensionContent.xml"/><BR>> =
=20
</extension><BR>> <BR>> I also copied=20
overviewExtensionContent.xml from the PDE. To this end <BR>> =
things work=20
as expected, the contribution shows up after going into <BR>>=20
Help/Introduction/Overview however it still invokes a PDE help=20
topic.<BR>> <BR>> From Help/Introduction/Overview I =
would like=20
to show a page FOO that is <BR>> based on HTML but would like to =
stay in=20
the same window.<BR>> <BR>> I tried getting a first version of =
that=20
page defined in <BR>> overviewExtensionContent.xml but that =
didn't work.=20
Here is the content <BR>> of the file:<BR>> <BR>> <?xml=20
version=3D"1.0" encoding=3D"UTF-8" ?><BR>> =
<introContent><BR>>=20
<BR>> <!-- Extension to the SDK Overview Page. --><BR>>=20
=20
<extensionContent<BR>>=20
=
&=
nbsp; =20
alt-style=3D"css/swt.properties"<BR>>=20
=
&=
nbsp; =20
style=3D"css/overview.css"<BR>>=20
=
&=
nbsp; =20
path=3D"overview/page-content/overview-links"><BR>>=20
=
=
<link<BR>>=20
=
&=
nbsp; =20
label=3D"XXX guidance"<BR>>=20
=
&=
nbsp; =20
url=3D"</FONT><A=20
href=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"><FONT =
face=3DArial=20
=
size=3D2>http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro</FONT></A><F=
ONT=20
face=3DArial size=3D2>"<BR>>=20
=
&=
nbsp; =20
id=3D"Foo"><BR>>=20
=
&=
nbsp; =20
<text>TBD</text><BR>>=20
=
=
</link><BR>>=20
=
=
<page<BR>> style=3D"css/overview.css"<BR>>=20
alt-style=3D"css/swt.properties"<BR>> title=3D"Getting started =
with=20
TBD"<BR>> id=3D"xxx-intro"><BR>>=20
=
=
<text>TBD</text><BR>>=20
=
=
</page><BR>> =
=20
</extensionContent><BR>> </introContent><BR>> =
<BR>>=20
However eclipse doesn't show a page with TBD when I click on the=20
link.<BR>> <BR>> The same page Foo should be shown to the user =
after=20
install. How would I <BR>> tell eclipse to do this?<BR>> =
<BR>> Also=20
I am wondering whether there are any tricks that make <BR>>=20
authoring/debugging pages in the IntroContentFile XML Format more=20
efficient?<BR>> =
</FONT></BLOCKQUOTE><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0014_01C44244.310691E0--
|
|
|
| Re: how to implement an intro page? [message #245130 is a reply to message #244860] |
Tue, 25 May 2004 14:28 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------080300040809020306060207
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
If I understand correctly there is exactly one (or none) Intro per
product. A plugin can contribute content to this intro using the
ui.intro framework, which is very cool!
Some welcome information should also be shown to the user whenever the
plugin is activated or first installed. Ideally the welcome information
is not shown if the user already gets the product-intro with the
extension. For example if the plugin was installed prior to the first
startup of eclipse.
In my mind it would be natural if the plugin-welcome information and the
plugin-intro information is the same. This is why I was wondering
whether I can do this via the ui.intro framework.
Ignoring the desire to have the content in the exactly same format it
seems that the welcome page gives me the behavior I am looking for.
Is the intent that ui.intro replaces or supersedes the welcomePage
mechanism? If this is the case I would open a feature request.
Otherwise it seems the way to go is to use both ui.intro to the
welcomePage mechanism
Mazen Faraj wrote:
> If I understand u correctly, u want a user to install your plugin, and
> then on a restart u want Intro to be shown.
> U cant accomplish this, and its by design. U can certainly open
> feature request if u strongly see a need.
> Here is the reason: Intro has a life cycle, dictated by the user. On
> clean install (never ran workbench before), u will always get intro.
> Then state is remembered. U close with intro, you open with intro.
> In your case, you dont know what state your user left his workbench in
> and u cant change it. In fact, with the new OSGI support, there may
> not be a need for a restart, a plugin is doewnloaded and installed
> live, so why would u want to shock your users with a maximazed intro?
>
> In your plugin documentation u can mention that if installing your
> plugin on a used workspace, open Welcome to see intro for your component.
>
> hope this helps...
> Mazen.
>
>
>
>
>
> "news.eclipse.org" <henrich.kraemer@us.ibm.com
> <mailto:henrich.kraemer@us.ibm.com>> wrote in message
> news:c8t6mb$ruv$1@eclipse.org...
> Thanks that worked.
> I am still not sure how to address issue 1.
> > 1. When the plugin is first installed the next start should
> surface an
> > introduction.
>
> If I was building a product, I think I know where to start but in
> the scenario of workbench extensions I am unsure whether there is
> a way to do this?
>
> Mazen Faraj wrote:
>
>> you're 99% there.
>> You included the Page element as a child of in your
>> extensionContent element. This is not the correct syntax,
>> apologies for lack of documentation. (BTW, M9 has the schema for
>> the content of the IntroContent xml file.)
>> All you have to do is make the Page element a sibling, not a
>> child of, the extensionContent element, and all works.
>>
>> <introContent>
>> *<extensionContent* alt-style="css/swt.properties"
>> style="css/overview.css"
>> path="overview/page-content/overview-links/pdeAnchor">
>> <link label="XXX guidance"
>> url="http://org.eclipse.ui.intro/showPage?id=xxx-intro" id="Foo">
>> <text>TBD</text>
>> </link>
>> *</extensionContent>
>> * *<page* style="css/overview.css" alt-style="css/swt.properties"
>> title="Getting started with TBD" id="xxx-intro">
>> <text>TBD</text>
>> * </page>
>> *</introContent>
>>
>>
>> As fyi, the deign of the introContent xml file is as follows:
>>
>> * When used as content for a configuration, all the following
>> can be children of introContent: page, group, link, html,
>> title, text, include, head, img, and anchor (<-- note this
>> is new in M9. You contribution in M9 would be the same, you
>> only have to replace
>> path="overview/page-content/overview-links" with
>> path="overview/page-content/overview-links/*pdeAnchor*".
>> * When used as content for a configuration extension, all
>> the above elemets are still valid, in there same hierarchy,
>> plus the extensionContent element. The reason for this
>> is simplicity. The same content file can be used as content
>> to a configuration, and can be referenced from a
>> configuration extension.
>>
>> hope this helps..
>> Mazen...
>>
>>
>>
>>
>> "news.eclipse.org" <henrich.kraemer@us.ibm.com
>> <mailto:henrich.kraemer@us.ibm.com>> wrote in message
>> news:c8ma0g$4aq$1@eclipse.org...
>> > I am working on a plugin that extends eclipse.
>> > Here is what I would like to happen.
>> > 1. When the plugin is first installed the next start should
>> surface an
>> > introduction.
>> > 2. The same content should also be linked to from the
>> > Help/Introduction/Overview.
>> >
>> > My plugin.xml contains this:
>> > <extension
>> > point="org.eclipse.ui.intro.configExtension">
>> > <configExtension
>> > configId="org.eclipse.platform.introConfig"
>> > content="overviewExtensionContent.xml"/>
>> > </extension>
>> >
>> > I also copied overviewExtensionContent.xml from the PDE. To
>> this end
>> > things work as expected, the contribution shows up after going
>> into
>> > Help/Introduction/Overview however it still invokes a PDE help
>> topic.
>> >
>> > From Help/Introduction/Overview I would like to show a page
>> FOO that is
>> > based on HTML but would like to stay in the same window.
>> >
>> > I tried getting a first version of that page defined in
>> > overviewExtensionContent.xml but that didn't work. Here is the
>> content
>> > of the file:
>> >
>> > <?xml version="1.0" encoding="UTF-8" ?>
>> > <introContent>
>> >
>> > <!-- Extension to the SDK Overview Page. -->
>> > <extensionContent
>> > alt-style="css/swt.properties"
>> > style="css/overview.css"
>> > path="overview/page-content/overview-links">
>> > <link
>> > label="XXX guidance"
>> >
>> url="http://org.eclipse.ui.intro/showPage?id=xxx-intro"
>> > id="Foo">
>> > <text>TBD</text>
>> > </link>
>> > <page
>> > style="css/overview.css"
>> > alt-style="css/swt.properties"
>> > title="Getting started with TBD"
>> > id="xxx-intro">
>> > <text>TBD</text>
>> > </page>
>> > </extensionContent>
>> > </introContent>
>> >
>> > However eclipse doesn't show a page with TBD when I click on
>> the link.
>> >
>> > The same page Foo should be shown to the user after install.
>> How would I
>> > tell eclipse to do this?
>> >
>> > Also I am wondering whether there are any tricks that make
>> > authoring/debugging pages in the IntroContentFile XML Format
>> more efficient?
>> >
>
>
--------------080300040809020306060207
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
If I understand correctly there is exactly one (or none) Intro per
product. A plugin can contribute content to this intro using the
ui.intro framework, which is very cool!<br>
<br>
Some welcome information should also be shown to the user whenever the
plugin is activated or first installed. Ideally the welcome information
is not shown if the user already gets the product-intro with the
extension. For example if the plugin was installed prior to the first
startup of eclipse.<br>
In my mind it would be natural if the plugin-welcome information and
the plugin-intro information is the same. This is why I was wondering
whether I can do this via the ui.intro framework.<br>
<br>
Ignoring the desire to have the content in the exactly same format it
seems that the welcome page gives me the behavior I am looking for. <br>
<br>
Is the intent that ui.intro replaces or supersedes the welcomePage
mechanism? If this is the case I would open a feature request.<br>
Otherwise it seems the way to go is to use both ui.intro to the
welcomePage mechanism<br>
<br>
<br>
Mazen Faraj wrote:<br>
<blockquote cite="midc8vl83$gpo$1@eclipse.org" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2800.1400" name="GENERATOR">
<div><font face="Arial" size="2">If I understand u correctly, u want
a user to install your plugin, and then on a restart u want Intro to be
shown. </font></div>
<div><font face="Arial" size="2">U cant accomplish this, and its by
design. U can certainly open feature request if u strongly see a need.</font></div>
<div><font face="Arial" size="2">Here is the reason: Intro has a life
cycle, dictated by the user. On clean install (never ran workbench
before), u will always get intro. Then state is remembered. U close
with intro, you open with intro. In your case, you dont know what
state your user left his workbench in and u cant change it. In fact,
with the new OSGI support, there may not be a need for a restart, a
plugin is doewnloaded and installed live, so why would u want to shock
your users with a maximazed intro? </font></div>
<div> </div>
<div><font face="Arial" size="2">In your plugin documentation u
can mention that if installing your plugin on a used workspace, open
Welcome to see intro for your component. </font></div>
<div> </div>
<div><font face="Arial" size="2">hope this helps...</font></div>
<div><font face="Arial" size="2">Mazen.</font> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div>"news.eclipse.org" <<a
href="mailto:henrich.kraemer@us.ibm.com">henrich.kraemer@us.ibm.com</a>>
wrote in message <a href="news:c8t6mb$ruv$1@eclipse.org">news:c8t6mb$ruv$1@eclipse.org</a>...</div>
Thanks that worked. <br>
I am still not sure how to address issue 1. <br>
<font face="Arial" size="2">> 1. When the plugin is first
installed the next start should surface an <br>
> introduction.<br>
<br>
</font>If I was building a product, I think I know where to start
but in the scenario of workbench extensions I am unsure whether there
is a way to do this?<br>
<br>
Mazen Faraj wrote:
<blockquote cite="midc8pbh3$vig$1@eclipse.org" type="cite">
<meta content="MSHTML 6.00.2800.1400" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">you're 99% there. </font></div>
<div><font face="Arial" size="2">You included the Page element as
a child of in your extensionContent element. This is not the correct
syntax, apologies for lack of documentation. (</font><font face="Arial"
size="2">BTW, M9 has the schema for the content of the IntroContent
xml file.)</font></div>
<div><font face="Arial" size="2">All you have to do is make the
Page element a sibling, not a child of, the extensionContent element,
and all works. </font></div>
<div> </div>
<div><font face="Arial" size="2"><introContent><br>
<strong><extensionContent</strong> alt-style="css/swt.properties"
style="css/overview.css"
path="overview/page-content/overview-links/pdeAnchor"> <br>
<link label="XXX guidance" url="</font><a
href="http://org.eclipse.ui.intro/showPage?id=xxx-intro"><font
face="Arial" size="2">http://org.eclipse.ui.intro/showPage?id=xxx-intro</font></a><font
face="Arial" size="2">" id="Foo"><br>
<text>TBD< ;/text> <br>
</link><br>
<strong></extensionContent><br>
</strong> <strong><page</strong> style="css/overview.css"
alt-style="css/swt.properties" title="Getting started with TBD"
id="xxx-intro"><br>
<text>TBD</text& ;gt; <br>
<strong> </page><br>
</strong></introContent> </font></div >
<div> </div>
<div> </div>
<div><font face="Arial" size="2">As fyi, the deign of
the introContent xml file is as follows: </font></div>
<ul>
<li><font face="Arial" size="2">When used as content for a
configuration, all the following can be children of introContent: page,
group, link, html, title, text, include, head, img, and anchor (<--
note this is new in M9. You contribution in M9 would be the same, you
only have to replace path="overview/page-content/overview-links" with
path="overview/page-content/overview-links/<strong>pdeAnchor </strong>".</font>
</li>
<li><font face="Arial" size="2">When used as content for a
configuration extension, all the above elemets are still valid, in
there same hierarchy, plus the extensionContent element. The reason for
this is simplicity. The same content file can be used as content to a
configuration, and can be referenced from a configuration extension. </font>
</li>
</ul>
<div><font face="Arial" size="2">hope this helps..</font></div>
<div><font face="Arial" size="2">Mazen...</font></div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div><font face="Arial" size="2">"news.eclipse.org" <</font><a
href="mailto:henrich.kraemer@us.ibm.com"><font face="Arial" size="2">henrich.kraemer@us.ibm.com</font></a><font
face="Arial" size="2">> wrote in message </font><a
href="news:c8ma0g$4aq$1@eclipse.org"><font face="Arial" size="2">news:c8ma0g$4aq$1@eclipse.org</font></a><font
face="Arial" size="2">...</font></div>
<font face="Arial" size="2">> I am working on a plugin that
extends eclipse.<br>
> Here is what I would like to happen.<br>
> 1. When the plugin is first installed the next start should
surface an <br>
> introduction.<br>
> 2. The same content should also be linked to from the <br>
> Help/Introduction/Overview.<br>
> <br>
> My plugin.xml contains this:<br>
> <extension<br>
> point="org.eclipse.ui.intro.configExtension"><br>
> <configExtension<br>
> configId="org.eclipse.platform.introConfig"<br>
> content="overviewExtensionContent.xml"/><br>
> </extension><br>
> <br>
> I also copied overviewExtensionContent.xml from the PDE. To this
end <br>
> things work as expected, the contribution shows up after going
into <br>
> Help/Introduction/Overview however it still invokes a PDE help
topic.<br>
> <br>
> From Help/Introduction/Overview I would like to show a page FOO
that is <br>
> based on HTML but would like to stay in the same window.<br>
> <br>
> I tried getting a first version of that page defined in <br>
> overviewExtensionContent.xml but that didn't work. Here is the
content <br>
> of the file:<br>
> <br>
> <?xml version="1.0" encoding="UTF-8" ?><br>
> <introContent><br>
> <br>
> <!-- Extension to the SDK Overview Page. --><br>
> <extensionContent<br>
> alt-style="css/swt.properties"<br>
> style="css/overview.css"<br>
> path="overview/page-content/overview-links"><br>
> <link<br>
> label="XXX guidance"<br>
> url="</font><a
href="http://org.eclipse.ui.intro/showPage?id=xxx-intro"><font
face="Arial" size="2">http://org.eclipse.ui.intro/showPage?id=xxx-intro</font></a><font
face="Arial" size="2">"<br>
> id="Foo"><br>
> <text>TBD</text><br>
> </link><br>
> <page<br>
> style="css/overview.css"<br>
> alt-style="css/swt.properties"<br>
> title="Getting started with TBD"<br>
> id="xxx-intro"><br>
> <text>TBD</text><br>
> </page><br>
> </extensionContent><br>
> </introContent><br>
> <br>
> However eclipse doesn't show a page with TBD when I click on the
link.<br>
> <br>
> The same page Foo should be shown to the user after install. How
would I <br>
> tell eclipse to do this?<br>
> <br>
> Also I am wondering whether there are any tricks that make <br>
> authoring/debugging pages in the IntroContentFile XML Format more
efficient?<br>
> </font></blockquote>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>
--------------080300040809020306060207--
|
|
|
| Re: how to implement an intro page? [message #245696 is a reply to message #245130] |
Wed, 26 May 2004 11:55 |
| Eclipse User |
|
|
|
Originally posted by: xxx.ca.ibm.com
This is a multi-part message in MIME format.
------=_NextPart_000_002B_01C44318.6932CEB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The legacy welcome behaved the same way as how the Intro behaves today. =
With one twist that I will point out.
The Welcome of the primary feature used to be shown to the user. An =
eclipse install could have more than one feature tagged as the primary =
feature, but only one will be honored and the welcome of that one =
primary feature was shown. Now here is the twist. Other welcomes could =
be launched also through the menus.
With the new Intro (now renamed to Welcome btw) its the same story. =
There could be more than one product defined in a given eclipse install, =
and each of these products could have an intro properly bound to it, but =
only one product would be honrored on startup, and the intro of that =
product will be shown. If that product does not have an intro, the old =
welcome of that product is shown, if it was defined. Now other intros =
can not be shown. and if an intro is shown, then all legacy welcome is =
hidden.=20
I believe there is a feature request already open to enable showing =
other intros through a menu, just like the old welcome.=20
if Im not wrong, the behavior that u are descriing could not be =
accomplished, even with the old welcome. The behavior is installing a =
plugin on an existing workspace and having the old welcome show up =
automatically.=20
This is the behavior of a new/fresh product. A plugin install should =
just introduce its new features intro the eclipse install and not =
intrude. Now if your plugin changes a perspective (which is already =
opened) the workbench will detect that and ask u to reset perspective to =
introduce the new changes. But thats ok. u alreay has the perspective =
open and u need to get whats new. For intro and welcome, not sure.=20
Is the intend for intro to replace welcome? They complement each other, =
but only one should be used, not both. Since Intro will hide welcome if =
both are defined. Legacy welcome needs to be supported for backward =
compatibility.
Mazen. =20
"news.eclipse.org" <henrich.kraemer@us.ibm.com> wrote in message =
news:c902r1$al9$1@eclipse.org...
If I understand correctly there is exactly one (or none) Intro per =
product. A plugin can contribute content to this intro using the =
ui.intro framework, which is very cool!
Some welcome information should also be shown to the user whenever the =
plugin is activated or first installed. Ideally the welcome information =
is not shown if the user already gets the product-intro with the =
extension. For example if the plugin was installed prior to the first =
startup of eclipse.
In my mind it would be natural if the plugin-welcome information and =
the plugin-intro information is the same. This is why I was wondering =
whether I can do this via the ui.intro framework.
Ignoring the desire to have the content in the exactly same format it =
seems that the welcome page gives me the behavior I am looking for.=20
Is the intent that ui.intro replaces or supersedes the welcomePage =
mechanism? If this is the case I would open a feature request.
Otherwise it seems the way to go is to use both ui.intro to the =
welcomePage mechanism
Mazen Faraj wrote:
If I understand u correctly, u want a user to install your plugin, =
and then on a restart u want Intro to be shown.=20
U cant accomplish this, and its by design. U can certainly open =
feature request if u strongly see a need.
Here is the reason: Intro has a life cycle, dictated by the user. On =
clean install (never ran workbench before), u will always get intro. =
Then state is remembered. U close with intro, you open with intro. In =
your case, you dont know what state your user left his workbench in and =
u cant change it. In fact, with the new OSGI support, there may not be a =
need for a restart, a plugin is doewnloaded and installed live, so why =
would u want to shock your users with a maximazed intro?=20
In your plugin documentation u can mention that if installing your =
plugin on a used workspace, open Welcome to see intro for your =
component.=20
hope this helps...
Mazen. =20
"news.eclipse.org" <henrich.kraemer@us.ibm.com> wrote in message =
news:c8t6mb$ruv$1@eclipse.org...
Thanks that worked.=20
I am still not sure how to address issue 1.=20
> 1. When the plugin is first installed the next start should =
surface an=20
> introduction.
If I was building a product, I think I know where to start but in =
the scenario of workbench extensions I am unsure whether there is a way =
to do this?
Mazen Faraj wrote:=20
you're 99% there. =20
You included the Page element as a child of in your =
extensionContent element. This is not the correct syntax, apologies for =
lack of documentation. (BTW, M9 has the schema for the content of the =
IntroContent xml file.)
All you have to do is make the Page element a sibling, not a =
child of, the extensionContent element, and all works. =20
<introContent>
<extensionContent alt-style=3D"css/swt.properties" =
style=3D"css/overview.css" =
path=3D"overview/page-content/overview-links/pdeAnchor">
<link label=3D"XXX guidance" =
url=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro" id=3D"Foo">
<text>TBD</text>
</link>
</extensionContent>
<page style=3D"css/overview.css" =
alt-style=3D"css/swt.properties" title=3D"Getting started with TBD" =
id=3D"xxx-intro">
<text>TBD</text>
</page>
</introContent>=20
As fyi, the deign of the introContent xml file is as follows:=20
a.. When used as content for a configuration, all the =
following can be children of introContent: page, group, link, html, =
title, text, include, head, img, and anchor (<-- note this is new in M9. =
You contribution in M9 would be the same, you only have to replace =
path=3D"overview/page-content/overview-links" with =
path=3D"overview/page-content/overview-links/pdeAnchor".=20
b.. When used as content for a configuration extension, all =
the above elemets are still valid, in there same hierarchy, plus the =
extensionContent element. The reason for this is simplicity. The same =
content file can be used as content to a configuration, and can be =
referenced from a configuration extension. =20
hope this helps..
Mazen...
"news.eclipse.org" <henrich.kraemer@us.ibm.com> wrote in message =
news:c8ma0g$4aq$1@eclipse.org...
> I am working on a plugin that extends eclipse.
> Here is what I would like to happen.
> 1. When the plugin is first installed the next start should =
surface an=20
> introduction.
> 2. The same content should also be linked to from the=20
> Help/Introduction/Overview.
>=20
> My plugin.xml contains this:
> <extension
> point=3D"org.eclipse.ui.intro.configExtension">
> <configExtension
> configId=3D"org.eclipse.platform.introConfig"
> content=3D"overviewExtensionContent.xml"/>
> </extension>
>=20
> I also copied overviewExtensionContent.xml from the PDE. To =
this end=20
> things work as expected, the contribution shows up after going =
into=20
> Help/Introduction/Overview however it still invokes a PDE help =
topic.
>=20
> From Help/Introduction/Overview I would like to show a page =
FOO that is=20
> based on HTML but would like to stay in the same window.
>=20
> I tried getting a first version of that page defined in=20
> overviewExtensionContent.xml but that didn't work. Here is the =
content=20
> of the file:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8" ?>
> <introContent>
>=20
> <!-- Extension to the SDK Overview Page. -->
> <extensionContent
> alt-style=3D"css/swt.properties"
> style=3D"css/overview.css"
> path=3D"overview/page-content/overview-links">
> <link
> label=3D"XXX guidance"
> =
url=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"
> id=3D"Foo">
> <text>TBD</text>
> </link>
> <page
> style=3D"css/overview.css"
> alt-style=3D"css/swt.properties"
> title=3D"Getting started with TBD"
> id=3D"xxx-intro">
> <text>TBD</text>
> </page>
> </extensionContent>
> </introContent>
>=20
> However eclipse doesn't show a page with TBD when I click on =
the link.
>=20
> The same page Foo should be shown to the user after install. =
How would I=20
> tell eclipse to do this?
>=20
> Also I am wondering whether there are any tricks that make=20
> authoring/debugging pages in the IntroContentFile XML Format =
more efficient?
>=20
------=_NextPart_000_002B_01C44318.6932CEB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>The legacy welcome behaved the same way =
as how the=20
Intro behaves today. With one twist that I will point out.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The Welcome of the primary feature used =
to be shown=20
to the user. An eclipse install could have more than one feature tagged =
as the=20
primary feature, but only one will be honored and the welcome of that =
one=20
primary feature was shown. Now here is the twist. Other welcomes could =
be=20
launched also through the menus.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>With the new Intro (now renamed to =
Welcome btw) its=20
the same story. There could be more than one product defined in a given =
eclipse=20
install, and each of these products could have an intro properly bound =
to it,=20
but only one product would be honrored on startup, and the intro of that =
product=20
will be shown. If that product does not have an intro, the old welcome =
of that=20
product is shown, if it was defined. Now other intros can not be shown. =
and if=20
an intro is shown, then all legacy welcome is hidden. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I believe there is a feature request =
already open=20
to enable showing other intros through a menu, just like the old =
welcome.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>if Im not wrong, the behavior that u =
are descriing=20
could not be accomplished, even with the old welcome. The behavior is =
installing=20
a plugin on an existing workspace and having the old welcome show up=20
automatically. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This is the behavior of a new/fresh =
product. A=20
plugin install should just introduce its new features intro the =
eclipse=20
install and not intrude. Now if your plugin changes a perspective =
(which is=20
already opened) the workbench will detect that and ask u to reset=20
perspective to introduce the new changes. But thats ok. u alreay has=20
the perspective open and u need to get whats new. For intro =
and=20
welcome, not sure. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Is the intend for intro to replace =
welcome?=20
They complement each other, but only one should be used, not both. Since =
Intro=20
will hide welcome if both are defined. Legacy welcome needs to =
be=20
supported for backward compatibility.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Mazen.</FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"news.eclipse.org" <<A=20
=
href=3D"mailto:henrich.kraemer@us.ibm.com">henrich.kraemer@us.ibm.com</A>=
>=20
wrote in message <A=20
=
href=3D"news:c902r1$al9$1@eclipse.org">news:c902r1$al9$1@eclipse.org</A>.=
...</DIV>If=20
I understand correctly there is exactly one (or none) Intro per =
product. A=20
plugin can contribute content to this intro using the ui.intro =
framework,=20
which is very cool!<BR><BR>Some welcome information should also be =
shown to=20
the user whenever the plugin is activated or first installed. Ideally =
the=20
welcome information is not shown if the user already gets the =
product-intro=20
with the extension. For example if the plugin was installed prior to =
the first=20
startup of eclipse.<BR>In my mind it would be natural if the =
plugin-welcome=20
information and the plugin-intro information is the same. This is why =
I was=20
wondering whether I can do this via the ui.intro =
framework.<BR><BR>Ignoring=20
the desire to have the content in the exactly same format it seems =
that the=20
welcome page gives me the behavior I am looking for. <BR><BR>Is the =
intent=20
that ui.intro replaces or supersedes the welcomePage mechanism? If =
this is the=20
case I would open a feature request.<BR>Otherwise it seems the way to =
go is to=20
use both ui.intro to the welcomePage mechanism<BR><BR><BR>Mazen Faraj=20
wrote:<BR>
<BLOCKQUOTE cite=3Dmidc8vl83$gpo$1@eclipse.org type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<DIV><FONT face=3DArial size=3D2>If I understand u correctly, u want =
a user to=20
install your plugin, and then on a restart u want Intro to be shown. =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>U cant accomplish this, and its by =
design. U=20
can certainly open feature request if u strongly see a =
need.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Here is the reason: Intro has a =
life cycle,=20
dictated by the user. On clean install (never ran workbench before), =
u will=20
always get intro. Then state is remembered. U close with intro, =
you=20
open with intro. In your case, you dont know what =
state your=20
user left his workbench in and u cant change it. In fact, with the =
new OSGI=20
support, there may not be a need for a restart, a =
plugin is=20
doewnloaded and installed live, so why would u want to shock =
your users=20
with a maximazed intro? </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>In your plugin documentation u =
can mention=20
that if installing your plugin on a used workspace, open Welcome to =
see=20
intro for your component. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>hope this helps...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mazen.</FONT> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV>"news.eclipse.org" <<A=20
=
href=3D"mailto:henrich.kraemer@us.ibm.com">henrich.kraemer@us.ibm.com</A>=
>=20
wrote in message <A=20
=
href=3D"news:c8t6mb$ruv$1@eclipse.org">news:c8t6mb$ruv$1@eclipse.org</A>.=
...</DIV>Thanks=20
that worked. <BR>I am still not sure how to address issue 1. =
<BR><FONT=20
face=3DArial size=3D2>> 1. When the plugin is first installed =
the next=20
start should surface an <BR>> introduction.<BR><BR></FONT>If I =
was=20
building a product, I think I know where to start but in the =
scenario of=20
workbench extensions I am unsure whether there is a way to do=20
this?<BR><BR>Mazen Faraj wrote:=20
<BLOCKQUOTE cite=3Dmidc8pbh3$vig$1@eclipse.org type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
<DIV><FONT face=3DArial size=3D2>you're 99% =
there. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>You included the Page element =
as a child of=20
in your extensionContent element. This is not the correct =
syntax,=20
apologies for lack of documentation. (</FONT><FONT =
face=3DArial=20
size=3D2>BTW, M9 has the schema for the content of the =
IntroContent xml=20
file.)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>All you have to do is make the =
Page element=20
a sibling, not a child of, the extensionContent element, =
and all=20
works. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial=20
=
size=3D2><introContent><BR> <STRONG ><extensionContent</STRO=
NG>=20
alt-style=3D"css/swt.properties" style=3D"css/overview.css"=20
=
path=3D"overview/page-content/overview-links/pdeAnchor"> <BR> &nbs=
p;<link=20
label=3D"XXX guidance" url=3D"</FONT><A=20
=
href=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"><FONT=20
face=3DArial=20
=
size=3D2>http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro</FONT></A><F=
ONT=20
face=3DArial size=3D2>"=20
=
id=3D"Foo"><BR> <text>TBD< ;/text> <BR> =
; </link><BR> <STRONG></extensionContent> <BR></STRO=
NG> <STRONG><page</STRONG>=20
style=3D"css/overview.css" alt-style=3D"css/swt.properties" =
title=3D"Getting=20
started with TBD"=20
=
id=3D"xxx-intro"><BR> <text>TBD</text& ;gt; <BR><STRO=
NG> </page><BR></STRONG></introContent> </FONT></DI=
V>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>As fyi, the deign of=20
the introContent xml file is as follows: =
</FONT></DIV>
<UL>
<LI><FONT face=3DArial size=3D2>When used as content =
for a=20
configuration, all the following can be children of =
introContent:=20
page, group, link, html, title, text, include, head, img, and =
anchor=20
(<-- note this is new in M9. You contribution in =
M9 would=20
be the same, you only have to replace =20
path=3D"overview/page-content/overview-links" with =20
=
path=3D"overview/page-content/overview-links/<STRONG>pdeAnchor </STRONG>".=
</FONT>=20
<LI><FONT face=3DArial size=3D2>When used as content =
for a=20
configuration extension, all the above elemets are still =
valid,=20
in there same hierarchy, plus the extensionContent element. =
The reason=20
for this is simplicity. The same content file can be used =
as=20
content to a configuration, and can be referenced from a=20
configuration extension. </FONT> </LI></UL>
<DIV><FONT face=3DArial size=3D2>hope this helps..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mazen...</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>"news.eclipse.org" =
<</FONT><A=20
href=3D"mailto:henrich.kraemer@us.ibm.com"><FONT face=3DArial=20
size=3D2>henrich.kraemer@us.ibm.com</FONT></A><FONT face=3DArial =
size=3D2>>=20
wrote in message </FONT><A =
href=3D"news:c8ma0g$4aq$1@eclipse.org"><FONT=20
face=3DArial =
size=3D2>news:c8ma0g$4aq$1@eclipse.org</FONT></A><FONT=20
face=3DArial size=3D2>...</FONT></DIV><FONT face=3DArial =
size=3D2>> I am=20
working on a plugin that extends eclipse.<BR>> Here is what I =
would=20
like to happen.<BR>> 1. When the plugin is first installed =
the next=20
start should surface an <BR>> introduction.<BR>> 2. The =
same=20
content should also be linked to from the <BR>>=20
Help/Introduction/Overview.<BR>> <BR>> My plugin.xml =
contains=20
this:<BR>> <extension<BR>>=20
=20
point=3D"org.eclipse.ui.intro.configExtension"><BR >>=20
<configExtension<BR>> =
=
=
configId=3D"org.eclipse.platform.introConfig"<BR>>=20
=
=
content=3D"overviewExtensionContent.xml"/><BR>> =
=20
</extension><BR>> <BR>> I also copied=20
overviewExtensionContent.xml from the PDE. To this end <BR>> =
things=20
work as expected, the contribution shows up after going into =
<BR>>=20
Help/Introduction/Overview however it still invokes a PDE help=20
topic.<BR>> <BR>> From Help/Introduction/Overview I =
would=20
like to show a page FOO that is <BR>> based on HTML but would =
like to=20
stay in the same window.<BR>> <BR>> I tried getting a =
first=20
version of that page defined in <BR>> =
overviewExtensionContent.xml=20
but that didn't work. Here is the content <BR>> of the =
file:<BR>>=20
<BR>> <?xml version=3D"1.0" encoding=3D"UTF-8" =
?><BR>>=20
<introContent><BR>> <BR>> <!-- Extension to the =
SDK=20
Overview Page. --><BR>>=20
=20
<extensionContent<BR>>=20
=
&=
nbsp; =20
alt-style=3D"css/swt.properties"<BR>>=20
=
&=
nbsp; =20
style=3D"css/overview.css"<BR>>=20
=
&=
nbsp; =20
path=3D"overview/page-content/overview-links"><BR>>=20
=
=
<link<BR>>=20
=
&=
nbsp; =20
label=3D"XXX guidance"<BR>>=20
=
&=
nbsp; =20
url=3D"</FONT><A=20
=
href=3D"http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro"><FONT=20
face=3DArial=20
=
size=3D2>http://org.eclipse.ui.intro/showPage?id=3Dxxx-intro</FONT></A><F=
ONT=20
face=3DArial size=3D2>"<BR>>=20
=
&=
nbsp; =20
id=3D"Foo"><BR>>=20
=
&=
nbsp; =20
<text>TBD</text><BR>>=20
=
=
</link><BR>>=20
=
=
<page<BR>> style=3D"css/overview.css"<BR>>=20
alt-style=3D"css/swt.properties"<BR>> title=3D"Getting =
started with=20
TBD"<BR>> id=3D"xxx-intro"><BR>>=20
=
=
<text>TBD</text><BR>>=20
=
=
</page><BR>>=20
=20
</extensionContent><BR>> </introContent><BR>> =
<BR>>=20
However eclipse doesn't show a page with TBD when I click on the =
link.<BR>> <BR>> The same page Foo should be shown to the =
user=20
after install. How would I <BR>> tell eclipse to do =
this?<BR>>=20
<BR>> Also I am wondering whether there are any tricks that =
make=20
<BR>> authoring/debugging pages in the IntroContentFile XML =
Format=20
more efficient?<BR>>=20
</FONT></BLOCKQUOTE><BR></BLOCKQUOTE></BLOCKQUOTE><BR></BLOCKQUOTE ></BODY=
></HTML>
------=_NextPart_000_002B_01C44318.6932CEB0--
|
|
|
Goto Forum:
Current Time: Fri May 09 14:57:50 EDT 2025
Powered by FUDForum. Page generated in 0.04494 seconds |
Home