Slavek,
I have time to look at the changes to sip4-tqt, but checking bug 1790 the
patches are crossed out and gone - what is up?
--
David C. Rankin, J.D.,P.E.
>> Is there a way to sort konqueror columns using the keyboard?
>Not that I am aware of.
Often I use the columns to resort files based upon what I am doing
to provide a different view perspective.
Ever since I encountered my mouse misbehavior a while back I have
been using the keyboard more and more. I should start a journal and
note which tasks are difficult without a mouse.
>> Is there a way to invoke the context popup menu with the
>keyboard
>>when a file is selected?
>On my system i can use the right window key to do that.
>The very first time it seems to take a while. Can you confirm
>that? Perhaps a bug similar to the Alt+F1 one. New bug report?
Ah yes, the infamous special "Super" keys. My main desktop keyboard
does not have any such keys. I have them disabled on the laptop
because I am continually inadvertently bumping the keys, and the
popup menus distrupt my thinking and work flow.
Looks like we need a shortcut.
Darrell
All,
Is there a way to sort konqueror columns using the keyboard?
Is there a way to invoke the context popup menu with the keyboard
when a file is selected?
Darrell
All,
We have an inconsistent mixed delivery of i18n files. Many locales
are packaged with tde-i18n; some are packaged in a smaller i18n
package, such as gwenview, k3b, and koffice; while others are
packages as part of the parent app. That last group includes the
following:
amarok
digikam
filelight
kbiff
kdbg
kdiff3
kile
kipi-plugins
kmplayer
knights
knutclient
konversation
krecipes
krusader
kshowmail
kshutdown
ksquirrel
kvpnc
rosegarden
showfoto
tdepowersave
tdesvn
tellico
Of this latter group, only a few locales are supported in each of
the packages.
With the three packages that include all i18n files: gwenview, k3b,
and koffice, a challenge is gwenview and k3b is an all or nothing
installation. Conversely, like tde-18n, koffice-i18n can be
compiled as separate locale packages.
tde-i18n has become a monster module, just too large to deal with.
That module should be split into smaller locale modules. Then the
packages listed above, as well as gwenview, k3b, and koffice, could
be merged into each respective locale module.
Comments appreciated.
Darrell
> I created a fantastic kicker wallpaper that I would like to have
>added to the
>tdebase install. (343 bytes total) It goes with the default theme
>and makes
>kicker look pretty slick. I'm not saying make it the default
>kicker background,
>but just provide it in the directory. I would probably rename it
>'blueglass.png'
>instead of the attached filename. Take a look.
Nobody complained and I built the new image without incident.
Pushed to git in commit 1a452134.
Nice artwork. :)
Darrell
>I assume that both patches (1912, 1913) from bug 1790 can be
>considered as tested => suitable for pushing to Git.
No build problems here. Push.
Darrell
All,
I don't know what happened within the past several weeks, but of
late, anytime I delete only the tdelibs package from my build
environment and rebuild to test patches, the build log is filled
with this kind of spew:
libtdeabc.so.1: cannot open shared object file: No such file or
directory
libtdeparts.so.2: cannot open shared object file: No such file or
directory
When I delete all other packages other than the tdelibs
dependencies, then tdelibs builds as expected without the spew.
Any ideas?
Darrell
All,
For several days I have been working on several items with the help
handbook system. I've been thorough and have been testing intensely
with the hope of avoiding new bugs after the patches are pushed to
git.
Much of the work revolves around fixing tdeioslaves and protocol
handbooks, but there are other patches such as fixing missing
icons, fixing DocPath keys, updated handbooks, etc.
The patches include tde-i18n fixes to match as much as possible the
changes made in the parent packages.
I ran a final full build set last night with all of the upcoming
patches, including tde-i18n. There were no build failures and my
usage tests today went as expected.
As the patch set includes the tdelibs module, which include entity
changes, your best approach is to run a full build set. Any time we
update the entities in tdelibs that means help handbooks using the
previous entities will fail to build.
After many rounds of package rebuilding and usability testing I'm
not expecting problems, but as always I'm only one person and don't
conceive of or anticipate all use cases. Please report potentially
related bugs to the list and I'll look into them. Please don't
report bugs unless you performed a full package set rebuild because
that will be my first reply. :)
I plan to soon start pushing those patches.
I plan to run another full build set tonight after I finish pushing
all patches to ensure no new problems.
Darrell