libs vs. apps

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

libs vs. apps
by Thorsten Schnebeck on Monday 22/Oct/2001, @08:04

Yes, there are quite some very nice universal players like xine, mplayer...

This is not about "assimilation" something into KDE.
This is about integration into KDE. We need a plugin-like player/arts-object/component also for integration in apps like kpresenter.

So maybe better go with a pool of libs than with one app (?)

Bye

Thorsten

Related Links

·   Articles on Community and Events
·   Also by Thorsten Schnebeck
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: libs vs. apps
by Carbon on Monday 22/Oct/2001, @16:14

Well, this being Open Source, we can have our cake and eat it too. We can just re-integrate any given codec as an aRts library, and then it should run (theoretically :-) in any app using KParts, including Konqi and KPresenter. Of course, (in KPresenter for example) doing things like making sure movies play at the right time in presentations, grabbing the first and last frame and using them for in and out effects, etc etc, would require special coding, but once that is done, you could swap out the backend for another fairly easily.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Feature freeze: You're allowed to add new bugs, but no new features." -- Richard J. Moore
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.