Well... We spoke about multi protocol before Telepathy... So why not consider Telepathy as a protocol and libmsn as another one ? With that we will be able to use Telepathy or LibMsn if we don't want a big stuff... Phil
Le Wednesday 19 July 2006 18:15, Youness Alaoui a écrit : > On Wed, Jul 19, 2006 at 08:56:46AM +0200, Harry Vennik wrote: > > Op woensdag 19 juli 2006 06:43, schreef Youness Alaoui: > > > No way we drop ANY platform... not even in the beta phase, we want > > > windows beta testers too! > > > > That's right. That is why I said 'If D-BUS for Windows is ready BEFORE > > aMSN2 gets into Beta stage, there is no problem at all.' > > What I meant by 'in beta phase' is 'in svn'.. people use SVN, without > having us release an RC or a beta version, so if we want users to test > while we're developing, it should be working correctly from the very > beginning (what if WE want to work from a windows machine ?) > > > > For now I think it concludes our previous discussion in the other > > > thread about a libmsn vs. a CM for telepathy... > > > > libmsn is going to have an API in C that is similar to the one of > > libtelepathy. This will make the solution of the problem very easy. We > > can just have two ways of building libamsn2_tcl: > > 1. Link libamsn2_tcl against libtelepathy, and have libmsn linked with > > D-BUS bindings (thus being a Telepathy CM). > > 2. Link libamsn2_tcl against libmsn directly (calls to libtelepathy > > functions are changed to libmsn function calls simply by including one > > specialized header file that translates all names). > > first, libamsn2_tcl is TCL, so there is no compilation/linking.. secondly, > NO, I hate and I don't want any conditional code! I do not want any #ifdef > DBUS do this code, #else do this... #endif it puts the overall code in a > very difficult to read/unmaintainable state!!! Trust me, I saw this too > many times already! > > > > in this case, we'll create a libmsn and we'll have it wrapped into Tcl > > > functions, we'll have a one application caling function APIs (Tcl stubs > > > calling the C libmsn functions)... and once and if telepathy gets to > > > the state where it is 100% multiplatform, THEN we'll reconsider it.. > > > > We can just use different build options depending of the platform. (That > > is, the one with Telepathy for Linux, and the one without Telepathy for > > Windows, and the Mac guys may choose which one they use for Mac). In fact > > we just jet the configure script set the build option based on > > availability of D-BUS. So people building aMSN on a Linux system without > > D-BUS would even get a working aMSN. > > see message above... > To it, I'll add something... > What are the advantages of using telepathy and dbus ? oh yeah, having more > than one protocol... but if I understood correctly, we're talking about > Dbus == IPC, INTERPROCESS communication.. which means BETWEEN different > processes.. does that mean that to launch amsn we'll say "hey, you first > need to launch the amsn 'server' (telpathy), then launch amsn client... ", > we're ONE application, why have many processes ? also, this means that if > you have one telepathy server runing, ANY client could be launched and > could receive the dbus messages and could connect.. so you mean we could > have more than one cleint running for the same account ? I just don't get > it... why use that ? why can't we have intraprocess communication.. like > doing a call to a function!!! we want mu,ltiprotocol, then why isn't it > simply a single API for communication ? why can't we do calls from one > function to another function, instead of sending our call through a DBUS > thing, then get our return value through a DBUS thing again ? first, > wouldn't that make aMSN SLOW as hell ? I'm not against DBUS, on the > contrary, I do want DBUS messages to be sent so that other processes can be > notified! like for example, you could create a custom applet that would > notify you when you get a message or whatever, BUT do WE need to use DBUS > internally ??? Sorry if I'm asking stupid questions, I don't know much > about telpathy and don't know much about dbus either, I do NOT want to > start a flame war, if it starts flaming or someone feels it might start > flaming, then we'll discuss it over IRC instead. > All I'm saying is that burger said "hey, telepathy is cool" (he's > developing it) and we all said "cool, we'll use it", but did we really do a > study for this, did we really do an engineer's work seeing which is best, > which solution is better, why use this instead of this.. that should be > done... > for now, this discussion does not change any plan so far, we don't need to > know if we'll use telepathy/dbus or simply function calls, in order to > developer libmsn or the XUL thing or the Tcl core.. the glue between those > modules is in question here, but it's still far from now, so if anyone > becomes unsure, it is not a reason for you to stop doing what you're doing. > > KKRT > > > > note also that the plugins will be Tcl code and they will be given a > > > detailed API that they can use to perform their tasks, no functionality > > > is lost... > > > > Correct. > > > > > KKRT > > > > > > On Tue, Jul 18, 2006 at 05:41:35PM +0200, [EMAIL PROTECTED] wrote: > > > > WE ARE NOT GOING TO DROP SUPPORT FOR ANY PLATFORM WE SUPPORT > > > > NOW!!!!!! > > > > > > > > Why would you think that Telepathy not being supported on Windows > > > > would make any of us drop Windows support? While reading the mails > > > > about multi-platform support, I just realized that we checked > > > > multi-platform support for everything but Telepathy, so I asked > > > > Roelof to check, and he reported here that Telepathy will be a > > > > problem for Windows. So now we've got a problem, and we need to solve > > > > that. > > > > > > > > Solutions are: > > > > - Find a way to get D-BUS/Telepathy to work on Windows > > > > - Forget about Telepathy. > > > > > > > > Harry > > > > > > > > Citeren Arieh Schneier <[EMAIL PROTECTED]>: > > > > >> Just some information about Telepathy that might be interesting > > > > >> for the multiplatform support discussion: Telepathy is not > > > > >> multiplatform! It depends on D-BUS and Windows does not support > > > > >> D-BUS (yet). > > > > > > > > > > ... > > > > > > > > > >> So using Telepathy will implicate dropping Windows support > > > > >> (for a while, until Windows supports D-BUS) or creating a > > > > >> workaround for Windows (keep using a monolithic program without > > > > >> IPC?? monolithic is not > > > > > > > > > > I know that it wouldn't even cross most of our minds to think about > > > > > dropping windows support (I know I wouldn't). But just for those > > > > > who do think about it, go and have a look at our downloads page > > > > > (http://sourceforge.net/project/showfiles.php?group_id=54091) and > > > > > look at the download counts for the different versions. > > > > > > > > > > Lio. > > > > > > > > > > > > > > > ------------------------------------------------------------------- > > > > >---- -- Take Surveys. Earn Cash. Influence the Future of IT > > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > > > share your opinions on IT & business topics through brief surveys > > > > > -- and earn cash > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID= > > > > >DEVD EV _______________________________________________ > > > > > Amsn-devel mailing list > > > > > [email protected] > > > > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > > > > > > --------------------------------------------------------------------- > > > >---- Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > > share your opinions on IT & business topics through brief surveys -- > > > > and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DE > > > >VDEV _______________________________________________ > > > > Amsn-devel mailing list > > > > [email protected] > > > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > > > > ----------------------------------------------------------------------- > > >-- Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > > your opinions on IT & business topics through brief surveys -- and earn > > > cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD > > >EV _______________________________________________ > > > Amsn-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys -- and earn > > cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Amsn-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Amsn-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Amsn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
