Re: [xwt-users]XWT requirements ?

"Jean-Guillaume LALANNE" <jeanguillaume.lalanne-JhP/[email protected]>
Newsgroups gmane.comp.java.xwt.users
Message-ID <004401c34793$fe710450$62d4430a@JELALANNE>
OK.
Thanks Emiliano for the info.
I never heard about this VMWare tool before but it seems that it emulates
the different
OS on another...And it uses only a part of the RAM... Is it right ?
So we this tool, I would be able to know if XWT runs well on windows 95 and
Solaris and Hp-ux. Wouldn't I ?

Cheers
Jean-Guillaume


----- Original Message -----
From: "Emiliano Heyns" <[email protected]>
To: "discussion list for people using XWT to create applications"
<[email protected]>
Sent: Friday, July 11, 2003 10:02 AM
Subject: Re: [xwt-users]XWT requirements ?


> On Fri, Jul 11, 2003 at 09:33:18AM +0200, Jean-Guillaume LALANNE wrote:
>
> > My only concern is about standard. The XWT description is XWT 's
propriety.
> > It would have been nice to stick to a W3C standard like UIML. But maybe
it
> > isn't possible.
> > Anyway, XWT is just great !
> > I am now wondering about the openeness of this application.
> > Is it possible to use XWT (I mean the plug-in xwt-xxx.exe) on a widows
95 ,
> > 75MHz, 64MB RAM desktop ?
>
> While I haven't tested it on a 75Mhz machine, I routinely test XWT in a
> 64MB VMWare session.
>
> > Of course, it depends of the widget complexity in terms of memory usage.
> > Is it possible to use it on a mobile device (PDA, pocket pc) ? Already
> > experienced or not ?
>
> Haven't tried (anyone want to donate a test device ;)
>
> > And what is the way to compile the XWT plug-in for a target plateform
like
> > SOLARIS or HP-UX or AIX ?
>
> Configuration of the gcc cross-compiler AFAIK, but the JVM version
> should already work on those platforms.
>
> --
> Emiliano
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.xwt.org/listinfo/users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.