Re: [pygtk] PyGTK FAQ moved
Hello, On 6/6/07, Johan Dahlin <[EMAIL PROTECTED]> wrote: My employer (Async Open Source) recently invested in server for faster hosting. I just moved over the PyGTK FAQ to the new server, it should be a lot more responsive now. Just to thank you and your employer for hosting this FAQ! It contains a lot of interesting stuff and has been useful quite a few times over the past for me. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] PyGTK FAQ moved
Pádraig Brady wrote: Johan Dahlin wrote: Hi there My employer (Async Open Source) recently invested in server for faster hosting. I just moved over the PyGTK FAQ to the new server, it should be a lot more responsive now. The DNS records has not been updated yet so it is temporary redirected to pygtk-faq.async.com.br Let me know if there are any problems. It's really fast, thanks! Great to hear! What's the story with the copy of the FAQ at: http://live.gnome.org/PyGTK/FAQ It was meant to be a replacement since the old server was very slow. But I think we prefer the old/current faq interface over a wiki. a little bit of organization helps. It's out of date wrt one entry I updated at async.com.br recently at least. I would much prefer there to be one copy, from both a maintenance and end user searching point of view. That should be fixed now, all links to the old wiki are redirected to the new. I couldn't find any differences though, the content seems to be identical to me.. Johan ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] PyGTK FAQ moved
Johan Dahlin wrote: > Hi there > > My employer (Async Open Source) recently invested in server for faster > hosting. I just moved over the PyGTK FAQ to the new server, it should be a > lot more responsive now. > The DNS records has not been updated yet so it is temporary redirected to > pygtk-faq.async.com.br > > Let me know if there are any problems. It's really fast, thanks! What's the story with the copy of the FAQ at: http://live.gnome.org/PyGTK/FAQ It's out of date wrt one entry I updated at async.com.br recently at least. I would much prefer there to be one copy, from both a maintenance and end user searching point of view. cheers, Pádraig. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] pygtk-FAQ entry 13.25 (sequence APIs for TreeStore andListStore)
On 27/08/2003 7:47 PM, [EMAIL PROTECTED] wrote: Hi again, The sequence API as described in the pygtk FAQ entry 13.25 http://www.async.com.br/faq/pygtk/index.py?req=show&file=faq13.025.htp does not work, the TreeStore and ListStore objects do have a function __getitem__, but no __setitem__. Where has __setitem__ gone? pygtk-1.99.15 on win32, gtk-2.2.2 please upgrade to a newer version of pygtk. I think the functionality you want was added later on. James. -- Email: [EMAIL PROTECTED] WWW: http://www.daa.com.au/~james/ ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] PyGTK Faq
>> I think having a 1.2 vs. 1.3 section might be a good idea as well. Christian> Fine by me, but since we don't have subsections, how do you Christian> propose we separate the "namespaces" since we have widgets Christian> with the same name in 1.2 and 1.3? I was thinking more about general 1.2 v. 1.3 questions, like which widgets disappeared, which are new, how has the build process changed, ... Skip ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
Re: [pygtk] PyGTK Faq
On Mon, 28 Jan 2002, Skip Montanaro wrote: > I think having a 1.2 vs. 1.3 section might be a good idea as well. If > nothing else, it might get people to realize the API has changed > significantly. Fine by me, but since we don't have subsections, how do you propose we separate the "namespaces" since we have widgets with the same name in 1.2 and 1.3? Take care, -- Christian Reis, Senior Engineer, Async Open Source, Brazil. http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
Re: [pygtk] PyGTK Faq
Christian> Sounds reasonable. Would you (anybody, really) have a Christian> suggestion of sections for us? Right now I have: Christian> 1. General Information and Availability Christian> 2. Widget Issues Christian> 3. Themes and Styles Christian> 4. Signal handling Christian> 5. Miscellaneous Christian> I understand that Widget Issues is pretty bad naming (I was Christian> aware at the time) but I wanted to get started and these Christian> things (naming..) hamper work. But now I think I am prepared Christian> to change it sooner than later. So what should I do? Christian> a) have a section for each widget? Christian> b) have a section for groups of widgets? Christian> c) have one big section like i do now? I'd go with b, perhaps patterning it after the section breakdown in the Gtk ref manual table of contents. I think having a 1.2 vs. 1.3 section might be a good idea as well. If nothing else, it might get people to realize the API has changed significantly. Skip ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
Re: [pygtk] PyGTK Faq
On Mon, 28 Jan 2002, Skip Montanaro wrote: > One thing that might help to generate more input and to lessen your load is > to add questions without answers when you realize they are faqs (should be a > lot lower effort on your part than trying to come up with answers as well). > Every now and again (monthly?) post a list of what questions lack answers. I have assorted a number of emails that answer things and I just have to stick them in as questions. > > I'd be willing to help. Send me the password when you think of it. One Okay. > thing that's worth noting about the FAQ wizard is that it's relatively > difficult to reorganize things if a section grows too large, so it helps to > have a reasonable structure set up before questions start flowing in. Sounds reasonable. Would you (anybody, really) have a suggestion of sections for us? Right now I have: 1. General Information and Availability 2. Widget Issues 3. Themes and Styles 4. Signal handling 5. Miscellaneous I understand that Widget Issues is pretty bad naming (I was aware at the time) but I wanted to get started and these things (naming..) hamper work. But now I think I am prepared to change it sooner than later. So what should I do? a) have a section for each widget? b) have a section for groups of widgets? c) have one big section like i do now? Maybe signal handling will end up being pretty short I need to add a section for libglade issues, I suppose? Any suggestions? Take care, -- Christian Reis, Senior Engineer, Async Open Source, Brazil. http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
Re: [pygtk] PyGTK Faq
> Skip Montanaro <[EMAIL PROTECTED]> writes: > > > >> Where is the faq ... > > Christian> I'm working on one in my spare time (which is why it is still > Christian> so short) at http://www.async.com.br/faq/pygtk/ > > Christian, > > One thing that might help to generate more input and to lessen your load is > to add questions without answers when you realize they are faqs (should be a > lot lower effort on your part than trying to come up with answers as well). > Every now and again (monthly?) post a list of what questions lack answers. > > I'd be willing to help. Send me the password when you think of it. One > thing that's worth noting about the FAQ wizard is that it's relatively > difficult to reorganize things if a section grows too large, so it helps to > have a reasonable structure set up before questions start flowing in. > Otherwise everything will wind up in one section. (Witness the Python FAQ.) > > Skip > ___ > pygtk mailing list [EMAIL PROTECTED] > http://www.daa.com.au/mailman/listinfo/pygtk That sounds like a good suggestion, I would be glad to contribute if I find something on the list that I actually know. -- Steve McClure 430 10th St NW Racemi Suite N-210 http://www.racemi.com Atlanta, GA 30318 [EMAIL PROTECTED] voice/fax: 404-892-5850 ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
Re: [pygtk] PyGTK Faq
>> Where is the faq ... Christian> I'm working on one in my spare time (which is why it is still Christian> so short) at http://www.async.com.br/faq/pygtk/ Christian, One thing that might help to generate more input and to lessen your load is to add questions without answers when you realize they are faqs (should be a lot lower effort on your part than trying to come up with answers as well). Every now and again (monthly?) post a list of what questions lack answers. I'd be willing to help. Send me the password when you think of it. One thing that's worth noting about the FAQ wizard is that it's relatively difficult to reorganize things if a section grows too large, so it helps to have a reasonable structure set up before questions start flowing in. Otherwise everything will wind up in one section. (Witness the Python FAQ.) Skip ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
