JavaFX 1.3.1 et NetBeans 6.9.1 sont disponibles

Disponible sur : http://javafx.com/downloads/all.jsp

Comme prévu, il n'y a pas de nouveautés majeures et c'est principalement une compilation de bug fixes et en plus la documentation des modifs est succinte. A noter plusieurs bugs non-corrigés dans le debugger.
Releases notes de JavaFX 1.3.1 : http://download.oracle.com/javafx/1....tes-1-3-1.html

Citation:

New Features

The following new feature is added to JavaFX in this release:

Applet and Web Start application startup process
JavaFX 1.3.1 introduces a new default process for starting JavaFX applet and Web Start applications, which can be customized by developers.

System Requirements

JDK 6 Update 21 is the recommended version of the Java SE Development Kit (JDK) for JavaFX 1.3.1 SDK. All other requirements are listed in the JavaFX System Requirements document.

Bug Fixes

The most important bug fixes in the JavaFX 1.3.1 release are as follows.

Issue: RT-7788 Scene.stylesheets are not taken into account.
Description: CSS styles were not applied if a Scene was created without any Controls, and then Controls were later added to the Scene.

Issue: RT-7939 Grid does not account for padding when calculating width and height.
Description: The Grid layout container did not take padding into account in its size calculations.

Issue: RT-8231 OverrunStyle.CLIP does not work as expected.
Description: In a Labeled control, setting the textOverrun variable to CLIP would remove characters from the middle of the string instead of clipping.

Issue: RT-8294 StringIndexOutOfBoundsException error is thrown in Labeled control.
Description: A Labeled control would throw StringIndexOutOfBoundsException if its textOverrun style was set to CLIP.

Issue: RT-8304 TreeView does not properly handle changes to its root.
Description: Changing the root node of a TreeView would fail if the tree was in the collapsed state.

Issue: RT-8324 Traversal Engine holds a strong reference to traversable nodes in the scene.
Description: An internal mechanism for focus traversal would retain references to Scene objects, causing memory leaks.

Issue: RT-8338 Padding changes on Flow layout do not set layoutBounds correctly.
Description: The preferred size calculations for the Flow container were incorrect if padding had been specified.

Issue: RT-8465 PopupMenu does not take Separator width into account.
Description: Menus were too wide if they contained all narrow items along with one or more separators.

Issue: RT-8565 Radial gradients do not work from stylesheet.
Description: Radial gradients did not work when specified via a CSS style sheet.

Issue: RT-8604 Grid prints error messages to console.
Description: The Grid container printed a warning message "Please set rows rather than content" even if the application had properly set the rows variable.

Issue: RT-8637 Toolbar does not render its items correctly.
Description: ToolBar did not display its contents properly if their layout bounds extended above or to the left of (0,0).

Issue: RT-8640 Setting Label.wrap to true makes the Label to increase its width.
Description: Setting Label.wrap to true caused the Label to increase its width continuously.

Issue: RT-8665 Text is positioned incorrectly in TextBox
Description: Text was positioned in a TextBox incorrectly if TextBox.positionCaret is used.

Detailed information is available in the JIRA Bug Database. You must have a JIRA account to access this database. If you don't have a JIRA account, you can register for one now.

This release also includes new CSS Reference Guide and improved JavaFX API documentation.

Documentation

All JavaFX 1.3 documentation is also accurate for JavaFX 1.3.1.

Known Issues and Limitations

There are no known issues specific to the JavaFX 1.3.1 SDK.

Releases notes de la Production Suite 1.3.1 : http://download.oracle.com/javafx/1....notes-1-3.html

Citation:

Known Issues and Limitations

Production Suite Installer

Issue RT-4788: Plugins for Adobe Illustrator and Photoshop from a previous installation will not be overwritten.

Description: If previous versions of Production Suite are not properly uninstalled, installing a new version will not overwrite the Plugins for Adobe Illustrator and Photoshop.

Workaround: Be sure to uninstall any older version of Production Suite before Installing Version 1.3. On Macintosh systems, you must manually uninstall the Adobe Photoshop and Adobe Illustrator plugins. For detailed instructions on how to uninstall previous versions, see Installing JavaFX Production Suite.

