The debugger is specifically for debugging WebOS, it was crucial for the development
of it. It keeps track of the files being loaded, and makes testing things easy. The
built-in JS debugger in Netscape is just plain awful, so we grab the window.onerror
messages and route them to our debugger, and there's also an evaluate field with
simply allows you to type in commands and evaluate them in the scope of the webos
window so you can test things on the fly.
The library loader is a pretty complex piece of work. A series of buffers controls
when objects get inherited and methods are added - but for this to work we couldn't
make use of the easy standard JS prototyping. So we have our own inheriting and
method adding system. For the Netscape version js files are loaded into layers just
like with LoadPanel, and then from there the library loader handles the rest, ensures
that all the dependent files are loaded before doing the prototyping.
But trust me, this is not something you'd want for DynAPI. It took a considerable
amount of time to get it working 100% effectively.
Dan
On Fri, Feb 16, 2001 at 08:49:24AM +0100, Pascal wrote:
>
> Question, that debugger is Javascript based!? (interested for obvious
> reasons)
>
>
> Also wondering, I know your ofcourse limited on your work for DynAPI2 and
> sharing info.. but can we find any info somewhere on how dynamic loading is
> done? is it done using the loadpanel ideas? If you can't, or don't want to
> mention this I totally understand.. but just wondering :) any tech paper
> about it openly available
>
>
> Pascal Bestebroer ([EMAIL PROTECTED])
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]Namens Dan Steinman
> > Verzonden: vrijdag 16 februari 2001 12:08
> > Aan: [EMAIL PROTECTED]
> > Onderwerp: [Dynapi-Dev] Screenshot of the new WebOS API
> >
> >
> > A lot of you have probably been wondering what the hell I've
> > been up to. Obviously I haven't been doing as much work on
> > the DynAPI as I used to, but that doesn't mean I haven't been
> > busy with DHTML. Most of the original group of
> > "DynDevelopers" are aware I work at WebOS.com, but since
> > there's a lot of new people around these days this may be new
> > information.
> >
> > I've been working on the Netscape version of the next WebOS
> > API - this is a commerical quality DHTML/JavaScript API. It
> > goes far beyond the capabilities of DynAPI2, offering a
> > complete fully functioning platform for web based
> > applications. This version is unlike the original MyWebOS
> > product, this has been rebuilt from the ground up in pure JavaScript.
> >
> > We're gearing this toward companies. It's a commercial
> > product, with a price tag. I'm not in charge of selling it,
> > but the talk is it'll be around $1000 for a full license.
> >
> > I've posted a screenshot of what the final version will be
> > like. This was taken in Linux, running Netscape 4.75:
> >
> > http://fury161.dyndns.org/webos/webos-screenshot.jpg
> >
> > Everything you see there is a fully working toolkit. You got
> > dynamic library and application loading, layout managers, and
> > enough widgets to build just about anything you'd like, and a
> > handy debugger. All written in JavaScript, crossplatform,
> > works in Netscape 4.5 (Win32/Linux/Mac), IE 4.0, 5.0, 5.5
> > probably IE 6.0, and Mozilla in a future version.
> >
> > There will be a trial version of the API released in a month
> > or so. You'll be able to download it, play with it, but you
> > can't use it on your site or redistribute it unless you buy
> > it. The API is open though, you can make applications for
> > WebOS and distribute them as you please.
> >
> > If you've done anything at all in DynAPI2 you'll understand
> > almost immediately how to build apps in WebOS. Instead of
> > DynLayer, you have webos.ui.Component, instead of DynDocument
> > you have webos.getContentPane(), and the event system works
> > similarly. The differences lie mainly in the amount of
> > different widgets (although we call them "components" in
> > WebOS), and the manner in which you build applications.
> > DynAPI was built as sort of an add-on to existing pages.
> > WebOS is designed to dynamically load up new apps on the fly.
> > You insert WebOS into a page, and then load up your
> > applications into WebOS.
> >
> > If any of you are seriously interested in this for your
> > development and looking for something more robust than
> > DynAPI, give me an email (to: [EMAIL PROTECTED] or
> > [EMAIL PROTECTED]) and I'll forward you to the marketing
> > department and you can likely be on the list of the first
> > people to recieve an evaluation copy.
> >
> > Cheers,
> > Dan
> >
> > BTW - I'm still working on my java-based editor for DynAPI,
> > you'll see a first version of that released pretty soon.
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
