I hope it has support for chemical reaction schemes (nice arrows for chemical equilibria et al).

Another thing missing for a scientific office desktop is a bibliography management system. Something like pybib or endnote that can get references directly from web sources, such as http://www.pubmed.org.

I heard, some time ago, there was a project on an application of this type but it's been so long since i heard anything from it...

This project looks awesome. I've been looking for a GOOD front-end to popular databases. Does anyone know if if will be able to connect to remote databases or if it will be limited to those on the local machine?

did you only check out the screenshots on kexi's homepage? they are a bit old, i'll need to update them. well i have to admit that it is still in a early stage, but hopefully we get it working till koffice's release.
btw, i'd never start with kexi if rekalm wouldn't be dead, but it is :(

however i would be very happy if you could post me whishes about it's features and it's priority. if i will get some feedbacks like that i know where to set priorities

how is rekall dead? that's a great shame. the idea in principle is great.

and sorry to pour scorn on your app. i just had a look at the feature list, and it doesn't look like much more than a direct database editor at the moment. i couldn't let someone who doesn't understand databases use it.

I don't use MS Office, but a friend showed me some of the (albeit UGLY) cross-office VB scripting he can do to generate pretty forms, spreadsheets, graphs, word docs and presentations from a database. if KOffice, and specifically a db forms frontend for it offered that sort of scripting with python, ruby, java etc - it would be getting somewhere new and useful.

Rekall is alive and well and actively developed, a new release is in beta3 right now, we have plug ins for IBM's DB2 as well as for ODBC coming out in the next week and Oracle is coming along nicely. Rekall is running as a KDE native app, or a Qt app on both Linux and Windows. A Mac OS X port will be coming either with the 1.1.1 release coming next week or the 2.0 release in a month.

The Rekall dataaccess engine is also being leveraged into some of our other products. And if you missed it, Rekall is also available on the Sharp Zaurus as tkcRekall.

oh, yes it exists :) last time i took a look it seemd like beeing dead, anyway i think the userinterface is a bit hard to work with and not intuitive. well i like some ideas which i am considering of including into kexi (no metter if it already happens in it's first version :)
but so far as i see the licence isn't really the one which should be taken for including into koffice ;)
wasn't it gpl before? anyway, now i see i should update the discribtion and make some new screenshots. btw. kexi will be/is definitly more than just another mysql frontend (i hope so), we got gui queries working and forms are already going into the right direction psn will fix table creation and for scripting we think about taking QSA which shoudn't be very hard to implement. however i hope that doesn't sound like a message against rekall.

Rekall - dead - never. I have just uploaded Rekall V2.3.2 beta1 for the Mac to our web site. As far as features are concern we add quite a lot of new stuff. For example, we have added a new set of Wizards which generate "starter" applications, a web interface, which allows you to publish your application to a web server, drivers for SQLite, Sybase/MS SQL Server, and Informix and much more. For more information, please visit http://www.totalrekall.co.uk or http://www.rekallrevealed.org

KOffice is such a fantastic effort, I think this small but able team deserves three cheers for partaking on such a ambitious but very needed project. I have in front of me now a stack of StarOffice 6 books, that I'm planning on using to train my staff of 30+ on soon, so I know SO pretty well. As good as it may be (and it has come a long way), nothing beats the look, feel, and integration of a native KDE office suite. Just as KHTML defeated Gecko on the MacOS X desktop, KOffice will grow to be a strong contender in the UNIX desktop world. A universal document format (based on the StarOffice XML formats) will help to get us there.

Kivio is rewritten for the KOffice architecture and there is (again) talk about a Dia stencil importer.
About project planner, there is no competition to MrProject. KPlato is still stuck in the design phase.

According to the release plan -- http://developer.kde.org/development-versions/kde-3.1-release-plan.html -- we will get the decision about KDE 3.1 final on Monday January 13th, 2003. I don't such a decision anywhere (and yes, after comments the last time I posted this, I *have* searched the mailing lists). The last thing I can find is the release coordinator saying that he liked the look of RC7 (which also isn't mentioned in the release plan).

Well, then they did/do need a few more days time to get everything in place and to build the packages.I don't see any problems with that. If you do not want to wait any longer i would go and grab the sources via cvs.

it's great to see that development on suite is going on and still not dead,
because the best desktop still needs it's own native best office suite.

There are 2 things that still worry me for making sure that one day this suite
will be the best one:

1. The raster drawing app. What happened with krita (formerly krayon), seems
that this one will never be released?

2. OpenOffice integration. As we know openoffice.org is mature suite and very
widespread one, however until kde has at least like it or even better one we
could use it's success and knowhow in order to promote the kde native office
suite. I am talking about integration as making koffice kparts for the various
openoffice components (not just embeding them but even making them to use kde's
menu and toolbar system, and may be even more to use the native kde/qt
widgets). This will at least help in the beginning for former
MS/Star/OpenOffice users to convert, and those components could be finally
replaced when koffice has mature and stable ones (I think that kword is good
examlpe).
Such of integration can probably consinst in folowing stages:
2.1 plugger kpart integration (or xkpart whatever) - the easyest way to embed
whatever xapp
2.2 make integrated openoffice kparts to use kde's menu and toolbar system
2.3 start replacing basic widgets (scrolls, panels, buttons, ..) with kde/qt
widgets in order to reflect to users' configuration settings of look and feel
and at least to have kde look and feel
2.4 make this components to support koffice native file formats
2.5 replace core classes with kde foundation classes (may be before this point
is reached kde will have it's own mature and stable office components, because
you guess it could be very ugly such of refactoring)

I would even CONTRIBUTE if koffice opens it's openoffice.org integration
subproject, what is important in the begining is to check the LGPL license that
sun composed because as I read in their faq there are some limitations.

Is there anybody who is aware with their license, is this really possible and
is there planned same/similar koffice subproject.

I agree. I would fully support OOo being ported to Qt, but porting that project to any new toolkit is simply not feasible. It's a project of over 6 million lines of code. It's not impossible, but it's more work than it's worth, apparently.

> I would even CONTRIBUTE if koffice opens it's openoffice.org integration
> subproject, what is important in the begining is to check the LGPL license that
> Sun composed because as I read in their faq there are some limitations.

Well, you can help here: import and export filters from/to OpenOffice.org are already under work (in KOffice CVS) and will become part of KOffice 1.3. As for the licence issue: you are not right, please read again http://www.openoffice.org/license.html, we are compatible.

> Well, you can help here: import and export filters from/to OpenOffice.org are
> already under work (in KOffice CVS) and will become part of KOffice 1.3. As
> for the licence issue: you are not right, please read again
> http://www.openoffice.org/license.html, we are compatible.

well, that's not exactly what I wanted to say, I think that koffice kpart of openoffice components would be the fastest way to bring industry standart working functionality for koffice. However the step of compatibility is important and part of both strategies (1st strategy - port openoffice comps to kde, 2nd stratrgy making koffice comps to support openoffice formats). It seems that in both cases i really need to research how compatible are the native document object models of both projects.

I can start with kword - openoffice writer, now can someone tell me how to get the fresh cvs of openoffice and koffice working with my kdevelop ide?

And also another question, formerly i read in the dot something about kxpart or xkpart which was intended to turn every xapp to kpart, is there anyone that can tell me how it works?

Whooohooo, Kexi, finally a lightweight database
like Access. This was badly needed. Perhaps
it could import/export mdb's one day? There is some OS-project
about that going on (cant rememeber the address
right now, though).
KWord definitely needs better RTF import/export.
I could live without DOC-export but without good
RTF export there's no way to get my documents
"out" to our clients. RTF is complicated but text-based
and documented so there's hope.
I hope Krita's eventually getting somewhere.
The Gimp is one of the worst UI-sins which
has remained on my desktop. I hardly use
it though, but Photoshop 5.5 on Wine which
runs OK but has got some bugs or PhotoPaint 9
which has a horribly slow file open/save dialog.
Something with Gimp functions but without
1000s of windows spread all over my desktop.
Everybody asks me why I don't use the GIMP.
Isn't there anybody else out there who finds
the UI of this app horrible?
Well, big thanks anyway for all those KDE/Koffice developers
have achieved so far - a user-friendly OpenSource desktop.

Have you thought about using libgda (look for it under the GNOME Office materials) for the backend library connecting to the various databases? libgda is interface agnostic; so it should be easy to put up a QT/KDE frontend.

Advantages to using libgda:
*It's actively maintained by the GNOME people and the Ximian Mono people.

*It's front-end agnostic. libgda does not use a GTK/GNOME front-end (that's what libgnomedb is for).

