Yo, and Ian's Roadmap
hydrogen at notyetimplemented.com
Wed Sep 13 17:26:04 UTC 2006
On Wednesday 13 September 2006 1:21 pm, Dan Meltzer wrote:
> On Wednesday 13 September 2006 7:12 am, Jeff Mitchell wrote:
> > First off:
> > Hawai'i FTW
> > Second, I read Ian's proposal to shelve 1.4 after 1.4.4 and
> > concentrate on 2.0 and I think it's a good idea...1.4 branch seems
> > pretty stable these days (unless something's changed in the last five
> > days while I've been gone...there have been 75 commits...). Two
> > suggestions, which I'd put in the wiki but I can't log into it now:
> > 1) Playlists: Move to XSPF instead of outdated, sucky M3U
> > 2) If someone has been working with KDE4 development and wants to
> > write a guide for how to get set up for an Amarok 2.0 development
> > environment, that'd be swell. I remember when I dealt with KDE from
> > SVN (when 3.5 was being worked on) that I had to create a separate
> > user account with a separate KDE build. I'm assuming that this would
> > be required again, but if someone knows the best way to go about this,
> > it'd be great to have that info available to all developers. Gentoo
> > ebuilds would be especially great...
> http://developer.kde.org/build/trunk.html is probably the best bet for the
> guide. it has some links in it to other useful things
> A few other links that will probably be helpful when the time to port
> actually comes
> There is a whole directory in svn with porting scripts of various use also,
> I can't remember where it is at the moment though.
"Porting to Qt4/KDE4
You can use several helper tools while porting an application to KDE4.
The first one is shipped with Qt4, and it's called qt3to4.
Example of its usage:
qt3to4 myFiles.cpp myFiles.h
The others one are located in KDE SVN, in the kdesdk module. The precise
location is kdesdk/scripts/qt4. They will help you to adapt the code to the
API changes of kdelibs."
> You probably want to avoid using kdesvn-build at the present because it
> uses unsermake and not cmake, and porting to cmake is one of the bigger
> things to do.
> I have a mostly working kde4 test environment up so I can help test things
> out as usual (and probably be just as useless too!)
> > Also, I will probably end up stabbing myself in the eyeball for saying
> > this, but I am volunteering to work on Amarok/Windows. Mainly because
> > I have a box with an Athlon X2 4200+ dual core proc in it, and I was
> > planning on keeping it Windows-only (or Windows-mostly). And that
> > mainly because it'll make my girlfriend really happy...
> > Anyways, if I have to be rebuilding half of KDE every day to keep up
> > with KDE4 development I may turn it into a dual-boot box anyways as
> > it's quite slow to rebuild all of kde on my laptop, but otherwise
> > it'll be a fast Windows box, so I can work on the Windows side of
> > things as well as other more normal Linux programming...
> > --Jeff
> > _______________________________________________
> > Amarok mailing list
> > Amarok at kde.org
> > https://mail.kde.org/mailman/listinfo/amarok
> Amarok mailing list
> Amarok at kde.org
More information about the Amarok