to take more than a few minutes to figure out, best
to punt on this rather than soak up Felipe's precious time.
I think its fine.
-phil.
Richard
On Jun 3, 2013, at 11:26 AM, David Grieve david.gri...@oracle.com wrote:
I would rather see the deriveFont methods, but not as factory methods
On Jun 18, 2013, at 3:54 PM, Mario Torre neug...@redhat.com wrote:
Hi all!
I was trying to figure out how JavaFX parses and uses the style under
the hood and I stumbled on something I don't fully understand (I admit
I'm not really a CSS expert yet :).
In the modena.css, right at the
https://javafx-jira.kenai.com/browse/RT-31282
Scene has a fillProperty which should be styleable via CSS but this would
require making Scene implement the javafx.css.Styleable interface. The
interesting bits from the interface are
public String getId()
public ObservableListString
Hi Martin,
With regard to having this work without a Scene…
I think having a method that would layout a node without the node actually
having to be part of the scene-graph would be _very_ useful. Often times,
developers will do the show-hide trick or add-remove trick to get a node's
bounds
On Jul 8, 2013, at 9:52 AM, David Grieve david.gri...@oracle.com wrote:
I'm wondering why this validate can't just be implicit in any call that
uses or returns layout bounds. Surely we can tell from the dirty bits
whether or not something needs layout and/or css.
On Jul 8, 2013, at 12:31 PM
Vote: yes
On Jul 9, 2013, at 6:07 PM, Richard Bair richard.b...@oracle.com wrote:
I hereby nominate Debbie Masada to OpenJFX Committer.
Debbie is a member of the samples team and works on Ensemble and other sample
applications, adding functionality etc. as necessary. Some of her recent
or was it
just to cover up errors we were seeing? I remember having done this but don't
remember if it was truly needed or not?
Richard
On Jul 12, 2013, at 9:03 AM, David Grieve david.gri...@oracle.com wrote:
I hesitate to mention Node#impl_processCSS(boolean) which is very very close
to your
Probably a question better put to the OTN forums, but…
In caspian.css, you'll find
/* A very light grey used for the background of windows. See also
* -fx-text-background-color, which should be used as the -fx-text-fill
* value for text painted on top of backgrounds colored with
Which build?
Yesterday I filed https://javafx-jira.kenai.com/browse/RT-31745
On Jul 18, 2013, at 9:39 AM, Peter Penzov peter.pen...@gmail.com wrote:
Hi,
I tested to run code developed on JavaFX 2.2. On JavaFX 8 the size of
the Font cannot be set properly with setStyle(-fx-font-size:
Currently, a control has a default style-class. For example, you can use
.button in a style-sheet to style a Button. I propose to move the default
style-class from the control to the skin (RT-32186). The impetus for this
change is two-fold.
Firstly, it can be argued that setting the
https://javafx-jira.kenai.com/browse/RT-31196
On Aug 7, 2013, at 12:35 PM, Martin Klähn grazer...@gmail.com wrote:
Hi guys,
I've just realized that the ProgressIndicator in Modena isn't shown as a
rotating circle. It looks like somebody pried apart the ProgressWheel and
left it apart.
I'm assuming this is 8.0? If so, what com.sun classes did you need to pull in
and why? I'd like to know from the perspective of the owner of the styleable
API. If you have to pull in com.sun, then I might have missed something
somewhere since all you should need is in the javafx.css package.
Vote: Yes
On Aug 15, 2013, at 2:11 PM, Artem Ananiev artem.anan...@oracle.com wrote:
I hereby nominate Mick Fleming (OpenJDK user name: mickf) to OpenJFX
Commmitter.
Mick is a member of JavaFX Controls team at Oracle. He fixed many bugs and
implemented tons of features in virtually
Vote: Yes
On Aug 15, 2013, at 1:36 PM, Artem Ananiev artem.anan...@oracle.com wrote:
I hereby nominate Felipe Heidrich (OpenJDK user name: felipe) to OpenJFX
Committer.
Felipe is a member of JavaFX graphics group at Oracle. He is mostly
responsible for JavaFX text and fonts, but not
There is https://javafx-jira.kenai.com/browse/RT-21206, which I've just edited
to be public.
On Aug 28, 2013, at 2:29 PM, John Smith john_sm...@symantec.com wrote:
Is there any plan to make impl_processCSS(true) public API?
Should I create a Jira for this?
If there were a public API, would
This is (or should be) RT-32839, which is fixed in 8.0 and should make its way
into next week's promotion.
On Sep 14, 2013, at 7:26 AM, Tom Eugelink t...@tbee.org wrote:
On JavaFX 8.0 we're getting all kind of CSS warnings when running the JFXtras
8.0 project. I personally am waiting for
And what about Stream? I like the declarative code that comes from using Stream
and I can see places in the code where Stream could be used, but I wonder about
its performance relative to iterators and/or enhanced for loops.
On Oct 3, 2013, at 4:45 PM, Richard Bair richard.b...@oracle.com
Vote: YES
On Oct 24, 2013, at 9:05 AM, Artem Ananiev artem.anan...@oracle.com wrote:
I hereby nominate Victor Shubov to OpenJFX Committer.
Victor is a member of JavaFX SQE team at Oracle. He has already contributed
enough changesets into the tests repository:
$ hg log -M -u Victor
Dear OpenJFX Community,
Please review the fix for the issue:
https://javafx-jira.kenai.com/browse/RT-26277
The webrev is available at: http://cr.openjdk.java.net/~kcr/RT-26277/webrev/
The JIRA issue contains detailed information.
Thanks,
David
The purpose of this email is to solicit feedback on an issue related to Region
layout and the use of percent values in insets.
https://javafx-jira.kenai.com/browse/RT-26277 is the relevant JIRA issue.
Currently, a Region's width and height depends on the width and height of its
content plus
https://javafx-jira.kenai.com/browse/RT-33919
Please review: http://cr.openjdk.java.net/~dgrieve/RT-33919/webrev/
Reviewers: jgiles
The ObservableMapStyleableProperty?,ListStyle should only contain only
those styles that apply in the current CSS transition state. This fix resolves
a regression
Here is one way that uses a linear-gradient style where the stop offsets are
defined by the slider value
public void startx(Stage stage)
VBox vbox = new VBox(4);
final Slider slider = new Slider();
SliderSkin skin = new SliderSkin(slider);
slider.setSkin(skin);
You might want to look at what Gerrit has done here:
http://harmoniccode.blogspot.com/2013/10/friday-fun-xviii.html
On Dec 4, 2013, at 5:05 PM, Pedro Duque Vieira pedro.duquevie...@gmail.com
wrote:
OK, sounds reasonable. Too bad about the code duplication that will need to
take place.
The way it works in 8.0 is that there is a cache of loaded stylesheets. When a
scene or parent adds a stylesheet, the stylesheet is added to the cache. Any
other scene or parent that uses the same stylesheet will get the one from
cache. If a scene or parent later removes the stylesheet, the
. Nothing visible
happens when I do:
scene.stylesheets.clear()
scene.stylesheets.add(sameStylesheet)
Given your description below, my impression is that RELOADING should also
work...
Thank you for any suggestions,
Neil
From: David Grieve david.gri...@oracle.com
It is possible, but probably not in the way that
https://javafx-jira.kenai.com/browse/RT-17293 would provide. By that I mean, it
would be nice to be able to progammatically say the border color for this
button when hovered is red. This can be done now by adding an invalidation
listener to the
The reason things are as they are is because most properties in the core
classes are lazily created and I didn't want cause the property to be created
just to see if it was bound. But that is a particular concern for the core
classes and not so much for controls.
I'm not sure if you are aware
Thanks, John. It would be helpful if you could create an issue in jira to track
this.
On Jan 8, 2014, at 4:18 PM, John Hendrikx hj...@xs4all.nl wrote:
On 8/01/2014 14:28, David Grieve wrote:
The reason things are as they are is because most properties in the core
classes are lazily created
I'm going to take a pass at bugs assigned to Mick.
https://javafx-jira.kenai.com/issues/?jql=project%20%3D%20RT%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20%3D%20mickf
If I get through that list, I'll start in on
On Jan 24, 2014, at 4:02 PM, John Hendrikx hj...@xs4all.nl wrote:
I've got an update on this.
I've rewritten the code now to make use of multiple skins, and doing some
trickery with Factories to make them easily switchable.
The main reason I've rewritten them is because I think I will
On Jan 25, 2014, at 5:54 AM, John Hendrikx hj...@xs4all.nl wrote:
On 24/01/2014 22:28, David Grieve wrote:
On Jan 24, 2014, at 4:02 PM, John Hendrikxhj...@xs4all.nl wrote:
I've got an update on this.
I've rewritten the code now to make use of multiple skins, and doing some
trickery
https://javafx-jira.kenai.com/browse/RT-30479 is probably the issue you are
bumping up against.
On Jan 28, 2014, at 2:29 PM, Christoph Caks cc...@bestsolution.at wrote:
Hi,
I have a question regarding regions on android
it seems that all regions with a set background have some kind of
Hi Jonathan, Martin,
Please review https://javafx-jira.kenai.com/browse/RT-21495.
A patch is attached to the bug that follows the comment I added to the bug on
January 13th. The patch addresses Alexander's observation re: potential NPE.
I encourage you to take a hack at ScrollPaneSkin. In particular the method
computeScrollNodeSize. I suspect the change would be pretty much localized to
this method.
On Jan 31, 2014, at 2:02 PM, Jeff Martin j...@reportmill.com wrote:
ScrollPane has the feature for content that needs to track
On 2/19/14, 5:07 AM, Hervé Girod wrote:
Hello,
I have a question about how the CSS styling work, when a node skin use sub
nodes.
For example, the Button control uses a LabeledText, but it is not necessary to
setup the style of the LabeledText inside the button to set the font of the
button
On 2/21/14, 11:36 AM, Aliaksei Kishko wrote:
Hello.
I allow me to express several opinions on the JavaFX:
5) Styles need get pseudo classes via setStyle(), for example:
menuItem.setStyle(:focused {-fx-background-color: yellow;});
The Node#setStyle(String) API is analogous to the 'style'
Everyone should just accept that there is no such thing as a 'point' in
JavaFX. Work in pixels and you will achieve nirvana.
On 3/5/14, 5:49 PM, Pedro Duque Vieira wrote:
Here is the definition of point:
http://www.w3schools.com/cssref/css_units.asp
As Jeff is saying it should be 1/72 inch.
Hi Martin,
Please review
Webrev: http://cr.openjdk.java.net/~dgrieve/RT-33073/webrev.00/
JIRA: https://javafx-jira.kenai.com/browse/RT-33073
Details are in JIRA. Please note that the webrev has diffs for
cssref.html that are not related to this change but are there because of
a changeset I
Hey Felipe,
I recall a couple of years ago when Phil drilled it into me that Font
size was pixels. So when you said that Font size is point, I was
skeptical. But, indeed, you are correct and I am mistaken.
I see now that setting font size from point units in our CSS is broken.
Our CSS
On 3/6/14, 4:10 PM, Phil Race wrote:
I think your sum is backward. If 0.75pts==1 pixel then a 12 pt font
will be 16 pixels.
Exactly why my wife doesn't let me near the checkbook.
The JIRA issue (now public) just says that these impl_ methods that
SceneBuilder uses need to be public API. Much work needs to be done in
the area of public API for accessing CSS styles and whatnot. But, unless
I'm told otherwise, there won't be any implementation of such an API
before 9.
Jonathan,
Please review http://cr.openjdk.java.net/~dgrieve/RT-36068/webrev.00/
Details of the change can be found in
https://javafx-jira.kenai.com/browse/RT-36068
Thanks,
-- David
Too bad we can't go back and have WritableValue also extend Styleable...
I'm happy to live with the @SuppressWarnings in this particular context
since we know that graphicProperty is indeed a StyleablePropertyNode,
as is the case where we cast in implementations of the CssMetaData
Jonathan,
Please review: http://cr.openjdk.java.net/~dgrieve/RT-35864/webrev.00
A summary of the changes is in:
https://javafx-jira.kenai.com/browse/RT-35864
Hopefully this will resolve this annoying warning once and for all.
Details of the change may be found in JIRA.
Changeset is http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/37342603df94:
JIRA issue is : https://javafx-jira.kenai.com/browse/RT-36272
I thought we were staying away from the Stream API for now?
On 4/2/14, 2:17 PM, hang...@oracle.com wrote:
Changeset: db120a66633f
Author:Felipe Heidrich felipe.heidr...@oracle.com
Date: 2014-04-02 11:13 -0700
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/db120a66633f
This is coming a bit late in the game, but the proposal is to add this
API to Scene:
public ObservableListString getUserAgentStylesheets()
This would allow a Scene to have a user-agent style distinct from the
application.
https://javafx-jira.kenai.com/browse/RT-35260
Jonathan,
Could you please review:
http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/fe6fe6108a11
for https://javafx-jira.kenai.com/browse/RT-35260. I still need to
update the cssref and to add unit tests.
naturally look at this from another angle and say the Syleable
interface should have been shown in the API but I guess this not going
to change so we need to live with casts and the implementation detail.
Tom
On 30.04.14 15:39, Tom Schindl wrote:
Hi,
On 29.04.14 14:35, David Grieve wrote:
I've
Unit test only changes, too?
On 5/5/14, 11:07 AM, Stephen F Northover wrote:
Hi all,
Note also that this is M4 Milestone week which means no post-commit
reviews and extra +1 controls required to release code. The main
point is that one of Kevin, Daniel, Jasper, Lisa or David H must be
This bug was reviewed and approved before, but in looking for a fix for
RT-36995, I found some issues with the fix. Namely, that it was possible
to have more than one REAPPLY queued up and that it was possible for the
REAPPLY happen without a following UPDATE. Rather than roll the fixes
for
Please review https://javafx-jira.kenai.com/browse/RT-36995. The fix is
a one-liner, so there is no webrev.
Per Kevin's instructions, the previous changeset for RT-36838 was backed
out in order to resolve RT-36995. I've attached a new webrev to RT-36838
which is an improved fix for RT-36838 and which also ensures RT-36995
doesn't regress. These changes won't be pushed until after M4 integration.
Issue is caused by an infinite loop in StyleManager code. The code in
question was referencing the wrong variable. Trivial fix can be found in
the JIRA issue.
https://javafx-jira.kenai.com/browse/RT-37018
Can I get your +1 or -1 on this change. Thanks.
On 5/9/14, 10:45 AM, David Grieve wrote:
Per Kevin's instructions, the previous changeset for RT-36838 was
backed out in order to resolve RT-36995. I've attached a new webrev to
RT-36838 which is an improved fix for RT-36838 and which also
Jonathan,
Can I get you to review
https://javafx-jira.kenai.com/browse/RT-37025
http://cr.openjdk.java.net/~dgrieve/RT-37025/webrev.00/
Thanks
Vote: YES
On 5/14/14, 1:39 PM, Stephen F Northover wrote:
I hereby nominate Jerome Cambon to be an OpenJFX Committer.
Jerome Cambon is a significant contributor of the JavaFX Scene Builder
2.0 product, and is the designated owner of the Inspector Panel as
well as the CSS Panel. Jerome has
Vote: YES
On 5/14/14, 1:48 PM, Stephen F Northover wrote:
I hereby nominate Mo Chicharro to be an OpenJFX Committer.
Mo Chicharro is a significant contributor of the JavaFX Scene Builder
2.0 product, and, as the visual and interaction designer, he is the
designated owner of all FXML and CSS
Vote: YES
On 5/14/14, 1:48 PM, Stephen F Northover wrote:
I hereby nominate Sandra Lions-Piron to be an OpenJFX Committer.
Sandra Lions-Piron is a significant contributor of the JavaFX Scene
Builder 2.0 product, and is the designated owner of the Hierarchy
Panel as well as all menu commands.
Vote: YES
On 5/14/14, 1:48 PM, Stephen F Northover wrote:
I hereby nominate Yves Joan to be an OpenJFX Committer.
Yves Joan is a significant contributor of the JavaFX Scene Builder 2.0
product, and is the designated owner of the Library Panel, Document
Panel and product packaging. Yves has
Jonathan,
Please review
http://cr.openjdk.java.net/~dgrieve/RT-36554/webrev.00/
https://javafx-jira.kenai.com/browse/RT-36554
Kevin, Steve, Lisa
I'd like at least one of you to review the StubToolkit change for
cross-platform considerations (I'm assuming there are none).
Jonathan,
I've pasted a diff for modena.css in
https://javafx-jira.kenai.com/browse/RT-36778
Would you mind creating a bug for this?
On 5/16/14, 10:38 AM, Scott Palmer wrote:
Should a better cross-reference or mention of CSS properties in the Javadocs?
Many properties can be set via calling methods or through CSS, but
when browsing the Javadocs the related CSS properties are not
Maintaining the css ref is a real pain. All those tables should be given
over to an automated process.
On 5/16/14, 12:03 PM, Scott Palmer wrote:
I'm not sure what you mean. I'm only talking about documentation for
the public API. It's just a clarification for the existing docs.
On a side
Good find. The code needs to save off the StyleOrigin and use applyStyle
instead of set. I don't like that you have to deal with this level of
detail, but I haven't figured out any way around it yet. I'm open to ideas.
// save and set tab animation to none - as it is
not a
, David Grieve wrote:
Good find. The code needs to save off the StyleOrigin and use applyStyle
instead of set. I don't like that you have to deal with this level of
detail, but I haven't figured out any way around it yet. I'm open to ideas.
// save and set tab animation to none
Jonathan, Martin,
Please review
http://cr.openjdk.java.net/~dgrieve/RT-37174/webrev.00/
http://cr.openjdk.java.net/%7Edgrieve/RT-37174/webrev.00/
https://javafx-jira.kenai.com/browse/RT-37174
Steve, Kevin,
I'm looking for your ok on a change to rt/build.gradle that will allow
me to add @css tags in javadoc. The diff is in the bug. This isn't the
fix for the bug, but if you don't want to allow the tag option, then I
need to approach this bug in a different way.
Only if someone runs javadoc without adding a -tag css arg, which will
result in an 'unknown tag' error.
On 5/22/14, 3:35 PM, Stephen F Northover wrote:
Hi David,
I didn't see a problem with this. Is there a downside to adding
arbitrary tags to JavaDoc?
Steve
On 2014-05-22 3:23 PM, David
easier!
Tom
On 22.05.14 21:42, David Grieve wrote:
Only if someone runs javadoc without adding a -tag css arg, which will
result in an 'unknown tag' error.
On 5/22/14, 3:35 PM, Stephen F Northover wrote:
Hi David,
I didn't see a problem with this. Is there a downside to adding
arbitrary tags
Using styles is preferable to setting the property value. If styles are
used, then you don't have the problem you describe.
An alternative, if styles are not used, is to cast the property to
StyleableProperty and use applyStyle(null, value) instead of set. CSS
then thinks that the value has
a clue about it.
Tom
Von meinem iPhone gesendet
Am 28.05.2014 um 21:19 schrieb David Grieve david.gri...@oracle.com:
Using styles is preferable to setting the property value. If styles are used,
then you don't have the problem you describe.
An alternative, if styles are not used, is to cast
Jonathan,
Please review https://javafx-jira.kenai.com/browse/RT-37299
Webrev: http://cr.openjdk.java.net/~dgrieve/RT-37299/webrev.00
Jonathan,
If you would please review, https://javafx-jira.kenai.com/browse/RT-37173
Webrev: http://cr.openjdk.java.net/~dgrieve/RT-37173/webrev.00
Please review diff which is entered as a comment in the bug. The diff
changes a MouseEvent handler to update the toolbar state on
mouse-released rather than updating the toolbar state on _every_ mouse
event.
https://javafx-jira.kenai.com/browse/RT-23891
Martin,
Please review the patch attached to
https://javafx-jira.kenai.com/browse/RT-37408.
Jonathan,
Please review the diff added as a comment to
https://javafx-jira.kenai.com/browse/RT-37420.
In 8u20, you can use @import in your .css file. That, along with
Application#setUserAgentStylesheet(String), should do the trick. If I'm
missing something, then please feel free to create a new feature request
in JIRA.
On 6/12/14, 4:57 PM, Robert Krüger wrote:
Hi,
RT-18543 has been closed
I have attached some java files to RT-36510 that are aimed at reducing
the amount of boiler-plate code needed to implement StyleableProperty
and CssMetaData. The code is not complete - it can only create a
StyleablePropertyBoolean right now - but it is sufficiently far along
to warrant a
I am seeking feedback on
http://cr.openjdk.java.net/~dgrieve/RT-36510/webrev.00 which addresses
https://javafx-jira.kenai.com/browse/RT-36510.
This iteration reduces the boiler-plate to one line to create the
StyleableProperty and one method to return the CssMetaData list.
Example use:
Changeset: 6789ab35bb59
Author:David Grievedavid.gri...@oracle.com
Date: 2014-06-24 18:55 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/6789ab35bb59
RT-36510: reduce CssMetaData boilerplate
+ modules/graphics/src/main/java/javafx/css/StyleablePropertyFactory.java
+
Changeset: 796678138fdf
Author:David Grievedavid.gri...@oracle.com
Date: 2014-06-26 15:04 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/796678138fdf
[JAVADOC ONLY] RT-36510: reduce CssMetaData boilerplate
! modules/graphics/src/main/java/javafx/css/CssMetaData.java
!
Changeset: 8d41ccb6bcdb
Author:David Grievedavid.gri...@oracle.com
Date: 2014-06-26 15:47 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/8d41ccb6bcdb
Take public off StyleablePropertyFactory pending further review of RT-36501:
Reduce CssMetaData boilerplate code
!
Have you tried the 8u20 EA release?
This can happen if a node is having CSS applied before the root node of
the scene has had CSS applied. This has been largely resolved in 8u20.
On 6/27/14, 12:19 PM, Jeff Martin wrote:
Jira and the web at large are full of references to this warning (which
looking into it.
jeff
On Jun 27, 2014, at 12:08 PM, David Grieve david.gri...@oracle.com wrote:
Have you tried the 8u20 EA release?
This can happen if a node is having CSS applied before the root node of the
scene has had CSS applied. This has been largely resolved in 8u20.
On 6/27/14, 12:19
Changeset: 588905b8806f
Author:David Grievedavid.gri...@oracle.com
Date: 2014-07-01 14:55 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/588905b8806f
RT-32522: Parser doesn't handle size{1,4} except for -fx-padding
!
Changeset: c8fa5e33e810
Author:David Grievedavid.gri...@oracle.com
Date: 2014-07-09 08:49 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/c8fa5e33e810
RT-37522: TableColumn: default comparator should use Collator for String types
Reviewed by: Jonathan
!
Changeset: 12667ba4eb22
Author:David Grievedavid.gri...@oracle.com
Date: 2014-07-09 17:15 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/12667ba4eb22
RT-37877: ConcurrentModificationException when changing user-agent stylesheets
!
Steve, Kevin -
I'd like for you to review these changes as they affect PlatformImpl.
https://javafx-jira.kenai.com/browse/RT-37551
http://cr.openjdk.java.net/~dgrieve/RT-37551/webrev.00/
http://cr.openjdk.java.net/%7Edgrieve/RT-37551/webrev.00/
Changeset: 779bbf1e9a68
Author:David Grievedavid.gri...@oracle.com
Date: 2014-07-09 20:47 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/779bbf1e9a68
RT-37818: [CSS] Drag triggers NPE at
com.sun.javafx.css.StyleManager.removeStylesheetContainer
!
The latest API for https://javafx-jira.kenai.com/browse/RT-36510 is
posted on http://cr.openjdk.java.net/~dgrieve/RT-36510/webrev.03. Please
see the comments in RT-36510 for details.
Hi Werner,
Please file a bug. I'll have to update the parser to accept 'infinity'
as a value.
On 7/24/14, 1:11 PM, Werner Lehmann wrote:
Hi,
since FX8 we have a styleable property -fx-max-width on Region. I'd
like to use this to replace the FXML attribute
Node maxWidth=Infinity/
with
Changeset: 101968b1eef0
Author:David Grievedavid.gri...@oracle.com
Date: 2014-07-31 14:37 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/101968b1eef0
RT-36510: [CSS] Reduce CssMetaData boilerplate code
!
Changeset: 4b2c53c5ac68
Author:David Grievedavid.gri...@oracle.com
Date: 2014-08-01 10:43 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/4b2c53c5ac68
RT-37787: Sizing fonts with CSS em can result in wrong size font being displayed
!
Changeset: d1aac088a16b
Author:David Grievedavid.gri...@oracle.com
Date: 2014-08-01 12:44 -0400
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/d1aac088a16b
RT-37551: loading user-agent stylesheets one at a time from PlatformImpl is
inefficient
!
I think you are looking for the padding property of Region.
On 8/3/14, 6:07 PM, Pedro Duque Vieira wrote:
Hi,
I miss having a way to define a margin in css or in any other way like with
java code. That is the rectangular white space between a node and the rest,
like w3c css margin property.
Jonathan,
If you could please, review
http://cr.openjdk.java.net/~dgrieve/RT-37454/webrev.00 relative to
https://javafx-jira.kenai.com/browse/RT-37454.
Basically, I override the Node methods in TabPane. In the normal case,
where the control has been skinned, the call to super.lookup will
Kevin, Steve,
Jonathan has reviewed and given his +1 to
https://javafx-jira.kenai.com/browse/RT-37454. I'm seeking your
additional +1. Webrev is
http://cr.openjdk.java.net/~dgrieve/RT-37454/webrev.00
http://cr.openjdk.java.net/%7Edgrieve/RT-37454/webrev.00
Thanks
Steve or Kevin,
I'm seeking your approval for
https://javafx-jira.kenai.com/browse/RT-38065. The change is small. I
pasted the diff in JIRA
https://javafx-jira.kenai.com/browse/RT-27785
On 8/4/14, 5:18 PM, Pedro Duque Vieira wrote:
I should add that margins are often used in web design to make up the
space between elements. I've also find myself wanting to add margins
to nodes in javafx but not found any good way of doing it,
1 - 100 of 201 matches
Mail list logo