[prev in list] [next in list] [prev in thread] [next in thread]
List: kc-kde
Subject: [kc-kde] issue #21 for proofing.
From: "Aaron J. Seigo" <aseigo () mountlinux ! com>
Date: 2001-08-30 23:30:24
[Download RAW message or body]
hi
if you could look this over, glean for errors, i'll send it out to Zack
tomorrow (at the latest)
--
Aaron Seigo
["kde20010824_21.html" (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN" \
"http://www.w3.org/TR/REC-html40/frameset.dtd"> <HTML><HEAD><TITLE> Kernel Cousin \
KDE</TITLE></HEAD> <BODY TEXT="black" BGCOLOR="#ffffff">
<table border="0" cellspacing="0">
<tr><td colspan="2" bgcolor="#cccccc" valign="top"> </td></tr>
<tr><td bgcolor="#cccccc" valign="top">
<table border="0">
<tr><td><font size="-1"><a href="index.html">Kernel Cousins Home</a></font></td></tr>
<tr><td><font size="-1"><a href="people.html">Indices</a></font></td></tr>
<tr><td><font size="-1"> <a \
href="apache/index.html">Apache</a></font></td></tr> <tr><td><font \
size="-1"> <a href="apache/latest.html">Latest</a> \
</font></td></tr>
</table></td>
<td>
<blockquote>
<h1 align="center">Kernel Cousin KDE #21 For 24 Aug</h1>
<h2 align="center">By <a href="mailto:aseigo@mountlinux.com">Aaron J. Seigo</a></h2>
<strong>Table Of Contents</strong>
<p>
<ul>
<li><a href="kde20010824_21.html#0">Introduction</a>
<li><strong>Threads Covered</strong>
<table border=0>
<tr><td><b>1</b>.</td><td>7 Aug - 11 Aug</td><td>(6 posts)</td><td><a \
href="#1">Touch Typing and Other Educational Apps</a></td></tr> \
<tr><td><b>2</b>.</td><td>8 Aug - 9 Aug</td><td>(7 posts)</td><td><a \
href="#2">Cookbook and kdeapps?</a></td></tr> \
<tr><td><b>3</b>.</td><td>10 Aug - 11 Aug</td><td>(13 \
posts)</td><td><a href="#3">Support For Large Files</a></td></tr> \
<tr><td><b>4</b>.</td><td>11 Jan 1904 - 16 Aug</td><td>(6 \
posts)</td><td><a href="#4">Kompare Moves Into Main CVS</a></td></tr> \
<tr><td><b>5</b>.</td><td>10 Aug - 14 Aug</td><td>(20 \
posts)</td><td><a href="#5">The Evolution of KNode and KMail</a></td></tr> \
<tr><td><b>6</b>.</td><td>12 Aug - 17 Aug</td><td>(7 posts)</td><td><a \
href="#6">EMail Templates in KMail</a></td></tr> \
<tr><td><b>7</b>.</td><td>14 Aug - 20 Aug</td><td>(15 \
posts)</td><td><a href="#7">KWinTV Sees Active Development</a></td></tr> \
<tr><td><b>8</b>.</td><td>15 Aug - 16 Aug</td><td>(4 posts)</td><td><a \
href="#8">Advanced Web Shortcuts Now In CVS</a></td></tr> \
<tr><td><b>9</b>.</td><td>21 Aug</td><td>(7 posts)</td><td><a href="#9">New KDE \
Website: enterprise.kde.org</a></td></tr> \
<tr><td><b>10</b>.</td><td>21 Aug</td><td>(6 posts)</td><td><a href="#10">S/MIME \
Support for KDE3</a></td></tr> <tr><td><b>11</b>.</td><td>22 Aug - \
23 Aug</td><td>(1 posts)</td><td><a href="#11">Plugins For the \
KMenu</a></td></tr> <tr><td><b>12</b>.</td><td>23 Aug</td><td>(1 \
posts)</td><td><a href="#12">Breaking Binary Compatibility on Fridays</a></td></tr> \
<tr><td><b>13</b>.</td><td>23 Aug</td><td>(1 posts)</td><td><a \
href="#13">KRegExpEditor: Graphical Regular Expressions</a></td></tr> \
<tr><td><b>14</b>.</td><td>23 Aug</td><td>(1 posts)</td><td><a href="#14">EMail \
List for KDE3 Users</a></td></tr>
</table>
</ul>
<p>
<strong><a name="0">Introduction</a></strong>
<p>
<p>Welcome to KC KDE! This week's installment celebrates the fantastic pace of the \
work being done on KDE3. The move to Qt3 is an important transition for KDE, despite \
the temporary pain it may bring. The next several months will see breakages
in compiling and in functionality that are inevitable during such a wide-scale \
porting effort. Binary compatibility breakages will be committed to CVS each Friday, \
potentially requiring a rebuild of much if not all of the KDE source tree. It also \
means that those wishing to develop or test the bleeding edge will need to install \
the latest Qt3 beta (or use the copy in the qt-copy KDE CVS module). While it is \
possible to keep a copy of both a stable release and a development version of KDE on \
the same machine (which many KDE developers already do), the challenges presented are \
not small ones for many would-be participants.</p>
<p>To make KDE3 as good as it can be, developers and testers are required. So,
why should one decide to take the plunge and live in the potentially chaotic world of \
KDE3 development that will exist for the next few months? Besides helping KDE to \
become the greatest desktop environment available, those around during this time will \
be able to see and use all of the new and improved capabilities in KDE3 months before \
the rest of the world gets to enjoy it. This issue of KC KDE highlights several of \
the developments that have occurred over just the past 2 weeks in KDE's head CVS \
branch. It is by no means a complete study of every current development nor does it \
cover those features that are still in the planning stages, but hopefully this issue \
can provide an exciting insight into the development of KDE3.</p>
<p>We hope you enjoy this issue and (as always) Happy Hacking!</p>
<p>
<h1>1. <a name="1">Touch Typing and Other Educational Apps</a></h1>
<b>7 Aug - 11 Aug (6 posts): <a \
href="http://lists.kde.org/?l=kde-devel&m=99722880515361&w=2">Moving KTouch</a></b>
<p>
<p>Where do you go when you want a selection of educationally oriented
applications for KDE? Perhaps <a href="apps.kde.com">apps.kde.com</a>,
or <a href="http://freshmeat.net">freshmeat.net</a>. Many are probably not aware
of the relatively new kdeedu package that is housed in KDE's CVS repository. kdeedu \
is a relatively small small package housing only three applications, the most recent \
addition to which is KTouch.</p>
<p>KTouch developer Haavard Froeiland said, <b><font color="#880000">"KTouch is a \
small education application for learning to touch type. I would like to move it from \
kdenonbeta to one of the packages being released. It would be nice to have it in kde, \
since there is many people out there who want to learn to touch type, and especially \
for schools installing kde. <a \
href="http://ktouch.sourceforge.net/">http://ktouch.sourceforge.net/</a>"</font></b></p>
<p>Waldo Bastian replied saying, <b><font color="#880000">"Seems like an excelent \
candidate for the recently created module "kdeedu". There is also a special \
mailinglist for educational issues in the form of kde-edu@kde.org."</font></b></p>
<p>Hopefully more educational applications will be imported over time into kdeedu to
make it as rich a resource for KDE users as the other packages are.</p>
<h1>2. <a name="2">Cookbook and kdeapps?</a></h1>
<b>8 Aug - 9 Aug (7 posts): <a \
href="http://lists.kde.org/?l=kde-devel&m=99728895729665&w=2">kde-apps (or whatever) \
and Cookbook</a></b>
<p>
<p>Here is the scenario: a developer has been working slavishly on their new KDE
application masterpiece. Needing a place to house it during development, they have \
put it in the kdenonbeta module. The time eventually arrives for it to graduate from \
the land of half-finished programs into a proper place in CVS. If the program in \
question fits neatly into one of the existing modules, this isn't a problem. But what \
of the numerous applications that don't really fit well into the any of the core \
categories? One such application is David Watson's Cookbook, a promising KDE recipe \
application. After some discussion as to what to do with Cookbook, David wrote, \
<b><font color="#880000">"There has been quite a bit of discussion as to what will be \
done with my poor little unwanted program ;), and it sounds like most people are in \
favor of the creation of a new kde-apps (or kde-misc, or kde-foobarbaz) - so is this
actually going to happen? It would be nice if I weren't just left hanging like this - \
the suspense is killing me. :) Not really in such a hurry, just want to know what's \
going to happen..."</font></b></p>
<p>George Staikos unwittingly summed up the situation, saying, <b><font \
color="#880000">"It seems like there can be no strong correlation between these \
applications that would be in the new package. Why not just package these things \
separately? I don't want to have to install KVirtualBarbieCollector in order to get \
KCookBook. I see a difference between a collection of small screen toys (kdetoys) \
and full apps. I'm not saying that I don't want to see KCookBook or other apps \
distributed with KDE though. I'm actually quite curious about KCookBook. I'm just \
saying that it might be better to allow fine-grained installation of these apps. As \
an alternative, they could, I guess, be put into a single module and then hopefully \
have the packagers make separate packages for each app inside."</font></b> Stephan \
Kulow replied, <b><font color="#880000">"That's actually _exactly_ what kde-apps is \
supposed to be - just a place different to kdenonbeta for apps to be in \
CVS."</font></b></p>
<p>To date such a cvs module has yet to be added though it seems
likely to occur as more and more applications are being built within KDE's CVS.</p>
<h1>3. <a name="3">Support For Large Files</a></h1>
<b>10 Aug - 11 Aug (13 posts): <a \
href="http://lists.kde.org/?l=kde-core-devel&m=99747126228803&w=2">Fwd: Re: 64 bit \
file support</a></b>
<p>
<p>As 64-bit operating systems become more common, support for large files becomes
important for the desktops that run on them. Lack of support for large files is a \
known limitation in KDE2 which will be addressed in KDE3, as Waldo Bastian said in an \
email to the kde-core-devel list, <b><font color="#880000">"One of the things todo \
for KDE 3.0 is to get 64-bit file support working. You might want to read the \
following URL in order to understand the problem. <a \
href="http://ftp.sas.com/standards/large.file/x_open.20Mar96.html"> \
http://ftp.sas.com/standards/large.file/x_open.20Mar96.html</a> It seems that since \
we can't control the way in which either Qt, other libs or applications are being \
compiled we will need to use the "Transitional Extensions".
I haven't tried it yet but I hope that we can circumvent this define mess
that Jeff talks about. I'm sure that after all the problems with X-headers
the glibc-developers wouldn't be that stupid.
As far as KDE's internal interfaces goes, I think that we should start to use
"long long" in the interfaces that need it. Maybe we can add a
KIO::filesize_t typedef so that we have a central place to change it to
something else."</font></b></p>
<p>Waldo later replied to himself saying, <b><font color="#880000">"The solution to \
this seems to be to define _LARGEFILE_SOURCE and _LARGEFILE64_SOURCE and to leave \
_FILE_OFFSET_BITS undefined. You should then be able to use stat64() and other 64-bit \
versions of the stdio functions. The normal functions remain 32-bit then. That also \
means that you have to use "struct stat64" instead of "struct \
stat"."</font></b> Then in reply to that message, Waldo posted a patch that \
provided a starting for large file suppor.</p>
<h1>4. <a name="4">Kompare Moves Into Main CVS</a></h1>
<b>11 Jan 1904 - 16 Aug (6 posts): <a \
href="http://lists.kde.org/?l=kde-core-devel&m=99789877019992&w=2">Moving and \
renaming kdiff</a></b>
<p>
<p>KDiff has been moving steadily towards completions during its incubation in \
kdenonbeta. The moment finally arrived to move it into one of the main CVS modules \
this week as John Firebaugh announced:</p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>I'd like to move kdiff from kdenonbeta to kdeutils and rename it to kompare
at the same time. Thanks to Dre for the name suggestion. Unless there are any
objections, could someone with access please make the move on the server?
</p></font></b>
</blockquote>
<p>It was recommended that it be moved to the kdesdk module instead, which is where \
it is slated to be moved.</p>
<h1>5. <a name="5">The Evolution of KNode and KMail</a></h1>
<b>10 Aug - 14 Aug (20 posts): <a \
href="http://lists.kde.org/?l=kmail&m=99744085616452&w=2">[RFC] Kmail to use \
Knode message classes and proposed schedule for</a></b>
<p>
<p>KNode and KMail have many cosmetic and functional similarities since they both
handle text based messaging. Each of them has a message composer, message threading, \
support for attachments, encryption capabilities, hierarchical views, etc. Many have \
wondered just how many of these common components (and therefore development effort) \
could be shared between the two projects. As it turns out the answer is, "quite \
a lot". KDE3 will see a merging of many of the capabilities and components of \
the two applications, as Marc Mutz outlined in an email cross posted to both the \
KMail and KNode development lists, saying:</p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>The Knode developers and Marc Mutz (from Kmail) have come to an
agreement on how to merge the message handling of the two projects.
This will be the first step on the road at whose end Kmail and Knode
are only frontends to a common library and the creation of a
"KMessenger" superset of both to rival Outlook will be possible. We
think that there is a consensus on both sides that this is the way to
go.
</p><p>We now want to lay out the schedule for this first part (with time
frames intentionally left out of the picture):
<ol>
<li>Outsource KNode classes into libkdenetwork (splitting up KNArticle
into a Knode-specific and a generic part).</li>
<li>Rename classes under a KMime:: namespace and port to Qt3.</li>
<li>Optimize the classes for both memory usage and RFC compliance.</li>
<li>Rewrite KMMessage / KNArticle as wrappers around KMime::Message
(defining a common load/store interface for on-demand loading of
message parts - some KMime::LoadHelper or such).</li>
<li>Create a transparent encryption/decryption
(multipart/{encrypted,signed}) interface for bodyparts based on Ian's
work on KGpgMe (codename:-) and George's S/MIME classes.</li>
</ol>
[now ready for release]
<ol start="6">
<li>Move Knode/Kmail semantics over to KMime and consolidate.</li>
<li>Merge reader classes (actually, rewrite them to become a KPart and
maybe use QTextBrowser for mails that don't contain HTML themselves
(should be much faster)).</li>
<li>Merge Composers and make them use QTextEdit, so that we can create
text/html (ugh. :-) and text/enriched mails.</li>
</ol>
[in the future:]
<ol start="9">
<li>Merge the message list classes.
<li>Merge the rest (esp. folder handling).</li>
</ol>
</p><p>Though this proposal seems like "Knode takes over Kmail" (or---as
Christian Thurner has put it: "We are KNode of Borg. You will be
assimilated. Resistance is futile" :-), this is not so. We use the MIME
framework of Knode as a basis, because it's technically sound and
Kmail's isn't, but the outcome of the merge will look quite different
from current Knode. What with the reader and composer; they will need
quite a bit of work for the port to QTextEdit and it's not decided in
any way from which side (Kmail/Knode) we start there.
</p></font></b>
</blockquote>
<p>Regarding the message class sharing Don Sanders replied, <b><font \
color="#880000">"initially the API of KMMessage shouldn't change, only the \
implementation. This way the new KMMessage can be tested for correctness.
Then the KMMessage API should be extended with load
on-demand of message parts and I think more importantly
methods for treating the entire message, message body and
each message part as a stream. Then KMail can be ported
over to using these streaming methods and finally
KMMessage::asString and the like can be removed completely.
Treating message parts as streams should allow large
messages to be handled efficiently memory wise (speed is
not so important)."</font></b> Marc agreed that this is exactly how it should be \
done. </p>
<p>The discussion progressed to cover advanced encryption handling,
gpg integration, cooperation with PIM applications and kparts usage. KNode
and KMail will probably both come out of this looking and feeling different than they \
did in KDE2 to the general improvement of both applications.</p>
<h1>6. <a name="6">EMail Templates in KMail</a></h1>
<b>12 Aug - 17 Aug (7 posts): <a \
href="http://lists.kde.org/?l=kmail&m=99777948730075&w=2">Patch: templates for kmail \
(Bug #1015)</a></b>
<p>
<p>Word processors, spread sheets, presentation packages and HTML editors all
come with support for template documents, so why not do the same for EMail programs?
Florian Weber posted such a patch for KMail saying, <b><font color="#880000">"Well, \
my guests left early, so here is the first (incomplete) draft for mail \
templates."</font></b> Florian went on to list what the patch already accomplished \
and what was left to do.</p>
<p>Ingo Klöcker questioned the wisdom of letting any mail folder become a template
folder, as Florian's patch allowed. Florian explained his thoughts on the matter \
saying, <b><font color="#880000">"I was thinking about those people who would like to \
have multiple template folders. In my experience, users often like to sort their
mails/templates/whatever by projects. This is made impossible by a single,
system-wide template folder.
I agree that most home users will (probably) use a single template folder. In
an enterprise environment however, splitting things up can be an absolute
neccessity."</font></b></p>
<h1>7. <a name="7">KWinTV Sees Active Development</a></h1>
<b>14 Aug - 20 Aug (15 posts): <a \
href="http://lists.kde.org/?l=kde-devel&m=99782032808463&w=2">KWinTV</a></b>
<p>
<p>What do you do when you discover that a certain program you rely on isn't being \
maintained anymore? If you are George Staikos you take it as a call to arms and \
correct the situation. With a desire to see KWinTV working properly, George posted to \
the main devel list saying, </p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>This is a note to inform you that I have received no feedback from the
KWinTV author and he doesn't seem to have done any work on it since November,
so I am starting to maintain it myself in KDE CVS. It's in rather rough
shape right now, but it does work and I have fixed many bugs already. I have
also applied a patch by Stefan Hellwig which makes the channel scanner work
and implements a brand new channel file format.
</p><p>Things are stable enough for me right now, but I can find ways to crash it
still, and some things just aren't being done in a nice way. Ideally it
could use a complete rewrite since it was originally based on KDE 1.x but I
just don't have time for that. So for now, I'm just going to plug away at my
TODO list which I have added to the app in CVS. You can find it under
kdenonbeta/kwintv. This is not in the main build because it doesn't use the
KDE build system yet. I'm not a pro at that, so it will take a while to
merge it. For now I will continue to make releases fairly frequently at
<a href="http://www.staikos.on.ca/~staikos/kwintv/">http://www.staikos.on.ca/~staikos/kwintv/</a>.
</p></font></b>
</blockquote>
<p>George also put out a call to others who use the application to send in
patches, fixes for the build scripts, icons, documentation, etc. Almost immediately
KWinTV was put into shape with an inspiring number of commits to CVS over the next \
several days. The users of KWinTV are no doubt happy that this program is once again \
moving in the right direction.</p>
<h1>8. <a name="8">Advanced Web Shortcuts Now In CVS</a></h1>
<b>15 Aug - 16 Aug (4 posts): <a \
href="http://lists.kde.org/?l=kfm-devel&m=99790060427067&w=2">Can I put my advanced \
web shortcuts into CVS?</a></b>
<p>
<p>Andreas Hochsteger's development efforts on extending Konqueror's web shortcuts
to support multiple search terms and flexible insertion patterns
occurred during the KDE2.2 feature freeze and therefore did not make it into that
release. With that freeze lifted Andreas asked, <b><font color="#880000">"I just got \
my own CVS write account from Stephan, so are there any objections, which will \
prevent me from commiting my changes into the HEAD branch? FYI: I've posted several \
patches, some time ago and the functionality has been extended and matured much since \
that time."</font></b> Andreas was given the green light and his patch was committed \
to CVS for testing and exploration.</p>
<h1>9. <a name="9">New KDE Website: enterprise.kde.org</a></h1>
<b>21 Aug (7 posts): <a \
href="http://lists.kde.org/?l=kde-devel&m=99839290925293&w=2">enterprise.kde.org</a></b>
<p>
<p>Jonathan "Jono" Bacon has been busy with the KDE usability
project, but that hasn't stopped him from taking on other projects as well. Jonathan
announced the availability of a new KDE website saying, </p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>I just thought I would let you know that <a \
href="http://enterprise.kde.org">enterprise.kde.org</a> has gone live today. :-)
</p><p>I am going to be concentrating on pushing KDE as a solid platform for
application development and system integration for the enterprise.
</p><p>The site went live today with it's basic functionality, and a few bugs
;-P, but I will be aiming for the following features:
<ul>
<li>Database driven business case addition and viewing</li>
<li>Research into business usage of KDE and type of usage</li>
<li>Information on companies that support KDE (eg, support, training etc)</li>
<li>Articles on KDE and the enterprise, and business usage</li>
</ul>
There is also a mailing list - kde-enterprise. All are welcome to join.
> -)
</p></font></b>
</blockquote>
<p>As a further insight into his plans for <a \
href="http://enterprise.kde.org">enterprise.kde.org</a>, Jonathan said:</p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>I am going to be starting work this week on the
following on the site:
<ul>
<li>Building a business case submissions engine for
businesses to share positive experiences with KDE.
<li>To begin a Focus portion of the site to do
interviews with businesses that successfully use KDE.</li>
</ul>
If you could ask all those people who use KDE at work
to get in touch with me that would be great, and
anyone who has made a presentation with slides on KDE
and the enterprise is welcome to put their slides on
the site.
</p></font></b>
</blockquote>
<h1>10. <a name="10">S/MIME Support for KDE3</a></h1>
<b>21 Aug (6 posts): <a \
href="http://lists.kde.org/?l=kmail&m=99838369228851&w=2">S/MIME for KDE 3.0</a></b>
<p>
<p>The mail facilities in KDE may not have all the visual frills one might find \
elsewhere, but it is hard not to respect the ever increasing range of capabilities
provided. With each release KMail has become more flexible and capable without losing
its stability or clean interface. All is not done, however. One ability that is being \
asked for frequently these days is S/MIME support. A new face appeared in the KMail
landscape when Jörg Beermann wrote, <b><font color="#880000">"I´m realy intressted in \
PKIX stuff and want to join the development of such an S/MIME class for KDE. So let \
me know if I´m welcome :)"</font></b> George Staikos replied, <b><font \
color="#880000">"You certainly are. As you know, I've been doing the certificate \
code, and I have the template here to write the OpenSSL backend support. What I most \
need help with is defining the interface needed in KMail, and implementing the code \
in KMail once the KSSL stuff is usable."</font></b> Jörg's reply to this was:
<b><font color="#880000">"helping to define the Interface for KMail seems to be a \
nice task. By the way, I´m a little bit experienced in S/MIME and x.509v3 stuff
so maybe I could be a good help for you.
I have worked with OpenSSL as well to implement an S/MIME solution,
the Library is realy great, but without documentation its a realy ugly \
job"</font></b></p>
<p>Technical discussion on the implementation details ensued between Jörg, George and \
Marc Mutz. Work on the KMime library has begun and significant functionality has \
already been achieved.</p>
<h1>11. <a name="11">Plugins For the KMenu</a></h1>
<b>22 Aug - 23 Aug (1 posts): <a \
href="http://lists.kde.org/?l=kde-core-devel&m=99848862723574&w=2">Kicker \
extension</a></b>
<p>
<p>First, Michael Goffioul wanted a good printing system in KDE so he wrote KPrint.
Once that was done he needed a way to configure those printers
so he wrote a KControl module and a services extension for Konqueror. Then he wanted
printers to show up dynamically in the KMenu. To accomplish this Michael implemented
a means to dynamically extend the KMenu at runtime. Describing the latest place his \
quest for printing nirvana has led him, Michael said:
<blockquote>
<b><font color="#880000">
<p>
</p><p>Following an idea I had, I implemented an dynamic extension mechanism to
kicker. Basically, this mechanism allows to add menu entries to the K-menu
using dynamically loaded libraries (kind of plugins). I applied it to the
integration of kdeprint into kicker and you can see the result here:
<a href="http://users.swing.be/kdeprint/kicker_ext.png">http://users.swing.be/kdeprint/kicker_ext.png</a>
(note: when you select a printer, the job viewer is started with that printer).
</p><p>Technically:
<ul>
<li>defined a PanelXMenu class that inherits PanelMenu</li>
<li>added 2 virtual functions "pixmap()" and "title()" that are \
used when inserting the entry into the K-menu</li>
<li>modified k_mnu.cpp to read the "Extensions" key from the config
file (in "menus" group), to know which extensions need to be loaded,
then load the extensions and add the menu entry</li>
<li>you can also think about associating those dynamic menus with
PanelPopupButton to add specialized buttons to the panel (not done
however).</li>
</p><p>This allows to build tools like "quickbrowser" except that it is \
dynamically loaded.
</p></font></b>
</blockquote>
<p>Joseph Wenninger responded saying, <b><font color="#880000">"it sounds like \
something I would have needed some time ago, but hadn't the time to implement it.
Why does it need to be in kdeui ? It is only usefull for kicker, isn't it \
?"</font></b> Michael agreed and refactored the code to make it cleaner and put it \
into the kicker library. He posted his final results saying,
<blockquote>
<b><font color="#880000">
<p>
I completed the previous code to be able to add this dynamic menu also
as a button into the panel (with a popup menu). Now it's working OK.
You can see all the results here:
<ul>
<li><a href="http://users.swing.be/kdeprint/kicker_ext1.png">http://users.swing.be/kdeprint/kicker_ext1.png</a> \
: menu extension</li> <li><a \
href="http://users.swing.be/kdeprint/kicker_ext2.png">http://users.swing.be/kdeprint/kicker_ext2.png</a> \
: add extension</li> <li><a \
href="http://users.swing.be/kdeprint/kicker_ext3.png">http://users.swing.be/kdeprint/kicker_ext3.png</a> \
: panel extension</li> </ul>
</p></font></b>
</blockquote>
</p>
<h1>12. <a name="12">Breaking Binary Compatibility on Fridays</a></h1>
<b>23 Aug (1 posts): <a \
href="http://lists.kde.org/?l=kde-core-devel&m=99855163930967&w=2">reminder: CVS HEAD \
/ BIC day</a></b>
<p>
<p>Binary incompatible changes to libraries, which require the apps that use those
components to be recompiled, can be frustrating and take up valuable time. However,
With some coordination the annoyance can be kept to a minimum.
To that end KDE3's release maintainer Dirk Mueller announced:</p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>due to popular request I'd like to ask everyone to schedule binary
incompatible changes in kdelibs to one day per week, that is Fridays.
</p><p>If somebody has no time to commit binary incompatible changes on such a
friday for whatever reason then please mail the patch with a commit
log to me and I'll commit it for you.
</p></font></b>
</blockquote>
<h1>13. <a name="13">KRegExpEditor: Graphical Regular Expressions</a></h1>
<b>23 Aug (1 posts): <a \
href="http://lists.kde.org/?l=kde-core-devel&m=99857810425321&w=2">Announcement: \
KRegExpEditor now available in kdelibs/kdesupport</a></b>
<p>
<p>A year and a half of hacking by Jesper K. Pedersen has resulted in the
KRegExpEditor, which is now part of the kdeutils package. Jesper explained
what KRegExpEditor was, saying:</p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>The last 1 1/2 year I've been working on a graphical editor for regular
expression. Finally I got it complete enough so that it is useful in
applications.
</p><p>What is KRegExpEditor
</p><p>=====================
</p><p>KRegExpEditor is basicly just a widget. A large one however. The widgets
resemble quite a lot a drawing tool.
</p><p>From a programmers point of view this is just an alternative to a QLineEdit
for asking the user for a regular expression. From, a users point of view,
however, this is an good chance to use regular expressions without having
to learn some hard-to-remember ascii syntax.
</p><p>Try a demo
</p><p>==========
</p><p>In kdeutils/regexptest there is a very small program that shows the widget
in action. To give you an expression of how easy it is to use this widget,
here is the program in its whole length:
<blockquote>
</p><pre>
#include <kregexpeditor.h>
#include <kapp.h>
#include <kcmdlineargs.h>
int main( int argc, char* argv[] )
{
KCmdLineArgs::init(argc, argv, "RegExp \
Example","",""); KApplication myapp( argc, argv );
KRegExpEditor *regexp = KRegExpEditor::createEditor(0);
regexp->show();
myapp.setMainWidget(regexp);
return myapp.exec();
}
</pre>
</blockquote>
For this program to work, you need to cvs update and compile
kdelibs/interfaces, kdeutils/kregexpeditor and of course kdeutils/regexptest
</p><p>See some screen dumps.
</p><p>======================
</p><p>You can see some screen dumps of the test program at work at
<a href="http://www.blackie.dk/KDE/KRegExpEditor">http://www.blackie.dk/KDE/KRegExpEditor</a>.
</p><p>All the icons have not been drawn yet, so please bare over with my own drawing \
;-)
</p><p>What is required for it to work
</p><p>===============================
</p><p>To use the widget you must link your application with -lkregexpeditor. If
you have kdeutil installed then you will get this fancy graphical
editor. If not, then you will get a null pointer back from the call to
KRegExpEditor::createEditor, and it is then your responsibility to just
offer a lineedit to the user.
</p><p>The idea behind this is that the widget is quite huge (takes several minute
on my dual PIII-800 to compile). Therefore it needed to be placed somewhere
else than kdelibs/kdebase still several programs in kdebase might use it if
available.
</p><p>As a result an interface is located in kdelibs, and the actual
implementation is located in kdeutil.
</p></font></b>
</blockquote>
<p>This sort of project takes a lot of determination and time but will undoubtedly
be useful to many KDE users.</p>
<h1>14. <a name="14">EMail List for KDE3 Users</a></h1>
<b>23 Aug (1 posts): <a \
href="http://lists.kde.org/?l=kde-devel&m=99858713930422&w=2">New List! \
kde3alpha</a></b>
<p>
<p>Leading up to KDE2 there was an email list for those who were using the pre-beta \
releases to compare notes and generally keep up with what was happening.
Now that KDE3 is on the way, a similar list has been created. Christopher Molnar
detailed the plans for the list saying:</p>
<blockquote>
<b><font color="#880000">
<p>
</p><p>Well, it's been a little over a year since the removal of the kde2-alpha list
that allowed users of what has since become kde 2, then 2.1, now 2.2 to
communicate, report bugs, and help each other work through problems. It was a
hell of a development cycle and that list helped a lot of additional people
test and provide input into the final product.
</p><p>Now along comes the planning stages of KDE3. Already we are seeing some major
enhancements to the HEAD branch of CVS. So, here we go again, it is time to
create a new list!
</p><p>I would like to announce the creation of the KDE3ALPHA mailing list and
explain it's purpose:
</p><p>Subscription is at: <a \
href="http://mail.kde.org/mailman/listinfo/kde3alpha">http://mail.kde.org/mailman/listinfo/kde3alpha</a>
or via email at: <a \
href="mailto:kde3alpha-request@mail.kde.org">kde3alpha-request@mail.kde.org</a>
</p><p>The kde3alpha list is created for the purpose of users (non-developer types)
to communicate problems, sollutions, and bugs to each other and then in turn
to developers who may be monitoring the list. The list is also being created
with the hopes that a lot of the install/compile problems that end up in the
bug database can be resolved on the list rather quickly between users.
</p><p>I would like to request that those people who build nightly or weekly builds
of CVS HEAD branch and make them public consider joining this list so that
you may answer questions regarding your builds. (You may also want to
consider sending a note to the list telling where people can find your
builds).
</p></font></b>
</blockquote>
</blockquote>
<p> <p> <p> <p> <p> <p>
</td></tr></table>
<p align=center>We Hope You Enjoy Kernel Cousin KDE
<hr noshade>
<p>
<a href="legal.html">Legal Notice</a>
</body></html>
_______________________________________________
kc-kde mailing list
kc-kde@mail.kde.org
http://mail.kde.org/mailman/listinfo/kc-kde
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic