Re: bugfix mode
I am seeing these warnings when starting JFXtras CalendarPicker using JDK 1.7.0_45. There is not much information to go on. Is there any way to git more information? WARNING: com.sun.javafx.css.StyleHelper calculateValue Could not resolve '-fx-text-base-color' while resolving lookups for '-fx-text-fill' from rule '*.toggle-button' in stylesheet jar:file:/C:/Program%20Files%20(x86)/Java/jdk1.7.0_21/jre/lib/jfxrt.jar!/com/sun/javafx/scene/control/skin/caspian/caspian.bss WARNING: com.sun.javafx.css.StyleHelper calculateValue Could not resolve '-fx-shadow-highlight-color' while resolving lookups for '-fx-background-color' from rule '*.toggle-button' in stylesheet jar:file:/C:/Program%20Files%20(x86)/Java/jdk1.7.0_21/jre/lib/jfxrt.jar!/com/sun/javafx/scene/control/skin/caspian/caspian.bss WARNING: com.sun.javafx.css.StyleHelper calculateValue Could not resolve '-fx-shadow-highlight-color' while resolving lookups for '-fx-background-color' from rule '*.text-field' in stylesheet jar:file:/C:/Program%20Files%20(x86)/Java/jdk1.7.0_21/jre/lib/jfxrt.jar!/com/sun/javafx/scene/control/skin/caspian/caspian.bss WARNING: com.sun.javafx.css.StyleHelper calculateValue Could not resolve '-fx-text-inner-color' while resolving lookups for '-fx-text-fill' from rule '*.text-field' in stylesheet jar:file:/C:/Program%20Files%20(x86)/Java/jdk1.7.0_21/jre/lib/jfxrt.jar!/com/sun/javafx/scene/control/skin/caspian/caspian.bss WARNING: com.sun.javafx.css.StyleHelper calculateValue Could not resolve '-fx-control-inner-background' while resolving lookups for '-fx-prompt-text-fill' from rule '*.text-field' in stylesheet jar:file:/C:/Program%20Files%20(x86)/Java/jdk1.7.0_21/jre/lib/jfxrt.jar!/com/sun/javafx/scene/control/skin/caspian/caspian.bss WARNING: com.sun.javafx.css.StyleHelper calculateValue Could not resolve '-fx-accent' while resolving lookups for '-fx-highlight-fill' from rule '*.text-input' in stylesheet jar:file:/C:/Program%20Files%20(x86)/Java/jdk1.7.0_21/jre/lib/jfxrt.jar!/com/sun/javafx/scene/control/skin/caspian/caspian.bss
hg: openjfx/8/graphics/rt: Fix to RT-33211: Fix TriangleMesh API to support a range of vertex format in the future
Changeset: 933044fa03e0 Author:Chien Yang chien.y...@orcale.com Date: 2013-10-19 00:29 -0700 URL: http://hg.openjdk.java.net/openjfx/8/graphics/rt/rev/933044fa03e0 Fix to RT-33211: Fix TriangleMesh API to support a range of vertex format in the future Reviewed-by: kcr, rbair ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/importers/Optimizer.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/importers/SmoothingGroups.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/importers/Validator.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/importers/maya/Loader.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/importers/obj/ObjImporter.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/jfx3dviewer/MainController.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/shape3d/PolygonMesh.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/shape3d/PolygonMeshView.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/shape3d/SkinningMesh.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/shape3d/symbolic/SubdividedPointArray.java ! apps/experiments/3DViewer/src/main/java/com/javafx/experiments/shape3d/symbolic/SymbolicPointArray.java ! apps/experiments/DukePad/modules/cubeGame/src/main/java/com/javafx/experiments/dukepad/cubeGame/FancyBox3D.java ! modules/base/src/main/java/com/sun/javafx/collections/ObservableIntegerArrayImpl.java + modules/graphics/src/main/java/com/sun/javafx/scene/shape/ObservableFaceArrayImpl.java + modules/graphics/src/main/java/javafx/scene/shape/ObservableFaceArray.java ! modules/graphics/src/main/java/javafx/scene/shape/TriangleMesh.java + modules/graphics/src/main/java/javafx/scene/shape/VertexFormat.java ! modules/graphics/src/test/java/javafx/scene/shape/TriangleMeshTest.java
Re: Media is now opensource
Sweet! See you there. On Oct 18, 2013, at 5:25 PM, Sven Reimers sven.reim...@gmail.com wrote: Put me down as interested Richard. We can chat a bit on it at Devoxx Sven Am 19.10.2013 02:08 schrieb Richard Bair richard.b...@oracle.com: That's pretty much it. VP6, T2K, deploy, FX JMX tooling. VP6 won't ever be opened because it is licensed 3rd party code. However it isn't used that much anymore, most folks are using h.264. T2K I will come back to. Deploy code (meaning, Applets) is not planned to be open sourced, and I don't think it can be, unless JavaSE open sources all the applet / webstart code. The JMX tooling code really doesn't work well (last I tried it didn't work at all…). However I have big plans for JMX tooling in the 9 timeframe which might come to fruition (anybody out there interested in live-debugging JavaFX let me know, I've got a project for you!). I don't now that we should bother open sourcing the JMX tooling code vs. just replacing it. Kevin, if it is easy to open it, lets just do it and use it as a starting point. For T2K, I'm a little unclear and hope someone can help clear up for me under what circumstances we use T2K in the shipping product. My current understanding was that we use native fonts for every platform except maybe embedded, but that we want to switch from T2K to native fonts (Pango or HarfBuzz or whatnot) soon. Is that right? The JDK uses an open source font library for OpenJDK, but T2K for the Oracle JDK. On FX we just wanted to have a single implementation that was used by both. The hope is that besides Applet code and VP6, everything in the Oracle JavaFX would be available in OpenJFX, so that JavaFX is truly an open source project built on open source code. For you guys at RedHat, the answer is: everything is open source. Go forth, build, and prosper :-). I read on twitter Miho succeeded in a build of OpenJFX based on OpenJDK. I think the doors are open for business. Other than we still need the mercurial server moved from version .9 to something modern so that we can have outside committers commit to the repo directly, whereas right now it would require gate repos. Sadness. But if it takes a Gate repo we'll use a darn gate repo so that we can be a real open source project. Richard
Re: Media is now opensource
We don't support it, and frankly there hasn't been any demand. I think along it easier to plug in codecs and letting developers do this (vs having built in support) is the way to go because shipping codecs with the platform (not app) is fraught with legal headaches. On Oct 18, 2013, at 5:29 PM, Felix Bembrick felix.bembr...@gmail.com wrote: Does JavaFX support VP8 and, if not, when will it support it? On 19 October 2013 11:16, Richard Bair richard.b...@oracle.com wrote: Is the fact that the VP6 decoder is not included because of a legal issue? Yes, we don't own the code (Google does!) so we can't release it. Google has opened VP8, the successor to VP6, but not VP6. Richard
Re: Media is now opensource
Regarding JMX: Kevin, if it is easy to open it, lets just do it and use it as a starting point. Should be pretty easy. I'll file a JIRA. -- Kevin Richard Bair wrote: That's pretty much it. VP6, T2K, deploy, FX JMX tooling. VP6 won't ever be opened because it is licensed 3rd party code. However it isn't used that much anymore, most folks are using h.264. T2K I will come back to. Deploy code (meaning, Applets) is not planned to be open sourced, and I don't think it can be, unless JavaSE open sources all the applet / webstart code. The JMX tooling code really doesn't work well (last I tried it didn't work at all…). However I have big plans for JMX tooling in the 9 timeframe which might come to fruition (anybody out there interested in live-debugging JavaFX let me know, I've got a project for you!). I don't now that we should bother open sourcing the JMX tooling code vs. just replacing it. Kevin, if it is easy to open it, lets just do it and use it as a starting point. For T2K, I'm a little unclear and hope someone can help clear up for me under what circumstances we use T2K in the shipping product. My current understanding was that we use native fonts for every platform except maybe embedded, but that we want to switch from T2K to native fonts (Pango or HarfBuzz or whatnot) soon. Is that right? The JDK uses an open source font library for OpenJDK, but T2K for the Oracle JDK. On FX we just wanted to have a single implementation that was used by both. The hope is that besides Applet code and VP6, everything in the Oracle JavaFX would be available in OpenJFX, so that JavaFX is truly an open source project built on open source code. For you guys at RedHat, the answer is: everything is open source. Go forth, build, and prosper :-). I read on twitter Miho succeeded in a build of OpenJFX based on OpenJDK. I think the doors are open for business. Other than we still need the mercurial server moved from version .9 to something modern so that we can have outside committers commit to the repo directly, whereas right now it would require gate repos. Sadness. But if it takes a Gate repo we'll use a darn gate repo so that we can be a real open source project. Richard
Re: Media is now opensource
https://javafx-jira.kenai.com/browse/RT-33682 Kevin Rushforth wrote: Regarding JMX: Kevin, if it is easy to open it, lets just do it and use it as a starting point. Should be pretty easy. I'll file a JIRA. -- Kevin Richard Bair wrote: That's pretty much it. VP6, T2K, deploy, FX JMX tooling. VP6 won't ever be opened because it is licensed 3rd party code. However it isn't used that much anymore, most folks are using h.264. T2K I will come back to. Deploy code (meaning, Applets) is not planned to be open sourced, and I don't think it can be, unless JavaSE open sources all the applet / webstart code. The JMX tooling code really doesn't work well (last I tried it didn't work at all…). However I have big plans for JMX tooling in the 9 timeframe which might come to fruition (anybody out there interested in live-debugging JavaFX let me know, I've got a project for you!). I don't now that we should bother open sourcing the JMX tooling code vs. just replacing it. Kevin, if it is easy to open it, lets just do it and use it as a starting point. For T2K, I'm a little unclear and hope someone can help clear up for me under what circumstances we use T2K in the shipping product. My current understanding was that we use native fonts for every platform except maybe embedded, but that we want to switch from T2K to native fonts (Pango or HarfBuzz or whatnot) soon. Is that right? The JDK uses an open source font library for OpenJDK, but T2K for the Oracle JDK. On FX we just wanted to have a single implementation that was used by both. The hope is that besides Applet code and VP6, everything in the Oracle JavaFX would be available in OpenJFX, so that JavaFX is truly an open source project built on open source code. For you guys at RedHat, the answer is: everything is open source. Go forth, build, and prosper :-). I read on twitter Miho succeeded in a build of OpenJFX based on OpenJDK. I think the doors are open for business. Other than we still need the mercurial server moved from version .9 to something modern so that we can have outside committers commit to the repo directly, whereas right now it would require gate repos. Sadness. But if it takes a Gate repo we'll use a darn gate repo so that we can be a real open source project. Richard
