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
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- something else. 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: PA OpenEmbedded support (WIP)
2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: 2012/3/30 Lamarque V. Souza lamarque.souza@basyskom.com: 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: PA OpenEmbedded support (WIP)
Em Thursday 19 April 2012, Samuel Stirtzel escreveu: 2012/4/19 Lamarque V. Souza lamarque.souza@basyskom.com: Em Thursday 19 April 2012, Samuel Stirtzel escreveu: 2012/3/30 Lamarque V. Souza lamarque.souza@basyskom.com: 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: 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
