From my experience, control is used for multiple row selection, but
shift is more common for multiple column selection.
I've never find an application using this controls, but it's not a
problem.
So what do you think on adding also the Control modifier here to have
the same thing (for consiste
Hi Greg,
>> Usually Shift on selection groups if for range selection, as already done in
>> Pivot Lists, tables, etc ...
>
> From my experience, control is used for multiple row selection, but shift is
> more common for multiple column selection.
I've never find an application using this control
Scott,
Nice work. I have a few comments:
- I suggest that we take an approach similar to how preferred width
and height are bounded in Component. Rather than firing two separate
events for min. and max. width changes, we would fire a single
"columnWidthLimitsChanged(Component component, in
styles are are exposed through a layer of indirection - not
by API. The fact that they're backed by real bean methods would be
something that ideally wouldn't be exposed to callers.
I actually think that the way styles are implemented is fairly
elegant. From the component's perspective, they
> have no problem with this, as Wicket is doing the same thing in reality.
> One
> additional problem for both Pivot and Wicket is that the API is not very
> clear, and in fact many classes are "polluted" by properties and
view/model interaction, and view styles are also APIs, even though the
> m
many classes are "polluted" by properties and view/model
interaction, and
view styles are also APIs, even though the methods are intended to be
hidden. This is the nature of the "accepted approach" and perhaps
not too
much can be done about it.
I'm not sure exactly what you mean by "pollute
many classes are "polluted" by properties and view/model interaction, and
view styles are also APIs, even though the methods are intended to be
hidden. This is the nature of the "accepted approach" and perhaps not too
much can be done about it.
In the long term, I expect a stable 2.0 emerge that
Well, all this is a lot of personal choice.
I'm pretty concious about these things myself, and wouldn't do a 1.0 release
until I feel the APIs are fairly stable from a compatibility point of view.
In a 0.x series you can change as much as you like.
For example, we are currently about to release Qi
Usually Shift on selection groups if for range selection, as already
done in Pivot Lists, tables, etc ...
From my experience, control is used for multiple row selection, but
shift is more common for multiple column selection.
Sorry, really the last question on this ...
what do you think on changing a little the Kitchen Sink demo to
include some null value in some cells ?
And, change one of the data columns for example to have inside only
numbered items like 0..9 repeated, so a sort on multiple columns will
show exactly
Ok, let's see in the future what happen, and if someone ask us to fix
something ...
Bye
Hi, excuse me, a last question on this theme:
is it possible to disable the sort feature (i think yes) ?
And is it possible to have a third status on sort (maybe enabled only
when desired), like ascending, descending, and none (default) ?
Ah,
the range selection (with the Shift key) doesn't work i
Ok.
Sandro
Hi Greg,
I've just seen: great, thanks very much !!
> Yes, you can currently sort on multiple columns. Left-click to sort on any
> single column. Shift-left-click to add another column to the sort. You can
> see an example in the Kitchen Sink demo.
Only one question: in many applications (at lea
It's certainly not a bad idea - just a lot of work :) I'd say let's see if
we get requests from users based on real needs so we don't just invent work
for ourselves. Unless of course you're volunteering to do this, in which
case, feel free to prototype it :)
-T
On Fri, Sep 18, 2009 at 8:12 AM,
In my old web applications (web pages) I had to use TFOOT section of
the table containing data, and make some css tricks to have the fixed
behavior, so if the table
Ok if other RIA toolkits doesn't have, but do you think could be
interesting to explore this feature (could be similar to the Header
someone has tried to see what happens sorting on a column that
contains null values ?
It's up to the comparator to decide how to handle (or if to handle)
null
values, though I do believe that supporting a binary search on a
list with
null values is a TODO in the code.
binarySearch() isn't
Most of the recent (last month) API changes
have been due to working through the tutorials, and as such, I
anticipate
that they'll stabilize a lot once we finish our push to provide better
documentation.
Agreed. We stabilized many APIs for 1.3 as we worked through the
tutorials and document
For what it's worth, I'm
not sure any other toolkit supports such features in scroll panes.
As far as I know, Swing's JScrollPane only supports row and column
headers, same as Pivot's ScrollPane. The WPF ScrollViewer class
doesn't support any kind of headers. Not sure about other toolkits.
Yeah - I've never seen this effect used in a list or tree view before.
So I agree that we should wait on implementing it.
On Sep 18, 2009, at 6:08 AM, Todd Volkert wrote:
TerraTableViewSkin already does this by default, and you can turn it
off via
a style property. We could theoretically s
someone has tried to see what happens sorting on a column that
contains null values ?
Actually, I just reintroduced support for sorting on null values this
morning. I had inadvertently removed it when I moved the class out of
TableView.
And with this change, will it be possible to have th
Feel free to take a look :)
On Fri, Sep 18, 2009 at 7:20 AM, Sandro Martini wrote:
> > The trouble is that until that TODO is done, it will likely throw
> exceptions ;-)
> mhhh not-so-good, sigh ...
>
> Exist a JIRA ticket for this ? Someone is already working on it ?
> If I find some time I coul
You bring up a very valid and good scenario. In such cases, we could choose
to branch from the last release's tag and apply fixes to that [stable]
branch as well, so as to release a 1.3.1 while continuing to work on a 1.4.
I think this methodology would serve us well, though probably only once the
> The trouble is that until that TODO is done, it will likely throw exceptions
> ;-)
mhhh not-so-good, sigh ...
Exist a JIRA ticket for this ? Someone is already working on it ?
If I find some time I could take a look ...
Thanks,
Sandro
Hi,
> My 2c is that thus far, we've been releasing minor versions (1.1, 1.2, etc.)
> every 3-4 months, and that that's about right. It's generally good practice
> in open source to release more often than you do in traditional closed source
> software.
Ok, my experience is mainly on big framewor
>
>
> > It's up to the comparator to decide how to handle (or if to handle) null
> > values, though I do believe that supporting a binary search on a list
> with
> > null values is a TODO in the code.
> Ok, my trouble here is to ensure that no exceptions will be thrown ...
> So what do you think on
Ok, no problem, we can wait if/when a real case will happen ...
My trouble here this was to have more consistency between components.
Bye
Hi Todd,
> It's up to the comparator to decide how to handle (or if to handle) null
> values, though I do believe that supporting a binary search on a list with
> null values is a TODO in the code.
Ok, my trouble here is to ensure that no exceptions will be thrown ...
So what do you think on add s
My 2c is that thus far, we've been releasing minor versions (1.1, 1.2, etc.)
every 3-4 months, and that that's about right. It's generally good practice
in open source to release more often than you do in traditional closed
source software. That would put a 1.4 release tag around early Dec for a
Funny you say that - I actually had a use case for such a thing in an app
that I wrote recently, though I found a different way to go about it that
was much simpler. It'd be up to ScrollPane to provide a column footer and
row footer, which would then mean that instead of providing a corner
compone
TerraTableViewSkin already does this by default, and you can turn it off via
a style property. We could theoretically support it in ListView and
TreeView as well, though I'd think we should wait for real-world use cases
first, since list views and tree views don't tend to be as wide as table
views
> someone has tried to see what happens sorting on a column that
> contains null values ?
>
It's up to the comparator to decide how to handle (or if to handle) null
values, though I do believe that supporting a binary search on a list with
null values is a TODO in the code.
> And with this chang
Hi Greg,
for me it's Ok, but my only trouble is to ensure that this new release
will not be delivered in a short time immediately after the 1.3,
because in this case the general perception could be that the project
is still evolving too fast (and this is true) because it's not enough
mature (and th
Hi to all,
in some applications I've found useful the feature to have fixed (not
scrollable with table data, like header) footers in data tables, for
example a row with total amounts, etc ... very useful in OLAP
applications.
What do you think ?
Bye,
Sandro
Hi to all,
to improve readability in tables, lists, trees and maybe other visual
components, what do you think on add an optional style (by default not
used) to have the zebra effect on rows of tables/grid and to other
components similar, like lists, but with any component with its own
style flag ?
Hi Scott,
welcome in the group ... happy coding.
Ah, thanks for your infos.
Bye
Hi Greg,
someone has tried to see what happens sorting on a column that
contains null values ?
And with this change, will it be possible to have the sort also on
multiple columns (useful in some cases) ?
Or if not, open Ticket in JIRA for this ?
A last thing:
what do you think on adding an optio
37 matches
Mail list logo
