What is the core ? Anyway, I am glad that Tcl won't be dropped... It let me clarify my thoughts... Well where I think you misunderstood previous mails was : we never said that we will drop Tcl/Tk for the XML2GUI thing... The only part that needed to be in C was binding to DBus... Don't forget something : the more you have in C the more you will have to port... And with compilation you have always many troubles... Dependency missing... Gcc not installed... Have you ever seen the forum ? It's full of guys who say : "Hey your soft doesn't want to compile !"... No, seriously, maybe Tk is ugly but it is installable easily on all distros... Windows included... And TkHtml isn't ugly... It's only the way for skinners to change all they want : even the place of widgets can be changed ! You want to have the OK button at the top in place of at the bottom ? It's easy you modify the template and nothing more ! I am not sure that XUL can do that... Oh I just think we said XML2GUI and you decided (and when I say you it's you alone) that it will be XULRunner... Well I agree : I help Tom and Boris with TkHtml but I think it would be the best and simplest engine to create using Snit objects... @Youness : Buttons with TkHtml won't have GTK or QT look they will have the skin's look... A new version of pixmap buttons in a better way ;) Phil P.S. Why do you want to out aMSN 1.0 ? In fact this code had been written by one guy and now we are a dozen to work on it... Its design is really bad and will never be good... During the development of aMSN2 we should provide basic support and feature upgrading... but nothing more and make its development slowed down... And during this time everybody could work on aMSN2... (With Tcl only modules except for bindings to D-Bus)
Le Monday 17 July 2006 22:25, Harry Vennik a écrit : > Op maandag 17 juli 2006 21:22, schreef Boris Faure (aka billiob): > > All the following is only my opinion. > > > > I wanted to use tkhtml in amsn. (i've got that goal since february > > with Tom) A part of it can be done, right now, but all the threads > > related to amsn2 are making me more and more lazy about coding it. > > Some of you wants to drop tcl (ok, none have told that in that thread, > > but i'm sure some are a bit fed up with tcl), and drop tk ! > > Why do people like amsn ? For tk, of course no ! They use amsn only > > because we have the better support of the msn protocol. And we can do > > something great with TK !! Improve the desktop integration plugin, use > > tkhtml, and keep on improving chameleon : i want Youness' code to be > > used. I don't want all those lines of code to be dropped this way. > > Yeah, somehow I expected a reply like this since the moment I read Tom's > mail about TkHtml. And, I do understand it. Somehow the idea has grown > somewhere that aMSN2 would be based on TkHtml, but in the aMSN2 threads, > there was only talk about XML2GUI. Maybe TkHtml has been mentioned, but > certainly there was no agreement on using that. So starting work on it at > all, was taking a risk from the very beginning. Of course that is not to > mean 'you should not have been doing that', as you can read in my previous > mail, TkHtml will even be in some aMSN releases if it can be finished soon > enough. If possible the HTML code will even be reused in aMSN2. The Tcl > code however would after those releases be wasted, that is true, and of > course that is a sad thing, but we are starting all over again, so much > more code that we spent years on to develop, is finally thrown away. Why? > because that codebase will not allow us to do what we'd like to do: make > aMSN into an MSN Messenger client that can compete with the original. > > Also, it has been clearly stated that TCL is not going to be dropped, only > TK. Nothing is wrong with TCL, a lot is wrong with TK. Don't forget that > the desktop integration pluging, skins support, pixmap widgets and > Chameleon are all just work-arounds for the problem caused by TK: uglyness. > With aMSN we want to get rid of all those work-arounds, and solve the > problem instead. TCL will be even more at home in aMSN2 than it has ever > been in aMSN before. TCL is a scripting language, not a programming > language. In aMSN2 the core programming will be in C, and all basic blocks > are joined using TCL scripts. > > > About telepathy, how are you going to handle smileys ? Events are only > > containing some text. I'm asking this question because i don't how to > > create such events to have a simple, but efficient support of smileys > > using tkhtml. > > The smiley triggers flow through a text channel perfectly. Probably custom > smilies will flow through another channel type (I suppose custom smileys > are an MSNP2P thing?). It has already been mentioned that Telepathy will > not be able to support everything that MSNP13 needs, and thus Telepathy > will need to be extended. Any shortcoming will be reported to the Telepathy > team, and we will work with them and with Telepathy-MSN to extend the > Telepathy API as needed. > > > In my opinion should depend a lot on libmsn (or whatever you call it) > > so that a nice gui be written having in mind all the specificities of > > each protocol we want to implement. > > > > How are you going to tell plugin developers to stop coding because > > their plugins won't work (and won't be easy to port to amsn2) with > > amsn2? > > We should just not wait too long before we tell them, and we should try to > publish drafts of the aMSN2 plugins API as early as possible, so people can > start porting their plugins long before aMSN2 is released. Also, we should > try not to modify the plugins interface of aMSN1 any more, otherwise they > will be right if they say we're changing it too often. > > > I wanted amsn 0.96 to be released soon. I had in mind amsn2. I was > > excited. no more now. > > I hope you will get excited again. > And indeed, 0.96 should get out soon. > > > Sorry. > > Greetings. > > > > Ps : J, tell us your opinion, i'm almost sure it's interesting. > > ------------------------------------------------------------------------- > 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
