[litwindow-users] Re: wxListCtrl and library status

[Hajo K. <mai...@ha...>]

Hi Joel,

thanks for your comments.

I am using the library myself for contract-based work I am doing for a 
client. It greatly reduces the time for anything related to data 
exchange between widgets and struct/class. Adding new properties to a 
settings dialog for example is very easy and works well. My project also 
contains a couple of interdependencies - buttons that need to be enabled 
only in certain situations, dynamic window captions etc... and I am 
using the library for that.

My approach is currently to use a mix of both. I use the library 
whenever possible and fall back to more traditional methods elsewhere, 
simply because I don't have the time to enhance the library at the 
moment. But the development is still very much alive, if quiet.

Now for your questions:

 > I understand that the RapidUI code will be streamlined in the future, 
but as
 > the entire package stands now is it well-behaved enough to use in a real
 > project (even if it might require some immature syntax)?
 >
 >
I would say yes. I use it in a commercial project. And if you need help 
with the syntax, just ask. I am happy to help out and also discuss any 
ideas with you.

 > My UI design requires a multicolumn wxListCtrl.  I was looking at
 > base_objects.* in lwwx and started to add wxListCtrl by modeling changes
 > after the support for wxListBox.  Am I duplicating existing efforts?
 >
 >
No. I haven't yet startet with wxListCtrl.

 > My first thought is that the number of columns in the listctrl should be
 > determined by the number of elements in the associated structure, but 
I am
 > not sure if this fits your conception.  Also, I have not dug deep 
enough to
 > see how to walk though the elements of a structure.
 >
 >
It fits perfectly. Additionally I'd also add a filter property, which 
would simply be string containing a ',' separated list of members 
(names) to omit.

 > I have been wavering between wanting to jump in using the Lit Window 
library
 > and deciding I should do it the traditional approach one more time.
 >
 >
Like I said, you could do both. Use the library if possible, fall back 
to the traditional approach elsewhere. Works fine for me. And if you 
contribute some of your work - wxListCtrl for example - you'll ensure 
that the library will continue to grow.

My current projects are a graphical user interface for a custom made 
hardware device and Version 2 of my bug tracking tool 'BugLister'.

BTW, are you using the version from the installer or did you check out 
the latest sources from sourceforge? The sources haven't changed much 
since last december, but contain a few bugfixes and documentation 
enhancements.

Best regards

Hajo