hi

i looked at my calendar and saw that the first beta would be better around the 
19th of april because our easter-hollidays begin at the 11th. that would 
offer a possibllity to get kexi in a even better state before it's first 
public release. 9 days of 24 hour programming... well that could be very 
usefull :)

think about it, maybe it isn't importent too much...

cu
lucijan

On Sunday 12 January 2003 18:41, Lucijan Busch wrote:
> On Sunday 12 January 2003 17:33, Nicolas Goutte wrote:
> > The problem is that the main application (KWord, KPresenter, KSpread)
> > need early feedback, especially on font problems. It does not mean that
> > everything needs to be ready.
> >
> > And if KOffice is in rather bad state at that time, we can always call it
> > KOffice 1.3. Alpha 1. ;-)
>
> well alpha would sound better for me, but ther won't be that much testers
> :)
>
> > Have a nice day/evening/night!
> >
> > On Sunday 12 January 2003 16:43, Lucijan Busch wrote:
> > > 11th of april isn't that a bit early for beta 1?
> > > well anyway one final thing, pleas write Kexi and not KExi...
> > >
> > > thank you
> > > lucijan
> > >
> > > On Sunday 12 January 2003 15:08, Lucijan Busch wrote:
> > > > On Sunday 12 January 2003 13:29, Lukáš Tinkl wrote:
> > > > hello
> > > >
> > > > > Hello dear KOffice developers,
> > > > > another year went by, and I feel like it's about time for thinking
> > > > > about another major KOffice release ;)
> > > >
> > > > uhm, what does thinking mean? ;)
> > > >
> > > > > I just posted a first and very preliminary schedule for the
> > > > > upcoming version of KOffice (1.3) which is available at, as
> > > > > usually, at
> > > > > http://developer.kde.org/development-versions/koffice-1.3-release-p
> > > > >la n. ht ml
> > > >
> > > > it isn't synced by now, are there already any dates on it, if yes,
> > > > when do you plan the feature-freeze?
> > > >
> > > > > I'd like to ask the specific maintainers to go through this list
> > > > > and review mainly these points:
> > > > > - add new features for your app when you think they're are worth
> > > > > mentioning and if you are sure this will indeed appear in the final
> > > > > version - cry out if the schedule is too tight, we have still
> > > > > enough time to change it
> > > >
> > > > i will cry after i see the dates ;)
> > > >
> > > > > :-)
> > > > >
> > > > > - please add entries for new/improved filters (Nicholas?)
> > > > > - please take some time and update the webpage for your
> > > > > application; take some great screenshots, update the information
> > > > > about current version, features, maintainers etc (most stuff is
> > > > > _really_ outdated!!!)
> > > > >
> > > > > What could be the major goals of this version[1]?
> > > > > - get more and better looking templates (this is a must IMHO)
> > > > > - new icons? (I've heard the artists are making some new crystal
> > > > > icons exclusively for KOffice)
> > > > > - incorporate/finish Krita/Karbon, make sure they work consistently
> > > > > with the rest of apps (drag'n'drop, copy&paste, etc.)
> > > > > - find a _real_ maintainer for Kivio
> > > > >
> > > > > Since I have little idea about the graphic apps we have, I'd
> > > > > appreciate some status info about the current state of Krita,
> > > > > Karbon and Kontour (and also KExi). If an app lacks an active
> > > > > maintainer and is unfinished/broken, it will get moved to
> > > > > kdenonbeta (seems to be the case for Kontour or KoSoap).
> > > >
> > > > kexi... it isn't in a real usible state by now but depends on how
> > > > much time we have, we could get it for the first release. we only
> > > > spent time cleaning the old source and not implementing/finishing
> > > > features. in my case a working kexi should at least have:
> > > > 1. working cql driver & cql-embedding
> > > > (cql == the native sql-engine shipped with kexi)
> > > > 2. working queries
> > > > 3. working tablealtering / table creating
> > > > 4. formbindings (eventually QSA bindings)
> > > > 5. and i don't know how the progress is with jowenn's report designer
> > > >
> > > > if i look at my list i see that most things (except QSA-bindings) are
> > > > already existing but not fully usible.
> > > > point 1 should be done quite fast. point 2 too. point 3 also (at
> > > > least the most-needed things, saving and SQL=>GUI-parsing has to be
> > > > implemented) i'm working hard on point 4 (saving will be some work
> > > > since we want it QUI-compatible), hm... QSA i don't know will be
> > > > implemented after all other points are done.
> > > > i can ask joseph for the 5th point
> > > >
> > > > > Last but not least, I'd like to thank David Faure for having been a
> > > > > wonderful maintainer of the past few KOffice versions. I hope I'll
> > > > > manage to pull some tasks off his back so he can concentrate on
> > > > > more interesting (and
> > > > > important[2]) things, thanks David!
> > > >
> > > > thank you :)
> > > >
> > > > > Thanks for your attention, keep the mails coming :)
> > > > >
> > > > > [1] Subject for discussion
> > > > > [2] Like hyphenation; hint, hint :-)
> > > >
> > > > _______________________________________________
> > > > koffice-devel mailing list
> > > > koffice-devel@mail.kde.org
> > > > http://mail.kde.org/mailman/listinfo/koffice-devel
> > >
> > > _______________________________________________
> > > koffice-devel mailing list
> > > koffice-devel@mail.kde.org
> > > http://mail.kde.org/mailman/listinfo/koffice-devel
> >
> > _______________________________________________
> > koffice-devel mailing list
> > koffice-devel@mail.kde.org
> > http://mail.kde.org/mailman/listinfo/koffice-devel
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel