Linux for PDAs / Re: [Nautilus-list] current thinking on canvas vs. anti-aliased canvas
- From: Kevin Rochowski <krochows cisco com>
- To: Maciej Stachowiak <mjs eazel com>
- Cc: Seth Nickell <seth eazel com>, nautilus-list lists eazel com
- Subject: Linux for PDAs / Re: [Nautilus-list] current thinking on canvas vs. anti-aliased canvas
- Date: Mon, 19 Jun 2000 10:49:36 +0200
At 08:37 16/06/2000 -0700, Maciej Stachowiak wrote:
Seth Nickell <seth eazel com> writes:
> I realize that there are various factors governing the deployment of the
> anti-aliased canvas vs. the regular canvas. However it would help me
> decide how much / how good / how specific gradient code I plan to write
> depending on current thinking and factors (and guesses) going into the
> decision. While the canvases are somewhat compatible (eg it shouldn't be
> too hard to move code between the two) I think it would be preferable to
> at least point the code I'm writing in a particular direction. This code
> could be deferred...but it looks like people are going to be wanting
> things like good 3-point gradients fairly soon (and it'd be better to
> use a generic framework ripped off, say, the gimp rather than dealing
> specifically with every case). Flame me!
>
OK, you asked for it. :-) I think we should do the minimum work
required to do the current required features (decently rendering
simple 2-point linear gradients), or, if we decide we need more
complex gradient rendering, add appropriate tasks to the `required'
milestone.
As far as the canvas goes, it is possible we may ship with the ability
to switch between the two modes still present, since there is a major
tradeoff of performance vs. graphics quality, and the desired point in
the tradeoff may not be the same for all users.
- Maciej
I believe that there is an area that we are all overlooking - that of
multi-platform flexibility. Currently we are looking at Linux on a
"standard" PC platform, and through Nautilus are trying to make it as user
friendly yet as flexible as possible. However, we should also note that
some developers are looking at putting embedded Linux into other
environments such as PDAs, which have not only different screen sizes /
colour depths, but also different usability concerns (the need for clean
interfaces, large icons etc).
In the case of something such as XML, the data and the representation of
that data are separate - so the way that I see it, it should be possible to
design a page that uses long descriptions and fancy graphics for PCs yet
uses cleaner formatting and simplified graphics for a PDA or Internet
Appliance.
I think that some thing such as Nautilus is a good idea not only for the
desktop, but for any graphical Linux application. Imagine being able to use
Nautilus as the application browser on a palmtop such as the palm and you
might see what I'm getting at.
So my reason for saying this all here is that surely the rendering should
be as flexible as possible, all the way from zero anti-aliasing all the way
to 36 bits or higher, depending on the environment / user prefs. We need
flexibility of the kind mentioned above to provide the real "killer" app.
Kevin
________________________________________
Kevin Rochowski
Systems Engineer
Cisco Systems Ltd
3 The Square
Stockley Park
Uxbridge
Middlesex UB11 1BN
United Kingdom
Direct Line: +44 (0)20 8756 9163
Mobile: +44 (0)7710 634698
Email: krochows cisco com
http://www.cisco.com/go/video/
http://www.cisco.com/go/iptv/
http://www.cisco.com/go/ipvc/
________________________________________
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]