briank wrote:Looks like okular is out, they had disabled kns2 as they felt it was outside the scope of what they wanted to build. Time to start on Plasma Weather I guess.

Yes, I talked to Albert who maintains Okular and it just doesn't fit. Maybe it would be interesting to start a "Book Management" application including automatic download of files.
Thanks for your effort in any case.

For all of those interested in Marble, let me run a short advertisement
You should visit #kde-edu on freenode and talk to jmho. He offered further mentoring and junior jobs.

Ok, I wrote today as official starting date of the Klassroom, so welcome everybody again!
I was happy to see that some people already got started without my help and were successful in porting the applications, so it doesn't seem to be impossible.

Now I hope we have several people left that didn't do all their homework ahead of time.
Let's get started!

First thing is to build the applications from source.
I'll try to sum up again, what is necessary, and how I'd do it, though there are probably many ways to get something compiled. For now I'll stick to applications in one of the base KDE modules, such as edu/games/graphics etc. The idea is that you can use your system kdelibs and kdelibs-dev packages to not have to build kdelibs. Some KCMs and Plasma applets will need kdelibs and/or kdebase which might be a little more tricky (no big problems, I just want to start as simple as possible here).

If anyone needs help, as always, ping me in #ghns on freenode irc, or post in this thread. And please post a "I'm still alive" even if all goes well that makes me happy and I know I haven't left you behind.

Hi Frederik: still-alive-ping

Compiled Emoticons-KCM yesterday and got it running with kcmshell-kde4. Managed to port it to use the KNS3-Dialog, but nothing more.

Does the same provider-url work? Or are there server-side changes needed?

Ciao,
Daniel

Ok, here is a getting started tutorial that duplicates some information found on techbase.
http://techbase.kde.org is where you can find a lot of information for KDE development. You can also add missing information (or poke me and others to add information that is missing if you're not yet confident how to edit it).
On techbase the first link is what we care about today: Setting up a KDE development environment
http://techbase.kde.org/Getting_Started
Since there is lots of material and we may not even need lots of it, I'll try to walk through the necessary steps with you.
Tell me what help you miss most, so we can improve in the future.

Here is a little overview, where you can find the source:
First you can simply look at the subversion server where the KDE source code is available in a web browser:
http://websvn.kde.org/
Here is what you see:

• trunk: this is where most development happens and what we'll focus on. This will become KDE SC 4.5 at some point (and the next release and so on...)
• branches: either ongoing work that will later end up in trunk, or the work branches for older KDE versions (KDE 4.0 to 4.4 for example)
• tags: Tags - this is what has been released as a certain version and usually fixed, no work should happen in here

For now trunk/KDE http://websvn.kde.org/trunk/KDE/ is what we are interested in - there you find kdelibs, kdebase, kdegames and all the other KDE modules that are released together.

I will use KDE Edu as example now, if you work on games for example, simply replace all "kdeedu" below by "kdegames".
Now is also the time to get some packages for: subversion, cmake and g++, check that you have them and take a look at http://techbase.kde.org/Getting_Started/Build/KDE4#Required_packages_from_your_distribution
to see what you might need.

I would not recommend creating a separate user account, but if you feel more comfortable that way, you can of course do that.

I suggest you create a folder "kde" in your home directory.
Now to actually check out the source code locally, here is what you need to do:

Code: Select all

mkdir -p ~/kde/src
cd ~/kde/src
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdeedu

This will download quite a bit of source code into a directory kdeedu.

Ok, before this post gets too long, I'll break it up and continue with a build my app post next.

* Hans is also still alive

I have trunk compiled, but unfortunately I don't think I'll have time to work on it until next week. On the other hand, seeing how others have already accomplished the task, I might be able to do something tomorrow if I get too bored of writing my report..

It would be good to know how to create a patch. Is this the recommended way, i.e.

Code: Select all

svn diff > patch.diff

?

Now that we have the source code, it's time to start building it. You need the build dependencies. You can either figure out by hand what you need, or try to take advantage of your distributions tools.
I currently only know the Debian/Kubuntu way to automatically fetch needed development packages from the top of my head:

Code: Select all

apt-get build-dep kdeedu

