Re: Discouraging use of sync APIs

2015-02-12 Thread Alexander Larsson
On ons, 2015-02-11 at 12:17 +, Philip Withnall wrote: I understand where you’re coming from; we should not be irritating experienced developers. I completely agree. What do you think of the proposal to use sync gstdio.h for small/local/pseudo-file-system I/O and async GIO for all other

Re: Discouraging use of sync APIs

2015-02-12 Thread Philip Chimento
On Thu, Feb 12, 2015 at 5:22 AM, Philip Withnall phi...@tecnocode.co.uk wrote: On Thu, 2015-02-12 at 11:22 +0100, Alexander Larsson wrote: On ons, 2015-02-11 at 12:17 +, Philip Withnall wrote: I understand where you’re coming from; we should not be irritating experienced

Planning to deprecate libgsystem, introduce libgsystem2 as git submodule

2015-02-12 Thread Colin Walters
I've updated this page: https://wiki.gnome.org/Projects/LibGSystem libgsystem has already become Linux specific (reading symlink xattrs from /proc), and I'd like to make it even more so (some container APIs). gnome-desktop used to depend on it, but with this bug:

Re: Planning to deprecate libgsystem, introduce libgsystem2 as git submodule

2015-02-12 Thread Dimstar / Dominique Leuenberger
On Thu, 2015-02-12 at 18:59 -0500, Colin Walters wrote: I've updated this page: https://wiki.gnome.org/Projects/LibGSystem libgsystem has already become Linux specific (reading symlink xattrs from /proc), and I'd like to make it even more so (some container APIs). gnome-desktop used

Re: Discouraging use of sync APIs

2015-02-12 Thread Philip Withnall
On Thu, 2015-02-12 at 11:22 +0100, Alexander Larsson wrote: On ons, 2015-02-11 at 12:17 +, Philip Withnall wrote: I understand where you’re coming from; we should not be irritating experienced developers. I completely agree. What do you think of the proposal to use sync gstdio.h

Re: Discouraging use of sync APIs

2015-02-12 Thread Philip Withnall
On Wed, 2015-02-11 at 11:33 -0800, Jim Nelson wrote: One of Philip's earlier suggestions was to print a console warning if a sync call is used. That seems like overkill to me, but it does lead to another possibility. Emmanuele refined that to printing a warning if G_ENABLE_DIAGNOSTIC is

Re: Canonical jhbuild documentation

2015-02-12 Thread Allan Day
Sriram Ramkrishna s...@ramkrishna.me wrote: ... I think though, as someone else further in the thread said, we want to make a distinction between 'quick start' and the manual. I honestly don't see why the manual can't contain a quick start section - we do this in other documentation without

Re: Discouraging use of sync APIs

2015-02-12 Thread Philip Withnall
On Wed, 2015-02-11 at 13:10 -0800, Jasper St. Pierre wrote: That's one example of low-hanging fruit. Calling query_info_async is the same thing. Creating a GFileMonitor for a GResourceFile (admittedly nonsense, but arbitrary code that tries to watch any GFile passed into it might hurt) will

Re: Canonical jhbuild documentation

2015-02-12 Thread Frederic Peters
Ekaterina Gerasimova wrote: https://wiki.gnome.org/HowDoI/Jhbuild is the one that seems to be preferred by most docs newcomers and team members so from my point of view it would be good that the final result resembles it and works just as well. Also jhbuild has been absorbing good practices

Re: Canonical jhbuild documentation

2015-02-12 Thread mdhillca
Sri, as the target audience of the HowDoI (as were many fellow attendees at various hackfests), I'd be dismayed if it went away. I'm not a beginner and I don't need to know all the switches, often I just need to know how to get it running again. As Fred says, it's written by someone who can