I've been trying to interrogate various objects. it seems that calling
these methods as part of the body's onload event of a web page doesn't seem
to work properly with Atlas. If I use a button's onclick event, everything
seems to work properly. Is this a timing problem? if so, is there a proper
way to get the onload event of a page to work?

Wally

--
Wallace B. McClure
"The Harder I Work, the Luckier I Get."
Listen to "The ASP.NET Podcast" at http://www.aspnetpodcast.com/
Database Award: http://url123.com/vc3er
Microsoft MVP - Visual Developer ASP/ASP.NET
AspInsider
"AJAX for ASP.NET" Coming Soon!
ADO.NET Book: http://url123.com/vc2bu
865-693-3004
118 Durwood Rd.
Knoxville, TN 37922
http://www.scalabledevelopment.com/
Blog: http://weblogs.asp.net/wallym/

You should add a function called 'pageLoad', which will be called by Atlas (specifically the Application instance) once window.onload was raised and Atlas is done processing the markup.

Eventually, the pageLoad "magic" function will go away. Instead, you can already use the load event of the application object. In your xml-script section, add this to components:

<application load="yourFunction"/>

load is a full Atlas event, which means that you can also use declarative actions with it, for example to invoke a web service.

Where can I find complete documentation about all these tricks?

Unfortunately, for the moment, the only documentation are the quickstarts and Wilco's class browser.

Putting my webservice call in a function called pageLoad instead of one that's called by the body's onLoad event seems to work in IE but not in Firefox 1.07. I just upgraded Firefox to version 1.5 and it still gives the same error.

I take the last post back. I'm having a lot of trouble getting the web service proxy to work even in IE.

My code looks like this:
// pageLoad is the Atlas load event
function pageLoad()
{
alert(SimpleWS);
}

I found out why it wasn't working on IE. It now works and I'm still trying to find out why it's not working in Firefox.

My problem might be related to the fact that I have two frames that have the same Atlas web reference. The problem was that in Debug/AtlasRuntime.js on lines 971, 981 and 988, baseName was not defined. It was defined on one frame and not the other. Specifically, I have two columns and it was defined in the first frame but not the second. I looked in AtlasCompat.js and replaced baseName with localName and that made it work fine. Hope this helps for the next CTP.

I found my problem. I was overwriting Atlas's Event object with my own. It wasn't an issue until I started using Atlas, of course.

can you give me a clear example of application start calling into a javascript function?

i can't seem to get it to work.

thanks

 

There already is an example in one of the previous post, but here you go:

<script type="text/xml-script">
  <page xmlns:script="http://schemas.microsoft.com/xml-script/2005">
    <components>
      <application load="yourFunction"/>
    </components>
  </page>
</script>

<script type="text/javascript">
  function yourFunction() {
    alert("Load function called.");
  }
</script>

strangely enough, this doesn't seem to work for me

i cut and paste the example directly into the body element of an existing atlas web page, and it doesn't seem to work.

is there something special i need to declare in the scriptmanager section?

 

Does anything else work?

yes, i am able to make atlas calls back to a web service on this page

i don't do any atlas UI stuff on the page.