[VK] Newsletter #1

[VisKProg t. <te...@vi...>]

Dear VisKProg developer,
Dear VisKProg user,

VK version 0.1.9 will be out soon, and yet nearly nobody really knows about
the things, that have changed since the previous version. So I thought, it
could be nice to send (from time to time) a newsletter over our discussion
list, to keep you up-to-date. Therefore you now received the first issue
of our "VisKProg newsletter"; please tell me if you like this idea, or whether
you think that such newsletters are just a waste of time (for you to read and
for me to write) - if most of you think so, I'll immediately break with that
new manner...

Now, enjoy it...
THE VisKProg TEAM
(Chris)

######################## VOLUME 1 ########################
I) VK 0.1.9 release
II) CVS access for everyone and daily CVS tar-balls
III) KDE1 or KDE2 ?

I) Next VisKProg release 0.1.9
  =======================
         After a long break (nearly all team members, including me, had not
         so much time during a looooong period) we plan to release v0.1.9
         the next weekend (at least I hope so).
         The version focuses on bug fixes, but there are also a lot of
         improvements, among them a lot of new function calls, a
         new "project manager", which is written in VisKProg,
         as a replacement for the "project management HTML front-end",
         and - last but not least - full syntax checking support in the
         source code editor.
         Maybe, we'll also have basic menu bar support, at least with
         a File/Quit menu and a complete help menu. But this is
         only sensible, if Topi finishes his documentation generator in
         time. For that tool isn't integrated in the CVS tree, yet we
         may possibly fail to get it in before the release.

         Unfortunately many people had problems to compile the
         0.1.8-IDE package, due to some warnings that turned into
         errors on some machines. I hope, that we have fixed these problems,
         but it still would be a great help, if you could test the actual
         CVS snapshot...

II) CVS access and daily VK tar-balls at Source-Forge
   =========================================

         As you may know, VisKProg also has a project site at Source-Forge,
         a great service for freeware projects. There, we also have our own
         CVS tree...
         If you want to check out the latest development snapshot of VK
         from the CVS, enter
cvs -d:pserver:ano...@cv...:/cvsroot/viskprog login
         (when asked for a password, just press enter!)
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/viskprog
	co .
         (<-one line. First cd into the directory, where you want the CVS to
         be stored on your local computer)

         For if you don't want to use CVS, or if don't have it installed on
         your system, you may also download the daily tar-ball, generated
         from the CVS:
http://cvs.sourceforge.net/cvstarballs/viskprog-cvsroot.tar.gz

         Most of the bug fixes and many improvements of version 0.1.9
         are already avaible there. And you can help making VisKProg
         better: just compile your CVS snapshot and tell us, whether it
         worked - or simply tell us your wishes for future versions.

III) KDE: 1.x versus 2pre
    =================

         I'm sure you've already heard about the upcoming new
         (and really great) KDE version 2. And of the incompatibility
         between KDE 1.x and KDE 2.0...
         The VisKProg-generated programs are not really concerned by
         this version step, for VisKProg is flexible enough to "export"
         it's projects to several environments (KDE2 will probably be
         supported in v0.1.10).
         But our VisKProg IDE (i.e. the source code editor and KWinEdit)
         must decide, which version to support. They can either work
         with KDE2 or with KDE1.x, not with both. I know that most people
         still are using KDE1.x but on the other hand, VisKProg 0.1.9
         will probably be the last version that will be released before
         the final KDE 2.0 release. And so, if we continue to make
         the VisKProg IDE KDE1-software, it is already obsolete when
         we release it... We may either port the VK IDE to KDE2, directly
         after releasing v0.1.9, or we may still wait and still release
         a (stable) v0.2.0 before switching to KDE2.
         I really don't know, how to proceed - so please discuss the
         pros and cons with me, then we could make our decision together :-)
         WE REALLY _NEED_ YOUR (USER-) FEEDBACK AT THIS POINT
         (it doesn't help at all if we decide to go with KDE2 and then nobody
         uses the new IDE)

Visit the VisKProg web site http://www.viskprog.org !
You are always welcome to contact the VisKProg team <te...@vi...>.