Re[2]: gnue-forms grid implementation using wx.grid

Hello Reinhard,

wx.grid creates NO controlls untill editing started. It uses
renderers to paint cells. After editing started every type of edit
control will be reused.

wx.grid asks it's model about only values visible in scroll window. So
it is possible to fetch only rows shown on screen.

Howewer grid tries to repaint while scrolling. It strenuously asks
model about [not very essential] values while user moves scrollbar.

-- 
Best regards,
 Oleg                            mailto:[email protected]



    ----- Original Message -----
    From: Reinhard Mueller <[email protected]>
    To: [email protected]
    Date: Tuesday, July 10, 2007, 9:34:06 PM
    Subject: [GNUe] gnue-forms grid implementation using wx.grid

RM> Am Montag, den 09.07.2007, 20:34 +0300 schrieb Oleg Noga:
>> What prompted gnue-forms developers to implement the home-maid grid
>> for wx26 uidriver while wxPython has wx.grid?

RM> The main point was this: A wx.grid needs all columns in memory at once,
RM> while our home-made grid control only has the controls you see on the
RM> screen.

RM> So if you query a database with a million of records, of which you
RM> display 5 at a time, our home-made grid will create 5 UI controls, while
RM> wx.grid would create a million UI controls.

RM> Thanks,
RM> Reinhard