Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[e4-dev] N&N from the 4.1 M6 ModelTooling 
Hi John or whoever collects the N&N for e4 M6,

Attached you find the N&N from Model tooling including some screenshots.
If you feel there are too many pictures in it feel free to remove them ;-)

The most segnificant additions are made for runtime inspection
(contribution instance inspection, widget tree inspection, control
finder), NLS-Support and Scripting Support to interface with running
application through JavaScript.

Tom

Attachment: search.png
Description: PNG image

Attachment: control-finder.png
Description: PNG image

Attachment: runtime_tooling.png
Description: PNG image

Attachment: widget-tree.png
Description: PNG image

Attachment: js-support.png
Description: PNG image

Title: Eclipse "New and Noteworthy" Template

Eclipse "New and Noteworthy" Template

Last revised 2010-11-30.

This is the template for the "New and Noteworthy" document that accompanies each Eclipse project milestone build.

Note: This template document is XHTML 1.0 Transitional. Please use the W3C XHTML Markup Validation Service to check your document's markup before submitting. This will detect screwed up HTML tags, images without an "alt" attribute, and other tedious little details.

Instructions
Item title, in sentence style, no trailing punctuation, with unique id attribute on <tr> A blurb pitched to the Eclipse community (not just to members of the Eclipse Platform development team). Tell end users about changes they'll see in the UI. Tell component writers about changes they'll see at the client- and server-side APIs. Try to generate some excitement; save the boring details for the manual. The description should be complete sentences, with trailing punctuation.

Use active voice (say "you", not "the user"), and follow other advice in the Topic Content section of the Eclipse Doc Style Guidelines.

Stick to the default font and size. Make command names (Quick Fix), keyboard shortcuts (Ctrl+1), and preference page paths (Preferences > General > Keys) bold.

Do not enclose the first paragraph of an item in <p></p> tags.

Screenshots If a small image sheds light, place it below the description, in a separate paragraph. Regular screen snapshots should be done on Windows XP. Crop out any extraneous stuff to focus the reader's attention on your new feature. The image should be no more than 519 pixels wide and in PNG format (as opposed to GIF, TIF, BMP, or JPG). Use PNG-8 if your image doesn't have a lot of color, or PNG-24 if the screen shot uses enough color to warrant additional color depth. See also the Graphics section of the Eclipse Doc Style Guidelines.

Microsoft Paint actually saves to PNG on Windows XP and can easily be used to crop and save screenshots:

  • Arrange the windows for the shot
  • Use the Print Screen key (or Alt+Print Screen) to capture the screen
  • Open Paint (under All Programs > Accessories)
  • Ctrl+V to paste
  • Select the area you want to keep
  • Ctrl+C to copy it
  • Ctrl+N to create a new canvas (ok to discard old one)
  • Ctrl+V to paste selected portion
  • Save As > PNG

Name the file is a way that is appropriate and specific to the item (e.g., key-bindings.png, rather than something generic like image.png). Use all lowercase letters in the image file name, including the ".png" file extension. As a separator, use hyphen "-" rather than underscore "_".

Put all the images in a sibling directory named "images". This gives HTML like <img src="" alt="The Foo View" />. Include a suitable alt property (which is mandatory in XHTML 1.0). Do not embed the width and height of the image.

The images should be left justified (as opposed to centered).

Use the W3C XHTML Markup Validation Service to check your document's markup before submitting.

Platform
First item Item blurb.
Second item Item blurb.

Platform 4.1

Platform Model Tooling 4.1
Edit/View Model as XMI The model editor allows the developer modify the Application Model directly by editing the XMI-Content
Externalizing Strings The model editor adds similar support the plugin.xml-Editor already provides to externalize Strings to support localizing an Eclipse 4 application
Improved Class Search The Class search support has been improved to better support wildcard searches in packages
Runtime Contribution Inspection The live model editor now support runtime inspection of Objects created through DI and attached to to Application Model (Parts, Handlers, ...)
Control Finder The live model editor adds help to find the UI-Control created by the renderer for a certain Application Model element
Widget-Tree Browser The live model editor adds a view to inspect and browse the widget Tree associated with an UIElement of the Application model
Scripting Support The model editor added support to integrate scripting languages (by default _javascript_ is provided via rhino) to interface with Application Model (at design and runtime) and the complete running application (live model editor). This allows the developer to modify a running instance e.g. to correct or test UI modifications, ...

JDT

PDE

Back to the top