dperez schrieb:
> The parameters aren't documented, as nothing is changed from the superclass
> definition (qx.ui.core.Target#addEventListener and #removeEventListener).
> I suppose, the documentation from a base class must be inherited if missing
> in a derived class.
>
>
> Fabian Jakobs-2 wrote:
The parameters aren't documented, as nothing is changed from the superclass
definition (qx.ui.core.Target#addEventListener and #removeEventListener).
I suppose, the documentation from a base class must be inherited if missing
in a derived class.
Fabian Jakobs-2 wrote:
>
- Some API doc is s
dperez schrieb:
> Done!
> Version 10051 (we have already 5 digit versions!)
> Changes:
> - New event cellContextmenu
> - qx.event.type.CellEvent --> qx.ui.table.pane.CellEvent
>
>
I have seen your changes hitting trunk. Nice work, thanks.
Best Fabian
--
Fabian Jakobs
JavaScript Framework Deve
Done!
Version 10051 (we have already 5 digit versions!)
Changes:
- New event cellContextmenu
- qx.event.type.CellEvent --> qx.ui.table.pane.CellEvent
dperez wrote:
>
>
> Fabian Jakobs-2 wrote:
>>
>>>Great, thank you! Just some minor notes:
>>
>>> - Could you move the event class into the tab
Hi David
> Fabian Jakobs-2 wrote:
>
>>> Great, thank you! Just some minor notes:
>>>
>>> - Could you move the event class into the table namespace? Since it is
>>>
>> only used by the table it would be more natural to put it there.
>>
>> For example to the qx.ui.table.pane.CellEve
Fabian Jakobs-2 wrote:
>
>>Great, thank you! Just some minor notes:
>
>> - Could you move the event class into the table namespace? Since it is
> only used by the table it would be more natural to put it there.
>
> For example to the qx.ui.table.pane.CellEvent?
>
>>- I think a context menu e
dperez schrieb:
> Note: the cellDblclick event replaces the rowdblclick one.
>
>
> dperez wrote:
>
>> I have committed the new events called cellClick and cellDblclick in the
>> 0.7 branch.
>>
Great, thank you! Just some minor notes:
- Could you move the event class into the table namespa
Note: the cellDblclick event replaces the rowdblclick one.
dperez wrote:
>
> I have committed the new events called cellClick and cellDblclick in the
> 0.7 branch.
> If you like it, I'll will port it to the trunk.
> With the current infraestructure, it's easy to create new cell events.
>
>
>
I have committed the new events called cellClick and cellDblclick in the 0.7
branch.
If you like it, I'll will port it to the trunk.
With the current infraestructure, it's easy to create new cell events.
Fabian Jakobs-2 wrote:
>
> dperez schrieb:
>> I also need an event when clicking on a cell,
dperez schrieb:
> This is OK for me.
>
Perfect, I think this is really still a missing feature.
> Fabian Jakobs-2 wrote:
>
>> dperez schrieb:
>>
>>> I also need an event when clicking on a cell, in addition to double
>>> clicking
>>> one.
>>> If appropiate, I offer myself to implement i
This is OK for me.
Fabian Jakobs-2 wrote:
>
> dperez schrieb:
>> I also need an event when clicking on a cell, in addition to double
>> clicking
>> one.
>> If appropiate, I offer myself to implement it.
>>
> I we tackle this now, why don't we implement all click events on cell
> level:
>
>
dperez schrieb:
> I also need an event when clicking on a cell, in addition to double clicking
> one.
> If appropiate, I offer myself to implement it.
>
I we tackle this now, why don't we implement all click events on cell level:
- click
- dblclick
- rightclick/contextmenu
The events should be
I also need an event when clicking on a cell, in addition to double clicking
one.
If appropiate, I offer myself to implement it.
dperez wrote:
>
> I prefer also a click cell event rather than a row event, as the column
> information is sometimes very useful.
>
>
> Fabian Jakobs-2 wrote:
>>
>
westor schrieb:
> Thank you Fabian, Derrell,
>
> this looks pretty good. Also the celleditor is in place, I'm impressed ;-)
> As I noticed, the wrap of long lines now is default behaviour, I can forget
> my wrapping renderer... :-)
>
> Torsten
>
Sorry, I have to disappoint you. We decided to s
Thank you Fabian, Derrell,
this looks pretty good. Also the celleditor is in place, I'm impressed ;-)
As I noticed, the wrap of long lines now is default behaviour, I can forget
my wrapping renderer... :-)
Torsten
Derrell Lipman wrote:
>
> Fabian just checked in changes to Table to use div ta
Fabian, I solved my row order problem, and also the row select in FF works
well, if I use the solution of Dietrich:
this.getSelectionModel().getSelectedRanges()[0].minIndex
But I have still a question regarding the celleditor. Please have a look at
my question "Table DataCellRenderer problem in le
I prefer also a click cell event rather than a row event, as the column
information is sometimes very useful.
Fabian Jakobs-2 wrote:
>
> Yes this would be a good idea and maybe we should fire a "cell double
> click event" instead of a "row double click event" and pass the selected
> row and c
On 9/17/07, westor <[EMAIL PROTECTED]> wrote:
>
> Fabian, I solved my row order problem, and also the row select in FF works
> well, if I use the solution of Dietrich:
> this.getSelectionModel().getSelectedRanges()[0].minIndex
> But I have still a question regarding the celleditor. Please have a lo
Hi Dietrich,
>> Second double click events attached to the table scroller will also be
>> fired if the table header is double clicked. Since the public table API
>> does not provide a clean way to detect double clicks on table rows, I
>> have added a "rowdblclick" event to the table scroller.
>
Fabian Jakobs schrieb:
westor schrieb:
If I'm in the near of Karlsruhe, I will do that :-)
But, it was to early to be satisfied :-/
I havn't looked close enough to see what happens in FF. Normally, if you
perform a doubleclick in a row, a line with the currently selected product
should ope
Thank you Dietrich, for this tip, that seems to work well.
Dietrich Streifert wrote:
>
> Hi Thorsten,
>
> I allways used this to determine the double-clicked row:
>
> var row =
> this.getSelectionModel().getSelectedRanges()[0].minIndex;
>
> Looks a little complicated but may be indep
Hi Thorsten,
I allways used this to determine the double-clicked row:
var row = this.getSelectionModel().getSelectedRanges()[0].minIndex;
Looks a little complicated but may be independent from the focus handling.
And yes ;-) continue posting here. We follow all your steps ;-)
westor s
As suggested, I post my last question here again.
I'm not shure, if I understand well.
To show a product in the iframe, if one performs a doubleclick, I pick up
the Data of invisible column 0.
This is what I do:
table.getPaneScroller(0).addEventListener('dblclick', function()
{
var row = t
Well, Derrell, I'll do this furthermore :-)
Derrell Lipman wrote:
>
> Yup, we are. (Those who aren't can easily press the Delete key.)
> Please keep sending these types of things to the list. That's what
> it's for, and others learn from your discussions.
>
> Derrell
>
> ---
On 9/14/07, westor <[EMAIL PROTECTED]> wrote:
>
> This thread becomes long and longer and I'm not shure if everyone in the list
> is
> interested in all these details.
Yup, we are. (Those who aren't can easily press the Delete key.)
Please keep sending these types of things to the list. That's
Fabian, I have a row hight of 63 and an image hight of 60. But as you
suggested, I tryed to increase the row hight, with the same result.
Regarding the other problems I sent you an email, did you receive? This
thread becomes long and longer and I'm not shure if everyone in the list is
interested i
On 9/14/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
> Derrell Lipman schrieb:
> > On 9/13/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
> >
> >> Regarding the table problem, could you send me the cell renderer
> >> configuration for the image cells?
> >>
> >
> > Fabian, I think you're on the wrong
westor schrieb:
> Hi Fabian,
>
> I increased the row hight, but with no other effect.
> Beyond, the images in my rows are scaled to fit into the cell.
> For my app it would be ok, to deactivate this indicator, is this possible?
> I think I should invite you for a beer, because of your effort ;-)
>
Derrell Lipman schrieb:
> On 9/13/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
>
>> Regarding the table problem, could you send me the cell renderer
>> configuration for the image cells?
>>
>
> Fabian, I think you're on the wrong track. This problem occurs in the
> Table_*.html examples in
westor schrieb:
> If I'm in the near of Karlsruhe, I will do that :-)
>
> But, it was to early to be satisfied :-/
> I havn't looked close enough to see what happens in FF. Normally, if you
> perform a doubleclick in a row, a line with the currently selected product
> should open. That's the way it
Sorting problem seems to be also a position problem: if you doubleclick in
the column head, a product opens too... ;-)
westor wrote:
>
> If I'm in the near of Karlsruhe, I will do that :-)
>
> But, it was to early to be satisfied :-/
> I havn't looked close enough to see what happens in FF. No
If I'm in the near of Karlsruhe, I will do that :-)
But, it was to early to be satisfied :-/
I havn't looked close enough to see what happens in FF. Normally, if you
perform a doubleclick in a row, a line with the currently selected product
should open. That's the way it runs in IE. Not so in FF.
On 9/13/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
> Regarding the table problem, could you send me the cell renderer
> configuration for the image cells?
Fabian, I think you're on the wrong track. This problem occurs in the
Table_*.html examples in demobrowser, with no images involved.
Cheers
Hi Torsten,
> Hi Fabian,
>
> I increased the row hight, but with no other effect.
> Beyond, the images in my rows are scaled to fit into the cell.
> For my app it would be ok, to deactivate this indicator, is this possible?
> I think I should invite you for a beer, because of your effort ;-)
>
W
Hi Fabian,
I increased the row hight, but with no other effect.
Beyond, the images in my rows are scaled to fit into the cell.
For my app it would be ok, to deactivate this indicator, is this possible?
I think I should invite you for a beer, because of your effort ;-)
Fabian Jakobs-2 wrote:
>
Derrell Lipman schrieb:
> On 9/12/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
>
>> westor schrieb:
>>
>>> Hi Fabian,
>>>
>>> I tested it, and select of table row works fine now for both browsers. But
>>> in FF you still have the box at the wrong place, I will attach a gif,
>>> showing the
On 9/12/07, Fabian Jakobs <[EMAIL PROTECTED]> wrote:
> westor schrieb:
> > Hi Fabian,
> >
> > I tested it, and select of table row works fine now for both browsers. But
> > in FF you still have the box at the wrong place, I will attach a gif,
> > showing the problem. I don't know if these attachmen
westor schrieb:
> Hi Fabian,
>
> I tested it, and select of table row works fine now for both browsers. But
> in FF you still have the box at the wrong place, I will attach a gif,
> showing the problem. I don't know if these attachments are going to the
> list, but you should see ist in nabble.
>
>
Hi Fabian,
I tested it, and select of table row works fine now for both browsers. But
in FF you still have the box at the wrong place, I will attach a gif,
showing the problem. I don't know if these attachments are going to the
list, but you should see ist in nabble.
Best Torsten
http://www.nab
westor schrieb:
> Hi Fabian,
>
> thanks for your investigation.
> I tryed the branch version, and it workes really better then the release
> version. But not perfect. My experience:
> Comboboxes are ok in both, IE6 and FF.
> But: Table row selection works not correct in both browsers. In the releas
No page scrolling is the 1st use I've done with qooxdoo.
But now, I also use it for adding popup menus to HTML reports, and normally
a lot of vertical scrolling is needed. It's not easy to convert such HTML
reports to a 100% qooxdoo solution.
The goals of 0.8 are good news.
Sebastian Werner wr
Hi Fabian,
thanks for your investigation.
I tryed the branch version, and it workes really better then the release
version. But not perfect. My experience:
Comboboxes are ok in both, IE6 and FF.
But: Table row selection works not correct in both browsers. In the release
version this was already o
Hi Torsten,
I have finally decided to backport the location stuff to legacy 0.7 and
fixed the scrolling issues already solved in trunk. I was able to cut
down the dependencies down so it was pretty easy to backport. Please try
your app with the legacy_0_7_x branch.
Best Fabian
> Hmmm I thi
Hmmm I think, there are a lot of people who want to use qoxxdoo also on a
normal webpage, like me. I think this is one of the most importend features
to become an alternative to the use flash, java-applets (they are already
dead, I think) or ather JS-frameworks.
I for myself think about to ma
westor schrieb:
> Hmmm I think, there are a lot of people who want to use qoxxdoo also on a
> normal webpage, like me. I think this is one of the most importend features
> to become an alternative to the use flash, java-applets (they are already
> dead, I think) or ather JS-frameworks.
I think
> I was able to fix those issues with this new functionality in the
> trunk. To fix it in the legacy 0.7 branch we may have to backport
> some classes but I am not sure about the required dependencies.
So how long until 0.8 comes out? Westor, can you wait?
Hugh
Hugh Gibson schrieb:
>> Another issue: The combobox popup opens at wrong place, if you
>> scroll the
>> browser. This error occures in both browsers, IE and FF. Sorry for
>> beeing
>> late with this, I saw it now.
>>
>
> That's pretty dramatic, and will probably be due to the coordinate syst
> Another issue: The combobox popup opens at wrong place, if you
> scroll the
> browser. This error occures in both browsers, IE and FF. Sorry for
> beeing
> late with this, I saw it now.
That's pretty dramatic, and will probably be due to the coordinate system
not being normalised. See my other
Another issue: The combobox popup opens at wrong place, if you scroll the
browser. This error occures in both browsers, IE and FF. Sorry for beeing
late with this, I saw it now.
Hugh Gibson wrote:
>
>> Firefox:
>> If you scroll the browser (not the table widget), the selected row
>> is not th
49 matches
Mail list logo
