On Tue, May 5, 2009 at 3:05 PM, Shaun McCance <[email protected]> wrote:
> Hey folks,
[...]
> I would like to get people's opinions on what technologies
> we should be pushing.  I'm interested both in the here and
> now and in what people think the Gnome 3 message should be.
>

Hi,
   Great time to brain-storm what we have...

I think we should put some emphasis on the devtools suite in
general, a basic "we have tools" message is called for.

Personally, I always compile gnome relocated by hand, I tried
jhbuild years ago and found it clunky then, Im trying MacPorts
now and find it works awesome, where are we with jhbuild ?
theres also another one out there iirc, cant remember the name...

I would be interested to know, what do we all generally recommend
in terms of a tool/setup to compile gnome ?

... anyway, that should also be part of this message, we have tools
and we can make it easy for you to build...

[...]
>
> GConf -- Configuration system.  There is talk of a new
> system (see below).  But I think it's obvious that we need
> to be pushing something here.  So as long as GConf is what
> we have, it's what we push.

ditto GConf as dbus below, settings, setting observations and
messaging to into a need-to-have bundle IMO

[...]
> D-Bus -- Inter-process messaging system.  Lots of stuff is
> built on it.  How much do we want to push it directly?

I think we want to push this alot, applications need IPCs,
I would expect a book about developing with GNOME
technologies to include a chapter on IPC/settings and
an observer model (something like GConf I guess, we
have GConf over dbus ? or GSettings now ? sorry for
not knowing all the details ...).

>From what I gather... which is a little vague... using some
language bindings you can observe the state of an object
even if its in another process, GObject mapping over dbus
is something I heard of... does that really exist ? if so,
its something people need to hear about..

Anyway IMO we need to have an IPC to use in the platform.

[...]
>
> libxml2/libxslt -- We put these into the external deps
> a couple release cycles back.  Do we want to continue
> pushing them as part of our platform?
>

I think its important to have an xml library, what is here
to replace libxml2 ? (maybe I'm missing something...)


[...]
>
> Libchamplain -- Wicked cool mapping library.  This is
> not something I would have thought of as something we
> need to offer.  But now that it's here, it's a really
> compelling technology with a lot of potential.

+1 for the ooh-aah factor heh

> Clutter -- Are we actively embracing Clutter, or is it
> just something we're OK with people using?  The message
> is unclear.

I am privately embracing Clutter myself, I think its wrong
to consider it as a drop in replacement for GTK+,
right now I would probably recommend Clutter or another
leading canvas like hippo-canvas, to do anything really
fancy in a UI...

> WebKit -- More and more applications are finding uses
> for an embedded HTML rendering widget.  I think we need
> to provide one with a solid API.  WebKit seems to be the
> direction people are heading in.

just pointing out that the next generation mozilla (xulrunner)
will also sport a portable embeddable GTK+ widget... although I
dont really have an opinion about what we should push in
this regard...


Anyway I should get back to work... thanks for starting this
thread, Im also interested to hear what people have to say ;-)

Cheers,
        -Tristan
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Reply via email to