Re: search item issue
But I have tried the search function of adding app or widgets. It still have three characters limits. Flash yan On 04/20/2012 08:19 AM, Lamarque V. Souza wrote: Em Thursday 19 April 2012, flash yan escreveu: > Hi all, > > I found that the search function in plasma-active is limited in three > characters. > I think it should no characters limits. That is already fixed in the development version: https://bugs.kde.org/show_bug.cgi?id=296941 -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: search item issue
Em Thursday 19 April 2012, flash yan escreveu: > Hi all, > > I found that the search function in plasma-active is limited in three > characters. > I think it should no characters limits. That is already fixed in the development version: https://bugs.kde.org/show_bug.cgi?id=296941 -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
search item issue
Hi all, I found that the search function in plasma-active is limited in three characters. I think it should no characters limits. Thanks. Flash Yan ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Some user feedback (mostly about the PA browser)
Em Thursday 19 April 2012, Mario Fux escreveu: > Am Dienstag 17 April 2012, 13.02:25 schrieb Thomas Pfeiffer: > > Morning again > > So I reinstalled (with 2012-04-10-10-15-basyskom-plasma-active-testing-mer- > usb-live.iso) and right now we're playing with the browser. It is > definitely much faster and zooms (with pinch) much faster as well. > > > On 17.04.2012 12:14, Mario Fux wrote: > > > Here the mentioned IRC log: > > > [12:46] She tried to use mainly the browser to read some news > > > sites (tagesschau.sf.tv and www.telepolis.de) > > > [12:47] But first the browser was relatively slow (the > > > website quite big) and thus took a while to load. > > > [12:48] And then she had problems with zooming and clicking > > > or tapping the links. > > > > How did the pinch-to-zoom gesture work for her? I think the image you > > used should already contain Marco's patch which greatly improves zooming > > with the pinch gesture. > > Now with the faster browser it works good. Before it was too unpredictable > as it reacted just after a few seconds. > > > > [12:48] I think the mousearea for links is just the link text > > > and thus difficult tap with small fonts. Should probably be bigger. > > > > I assume this won't be easy to do (especially since we'd also have to > > avoid collisions between nearby links), but it would surely help. How is > > e.g. the Android browser handling this issue? > > No idea. But the link hitting problem is still there. Workaround. Zoom in > and hit again. We had the problem that we weren't sure if the link was > tapped or not but lamarque then told us on IRC: > [18:44] unormal: if the "reload" button turns into a "X" that > means the link was tapped. > which helps but the urlbar doesn't always reappear instantly. > > > > [12:50] sebas: Zoom triggered as she couldn't tap the link > > > and tried several times. > > > > So if we can make the links easier to hit, this should not happen > > anymore, either. > > > > > So I will try the mer image in the next days. > > > > Would be great to see how big the difference between the images actually > > is. I noticed the painfully slow loading on the Meego images as well. > > Worlds. > > > > And here some additional feedback. PA looks great, I like it! > > > > Glad to hear! :) > > > > > Another idea I had was to use QML news (RSS) thingie. What's the status > > > here? It doesn't seem to be ready yet? > > > > I've used it successfully on my device. Does it work at all on yours? And > > if so, what's missing? > > It works. But sometimes old feeds start to not work anymore and have > something like "undefined" in the config. Will try again with this mer > image. Maybe this is a problem with kded's networkstatus module not working with connman. Most KDE programs treats Solid::Networking::status() == Solid::Networking::Unknown as Solid::Networking::Connected (online), which is what happens with connman. But if the system is really offline then the program must recover by itself since there will be no statusChanged(Connected) signal. By what I could see in the rss dataengine it only fetches data if the statusChanged(Connected or Unknown) signal is received or when data source is requested. If we compile kde-runtime against QtNtrack then networkstatus should work with any network management software. But NTrack has a history of causing problems in kded (Ntrack 0.14 causes 100% CPU problems, Ntrack 0.16 force networkstatus to offline mode). Well, Ntrack 0.15 is also not perfect but seems to work. networkstatus includes a backend for NetworkManager and Wicd, so if we change to NM if will not need Ntrack. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Some user feedback (mostly about the PA browser)
On Thursday 19 April 2012, Lamarque V. Souza wrote: > > > > But ... we do support Flash in principle, meaning you can switch it on in > > the browser's settings, and then it'll work as horrible as flash works > > everywhere else, and your browser will feel slow while flash is enabled. > > And you also need to install the Shockwave flash plugin since we do not > ship it in any image. and in case of html5 would also mean of course missing h264 codec as well. all of this suck but we can't legally distribute them -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Some user feedback (mostly about the PA browser)
Em Thursday 19 April 2012, Sebastian Kügler escreveu: > On Thursday, April 19, 2012 18:57:09 Mario Fux wrote: > > One last thing about the browser. She told me that the videos on the news > > side "work" now. At least the play button and co are visible but she > > didn't manage to get one loading. > > Flash? If so, it just doesn't work. > > But ... we do support Flash in principle, meaning you can switch it on in > the browser's settings, and then it'll work as horrible as flash works > everywhere else, and your browser will feel slow while flash is enabled. And you also need to install the Shockwave flash plugin since we do not ship it in any image. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Some user feedback (mostly about the PA browser)
On Thursday, April 19, 2012 18:57:09 Mario Fux wrote: > One last thing about the browser. She told me that the videos on the news > side "work" now. At least the play button and co are visible but she > didn't manage to get one loading. Flash? If so, it just doesn't work. But ... we do support Flash in principle, meaning you can switch it on in the browser's settings, and then it'll work as horrible as flash works everywhere else, and your browser will feel slow while flash is enabled. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Bug 295839] Deleting / overwriting selected text not possible in some cases
https://bugs.kde.org/show_bug.cgi?id=295839 Mario Fux changed: What|Removed |Added CC||kde...@unormal.org --- Comment #1 from Mario Fux --- I've the same problem with the browser on the below mentioned image [1]. The on-screen-keyboard doesn't delete or overwrite the selected url (no matter if from rtl or ltr). But it works with an attached usb keyboard. [1] 2012-04-10-10-15-basyskom-plasma-active-testing-mer-usb-live.iso -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Some user feedback (mostly about the PA browser)
Am Dienstag 17 April 2012, 13.02:25 schrieb Thomas Pfeiffer: Morning again So I reinstalled (with 2012-04-10-10-15-basyskom-plasma-active-testing-mer- usb-live.iso) and right now we're playing with the browser. It is definitely much faster and zooms (with pinch) much faster as well. > On 17.04.2012 12:14, Mario Fux wrote: > > Here the mentioned IRC log: > > [12:46] She tried to use mainly the browser to read some news > > sites (tagesschau.sf.tv and www.telepolis.de) > > [12:47] But first the browser was relatively slow (the website > > quite big) and thus took a while to load. > > [12:48] And then she had problems with zooming and clicking or > > tapping the links. > > How did the pinch-to-zoom gesture work for her? I think the image you used > should already contain Marco's patch which greatly improves zooming with > the pinch gesture. Now with the faster browser it works good. Before it was too unpredictable as it reacted just after a few seconds. > > [12:48] I think the mousearea for links is just the link text > > and thus difficult tap with small fonts. Should probably be bigger. > > I assume this won't be easy to do (especially since we'd also have to avoid > collisions between nearby links), but it would surely help. How is e.g. the > Android browser handling this issue? No idea. But the link hitting problem is still there. Workaround. Zoom in and hit again. We had the problem that we weren't sure if the link was tapped or not but lamarque then told us on IRC: [18:44] unormal: if the "reload" button turns into a "X" that means the link was tapped. which helps but the urlbar doesn't always reappear instantly. > > [12:50] sebas: Zoom triggered as she couldn't tap the link and > > tried several times. > > So if we can make the links easier to hit, this should not happen anymore, > either. > > > So I will try the mer image in the next days. > > Would be great to see how big the difference between the images actually > is. I noticed the painfully slow loading on the Meego images as well. Worlds. > > And here some additional feedback. PA looks great, I like it! > > Glad to hear! :) > > > Another idea I had was to use QML news (RSS) thingie. What's the status > > here? It doesn't seem to be ready yet? > > I've used it successfully on my device. Does it work at all on yours? And > if so, what's missing? It works. But sometimes old feeds start to not work anymore and have something like "undefined" in the config. Will try again with this mer image. > > Oh and I like the new "file" browser (I still think "file" is not the > > right term as IIRC you want to get rid of the file hierarchy paradigm > > which IMHO goes in the right direction and brings KDE software (together > > with Nepomuk) in a pole position). > > Yes, this will definitely be renamed before the PA3 release. It's actually > more of a proof of concept at its current state, since it does not support > any operation other than "open" yet. And it will also support browsing any > type of resource in the future, not just files. So the current name would > not make any sense then, anyway. > Glad that you like our direction of replacing the file hierarchy with > semantic data. Oh I liked it from the start of Nepomuk on ;-). One last thing about the browser. She told me that the videos on the news side "work" now. At least the play button and co are visible but she didn't manage to get one loading. Thx Mario & Betty ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
Em Thursday 19 April 2012, Samuel Stirtzel escreveu: > Another idea, could this be a visibility problem? > Log of binutils nm: > - > samuel@s-stirtzel-linux:/work/oe-core/tmp-eglibc/sysroots/overo/usr/lib/kde > 4$ nm -C plasma_appletscript_declarative.so | grep script > 00023c68 t global constructors keyed to declarativescriptenv.cpp > 000347d8 r qt_meta_data_JavascriptAddonPackageStructure > 00034790 r qt_meta_stringdata_JavascriptAddonPackageStructure > 0002b3b0 T DeclarativeAppletScript::scriptEnv() > 0001ed60 T JavascriptAddonPackageStructure::pathChanged() > 0001ecb4 T JavascriptAddonPackageStructure::qt_metacall(QMetaObject::Call, > int, void**) > 0001ecb8 T JavascriptAddonPackageStructure::qt_metacast(char const*) > 00038138 D JavascriptAddonPackageStructure::staticMetaObject > 0001ec84 T JavascriptAddonPackageStructure::qt_static_metacall(QObject*, > QMetaObject::Call, int, void**) > 00038130 D JavascriptAddonPackageStructure::staticMetaObjectExtraData > 0001efcc T > JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*, > QList const&) > 0001efcc T > JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*, > QList const&) > 0001f9bc t > JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() > 0001f988 t > JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() > 0001f988 t > JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure() > 0001ec88 T JavascriptAddonPackageStructure::metaObject() const > U Plasma::AppletScript::description() const > U Plasma::DeclarativeWidget::scriptEngine() const > 00038194 D typeinfo for JavascriptAddonPackageStructure > 000347b4 R typeinfo name for JavascriptAddonPackageStructure > 00038148 D vtable for JavascriptAddonPackageStructure > - > U means undefined and "U Plasma::DeclarativeWidget::scriptEngine() > const" exports no function. > > Any ideas where I could look next? On Meego x86 image: [root@localhost ~]# nm -C /usr/lib/kde4/plasma_appletscript_declarative.so nm: /usr/lib/kde4/plasma_appletscript_declarative.so: no symbols -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
Em Thursday 19 April 2012, Samuel Stirtzel escreveu: > 2012/4/19 Lamarque V. Souza : > > Em Thursday 19 April 2012, Samuel Stirtzel escreveu: > >> 2012/3/30 Lamarque V. Souza : > >> > Em Friday 30 March 2012, Samuel Stirtzel escreveu: > >> >> Hi, > >> > > >> > Hi, > >> > > >> >> lately I have good progress on my work, normal KDE applications seem > >> >> > >> >> > >> >> > >> >> to work fine in OpenEmbedded. > >> >> > >> >> > >> >> > >> >> But my main goal, to port PA, still needs some effort. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> Currently I'm at the point that the home screen of PA shows up, > >> >> > >> >> > >> >> > >> >> but it seems like something went wrong with the declarative > >> >> > >> >> scriptengine. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> So there is a big sign with a "X" as label showing the text: > >> >> > >> >> > >> >> > >> >> "Could not create a declarativeappletscript sctiptengine" > >> > > >> > Enable all debug messages using kdebugdialog program (if possible), > >> > > >> > restart the graphical interface, try again and send me the > >> > > >> > ~/.xsession-errors file. > >> > >> Hi, > >> > >> I'm still working on this and looked through it once again, > > > >> and there seem to be more relevant parts in the logfile: > > You are probably using packages compiled with different versions of Qt, > > kdelibs or other dependencies of DeclarativeWidget. Send me the output of > > the command "rpm -qa". > > Please note I am a developer, > I am not using any precompiled iso/images. > Currently I am running on an ARMv7a Overo Gumstix and create build > instructions (to cross compile PA on a tool-chain) for OpenEmbedded > [1] and the Yocto Project [2]. Well, there must be something wrong with the kde-runtime package you compiled. The message plasma-device(583)/libplasma Plasma::loadEngine: Couldn't load script engine for language "declarativeappletscript" ! error reported: "The service 'Declarative widget' does not provide an interface 'Plasma::AppletScript' w" DeclarativeAppletScript (from plasma_appletscript_declarative.so, which is the library used by 'Declarative widget' service) inherits from Plasma::AppletScript. > I am building everything from source, so I don't have them installed via > RPM. But as opkg (the package manager I use) shows them as: > libqtcore4 - 4.8.0 > kdelibs4 - 4.8.0 > kde-runtime - 4.8.0 That seems fine regarding this particular problem. You should use kdelibs-4.8.2, which includes a fix for a slowness problem in nepomuk. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
2012/4/19 Lamarque V. Souza : > Em Thursday 19 April 2012, Samuel Stirtzel escreveu: > >> 2012/3/30 Lamarque V. Souza : > >> > Em Friday 30 March 2012, Samuel Stirtzel escreveu: > >> >> Hi, > >> > > >> > Hi, > >> > > >> >> lately I have good progress on my work, normal KDE applications seem > >> >> > >> >> to work fine in OpenEmbedded. > >> >> > >> >> But my main goal, to port PA, still needs some effort. > >> >> > >> >> > >> >> > >> >> Currently I'm at the point that the home screen of PA shows up, > >> >> > >> >> but it seems like something went wrong with the declarative > >> >> scriptengine. > >> >> > >> >> > >> >> > >> >> So there is a big sign with a "X" as label showing the text: > >> >> > >> >> "Could not create a declarativeappletscript sctiptengine" > >> > > >> > Enable all debug messages using kdebugdialog program (if possible), > >> > restart the graphical interface, try again and send me the > >> > ~/.xsession-errors file. > >> > >> Hi, > >> I'm still working on this and looked through it once again, > >> and there seem to be more relevant parts in the logfile: > > > > You are probably using packages compiled with different versions of Qt, > kdelibs or other dependencies of DeclarativeWidget. Send me the output of > the command "rpm -qa". > Please note I am a developer, I am not using any precompiled iso/images. Currently I am running on an ARMv7a Overo Gumstix and create build instructions (to cross compile PA on a tool-chain) for OpenEmbedded [1] and the Yocto Project [2]. I am building everything from source, so I don't have them installed via RPM. But as opkg (the package manager I use) shows them as: libqtcore4 - 4.8.0 kdelibs4 - 4.8.0 kde-runtime - 4.8.0 ... A full list of _all_ installed packages: http://pastebin.com/CVV2zRvy [1] http://www.openembedded.org/wiki/Main_Page [2] http://www.yoctoproject.org/ -- Regards Samuel ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: System Monitor on MeeGo Images?
Em Thursday 19 April 2012, Thomas Pfeiffer escreveu: > On 19.04.2012 12:12, Lamarque V. Souza wrote: > > Yesterday I built a custom kde-workspace package in my notebook with > > ksysguard (the file name of the executable for "System Monitor") > > included and it works in PA. I do not see anything really wrong with it > > except it uses right button menus for some features and tooltips (needs > > mouse over events) to show some information. The most important features > > are still usable with touchscreen and since we do not have any other > > system monitor application I think we should ship ksysguard until we > > find a more touchscreen-friendly one. > > +1 > It isn't touch.optimized, but it usually helps finding out why the heck > everything is so slow at some point. I pushed the changes. There is now a package called kde-workspace- ksysguard. The old kde-workspace-ksysguardd (with extrad 'd') is obsoleted by the kde-workspace-ksysguard because I have found that ksysguard really requires ksysguardd to work. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
Em Thursday 19 April 2012, Samuel Stirtzel escreveu: > 2012/3/30 Lamarque V. Souza : > > Em Friday 30 March 2012, Samuel Stirtzel escreveu: > >> Hi, > > > > Hi, > > > >> lately I have good progress on my work, normal KDE applications seem > >> > >> to work fine in OpenEmbedded. > >> > >> But my main goal, to port PA, still needs some effort. > >> > >> > >> > >> Currently I'm at the point that the home screen of PA shows up, > >> > >> but it seems like something went wrong with the declarative > >> scriptengine. > >> > >> > >> > >> So there is a big sign with a "X" as label showing the text: > >> > >> "Could not create a declarativeappletscript sctiptengine" > > > > Enable all debug messages using kdebugdialog program (if possible), > > restart the graphical interface, try again and send me the > > ~/.xsession-errors file. > > Hi, > I'm still working on this and looked through it once again, > and there seem to be more relevant parts in the logfile: You are probably using packages compiled with different versions of Qt, kdelibs or other dependencies of DeclarativeWidget. Send me the output of the command "rpm -qa". -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA OpenEmbedded support (WIP)
2012/3/30 Lamarque V. Souza :
> Em Friday 30 March 2012, Samuel Stirtzel escreveu:
>
>> Hi,
>
>
>
> Hi,
>
>
>
>> lately I have good progress on my work, normal KDE applications seem
>
>> to work fine in OpenEmbedded.
>
>> But my main goal, to port PA, still needs some effort.
>
>>
>
>> Currently I'm at the point that the home screen of PA shows up,
>
>> but it seems like something went wrong with the declarative scriptengine.
>
>>
>
>> So there is a big sign with a "X" as label showing the text:
>
>> "Could not create a declarativeappletscript sctiptengine"
>
>
>
> Enable all debug messages using kdebugdialog program (if possible), restart
> the graphical interface, try again and send me the ~/.xsession-errors file.
>
Hi,
I'm still working on this and looked through it once again,
and there seem to be more relevant parts in the logfile:
-
plasma-device(583)/libplasma
Plasma::DeclarativeWidgetPrivate::finishExecute: Execution of QML
done!
QGraphicsScene::addItem: item has already been added to this scene
Object::connect: No such signal HomeScreen_QMLTYPE_10::minimumWidthChanged()
Object::connect: (sender name: 'homeScreen')
Object::connect: No such signal HomeScreen_QMLTYPE_10::minimumHeightChanged()
Object::connect: (sender name: 'homeScreen')
Object::connect: No such slot PlasmaApp::containmentsTransformingChanged(bool)
Object::connect: (sender name: 'homeScreen')
Object::connect: (receiver name: 'plasma-device')
plasma-device(583)/libplasma Plasma::CoronaPrivate::importLayout: !!{}
STARTUP TIME 2554761 Adding Containment
"org.kde.active.activityscreen"
plasma-device(583)/libplasma Plasma::PluginLoader::loadApplet: we have
a script using the "declarativeappletscript" API
plasma-device(583)/libplasma Plasma::loadEngine: Couldn't load script
engine for language "declarativeappletscript" ! error reported: "The
service 'Declarative widget' does not provide an interface
'Plasma::AppletScript' w"
-
Here is the full log: http://pastebin.com/hjffJQ3q
At the end of the log I removed redundant Soprano messages.
Another idea, could this be a visibility problem?
Log of binutils nm:
-
samuel@s-stirtzel-linux:/work/oe-core/tmp-eglibc/sysroots/overo/usr/lib/kde4$
nm -C plasma_appletscript_declarative.so | grep script
00023c68 t global constructors keyed to declarativescriptenv.cpp
000347d8 r qt_meta_data_JavascriptAddonPackageStructure
00034790 r qt_meta_stringdata_JavascriptAddonPackageStructure
0002b3b0 T DeclarativeAppletScript::scriptEnv()
0001ed60 T JavascriptAddonPackageStructure::pathChanged()
0001ecb4 T JavascriptAddonPackageStructure::qt_metacall(QMetaObject::Call,
int, void**)
0001ecb8 T JavascriptAddonPackageStructure::qt_metacast(char const*)
00038138 D JavascriptAddonPackageStructure::staticMetaObject
0001ec84 T JavascriptAddonPackageStructure::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**)
00038130 D JavascriptAddonPackageStructure::staticMetaObjectExtraData
0001efcc T
JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*,
QList const&)
0001efcc T
JavascriptAddonPackageStructure::JavascriptAddonPackageStructure(QObject*,
QList const&)
0001f9bc t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure()
0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure()
0001f988 t JavascriptAddonPackageStructure::~JavascriptAddonPackageStructure()
0001ec88 T JavascriptAddonPackageStructure::metaObject() const
U Plasma::AppletScript::description() const
U Plasma::DeclarativeWidget::scriptEngine() const
00038194 D typeinfo for JavascriptAddonPackageStructure
000347b4 R typeinfo name for JavascriptAddonPackageStructure
00038148 D vtable for JavascriptAddonPackageStructure
-
U means undefined and "U Plasma::DeclarativeWidget::scriptEngine()
const" exports no function.
Any ideas where I could look next?
--
Regards
Samuel
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
Re: System Monitor on MeeGo Images?
On 19.04.2012 12:12, Lamarque V. Souza wrote: Yesterday I built a custom kde-workspace package in my notebook with ksysguard (the file name of the executable for "System Monitor") included and it works in PA. I do not see anything really wrong with it except it uses right button menus for some features and tooltips (needs mouse over events) to show some information. The most important features are still usable with touchscreen and since we do not have any other system monitor application I think we should ship ksysguard until we find a more touchscreen-friendly one. +1 It isn't touch.optimized, but it usually helps finding out why the heck everything is so slow at some point. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: System Monitor on MeeGo Images?
On Thursday 19 April 2012, Lamarque V. Souza wrote: > Ok, so we can package it separately and not include it in the images. > This way anybody can use zypper to install it. Currently it is not even > compiled at all. The package name will be kde-workspace-ksysguard or should > we use only ksysguard. There is a kde-workspace-ksysguardd package already > (notice the extra 'd' at the end), so for consistency we should use kde- > workspace-ksysguard in my oppinion. ksysguardd is a daemon used only for > monitoring remote computers, it is not necessary most of the time. +1 for kde-workspace-ksysguard -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: System Monitor on MeeGo Images?
Em Thursday 19 April 2012, Marco Martin escreveu: > On Thursday 19 April 2012, Lamarque V. Souza wrote: > > Yesterday I built a custom kde-workspace package in my notebook with > > > > ksysguard (the file name of the executable for "System Monitor") included > > and it works in PA. I do not see anything really wrong with it except it > > uses right button menus for some features and tooltips (needs mouse over > > events) to show some information. The most important features are still > > usable with touchscreen and since we do not have any other system monitor > > application I think we should ship ksysguard until we find a more > > touchscreen-friendly one. > > the fact is that we were trying to make the mobile setup a bit more > minimal, also including phasing out qwidget based apps. > i don't have particular things against ksysguard per se tough Ok, so we can package it separately and not include it in the images. This way anybody can use zypper to install it. Currently it is not even compiled at all. The package name will be kde-workspace-ksysguard or should we use only ksysguard. There is a kde-workspace-ksysguardd package already (notice the extra 'd' at the end), so for consistency we should use kde- workspace-ksysguard in my oppinion. ksysguardd is a daemon used only for monitoring remote computers, it is not necessary most of the time. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: System Monitor on MeeGo Images?
On Thursday 19 April 2012, Lamarque V. Souza wrote: > > Yesterday I built a custom kde-workspace package in my notebook with > ksysguard (the file name of the executable for "System Monitor") included > and it works in PA. I do not see anything really wrong with it except it > uses right button menus for some features and tooltips (needs mouse over > events) to show some information. The most important features are still > usable with touchscreen and since we do not have any other system monitor > application I think we should ship ksysguard until we find a more > touchscreen-friendly one. the fact is that we were trying to make the mobile setup a bit more minimal, also including phasing out qwidget based apps. i don't have particular things against ksysguard per se tough -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: System Monitor on MeeGo Images?
Em Wednesday 18 April 2012, Lamarque V. Souza escreveu: > Em Tuesday 10 April 2012, Thomas Pfeiffer escreveu: > > Hi, > > I'm not sure if it's only on the MeeGo images, but at least there the > > System Monitor application seems to have been removed a few months ago. > > I'm not sure why, since I think it's quite a useful application (for > > those who don't want to use top) and it seemed to work fine while it was > > still available. > > So could we put it back in or was there a specific reason to remove it? > > Commit e93562f42e73d3d3a99d1d2dfb704645eb36b39b from kde-workspace > disabled ksysguard for mobile profile, which is the one we use in Plasma > Active. I do not know why it was removed and (strangely enough) ksysguardd > (the daemon to monitor remote computers) is still compiled in mobile > profile. > > I also want to re-enable ksysguard in Plasma Active if nobody has > anything against it. Yesterday I built a custom kde-workspace package in my notebook with ksysguard (the file name of the executable for "System Monitor") included and it works in PA. I do not see anything really wrong with it except it uses right button menus for some features and tooltips (needs mouse over events) to show some information. The most important features are still usable with touchscreen and since we do not have any other system monitor application I think we should ship ksysguard until we find a more touchscreen-friendly one. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: default config machinery
Em Thursday 19 April 2012, Marco Martin escreveu: > On Monday 16 April 2012, Marco Martin wrote: > > Hi all, > > > > we now have a plasma-mobile-config git repo (where different devices > > would be different branches) that has also the startactive modules, > > since they may be device dependent as well. > > to update this, now i have > > plasma-contour-config > plasma-contour-config-meego > plasma-contour-config-vivaldi > > building from the different branches > > > i would still try to rename > kde-skel-binary > to > nepomuk-default-database-skel (since is what it is) I think we should follow a standard to name packages. Above you used the customization strings (device name / operating system) as suffix (e.g. plasma-contour-config-meego), here you used the customization string (default) in the middle of the package name. nepomuk-database-default would be a better name (or just nepomuk-database if we really follow the standard for plasma- contour-config). Then we can use nepomuk-database-vivaldi, nepomuk-database- . The "skel" is not necessary in my oppinion. If you check you will see that other packages install files in /etc/skel without having "skel" in their names. > and try to keep the startactive modules in startactive (hopefully not many > device specific changes will be needed?) tomake a tad easier to package +1. I prefer keeping configuration files near the programs that use them (if possible). -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: default config machinery
On Monday 16 April 2012, Marco Martin wrote: > Hi all, > > we now have a plasma-mobile-config git repo (where different devices would > be different branches) that has also the startactive modules, since they > may be device dependent as well. to update this, now i have plasma-contour-config plasma-contour-config-meego plasma-contour-config-vivaldi building from the different branches i would still try to rename kde-skel-binary to nepomuk-default-database-skel (since is what it is) and try to keep the startactive modules in startactive (hopefully not many device specific changes will be needed?) tomake a tad easier to package then i would really like to merge this asap in devel (if continuous integration out of the different branches can be enabled would be awesome) Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
