Daniel Espinosa pisze:
Hi!
> I think GDA must be considered, as a developer platform, because
> Anjuta depends on it. I think other projects may can take advantage of
> its features to save metadata, documents, history, etc. on database
> engines and share with others by using central servers or
I think GDA must be considered, as a developer platform, because
Anjuta depends on it. I think other projects may can take advantage of
its features to save metadata, documents, history, etc. on database
engines and share with others by using central servers or so.
2010/3/8 Alberto Ruiz :
> 2010/3
On Mon, 2010-03-08 at 09:57 +0100, Tomeu Vizoso wrote:
> Have you considered talking a bit about coarser components such as
> abiwidget, evince, vte, webkit/gtk+, tinymail-ui, gtksourceview,
> empathy-gtk, etc?
There is no libempathy-* any longer.
All programming should be done with telepathy-gl
2010/3/8 John Stowers :
> Forgive me if I misrepresent Lennart here, but I thought the PulseAudio
> policy [1] was "use GStreamer, libcanberra or ALSA (if you know what you
> are doing)", and then PulseAudio will keep out of your way.
>
> Therefore, for the purposes of this list, having GStreamer a
On Mon, 2010-03-08 at 10:23 -0600, Brian Cameron wrote:
> However, I do think more energy should be focused on the truly
> cross-platform interfaces that everybody uses. At the very least, the
> documentation should avoid making assumptions about these sorts of
> interfaces being used by everyone.
>
> I'm growing a bit sick of GNOME having to be in this "limbo" situation
> where it can't stick to any technology because downstream
> distributions choose not to ship some components by default.
>
> PackageKit and PulseAudio are two projects that are pretty well
> aligned with the GNOME platf
Alberto/Shaun:
I agree that there is no reason why the developer docs should not
include good documentation for modules such as PackageKit, PulseAudio,
PolicyKit, and udev (DeviceKit & friends or whatever they are called
this month).
That said, OpenSolaris does not distribute any of these. How
Le lundi 08 mars 2010 à 15:54 +, Alberto Ruiz a écrit :
> I'm growing a bit sick of GNOME having to be in this "limbo" situation
> where it can't stick to any technology because downstream
> distributions choose not to ship some components by default.
Ever wondered why we choose not to ship t
2010/3/8 Josselin Mouette :
> Le dimanche 07 mars 2010 à 15:16 -0600, Shaun McCance a écrit :
>> * PackageKit
>
> I don’t think we should consider PackageKit as a core development
> interface, but rather as an optional service. It doesn’t integrate
> properly with all distributions, and not all use
Le dimanche 07 mars 2010 à 15:16 -0600, Shaun McCance a écrit :
> * PackageKit
I don’t think we should consider PackageKit as a core development
interface, but rather as an optional service. It doesn’t integrate
properly with all distributions, and not all user setups make it useful,
especially t
2010/3/8 Tomeu Vizoso :
> Have you considered talking a bit about coarser components such as
> abiwidget, evince, vte, webkit/gtk+, tinymail-ui, gtksourceview,
> empathy-gtk, etc?
Guys, I think Shaun is trying to focus in a handful of components
first, the main ones, he already has a lot on his pl
On Sun, Mar 7, 2010 at 22:16, Shaun McCance wrote:
> Hi folks,
>
> I'm working on what to include in the Platform Overview.
> This affects what gets focused on in the introductions
> and howtos in my developer documentation plan:
>
> http://live.gnome.org/DocumentationProject/Planning/DeveloperDoc
El dom, 07-03-2010 a las 15:16 -0600, Shaun McCance escribió:
> Hi folks,
>
> I'm working on what to include in the Platform Overview.
> This affects what gets focused on in the introductions
> and howtos in my developer documentation plan:
>
I just wanted to high five Shaun for JFDI. I owe you
2010/3/7 Shaun McCance :
> Hi folks,
>
> I'm working on what to include in the Platform Overview.
> This affects what gets focused on in the introductions
> and howtos in my developer documentation plan:
>
> http://live.gnome.org/DocumentationProject/Planning/DeveloperDocs
>
> I've tried starting t
2010/3/7 Shaun McCance :
> On Sun, 2010-03-07 at 22:32 +, Philip Withnall wrote:
>> On Sun, 2010-03-07 at 15:16 -0600, Shaun McCance wrote:
>> > I'm going to begin sketching out the content plan for
>> > the Platform Overview based on this. If I've forgotten
>> > something, please tell me. If
On Sun, 2010-03-07 at 22:32 +, Philip Withnall wrote:
> On Sun, 2010-03-07 at 15:16 -0600, Shaun McCance wrote:
> > I'm going to begin sketching out the content plan for
> > the Platform Overview based on this. If I've forgotten
> > something, please tell me. If you feel strongly that
> > any
Hi!
> On top of this, I would like to have a section where we
> highlight application plugin APIs. I'll be hunting for
> places where developers can plug into our desktop. If
> you want your application highlighted, send me an email
> to make sure I don't overlook it.
Well, would be cool to add
On Sun, 2010-03-07 at 23:34 +0100, Emilio Pozuelo Monfort wrote:
> On 07/03/10 22:16, Shaun McCance wrote:
> > I'm going to focus on the following programming languages:
> >
> > * C
> > * C++
> > * Java
> > * JavaScript
> > * C#
> > * Perl
> > * Python
>
> > I'm going to begin sketching out the c
2010/3/7 Robert Ancell :
> Is soup required now that we have GIO?
GIO doesn't implement an http client at all, yes, soup is definitively needed.
Although I would like to see more integration between Soup and GIO in
the future (like using GMemoryIntputStream instead of Soup.Buffer or
the ability t
Is soup required now that we have GIO?
On 8 March 2010 08:16, Shaun McCance wrote:
> Hi folks,
>
> I'm working on what to include in the Platform Overview.
> This affects what gets focused on in the introductions
> and howtos in my developer documentation plan:
>
> http://live.gnome.org/Documenta
2010/3/7 Emilio Pozuelo Monfort :
> On 07/03/10 22:16, Shaun McCance wrote:
>> I'm going to focus on the following programming languages:
>>
>> * C
>> * C++
>> * Java
>> * JavaScript
>> * C#
>> * Perl
>> * Python
>
>> I'm going to begin sketching out the content plan for
>> the Platform Overview ba
On 07/03/10 22:16, Shaun McCance wrote:
> I'm going to focus on the following programming languages:
>
> * C
> * C++
> * Java
> * JavaScript
> * C#
> * Perl
> * Python
> I'm going to begin sketching out the content plan for
> the Platform Overview based on this. If I've forgotten
> something, pl
On Sun, 2010-03-07 at 15:16 -0600, Shaun McCance wrote:
> Hi folks,
*snip*
> On top of this, I would like to have a section where we
> highlight application plugin APIs. I'll be hunting for
> places where developers can plug into our desktop. If
> you want your application highlighted, send me
Hi folks,
I'm working on what to include in the Platform Overview.
This affects what gets focused on in the introductions
and howtos in my developer documentation plan:
http://live.gnome.org/DocumentationProject/Planning/DeveloperDocs
I've tried starting this discussion before, but haven't
gotte
24 matches
Mail list logo