See the previous post, get cmake and g++ and maybe some other packages (let me know what was missing, I'm just making this up as I go).

Ok, I assume you have a kde module checked out as for example /home/frederik/kde/src/kdeedu.
One way is to simply create a build subdirectory in the source dir, that is what we'll do next. First we want some environment variables set up though:

Code: Select all

export KDEDIR=$HOME/kde/kdeinstall
export KDEDIRS=$KDEDIR

export KDEHOME=$HOME/.kde4-svn

export KDETMP=/tmp/$USER-kde4-svn
mkdir -p $KDETMP

export KDEVARTMP=/var/tmp/$USER-kde4-svn
mkdir -p $KDEVARTMP
export KDESYCOCA=$KDEVARTMP/kdesycoca-custom

export PATH=$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH

export XDG_DATA_DIRS=$KDEDIR/share/:/usr/local/share/:/usr/share/
export XDG_CONFIG_DIRS=$KDEDIR/etc/xdg/:/etc/xdg/


I would recommend you put the few lines above into a file that you can use later instead of typing that much every time. A simple solution is to have the needed lines in a text file and just type "source kde_devel_env".

Once you have that set up go into ~/kde/src/kdeedu and

Code: Select all

mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$KDEDIR -DCMAKE_BUILD_TYPE=debugfull
make
make install


if this worked, you should have an installation of kdeedu in ~/kde/kdeinstall.
You can start any app from the bin dir:

Code: Select all

~/kde/kdeinstall/bin/parley

Hans wrote:It would be good to know how to create a patch. Is this the recommended way, i.e.

Code: Select all

svn diff > patch.diff

Yes, in order to produce a patch, that is just the difference of what the svn server has and the code you have on your harddisk, use svn diff. You can send this patch to a mailing list or post it on http://reviewboard.kde.org

Still alive.
Although as I'm app-less at the moment I believe I'll have a go at writing that book management app.

briank wrote:Still alive.
Although as I'm app-less at the moment I believe I'll have a go at writing that book management app.

Both makes me happy Let's talk on IRC about this idea.

I'm still alive too!

I updated Kalzium to use the KNewStuff3 dialog, but noticed it doesn't display anything using the URL, http://data.kstuff.org/cgi-bin/hotstuff ... e=kalzium; the KNewStuff2 dialog in the current version of Kalzium doesn't either. Most of the KNewStuff URLs seem to end with a providers.xml file, could there be a bug somewhere regarding resolving dynamic URLs?

I'm about to leave for school, but will check back in a couple hours.

deltaecho wrote:I updated Kalzium to use the KNewStuff3 dialog, but noticed it doesn't display anything using the URL, http://data.kstuff.org/cgi-bin/hotstuff ... e=kalzium; the KNewStuff2 dialog in the current version of Kalzium doesn't either. Most of the KNewStuff URLs seem to end with a providers.xml file, could there be a bug somewhere regarding resolving dynamic URLs?

I just tested, using the stand alone knewstuff app:

Code: Select all

khotnewstuff4 kalzium.knsrc


and for me it worked, but the server (data.kstuff.org) seems to be ... uhm... slower than slow. So after about a minute something did show up.
data.kstuff.org does implement two APIs for get hot new stuff - the XML files you accessed and a SOAP API that was intended to replace them. In the meantime people found out that SOAP is not much fun and so openDesktop.org for example implements a REST API instead.
The SOAP API did never work on the client side, so for now we need to use the static XML.
In this case the benefit of porting to knewstuff3 is not as big as in the case of using openDesktop.org for the data. I hope that kstuff will catch up. Having the new dialog everywhere is still desirable.
Can you check again, if it's just slow?

still here;)

Is there an easy way to just compile one small application, i.e kanagram?
The last day i could compile marble, but faild to compile kanagram (Which shoulb be small and easy:D ).

By the way, tanks for the intruduction it alredy gave some usfull tip's. Kde-edu ist compiling...

frederik wrote:Can you check again, if it's just slow?

Yep, that's what it was -- I had to wait ~15 seconds before I got any results.

Here is the diff: http://pastebin.com/f408df1e3

_eti_ wrote:By the way, tanks for the intruduction it alredy gave some usfull tip's. Kde-edu ist compiling...

Hi _eti_, does that mean you have KAnagram working now? Please let me know what more help you need