[Dynapi-Widgetdev] Thanks for the input

[Cheston U. <che...@ya...>]

I want to start by thinking those who replied with
comments.

The site is in it's prototype stage, since I havn't
gotten the actual Content of the website applied yet,
it's basically just up to see if the interface engine
itself works. The Button/Tree menu is a Java applet. 
I havn't applied any content to it yet, and it is in
it's stock config from when I downloaded it.

About the duplicate HTTP problem...
   I started without the HTTP being inserted, and may
yet keep that part out. I believe in the next upload I
make, that particular feature will be fixed.

As far as Frame Breakouts...
   I figure that most websites that Students will be
going to from my page won't have that script.  If they
do, oh well.  Can't have it all, and can't control the
whole internet.

Screen Resizing...
   Unfortunately, there's a slight glitch that causes
the layers of WebDICE to be 15 pixels short of the
window width.  While I suspect this has something to
do with the scrollbars of the browser, there's nothing
that can be done about it, as far as I know.  The only
way to get everything to dimension right, is to
re-size the window AFTER everything is loaded.  This
is done by maximizing the page, if it isn't allready. 
If it is, however, the window size will increase by 1,
then decrease by 1.  This makes the page "shimmy", and
that fixes the problem.  Since the computers at the
School are very old (P133s), and have 800x600
resolution, the browser becomes VERY cramped, unless
it's maximized.  Given the target audience (very old
machines), It will most likely stay as it is. .  I
will look into allowing the window to start
non-maximized, however.  Perhapse I can whip up a
settings cookie or something.  If anyone has ideas
reguarding that, mail me some juicy details.  We'll
talk.

Now, for the widget...
    I pretty much decided that this WebDICE interface
is not going to be a single widget, but perhapse a
small collection of Widgets, each being a component of
the total Engine.  (Why would anyone need more than 1
WebDICE interface per site, anyway? It's DynAPI, so
everything can be changed on-the-fly.)
    My previous widget-building ventures dont seem to
work right, and if anyone has specifics on how to go
about converting this massive script into a
widget-based engine... I'd love the info.

Thanx to everyone.



_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca