We currently have the InvokeMethod call that can be made server-side to call javascript on the client. But there's no good (read: easy) way to add custom javascript that can be called via InvokeMethod. We're limited to either calling intrinsic methods that exist on the browser or calling methods that exist in VWG stock controls or in custom controls that we write.

Writing a custom control is a lot of work (even extending an existing one) just to emit a bit of javascript.

I'm proposing the addition of another method to the Form class that would allow javascript to be sent to the client, therefore giving us the opportunity to later call InvokeMethod on that javascript. Something similar to RegisterClientScriptBlock. The script could be emitted into the HEAD, thereby callable server-side.

Thanks.

-- Michael

Hi Ori,

It all started in this post, where I was looking to be able to resize the initial browser size ... more in line with the way WinForms works, where the size that we set the window at design time is the size that the window first appears. I can call a javascript function to do this, but I need to get that function (and its helper functions) into the browser's environment space first.

That's where I got stuck. It seemed that I could derive from Form and output my own javascript, but that was a really heavy approach for something that seemed, on the surface, to be an action that should be easy. And in my experience, if I have to work hard against a framework to do something that should be easy, it's almost always my lack of understanding of the framework. So I asked the question, and from what I got from Palli it seems that I was right -- there is no easy way to add javascript to the output.

Thanks for any help you can provide.

-- Michael

Hi Ori,

I have written applications where the content is in a Panel which is not anchored to any side, thereby allowing the panel to float in the center of the browser, but that's not the effect I'm after. I don't have an issue with the user resizing the browser, and the content will, of course, behave appropriately when they do (just like a WinForm application), but I am wanting the browser window to start its life at a certain size (just like a WinForm application).

That being said, there's really two things going on here:

1) I believe I have the javascript for multi-browser support. I'm not concerned about that, but that's really the smaller picture.

2) The bigger picture is, as far as I've been able to find, there's really no good (read: easy) way to add custom javascript to a VWG form. In general, I believe that's a problem that needs solved. Solutions could be an api call that injects the javascript in an appropriate place, a control that can get added to the form to output javascript, or something I haven't thought of, but IMHO that facility needs to be there.

I can see the issue where the javascript emitted by the programmer might conflict with that emitted by the VWG engine, but that would be on the programmer's shoulders to fix. A few simple caveats in the documentation may be enough to help the programmer determine would can and should not be done in custom javascript. But that's, I believe, an issue today with custom controls anyway.

-- Michael