JavaFX Plugin for Adobe Illustrator or Adobe Photoshop

Issue RT-8526: Adobe Photoshop preview and export of clipped layers require the Export Effects option.

Description: During export from Adobe Photoshop to JavaFX, clipped layers require that the Export Effects option be selected for the clipped image to preview and export properly..

Workaround: If you cannot see the clipped image in the Preview screen, select the Export Effects checkbox, then click Preview again.
Issue RT-8496: System fonts are exported when fonts are embedded

Description: The online help incorrectly states that system fonts are not exported when the Embed Fonts option is selected during export from Adobe Illustrator or Photoshop. As of JavaFX 1.3, system fonts are exported when the Embed Fonts option is selected. Note, however, that the JavaFX Amble font family is never exported as an embedded font.

Workaround: None
Issue RT-6718: Some embedded fonts do not display correctly on Windows Vista

Description: When the Embed Fonts option is selected when exporting from Adobe Illustrator or Photoshop, the text in the JavaFX graphic might look fuzzy with some fonts on the Windows Vista operating system.

Workaround: None.
Issue RT-4728: Adobe Photoshop text layers display only the first font in each layer after export.

Description: When a text layer from Adobe Photoshop is exported as an FXD text description (not rasterized), the entire text string is displayed in the first font from the layer. This occurs whether or not the Embed Fonts option is selected during export.

Workaround: There are two possible workarounds if any single text layer in the graphic has more than one font:
Choose the Rasterize Text option during export.
Divide the text into different layers so that each layer has a single font.
Issue RT-3493: Limitations when exporting text from Adobe Photoshop.

Description: Note the following limitations when the Rasterize Texts checkbox is cleared when exporting from Adobe Photoshop:

Multiline text is exported correctly if end-of-line characters are used to separate lines, if text is auto-wrapped into a box, it will be exported as a single line
No extended attributes are exported, such as justification, kerning, or tracking.
No text transformations are exported.

Workaround: Export the graphic with the Rasterize Texts checkbox selected. The text will be exported as a PNG graphic. Although it cannot be edited by the application developer, it does appear in the application as it was designed.
Issue RT-2909: An applied effect can cause Adobe Illustrator names to get lost during conversion in some cases.

Description: Due to an Adobe Illustrator conversion characteristic, the name of a graphic object in Adobe Illustrator can be lost during conversion when both of the following conditions are true:
The element is a member of a layer or group with an applied effect.
This layer group is exported with either the Rasterize All Effects or Rasterize Unknown Effects option selected.
The result is that entire group, including that element, is replaced by a bitmap, and the element name is lost.

Workaround: There are two possible workarounds:
Apply the effect on a subtree that does not contain the named element.
Move the named element outside of the subtree and apply the effect on this named element.
Issue RT-1905: Text might not be exported correctly from Adobe Illustrator.

Description: This issue can manifest itself in various ways, especially when text is positioned on the path, or when extra vertical spacing is inserted in paragraphs.

Workaround: None.
Issue RT-2298: Neighboring shapes might not fit seamlessly in graphics exported from Adobe Illustrator.

Description: Shapes with different colors occasionally do not align perfectly in the exported JavaFX graphic, and a thin separation line appears with the background visible.

Workaround: None.
Issue RT-825: Styles are not supported for Adobe Photoshop export.

Description: When you export files from Adobe Photoshop, styles are not recognized.

Workaround: None.
Issue RT-3261: Adobe Photoshop on Mac crashes intermittently when you open the Save for JavaFX preview window.

Description: After opening a graphics file in Photoshop and choosing File > Automate > Save for JavaFX, one user experienced Photoshop intermittently crashing with the error message "The application 'Photoshop' has unexpectedly quit." The problem was not due to Production Suite but due to a Photoshop problem.

