As I’d rather show the participants around git and not just “how the hell do I use vimdiff?!” I’m posting this little snippet on howto use KDiff3 on windows. Of course we’re probably going to have quite simple conflicts that could easily be conflicted without tooling but it’s nice to have one prepared when you need one. So, this is what you need to run KDiff3 on windows as a mergetool (paste this inside of your .git/config file)

[merge]
    tool = kdiff3

[mergetool "kdiff3"]
    path = C:/Program Files/KDiff3/kdiff3.exe
    keepBackup = false
    trustExitCode = false

And you’ll need to download kdiff3 for windows of course, this can be done on their sourceforga page. And that’s basically it. I’ll reconfirm that this really works tomorrow as I’m getting somewhat tired already… Well then…

Gundam fighters set, ready….. goooo!
* stupid quote from  G Gundam ;-)

As my blog is being listed on http://www.dworld.pl/Blogsfera (and for other obvious reasons) I didn’t want all my tweets to be translated “1 to 1″ to plain old blog posts since this would cause each of my tweets (which can be silly sometimes (but quite rarely!)) to land on dworld, which they obviously shouldn’t as it’s only an place for Java/Development oriented posts. Also I’d rather they’d take less space, and would skip all the categories/tags – it’s all in the tweet, so why repeat it again and again?

So… let’s start by importing tweets into wordpress. There’s an great plugin for that, and it’s called Tweet Import by skinju. Just install it and set it up to fetch your tweet’s at an regular basis. Ok, we’re done with step 1 – but neither are the current tweets smaller or ommitted in the rss feed. Let’s start by filtering them out from the rss feed:

Open up the file /wp-content/themes/default/functions.php and go to the end of the file, we’ll add an filter here. Please note that in step 1 you should have created an “twitter” category all tweets should be marked with. Let’s assume this category has an ID of 131, then the following code would do the filtering for us:

It’s a very nice trick, and it’s explained more in detail here. The code is really simple, so no explaining here and let’s go and tune our view (yup, the RSS feed is already fixed!).

To setup our view to work a little different for tweets than for posts, well have to edit: /wp-content/themes/maze/index.php so open it up in your favourite editor and add such an if statement inside an post’s while statement:

Ok, with this done let’s write the else part…

(You can complain about the in line css styling if you want later, I know it’s bad but this wordpress theme is a mess anyways… ;-)) Let’s have a look at the more important parts of this code part. You’ll notice that I’m using some weird get_post_meta() function. It’s an method that fetches additional information that each post CAN but doesn’t have to have. And as the TweetImport plugin does fill an post with a lot of useful tweet data, such as post time and tweet url – that’s what I’m fetching here. The rest should be quite self explanatory, there are bit’s of hardcoded “ktosopl” in there but hey – it’s just my blog and I’m a busy person ;-)

Hope you found this post interesting and maybe you’ll implement the same thing on your blogs…? :-)
Cheers!

PS: Oh, and if your interested in talking on one of your upcomming JavaCamps – feel free to contact me or anyone from the java.pl team, we’re looking forward to hearing from you. The nearest meeting will probably be organized around 23′th or 6′th…

Helo again! Today’s post will be an super quick usage scenario for NetBeans Platform Lookups – the probably most essential part of the Platform. An super simple explanation of them is “an Map<Class, Object>”. Sounds simple right? Well it is, and it’s quite powerful at the same time. It enables you to loosely couple parts of your app, create extension points etc. Another use case is passing some date around in the app, but you don’t know where the modules interested in this data are (because you’re loosely coupled, right?). In an app I’ve been writing for my Uni since some days, I’ve used the Lookup to do exactly this – pass data from an algorithm to an LineChartDrawer that then will update it’s chart each time the data is being updated.

This is going to be quite similar to an  Observer Pattern implementation, but using the lookup as notification mechanism. Let’s start out with our Algorithm class (and module – note that this module is not dependent on the chart drawing module!)

The code is well commented for this post so take a moment and read through it. It’s just some pieces of the actual class we’re using – so no actual computing stuff is shown here, let’s focus on the lookups. Note that I’m getting the TopComponent that I’ll add as an listener “by name”, it’s super simple but would you need to “find some implementation of some drawer interface” just use an lookup and get the instance, or even all the instances of such interface implementations. That said, this solution is not the most universal here (getting the instance) but it’s good enough for our app since it’s a very small application. No let’s look at the “Observer”, better named as “LookupListener”:

That’s about it. We simply have an resultChanged() method that will be called if the contents of the resultset are changed. We might also want to arr more lookups to be observed, so it’s better to check this instanceof I think than not, since there might be some unexpected stuff inside of it…

All in all, you write an Lookup.Provider and LookupListener, implement both’s methods and then at some place in your app hook them up. It doesn’t really matter “who looks for who” as long as it’s consistent and logical. In this case, the algorithm is looking for people interested in his data. Note that at any moment in time, we can add another listener, no problems here. Note that the Lookup.Provider and LookupListener are quite similar to the Observer and Observables mentioned before.And the good thing is, the algorithm does not know about any concrete drawer, and the drawer has no idea about some algorithm. They just have one shared API module – the toolbox, in which there is the DataTransferObject we’re using to pass the data from one to another – yay, an loosely coupled system. (yeah, I know our code is tightly coupled at some other places, but this part is quite ok :-))

If you have anything you’d like to comment on this code, feel free to do so. It’s just parts taken from http://github.com/ktoso/TravelingSalesman-NBP our implementation and visualization of the Traveling Salesman Problem being solved by Genetic Algorithms.

For more information about lookups goto: a nice post by Anton Epple on dzone.com or to Geertjan’s post with some good links or http://www.antonioshome.net/blog/2008/20081023-1.php

Anyways, I’m using github most of the time, but now I’d like to hava a non public repository (yet remote) for some small project. I’ve been commiting to a local git instance from the begining of this project so just pushing it into a new repo will be really simple.

I wanted to have som easy to administer localozed git to serve hit hosting for my friends etc. So this is how I did it:

On server:

Now we can do all the administration without being logged in into our server – just by using git!

You can then just pull/clone this repo:

git clone git://stratos/bla.git

Yeah, this post isn't much of an discovery - yet I wanted to show you how SIMPLE and SCALABLE a simple git repository can be. For mor information about git and gitosis see: a simple google search

Dzisiejszy temat to obracanie całego filmu:

Masowe obrócenie filmików z wakacji teraz nagle stało się proste czyż nie? :-) Czemu się tym zainteresowałem można by się spytać… otóż obracałem filmik nagrania mojej nowej popierdółki w j2me: Xplode. ale to już materiał na kolejny wpis.