KDissert is KDE's mindmapping tool. App of the Month interviews KDissert's author Thomas Nagy about why he started it, the relationship to BKSys and his plans for the future. There is also an overview to help you get started using this exciting application and for the first time we have a Flash Demonstration of KDissert in action. Enjoy app of the month in Dutch, English, French, German and Turkish.
Dot Categories:
Comments
klik://kdissert works beautifully on my SUSE-10.0 box!
I'm using SuSE 10.0 and when I type "klik://kdisser", Konqueror says "Protocol not supported: klik". Wassup?
I'll try a wild guess, have you klik installed?
Take a look at http://www.opensuse.org/SUPER_KLIK
FIRST, it is "klik://kdissert" (and not "klik://kdisser")
SECOND, you need to have the klik client installed (less than 20 kBytes, less than 20 seconds of effort) (*)
------------------
To install the klik client:
* Hit "[alt]+[f2]"
* Type "wget klik.atekon.de/client/install -O -|sh"
* Hit "Enter/OK"
* Follow instructions on screen
Done.
That install script is not exactly foolprof, or in other words it fails for me. The first error I get is for not having Xdialog, easily solved by making link to kdialog. Anyway automatic selection of kdialog/gdialog(?)/Xdialog could be an idea.
The second error I got was in the post install part, the folowing error:
sh: line 512: firefox: command not found
Same thing here really, perhaps looking for Konqueror too, and some distros use mozilla-firefox rather than simply firefox. And some may prefer the Mozilla suite rather than standalone firefox.
It would help debug this if you told the exact distro version you tried klik on....
(And yes, "automatic selection of kdialog/gdialog(?)/Xdialog" is as good an idea that it even is already implemented. It just happens, that in your (exotic?) case it didnt work out as intended...)
I had not really expected klick to work on my system anyway, it's not so much exotic as a case of mixing old and new. But with statements like this "less than 20 kBytes, less than 20 seconds of effort", there really are no reasons for not trying:-)
I'm running a old Mandrake 10.1, with KDE svn in /opt. Used ftp install so I have only installed the things I need, looks like Xdialog never has been needed:-). Perhaps having kdialog in /opt was the reason it was not found, anyway I'm not sure spending time debuging it are worth it:-). Except for the issues With XDialog and firefox, it did install.
I had the same problem. I had to install Xdialog, since it wasn't already on my system (Debian etch, upgraded a few times from, oh... potato, originally? :^) )
If kdialog is in your $PATH, this would help too:
"DIALOG=kdialog wget klik.atekon.de/client/install -O -|sh",
or
"DIALOG=/opt/bin/kdialog; export DIALOG; wget klik.atekon.de/client/install -O -|sh"
or similar
Works nice on suse 9.3 as well :)
And fast, before I knew it, kdissert popped up on my desktop
When I go to that URL, a window appears telling me it's going to download an RPM from http://ftp4.gwgd.de/ but then nothing happens. After trying a few times, I discovered I had some suspicious looking files in my home directory, "index.php?mid=23403", "index.php?mid=23403.1", etc. Looking inside, it looks like some page from a music download website called "chimp3.com". WTF???
This recipes uses as its input file an RPM from http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/packages/Office/kdissert/ to create the klik .cmg from (most others use a set of .deb files).
Unfortunately, minutes after createing and testing the recipe, the version was bumped by Guru, the RPM packager. He removed the 1.0.4 an made a 1.0.5 available. So the recipe's link wasn't valid any more. The index.php file you received was an error in the recipe: there is a line that is usually commented out (and which we use for debugging only) which may point to various other non-klik related sites (such as the chimp3 one). Sorry for the inconvenience.
(You can easily verify/control what the .klik script does, by running it from the commandline like this:
user@host:~> sh -x $HOME/.klik kdissert
I hope this helps.)
It works beautifully on my SuSE 10.0 box. There is one minor flaw. Spellchecking does not work. Spellchecking is done, but not saved. Anyone with suggestions?
Wolfgang
I am amazed by the breadth and quality of available applications for KDE. It's a good sign when you start to see real diversity in the applications, not only image viewers and mediaplayers.
As for mindmapping I remember looking at it when I was a student, but back then the old pen and paper version was really no good with my workpattern. KDissert looks much more practical, and to looks like it concentrate more on aiding the workflow than doing mindmaps for the sake of doing mindmaps. Looks flexible and userfriendly, I definitely have to try it out.
One question tho, is it possible to make hierarchical maps with it? Having boxes representing submaps and a easy way to navigate up and down in the structure. Since I find it usefull to work on problems that way and it looks like more complex maps soon would clutter the workspace.
Since I know makefies and automake are evil, everything I hear about BKSys fills me with joy. I'd love to see a HOWTO or step by step guide on how to convert a automake project to use BKSys(perhaps aimed at those of us with lesser skill in the black art of buildsystems:-).
Perhaps it is merely a reflection of my nay-saying personality, but I would like someone to explain to me the benefits this visual tool over the form of a purely textual outline.
I cannot see any added benefits and an outline can be developed with many readily available tools. Even pictorial elements could be added to an outline, if needed.
Mind maps benefits are described all over the web, see for example http://members.optusnet.com.au/~charles57/Creative/Mindmap/Radiant.html
A purely textual outline will always impose a greater degree of structure, in the way the outline is created and developed. This tool allows using a much more unstructured approach. It will give more flexibility in the initial or brainstorming phase. And you can export it to a textual outline, at the point when switching to that mode of working is more appropriate.
But I guess it mostly boils down to your personal workpattern and style if you will get any benefit out of it or not. Some people are more visually oriented than others, perhaps making this approach better suited for them.