*More cooperation between KDE and GNOME.

Disadvantages:
*libgda is written in C using GLib. OOP C may not seem elegant to a C++ programmer, but it works and can be easily called from C++. Other programs in KDE link to GLib, I've heard, so this might not be so bad.

*libgda is not a native KDE library. Therefore, it might not fit in to the overarching KDE scheme.

*[I'm probably missing a few more here.]

At any rate, give libgda a look if you haven't already. It's shaping up quite nicely and can provide a good general method of accessing different database systems. It's also nice to see more code-sharing between the two desktop projects. Either way, good luck with your application!

Well it's pretty easy to wrap GObject code into C++, the gtkmm people do that all the time, there are automated tools for it. They produce pretty good bindings, though they aren't based on Qt (for instance they use std::string instead of QString etc).

what makes a database a "real" database to you? i think you're thinking of RDBMS, which would still include access as it implements the R, the DB, and the MS. a text file can be a database, but the user has to be the R, and MS.

now if you start throwing in ACID test, then you start throwing out lots of competition. if you need redundancy built in for 99.999% uptime, the you're throwing out lots of others. you're left with oracle maybe one or two others.

Go KOffice! If I could only get nice support for my printers, but that's another project all together (Lexmark Z53, and Lexmark 4039).

Here is one !! I too agree that the Gimp is a UI headache. I do a great deal graphics design, for the web mostly (using MM Fireworks MX) and also some print graphics (have used Corel PhotoPaint 8) however I intend to persevere with the Gimp.

Although the UI really desperately needs a whole rethink and redesign no one can ignore the immense power of the beast, it is awesome.

Hmm, is Kexi just a standalone application or are KWord and Kalc (or whatever it's called) able to actually make use of it. In OpenOffice.org, it's possible to call up a DataSources slider. Create a query, create a document which has 'fields' and have OpenOffice.org fill in your document. This is still a tad buggy, and only works with adabas or ODBC, but if it'd work more correctly I'd love it for pretty invoice generation!

Oh yes! I agree with you completely. I have often asked myself when the GIMP developers are going to revamp their interface. No matter what distro or theme you use, it #1 looks ugly, and #2 is highly unintuitive. They could do MUCH better. If any GIMP developer reads this, I mean this as constructive criticism; you are free to email me with questions.

Since a while I'm trying to find out if open source will meet my needs for my small office. Today I was looking for an alternative for Acces,for Linux of course, and I found Kexi. Wow. I use simple databases:
.tables and relations between them,
.forms to fill them,
.queries to make summaries,
.forms to display them,
.and a menu to work with it.
Acces gives me just enough tools to make and use them, and I hope Kexi will give me the same. I'm not a big programmar, but what I saw on the screenshots gives me hope. Thanks a lot. I'm looking forward to it.

Still missing the feature in KChart that would allow to put
the "X-Axis" data in one column and "Y-Axis" data in another,
then make some "quasi-scientific" plots (a'la gnuplot). I'd love
to have the possibility to embed the kchart plots instead of
embeding the graphics prepared using other tools.

I hope opening foreign documents in KSpread will work in this release. Opening Corel Quattro Pro documents in KOffice 1.2.1 would only make KSpread crash. A bug on this was already reported. Also, Corel Presentations shows should be incorporated in this release as well since Not everyone uses MS PowerPoint. Support for Lotus SmartSuite and Sun StarOffice documents should be considered as well since Lotus is the other major competitor to MS Office and StarOffice is the most popular office suite for Linux at this moment. A database component for KOffice might be useful as well.

KDE and KOffice are remarkable. Sure the various programs need to be developed a lot more, but that will happen. KOffice has immense potential. Look to WordPerfect for some ideas on how to improve KWord - look at the features in WordPerfect that are way ahead of MS Word: reveal codes; delay codes; find and replace codes; dynamic property bar; etc. Likewise with Quattro Pro and Presentations. KOffice is only up to version 1.3 and is already remarkable. You are doing what massive corporations have refused to do. Don't ever give up!!!! Everything you do is appreciated by an increasing community of users!!

KDE and KOffice are remarkable. Sure the various programs need to be developed a lot more, but that will happen. KOffice has immense potential. Look to WordPerfect for some ideas on how to improve KWord - look at the features in WordPerfect that are way ahead of MS Word: reveal codes; delay codes; find and replace codes; dynamic property bar; etc. Likewise with Quattro Pro and Presentations. KOffice is only up to version 1.3 and is already remarkable. You are doing what massive corporations have refused to do. Don't ever give up!!!! Everything you do is appreciated by an increasing community of users!!

Citation tools, like those found in Endnotes and Oberon's Citation etc, would be extrememly useful in KWord and would set it apart from programs like WordPerfect and MSWord. Now that Kexi is integrated into the KOffice suite, can it be the database for such a feature? An integrated citation tool as well as the usual indexing and table of contents/figures/authorities etc tools would be fabulous.