Ktable has one weakness: it doesn't look like a native table.
(Especially on platforms other than windows)
For some projects this may be a problem, for others it simply doesnt matter.

> Hi,
>
> I am currently writing a new SWT application with lot's of tables.
>
> Now, which one to use? Who is using KTable? Why? WShat is the futur of KTable?
>
> The KTable model idea is a good one for me. When i select a cell i get the object related to it easily and i can display the info. When you look at the samples it looks great.
>
> Thanks
>
> JMi

As a rule, use SWT widgets as much as possible!
This has many benefits in the long term.

Regards.

"jmi" <jmidelsaux@skynet.be> wrote in message
news:27975769.1130502206902.JavaMail.root@cp1.javalobby.org...
> Hi,
>
> I am currently writing a new SWT application with lot's of tables.
>
> Now, which one to use? Who is using KTable? Why? WShat is the futur of
> KTable?
>
> The KTable model idea is a good one for me. When i select a cell i get the
> object related to it easily and i can display the info. When you look at
> the samples it looks great.
>
> Thanks
>
> JMi

Ktable will never look native on every platform - as long as you don't
write specific cellrenderers that emulate every platform (which probably
is out of question).

On the other hand, being a custom control and not forcing any look
allows it to be used in many cases that differ from normal table
usecases but need a grid control anyway. For an example see the color
picker example.

I have an application that extensively uses tables as main controls for
user interaction - and at first I tried a SWT table based solution (in a
prototype). But I made the experience that overcoming restrictions of
the native table control (and there are many!) is really horrible and in
many cases practically impossible.

regards,
Lorenz

Yves Harms wrote:
> Ktable has one weakness: it doesn't look like a native table.
> (Especially on platforms other than windows)
> For some projects this may be a problem, for others it simply doesnt
> matter.
>
>> Hi,
>>
>> I am currently writing a new SWT application with lot's of tables.
>>
>> Now, which one to use? Who is using KTable? Why? WShat is the futur
>> of KTable?
>>
>> The KTable model idea is a good one for me. When i select a cell i get
>> the object related to it easily and i can display the info. When you
>> look at the samples it looks great.
>>
>> Thanks
>>
>> JMi

Generally there is no point to use KTable as long as you can cope with the
standard SWT table restrictions. Arguably, using KTable is more work as
compared to the typical table/table viewer setup but it gives you
significantly more freedom in terms of what you can do with it.

--Vlad.

"jmi" <jmidelsaux@skynet.be> wrote in message
news:27975769.1130502206902.JavaMail.root@cp1.javalobby.org...
> Hi,
>
> I am currently writing a new SWT application with lot's of tables.
>
> Now, which one to use? Who is using KTable? Why? WShat is the futur of
KTable?
>
> The KTable model idea is a good one for me. When i select a cell i get the
object related to it easily and i can display the info. When you look at
the samples it looks great.
>
> Thanks
>
> JMi