Re: [Wengophone-devel] New list and and web home are active
Hello, Thumbs up vadim for managing the mailing list transfer to qutecom. What do you think we should do of the archives ? I was thinking about stopping the openwengo mailman as all the archives are on gmane at http://blog.gmane.org/gmane.comp.voip.wengophone.devel what do you think ? maybe gmane could transfer the subscription from openwengo-devel to qutecom-devel and the history would flow with both archives on it. In any case, now that the new lists are active, I strongly suggest you to subscribe on http://gmane.org/subscribe.php Jérôme --- Andreas Schneider wrote: Vadim Lebedev wrote: Folks, The subejcts says it all. Take a look to www.qutecom.org i've subscribed all existing subscribes to the new list You you didnt't receive a welcome message in couple of hours it means i've goofed so please go to http://lists.qutecom.org/mailman/listinfo/qutecom-dev and subscribe manually I've already registered a channel on freenode: #qutecom @ freenode Thanks Vadim -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New list and and web home are active
Folks, The subejcts says it all. Take a look to www.qutecom.org i've subscribed all existing subscribes to the new list You you didnt't receive a welcome message in couple of hours it means i've goofed so please go to http://lists.qutecom.org/mailman/listinfo/qutecom-dev and subscribe manually Thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New list and and web home are active
Vadim Lebedev wrote: Folks, The subejcts says it all. Take a look to www.qutecom.org i've subscribed all existing subscribes to the new list You you didnt't receive a welcome message in couple of hours it means i've goofed so please go to http://lists.qutecom.org/mailman/listinfo/qutecom-dev and subscribe manually I've already registered a channel on freenode: #qutecom @ freenode Thanks Vadim -- andreas signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Dave Neary wrote: Hi Vadim, Vadim Lebedev wrote: Anybody have an advice for a CMS to use for www.qutecom.org? Before we'd closed up shop, we were evaluating two: Drupal and WordPress. WordPress would probably be the most simple of the two - it allows you to create static pages easily, and of course allows you to have a normal blog interface to your news page, as well as allowing you to have member blogs (which could then be aggregated with Planet). I would suggest Wordpress too. I use Wordpress and trac at http://www.csync.org/ The code quality is good. It works with APC. It is easy to maintain... For mailing list management I suggest http://mlmmj.mmj.dk/ Cheers, Dave. -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Andreas Schneider wrote: Vadim Lebedev wrote: Folks I've installed new repositories at http://hg.qutecom.org please start using them All further commits will go to the new repos Hi Vadim, http://hg.qutecom.org/ is only a directory listing. The cgi script doesn't get executed. -- andreas Soemthing strange happened this night with the web server I'm trying to figure it out Thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Vadim Lebedev wrote: Andreas Schneider wrote: Vadim Lebedev wrote: Folks I've installed new repositories at http://hg.qutecom.org please start using them All further commits will go to the new repos Hi Vadim, http://hg.qutecom.org/ is only a directory listing. The cgi script doesn't get executed. -- andreas Soemthing strange happened this night with the web server I'm trying to figure it out Thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel It's fixed Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New repositories
Folks I've installed new repositories at http://hg.qutecom.org please start using them All further commits will go to the new repos I'm working know to install TRAC and to connect it to the repositories Anybody have an advice for a CMS to use for www.qutecom.org? Thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Hi Vadim, Vadim Lebedev wrote: Anybody have an advice for a CMS to use for www.qutecom.org? Before we'd closed up shop, we were evaluating two: Drupal and WordPress. WordPress would probably be the most simple of the two - it allows you to create static pages easily, and of course allows you to have a normal blog interface to your news page, as well as allowing you to have member blogs (which could then be aggregated with Planet). Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Dave Neary wrote: Hi Vadim, Vadim Lebedev wrote: Anybody have an advice for a CMS to use for www.qutecom.org? Before we'd closed up shop, we were evaluating two: Drupal and WordPress. WordPress would probably be the most simple of the two - it allows you to create static pages easily, and of course allows you to have a normal blog interface to your news page, as well as allowing you to have member blogs (which could then be aggregated with Planet). Cheers, Dave. Dave, Do you and anybody else think we need member blog space? Thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Hi, Vadim Lebedev wrote: Do you and anybody else think we need member blog space? That certainly wasn't the most compelling argument of having WordPress :) But it's *an* argument - updating the news page with a blog was about as far as I had planned. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Dnia czwartek 28 luty 2008, Vadim Lebedev napisał(a): Dave Neary wrote: Hi Vadim, Vadim Lebedev wrote: Anybody have an advice for a CMS to use for www.qutecom.org? Before we'd closed up shop, we were evaluating two: Drupal and WordPress. WordPress would probably be the most simple of the two - it allows you to create static pages easily, and of course allows you to have a normal blog interface to your news page, as well as allowing you to have member blogs (which could then be aggregated with Planet). Cheers, Dave. Dave, Do you and anybody else think we need member blog space? Thanks Vadim I am using Drupal on a number of websites I manage and it gets the job done well. WordPress is IMHO definitely more blog-oriented. Drupal allows to create static pages as easily, plus it has loads of extensions (for galleries, forums, taxonomy-based access, wiki, I believe I have seen a TRAC-integrating one, too). Plus it allows to have per-user blogs just as well. I would go for Drupal, although my experience with WP is close to none. Just my 2 cents. Cheers Mike signature.asc Description: This is a digitally signed message part. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
Joomla from Joomla.org is another option, you have to think about it. Rgds, Alaa - Original Message - From: Micha? Andrzej Wo?niak [EMAIL PROTECTED] To: wengophone-devel@lists.openwengo.com Sent: Friday, February 29, 2008 1:26 AM Subject: Re: [Wengophone-devel] New repositories ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel __ NOD32 2910 (20080228) Information __ This message was checked by NOD32 antivirus system. http://www.eset.com ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New repositories
I vote for Joomla. Cheers. 2008/2/28, Alaa Ayad - InternetVSAT.com [EMAIL PROTECTED]: Joomla from Joomla.org is another option, you have to think about it. Rgds, Alaa - Original Message - From: Micha? Andrzej Wo?niak [EMAIL PROTECTED] To: wengophone-devel@lists.openwengo.com Sent: Friday, February 29, 2008 1:26 AM Subject: Re: [Wengophone-devel] New repositories ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel __ NOD32 2910 (20080228) Information __ This message was checked by NOD32 antivirus system. http://www.eset.com ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Gustavo A. Díaz GDNet Projects www.gdnet.com.ar ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
Hi, Patrick Aljord wrote: On Sun, Feb 24, 2008 at 3:21 PM, Dave Neary [EMAIL PROTECTED] wrote: I find it a little disheartening that what was initially announced as a competition to choose a new name has now been announced as a unilateral decision... at the very least, I would have liked to see a shortlist of 4 or 5 candidates registered and thrown out to the community for voting/comments. As Vadim explained, this is technically not possible. I don't know if you've ever tried to buy a domain name, but people just try to speculate and buy everything in the dictionary or not. Doing a public contest would be impossible cause some people would simply buy the winner and try to sell it to the community later. I have about a dozen domain names mostly lying idle. Some will be used in the future. You can buy a domain name for a year for under $10. Let's say that after doing the first level of filtering, you whittle things down to 5 names whose domain names in .com and .org are available - register 2*5 domain names for $100, and publish the short list. If all else fails, sell the other 8 :) It's a little self-important to imagine domain name hoarders following our little mailing list by the way :) There are also projects who use names derived from the project name - think of sane-project.org, spreadfirefox.com getfirefox.com (not sure why MoFo didn't buy the .orgs associated with those, though...), mono-project.com, etc. While having the right domain name is important, it's not the end of the world to have a related domain name (like say pidgin.im) as long as it's distinctive memorable. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
Hi, Patrick Aljord wrote: On Sat, Feb 23, 2008 at 11:32 PM, EdPimentl [EMAIL PROTECTED] wrote: Why not shorten the name to GoPhone... gPhone wPhone And leverage the brand that WengoPhone built. I think it's too late, the domains are registered already. wphone is for sale, and I don't really get the interest for gphone and gophone. I'd personally like to mark the break from the past, and choose a very different name. Qute* comes across to me as not very qute, and quite possibly contentious with Trolltech trademarks. I find it a little disheartening that what was initially announced as a competition to choose a new name has now been announced as a unilateral decision... at the very least, I would have liked to see a shortlist of 4 or 5 candidates registered and thrown out to the community for voting/comments. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
On Sun, Feb 24, 2008 at 3:21 PM, Dave Neary [EMAIL PROTECTED] wrote: I'd personally like to mark the break from the past, and choose a very different name. Qute* comes across to me as not very qute, and quite possibly contentious with Trolltech trademarks. Don't worry, Trolltech didn't get the trademark on anything that sounds like Cute. They don't even have Qute, where did you get that? The only thing they have as a trademark is Qt. I find it a little disheartening that what was initially announced as a competition to choose a new name has now been announced as a unilateral decision... at the very least, I would have liked to see a shortlist of 4 or 5 candidates registered and thrown out to the community for voting/comments. As Vadim explained, this is technically not possible. I don't know if you've ever tried to buy a domain name, but people just try to speculate and buy everything in the dictionary or not. Doing a public contest would be impossible cause some people would simply buy the winner and try to sell it to the community later. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
Just My thoughts :
As we all know, We still haven't a decent solution for SIP video/audio/text.
As Wengophone as its main features based on SIP , including SIP in its
name, would help visibility about the protocol and not the software.
As people currently don't say send me a yahoo or a gmail !!! , I
hope it would help them to say one day Call me on SIP !!!
On Sat, Feb 23, 2008 at 1:05 AM, Dave Neary [EMAIL PROTECTED] wrote:
Hi Vadim,
Be careful to check if you're infringing on QT trademarks - the QT guys
pronounce if Cute (same as Qute), so you may be getting a note from
Norway if you stick with this name.
Cheers,
Dave.
Vadim Lebedev wrote:
Folks,
I've really intended to arrange for some kind of vote on the new name
however i was strongly advised against it due fear of domain name
squatters.
So i researched availablity of domains and trademarks for the
proposed names and finally the result is:
QuteCom{.com,.org, .net} - As Qute Communicator
and
QutePhone{.com, .org, .net} - as Qute Phone
The domains are already registered.
Monday i'll start to work on web server
Folks with graphical minds, please start submitting logo's proposals
Thanks
Vadim
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
--
Dave Neary
[EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
--
%---%
Michel memeteau
Blog 0.2 : http://memeteau.free.fr
Fixe : 0874763294 Mobile : 0624808051
VOIP | Visio: sip:[EMAIL PROTECTED]
jabber/GoogleTalk : xmpp:[EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
Why not shorten the name to GoPhone... gPhone wPhone And leverage the brand that WengoPhone built. -E On Sat, Feb 23, 2008 at 1:33 PM, michel memeteau [EMAIL PROTECTED] wrote: Just My thoughts : As we all know, We still haven't a decent solution for SIP video/audio/text. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
On Sat, Feb 23, 2008 at 11:32 PM, EdPimentl [EMAIL PROTECTED] wrote: Why not shorten the name to GoPhone... gPhone wPhone And leverage the brand that WengoPhone built. I think it's too late, the domains are registered already. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New Project Name
Folks,
I've really intended to arrange for some kind of vote on the new name
however i was strongly advised against it due fear of domain name squatters.
So i researched availablity of domains and trademarks for the
proposed names and finally the result is:
QuteCom{.com,.org, .net} - As Qute Communicator
and
QutePhone{.com, .org, .net} - as Qute Phone
The domains are already registered.
Monday i'll start to work on web server
Folks with graphical minds, please start submitting logo's proposals
Thanks
Vadim
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
Hi Vadim,
Be careful to check if you're infringing on QT trademarks - the QT guys
pronounce if Cute (same as Qute), so you may be getting a note from
Norway if you stick with this name.
Cheers,
Dave.
Vadim Lebedev wrote:
Folks,
I've really intended to arrange for some kind of vote on the new name
however i was strongly advised against it due fear of domain name
squatters.
So i researched availablity of domains and trademarks for the
proposed names and finally the result is:
QuteCom{.com,.org, .net} - As Qute Communicator
and
QutePhone{.com, .org, .net} - as Qute Phone
The domains are already registered.
Monday i'll start to work on web server
Folks with graphical minds, please start submitting logo's proposals
Thanks
Vadim
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
--
Dave Neary
[EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New in this!!
Hello all. I was looking to get a look at the openwengo but I can't understand what steps I have to do to put this working on the VS2003. I install the Visual SVN plugin and created a new solution. I have downloaded the source code through the Visual SVN to the Solution but now I don't know what to do... Do I have to create a new Project? Please guide me through the steps that I have to do. BR, Joel Silva Analyst . Novabase Av. Eng. Duarte Pacheco, 15F . 1099-078 Lisboa - Portugal Tel. (+351) 213 836 300 . Fax (+351) 213 836 301 . mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] www.novabase.pt http://www.novabase.pt/ ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New in this!!
Joel Silva wrote: Hello all. I was looking to get a look at the openwengo but I can't understand what steps I have to do to put this working on the VS2003. I install the Visual SVN plugin and created a new solution. I have downloaded the source code through the Visual SVN to the Solution but now I don't know what to do... Do I have to create a new Project? Please guide me through the steps that I have to do. Hi, take a look at http://dev.openwengo.org/trac/openwengo/trac.fcgi/wiki/HowToBuildFromSource BR, *Joel Silva** *Analyst Cheers, -- andreas signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New in this!!
Joel Silva wrote: Thanks for the quick reply!;) I read the link you you sent but I don't know what modifications I'm supposed to do... For a newbie like me its a little hard to understand what I should do looking only for that site. You need to run cmake which creates the MSVC files. For more information see http://www.cmake.org/ I'm not a Windoze user so someone else has to help you from that point. Feel free to improve the documentation on the trac wiki. -- andreas Br, Joel Silva -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Schneider Sent: quinta-feira, 18 de Outubro de 2007 12:34 To: wengophone-devel@lists.openwengo.com Subject: Re: [Wengophone-devel] New in this!! Joel Silva wrote: Hello all. I was looking to get a look at the openwengo but I can't understand what steps I have to do to put this working on the VS2003. I install the Visual SVN plugin and created a new solution. I have downloaded the source code through the Visual SVN to the Solution but now I don't know what to do... Do I have to create a new Project? Please guide me through the steps that I have to do. Hi, take a look at http://dev.openwengo.org/trac/openwengo/trac.fcgi/wiki/HowToBuildFromSou rce BR, *Joel Silva** *Analyst Cheers, -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
On 10/9/07, Alec leamas [EMAIL PROTECTED] wrote: Or, just shut up. Amen, brother... --alec aka The new committer Congratulations... and remember: With great power comes great responsibility. :) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On Tuesday 09 October 2007 02:44:32 Sean Bride wrote: On 10/8/07, Dave Neary [EMAIL PROTECTED] wrote: Please enlighten me as to how a distributed version control system automatically solves the problem of community governance and software maintenance processes, I'm eager to find out what it is I've been missing. well, you're the dev manager so I guess you should know better. Anyway, ever wndered why Mozilla, xine, opensolaris, gnome and kde have already switched or are in the process of switching to decentralized SCM? And I am sure they all got convinced because someone totally unknown to the project community, who made zero contribution to it, came to them and told them kind words like those: why are you being so stubborn about it? I don't get it please educate yourself Oh, BTW, I am pretty sure Dave would be aware of any switch of gnome to some centralized SCM. You might want to educate yourself about him. Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On Tuesday 09 October 2007 10:30:43 Aurélien Gâteau wrote: centralized SCM. decentralized, I mean. Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On 10/9/07, Aurélien Gâteau [EMAIL PROTECTED] wrote: Oh, BTW, I am pretty sure Dave would be aware of any switch of gnome to some centralized SCM. You might want to educate yourself about him. I do educate myself, here is the thread: http://www.mail-archive.com/foundation-list%40gnome.org/index.html#02139 with Jeff Waugh, one of the biggest gnome dev (http://live.gnome.org/JeffWaugh) saying: Today, the question is truly about What, When and How -- not Why. http://www.mail-archive.com/foundation-list%40gnome.org/msg02148.html It's kind of complicated to switch for gnome and kde because they are huge but even though that they want and will switch. OpenWengo could do it quickly but it seems like its masters don't feel like doing so because they live in a wonderland where centralized is more powerful than decentralized SCM, some people call this wonderland the past, let's hope they wake up or get a time machine real soon :-) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On 10/9/07, Aurélien Gâteau [EMAIL PROTECTED] wrote: OpenWengo could do it quickly but it seems like its masters don't feel like doing so because they live in a wonderland where centralized is more powerful than decentralized SCM, some people call this wonderland the past, let's hope they wake up or get a time machine real soon :-) You aren't getting anything with such an insulting behavior. I have some real work to do, so I hope you don't mind if I do not answer to any of your further sarcasms. Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
Hi, Sean Bride wrote: with Jeff Waugh, one of the biggest gnome dev Calling Jeff fat is really insulting. (http://live.gnome.org/JeffWaugh) saying: By his own admission, Jeff doesn't code, never has on GNOME, and is a marketing dude more than anything else. So... hyperbola comes easy to him, and he's not God on this subject in GNOME. Not to say his opinion doesn't mean anything, just saying that it's a pretty chasm-sized leap to go from Jeff waugh said distributed is inevitable to GNOME is moving to a distributed SCM. OpenWengo could do it quickly but it seems like its masters don't feel like doing so because they live in a wonderland where centralized is more powerful than decentralized SCM, some people call this wonderland the past, let's hope they wake up or get a time machine real soon :-) Thanks for your insights. I'm sure your contribution will help us when the time comes to decide to move to another SCM. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On 10/9/07, Dave Neary [EMAIL PROTECTED] wrote: By his own admission, Jeff doesn't code, never has on GNOME, and is a marketing dude more than anything else. So... hyperbola comes easy to him, and he's not God on this subject in GNOME. My bad then :) , Jeff is not a dev but you can see from the thread that they all agree that decentralized is better and Jeff saying that How and What rather Why summarizes pretty well the whole thread that gnome devs want to switch to decentralized which was my point :p Thanks for your insights. I'm sure your contribution will help us when the time comes to decide to move to another SCM. I'm sure the OW devs are smart enough to switch to Git without any of my insights, after all, they already changed two times their build systems, their repository address, and refactored the OW code like 10 thousands times so it's not like they're not used to changes :) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
Hey, whats your objective? If it's to make this bunch of developers going to change their mind, face the fact: you have failed. It's doesn't really matter what you say at this point, unless you apologize for all the lack of netiquette you have showed in your messages.. People are angry with you, for very understandable reasons. Angry people doesn't listen, such is life. I'm one of those. So: either stop this meaningless discussion, or start a new thread (another subject line, that is) and try to start from scratch. To apologize would be a reasonable start. To respect the skills and competence of this team (don't count me, I'm just a guest) is another part. And present yourself. Who are you, what's your interest in this, what's your record? And whatever thoughts you have about who is smart or not, keep them for yourself. Nobody is interested. Or, just shut up. --alec aka The new committer ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
Hi Alec, Alec leamas wrote: OK folks, I'm the new committer. And I'm just a little curios about the subject line for this discussion. Something I should know? ;-) It's just that every time people talk about a core development team, someone comes out of the woodwork to say that we wouldn't have this problem if we used a decentralised system - nothing to do with you, I assure you. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On 10/8/07, Dave Neary [EMAIL PROTECTED] wrote: It's just that every time people talk about a core development team, someone comes out of the woodwork to say that we wouldn't have this problem if we used a decentralised system That's probably because you actually wouldn't have that problem if you used a decentralized system. Ever thought of it this way? :-) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
Hi Sean, Sean Bride wrote: On 10/8/07, Dave Neary [EMAIL PROTECTED] wrote: It's just that every time people talk about a core development team, someone comes out of the woodwork to say that we wouldn't have this problem if we used a decentralised system That's probably because you actually wouldn't have that problem if you used a decentralized system. Ever thought of it this way? :-) I admire your moxy :) Coming to a mailing list to say that you people are so stubborn for not doing things the git way must work just as well as you have to buy my car - look at the pile of junk you're driving or how could you be so stupid as to not agree with me? We're stubborn either because we spend more time developing software than maintaining the version control system, or because we're so stupid we don't know a good thing when we see it. I guess it's our lack of software development experience that's handicapping us. Please enlighten me as to how a distributed version control system automatically solves the problem of community governance and software maintenance processes, I'm eager to find out what it is I've been missing. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Ang: Re: [Wengophone-devel] New committer
On 10/8/07, Dave Neary [EMAIL PROTECTED] wrote: Please enlighten me as to how a distributed version control system automatically solves the problem of community governance and software maintenance processes, I'm eager to find out what it is I've been missing. well, you're the dev manager so I guess you should know better. Anyway, ever wndered why Mozilla, xine, opensolaris, gnome and kde have already switched or are in the process of switching to decentralized SCM? Maybe they do it just for fun or maybe they do it because it's actually superior. But if you think for whatever reason (I suppose it's ignorance because you're not stupid ;-) ) svn is better well please stay with svn even though it's a pain for the rest of us and that eventually we'll all be using decentralized SCM. To answer your question about governance, as I said before everybody has commit access so you don't need to worry about who has commit access and you don't have to waste time on politics. If someone has a patch, you just pull from the patcher branch and vice versa. It saves a lot headaches and time. There are other advantages that are listed and detailed in the previous links and video but if you're not interested then who cares. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
Sean Bride wrote: Our requirements are pretty specific: * Source control system must be cross-platform, and fast Git is cross-platform and fast. It runs perfect on windows now: http://code.google.com/p/msysgit/ * A central canonical source for the software is essential Git does canonical too. * An easy migration path from our existing system (svn) Git does this also (git-svn clone https://dev.openwengo.org/svn/openwengo/wengophone-ng/trunk; for trunk), I've just cloned the whole OW trunk repository in a git one in a couple of minutes with all the commits history. The cross-platform requirement rules out git for the moment, the best distributed candidate is Mercurial, then perhaps Bazaar-NG. False, it runs fine on windows see previous link. (and Bazaar is really slow). Subversion fulfils its requirements very well - it is cross-platform, allows us to manage access rights for developers, Well with Git, you don't need to worry about access rights for developers, you don't need to waste a lot of time on politics and trying to figure out who's smart enough to commit and who's not. It will save OW devs lot of time actually. provides a canonical source for the source code, again, you can have a central repository with Git, it's even very easy to use. Actually Git is a lot simpler than SVN to use. and was very easy for developers to use from the start because of both windows GUI front ends Git comes with gitgui and gitk to view and commit on all platforms. The arguments for investing time effort into moving away from our existing system would need to be very compelling, and so far I haven't heard a really compelling one. ok how about it saves time and resources for OW developers because it is so much easier to manage, people will be able to commit and send patches more easily and decentralized is just the natural way to do things in the Open Source community. I've never met anybody switching to Git coming back to SVN, it's just superior and so much nicer to use, there's just no turning back. Is git submodule already done? We need this feature. We make heavy use of svn externals. -- andreas signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
On 10/7/07, Andreas Schneider [EMAIL PROTECTED] wrote: Is git submodule already done? We need this feature. We make heavy use of svn externals. yep, http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html git-submodule - Initialize, update or inspect submodules ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Ang: Re: [Wengophone-devel] New committer
OK folks, I'm the new committer. And I'm just a little curios about the subject line for this discussion. Something I should know? ;-) --alec ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
I don't understand why wengo devs don't want to switch to something more powerful like git or mercurial where everybody can commit easily and send nice patches and actually *help* the openwengo more efficiently. Don't you want the community to help the project? why are you being so stubborn about it? I don't get it please educate yourself about Git and Mercurial and stop using SVN which is a pain for people that want to actually help you (for free): http://youtube.com/watch?v=4XpnKHJAok8 http://www.stonehenge.com/pic/Git-2.0.3-to-be.pdf http://blogs.gnome.org/shaunm/2007/09/17/git-for-gnome/ http://blog.cmsmadesimple.org/2007/09/13/using-git-for-core-development/ http://www.betaversion.org/~stefano/linotype/news/106/ Decentralized SCM are more democratic, faster and more efficient and doesn't make people (that want to give *you* some of their free time) feel like they're inferior to the other members of the community that have the divine commit access. Thanks for reading, Sean ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
that was a little harsh but I agree with Sean, Git is way better than svn and it's also much easier to switch from svn to git than from SCons to cmake :-) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
Sean Bride wrote: I don't understand why wengo devs don't want to switch to something more powerful like git or mercurial where everybody can commit easily and send nice patches and actually *help* the openwengo more efficiently. Don't you want the community to help the project? why are you being so stubborn about it? I don't get it please educate yourself about Git and Mercurial and stop using SVN which is a pain for people that want to actually help you (for free): http://youtube.com/watch?v=4XpnKHJAok8 http://www.stonehenge.com/pic/Git-2.0.3-to-be.pdf http://blogs.gnome.org/shaunm/2007/09/17/git-for-gnome/ http://blog.cmsmadesimple.org/2007/09/13/using-git-for-core-development/ http://www.betaversion.org/~stefano/linotype/news/106/ Decentralized SCM are more democratic, faster and more efficient and doesn't make people (that want to give *you* some of their free time) feel like they're inferior to the other members of the community that have the divine commit access. http://article.gmane.org/gmane.comp.voip.wengophone.devel/5096/match=git Thanks for reading, Sean -- andreas signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
Our requirements are pretty specific: * Source control system must be cross-platform, and fast Git is cross-platform and fast. It runs perfect on windows now: http://code.google.com/p/msysgit/ * A central canonical source for the software is essential Git does canonical too. * An easy migration path from our existing system (svn) Git does this also (git-svn clone https://dev.openwengo.org/svn/openwengo/wengophone-ng/trunk; for trunk), I've just cloned the whole OW trunk repository in a git one in a couple of minutes with all the commits history. The cross-platform requirement rules out git for the moment, the best distributed candidate is Mercurial, then perhaps Bazaar-NG. False, it runs fine on windows see previous link. (and Bazaar is really slow). Subversion fulfils its requirements very well - it is cross-platform, allows us to manage access rights for developers, Well with Git, you don't need to worry about access rights for developers, you don't need to waste a lot of time on politics and trying to figure out who's smart enough to commit and who's not. It will save OW devs lot of time actually. provides a canonical source for the source code, again, you can have a central repository with Git, it's even very easy to use. Actually Git is a lot simpler than SVN to use. and was very easy for developers to use from the start because of both windows GUI front ends Git comes with gitgui and gitk to view and commit on all platforms. The arguments for investing time effort into moving away from our existing system would need to be very compelling, and so far I haven't heard a really compelling one. ok how about it saves time and resources for OW developers because it is so much easier to manage, people will be able to commit and send patches more easily and decentralized is just the natural way to do things in the Open Source community. I've never met anybody switching to Git coming back to SVN, it's just superior and so much nicer to use, there's just no turning back. You really should try it, it would be too bad to miss on such a goody for the community. (http://youtube.com/watch?v=4XpnKHJAok8) As Linus says: I'm not gonna force you to switch to decentralized, I'm just gonna call you ugly and stupid ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New committer
Hi all, I'm pleased to announce the addition of a new committer to the OpenWengo repository, Alec Leamas. In the past month or so, he has done great work on the ALSA driver for phmedia, and has shown a great ability to identify problems and exercise good judgement. Alec, welcome to the team! Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New committers
Hi all, I'm glad to inform you that two new people gained commit access to the openwengo project thanks to their several patches and/or addition to the project: - Ludovico Cavedon (he fixed several bugs and is working on ipv6 support for WengoPhone) - Dave Neary (he tracked some bugs on Linux and managed the gathering of WengoPhone translation) They gained their access by the rules descrided by Dave Neary in a previous mail (subject: Initial commiters on svn). Regards -- Philippe BERNERY [EMAIL PROTECTED] http://dev.openwengo.org ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New user baffled...
Thomas Monjalon a écrit : Guillaume Yziquel a écrit : - I did not find any documentation or HOWTO on any website, and that is something I'd like to have handy... I think you need to visit this website: http://dev.openwengo.com Thanks. - Is there some testing machine, to see if the whole software is working with my hardware? What do you mean by testing machine ? The number 333 is an echo service. Yes, that's what I meant. Thank you, Guillaume. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New user baffled...
Hello, I've heard of OpenWengo as a free software providing a decent alternative to Skype, for instance. However, here are a few things that baffled me: - I did not find any documentation or HOWTO on any website, and that is something I'd like to have handy... - Is there some testing machine, to see if the whole software is working with my hardware? Because on my Debian GNU/linux box, wengophone does not exactly seem to work out of the box. Thanks for any help. Guillaume Yziquel. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New user baffled...
Guillaume Yziquel a écrit : - I did not find any documentation or HOWTO on any website, and that is something I'd like to have handy... I think you need to visit this website: http://dev.openwengo.com - Is there some testing machine, to see if the whole software is working with my hardware? What do you mean by testing machine ? The number 333 is an echo service. -- Thomas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] new enhancement : Wengo SIp adress
Hi I ve opened a new enhancement proposal : Use SIP adresses instead of Wengo username in the GUI http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1696 Is this has already been discussed ? I guess from the begining the concept of the wengo username is the base of the service. -- %---% Michel memeteau VOIP | Visio: sip:[EMAIL PROTECTED] 0491886375 0624808051 jabber/GoogleTalk : [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New debian package.
I've just upload the first 2.1~rc2 package in debian unstable. It will be on all debian mirrors tomorrow after 11 CEST. You can also find it on my repository deb http://www.prato.linux.it/~mnencia/debian wengophone-ng/ deb-src http://www.prato.linux.it/~mnencia/debian wengophone-ng/ Ciao -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | [EMAIL PROTECTED] | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4 signature.asc Description: Digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
RE: [Wengophone-devel] New dependencies
Hello Claudio, Can you be a bit more specific ? are you using scons / cmake ? I know that with the cmake buildsystem, default choices of internal / external libs may not be the same as before. What exactly was the experience that made you send this email ? Thank you Jerome -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Claudio André Envoyé : samedi 27 janvier 2007 00:25 À : Wengophone Devel Objet : [Wengophone-devel] New dependencies Seems to be mandatory now! - libportaudio-dev - libavcodec-dev - libsamplerate-dev - libspeex-dev ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New build script for Linux
Claudio André wrote: Hi, Hi Claudio, ./build_make.sh --help Usage: build_make.sh [--configure [debug|final]|--clean|--verbose|--help] But if i try, ./build_make.sh --configure debug, i get. Unknown Option --configure. Exit The right seems to be ./build_make.sh --build debug Thanks, fixed ;) -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New dependencies
Hi, i'm using cmake, on OW 2.1. Rev 943x to 9492 Since a few days ago, cmake is not able to find some libraries and failed to build if these dev packages are not installed (+ libsndfile-dev, from previous message). Well, i sent this message because i agree with [EMAIL PROTECTED] The idea behind my message is: - advice someone who finds an error not seen before (maybe a new dependancy). I'm sorry. I could be clear on my point in the previous message. Next time, i'll try to clarify the message. So, it was just a bip message. Thanks. Jerome WAGNER wrote: Hello Claudio, Can you be a bit more specific ? are you using scons / cmake ? I know that with the cmake buildsystem, default choices of internal / external libs may not be the same as before. What exactly was the experience that made you send this email ? Thank you Jerome -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Claudio André Envoyé : samedi 27 janvier 2007 00:25 À : Wengophone Devel Objet : [Wengophone-devel] New dependencies Seems to be mandatory now! - libportaudio-dev - libavcodec-dev - libsamplerate-dev - libspeex-dev ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New build script for Linux
Hi, I've rewritten the build_make.sh from scratch. New Features: * Logging (build/.build.log) * Nice command line options ;) * error return values form make or cmake * build directory cleanup (--clean) more: ./build_make.sh --help Have fun, -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New build script for Linux
Hi, ./build_make.sh --help Usage: build_make.sh [--configure [debug|final]|--clean|--verbose|--help] But if i try, ./build_make.sh --configure debug, i get. Unknown Option --configure. Exit The right seems to be ./build_make.sh --build debug Andreas Schneider wrote: Hi, I've rewritten the build_make.sh from scratch. New Features: * Logging (build/.build.log) * Nice command line options ;) * error return values form make or cmake * build directory cleanup (--clean) more: ./build_make.sh --help Have fun, -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New dependencies
Seems to be mandatory now! - libportaudio-dev - libavcodec-dev - libsamplerate-dev - libspeex-dev ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New patch for the qtwengophone-install target
On 8/16/06, Andreas Schneider [EMAIL PROTECTED] wrote:
if WengoGetConsoleArgument('enable-shared-phapi') == yes
doesn't work, WengoGetConsoleArgument('enable-shared-phapi') return an
integer, I've uplaoded a fixed patch to my bug #806
Thanks for spotting the problem; reading the docs in wengoenv.py I
realized it's even funnier: the return value can be a string or a
boolean value, very clever...
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New way of handling Qt interface inside NG
Gianluca Sforna wrote:
I think the most widely used approach for this (coincidentally, at
work we also use this one...) is the second one (subclassing), and it
also works the quite the same in QT 3.
I prefer the first approach (a bit modified):
#include QObject
namespace Ui { class ImageDialog; }
class ImageDialog : public QObject {
Q_OBJECT
public:
ImageDialog(QWidget * parent);
private:
Ui::ImageDialog * _ui;
};
Rather than inheritance:
#include ui_ImageDialog.h
#include QObject
class ImageDialog : public QObject, private Ui::ImageDialog {
Q_OBJECT
public:
ImageDialog(QWidget * parent);
private slots:
void checkValues();
};
The reason is very simple, with inheritance you need to include
ui_imagedialog.h inside ImageDialog.h thus each time you will change the
ui file using Qt Designer, you will need to recompile all the files that
include ImageDialog.h
The first approach does not have this drawback since Ui::ImageDialog *
_ui is a pointer and can be class forwarded. Do be simple, encapsulation
is higher using the first than the second approach and encapsulation is
very very important.
Of course using the first approach you need to code 2-3 lines more
inside ImageDialog.cpp than the second:
#include ImageDialog.h
#include ui_ImageDialog.h
ImageDialog::ImageDialog(QWidget * parent) : QObject(parent) {
_ui = new Ui::ImageDialog();
_ui-setupUi(new QDialog(parent));
}
BTW, I wonder how did you manage to work so far without access to
protected methods...
By using event filters cf
http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/wengophone-ng/trunk/libs/qtutil/include/qtutil
--
Tanguy Krotoff [EMAIL PROTECTED]
http://openwengo.org
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] New way of handling Qt interface inside NG
With Qt it's possible to deal with Qt Designer in different ways:
http://doc.trolltech.com/4.1/designer-using-a-component.html
Inside WengoPhone NG, we are using a different approach, here a simple
example of code:
#include qtutil/Object.h
#include qtutil/WidgetFactory.h
#include QtGui
QtAbout::QtAbout(QWidget * parent) {
_aboutWindow = WidgetFactory::create(:/forms/AboutWindow.ui,
parent);
QLabel * wengoPhoneBuildIdStringLabel =
Object::findChildQLabel *(_aboutWindow,
wengoPhoneBuildIdStringLabel);
wengoPhoneBuildIdStringLabel-setText(Hello World);
}
This approach is not powerfull enough because most of Qt classes have
protected method that we need to access, so we are switching to the
standard Qt approach using uic.
This will allow us to use more efficiently Qt Designer.
A simple example:
#include ui_AboutWindow.h
QtAbout::QtAbout(QWidget * parent) {
_aboutDialog = new QDialog(parent);
_ui = new Ui::AboutWindow();
_ui-setupUi(_aboutDialog);
_ui-wengoPhoneBuildIdStringLabel-setText(Hello World);
}
A new function WengoCompileQt4UiFile() has been added to WengoScons.
An example of the new approach is available in playground:
http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/playground/demouic
We will switch to this new approach over time, starting by components
that need to access Qt protected methods.
--
Tanguy Krotoff [EMAIL PROTECTED]
http://openwengo.org
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New way of handling Qt interface inside NG
2006/4/20, Tanguy Krotoff [EMAIL PROTECTED]:
With Qt it's possible to deal with Qt Designer in different ways:
http://doc.trolltech.com/4.1/designer-using-a-component.html
Inside WengoPhone NG, we are using a different approach, here a simple
example of code:
#include qtutil/Object.h
#include qtutil/WidgetFactory.h
#include QtGui
QtAbout::QtAbout(QWidget * parent) {
_aboutWindow = WidgetFactory::create(:/forms/AboutWindow.ui,
parent);
QLabel * wengoPhoneBuildIdStringLabel =
Object::findChildQLabel *(_aboutWindow,
wengoPhoneBuildIdStringLabel);
wengoPhoneBuildIdStringLabel-setText(Hello World);
}
This approach is not powerfull enough because most of Qt classes have
protected method that we need to access, so we are switching to the
standard Qt approach using uic.
This will allow us to use more efficiently Qt Designer.
A simple example:
#include ui_AboutWindow.h
QtAbout::QtAbout(QWidget * parent) {
_aboutDialog = new QDialog(parent);
_ui = new Ui::AboutWindow();
_ui-setupUi(_aboutDialog);
_ui-wengoPhoneBuildIdStringLabel-setText(Hello World);
}
A new function WengoCompileQt4UiFile() has been added to WengoScons.
An example of the new approach is available in playground:
http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/playground/demouic
We will switch to this new approach over time, starting by components
that need to access Qt protected methods.
--
Tanguy Krotoff [EMAIL PROTECTED]
http://openwengo.org
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
:-o
:-))
--
mstute
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New way of handling Qt interface inside NG
On 4/20/06, Tanguy Krotoff [EMAIL PROTECTED] wrote: This approach is not powerfull enough because most of Qt classes have protected method that we need to access, so we are switching to the standard Qt approach using uic. I think the most widely used approach for this (coincidentally, at work we also use this one...) is the second one (subclassing), and it also works the quite the same in QT 3. We will switch to this new approach over time, starting by components that need to access Qt protected methods. BTW, I wonder how did you manage to work so far without access to protected methods... Cheers Gianluca PS. may I be damned if I ever remember to press reply-all... this setup is insane for me :) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] new deb for classic
Hello, Sorry for the late reply Patrick, your contribution deserved as much attention as any other, without a doubt, but we're a bit busier than usual these days :-(. Patrick Aljord wrote: I suggested putting new debs on openwengo.org as the one available is kind of buggy so here is the one I built from a couple of days. It works pretty decents. Has anyone been able to test it? If so, did it work properly? I'd be glad to get some feedback about these packages used on various setups. Here is the new deb: http://p80.free.fr/wengostuff/Wengophone-0.99-rev3722-1.i386.deb Is it really based on revision 3722? If so, it is an old revision. Could you please verify that you used a fairly recent revision? I built it on kubuntu drapper but it works on breezy too. I built it this way: QTDIR=/usr scons softphone-deb-installer mode=release-symbolsk Great! That would be very nice to have official Ubuntu packages. Patrick, would you like to investigate in that direction? Thank you very much for this contribution, i hope to have some time to test it in the near future so that we can publish it on the .org web site. Regards, -- Julien Gilli OpenWengo, the free and multiplatform VoIP client http://www.openwengo.com/ ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] new deb for classic
I suggested putting new debs on openwengo.org as the one available is kind of buggy so here is the one I built from a couple of days. It works pretty decents. It doesn't complain about SIP ports being already used all the time and the link to create a wengo account does work. Here is the new deb: http://p80.free.fr/wengostuff/Wengophone-0.99-rev3722-1.i386.deb I built it on kubuntu drapper but it works on breezy too. I built it this way: QTDIR=/usr scons softphone-deb-installer mode=release-symbolsk I didn't modify any default options but just in case, here are the scons script: http://p80.free.fr/wengostuff/scons Hope that helps Pat ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
