Data aware KDE widgets in dataKiosk

Hey, ruurd, I was going to post this as a comment, but blogger's login crap was giving me problems. Anyway, I have several data aware KDE widgets in DataKiosk I hope to introduce into KDElibs with KDE4. They include some widgets that DataKiosk shares with KDEPIM and some that are entirely new to KDE including one that mimics the MS Access Relation Combo. They are written to be generic enough to use for any QSql driver.

If you want to have a go at them before the KDE4 timeline ( or if you want to start the port early ) feel free. The widget I'd most like to see in KDELibs is the multi-column KComboBox derivative I created as a foreign key relation editor. It comes with completion courtesy of KCompletionBox, but it employs a couple of hacks to overcome deficiencies in the API that should be solved for KDE4. You could also look into making the entire DataTable class ( which is derived from QTabWidget and features custom QDataTable, QDataBrowser tabs that work with eachother ) into a standalone KDE widget if there is interest.

Here is the pic of the multi-column KComboBox derivative embedded in the DataTable widget.

Comments generic data backends. For the most part I was referring to including some advanced widgets like the multi-column combo ( with _completion_ for those to lazy to actually read *cough* *cough* ) that are not tied to QtSQL. And a couple of widgets that I share with KDEPIM.

I realized half way through that ruurd is talking more about K versions of QDataTable and QDataBrowser and the like and so I suggested dataKiosk's DataTable which actually is tied to QtSQL.

And you have it exactly right about dataKiosk not being another MS Access ripoff *cough* *cough*. It is a juK ripoff if anything.

It's hard for me to imagine expanding dataKiosk beyond SQL without first having a clue what you mean by more generic data backend :)

By Adam Treat at Sat, 05/14/2005 - 15:24

I have been trying to get my head around the model view stuff in Qt4. Granted it smells of over engineering, and writing code for the sake of using someones GOF book, but it might pay off.

What I am thinking is a set of widgets setup to provide views for models, and models for things like DOMs, csv files etc. Then the developer only has to provide the control logic and a layout on the screen. I have a quasi working model for a gdbm database that seems to have promise. Either way, its something I think warrents some understanding.

By Ian Reinhart Geiser at Sun, 05/15/2005 - 01:44