On 6 Sep., 19:59, Thomas Broyer t.bro...@gmail.com wrote:
But honestly, I don't understand how this design is any different from
redirecting to the login page (unless maybe you have a cancel button
that leaves you in the app, i.e. without reload)
Well, from my point of view it would be nice if
Just for the completeness: I recall what was the problem with the GWT
integration:
As I said I had an iframe with the src attribute pointing to a
separate html file with the login form. Then, to inject the JS code
for form submission I needed to wrap the form. But I did not get
access to the
Thomas,
I was too quick when saying that it works with iframes: The login page
was shown correctly and the browser offered autofill, but
FormPanel.wrap caused an exception which I could not get away (i think
a JS exception).
Then I tried a combination of both - external login and visual GWT
Hello Magnus,
That's called Breaking out of frames [1]. If you need your app to be
able to detect a valid login, then you'll need to communicate from
within the iframe to the hosting app that the login was ok (have a
look at window.name transport in this case [2])
[1]
On 6 sep, 19:22, George Georgovassilis g.georgovassi...@gmail.com
wrote:
Hello Magnus,
That's called Breaking out of frames [1]. If you need your app to be
able to detect a valid login, then you'll need to communicate from
within the iframe to the hosting app that the login was ok (have a
Hmmm...I would like to get my peace with this, but...
I now created an invisible iframe in my host html.
On login I just show it, so it's a native html form.
It's not so nice as a DialogBox, but it works.
I cannot see why this is bad.
Why is it bad?
You see, I cannot let it go... :-)
Magnus
Hi Thomas,
I have thought about this the whole day now and it really sounds
interesting to me to give it a try with external login, but - if I
understood you right - I see a big disatvantage:
Many applications are not or should not be usable at all when the user
is not logged in. But there are
Hi Thomas,
I have thought about this the whole day now and it really sounds
interesting to me to give it a try with external login, but - if I
understood you right - I see a big disatvantage:
Many applications are not or should not be usable at all when the user
is not logged in. But there are
On Wed, Sep 1, 2010 at 6:42 AM, Magnus alpineblas...@googlemail.com wrote:
Hi Thomas,
I have thought about this the whole day now and it really sounds
interesting to me to give it a try with external login, but - if I
understood you right - I see a big disatvantage:
Many applications are
On Sep 1, 3:42 pm, Magnus alpineblas...@googlemail.com wrote:
Hi Thomas,
I have thought about this the whole day now and it really sounds
interesting to me to give it a try with external login, but - if I
understood you right - I see a big disatvantage:
Many applications are not or should
On 31 août, 11:38, Magnus alpineblas...@googlemail.com wrote:
Hi Thomas,
didn't you propose exactly this method which is referenced in the
document I referred to?
Yes, and I implemented it, and I now regret.
On 30 Aug., 10:48, Thomas Broyer t.bro...@gmail.com wrote:
...which violates
Hi folks,
is it the common opinion for GWT apps to have a separate login page?
(Thomas, your cache example seems a bit artificial to me (although I
believe that you know why you recommend a separate login page).)
Could someone please provide an example for a separate login page? I
wonder if this
On 31 août, 19:34, Magnus alpineblas...@googlemail.com wrote:
Hi folks,
is it the common opinion for GWT apps to have a separate login page?
(Thomas, your cache example seems a bit artificial to me (although I
believe that you know why you recommend a separate login page).)
Having built 2
On 30 août, 07:45, Magnus alpineblas...@googlemail.com wrote:
Hi,
I implemented a login form suitable for auto-complete by the browser
nearly exactly as described here:
http://borglin.net/gwt-project/?page_id=467
...which violates rule #3: do not move the form around or the browser
will
14 matches
Mail list logo
