Go here: http://examples.roughian.com/#Widgets~PopupPanel and click the
"Show Popup" button - Now I would say that looks pretty modal. And you can
always blank the background completely if some of your users are so thick
they don't recognise from that that the screen has been disabled.
All you are
I would disagree - controls on the main page still looks active while
modal dialog that prevents their usage is present - is it not
frustrating as well? As, BTW, user has no way to visually distinguish
modal and non-modal dialogs, right?
Reallym there are to separate concerns - syncronous call as
Paraphrasing what I said above, I think developers are basically
trying to create a synchronous experience for their users*, which is a
perfectly reasonable goal, not to be confused with synchronous RPC
calls. Hopefully, recognizing that these are two different things
will help.
Walden
* "synch
You can emulate synchronous behavior by following these rules:
1. Any RPC or other call has to be made at the end of a method/
function. Theoretically, the call may return before the method has
finished. Don't put any other code at the end.
2. Don't use Timers or make sure all Timers have stopped
Synchronous calls could make sense when one builds a standalone
application with a browser. Synchronous calls in such use cases could
be a useful tool. For example, pre-AJAX database lookups had to
preserve state in addition to returning query results. The resulting
calls either had to fail or co
GWT is a powerful framework, and it is certainly possible to create a
Synchronous XHR with it, but it is such an epically bad idea that 1)
it is not available by default, 2) everyone who is familiar with GWT
development is warning you against doing it, and 3) we sure aren't
going to go thr
al0,
No, actually it's not a workaround. Its an even better user
experience, because if the controls on the page still look like they
are active (but they're not because the browser is locked up), then
the app is lying to the user, whereas if the controls are explicitly
inactive, then we're tell
ping2ravi,
It's true that good and poor are relative terms, and it's also true
that design can be viewed as a matter of selecting among tradeoffs.
The reason you (and others) receive so much flack on this list for
stubbornly insisting on a synchronous RPC mechanism is that it trades
off user expe
Hi,
Your use of a modal dialog, greyed button constitutes just a
workaround ror and (absent) synchronous call. If latter would be
present your code would be min. 3 times shorter and (IMHO) much more
clear.
Oleksandr
--~--~-~--~~~---~--~~
You received this mes
Hi Waiden,
I put forward a way of getting the (AFAICT) desired result, but the OP still
seems to want to lock the user out of the browser.
The OP's question was (and still seems to be) how to do this.
Ian (aka Lan)
2008/8/27 walden <[EMAIL PROTECTED]>
>
> Hi group,
>
> First of all, Ian, when
Hi group,
First of all, Ian, when I sent your wife for beer 7 years ago, she
returned immediately with the cold ones. I'm not sure what happened
in your case, maybe something in your environment [you?] that accounts
for the different result.
It occurs to me [being serious now] that when newbs a
Ravi,
You can't give developers all options to design their own way. JavaScript
doesn't do all options, therefore you can't have all options in GWT.
The only thing a synchronous call does which an async call doesn't, is to
lock up the user's browser - all tabs, not just yours.
This is, relativel
Jason,
I think any framework should give all options to developer to design
his own way, and poor design and good design are all relative terms,
so cant do generalization of that.
But thanks for sharing your thoughts.
cheers,
Ravi :)
On Aug 26, 7:14 pm, Jason Essington <[EMAIL PROTECTED]> wrote
It's OK, it was very asynchronous. I was in the pub, and I phoned her to get
her to stock up the refrigerator for when I got home. Pre-loading it. But
she obviously lost the thread somewhere.
2008/8/26 Jason Essington <[EMAIL PROTECTED]>
>
>
> On Aug 26, 2008, at 12:33 PM, Ian Bambury wrote:
>
On Aug 26, 2008, at 12:33 PM, Ian Bambury wrote:
> I sent my wife out for beer 7 years ago.
>
> Where's she got to, that's what I want to know.
Good thing that wasn't a synchronous request, or you'd still be stuck
on the couch!
> PS: Don't get me wrong, I'm not complaining...
7 years without
2008/8/26 gregor <[EMAIL PROTECTED]>
>
> Jason, I think u are doing less than justice to yourself:
>
>
> http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/faca1575f306ba0f#
>
> Now, has anybody got any argument with that?
>
I sent my wife out for beer 7 years ago.
Where's s
Jason, I think u are doing less than justice to yourself:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/faca1575f306ba0f#
Now, has anybody got any argument with that?
On Aug 26, 7:18 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote:
> I can't think of a single good reason t
I can't think of a single good reason to lock up all tabs in the user's
browser.
In your example:
Show a modal popup for the user to log in.
Once submitted, disable the Submit button.
If the login fails, show a message and enable the Submit button.
If the login succeeds, remove the modal popup
nope, again, this use case shows a poor decision of using a
synchronous request. In fact I'm not aware of a single good use of a
synchronous request in a browser.
I do this very thing using Async RPCs. I start by opening a modal
dialog. the user can type his credentials into the "login" dia
yes i do have have workaround for this, but was just wondering if i
can use any of GWT feature.
Also i read in GWT FAQ, GWT do not support Synchronous calls and in
future they are not planning to have it(they have some theory). So i
guess need to implement my own workaround.
http://code.google.com
can't you just do:
doTaskCallBack {
onResponse(...) {
userService.doSynchronousTask(...);
}
}
Wouldn't that just give the synchronous effect?
On Mon, Aug 25, 2008 at 6:24 AM, ping2ravi <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> Does any one know how to make Synchronous calls using GWT.
And there is no reason to do so. Unless you want to lock p the browser, in
which case, just use a tight endless loop.
2008/8/25 Ian Petersen <[EMAIL PROTECTED]>
>
> On Mon, Aug 25, 2008 at 7:24 AM, ping2ravi <[EMAIL PROTECTED]> wrote:
> > So i guess this is not the way to make synchronous call in
There is only one who knows how to make synchronous calls in GWT. He
spends most of his time wandering in the desert, and usually kills
anyone brave enough to approach him. You'll need a camel...
Just kidding. :-)
Walden
On Aug 25, 7:24 am, ping2ravi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> D
On Mon, Aug 25, 2008 at 7:24 AM, ping2ravi <[EMAIL PROTECTED]> wrote:
> So i guess this is not the way to make synchronous call in GWT
> Can any one point me how to do that. Or its not possible at all in
> GWT.
There is no GWT-approved way to make a synchronous call to the server.
See also:
htt
Hi All,
Does any one know how to make Synchronous calls using GWT.
Currently i am using GWT to build services, creating files like
com.app.client.MyService.java
//One function in this interface
doMyTask(ParamTpye myparams) throws ClientException;
com.app.client.MyServiceAsync.java
//One functi
25 matches
Mail list logo
