On Oct 29, 6:29 am, lkcl [EMAIL PROTECTED] wrote:
rummikub has 110 images loaded onto the page. firefox takes about 5-8
seconds to add all the tokens, one-by-one with javascript (compiled
from python of course). pyjamas-desktop, usingwebkit, takes about 2
seconds. the javascript is gone
I'm partly humoured partly intrigued. How would this GWT have access
to the File System and other such resources, since by definition
javascript can't do any of that kind of thing. What if it wants to do
other cool things on your system?
I've never been a fan of building bad desktop clients,
lkcl schrieb:
so, in this specific instance, being able to migrate - pretty much
instantaneously and with zero code modifications from a [too-slow]
browser-based environment to a [very-fast] desktop-based one would be
a definite advantage, yes?
especially given that 1) running compiled
On Oct 26, 10:16 pm, ross [EMAIL PROTECTED] wrote:
this thread makes me laugh :)
I will continue to :
-use pyjamas only in bed
i _love_ talking about pyjamas because i get advertised about women's
nightwear with googlemail.
-use GWT for building my sizzling new web app
-use J2SE to
On Oct 27, 9:35 am, Thomas Broyer [EMAIL PROTECTED] wrote:
2008/10/27 Guy Rouillier [EMAIL PROTECTED]
Ross, you are thinking too narrowly. Think of a single code base. When
it runs on the desktop, it has access to local file system and other OS
facilities. When it runs in a browser
On Oct 27, 2:51 am, Ian Bambury [EMAIL PROTECTED] wrote:
If you gave a practical example it might help people understand the benefits
ian, hi, i do know what you mean.
however, it is quite hard to give a practical example when what
you're talking about is that the entire GWT application -
On Oct 27, 3:54 pm, Magno Machado [EMAIL PROTECTED] wrote:
What's the point on running the application on desktop if it will run in the
exact same way that it would do on browser?I mean... If the desktop app will
look exactly equals to the browser version, with the same look and feel,
same
On Oct 28, 6:17 am, GWBasic [EMAIL PROTECTED] wrote:
The browser and desktop are fundamentally different environments,
pyjamas-desktop shows that that's no longer really the case; it shows
that there are sufficient concepts in the DOM model to map one-for-one
into desktop widget set
Ian Bambury schrieb:
I write desktop apps when I have to because I need to use the local file
system plus or minus the web, or when I need to eliminate the lag of the
net or I need my users to be able to work in a lead-lined box or on the
train in tunnels that haven't yet been fitted with an
Hi Lothar,
I can't actually think of a single situation where I myself would design a
web app (or even a desktop app) with 10,000+ tree nodes open at the same
time, and I don't think I've ever come across one while surfing the web, but
if I'm ever forced to build one that the general public might
Ian Bambury schrieb:
I can't actually think of a single situation where I myself would design
a web app (or even a desktop app) with 10,000+ tree nodes open at the
same time, and I don't think I've ever come across one while surfing the
web, but if I'm ever forced to build one that the
So independent of the fact that you might not be able to imagine
reasons, it doesn't mean that there aren't any ;-)
Oh no, I wasn't suggesting that at all - quite the opposite. It's precisely
because I *don't* have the imagination that I need help :-)
For example, if you are writing
Ian Bambury schrieb:
For example, if you are writing applications where browsers are
forbidden, then why would you write it as a browser-based application
and then convert to a desktop app and never use the browser version?
If you're developing an application that should be sold as
2008/10/27 Guy Rouillier [EMAIL PROTECTED]
Ross, you are thinking too narrowly. Think of a single code base. When
it runs on the desktop, it has access to local file system and other OS
facilities. When it runs in a browser like GWT does today, it degrades
nicely and only loses
What's the point on running the application on desktop if it will run in the
exact same way that it would do on browser?I mean... If the desktop app will
look exactly equals to the browser version, with the same look and feel,
same functionalities, it's better to not have a desktop version at all
On Oct 26, 4:18 am, GWBasic [EMAIL PROTECTED] wrote:
I don't see the point. GWT is designed to run in a browser;
it's designed to run in a browser - and with a little bit of work,
can be turned into a _desktop_ widget-set with an *identical*
interface.
if you
want to do a true desktop
however, you _should_ be designing your app around an MVC concept of
some kind _anyway_.
Is everything else officially politically incorrect now, then?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web
(or something like that)
but I haven't had time to look into them.
--
From: lkcl [EMAIL PROTECTED]
Sent: Sunday, October 26, 2008 12:12 PM
To: Google Web Toolkit Google-Web-Toolkit@googlegroups.com
Subject: Re: Suggestion: GWT port to Desktop
On Oct
ross wrote:
Limiting your
desktop application to run on a JRE equivalent to that which is
emulated by the GWT will by quite funny. Let's do the time warp baby
Ross, you are thinking too narrowly. Think of a single code base. When
it runs on the desktop, it has access to local file
If you gave a practical example it might help people understand the benefits
Ian
http://examples.roughian.com
2008/10/27 Guy Rouillier [EMAIL PROTECTED]
ross wrote:
Limiting your
desktop application to run on a JRE equivalent to that which is
emulated by the GWT will by quite funny.
I don't see the point. GWT is designed to run in a browser; if you
want to do a true desktop application, there are plenty of desktop
development systems that are much better. C#, Java, Objective C...
They're a dime a dozen.
If all you're looking to do is get rid of the browser chrome and give
:)
Rather than copy the previous messages here, I'll just point you to the
threads which you can read from the archives:
ANN: Pyjamas 0.3 Released
Suggestion: GWT port to Desktop
And here are some links the original author provided:
http://pyjd.org for Pyjamas-Desktop
http://pyjs.org
you :)
Rather than copy the previous messages here, I'll just point you to the
threads which you can read from the archives:
ANN: Pyjamas 0.3 Released
Suggestion: GWT port to Desktop
And here are some links the original author provided:
http://pyjd.org
Hi... I just picked up on this thread. How does this work and where can I
read more about this project? Is there a way to have GWT code running on
mobile apps?
Looking forward to hearing from you :)
On Tue, Oct 21, 2008 at 3:46 PM, lkcl [EMAIL PROTECTED] wrote:
I known nothing
you to the
threads which you can read from the archives:
ANN: Pyjamas 0.3 Released
Suggestion: GWT port to Desktop
And here are some links the original author provided:
http://pyjd.org for Pyjamas-Desktop
http://pyjs.org for Pyjamas
For your last question, GWT is (clever) Javascript
I known nothing aboutpyjamas, but I'm intrigued about what lkcl has
been discussing. What he has done (and is suggesting could be done with
GWT) is to have a browser-based application (via a Java-Javascript
translater like GWT) and a desktop application (via a direct Java
runtime) derived
On 17 oct, 15:45, lkcl [EMAIL PROTECTED] wrote:
does anyone want to be able to run applications written for GWT as a
*desktop* application?
if so, port GWT _back_ into pure java, using Java bindings to
Webkit's DOM model to manage the screen.
Or just package your GWT app as an Adobe AIR
You could also use something like Prism or Fluid to run it as a desktop
app. Bind it to Google Gears and you're good to go.
--
Arthur Kalmenson
On Fri, Oct 17, 2008 at 11:14 AM, Thomas Broyer [EMAIL PROTECTED] wrote:
On 17 oct, 15:45, lkcl [EMAIL PROTECTED] wrote:
does anyone want to
much :-)
does anyone want to be able to run applications written for GWT as a
*desktop* application?
if so, port GWT _back_ into pure java, using Java bindings to
Webkit's DOM model to manage the screen.
... is that better? :)
l.
--~--~-~--~~~---~--~~
On Oct 17, 3:14 pm, Thomas Broyer [EMAIL PROTECTED] wrote:
On 17 oct, 15:45,lkcl[EMAIL PROTECTED] wrote:
does anyone want to be able to run applications written for GWT as a
*desktop* application?
if so, port GWT _back_ into pure java, using Java bindings to
Webkit's DOM model to
I'm obviously missing something here...
I have a requirement to build an Ajax web site. To make the coding easier, I
use GWT so I can write in Java.
i'm advocating running _native_ java - because all of the javascript is
replaced
You are suggesting that I write it in the GWT subset of Java,
Ian Bambury wrote:
I'm obviously missing something here...
I have a requirement to build an Ajax web site. To make the coding
easier, I use GWT so I can write in Java.
i'm advocating running _native_ java - because all of the javascript
is replaced
You are suggesting that I
folks, hi,
as you've no doubt seen, i mentioned in the announcement of pyjamas
0.3 that there's a parallel project, pyjamas-desktop, which is a port
of pyjamas to run as a desktop widget set and framework. it works ...
incredibly well, thanks to webkit.
the way it's done is by some glib /
33 matches
Mail list logo
