Re: i18n bugs in plasma branch 4.3 + in trunk
Am Freitag 10 Juli 2009 11:18:49 schrieb Burkhard Lück: Am Donnerstag 09 Juli 2009 17:20:50 schrieb Burkhard Lück: Am Mittwoch 08 Juli 2009 19:25:56 schrieb Aaron J. Seigo: On Wednesday 08 July 2009, Burkhard Lück wrote: looking at the Messages.sh file i see that only one pot file is created, however. that's perhaps unfortunate. so you'd like to go with 6 different message catalogs plasma_applet_sm_[cpu| hdd|hwinfo|net|ram|temperature] in branch and trunk? as long as that's not too much of a hassle, that matches the design. Ok, i can do the i18n part - adjusting the Messages.sh's and splitting all existing translations into the six new catalogs. Which solution for this i18n bug would you like to have: 1) KGlobal::locale()-insertCatalog(plasma_applet_system-monitor); in each applet or 2) But before i can do that, these files have to be moved into six new sub dirs: ram*.* net*.* cpu*.* hwinfo*.* hdd*.* temperature*.* Reason for that is scripty, see l10n-kde4/scripts/extract-messages.sh When you move these files, change this line in the existing Messages.sh to avoid loosing any translation in the transition: -$XGETTEXT *.cpp -o $podir/plasma_applet_system-monitor.pot +$XGETTEXT `find . -name '*.cpp'` -o $podir/plasma_applet_system-monitor.pot Ping? -- Burkhard Lück ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: i18n bugs in plasma branch 4.3 + in trunk
Am Freitag 10 Juli 2009 09:26:27 schrieb Burkhard Lück: Am Donnerstag 09 Juli 2009 08:10:48 schrieb Burkhard Lück: what's with these catalogs in kdeplasma-addons/dataengines: ocs/lib/Messages.sh:2:$XGETTEXT *.cpp -o $podir/libocsclient.pot ocs/ocsengine.h:80:K_EXPORT_PLASMA_DATAENGINE(attica, OcsEngine ) ocs/Messages.sh:2:$XGETTEXT *.cpp -o $podir/plasma_engine_ocs.pot libocsclient has only one message, but is never pulled in anywhere. EXPORT makro says attica, but catalog is named ocs. mv plasma_engine_ocs plasma_engine_attica? does this catalog need to be renamed? Ping? -- Burkhard Lück ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: i18n bugs in plasma branch 4.3 + in trunk
On Sun, Jul 12, 2009 at 13:15, Burkhard Lücklu...@hube-lueck.de wrote: Ping? Hi Burkhard, if your ping means, you are waiting for an answer from Aaron, you should be aware, that: i'll be out in vancouver for the next two weeks or so arranging things for my move out there. i don't know what kind of internet access i will have out there (in theory i'll have an internet connection) or how much time i will have for working on plasma/kde during this time (probably very little). i'll do my best to keep up with email, but i will almost certainly not be on irc during that time. Taken from an email from Aaron to plasma-devel@ a few days ago. I hope that helps. michael ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: window management ideas
On Fri, Jul 10, 2009 at 9:28 PM, Chanichan...@gmail.com wrote: today I was told that wmii is a window manager that uses tags, so I need to go look into that. http://dwm.suckless.org/ Also worth a look. Rich. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
qWarnings in plasma
I'm currently hunting down some qWarnings. Please have a look and see if we
can get rid of these in plasma. I'm on qt trunk so it could be those warning
are new there. But i thought they probably tell use about a problem so here
they are.
This kind of warning happens twice.
#0 qWarning (msg=0x73ea55d8 QGraphicsLinearLayout::removeAt: invalid
index %d) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/global/qglobal.cpp:2130
#1 0x73dc8c15 in QGraphicsLinearLayout::removeAt (this=0xbaaf50,
index=0)
at
/home/mjansen/kde/trunk/src/qtmaster/src/gui/graphicsview/qgraphicslinearlayout.cpp:327
#2 0x775e9395 in Plasma::PopupAppletPrivate::popupConstraintsEvent
(this=0x846710, constraints={i = -15088})
at /home/mjansen/kde/trunk/src/kdelibs/plasma/popupapplet.cpp:156
#3 0x775a37b2 in Plasma::Applet::flushPendingConstraintsEvents
(this=0x964cc0) at /home/mjansen/kde/trunk/src/kdelibs/plasma/applet.cpp:1167
#4 0x775c5474 in Plasma::Corona::loadLayout (this=0x777a40,
configName=value optimized out) at
/home/mjansen/kde/trunk/src/kdelibs/plasma/corona.cpp:379
#5 0x775c569e in Plasma::Corona::initializeLayout (this=0x777a40,
configna...@0x7fffc970) at
/home/mjansen/kde/trunk/src/kdelibs/plasma/corona.cpp:324
#6 0x77ba0edf in PlasmaApp::corona (this=0x624610) at
/home/mjansen/kde/trunk/src/kdebase/workspace/plasma/shells/desktop/plasmaapp.cpp:540
#7 0x77ba27ee in PlasmaApp::setupDesktop (this=0x624610) at
/home/mjansen/kde/trunk/src/kdebase/workspace/plasma/shells/desktop/plasmaapp.cpp:252
#8 0x77ba29bd in PlasmaApp::qt_metacall (this=0x624610,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fffcbf0)
at
/home/mjansen/kde/trunk/bld/kdebase/workspace/plasma/shells/desktop/plasmaapp.moc:115
#9 0x72fc07c8 in QMetaObject::activate (sender=0x74c360,
from_signal_index=4, to_signal_index=4, argv=0x0)
at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qobject.cpp:3115
#10 0x72fc1b89 in QMetaObject::activate (sender=0x74c360,
m=0x732dc5c0, local_signal_index=0, argv=0x0)
at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qobject.cpp:3192
#11 0x72fc88e4 in QSingleShotTimer::timeout (this=0x74c360) at
.moc/debug-shared/qtimer.moc:76
#12 0x72fc89db in QSingleShotTimer::timerEvent (this=0x74c360) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qtimer.cpp:298
#13 0x72fbc8cc in QObject::event (this=0x74c360, e=0x7fffd580) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qobject.cpp:1065
#14 0x7377086d in QApplicationPrivate::notify_helper (this=0x63aff0,
receiver=0x74c360, e=0x7fffd580)
at
/home/mjansen/kde/trunk/src/qtmaster/src/gui/kernel/qapplication.cpp:4106
#15 0x7377950c in QApplication::notify (this=0x624610,
receiver=0x74c360, e=0x7fffd580)
at
/home/mjansen/kde/trunk/src/qtmaster/src/gui/kernel/qapplication.cpp:3632
#16 0x76149f8e in KApplication::notify (this=0x624610,
receiver=0x74c360, event=0x7fffd580)
at /home/mjansen/kde/trunk/src/kdelibs/kdeui/kernel/kapplication.cpp:302
#17 0x72faa481 in QCoreApplication::notifyInternal (this=0x624610,
receiver=0x74c360, event=0x7fffd580)
at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qcoreapplication.cpp:620
#18 0x7376d1e5 in QCoreApplication::sendEvent (receiver=0x74c360,
event=0x7fffd580)
at
../../include/QtCore/../../../../src/qtmaster/src/corelib/kernel/qcoreapplication.h:213
#19 0x72fdbd59 in QTimerInfoList::activateTimers (this=0x63e190) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qeventdispatcher_unix.cpp:580
#20 0x72fd9542 in timerSourceDispatch (source=0x63e130) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qeventdispatcher_glib.cpp:165
#21 0x7fffeeb790fb in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#22 0x7fffeeb7c8cd in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x7fffeeb7ca8b in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#24 0x72fd871a in QEventDispatcherGlib::processEvents (this=0x60ba00,
flags={i = -10272})
at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qeventdispatcher_glib.cpp:327
#25 0x7382919f in QGuiEventDispatcherGlib::processEvents
(this=0x60ba00, flags={i = -10176})
at
/home/mjansen/kde/trunk/src/qtmaster/src/gui/kernel/qguieventdispatcher_glib.cpp:202
#26 0x72fa773b in QEventLoop::processEvents (this=0x7fffd900,
flags={i = -10080}) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qeventloop.cpp:149
#27 0x72fa795d in QEventLoop::exec (this=0x7fffd900, flags={i =
-9968}) at
/home/mjansen/kde/trunk/src/qtmaster/src/corelib/kernel/qeventloop.cpp:197
#28 0x72faaccc in QCoreApplication::exec () at
Re: zui ideas
It's been a while (since the 4.2 cycle) since I've contributed to plasma; things got really busy this last six months. If it's worth anything, I thought I'd provide a little feedback on this zui topic. - Original Message From: Chani chan...@gmail.com zoom 2 (fully zoomed out): ... zoom level 1: ... zoom 1/2: ... zoom 0 (fully zoomed in): The terms Zoom Out and Zoom In are presented to the user. I wonder if this perhaps exposes the mechanism rather than the action(s) the user would like to perform. What distinct functionality does each of the zoom level provide? Or another way to put it might be, what activity would the user like to perform that would prompt the user to change zoom levels? At the zoom 0 (fully zoomed in) level, the only thing I can think that Zoom Out provides is to show the available activities. Once zoomed out (1/2, 1, 2) the user can currently select an activity, create new activities, or remove existing activities. If that is what it does (or is envisioned to do), would it make sense to label Zoom Out in the fully-zoomed-in/normal-desktop-view mode something like Show Activities. Selecting an activity could use the same Qt/KDE selection model similar to what's used throughout the desktop (essentially a single selection view). Keyboard navigation could be the same as elsewhere on the desktop: arrows keys highlight, enter activates (zooms in). Mouse navigation would be the same: mouse over highlights, click/double-click activates. To keep the move-applets-between-containments-using-the-mouse functionality probably requires the activate target outside the containment like the Zoom In on the handle is now (but perhaps bigger and labeled Select or Select this activity Use or something...). If all the activites don't fit on the screen, perhaps the same mechanic that's used througout the desktop when display items don't fit on the display area could be used here: a horizontal scrollbar. I have to keep reminding myself that I can drag-to-scroll when I've zoomed out to see the available activities. To push a little the further; what about a zoom slider in the tool box once the user is in the Show Activities/(zoom 0) mode. The slider could use detents for each zoom level. The user is arguably already familiar with the zoom slider from many apps (dolphin, gwenview). The visual presentation and interation would be mostly similar to a dolphin icon view in preview mode, only with live, more interactive previews (containments). One remaining question would be: are there any functions envisioned in the zoomed out modes that go beyond selecting, creating and removing activies that would not work with this suggested mechanic? Just a few thoughts I hope are helpful, and I'm happy to pitch in some coding time to help whoever wants to work on this, Andrew Lake ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
