Siduction Forum
Siduction Forum => Experimental => Topic started by: jackyohh on 2014/02/09, 12:21:38
-
Hi,
i recently found a great placement for kmenu, called homerun
http://blogs.kde.org/2014/01/29/homerun-120 (http://blogs.kde.org/2014/01/29/homerun-120)
(http://www.eikehein.com/kde/blog/homerun120/homerun_kicker_1.png)
- flawless Plasma integration
- it's as fast as the old kmenu (and way fast than the modern kmenu with its submenus)
- with search function (including nepomuk)
- you can place favourite apps in homerun
This app is really great! I hope it will get fast into debian!!
-
sea homerun
hdhomerun-config - Konfigurationswerkzeug für Silicon Dust HD HomeRun
libhdhomerun-dev - Development library for Silicon Dust HD HomeRun
libhdhomerun1 - Library for Silicon Dust HD HomeRun
-
jackyohh, that one seems indeed well integrated and clean.
Two others kicker-replacements worth a look are lancelot and appmenu-qml. Lancelot is in the repos, installable via apt-get install plasma-widget-lancelot, it has more options but for me sometimes looks a bit cluttered. Appmenu-qml is just a plasmoid downloadable from kde-apps and intallable via 'add plasmoids'.
Lancelot: http://userbase.kde.org/Lancelot
appmenu-qml: http://kde-apps.org/content/show.php/AppMenu+QML?content=146098
spacepenguins appmenu-screenshot here http://forum.siduction.org/index.php?topic=7.msg23954#msg23954
-
I use lancelot for some years now, but homerun looks very good. I'll give it a try. Thank you for the hint!
-
yeah i know lancelot and as far as is see appmenu-qml is quite similar.
both have one big usability problem (imho). you have to click to watch submenus/enter. AND you have to click AGAIN to go back into rootmenu. that's so annoying!!
the classic kmenu with its hover functionality is so damn fast.
nowadays developers pay more and more attention to pretty UIs and less to a quick accessibility. :o
so its nice to see that homerun is a good mix of both!! :D
-
So should I expect a plasmoid after building it? Cause that is not the case. Looking for a way to start this...
greetz
devil
-
.... you have to click to watch submenus/enter. AND you have to click AGAIN to go back into rootmenu...
For appmenu you are right with that, lancelot is configurable to no-click-behaviour (http://userbase.kde.org/Lancelot/Discover_Lancelot#No-click_activation). But still, every time I try lancelot I come back to Kicker after one day.
-
I just built homerun from the ubuntu sources and it works fine.
greetz
devil
-
Since I haven't used my new install for any kind of development yet, I had to install a few dev applications, then, I finally got it built.
There were 2 plasmoids that got built, a kicker and a launcher. The launcher made KDE look like Gnome 3, something I'm not crazy about. BUT - The kicker is a visually well done mix of the Classic Menu and the Application Launcher, I liked it right away.
I'll just have to play with it for a while to see if anything bugs me. So far, it looks good.
-
The homerun kicker looks promising, I agree. I have not yet tested it - is it possible to have an icon size of 32 for the application/submenu entries?
Lancelot never was an option for me because the icon size is not configurable and 22 is too small for me. Apart from that it really looks like a mess with those different icon sizes and different spaces and it's somewhat slow.
My favorite still is the AppMenu QML with three panes. I don't need a no-click menu but I need to see "everything". It is more like the good old KDE3 TastyMenu (and it looks so cool in transparent blue with the BlueTintGlass plasma theme ;) ). BTW: in the AppMenu QML you don't need to click to go back to a former pane as in kickoff, you just drag the content back and forth. The only issues are that you cannot drag items to the panel/desktop and that the searching is very slow.
-
Homerun kicker is a nice and functional launcher for KDE. I replaced Lancelot and kmenu with it approximately 2 months ago in my SolydK partition. This distro is gearing toward replacing the default launcher in favor of kicker.
-
We might also go that way.
greetz
devil
-
Could the homerun 32-bit and 64-bit packages be made available in the siduction repo, for testing purposes?
-
Could the homerun 32-bit and 64-bit packages be made available in the siduction repo, for testing purposes?
+1
-
good Idea Dibl!
+1
-
I just did a new siduction install and realized that the homerun kicker is still not in the repos. Is there any chance of it getting included soon?
-
I would advocate that, been using it for ~ 3 months and like it best of the program starters. Although milou can also start apps.
greetz
devil
-
I gave it a try now but don't use it anymore. Only the main menu looks good, the rest looks very very cluttered as the categories don't have any submenus and ignore the submenus set in the menu editor.
Do I miss something? There is no way to increase the icon size, there is no way to sort the entries, entries appear twice because they originally are in different submenus, there are categories with menus twice the height of the display because of missing submenus, the entry names have no description, I don't really find things in a quick and easy way. Nice try - but needs a lot of improvement IMHO. If it would be like the classic fly-out menu with its subcategories combined with this modern look it really would be great.
I'm using - no - I have installed version 1.2.0+git20140206, maybe there is a newer version which allows more customization?
-
I like the look of this but currently am completely satisfied with the KDE Classic style menu (I don't like the other newer style one).
What advantages are there from default apart from "pretty" ?
-
I like homerun because it seems to have the best parts of classic and the new menu. One really doesn't see how useful it is, or, how nice it looks, until you have it installed and play with it for a while. I was also a fan of the classic style menu, until I started using homerun. Now I put it on all my installs.
Link if curious: https://blogs.kde.org/2014/01/29/homerun-120
-
OK, I'm curious but not very experienced with building stuff. Any ideas what is wrong here?
roger@brain:~/Downloads/homerun-1.2.0/build$ cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..
-- The C compiler identification is GNU 4.8.3
-- The CXX compiler identification is GNU 4.8.3
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (message):
ERROR: cmake/modules/FindKDE4Internal.cmake not found in
/home/roger/.kde/share/apps;/usr/share/siduction-settings-kde-december/share/apps;/usr/share/kde4/apps
Call Stack (most recent call first):
CMakeLists.txt:9 (find_package)
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring incomplete, errors occurred!
See also "/home/roger/Downloads/homerun-1.2.0/build/CMakeFiles/CMakeOutput.log".
Here's the whole CMakeOutput.log -
http://pastebin.com/wGak6AZf (http://pastebin.com/wGak6AZf)
-
dibl: good idea - but false question. The right question would be: Can someone stand up and pack and maintain this thing for siduction. And please don't point to towo`, santa or me.
-
OK, I'm curious but not very experienced with building stuff. Any ideas what is wrong here?
Sure:
$ apt-file search Internal.cmake
kdelibs5-dev: /usr/share/kde4/apps/cmake/modules/FindKDE4Internal.cmake
libphonon-dev: /usr/share/phonon/buildsystem/FindPhononInternal.cmake