elementary-dev-community team mailing list archive

[Cassidy James <c@xxxxxxxxxxx>]

Hi everyone,

I'm not sure if nobody else saw this email, or if I'm just totally missing
the replies to it, or what, but I think it's very important. I'll just
leave it below. :)

Thanks,
Cassidy James


To: elementary-dev-community@xxxxxxxxxxxxxxxxxxx
From: Lucas Baudin <xapantu@xxxxxxxxx>
Date: Wed, 26 Oct 2011 19:29:23 +0200

Hi,

We need to discuss about the first release of granite. What do we want in
it?

I personally think all main features are here now, remaining points are:


   - *Better contractor integration*: we have a stub of methods for that,
   but we may need some widgets, some docs, etc...
   - *PopOvers debugging*: I think there is not a lot of bugs for the
   popovers, excepted the bug of double PopOvers (if you try to put a popover
   in a popover, it behaves oddly). API checks are needed here too. And
   non-compositing detection (to fallback to a basic dialog).
   - I*ntroduce a Granite.Init function?* It might be needed in the future,
   so, having it now may be better. It could be used to detect the compositing
   for instance, or whatever.
   - *License changes*: do we want to switch to a LGPL base?

We need this first release *before* Luna to be sure to have well tested
packages of it, and to force us to freeze the api for the 0.2.x branch. And
it might be useful if some distributions want to put one of our apps in
their repo (I can't see Debian or Fedora putting a snapshot of our trunk in
their package). And it would be reassuring for developers to have a fixed
basis.

Thoughts?
Lucas