Does Trinity support any methods for configuring autostart apps?
I came across this applet but the links to the sources are dead:
http://kde-apps.org/content/show.php?content=45975&forumpage=0&PHPSE...
With that said, looks like the applet might still exist:
http://packages.ubuntu.com/search?keywords=kcontrol-autostart
Darrell
On Mon, 16 Apr 2012 19:21:36 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
Does Trinity support any methods for configuring autostart apps?
I came across this applet but the links to the sources are dead:
http://kde-apps.org/content/show.php?content=45975&forumpage=0&PHPSE...
With that said, looks like the applet might still exist:
http://packages.ubuntu.com/search?keywords=kcontrol-autostart
Source code: http://kcontrol-autostart.sourcearchive.com/documentation/0.5/dir_832320ed3c... (links at bottom).
However, if you check toward the end of the comments on kde-apps, there are some complaints about crashing and compile failures with KDE 3.5.10, so it may not be usable.
Does Trinity support any methods for configuring
autostart apps?
I came across this applet but the links to the sources
are dead:
http://kde-apps.org/content/show.php?content=45975&forumpage=0&PHPSE...
With that said, looks like the applet might still exist:
http://packages.ubuntu.com/search?keywords=kcontrol-autostart
Source code: http://kcontrol-autostart.sourcearchive.com/documentation/0.5/dir_832320ed3c... (links at bottom).
However, if you check toward the end of the comments on kde-apps, there are some complaints about crashing and compile failures with KDE 3.5.10, so it may not be usable.
Thanks! Yes, I saw the complaints too. :) That makes me curious about the Debian/Ubuntu package for KDE3. Possibly one and the same, possibly not.
I think the module would be a nice addition once we debugged the code. :)
Ok --- I grabbed the sources. After I sanitize them for the TQt layer, how do I merge them with a parent package? Or would we host the module in the applications sources?
Darrell
Does Trinity support any methods for configuring
autostart apps?
I came across this applet but the links to the sources
are dead:
http://kde-apps.org/content/show.php?content=45975&forumpage=0&PHPSE...
With that said, looks like the applet might still exist:
http://packages.ubuntu.com/search?keywords=kcontrol-autostart
Source code: http://kcontrol-autostart.sourcearchive.com/documentation/0.5/dir_832320ed3c... (links at bottom).
However, if you check toward the end of the comments on kde-apps, there are some complaints about crashing and compile failures with KDE 3.5.10, so it may not be usable.
Thanks! Yes, I saw the complaints too. :) That makes me curious about the Debian/Ubuntu package for KDE3. Possibly one and the same, possibly not.
I think the module would be a nice addition once we debugged the code. :)
Ok --- I grabbed the sources. After I sanitize them for the TQt layer, how do I merge them with a parent package? Or would we host the module in the applications sources?
Darrell
Files would go in tdebase/kcontrol/autostart/ Copy a CMakeLists.txt file from any other folder in the tdebase/kcontrol/ directory into your new tdebase/kcontrol/autostart/ directory. Then edit tdebase/kcontrol/autostart/CMakeLists.txt so that the source file names, .desktop file name, and library name are all correct for the new autostart module. Finally, edit tdebase/kcontrol/CMakeLists.txt and add a new line "add_subdirectory( autostart )" where it makes sense.
Tim
Files would go in tdebase/kcontrol/autostart/ Copy a CMakeLists.txt file from any other folder in the tdebase/kcontrol/ directory into your new tdebase/kcontrol/autostart/ directory. Then edit tdebase/kcontrol/autostart/CMakeLists.txt so that the source file names, .desktop file name, and library name are all correct for the new autostart module. Finally, edit tdebase/kcontrol/CMakeLists.txt and add a new line "add_subdirectory( autostart )" where it makes sense.
Ok. Thanks. Yet Another Side Project!
Darrell
Ok --- I grabbed the sources. After I sanitize them for the TQt layer, how do I merge them with a parent package? Or would we host the module in the applications sources?
Files would go in tdebase/kcontrol/autostart/ Copy a CMakeLists.txt file from any other folder in the tdebase/kcontrol/ directory into your new tdebase/kcontrol/autostart/ directory. Then edit tdebase/kcontrol/autostart/CMakeLists.txt so that the source file names, .desktop file name, and library name are all correct for the new autostart module. Finally, edit tdebase/kcontrol/CMakeLists.txt and add a new line "add_subdirectory( autostart )" where it makes sense.
Um, golly gee willikers, Mr. Wilson. I actually got the module to build!
For the moment I am building as a separate package that would get merged to the applications tree. I started to fiddle with merging directly into tdebase/kcontrol but then got unsure about what to strip from the original sources. Further, I wondered whether everybody would want this module, although we could add a -DWITH-AUTOSTART build option. Anyway, I figure we can merge to tdebase later, but for now we need to ensure the sources build and develop a usability test plan.
According to the original kde-look.org descriptions (http://kde-apps.org/content/show.php?content=45975), there does not seem to be much to this module. Just a graphical way to add or remove apps, which is a notch better than the previous methods KDE3 required.
I used the Ubuntu sources, which came with a large Ubuntu/Debian patch, which merged without error (after updating one line for TDE). I don't know whether that patch fixed any of the known bugs listed at kde-look.org. Therefore the test plan includes testing those reported bugs.
The docbook file is merely a template.
Test plan:
* Installs correctly to TDE Components.
* If the user's Autostart directory is already populated, verify those items appear in the modules list.
* Can add new apps to the list.
* Those newly added apps actually start with the next new session.
* Previously populated apps still start with the next new session.
* Can remove apps from the list.
* Apps not removed still start with the next new session.
* Bug: When launching apart for kcontrol, clicking "Cancel" with a properties dialog open will generate a crash.
* Bug: When launching inside kcontrol, option "Reset" does not work.
* Bug: Clicking "Reset" with a properties dialog open inserts a duplicate entry into the list of the entry which has the properties open.
* What else?
Darrell
Um, golly gee willikers, Mr. Wilson. I actually got the module to build!
For the moment I am building as a separate package that would get merged to the applications tree. I started to fiddle with merging directly into tdebase/kcontrol but then got unsure about what to strip from the original sources. Further, I wondered whether everybody would want this module, although we could add a -DWITH-AUTOSTART build option. Anyway, I figure we can merge to tdebase later, but for now we need to ensure the sources build and develop a usability test plan.
According to the original kde-look.org descriptions (http://kde-apps.org/content/show.php?content=45975), there does not seem to be much to this module. Just a graphical way to add or remove apps, which is a notch better than the previous methods KDE3 required.
I used the Ubuntu sources, which came with a large Ubuntu/Debian patch, which merged without error (after updating one line for TDE). I don't know whether that patch fixed any of the known bugs listed at kde-look.org. Therefore the test plan includes testing those reported bugs.
The docbook file is merely a template.
Test plan:
* Installs correctly to TDE Components. Check!
* If the user's Autostart directory is already populated, verify those items appear in the modules list. Check!
* Can add new apps to the list. Check!
* Those newly added apps actually start with the next new session. Check!
* Previously populated apps still start with the next new session. Check!
* Can remove apps from the list. Check!
* Apps not removed still start with the next new session. Check!
* Alleged Bug: When launching apart for kcontrol, clicking "Cancel" with a properties dialog open will generate a crash. Can't reproduce.
* Alleged Bug: When launching inside kcontrol, option "Reset" does not work. Button does work --- sort of: read the next item.
* Alleged Bug: Clicking "Reset" with a properties dialog open inserts a duplicate entry into the list of the entry which has the properties open. Reproduced. Checking the contents of the Autostart directory shows the items are not really duplicating. Toggling out of the Autostart manager module and returning immediately clears the list of duplicate entries. Not a blocker bug but not professional looking.
I could not replicate this bug: https://bugs.kde.org/show_bug.cgi?id=150439.
I discovered a new bug: I monitored my Autostart and shutdown directories in Konqueror while testing the module. When adding or removing items they are added or removed immediately --- before selecting the Apply button. Probably not good.
Overall, we have a nice user-friendly addition with this module. As far as I can see, only two minor bugs.
Reading the discussion at kde-look.org, one person suggested a "Disable" option, which seems handy. Another possible enhancement is mentioned here: http://lists.kde.org/?l=kde-devel&m=116924533130243&w=2 --- basically provide a portal to override anything in the global autostart locations.
Yet even as is, this module provides a handy way of adding and removing items to the Autostart, shutdown and env directories. Yes, shutdown too.
What next? Fixing the two bugs probably is beyond my noob C++ skills, although I'll take a gander. Does this new module sound like a good addition? If yes then do we want to keep this as a separate optional module or merge into tdebase/kcontrol or tdeadmin?
Darrell
Obligatory screen shot:
http://humanreadable.nfshost.com/trinity/build_logs/autostart.png
Darrell
Looks good to me. Will this be pushed to tdebase GIT or did you build it as a standalone module?
Tim
Obligatory screen shot:
http://humanreadable.nfshost.com/trinity/build_logs/autostart.png
Darrell
Looks good to me. Will this be pushed to tdebase GIT or did you build it as a standalone module?
I built as a standalone module:
* I don't know how far to strip the original sources and support files to fit the kcontrol structure.
* The module is automake and I don't know enough yet to convert to cmake.
* I don't know that everybody wants this. If placed in kcontrol then nobody has a choice. If placed in applications then everybody has a choice.
There are two minor bugs that need attention, as mentioned in my previous post. I'll try to expand my noob C++ skills and take a look, but if I stumble then I'll file a bug report after we merge. If we want to keep as a standalone module then I'll need a spot created in applications before I can push, like you did with tqca.
Darrell
Darrell
--- On Sun, 4/22/12, Darrell Anderson humanreadable@yahoo.com wrote:
From: Darrell Anderson humanreadable@yahoo.com Subject: Re: [trinity-devel] KControl and configuring autostart (success!) To: trinity-devel@lists.pearsoncomputing.net Date: Sunday, April 22, 2012, 1:19 AM
Obligatory screen shot:
http://humanreadable.nfshost.com/trinity/build_logs/autostart.png
Darrell
Looks good to me. Will this be pushed to tdebase
GIT
or did you build it as a standalone module?
I built as a standalone module:
- I don't know how far to strip the original sources and
support files to fit the kcontrol structure.
- The module is automake and I don't know enough yet to
convert to cmake.
- I don't know that everybody wants this. If placed in
kcontrol then nobody has a choice. If placed in applications then everybody has a choice.
There are two minor bugs that need attention, as mentioned in my previous post. I'll try to expand my noob C++ skills and take a look, but if I stumble then I'll file a bug report after we merge. If we want to keep as a standalone module then I'll need a spot created in applications before I can push, like you did with tqca.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Looks good to me. Will this be pushed to tdebase GIT or did you build it as a standalone module?
I built as a standalone module:
- I don't know how far to strip the original sources and
support files to fit the kcontrol structure.
- The module is automake and I don't know enough yet to
convert to cmake.
- I don't know that everybody wants this. If placed in
kcontrol then nobody has a choice. If placed in applications then everybody has a choice.
There are two minor bugs that need attention, as mentioned in my previous post. I'll try to expand my noob C++ skills and take a look, but if I stumble then I'll file a bug report after we merge. If we want to keep as a standalone module then I'll need a spot created in applications before I can push, like you did with tqca.
Tim
I need an applications/autostart module in GIT to push the files.
Darrell
Looks good to me. Will this be pushed to tdebase GIT or did you build it as a standalone module?
I built as a standalone module:
- I don't know how far to strip the original sources and
support files to fit the kcontrol structure.
- The module is automake and I don't know enough yet to
convert to cmake.
- I don't know that everybody wants this. If placed in
kcontrol then nobody has a choice. If placed in applications then everybody has a choice.
There are two minor bugs that need attention, as mentioned in my previous post. I'll try to expand my noob C++ skills and take a look, but if I stumble then I'll file a bug report after we merge. If we want to keep as a standalone module then I'll need a spot created in applications before I can push, like you did with tqca.
Tim
I need an applications/autostart module in GIT to push the files.
Darrell
git clone http://<username>@scm.trinitydesktop.org/scm/git/kcmautostart
Tim
Looks good to me. Will this be pushed to tdebase GIT or did you build it as a standalone module?
I built as a standalone module:
- I don't know how far to strip the original sources and
support files to fit the kcontrol structure.
- The module is automake and I don't know enough yet to
convert to cmake.
- I don't know that everybody wants this. If placed in
kcontrol then nobody has a choice. If placed in applications then everybody has a choice.
There are two minor bugs that need attention, as mentioned in my previous post. I'll try to expand my noob C++ skills and take a look, but if I stumble then I'll file a bug report after we merge. If we want to keep as a standalone module then I'll need a spot created in applications before I can push, like you did with tqca.
Tim
I need an applications/autostart module in GIT to push the files.
Darrell
git clone http://<username>@scm.trinitydesktop.org/scm/git/kcmautostart
Tim
I hate to pester, but could you upload the sources into that repository so that I can get Debian/Ubuntu builds started?
Thanks!
Tim
git clone http://<username>@scm.trinitydesktop.org/scm/git/kcmautostart
I hate to pester, but could you upload the sources into that repository so that I can get Debian/Ubuntu builds started?
Thanks!
Can I still do this after I resetting my local repo to April 10? I reset my local repo to help debug the kate/kwrite problems. I have already started a fresh rebuild based on that date.
Never mind. :-) Here is a tar.gz:
http://humanreadable.nfshost.com/trinity/patches/autostart.tar.gz
Here is the directory layout:
http://humanreadable.nfshost.com/trinity/patches/autostart/
Of course, these files are updated and patched for Trinity and no longer are the same as the original Ubuntu sources.
Nothing specific needed to build:
CFLAGS=$CPUOPT \ CXXFLAGS=$CPUOPT \ ./configure \ --prefix=${PREFIX} \ --sysconfdir=${SYSCONFDIR} \ --libdir=${LIBDIR} \ --mandir=${MANDIR} \ --with-qt-dir=${QTDIR} \ --with-qt-includes=${QT_INCLUDE_DIR} \ --with-qt-libraries=${QT_LIB_DIR} \ $DEBUG_AUTOTOOL_OPT || exit 1
I have to review my previous list posts to start a bug report. There were two minor bugs, none fatal.
Darrell
git clone
http://<username>@scm.trinitydesktop.org/scm/git/kcmautostart
I hate to pester, but could you upload the sources into that repository so that I can get Debian/Ubuntu builds started?
Thanks!
Can I still do this after I resetting my local repo to April 10? I reset my local repo to help debug the kate/kwrite problems. I have already started a fresh rebuild based on that date.
Normally you would check out that single GIT repository somewhere else (e.g. /tmp), upload the files to it, then just purge it.
Never mind. :-) Here is a tar.gz:
http://humanreadable.nfshost.com/trinity/patches/autostart.tar.gz
403 forbidden.
Tim
Can I still do this after I resetting my local repo to
April 10? I reset my local repo to help debug the kate/kwrite problems. I have already started a fresh rebuild based on that date.
Normally you would check out that single GIT repository somewhere else (e.g. /tmp), upload the files to it, then just purge it.
Too many things going on here today. Feeling stressed....
Never mind. :-) Here is a tar.gz:
http://humanreadable.nfshost.com/trinity/patches/autostart.tar.gz
403 forbidden.
I don't understand. Permissions look fine. Can you see the contents of the parent directory?
http://humanreadable.nfshost.com/trinity/patches/
Darrell
On Mon, Apr 30, 2012 at 10:02 PM, Darrell Anderson humanreadable@yahoo.comwrote:
Can I still do this after I resetting my local repo to
April 10? I reset my local repo to help debug the kate/kwrite problems. I have already started a fresh rebuild based on that date.
Normally you would check out that single GIT repository somewhere else (e.g. /tmp), upload the files to it, then just purge it.
Too many things going on here today. Feeling stressed....
Never mind. :-) Here is a tar.gz:
http://humanreadable.nfshost.com/trinity/patches/autostart.tar.gz
403 forbidden.
I don't understand. Permissions look fine. Can you see the contents of the parent directory?
I can access it fine. If you still haven't, give a try Tim.
Best regards, Tiago
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Mon, Apr 30, 2012 at 10:02 PM, Darrell Anderson humanreadable@yahoo.comwrote:
Can I still do this after I resetting my local repo to
April 10? I reset my local repo to help debug the kate/kwrite
problems. I
have already started a fresh rebuild based on that date.
Normally you would check out that single GIT repository somewhere else (e.g. /tmp), upload the files to it, then just purge
it.
Too many things going on here today. Feeling stressed....
Never mind. :-) Here is a tar.gz:
http://humanreadable.nfshost.com/trinity/patches/autostart.tar.gz
403 forbidden.
I don't understand. Permissions look fine. Can you see the contents of the parent directory?
I can access it fine. If you still haven't, give a try Tim.
Best regards, Tiago
Got it that time; uploaded to GIT.
Tim
Le 06/05/2012 01:05, Timothy Pearson a écrit :
Got it that time; uploaded to GIT.
Tim
Hello, you will find 2 files attached: - 1 patch to add French translations to kcmautostart (please push them to git) - 1 patch to allow build of kcmautostart with TDE 3.5.13 (backport), for those who want to package it in stable release.
It works nicely BTW :-)
Francois
Le 06/05/2012 01:05, Timothy Pearson a écrit :
Got it that time; uploaded to GIT.
Tim
Hello, you will find 2 files attached:
- 1 patch to add French translations to kcmautostart (please push them
to git)
Pushed to GIT in hash 035e48e.
Thanks for the translations!
Tim
-
Darrell Anderson -
E. Liddell -
Francois Andriot -
Tiago Marques -
Timothy Pearson