This looks more difficult than I first thought. I think I'd have to
somehow also attach to the form element. I would need to set the action to
go to a servlet. I don't see a way to take some HTML and get the FORM
element.
I may try a completely different way to do this. I'll create a servle
Hi,
I'm using protected members, nothing private. So any change to those
methods in the Widget API will break compatibility for a lot of projects.
But regardless, if the widget API is ever changed or something better is
created that would allow us to use Renderers and do it in a supported way
then
> They way I use the widgets, maybe not supported, work perfectly. It is
> made part of the widget hierarchy. And when I remove the widget, everything
> is again cleaned up. I did a lot of memory leak investigating and it is
> just working the way it should. Even if the window close event is
Jens,
They way I use the widgets, maybe not supported, work perfectly. It is made
part of the widget hierarchy. And when I remove the widget, everything is
again cleaned up. I did a lot of memory leak investigating and it is just
working the way it should. Even if the window close event is trigger
> From my experimentation with wrap() I can see very few circumstances in
> which case it is actually useful. It appears to be useful where there is
> only one page. The way nesting of widgets is handled would make it tricky
> in anything more complicated.
>
Yes, imagine a login application
I guess what I would do for a fallback option is to simply show the form in
the GWT app. If the user wants to alter any form fields, they could click
a link and the form could be showed in a JSP page (new window). From a
JSP we could get everything we need. But it would be nice to have this w
So, what is recommended - or what is good practice for a case where one has
a page of HTML and needs to do something relatively simply? Think of a
form (HTML generated externally) and the form needs to be displayed in a
GWT Composite-derived class. The only thing desired is to allow the form
Is my case considered static HTML? The HTML is not known at run time. It
is received once the app is up and running. It is not altered at all. The
intent is to display it. The HTML is generally always contains a form and
there is an option to allow the user to alter some of the form fields a
In my case I have no choice.
If you just need it for one widget I agree it is maybe over-the-top. But I
want the rich behavior of custom widgets, without the cost of
re-implementing all the workarounds and tricks in my own onBrowserEvent
then wrapping is the way to go since all you do this way is
I think you kind of misuse the *.wrap() method. They are meant to be used
with static html pages that you want to enhance with GWT.
I think what you really want for now is to extend Widget and overwriting
onBrowserEvent(), e.g.
MyServerFormWidget extends Widget {
MyServerFormWidget() {
On Monday, June 3, 2013 9:39:08 AM UTC+2, stuckagain wrote:
>
> Hi,
>
> OK, I forgot about that part - I once had to go through these issues as
> well but forgot soon after.
>
> You need to subclass HTMLPanel and SubmitButton to get what you want. The
> HTMLPanel only supports adding widget
Hi,
OK, I forgot about that part - I once had to go through these issues as
well but forgot soon after.
You need to subclass HTMLPanel and SubmitButton to get what you want. The
HTMLPanel only supports adding widgets to existing HTML elements, not just
make an Element into a widget without detach
Now, this has gone from fun to just downright frustrating. I'm stuck at
the point of finding and wrapping the submit button. I get the ubiquitous,
"A widget that has an existing parent widget may not be added to the detach
list". Looked through the dozens of posts regarding that message. The
Form submission works like any form, so you will need a servlet to handle
the post.
You will have to redirect the post to an internal IFrame otherwise your
document will be replaced. This is what the GWT Form widget is doing.
David
On Thu, May 30, 2013 at 5:43 PM, Mike Dee wrote:
> Thanks for p
Thanks for pointing me in the right direction.
One last question. How is the form submission handled? Is a servlet
needed? In this case, the form will simply save any changes (to a db) and
redisplay itself.
Thanks,
Mike
--
You received this message because you are subscribed to the Google
Hi,
The HTMLPanel accepts HTML snippets, you should not put and entire HTML
page in it since it is part of the window document.
So what you are doing is correct. Otherwise you will have to play with
Frames (which you should avoid due to memory leak issues).
For the second question: the HTMLPanel
Hi,
I'm hoping this can be done with relative ease in GWT. I need to integrate
a couple of features that involve HTML that is generated on the fly.
Basically, the app gets some XML and sends it to a service which returns
HTML (via an XSL transform).
There are two cases.
1) The first is easy
17 matches
Mail list logo
