[Pidgin] #34: Voice/video support
Pidgin
trac at pidgin.im
Sat Dec 1 22:01:42 EST 2007
#34: Voice/video support
--------------------------+-------------------------------------------------
Reporter: MarkDoliner | Owner: seanegan
Type: enhancement | Status: assigned
Priority: minor | Milestone: Patches welcome
Component: libpurple | Version:
Resolution: | Keywords:
Pending: 0 |
--------------------------+-------------------------------------------------
Changes (by rekkanoryo):
* milestone: => Patches welcome
Comment:
Replying to [comment:58 pellingert]:
> isnt the meaning of open source, sharing code with other developpers?
> so the code is there (amsn, copete, ...) you just have to integrate it
into pidgin and give the original developpers some credit in the about
screen.
> and if you do not want to integrate it, for what reason is there this
years old promisse to have tis function in a near future version? just to
attract users to your project with face promisses?
[[BR]]
Why is it that no one ever understands that we can't just cut and paste
code from another client?! Code structure, library usage, difference in
programming languages used, and a multitude of other factors make it
difficult (at best) or nearly impossible (more like reality) to reuse any
of the existing code in other clients. Using them as a "reference" isn't
exactly easy either, as almost no other clients keep their protocol code
completely separate from the UI, which means we would have to understand
the conventions of not only the base libraries, but the UI toolkits as
well '''and''' have to pick out useless UI element code from the actual
protocol implementations that we would need.
Again, as has been said a hundred thousand times over, we want a core/UI
split API, such that libpurple uses the gstreamer and farsight libraries
and has absolutely no UI-specific code whatsoever. The API also has to
take into account that we support more than 10 protocols--there can be
nothing protocol-dependent anywhere in libpurple except in the protocol
plugins themselves. There are other significant design issues that have
to be considered as well.
It doesn't really matter that aMSN, Kopete, or half a million other IM
clients have these features. Developers who cared implemented those
features in ways that were acceptable to those projects. It hasn't
happened here yet, and no amount of user complaints is going to change
that.
For the last time, if you are not a Pidgin developer or patch writer,
'''''DO NOT WASTE OUR TIME BY COMMENTING ON THIS TICKET.'''''
--
Ticket URL: <http://developer.pidgin.im/ticket/34#comment:59>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list