Workaround: Delete the Photoshop Preferences file. For instructions on deleting the Preferences file and other troubleshooting tips, see the Adobe tech note at http://kb.adobe.com/selfservice/view...1517&sliceId=2.
Issue: JavaFX graphics (with an FXZ or FXD extension) cannot be imported into Adobe Photoshop.

Description: JavaFX graphics that are exported from Adobe Illustrator or Adobe Photoshop cannot be imported back into Adobe Illustrator or Adobe Photoshop.

Workaround: To view JavaFX graphics, use the JavaFX Graphics Viewer, included in the Production Suite installation, or use the NetBeans IDE to preview the graphic or view the code. See Getting Started With JavaFX Production Suite or the Production Suite online help for instructions on how to use the JavaFX Graphics Viewer.

SVG Converter

Issue RT-8114: SVG Converter converts SVG Polyline into JavaFX Polygon.

Description: When a polyline is converted from SVG to JavaFX format, the FXD description contains a Polygon element rather than a Polyline element.

Workaround: Manually change the FXD description from Polygon to Polyline.
Issue RT-5272: SVG Converter ignores the SVG spreadMethod attribute.

Description: The SVG Converter tool ignores the spreadMethod attribute of the SVG <gradient> element.

Workaround: None.
Issue RT-5270:

Description: In the conversion from SVG to JavaFX, the rx attribute can only be converted to arcWidth, and the ry attribute can only be converted to arcHeight. The ability in SVG to infer the ry attribute value from that of rx and vice versa is not supported by the SVG converter tool.

Workaround: Specify both the rx and ry attributes, even when the values are the same.
Issue RT-2415: The opacity attribute appears twice on the elements in files converted from SVG format.

Description: Opacity and fill-opacity in SVG are both converted to the opacity attribute in JavaFX Data Files (FXD). This conversion results in two opacity attributes in the FXD source description: the first occurrence has a value set to 1, and the second occurrence has the value set correctly. The graphic is displayed correctly, because the second occurrence overwrites the first.

Workaround: No workaround is required.

Releases notes de NetBeans 6.9.1 : http://download.oracle.com/javafx/1....tes-1-3-1.html

Citation:

What's New
NetBeans IDE 6.9.1 for JavaFX incorporates the JavaFX 1.3.1 SDK and provides an improved JavaFX debugger with the following enhancements:

Virtual Machine names display as they are typed (in previous version they included ascii characters such as $)
Sequences are properly displayed.
Debugger variable evaluation must be manually triggered.

[...]

Known Bugs, Issues, and Limitations

Debugger

Issue187976: Watch window shows IntVal@1365c67 as an expression value.
Issue188711: ClassCastException: com.sun.tools.jdi.ObjectReferenceImpl cannot be cast to com.sun.javafx.jdi.FXObjectReference.
Issue188659: IOOBE when stepping through the code.
Issue188663: +Script node is not always displayed.
Issue188482: Debugger does not stop on a breakpoint.
Issue188726: Debugger should not allow to put breakpoints if line number is missing.
Issue189021: NullPointerException is thown at org.netbeans.modules.debugger.jpda.models.ArgumentObjectVariable.

Pour quoter PhiLho sur les forums de Sun:

Citation:

Envoyé par PhiLho

1.3.1 is out? It was a quiet release!

Salut!

Cela a l'air vraiment d'une release rapide :roll:

Ce qui serait intéressant actuellement ce serait qu'il mette tout en open-source!:P

http://www.developpez.net/forums/d95...-allez-signer/

mouais.. quelques améliorations,malheureusement, tant que les applets et javafx ne seront pas bien supportés par des outils tels que maven, je reste septique.

en plus, toujours pas opensource !

Petite correction, j'ai pointé sur le mauvais readme (c'était celui de NetBeans 6.9.1) mais bon comme indiqué celui de la 1.3.1 n'est pas transcendant non plus.

1 pièce(s) jointe(s)

Toujours aucune amélioration sur la conversion des gradients circulaires transformés :roll:.

Pièce jointe 65636

Outil pour les designers, mon c.... oui... :roll:

