faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Kommander is Great
by ltmon on Tuesday 19/Apr/2005, @22:48
|
The links at the bottom of this page (in the "Useful Links" section) may help. At least, they helped me get started.
http://developer.kdewebdev.org/ |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
BAD Tutorial
by Fast_Rizwaan on Wednesday 20/Apr/2005, @01:04
|
http://hektor.umcs.lublin.pl/~mikosmul/computing/articles/kommander-introduction.html
The "Set Wallpaper" kommander tutorial is very confusing, I can't understand many things there. And there is NO FORMATTING (BOLD, italic, underline, color etc) to make the tutorial easy to understand. It looks that i'm looking to plain text. I guess lack of formatting is what makes that tutorial unhelpful :(
The Disclaimer says it all ;)
Disclaimer:
The author disclaims all warranties with regard to this document, including all implied warranties of merchantability and fitness for a certain purpose.
And Certianly it is not fit for learning kommander ;) It's good but lacking formatting.
|
[
Reply To This | View ]
|
Re: BAD Tutorial
by Eric Laffoon on Wednesday 20/Apr/2005, @10:39
|
Okay, so you don't like the formatting of the tutorial that a user contributed. Maybe you could offer to help them format it? This is community software, which means you get it for free and people in the community (supposedly all of us are) help out... However it often feels like it means that I sponsor Michal Rudolf to develop it and we keep waiting for others in the community to show up. We had some help with docs and we got some help with tutorials.
As far as actually learning it, do you want to? Certainly it takes less effort to point out what we haven't done with our limited resources, but we hope not too much more effort to learn to do something. ;-) First of all there are included "tutorial" examples where you can see how to use each widget in a simple dialog where it's easy to examine in the editor. (We need to make these more obvious for those getting binary packages.) There are docs on http://kommander.kdewebdev.org, though admittedly they are mostly out of date. We will be working on the docs soon I hope and we welcome anyone who wants to help there. However we also have a mailing list...
On the Kommander mailing list you can ask any question and get help from the developers and other users. You can ask about features or make suggestions. You can even submit dialogs you're working on for debugging, analysis and advice. Since most small dialogs are under 40K this is easy. In short, we will do penance for our doc shortcomings by serving you directly and personally consulting you until you understand how Kommander works. Funny how people often don't read docs and just fire off a question with Quanta... I personally would pick the free consultant. Kommander is my baby and I will go the extra mile to see it succeed.
Of course all of this overlooks that fact that once you have the basic theory down you need to know very little. There is a function browser you can call from the widget editor which will enable you to construct virtually every DCOP or scripting statement with a point and click, fill in the blank skill set. I use this all the time so I don't have to use the effort to remember things and not make typos. The basic concepts of Kommander are pretty simple so this means you can be making something pretty quickly.
So if you want to learn how to use Kommander it is in fact pretty easy. Granted it really needs better docs quickly and more tutorials but it is still very easy. I can attest from some of Pat's early emails with Katiuska that he absolutely did not think like a programmer coming to Kommander. After a few "silly" questions Pat was on his way. Interestingly I haven't seen a question from him in some time so to me this means that even though our docs are lacking, you can learn to program an application in Kommander in a matter of days with no more than half a dozen questions if you've never written a program of any sort in your life. It's been done and if someone else can do it so can you.
We are not trusting to luck for you to learn Kommander. We want you to succeed and we are doing our best to make tools available. If you want to succeed join our list and I promise you will be writing Kommander programs in no time. If you want to help that would be nice because we're working hard on what we consider essential improvements to Kommander too.
|
[
Reply To This | View ]
|
Re: BAD Tutorial
by anonymous on Thursday 21/Apr/2005, @08:48
|
I'd encourage you to setup a KDEwebdev MediaWiki page, for all KDEWebdev related stuff.
The media wiki looks good (nice appearance) and you even can encourage users to improve its contents!
|
[
Reply To This | View ]
|
Re: BAD Tutorial
by Ian Monroe on Thursday 21/Apr/2005, @10:43
|
Mediawiki has turned out really well for amaroK:
http://amarok.kde.org/wiki/index.php/Main_Page
Much of the documentation (like the FAQ) and all the translations have been written by users. Its also a nice way to hash out development ideas, as an alternative to a mailing list thread.
Actually the appearance of mediawiki is one of the problems... its complicated to integrate it the rest of site. Mediawiki was written for Wikipedia, so stuff like that isn't such a priority. However, mediawiki's syntax and ability to organize large pages is well polished.
That said, the Kommander people really do give great support on their mailing list.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
