7 Apr
2009
7 Apr
'09
6:57 p.m.
Jean-Vincent Drean wrote:
On Mon, Apr 6, 2009 at 12:35 PM, Vincent Massol
<vincent(a)massol.net> wrote:
This is not UI related stuff. This is not about a new flashy cool skin,
but about having a usable and reusable skin. Toucan is much to fragile
to fix. The prioritized list of points that need to be addressed is:
- Reusable skin, with not so fragile CSS rules (changing something
breaks something else right now) and easy to customize parts. Building
on top of the Toucan is close to impossible. This is something that our
custom development team would really love, and something our users are
complaining about.
- Usability improvements. While this can be done incrementally inside
Toucan, its fragility makes it very hard to introduce such changes.
- Bugfixing and ensuring a uniform aspect. Same as above.
The fact that we've spent more than a year on stabilizing a skin that is
still far from being stable says something to me. And that's not that we
should use it more. The scroll problem on Linux is not it's biggest
problem, and definitely not the only one.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
* We consider the 2.0 release as a normal release that we release
early September:
- 2.0 M1: 22 June 2009
- 2.0 M2: 13 July 2009
- 2.0 M3: 3 Aug 2009
- 2.0 RC1: 17 Aug 2009
- 2.0 RC2/Final: 31 Aug 2009
+1
* We add a new skin
I'm not sure about this:
1/ We've spent more than a year stabilizing toucan and we still have
issues on some browsers/OS (namely linux).
2/ We lack resources to work on UI related stuff.
3/ XE 1.0 was albatross, it seems logical to me that our next major
release uses toucan.
Don't get me wrong, I'd like that we have a new skin but I think that
if we can spend time on skin development this summer we should focus
on making toucan better before 2.0 (css cleaning, bug fixing, drop
albatross).
WDYT ?