Friday, November 14. 2008"If we have 2 or 3 good services at launch I will be happy"Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
That so many scripts already exist and that 3rd party folk are jumping on board is a great testament to you plugin framework.
Could you perhaps write a blog entry or even techbase tutorial on what your design considerations were and the technical aspects of implementing such a framework? The way that service extensible architectures such as this and the one in plasma really open up the environment for all kinds of creativity and I'm sure there are many other areas that could benefit!
This might sound extremely odd, but my advice to anyone who wants to build a framework like this is: Don't!!
This is not me trying to be funny though. The point is that I could never in a million years have designed the Service Framework, and if you look at the history of the services and the framework, you will realize that I really didn't. What I did do was build one service, the Magnatune store, and then extrapolate the best parts of that ( the parts that really proved useful, and not the parts that I thought in advance would be useful ). I then used these parts to build the next service, Jamendo.com, and then extracted some more bits. Doing development this way does cost you quite a few rewrites of stuff you have already done, but the benefit is that you don't start out by trying to look far into the future, trying to anticipate every possible feature that services some time in the future might require. This will in my experience only lead to you implementing tons of stuff that you do not really need, and missing bunch of features that you really should have been doing instead. By letting a framework evolve rather than designing it up front, it will likely become less complex and much better adapted to the stuff that it actually ends up being used for. I should stop now. You sort of hit on of my push buttons
There's actually a rule in game development which sort of fits this as well. It's a pretty simple one, which just reads "Don't write an engine, write a game"
Both good points and I do agree that when doing something from the first time it serves to take small steps and revisit past code as new ideas emerge. Maybe that in itself is a lesson worth sharing?
It is, but I think others have done so way better than I will ever be able to
Personally I think someone like David Heinemeier Hansson (the guy who invented Ruby on Rails) explains it very eloquently ( from http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html ): "That's why we hold the notion that "frameworks are extractions" so very dear in the Rails community. Frameworks are not designed before the fact. They're extracted when you've proved to yourself that an approach works. Whenever we get ahead of ourselves and try to leap over the extraction process, we come back sorely disappointed."
i hope that the "random" feature will be fixed by the release version... now isn't a great random between albums, it still in the same album...
and by the 2.1 i hope to see again the filter and queue functionality btw, great work and thanks for everything
I am not really sure what you mean about the random feature.
Filter and queue will definitely be back again soon, as many devs hold these features very dear.
I've add some albums to the playlist. With random=off when a track end it start the next one. But if i set random=tracks or album it's the same, when a track end it start just the next one following the order instead of select another track in a random way.
Another stuff i've noted is this: random:off, repeat: off, start a track, go to the end, it pass to the next one, while is playing set repeat:track, go to the end of the track, and it repeat itself...ok, for now is all right, but while is playing set repeat:off and go to the end of the track, it still repeat itself instead go to the next one. you have to stop and start the play manually. I'm using Amarok Version 1.90 and KDE 4.1.3 (KDE 4.1.3) (compiled by the gentoo ebuilds), so maybe with the last beta these are already fixed
Ramdom works for me. If random=track, it will jump all over the playlist, if random=album, it will play one album to the end, and then play a random album from the start.
Do note that 1.90 is practically ancient, and all of these issues are most likely fixed either in Beta 3 or in current svn.
Ok, perfect
I'm still with the 1.90 because gentoo doesn't have the latest beta in portage
The latest beta is in the kde-testing overlay, I had to keyword and unmask. This version fixed a lot of my problems.
I heard that there will be some basic video support in Amarok2. Is there any plan of creating a service for, say, PBS videos similar to NPR's audio library?
Yes, this will very likely be possible in later Amarok 2 versions.
In 2.0.0 we decided to disable the Video applet, as it is not quite finished yet. |
Amarok LinksCalendar
QuicksearchCategoriesBlog Administration |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||