By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 518

Summary:	Amarok-trinity by Clementine authors development.
Product:	TDE	Reporter:	Michael Martin <michaelmartin007>
Component:	tdemultimedia	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	bugwatch, darrella, fatzer2
Priority:	P5
Version:	3.5.13 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Michael Martin 2011-09-24 18:43:26 CDT

Let me tell you first that Trinity desktop environment was born as a fork of kde 3.5.

In this way Clementine music player was born from the code of Amarok 1.4, just
the same Amarok-trinity. I think that you, TDE developers could email to clementine developers offering development of Amarok-trinity. Maybe renaming it as Clementine-trinity. 
I think that with it you gain more developers for the TDE because amarok-trinity should have the clementine authors as maintainers. 
Clementine developers would see their official music player as the default for TDE. I think too that for a developer is a good reason and proud to see his/her app as default in a desktop environment.

Thanks.

Comment 1 Alexander Golubev (Fat-Zer) 2011-09-24 19:24:07 CDT

I thought about this too... but i'm not sure that's a really good idea, becouse clementine is copletly ported to qt4 and it loosed all kde integration. Also it's ton full-feature yet...

BTW it's still not pink see bug #219 in clementine bugzilla =)

Comment 2 Michael Martin 2011-09-25 07:46:11 CDT

(In reply to comment #1)
> I thought about this too... but i'm not sure that's a really good idea, becouse
> clementine is copletly ported to qt4 and it loosed all kde integration. Also
> it's ton full-feature yet...
> 
> BTW it's still not pink see bug #219 in clementine bugzilla =)

I understand. But I think the clementine developers know the code of amarok 1.4. This idea it's not a direct substitute of amarok-trinity for clementine. We all know that Clementine has no integration with kde nor TDE. However clementine developers have the knowledge to make a new clementine-trinity from amarok-trinity code without losing its integration with the TDE. 

http://www.trinitydesktop.org/wiki/bin/view/Developers/RoadMap

You can read here: "Add Qt4 support to Trinity Qt Interface 3.5.13 60+% Now Mandatory". This date from 19 Jun 2011. I guess now would be almost complete.

Clementine developers could work then with the code of amarok-trinity 3.5.13 compiled with qt4. In this way they could start adding code to amarok-trinity from clementine and transform it. 

The result would be clementine-trinity. Clementine with full integration with the TDE.

Comment 3 Timothy Pearson 2011-09-25 13:45:01 CDT

(In reply to comment #2)
> (In reply to comment #1)
<snip>
> 
> http://www.trinitydesktop.org/wiki/bin/view/Developers/RoadMap
> 
> You can read here: "Add Qt4 support to Trinity Qt Interface 3.5.13 60+% Now
> Mandatory". This date from 19 Jun 2011. I guess now would be almost complete.
> 

The roadmap was/is badly out of date.  Qt4 integration has stalled due to continual problems with Qt4 itself which we have absolutely no control over, and were turning the Qt4 port into a sinkhole of developer time/resources.

> Clementine developers could work then with the code of amarok-trinity 3.5.13
> compiled with qt4. In this way they could start adding code to amarok-trinity
> from clementine and transform it. 
> 
> The result would be clementine-trinity. Clementine with full integration with
> the TDE.

I don't think this is a good idea.

Tim