Oui une petite release, en attendant que le debugger soit finalisé j'ai l'impression.
Les variables globales ne sont toujours pas visibles:cry:http://www.developpez.net/forums/ima...s/icon_cry.gif
A noté que la zone de texte dans la démo du CSS ne se gondole plus, il était temps:aie:

Donc la nouveauté c'est de pouvoir personnaliser simplement la fenêtre de chargement :ccool:
http://download-llnw.oracle.com/java...cationStartup/
Ceci dit on pouvait déjà le faire avec un JPanel depuis un moment.

Citation:

Loading and preparation
The required resources are loaded, including the JavaFX runtime and application code, from either the network or a disk cache, and validation procedures occur.

Hum... commencerait-on enfin à appercevoir la lumière au bout du tunnel (du mic-mac de la redistribution des runtimes) ?

Je crois que la licence du runtime concerne l'utilisation du cache de Webstart, rien n'interdisait de mettre à jour le cache manuellement et / ou hors ligne, du moment que l'application javaFX est lancée via un jnlp.
Ceci dit il est grand temps de clarifier ce 'mic mac', he he c'est un peu la spécialité d'Oracle les licences non? :mouarf:

Utilisation avec InkScape

Salut bouye, dis moi il me semble que tu travailles avec InkScape, je commence à regarder mais je ne vois pas comment exporter directement en fxd sans passer par la production suite.
J'ai aussi essayé quelques effets mais cela ne semble pas fonctionner, sais tu si il existe un tableau de correspondance SVG->FXD.
Merci ;)

Pas grand chose du côté de Netbeans si ce n'est la possibilité de mettre ses CustomNode dans la palette, etc...:mrgreen:
http://wiki.netbeans.org/JavaFXComposerNewIn691FCS

Cool ENFIN ! :ccool:

Ah oui j'avais oublie de repondre a la question. Non pour ce que j'en sait il n'y a pas de tableau de conversion officiel SVG -> FXD. Le plus simple serait de produire quelques formes basiques et peintures basiques et de les convertir pour voir ce que ca donne et se creer un catalogue (mais bon bien sur il faut un mac ou windows sous la main).

Mais tu peux sinon directement produire du code FX depuis Inkscape aussi (File->Save As et choisir JavaFX (*.fx)). Faut pas une version trop ancienne car sinon ca produit du code pour F3 / JavaFX beta et donc non compatible bien sur. Jamais trop teste le degre de fidelite de la conversion par contre.

C'est vrai que cette fonction était plus que nécessaire, cependant le menu n'apparait pas avec un fichier 'design', plutôt embêtant quand on a encapsuler tous ses 'design fragment' dans des Panel depuis que les layouts fonctionnent à peu près :massacre:
Au sujet de Inkscape en fin de compte je crois que je vais surtout faire du SVG et utiliser le convertisseur SVG->FXD.:aie:
Le gros problème viens surtout de la structure du SVG pour faire en sorte que les nodes soient bien groupés à l'export ou que l'on puisse partager des couleurs entre les objets SVG.
Je sais, je rêve un peu en imaginant qu'on ne soit pas obliger de reprendre à la main les FXD.

Pour la demo de test que j'ai ou l'interface qui l'a precedee (qui avait bien plus de noeuds animes) je ne me suis pas casse la tete a chercher a optimiser quoi que ce soit et ca marche plutot bien. Les calques et les groupes d'Inkscape deviennent des Group en FXD / FX.

Pour le partage des paint meme Inkscape est penible a ce niveau-la et les duplique a tout va et donc il faut gerer ca manuellement au final ; sans compter qu'il faut regulierement nettoyer les references inutiles pour garder un SVG light (File -> Vacuum Defs).

Sinon pour de "vrais" programmes, je n'utilise le FXD que pour des trucs ponctuels (icone, dessin qui a besoin d'etre vectoriel) puisque comme FX ne supporte pas le 9-slicing pour me moment, on ne peut pas designer des apparences de controle ou de fenetre redimensionnables par exemple et donc ca perd tout son interret (donc abandon du FXD dans la plupart des projets 2 mois apres l'essai initial).

Mieux vaut tard que jamais : les specifications FXD.