Community
Participate
Working Groups
The I20091119-0815 E4 SDK has "e4" menu on the main menu bar: "Generate E4 example project" "UI Editor" "Reload Style Sheet" I don't think those menu items work.
Correct, because now they're 3.6 menu items that depend on e4 content in their IEvaluationContext I hope to fix them today, so at least they'll work (or remove them). PW
I fixed generate PSFs and removed the reload CSS for M2. We'll have to fix the UI editor for M3 PW
For M3, could the code examples be moved to a wiki page and the "e4 > Generate e4 Example Project" be changed to "e4 > Examples" and open a web browser on that new examples wiki page?
Moving the e4 examples to a wiki page would allow us to separate concerns and evolve/enhance/add examples independent of milestones.
I think that would be do-able. Right now the command executes org.eclipse.e4.ui.examples.legacy.workbench.GeneratePsfHandler We could open a URL in org.eclipse.ui.IWorkbench.getBrowserSupport() ... perhaps create a browser view (although we might get that for free). I think there's also a bug that would allow us to import a team project set (PSF) from a URL, so we could reference those on the wiki (or some other way) and import them without creating them in the workspace itself. PW
Created attachment 154606 [details] Patch with new command that opens web page Something like this that opens a web page in an editor?
# UI: Running the e4 photo demo, contacts demo, and the CSS examples http://wiki.eclipse.org/E4/UI/Running_the_photo_demo http://wiki.eclipse.org/E4/UI/Running_the_contacts_demo http://wiki.eclipse.org/E4/CSS I'd use these URLs and add them as 3 separate commands. You can use the parameterized command from o.e.ui.browser (I didn't even know this existed :-), id = org.eclipse.ui.browser.openBrowser which takes a couple of paramters. possibly: <command commandId="org.eclipse.ui.browser.openBrowser" id="e4.open.contact" label="Running the Contact Demo" mnemonic="C" style="push"> <parameter name="url" value="http://wiki.eclipse.org/E4/UI/Running_the_contacts_demo"> </parameter> <parameter name="browserId" value="org.eclipse.e4.ui.ContactsBrowser"> </parameter> <parameter name="name" value="Contacts Browser"> </parameter> <parameter name="tooltip" value="Running the Contacts Demo"> </parameter> </command>
I like your approach for modifying the plugin manifest and will use it, but I recommend a single menu item that opens a single web page. That web page contains references to multiple examples available for e4. If we have multiple menu items opening multiple web pages, one for each example, then the examples become tightly coupled to the distribution. If instead, as I am recommending, we have a single menu item that opens a single web page listing many if not all of the available examples, then we can add examples independent of the getting the e4 distribution out the door.
Fixing bug 162608 would also help improve the user's first impression. Perhaps the ability to drag a URL pointing to a *.psf file and dropping it on the package view which opens the "Import Project Set..." dialog to import the project set that was dropped.
*** Bug 298011 has been marked as a duplicate of this bug. ***
*** Bug 299842 has been marked as a duplicate of this bug. ***
*** Bug 318244 has been marked as a duplicate of this bug. ***
Created attachment 174694 [details] Add new menu items to open web page v02 Apply the web page idea with the already provided command. I've added the 3 pages that we have, contacts, e4 photo, and css examples. PW
We're not adding the e4 menu to the 4.0 SDK and we are using our wikis as our main method of providing "getting started' and links to tutorials, so for 4.0 the consensus was to remove this. PW
Created attachment 174776 [details] remove e4 menu v01
Boris, removal safe? PW
(In reply to comment #16) > Boris, removal safe? yes.
Released PW
