Tim Ellison wrote:
... or the sound a user makes when they see a Swing app start up.
ROTFL :-)
Tim
Davanum Srinivas wrote:
Pluggable look and feel
(http://java.sun.com/j2se/1.4.2/docs/api/javax/swing/plaf/package-summary.html)
-- dims
On 2/14/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrot
hehe :) good one for those uninitiated...that's with an 'i' like so
(http://images.google.com/images?hl=en&q=pilaf)
-- dims
On 2/14/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
> Isn't it a rice dish?
>
> Stefano Mazzocchi wrote:
> > Anton Avtamonov wrote:
> >> Yeah, thank you Tim.
> >>
> >>
... or the sound a user makes when they see a Swing app start up.
Tim
Davanum Srinivas wrote:
> Pluggable look and feel
> (http://java.sun.com/j2se/1.4.2/docs/api/javax/swing/plaf/package-summary.html)
>
> -- dims
>
> On 2/14/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
>> Anton Avtamonov w
Isn't it a rice dish?
Stefano Mazzocchi wrote:
Anton Avtamonov wrote:
Yeah, thank you Tim.
I also thought about SwingWT when saw Stefano's letter.
Unfortunately such approach have serious problem with supporting PLAF
concept, as I know :-(, but really very fast (thanks to swt :-))
what's PLA
Pluggable look and feel
(http://java.sun.com/j2se/1.4.2/docs/api/javax/swing/plaf/package-summary.html)
-- dims
On 2/14/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
> Anton Avtamonov wrote:
> > Yeah, thank you Tim.
> >
> > I also thought about SwingWT when saw Stefano's letter.
> > Unfortunat
Anton Avtamonov wrote:
Yeah, thank you Tim.
I also thought about SwingWT when saw Stefano's letter.
Unfortunately such approach have serious problem with supporting PLAF
concept, as I know :-(, but really very fast (thanks to swt :-))
what's PLAF?
--
Anton Avtamonov,
Intel Middleware Produc
Yeah, thank you Tim.
I also thought about SwingWT when saw Stefano's letter.
Unfortunately such approach have serious problem with supporting PLAF
concept, as I know :-(, but really very fast (thanks to swt :-))
--
Anton Avtamonov,
Intel Middleware Products Division
On 2/13/06, Tim Ellison <[EM
http://swingwt.sourceforge.net/
(I merely mention it, not recommending it)
Regards,
Tim
Stefano Mazzocchi wrote:
> Anton Avtamonov wrote:
>> On 2/13/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
>> [snip]
>>> The other thing to consider is to follow apple's advice and implement
>>> Swing usin
Anton Avtamonov wrote:
On 2/13/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
[snip]
The other thing to consider is to follow apple's advice and implement
Swing using native widgets. I don't know what this entails in terms of
complexity but I always found stupid that swing is barely scratching
Anthony Green wrote:
On Mon, 2006-02-13 at 13:38 +0300, Sergey Soldatov wrote:
In my opinion the only area to use Cairo is the Java2D part of AWT.
Unfortunately any additional layer between 2D and native calls may
dramatically affect the performance of UI, especially Swing.
GNU Classpath is us
On Mon, 2006-02-13 at 13:38 +0300, Sergey Soldatov wrote:
> In my opinion the only area to use Cairo is the Java2D part of AWT.
> Unfortunately any additional layer between 2D and native calls may
> dramatically affect the performance of UI, especially Swing.
GNU Classpath is using Cairo, but I th
On 2/13/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
[snip]
> The other thing to consider is to follow apple's advice and implement
> Swing using native widgets. I don't know what this entails in terms of
> complexity but I always found stupid that swing is barely scratching the
> surface of wh
Alexey Petrenko wrote:
I'll check the Cairo. Thanks for pointing...
my pleasure.
Well, that Graphics object at some points needs rendering to the screen
doesn't it? :-)
Yep. :)
But Graphics object is a small part of AWT...
agreed, yet having a solid and hardware accelerated graphics part (
Sergey Soldatov wrote:
> In my opinion the only area to use Cairo is the Java2D part of AWT.
> Unfortunately any additional layer between 2D and native calls may
> dramatically affect the performance of UI, especially Swing.
>
Yes, that's what GNU Classpath does. Using Cairo for other things mean
In my opinion the only area to use Cairo is the Java2D part of AWT.
Unfortunately any additional layer between 2D and native calls may
dramatically affect the performance of UI, especially Swing.
On 2/13/06, Leo Simons <[EMAIL PROTECTED]> wrote:
>
> On Mon, Feb 13, 2006 at 02:04:18AM +0100, Tor-Ei
I'll check the Cairo. Thanks for pointing...
> Well, that Graphics object at some points needs rendering to the screen
> doesn't it? :-)
Yep. :)
But Graphics object is a small part of AWT...
--
Alexey A. Petrenko
Intel Middleware Products Division
Tor-Einar Jarnbjo escreveu:
Stefano Mazzocchi wrote:
Another think that I wonder, for the windowing stuff, why don't we use
Cairo[1]?
Isn't Cairo just a rendering library? AFAIK, it does not offer any kind
of e.g. portable widget access, which is probably the most tricky thing
to implement
On Mon, Feb 13, 2006 at 02:04:18AM +0100, Tor-Einar Jarnbjo wrote:
> Stefano Mazzocchi wrote:
>
> >Another think that I wonder, for the windowing stuff, why don't we use
> >Cairo[1]?
>
> Isn't Cairo just a rendering library?
Err, yes...it offers drawing primitives for things such as lines and p
Stefano Mazzocchi wrote:
Another think that I wonder, for the windowing stuff, why don't we use
Cairo[1]?
Isn't Cairo just a rendering library? AFAIK, it does not offer any kind
of e.g. portable widget access, which is probably the most tricky thing
to implement for AWT. Swing can be impleme
On Sat, Feb 11, 2006 at 12:08:55PM -0500, Stefano Mazzocchi wrote:
> Ryan Bloom wrote:
> >As one of the original authors of APR, I would like to suggest that
> >instead of using OS dependant native code, when we get to the point of
> >writing awt, we should create an apr-window project, and create
Ryan Bloom wrote:
As one of the original authors of APR, I would like to suggest that
instead of using OS dependant native code, when we get to the point of
writing awt, we should create an apr-window project, and create the
library for the abstraction layer. I have had enough conversations
with
21 matches
Mail list logo