Hello sir,
I don't know where to put my questions so just write it here.
I 'm uning pivot in my test applications since I like it very much.
for now there are something really troubles me .
1) are there a XSD or DTD for wtkx file, I really can't get clear that what
elements and attribu
I based my suggestion on my usage of the Netbeans Form Editor
(Matisse), where I typically specify a "+1" or "+2" font to make a
heading label stand out.
But yeah, percentage would probably make more sense.
On Mon, Oct 5, 2009 at 21:29, Greg Brown wrote:
> That is doable, though those values wou
Howdy Hi,
What issue type do I use to submit a patch?
Thanks,
Scott.
Hi all,
Just a minor update to the JSON font encoding email I sent out
earlier. It didn't really make sense to support the JSON encoding for
arbitrary fonts, since they can be more efficiently represented using
the existing Font.decode() syntax. It also didn't make sense to use
the JSON e
I don't feel particularly strongly about this either way, so that
seems fine to me.
On Oct 5, 2009, at 6:09 PM, Todd Volkert wrote:
What's weird in this case is that width can be -1 or relative, which
isn't
its real width (the same is not true for a component's width). I'd
vote
that we ca
What's weird in this case is that width can be -1 or relative, which isn't
its real width (the same is not true for a component's width). I'd vote
that we call the limits minimumWidth and maximumWidth, but I'm fine with
allowing the width to exist outside the limits, and it's up to the skin to
rec
No, width would still be "width", in the same way that a component has
a preferred size and an actual size.
On Oct 5, 2009, at 5:58 PM, Scott Lanham wrote:
If the width limits were preferred would the width also need to be
called
preferred?
Project wide consistency is not my domain so I am
If the width limits were preferred would the width also need to be called
preferred?
Project wide consistency is not my domain so I am happy to go with whatever
you guys decide :-)
On Tue, 6 Oct 2009 05:42:58 am Greg Brown wrote:
> I think it actually may be OK to skip the bounds checking in th
I think it actually may be OK to skip the bounds checking in this case
as well as in Component:
1) In Component, we're currently validating an explicitly set
preferred dimension against its limits. However, there is no real need
to do this, because getPreferredSize() does it automatically:
That is doable, though those values would have to be specified as
strings, since "size:+1" isn't valid JSON. But that is OK, since that
makes it easier to handle those cases. If size is a number, it is
handled as a point size. Otherwise, if it is a string and begins with
"+" or "-", we can
Hi
Since font sizing is also generally part of the theme, is would be
nice to be able to specify
styles="font:{size:+1}"
or
styles="font:{size:120%}"
so that no knowledge of the theme's settings is necessary.
Regards, Noel.
On Mon, Oct 5, 2009 at 19:56, Greg Brown wrote:
> Hi all,
>
> I
Hi all,
I have just finished making a change that provides much more
flexibility in customizing the appearance of text-based components.
Instead of the "fontBold", "fontItalic", and "fontSize" styles that
were previously limited to the Label skin, you can now use a new JSON-
based encoding
[
https://issues.apache.org/jira/browse/PIVOT-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Volkert resolved PIVOT-303.
Resolution: Fixed
> Add DisabledCheckmarkFilter to TreeView and ListView
> -
[
https://issues.apache.org/jira/browse/PIVOT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Volkert resolved PIVOT-305.
Resolution: Fixed
> Renderers should be passed index/path
> -
>
Add new font setters to text-based skin classes that allow a caller to
customize the theme font
---
Key: PIVOT-312
URL: https://issues.apache.org/jira/browse/PIVOT-312
* We should probably throw if the column is fixed-width and outside
the
limits (both in setWidth() and in setWidthLimits()). This check
obviously
wouldn't apply to relative and default width columns.
I agree that we should throw in setWidth(), but I'm not sure we can do
that in setWidthLi
[
https://issues.apache.org/jira/browse/PIVOT-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Volkert resolved PIVOT-295.
Resolution: Fixed
> Add hit detection to drawing primitives
> --
Scott,
This looks great! Only a few comments, most of them coding-style nitpicks.
* We should probably throw if the column is fixed-width and outside the
limits (both in setWidth() and in setWidthLimits()). This check obviously
wouldn't apply to relative and default width columns.
* [style nit
[
https://issues.apache.org/jira/browse/PIVOT-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762151#action_12762151
]
Todd Volkert commented on PIVOT-311:
Actually, this happens even if you move back over t
Exception in Mouse.release when released outside the display host's bounds
--
Key: PIVOT-311
URL: https://issues.apache.org/jira/browse/PIVOT-311
Project: Pivot
Issue Ty
20 matches
Mail list logo
