MessageType.Question Doesn't Offer the User a 'Cancel' Button
-
Key: PIVOT-676
URL: https://issues.apache.org/jira/browse/PIVOT-676
Project: Pivot
Issue Type: Bug
Affects Versio
[
https://issues.apache.org/jira/browse/PIVOT-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936144#action_12936144
]
ocean commented on PIVOT-675:
-
Hey Greg. Not sure what you mean by self-contained. Note that I'v
Hi all,
All of the remaining issues for the 2.0 release have been resolved, and new
binaries, demos, and tutorials have been posted:
http://ixnay.biz/pivot-2.0/
http://ixnay.biz/pivot-demos/
http://ixnay.biz/pivot-tutorials/
http://ixnay.biz/pivot-jfree-demos/charts_demo.html
If you are current
[
https://issues.apache.org/jira/browse/PIVOT-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-569.
--
Resolution: Fixed
Resolved for TreeView.
> Make ListView selectedItem, etc. notifying properties
> ---
[
https://issues.apache.org/jira/browse/PIVOT-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-548.
--
Resolution: Fixed
Resolved for TreeView.
> Fire selection change events when selection changes indirec
[
https://issues.apache.org/jira/browse/PIVOT-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-672.
--
Resolution: Fixed
> Add a StringSerializer
> --
>
> Key: PIVOT-672
>
[
https://issues.apache.org/jira/browse/PIVOT-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-369.
--
Resolution: Fixed
Resolved for TreeView.
> Unable to easily drag multiple selected items in ListView
>
[
https://issues.apache.org/jira/browse/PIVOT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-557.
--
Resolution: Fixed
> Pivot javadoc artifacts for Maven
> -
>
>
I just checked in an update to JSONSerializer that improves support for
deserializing typed lists and maps. The following approaches are now supported:
- Parameterized property of Java bean class; e.g. public ArrayList
getFooList() {...}
- TypeLiteral
- Subclass of concrete generic sequence or
> Yes - the "missing" features are pretty accurately described in the JIRA
ticket. ;-) As for Todd's time - can't say for sure, but hopefully he will
be able to resolve it soon.
Very good, but in the meantime I can try the same to look at it ... could be
useful (at least for me to learn how thi
No, I don't see this warning.
On Nov 26, 2010, at 8:59 AM, Sandro Martini wrote:
>
>> I have not seen this error. The demos and tutorials should either be using
> all signed or all unsigned JARs, so I'm not sure what might be causing it.
> Can you try to narrow it down?
> Ok, in next days I'll s
Yes - the "missing" features are pretty accurately described in the JIRA
ticket. ;-) As for Todd's time - can't say for sure, but hopefully he will be
able to resolve it soon.
On Nov 26, 2010, at 8:55 AM, Sandro Martini wrote:
>
>> I actually don't think we should release 2.0 until those tic
> I have not seen this error. The demos and tutorials should either be using
all signed or all unsigned JARs, so I'm not sure what might be causing it.
Can you try to narrow it down?
Ok, in next days I'll start to look at it, but is one thing that needs many
investigations (and time), but for user
> I actually don't think we should release 2.0 until those tickets are
resolved. We'd be releasing a major version with known inconsistencies
between major components, which is not good.
I agree with you, absolutely ... but do you know if Todd has time to work on
this ?
Or at least are we able to
> Important: running Tutorials I always get a (very annoying) Startup dialog
> from Java, asking me if block the Applet (default Yes = block), because it
> contains a mix of signed and unsigned code ... do you see this ?
I have not seen this error. The demos and tutorials should either be using al
I actually don't think we should release 2.0 until those tickets are resolved.
We'd be releasing a major version with known inconsistencies between major
components, which is not good.
On Nov 26, 2010, at 4:43 AM, Sandro Martini wrote:
>
> Hi Greg,
>
>> Those tickets have been resolved for so
Hi Greg,
> Those tickets have been resolved for some components but not yet TreeView.
> Ideally, they should be resolved for TreeView as well before we release
> 2.0.
Yes, so in the worst case maybe we could split them and keep for the 2.1 all
parts still not solved.
> You are welcome to take
17 matches
Mail list logo
