dynapi-dev — List related to the current DynAPI Core development

Re: [Dynapi-Dev] DynLayer Box Model Fix

[Raymond I. <xw...@ya...>]

We will support both inner and outer borders in border
manager. So which ever way the use wants it then they
got it.

--
Raymond Irving

--- Michael Bystrom <mi...@mi...>
wrote:
> Den 03-09-15 00.47, skrev "Kevin"
> <ke...@ke...>:
>  
> > Michael wrote:
> > 
> >> Raymond,
> >> 
> >> I STRONGLEY suggest that we render the borders
> inside the layers...
> >> All the widgets that we create can NOT have a
> border outside the layer...
> >> If a layer is "100px in width" then it needs to
> be a "100px in width"
> 
> > If you set a 1px border in CSS for 100px wide box
> it will be in total 102px
> > The same for adding margin and padding it is an
> outer dimension and that's
> > the way it is (well except for the broken box
> model in IE5). If I have got
> > this wrong please point me to the correct
> reference thanks!
> > Kevin
> 
> Jepp! the borders are suppose to go on the outside
> http://www.w3.org/TR/REC-CSS1#formatting-model
>
http://www.w3.org/TR/REC-CSS2/box.html#box-dimensions
> 
> ... all boxes have a core content area with optional
> surrounding padding,
> border and margin areas.
> 
> I just found it easier to work with borders if 100px
> is a 100px and not 98px
> using a 1px border
> 
> Should stick to CSS2 recommendations that's
> perfectly fine with me
> 
> Just a idea.
> 
> :)
> 
> Michael
> 
> >>> Hi Everyone,
> >>> 
> >>> I've managed to get DynLayers to now support CSS
> >>> borders in ie, opera and mozilla. All DynLayers
> will
> >>> render the same way in all browsers. NS4 does
> not work
> >>> well with CSS so I don't know it if makes sense
> to try
> >>> and create a fix for that.
> >>> 
> >>> Should I add this to the setCSSBorder() to
> >>> BorderManager or should we just create a
> different
> >>> libary (e.g. CSSBorder)?
> >>> 
> >>> 
> >>> --
> >>> Raymond Irving
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] Hello List

[Michael B. <mi...@mi...>]

Den 03-09-14 18.12, skrev "Leif W" <war...@us...>:

> ----- Original Message -----
> From: "Michael Bystrom" <mi...@mi...>
> To: <dyn...@li...>
> Sent: Friday, September 12, 2003 5:59 AM
> Subject: Re: [Dynapi-Dev] Hello List


>> Man o Man you have been busy I hope I didn't make you stay up all night

> I did stay up until about 2330 which isn't too late, but I was sleepy all
> day yesterday.  ;-)

Yepp the code does that to you


>>> 2) On the first page, the content is centered in IE 6 only, and is not
>>> centered in the other 3 browsers.

>> Hmm ?? It should not be centered align:left

> It's most definitely centered in my IE 6.  Screenshot:
> http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/IE6_c
> entered.gif

Yes there it is!!!
Well Have to fix that now don't I :P



>>> 4) In the HTML Document demo, in IE 6, when dragging the "txt1.html" icon,
>>> the image disappears, then IE starts transferring data, gets the image, then
>>> displays it.  I seem to remember some recent discussion about this issue
>>> (how to cache images in IE using the DynAPI).  The whole experience in IE is
>>> affected by this.  Every time anything changes, all images are either
>>> reloaded or compared to the server, and it's slow.

>> Is this for ALL the image swapping?
>> I use this.icon.setBgImage()
>> If this is the case we/I  have to re-think the use of setBgImage and use
>> This.icon.setHTM("<img src=''>")
>> I know I did this with a client once and I changed the thumb in the
>> scrollpane to use set.HTML()

>>> * Note: when looking at
>>> the more complex things, the entire demo is so slow I'd call it unusable or
>>> unacceptable in a real-world setting.

>> IOS is very complex I give you that, and I think that broadband is a
>> necessity. But to call it unusable is harsh.
>> 
>> I've let people play with it a my local library Win IE6 (where the have a
>> nice set up for the school kids, broadband) and I works perfectly fine, and
>> I've also set it up at local networks where I think it works best. I also
>> tested in some other ways.
>> 
>> But I would agree that IOS NEEDs a fast computer there is a lot of computing
>> that is going on.
>> 
>> On a personal note:
>> I really done my best to speed things up ex. The "list.js" script is one
>> example where I use id's to identify the nodes so that if we have huge
>> tree's it will only change collapse the selected nodes. Just a simple setup
>> is faster then using the browsers style "display" feature.

> Mozilla Firebird 0.6.1 was fastest, with Mozilla 1.5 beta being about 2-3
> times slower, and IE 6 being 20-30 times slower than Mozilla Firebird 0.6.1.
> Some clarification on this.  I had my IE 6 cache setting to check for newer
> versions every visit to page.  With this setting, each and every movement or
> change on the page causes ALL images to be compared, and it's really
> unusable.  When I changed the cache setting to the other extreme, to never
> look for newer versions, then it's usable, maybe 2-3 times slower than
> Mozilla 1.5 beta.

I have the cache (mac) IE5 setup that way too (always) but hey It's a Mac...
So it works... Hehe :)

> I'm using a Athlon XP 2700 with 1GB RAM 512MB swap on a cable connection at
> 1.5Mbit/s down / 128 kbit/s up.  So line and CPU speed isn't an issue.  What
> kills the performance with the cache setting to check every time, is the
> overhead for creating a connection and doing the comparison.  The files are
> small, but when there's 100 files, and it takes about 1-2 seconds to create
> a connection to the server and compare, that's easily 100-200 seconds,
> nearly two minutes to over three minutes waiting for the images to all
> reload, after doing something simple like for example drag a Texter about 50
> pixels in one direction.  That's why I called it unusable, under those
> specific circumstances.

Ok I understand, I think I have to get me a Windows machine to play with, I
wonder what 

 
> I could do a video screen capture but I hope my description is adequate.

No need.

> Further note, I have the same "check every visit to the page" cache setting
> in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, but they perform very well.

Yes I agree

> If this is specifically a browser problem, you may need to have a disclaimer
> on the page that IE with cache setting to check on "every visit to the page"
> will degrade performance drastically.

Yes agree



>>> 8) In Folder in Symbol Mode, in all browsers, there's no "taskbar" so it's
>>> difficult to get to windows that lie underneath other windows, unless moving
>>> or minimizing all windows above the target window.  This quickly becomes
>>> cumbersome.

>> Are you talking about Windows like taskbar??
>> I have no plans to add such a feature, but I think it's a good Idea and will
>> put it on the board.

> I think it's a necessity to have something like this, yes.  Even if it's
> like a floating taskbar or something.  What you've got is a basic windowing
> system, but no window manager.  Windows(tm) barely has what I'd call a
> window manager, but the taskbar feature is the minimum requirement.

I've started to write a WindowManager



>>> 9) In Folder in Symbol Mode (and probably anything with a DynAPI window with
>>> scrollbars), can't scroll with the mousewheel.  It scrolls the entire
>>> browser window, not the DynAPI window.

>> I have no plans to include such a feature it.

> This is a great inconvenience as most people nowadays have a mouse wheel,
> and it greatly increases efficiency using a windowed environment.  Maybe if
> you port this to DynAPI 3.x I'll try and add the feature.  :)

Ok



>>> 11) In all demos, in all browsers, double clicking on the text label of
>>> something selects the text in addition to the expected behaviour or opening
>>> the file, folder, or starting the app.

>> Yes I know this I know of no way a fix this.

> Think this bug was fixed in DynAPI3.

I will look into it.



>>> 13) In ColorRGB, all browsers.  Browser's scrollbars show that there's more
>>> content on the page, but there's no visible elements and there should be no
>>> scrollbars expected.
>> 
>> I don't understand what you mean
> 
> In the browser, when I first click on the ColorRGB demo link, the new
> browser window opens, and there's no scrolling.  When I double-click on
> ColorRGB(), then scrollbars appear, which look as if only 20% of the page is
> being displayed.  So I scroll down and there's nothing there.  Screenshot
> (note the scrollbar on the right side):
> http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/Color
> RGB_scrolling.gif

Aha, jepp I know abaut this, the ie's scrollbars does not know that the
RGB's scrollpane is clipped it thinks it just goes on...


> No comments to 21, 22?

Sorry missed them.



>>> 21) In Texter App Mode (and all other dragable / resiable elements), in all
>>> browsers. All four size should allow resizing of the window in the
>>> specified direction only.  All 4 corners should allow simultaneous resizing
>>> in both directions specified.  Currently only the lower-right is resizable.

Jepp that's the way I like it, I know Windows has that but I've always used
the corner, BUT I'm seriously thinking about making the window pane borders
part of the dragable window.

>>> 22) In Texter App Mode (and all other dragable / resiable elements), in all
>>> browsers. There needs to be an indication when the mouse is over a
>>> button, or a draggable area.

Well I thought of that but decided that the less clutter there is the faster
the app will run, I don't want to evoke a onmouseover a trigger a method for
each thing... All that glimmer isn't gold :O)

>>> Maybe change to a reverse highlight for menu
>>> buttons, or like any apps in Windows, a little box with shading appears
>>> around the items in the menu bar.  In windows when moving the mouse over a
>>> resizable element, the mouse pointer changes to some arrows.

Yes I could change the cursor to change for the resize corner, yes
On the board

>>> While this may not be easy to do in all browsers, you can change the thing
>>> underneath the mouse i.e. make the left border change highlighted colors
>>> when mouse over, etc..


>>> Also, having "resizable" or "draggable" hotspots look "grippy"
>>> somehow, instead of all the same grey, might be an option, or might not.

Hehe well that's why I have a theme system so that YOU can design a new skin
I have a new skin that I will include with the 3.0 port.

:)




>> 23,24,25) Yes! I can not fix this.

> Yep, just thought I'd be complete in my QA.  ;-)  We've seen this in DynAPI
> 3x, someone reported to Mozilla, and they said it was a duplicate of another
> bug they were already aware of.  But didn't say when they were to fix it.
> Maybe we should be squeakier / noiseier to Mozilla?  Or are we too squeaky
> already?

Mozilla team has fixed all the bugs I've reported exept the key events, but
they have dropped support for mac OS9+ so there will never be a fix.
I will be moving over to MacX soon. They usually listen a fix stuff. Nice
people.





> No comments 26-34?

No.
I will rewrite the Viewer and your suggestions and input is noted. The
viewer was written as a test for me if I could see a Futerama Cartoon and
then I just added a buch of stuff... Need to rethink some things.




>> Leif Thanks for your input very helpful, thanks a million. Really :)
>> A little sad that you think it's unusable (but if it is because image  cache,
>> this will be fixed)
> 
> Ah, hope I cleared this up earlier, but it IS usable in Mozilla 1.5 beta and
> Mozilla Firebird 0.6.1 (except for the Mozilla family specific input event
> bug), and it was only unusable in IE 6 with the image caching issue while
> checking on every visit to the page.
"
Yes I now cleared the "cache of this... Hehe


>> IOS was written on a 300hz Macintosh powerbook and all of the examples are
>> work perfectly fine and fast. (on mozilla, it does not matter what api you
>> use or if you hard code on IE5, it does not handle complex dhtml very
>> well... And this will NEVER change since Microsoft has discontinued the
>> browser)
>> 
>> I know that IOS and DynEditor can work perfect on Windows too, I just have
>> to get my hands on one of those machines
> 
> Wish I could help out.  If you lived a little closer I'd let you borrow one.
> ;-)  If I had a faster connection I'd let you VNC into one.

Well I just have to let go of my pride and for the first time buy a (dare to
say it) Windows PC... Usch.

:)


>> Now I going to crawl under my house and install a new antenna system. Ijust
>> installed a brand new (read HUGE THX 3 preamps and 4 tvs) Hometheater and my
>> girlfriend finally got that tv in our bathroom.
> 
> BATHROOM?!?!  Wow...
> 
> Leif

Yepp we have a huge bathroom and now she can lay in the bathtub and watch
movies. No surround system yet... But maybe later :)




>> Life is sweet
>> Michael
>> 
>> 
>>> 
>>> ----- Original Message -----
>>> From: Michael Bystrom
>>> To: dyn...@li...
>>> Sent: Monday, September 08, 2003 9:48 AM
>>> Subject: [Dynapi-Dev] Hello List
>>> 
>>> 
>>> Hi there dynapi folks
>>> 
>>> I just signed on and wanted to let you guys know that I've been playing
>>> around with dynapi for a while now and the result is IOS (internet
> operating
>>> system)
>>> 
>>> IOS is a virtual OS. It creates a virtual desktop in your browser
> window.
>>> You can drag, drop, move, open, close, type and more
>>> 
>>> I'm using a older version 2.55 ( I now see that you have a version 3 :)
>>> nice )  that has been modified for the Macintosh platform, the dynapi is
> NOT
>>> Mac friendly.
>>> 
>>> I only using the dynapi for object creation and events
>>> 
>>> I've written a written a bunch of new widgets that works fine on the
>>> Macintosh and windows for that matter.... :)
>>> 
>>> I've just released the first version and would like you guys to help out
>>> with some debugging, code suggestions, new widgets etc...
>>> 
>>> I got some cool ideas for IOS in the future and would like to see it
> grow.
>>> 
>>> Go to http://www.michaelbystrom.com download and play
>>> 
>>> I could say a million more things but I'll save it for a another day.
>>> 
>>> Nice day...
>>> Michael

Re: [Dynapi-Dev] DynLayer Box Model Fix

[Michael B. <mi...@mi...>]

Den 03-09-15 00.47, skrev "Kevin" <ke...@ke...>:
 
> Michael wrote:
> 
>> Raymond,
>> 
>> I STRONGLEY suggest that we render the borders inside the layers...
>> All the widgets that we create can NOT have a border outside the layer...
>> If a layer is "100px in width" then it needs to be a "100px in width"

> If you set a 1px border in CSS for 100px wide box it will be in total 102px
> The same for adding margin and padding it is an outer dimension and that's
> the way it is (well except for the broken box model in IE5). If I have got
> this wrong please point me to the correct reference thanks!
> Kevin

Jepp! the borders are suppose to go on the outside
http://www.w3.org/TR/REC-CSS1#formatting-model
http://www.w3.org/TR/REC-CSS2/box.html#box-dimensions

... all boxes have a core content area with optional surrounding padding,
border and margin areas.

I just found it easier to work with borders if 100px is a 100px and not 98px
using a 1px border

Should stick to CSS2 recommendations that's perfectly fine with me

Just a idea.

:)

Michael

>>> Hi Everyone,
>>> 
>>> I've managed to get DynLayers to now support CSS
>>> borders in ie, opera and mozilla. All DynLayers will
>>> render the same way in all browsers. NS4 does not work
>>> well with CSS so I don't know it if makes sense to try
>>> and create a fix for that.
>>> 
>>> Should I add this to the setCSSBorder() to
>>> BorderManager or should we just create a different
>>> libary (e.g. CSSBorder)?
>>> 
>>> 
>>> --
>>> Raymond Irving

Re: [Dynapi-Dev] DynLayer Box Model Fix

[Kevin <ke...@ke...>]

See below.

Michael wrote:

> Raymond,
> 
> I STRONGLEY suggest that we render the borders inside the layers...
> 
> All the widgets that we create can NOT have a border outside the layer...
> If a layer is "100px in width" then it needs to be a "100px in width"

If you set a 1px border in CSS for 100px wide box it will be in total 102px
The same for adding margin and padding it is an outer dimension and that's
the way it is (well except for the broken box model in IE5). If I have got
this wrong please point me to the correct reference thanks!

It would be good to emulate correct CSS behaviour in NS4 with adding
outer borders. Or more precisely:
1) increasing the size of the layer (and content auto centers) then adding
the borders inside 
2) creating a new larger container layer center anchoring the original layer
then adding the borders inside.

Something like this is in dynapi3x anyway!

> The DynAPI is a precise tool so the layers NEED to be that to.
> 
> Well that's what I think :-)

It is precise. We just all need to sing from the same style sheet. This has
been a subject of discussion in the past. If personal projects have had the
development of DynAPI move in one direction then it would be difficult
to change back to the CSS standard (for complicated page layouts).

I don't care either way I'm just making the point about consistency and
CSS. We've all put something in the dynapi project for own needs I guess. 

> I wrote something for the IOS a while back (included in the IOS release)
> when I got sick of using extra lay's for borders (to reduce the memory).
> "borderbutton.js" 
> 
> This also takes care of all the parent's layer childern.
> 
> This is a old version and I made some dynapi3 hacks but you get the point.
> 
> There are some minor drawbacks (resizing) because the layers a manipulated
> and need to be realign.
> 
> Why no use shorthand for the CSS model
> lyr.setBorder("10px solid purple")

There is something like that:
lyr.setBorder(10,'red')
or
lyr.setBorder([1,2,3,4],['red','green','blue','yellow'])
or
lyr.setBorder([5,10],['top.gif','right.gif','bottom.gif','left.gif')
or
different side and corner images too.

> I've uploaded a test for you to see
> http://www.michaelbystrom.com/download/dynapi_border.zip
> 
> How big zip file can I send through to this list??

Quite small I think about 30k.

_

Kevin

> I've also inclued a css for a grid that I use now and then to test the
> locations of layers. I've also included some screen shots of examples.
> 
> Rock'n Roll
> Michael
> 
> 
> 
> > Hi Everyone,
> > 
> > I've managed to get DynLayers to now support CSS
> > borders in ie, opera and mozilla. All DynLayers will
> > render the same way in all browsers. NS4 does not work
> > well with CSS so I don't know it if makes sense to try
> > and create a fix for that.
> > 
> > Should I add this to the setCSSBorder() to
> > BorderManager or should we just create a different
> > libary (e.g. CSSBorder)?
> > 
> > 
> > --
> > Raymond Irving
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] DynLayer Box Model Fix

[Michael B. <mi...@mi...>]

Raymond,

I STRONGLEY suggest that we render the borders inside the layers...

All the widgets that we create can NOT have a border outside the layer...
If a layer is "100px in width" then it needs to be a "100px in width"

The DynAPI is a precise tool so the layers NEED to be that to.

Well that's what I think :-)

I wrote something for the IOS a while back (included in the IOS release)
when I got sick of using extra lay's for borders (to reduce the memory).
"borderbutton.js" 

This also takes care of all the parent's layer childern.

This is a old version and I made some dynapi3 hacks but you get the point.

There are some minor drawbacks (resizing) because the layers a manipulated
and need to be realign.

Why no use shorthand for the CSS model
lyr.setBorder("10px solid purple")

I've uploaded a test for you to see
http://www.michaelbystrom.com/download/dynapi_border.zip

How big zip file can I send through to this list??

I've also inclued a css for a grid that I use now and then to test the
locations of layers. I've also included some screen shots of examples.

Rock'n Roll
Michael



> Hi Everyone,
> 
> I've managed to get DynLayers to now support CSS
> borders in ie, opera and mozilla. All DynLayers will
> render the same way in all browsers. NS4 does not work
> well with CSS so I don't know it if makes sense to try
> and create a fix for that.
> 
> Should I add this to the setCSSBorder() to
> BorderManager or should we just create a different
> libary (e.g. CSSBorder)?
> 
> 
> --
> Raymond Irving

Re: [Dynapi-Dev] DynLayer Box Model Fix

[Kevin <ke...@ke...>]

"Raymond Irving" <xw...@ya...> wrote:

> Hi Everyone,
> 
> I've managed to get DynLayers to now support CSS
> borders in ie, opera and mozilla. All DynLayers will
> render the same way in all browsers. NS4 does not work
> well with CSS so I don't know it if makes sense to try
> and create a fix for that.

The setInnerBorder code could be changed now to add the
Highlighters as correct outer dimensions for NS4 (would
the new auto size stuff take care of the parents increased
size?).

> Should I add this to the setCSSBorder() to
> BorderManager or should we just create a different
> libary (e.g. CSSBorder)?

Add the above suggested NS4 code to new setCSSBorder
(default solid style) and put it in the bordermanager.js file
with the FixBoxModel code. If setCSSBorder is called on
a layer do a dynapi.onLoad FixBoxModel for that layer if
not already added?

I'm assuming the FixBoxModel code is doing something
similar to the previously posted:
http://jscript.dk/Util/BoxModelFix/
so all browsers have outer borders? I haven't had much
time to delv into this lately. 

-
Kevin

> 
> --
> Raymond Irving

Re: [Dynapi-Dev] WYSIWYG editor for the DynAPI

[Kevin <ke...@ke...>]

See below,

"Raymond Irving" <xw...@ya...> wrote:

> --- Michael Bystrom <mi...@mi...>
> wrote:
> > > 3) Have us create a CVS module (similat to the
> > logo
> > > module/directory) on the DynAPI Project for the
> > > source?
> > ......
> > .......
> > 
> > #3 I want this to evolve, I will always keep a
> > "stabile" version on my site
> > so we can point to that. I want this will be it's
> > home. But for the
> > development I agree with you, let everybody mess
> > with it. :)
> > 
> > I've never had to use a CVS dunno how it works! so
> > can you set it up? Or..
> > I guess I have to learn now :)
> 
> Well I can create a module (directory) on CVS for the
> editor so you just check it out the same way you would
> with dynapi3x. Is everyone in a greement with this?
> 
> Another thing I think we should first do is to convert
> the editor to work with 3.0 

That would be good.
 
> Btw can we call it Visual DynAPI Editor (VDE) as the
> "visual" tells the user exactly what it does?
> 
> > Raymond! Are you the admin if so, how many
> > subscriber do we have to this
> > list, 
> 
> Yes. I'm one of the developers the DynAPI project 
> with administrator priviledges.
> 
> Can't say for sure how many subscribers we have. But I
> do know that a lot of users are subscribed to the
> list. Some are only watching and waiting to see what
> will become of 3.0

I have done some bits and pieces for the projct but have
been watching recently.  
 
> You can look at the polls on the dynapi website
> dynapi.sf.net to see users feedback. For more
> publicity I would suggest you post a news article on
> the DynAPI website.
> 
> > I have a surprisingly low download count.
> > IOS: 11
> > Dyneditor: 19

Probably the same for the manual too. Can I drop
the later version of IOS over the Dyneditor's IOS. 

> >
> > How many are developing for the api
> >
> > Where are you guys located!

I am in London England.

-
Kevin

> We are all developers who are located all over the
> world. The DynAPI project is hosted on SourceForge wih
> I think is located in the US.
> 
> --
> Raymond Irving
> 
>  
> > I just moved back from Los Angels after 12 years to
> > Sweden.
> > 
> > Michael
> > 
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] Standardizing on the basic wigdet set

[Kevin <ke...@ke...>]

Hi,

I've just got the latest cut from cvs and catching up. I think things
are looking up - excellent explorer style menu in a scroll pane too.
If I understand this is different to an HTMLComponent? Sort of
a raw DynLayer extension.

I haven't had a good look at StyleManager yet so I can't comment.

-
Kevin

> Thanks Daniel,
> 
> Does anyone else have any other feedback?
> 
> 
> --
> Raymond Irving
> 
> --- Daniel Tiru <de...@ti...> wrote:
> > Hi Raymond!
> > 
> > For me it dont really matter, but we need some kind
> > of blueprint, and
> > aswell some kind of documentation on "how to build
> > widgets", regarding
> > the 
> > StyleManager's features, i think its good, however i
> > have not looked
> > into that one yet.
> > 
> > Best Regards
> > Daniel
> > 
> > 
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...] On
> > Behalf Of Raymond
> > Irving
> > Sent: den 11 september 2003 01:36
> > To: DynAPI-Dev
> > Subject: [Dynapi-Dev] Standardizing on the basic
> > wigdet set
> > 
> > 
> > Hi Everyone,
> > 
> > I think we need to standardize on a basic widget
> > format. Should we stick to the old method, use a new
> > 
> > theme-able or skin-able method or use StyleManager's
> > approach?
> > 
> > Need some feedback
> > 
> > 
> > --
> > Raymond Irving
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site
> > design software
> > http://sitebuilder.yahoo.com
> > 
> > 
> >
> -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
> http://www.mail-archive.com/dyn...@li.../
> > 
> > 
> > 
> > 
> >
> -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
> http://www.mail-archive.com/dyn...@li.../
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

[Dynapi-Dev] DynLayer Box Model Fix

[Raymond I. <xw...@ya...>]

Hi Everyone,

I've managed to get DynLayers to now support CSS
borders in ie, opera and mozilla. All DynLayers will
render the same way in all browsers. NS4 does not work
well with CSS so I don't know it if makes sense to try
and create a fix for that.

Should I add this to the setCSSBorder() to
BorderManager or should we just create a different
libary (e.g. CSSBorder)?


--
Raymond Irving




__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] Hello List

[Leif W <war...@us...>]

----- Original Message ----- 
From: "Michael Bystrom" <mi...@mi...>
To: <dyn...@li...>
Sent: Friday, September 12, 2003 5:59 AM
Subject: Re: [Dynapi-Dev] Hello List


> Den 03-09-11 05.37, skrev "Leif W" <war...@us...>:
>
> Man o Man you have been busy I hope I didn't make you stay up all night

I did stay up until about 2330 which isn't too late, but I was sleepy all
day yesterday.  ;-)

> :)
>
> Nice work
> Now let me run through the list with you

Erasing the fixed ones, and the to be fixed ones.

> > 2) On the first page, the content is centered in IE 6 only, and is not
> > centered in the other 3 browsers.
>
> Hmm ?? It should not be centered align:left

It's most definitely centered in my IE 6.  Screenshot:
http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/IE6_centered.gif

> > 4) In the HTML Document demo, in IE 6, when dragging the "txt1.html"
icon,
> > the image disappears, then IE starts transferring data, gets the image,
then
> > displays it.  I seem to remember some recent discussion about this issue
> > (how to cache images in IE using the DynAPI).  The whole experience in
IE is
> > affected by this.  Every time anything changes, all images are either
> > reloaded or compared to the server, and it's slow.
>
> Is this for ALL the image swapping?
> I use this.icon.setBgImage()
> If this is the case we/I  have to re-think the use of setBgImage and use
> This.icon.setHTM("<img src=''>")
> I know I did this with a client once and I changed the thumb in the
> scrollpane to use set.HTML()
>
> > * Note: when looking at
> > the more complex things, the entire demo is so slow I'd call it unusable
or
> > unacceptable in a real-world setting.
>
> IOS is very complex I give you that, and I think that broadband is a
> necessity. But to call it unusable is harsh.
>
> I've let people play with it a my local library Win IE6 (where the have a
> nice set up for the school kids, broadband) and I works perfectly fine,
and
> I've also set it up at local networks where I think it works best. I also
> tested in some other ways.
>
> But I would agree that IOS NEEDs a fast computer there is a lot of
computing
> that is going on.
>
> On a personal note:
> I really done my best to speed things up ex. The "list.js" script is one
> example where I use id's to identify the nodes so that if we have huge
> tree's it will only change collapse the selected nodes. Just a simple
setup
> is faster then using the browsers style "display" feature.

Mozilla Firebird 0.6.1 was fastest, with Mozilla 1.5 beta being about 2-3
times slower, and IE 6 being 20-30 times slower than Mozilla Firebird 0.6.1.
Some clarification on this.  I had my IE 6 cache setting to check for newer
versions every visit to page.  With this setting, each and every movement or
change on the page causes ALL images to be compared, and it's really
unusable.  When I changed the cache setting to the other extreme, to never
look for newer versions, then it's usable, maybe 2-3 times slower than
Mozilla 1.5 beta.

I'm using a Athlon XP 2700 with 1GB RAM 512MB swap on a cable connection at
1.5Mbit/s down / 128 kbit/s up.  So line and CPU speed isn't an issue.  What
kills the performance with the cache setting to check every time, is the
overhead for creating a connection and doing the comparison.  The files are
small, but when there's 100 files, and it takes about 1-2 seconds to create
a connection to the server and compare, that's easily 100-200 seconds,
nearly two minutes to over three minutes waiting for the images to all
reload, after doing something simple like for example drag a Texter about 50
pixels in one direction.  That's why I called it unusable, under those
specific circumstances.

I could do a video screen capture but I hope my description is adequate.
Further note, I have the same "check every visit to the page" cache setting
in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, but they perform very well.
If this is specifically a browser problem, you may need to have a disclaimer
on the page that IE with cache setting to check on "every visit to the page"
will degrade performance drastically.

> > 7) In the HTML Document demo, in all browsers: After maximizing the HTML
> > Document, scrollbars extend beyond the screen, when they probably should
> > not.  After minimizing, the scrollbars still remain, as if there's still
> > content going past the browser's viewable area.
>
> Yes I aware of this.
> If drag a simple dynlayer is out side the browser window the scrollbars
are
> activated then Check the "demo.dragdrop-collision.html" in the DynAPI 3x
>
> I don't know how to fix this.

Ok, this may be just one of those "open issues" or annoyances, but it
doesn't appear to affect performance too much otherwise, so non-critical.

> > 8) In Folder in Symbol Mode, in all browsers, there's no "taskbar" so
it's
> > difficult to get to windows that lie underneath other windows, unless
moving
> > or minimizing all windows above the target window.  This quickly becomes
> > cumbersome.
>
> Are you talking about Windows like taskbar??
> I have no plans to add such a feature, but I think it's a good Idea and
will
> put it on the board.

I think it's a necessity to have something like this, yes.  Even if it's
like a floating taskbar or something.  What you've got is a basic windowing
system, but no window manager.  Windows(tm) barely has what I'd call a
window manager, but the taskbar feature is the minimum requirement.

> > 9) In Folder in Symbol Mode (and probably anything with a DynAPI window
with
> > scrollbars), can't scroll with the mousewheel.  It scrolls the entire
> > browser window, not the DynAPI window.
>
> I have no plans to include such a feature it.

This is a great inconvenience as most people nowadays have a mouse wheel,
and it greatly increases efficiency using a windowed environment.  Maybe if
you port this to DynAPI 3.x I'll try and add the feature.  :)

> > 10) In Folder in List Mode, in all browsers, a user interface
suggestion, is
> > to put the files and folders on the right, (M$ Explorer style), and only
> > Folder tree on the left side.  Since I'm very familiar with windows
> > explorer, and it's one of the good things about M$ Windoze, I'd find the
> > Folder in List Mode much easier to use if it was set up this way,
>
> Are you talking about the Microsoft's explorer window? Yes that could be
> fun. But There would involve a SHIT load of layers to be created. But I
> would look nice...

Yes, like the M$ Windows Explorer.

> > And what about in column view mode,
>
> As for columns! The first version had columns sort able, BUT due to much
> pressure on the poor browser I removed this feature. I have have made some
> holes in the code so I might restate this feature but I think this have to
> use a simple CSS set up. But this is not something I will add soon.

As long as it's GPLed or similar open source, I could always add features.
:)

> > 11) In all demos, in all browsers, double clicking on the text label of
> > something selects the text in addition to the expected behaviour or
opening
> > the file, folder, or starting the app.
>
> Yes I know this I know of no way a fix this.

Think this bug was fixed in DynAPI3.

> > 13) In ColorRGB, all browsers.  Browser's scrollbars show that there's
more
> > content on the page, but there's no visible elements and there should be
no
> > scrollbars expected.
>
> I don't understand what you mean

In the browser, when I first click on the ColorRGB demo link, the new
browser window opens, and there's no scrolling.  When I double-click on
ColorRGB(), then scrollbars appear, which look as if only 20% of the page is
being displayed.  So I scroll down and there's nothing there.  Screenshot
(note the scrollbar on the right side):
http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/ColorRGB_scrolling.gif

> > 17) In ColorPicker (and possibly others, just noticed now), in Mozilla
1.5
> > beta.  There's a message in the JavaScript console after page load,
before
> > anything user input:
> > Warning: The stylesheet http://cyclone.he.net/cgi-bin/error404 was
loaded as
> > CSS even though its MIME type, "text/html", is not "text/css".
>
> This I don't get.
> I have only one stylesheet and is loaded correct.
> Hmm we just moved and upgraded all server software apache, perl, php,
mysql
> etc.. I know there are some problems with the referrals.

Might be helpful to check the web server logfiles to see what's causing the
404.

> > 21) In Texter App Mode (and all other dragable / resiable elements), in
all
> > browsers.    All four size should allow resizing of the window in the
> > specified direction only.  All 4 corners should allow simultaneous
resizing
> > in both directions specified.  Currently only the lower-right is
resizable.
> >
> > 22) In Texter App Mode (and all other dragable / resiable elements), in
all
> > browsers.      There needs to be an indication when the mouse is over a
> > button, or a draggable area.  Maybe change to a reverse highlight for
menu
> > buttons, or like any apps in Windows, a little box with shading appears
> > around the items in the menu bar.  In windows when moving the mouse over
a
> > resizable element, the mouse pointer changes to some arrows.  While this
may
> > not be easy to do in all browsers, you can change the thing underneath
the
> > mouse i.e. make the left border change highlighted colors when mouse
over,
> > etc..  Also, having "resizable" or "draggable" hotspots look "grippy"
> > somehow, instead of all the same grey, might be an option, or might not.

No comments to 21, 22?

> 23,24,25) Yes! I can not fix this.

Yep, just thought I'd be complete in my QA.  ;-)  We've seen this in DynAPI
3x, someone reported to Mozilla, and they said it was a duplicate of another
bug they were already aware of.  But didn't say when they were to fix it.
Maybe we should be squeakier / noiseier to Mozilla?  Or are we too squeaky
already?

> > 26) In Viewer Quicktime, in all browsers, when resizing the DynAPI
window
> > container thing, the Quicktime plugin does not reesize.  Maybe no need
to
> > have the DynAPI window resizable if the underlying plugin isn't capable.
> > 27) In Viewer Quicktime, in all browsers, when using the "minimize to
> > titlebar" (I know it's a MAC thing, there's no windows equivalent, and
it's
> > NOT the same thing as a windows minimize, so that's why I call it
minimize
> > to titlebar, as opposed to the assumed taskbar in windows nomenclature),
the
> > DynAPI window minimizes nicely but it leaves the plugin visible on the
> > screen.  This is a bit silly.  Maybe shouldn't be minimizable.
> >
> > 28) In Viewer Quicktime, in Mozilla 1.5 beta, when dragging the DynAPI
> > window after clicking the Quicktime Plugin's play button, the image
skips to
> > the (first or last, not sure, they're both the same) image even though
the
> > sound still plays through the other frames.  Maybe the window should not
be
> > draggable while a movie is playing, if there's any possible way to
detect
> > the play status.
> >
> > 29) In Viewer Quicktime, in Mozilla 1.5 beta, somehow by playing,
dragging,
> > and minimizing to titlebar, I managed to make the Quicktime Plugin go on
top
> > on the title bar, and now it's stuck half way up.  It moves when I move
the
> > titlebar.  Kind of comical.  :D  Have to see the screenshot to believe
it I
> > guess.
> >
http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/Viewe
> > r_QuickTime_bug.gif
> >
> > 30) In Viewer Quicktime, in all browsers, you can resize the DynAPI
window
> > so it's smaller than the Quicktime plugin, then you can't make it
bigger,
> > unless you Maximize, close, and reopen to exploit problem in 5) above,
OR if
> > you drag the DynAPI window off the browser, let go of the mouse button,
> > return the mouse over the browser and click.  Then the DynAPI window
appears
> > saying the Quicktime plugin is hidden.  You can then get one click
anywhere
> > on that DynAPI window, then the plugin appears.  But if you click on the
> > lower-right corner for resizing, you can make the DynAPI window bigger
> > again.  OR you can make it go hidden just by clicking anywhere else on
the
> > browser... so that's easier.  But maybe there should be a restriction on
how
> > small you can make a window, and never make it smaller than the plugin.
And
> > if the plugin is not scalable, don't allow resizing at all.
> >
> > 31) In Viewer Flash, in all browsers, same issue as 30).
> >
> > 32) In Viewer Image, in all browsers, suggested idea, underneath the
> > titlebar, where the menubar would be, there's no menu header items, so
is
> > there any option to disable menubars?  Likewise with the bottom, where
there
> > is a long narrow reectangular area across the bottom, caused by the
offset
> > of the <-> arrows in the lower-right hand corner, this user interface
> > realestate is being unused.  Perharps this realestate can be reclaimed
by
> > folding in the <-> when considering 22) above.  Or perhaps more useful
info
> > about the image could be displayed in the bottom, call it a "status
bar",
> > with original image dimensions, current dimensions, and ratio in either
(or
> > both, having an option to change it) ratio or percentage.  Have the
status
> > bar be dockable, with options accessible by the menu bar header item
> > "View" -> status bar.
> >
> > 33) In Viewer Image, in all browsers, perhaps have an option to scale X
and
> > Y independently (maybe beyond the scope of what we want to do, but just
an
> > idea), and have independent X/Y ratio and percentage in the status bar.
> >
> > 34) In Viewer Image, in all browsers, suggested idea, [got distracted,
> > sidetracked, tired, braindead, forgot] ... oh, have a popup dialog if
you
> > want to resize the image or something, with units in pixels, width and
> > height, and constrain proportions checkbox, etc., and other options like
> > that.

No comments 26-34?

> > 35) In Snake, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1, Game
Control ->
> > Help and Help button don't work.  Arrow keys don't work.  Not sure what
to
> > do to play the game.  Related JavaScript Console error:
> >
> > ScrollPane not found in file /ios/dynapi/src/lib/snake/snake.js at line
88
> > column 5:
> >
> > this.sp = new ScrollPane(dynapi.librarypath+"/snake/files/help.html")
> >
> > 36) In Snake, in Internet Explorer 6, Game Control -> Help does not
work.
> > Help button acts as the same as Start button.
>
> I will have to look at this on a real window machine not VPC

Ok.

> > 37) In Tetris, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, 'h'
doesn't
> > work for help.  No Javascript Console errors.  Seems no key input works
> > (unless I missed something).
>
> Hmmm again have to look on a real Windows machine

Ok.

> Leif Thanks for your input very helpful, thanks a million. Really :)
> A little sad that you think it's unusable (but if it is because image
cache,
> this will be fixed)

Ah, hope I cleared this up earlier, but it IS usable in Mozilla 1.5 beta and
Mozilla Firebird 0.6.1 (except for the Mozilla family specific input event
bug), and it was only unusable in IE 6 with the image caching issue while
checking on every visit to the page.

> IOS was written on a 300hz Macintosh powerbook and all of the examples are
> work perfectly fine and fast. (on mozilla, it does not matter what api you
> use or if you hard code on IE5, it does not handle complex dhtml very
> well... And this will NEVER change since Microsoft has discontinued the
> browser)
>
> I know that IOS and DynEditor can work perfect on Windows too, I just have
> to get my hands on one of those machines

Wish I could help out.  If you lived a little closer I'd let you borrow one.
;-)  If I had a faster connection I'd let you VNC into one.

> Now I going to crawl under my house and install a new antenna system. I
just
> installed a brand new (read HUGE THX 3 preamps and 4 tvs) Hometheater and
my
> girlfriend finally got that tv in our bathroom.

BATHROOM?!?!  Wow...

Leif

> Life is sweet
> Michael
>
>
> >
> > ----- Original Message -----
> > From: Michael Bystrom
> > To: dyn...@li...
> > Sent: Monday, September 08, 2003 9:48 AM
> > Subject: [Dynapi-Dev] Hello List
> >
> >
> > Hi there dynapi folks
> >
> > I just signed on and wanted to let you guys know that I've been playing
> > around with dynapi for a while now and the result is IOS (internet
operating
> > system)
> >
> > IOS is a virtual OS. It creates a virtual desktop in your browser
window.
> > You can drag, drop, move, open, close, type and more
> >
> > I'm using a older version 2.55 ( I now see that you have a version 3 :)
> > nice )  that has been modified for the Macintosh platform, the dynapi is
NOT
> > Mac friendly.
> >
> > I only using the dynapi for object creation and events
> >
> > I've written a written a bunch of new widgets that works fine on the
> > Macintosh and windows for that matter.... :)
> >
> > I've just released the first version and would like you guys to help out
> > with some debugging, code suggestions, new widgets etc...
> >
> > I got some cool ideas for IOS in the future and would like to see it
grow.
> >
> > Go to http://www.michaelbystrom.com download and play
> >
> > I could say a million more things but I'll save it for a another day.
> >
> > Nice day...
> > Michael
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>

[Dynapi-Dev] [ dynapi-Patches-799368 ] MSIE 6 WinXP: Error raised importing dynapi.api.MouseEvent

[SourceForge.net <no...@so...>]

Patches item #799368, was opened at 2003-09-02 20:14
Message generated for change (Comment added) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305757&aid=799368&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Romianowski (antarapero)
Assigned to: Nobody/Anonymous (nobody)
Summary: MSIE 6 WinXP: Error raised importing dynapi.api.MouseEvent

Initial Comment:
Hi,



if I import dynapi.api.MouseEvent I get some strange

error messages saying that a variable is undefined. I

tracked

it down to mouse_ie.js. I changed Line 70ff like this:



if (e.type=="mouseout" || e.type=="mouseover") {

	if (r && src && (r==src||src.isParentOf(r))) return;

//fix for #15 (ie only)

	if (r && src && (r == src.parent ||

r.isChildOf(src.parent)) ) me.bubble=false;

}



The only difference to the original source is that src

is checked for "undefined", too. That did the trick for me.



The error was hardly reproducable, only one page I did

had this error (after whirling the mousepointer around

the screen ;)



BTW: DynAPI 3 is a huge step ahead! Great, great work!



----------------------------------------------------------------------

>Comment By: Raymond Irving (xwisdom)
Date: 2003-09-14 14:36

Message:
Logged In: YES 
user_id=696242

Thanks Peter,



This patch is now inside CVS



Keep up the good work.



----------------------------------------------------------------------

Comment By: Peter Romianowski (antarapero)
Date: 2003-09-12 16:29

Message:
Logged In: YES 
user_id=346105

Hi Raymond,



no, just tested it with IE6 on WinXP. If you are asking

because of incompatibility issues that may arise applying

this patch - I don't think there are any. Really the only

thing I did is adding another check to assure that src is

not undefined. Otherwise it raises a "Object undefined has

no"-blablabla thing ;)



Regards

Peter Romianowski

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-09-05 16:16

Message:
Logged In: YES 
user_id=696242

Hi,



Have you tested this with IE 4, 5 and 6?



--

Raymond Irving

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305757&aid=799368&group_id=5757

RE: [Dynapi-Dev] Standardizing on the basic wigdet set

[Raymond I. <xw...@ya...>]

Thanks Daniel,

Does anyone else have any other feedback?


--
Raymond Irving

--- Daniel Tiru <de...@ti...> wrote:
> Hi Raymond!
> 
> For me it dont really matter, but we need some kind
> of blueprint, and
> aswell some kind of documentation on "how to build
> widgets", regarding
> the 
> StyleManager's features, i think its good, however i
> have not looked
> into that one yet.
> 
> Best Regards
> Daniel
> 
> 
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...] On
> Behalf Of Raymond
> Irving
> Sent: den 11 september 2003 01:36
> To: DynAPI-Dev
> Subject: [Dynapi-Dev] Standardizing on the basic
> wigdet set
> 
> 
> Hi Everyone,
> 
> I think we need to standardize on a basic widget
> format. Should we stick to the old method, use a new
> 
> theme-able or skin-able method or use StyleManager's
> approach?
> 
> Need some feedback
> 
> 
> --
> Raymond Irving
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> http://sitebuilder.yahoo.com
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../
> 
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] WYSIWYG editor for the DynAPI

[Raymond I. <xw...@ya...>]

--- Michael Bystrom <mi...@mi...>
wrote:
> > 3) Have us create a CVS module (similat to the
> logo
> > module/directory) on the DynAPI Project for the
> > source?
> ......
> .......
> 
> #3 I want this to evolve, I will always keep a
> "stabile" version on my site
> so we can point to that. I want this will be it's
> home. But for the
> development I agree with you, let everybody mess
> with it. :)
> 
> I've never had to use a CVS dunno how it works! so
> can you set it up? Or..
> I guess I have to learn now :)

Well I can create a module (directory) on CVS for the
editor so you just check it out the same way you would
with dynapi3x. Is everyone in a greement with this?

Another thing I think we should first do is to convert
the editor to work with 3.0 

Btw can we call it Visual DynAPI Editor (VDE) as the
"visual" tells the user exactly what it does?

> Raymond! Are you the admin if so, how many
> subscriber do we have to this
> list, 

Yes. I'm one of the developers the DynAPI project 
with administrator priviledges.

Can't say for sure how many subscribers we have. But I
do know that a lot of users are subscribed to the
list. Some are only watching and waiting to see what
will become of 3.0

You can look at the polls on the dynapi website
dynapi.sf.net to see users feedback. For more
publicity I would suggest you post a news article on
the DynAPI website.

> I have a surprisingly low download count.
> IOS: 11
> Dyneditor: 19
>
> How many are developing for the api
>
> Where are you guys located!

We are all developers who are located all over the
world. The DynAPI project is hosted on SourceForge wih
I think is located in the US.

--
Raymond Irving

 
> I just moved back from Los Angels after 12 years to
> Sweden.
> 
> Michael
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] WYSIWYG editor for the DynAPI

[Michael B. <mi...@mi...>]

Raymond,

>> Well first of I would like the DynAPI Community to
>> help with it,

> Great! Do you plan on:
> 
> 1) Keeping the source on your website? Or
> 2) Starting a new SourceForge Project or similar? Or
> 3) Have us create a CVS module (similat to the logo
> module/directory) on the DynAPI Project for the
> source?

> I prefer #3 as dynapi developers will not have to join
> Yet-Another-Project to help out with the development
> of the editor. Would could all decide what we want to
> do right here. Changes made to the DynAPI can be
> easily reflected inside the editor.


#3 I want this to evolve, I will always keep a "stabile" version on my site
so we can point to that. I want this will be it's home. But for the
development I agree with you, let everybody mess with it. :)

I've never had to use a CVS dunno how it works! so can you set it up? Or..
I guess I have to learn now :)

Raymond! Are you the admin if so, how many subscriber do we have to this
list, I have a surprisingly low download count.
IOS: 11
Dyneditor: 19

How many are developing for the api

Where are you guys located!

I just moved back from Los Angels after 12 years to Sweden.

Michael





>>>> I decided to release the DynEditor.
>>>> The DynEditor is a WYSIWYG editor for the DynAPI
>>>> library.
>>>> 
>>>> For more info go http://www.michaelbystrom.com
>>>> 
>>>> Please let me know what you think
>>>> 
>>>> Enjoy
>>>> Michael

[Dynapi-Dev] CVS Update

[Leif W <war...@us...>]

[+] cross frame access demo update, added textarea to set custom HTML

Leif

[Dynapi-Dev] [ dynapi-Patches-799368 ] MSIE 6 WinXP: Error raised importing dynapi.api.MouseEvent

[SourceForge.net <no...@so...>]

Patches item #799368, was opened at 2003-09-02 20:14
Message generated for change (Comment added) made by antarapero
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305757&aid=799368&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Romianowski (antarapero)
Assigned to: Nobody/Anonymous (nobody)
Summary: MSIE 6 WinXP: Error raised importing dynapi.api.MouseEvent

Initial Comment:
Hi,



if I import dynapi.api.MouseEvent I get some strange

error messages saying that a variable is undefined. I

tracked

it down to mouse_ie.js. I changed Line 70ff like this:



if (e.type=="mouseout" || e.type=="mouseover") {

	if (r && src && (r==src||src.isParentOf(r))) return;

//fix for #15 (ie only)

	if (r && src && (r == src.parent ||

r.isChildOf(src.parent)) ) me.bubble=false;

}



The only difference to the original source is that src

is checked for "undefined", too. That did the trick for me.



The error was hardly reproducable, only one page I did

had this error (after whirling the mousepointer around

the screen ;)



BTW: DynAPI 3 is a huge step ahead! Great, great work!



----------------------------------------------------------------------

>Comment By: Peter Romianowski (antarapero)
Date: 2003-09-12 16:29

Message:
Logged In: YES 
user_id=346105

Hi Raymond,



no, just tested it with IE6 on WinXP. If you are asking

because of incompatibility issues that may arise applying

this patch - I don't think there are any. Really the only

thing I did is adding another check to assure that src is

not undefined. Otherwise it raises a "Object undefined has

no"-blablabla thing ;)



Regards

Peter Romianowski

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-09-05 16:16

Message:
Logged In: YES 
user_id=696242

Hi,



Have you tested this with IE 4, 5 and 6?



--

Raymond Irving

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305757&aid=799368&group_id=5757

Re: [Dynapi-Dev] Hello List

[Michael B. <mi...@mi...>]

Den 03-09-11 05.37, skrev "Leif W" <war...@us...>:

> Hello List
> Here's my long-awaited QA review of all the "demo" pages.  Again,
> I wouldn't have spent about 12 hours today doing this if I didn't think it
> was worthwhile for the IOS and the DynAPI in general.  So keep that in mind
> as you get all these critiques.  I don't think I missed anything.  ;-)  One
> thing, since I am often saying "in all browsers", it's a good sign, because
> even if there's a problem, at least it's consistent behaviour in all the
> browsers.
> 
> Without further ado, my QA review, analysis, and report.

Man o Man you have been busy I hope I didn't make you stay up all night

:) 

Nice work
Now let me run through the list with you
 
> 1) There's no BGCOLOR setting the background to white, so in my browser
> where the default background isn't white, the pages look a bit odd.  ;-)

fixed

> 2) On the first page, the content is centered in IE 6 only, and is not
> centered in the other 3 browsers.

Hmm ?? It should not be centered align:left

> 3) When looking into the above issue, there's a <div> tag before the <body>
> tag.

Yeah I publish the whole site in MT type and missed one of the modules :)
Fixed.

> 4) In the HTML Document demo, in IE 6, when dragging the "txt1.html" icon,
> the image disappears, then IE starts transferring data, gets the image, then
> displays it.  I seem to remember some recent discussion about this issue
> (how to cache images in IE using the DynAPI).  The whole experience in IE is
> affected by this.  Every time anything changes, all images are either
> reloaded or compared to the server, and it's slow.

Is this for ALL the image swapping?
I use this.icon.setBgImage()
If this is the case we/I  have to re-think the use of setBgImage and use
This.icon.setHTM("<img src=''>")
I know I did this with a client once and I changed the thumb in the
scrollpane to use set.HTML()

> * Note: when looking at
> the more complex things, the entire demo is so slow I'd call it unusable or
> unacceptable in a real-world setting.

IOS is very complex I give you that, and I think that broadband is a
necessity. But to call it unusable is harsh.

I've let people play with it a my local library Win IE6 (where the have a
nice set up for the school kids, broadband) and I works perfectly fine, and
I've also set it up at local networks where I think it works best. I also
tested in some other ways.

But I would agree that IOS NEEDs a fast computer there is a lot of computing
that is going on. 

On a personal note:
I really done my best to speed things up ex. The "list.js" script is one
example where I use id's to identify the nodes so that if we have huge
tree's it will only change collapse the selected nodes. Just a simple setup
is faster then using the browsers style "display" feature.

> 5) In the HTML Document demo, in Mozilla 1.5 beta, IE 6, and Mozilla
> Firebird 0.6.1, after "maximizing" the txt1.html window, and then closing it
> (upper-left corner diagonal arrow), further opening is no longer the
> original size but nearly the maximized size.  Size isn't reset on close?
> Could be a good feature.  But maybe should have a "maximize" flag/size, and
> if it's closed while maximized, also save the unmaximized size, and reopen
> in the maximized state, but allow it to be unmaximized to the previous size.
 
Cool I missed that one noted will be fixed

> 6) HTML Document demo does not work in Opera 7.11 browser.  Now I think I
> remember Opera 7 support was added in DynAPI 3, so I won't test Opera 7.11
> anymore.  Further references to "all browsers" means all except Opera 7.11.

Yes! I'd guess that it wouldn't
I will not update 2.55 to support Opera

> 7) In the HTML Document demo, in all browsers: After maximizing the HTML
> Document, scrollbars extend beyond the screen, when they probably should
> not.  After minimizing, the scrollbars still remain, as if there's still
> content going past the browser's viewable area.

Yes I aware of this.
If drag a simple dynlayer is out side the browser window the scrollbars are
activated then Check the "demo.dragdrop-collision.html" in the DynAPI 3x

I don't know how to fix this.

> * Note, in Folders in Symbol  Mode, I noticed if I expand a folder
> window beyond the endge of the
> browser's viewable area, scrollbars appear in the browser, and the mouse
> becomes "detached" from the window resize (letting up the mouse button while
> outside the browser window doesn't cancel the resizing, so moving the
> mouuuse back over the window causes the resizing to continue until the mouse
> is clicked and released).

This is how the events work.
The DynEvents are "put on hold" if you leave the browsers viewable area.
It's the same if you move a folder outside, release the mouse, move back to
the window the folder will follow the mouse.

This is also true for the dynapi 3.0 check "demo.dragdrop-collision.html"

I sure that there is a way to cancel the events and reset the IOS but I will
not spend time on this.

> When I shrink the folder window again, the
> browser's scrollbars go away.

Yes on IE5 Macintosh
Not on Macintosh Mozilla

> This is the behaviour I'd expect with the
> HTML Document maximize/minimize/close.

Yes I would like that to :)

> HTML Document resizing works as
> expected, with browser scrollbars appearing and disappearing as needed.

:)

> 8) In Folder in Symbol Mode, in all browsers, there's no "taskbar" so it's
> difficult to get to windows that lie underneath other windows, unless moving
> or minimizing all windows above the target window.  This quickly becomes
> cumbersome.

Are you talking about Windows like taskbar??
I have no plans to add such a feature, but I think it's a good Idea and will
put it on the board.

> 9) In Folder in Symbol Mode (and probably anything with a DynAPI window with
> scrollbars), can't scroll with the mousewheel.  It scrolls the entire
> browser window, not the DynAPI window.

I have no plans to include such a feature it.


> 10) In Folder in List Mode, in all browsers, a user interface suggestion, is
> to put the files and folders on the right, (M$ Explorer style), and only
> Folder tree on the left side.  Since I'm very familiar with windows
> explorer, and it's one of the good things about M$ Windoze, I'd find the
> Folder in List Mode much easier to use if it was set up this way,

Are you talking about the Microsoft's explorer window? Yes that could be
fun. But There would involve a SHIT load of layers to be created. But I
would look nice...

Hmm maybe

IOS design was inspired by the Macintosh OS and I was careful to weigh the
design with regards to memory. This is a fine line to walk here.

> with
> option to choose view type (icons and filename text only, or with columns
> with file info (size, last modified, or whatever JavaScript has access to,
> which I understand it may not have much access), and sortable by clicking on
> the column header.

It is alphabetically sort able now


> Also the grid lines are somewhat distracting.  Maybe an
> option to turn them on or off.

I added this request to the board

> And what about in column view mode,

As for columns! The first version had columns sort able, BUT due to much
pressure on the poor browser I removed this feature. I have have made some
holes in the code so I might restate this feature but I think this have to
use a simple CSS set up. But this is not something I will add soon.

> vertical grids as well?

Not in the foreseeable future



> 11) In all demos, in all browsers, double clicking on the text label of
> something selects the text in addition to the expected behaviour or opening
> the file, folder, or starting the app.

Yes I know this I know of no way a fix this.

> 12) In Calendar, in all browsers, has "this is not ready".  Would be nice to
> enter some data here.

That because it's not ready yet


> 13) In ColorRGB, all browsers.  Browser's scrollbars show that there's more
> content on the page, but there's no visible elements and there should be no
> scrollbars expected.

I don't understand what you mean



> 14) In ColorRGB, in all browsers.  Can't type numbers into the hex value or
> R, G or B fields.

Yes I will add text areas to all colorpickers later.


> 15) In ColorRGB, in Mozilla Firebird 0.6.1, after trying to type into the
> text fields, can't type CTRL-W to close the window.  Somehow the key events
> are being captured and ignored?

Mozilla has problems with it's key events overall. I sometimes loose the
copy, new window, and close
 
> 16) In ColorPicker, in all browsers, the slidebar labels aren't in English,
> so I don't know what they do.  :-)  Maybe a "language" option should be
> considered for GUIs -- internationalization, localization, globalization,
> locales, whatever buzzword fits best? -- so the user can choose the desired
> language.

:) That is Swedish hehe
There will not be a "language" option in the foreseeable future
But I will change that :)


> 17) In ColorPicker (and possibly others, just noticed now), in Mozilla 1.5
> beta.  There's a message in the JavaScript console after page load, before
> anything user input:
> Warning: The stylesheet http://cyclone.he.net/cgi-bin/error404 was loaded as
> CSS even though its MIME type, "text/html", is not "text/css".

This I don't get.
I have only one stylesheet and is loaded correct.
Hmm we just moved and upgraded all server software apache, perl, php, mysql
etc.. I know there are some problems with the referrals.


> 18) In ColorPicker, in all browsers.  The new color is not remembered after
> clicking "ok".  When opening the ColorPicker by double clicking, the old and
> new colors are both cyan (pale blue).

I've add this feature to the board.


> 19) In ColorPicker (and probably any other draggable DynAPI window), I can
> drag the window to the bottom of the screen, a scrollbar appear, drag it
> back up, disappears.  Same with the right side.  But not when dragging to
> the left or top of the browser.  This can make it hard to grab a window if
> you've shoved it too far to the top or left.  There's no way to scroll in
> those directions.

See 7


> There's maybe three options that would be good.  First option is the
> default, as it is now.  Second and third, have boundaries where you can
> specify the top-right-bottom-left 'softness' or 'hardness', to either be
> soft or hard, hard being like a brick wall, and not allowing the dragged
> window to go beyond visible space, or soft being like mush, allowing a
> DynAPI window to be dragged anywhere, and automatically resize the viewable
> area in the browser and scroll the viewable area to where the dragged dynapi
> window will end up.  (Not sure if this is possible or the complexity, but
> from a GUI standpoint it would be more consistent with the behaviour
> observed in the other two browser borders).

I thought of doing that locking the window, but I like the ide you have with
resizeing it when you reach the borders...

I put it on the board.


> Maybe a fourth option, is to have something like an taskbar (autohide
> option, always on top option), that is a dock, and have DynAPI windows be
> dockable and get minimized to icons with (optional text labels).

Don't think so I might consider a taskbar see 8)


> 20) In ColorPicker, in all browsers, clicking in the color plane area
> (largest square with continuous color variations) does not move the circular
> color selector until the click is released.  This prohibits the user from
> clicking anywhere and starting to drag immediately and see the colors he's
> currently dragging over.  The user must click the circle first.  It would be
> more user friendly to have the circle snap into place underneath the click,
> so dragging can continue seamlessly.

Yes I know, I don't remember why I did it that way. I'm using DynAPI's
DragEvents for the drag and I would have to rewrite the code if the maker to
fallow the mouse after a click but I put on the list.

But I changed the marker to respond to onmousedown.



> 21) In Texter App Mode (and all other dragable / resiable elements), in all
> browsers.    All four size should allow resizing of the window in the
> specified direction only.  All 4 corners should allow simultaneous resizing
> in both directions specified.  Currently only the lower-right is resizable.
> 22) In Texter App Mode (and all other dragable / resiable elements), in all
> browsers.      There needs to be an indication when the mouse is over a
> button, or a draggable area.  Maybe change to a reverse highlight for menu
> buttons, or like any apps in Windows, a little box with shading appears
> around the items in the menu bar.  In windows when moving the mouse over a
> resizable element, the mouse pointer changes to some arrows.  While this may
> not be easy to do in all browsers, you can change the thing underneath the
> mouse i.e. make the left border change highlighted colors when mouse over,
> etc..  Also, having "resizable" or "draggable" hotspots look "grippy"
> somehow, instead of all the same grey, might be an option, or might not.
> 
> 23) In Texter App Mode, in Mozilla 1.5 beta, get this silent JavaScript
> error in the console when mousing over the text area.  Thinking it's due to
> the Mozilla race condition bug or something.
> 
> Error: [Exception... "'Permission denied to get property
> HTMLDivElement.parentNode' when calling method:
> [nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001e
> (NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]
> 
> 24) In Texter App Mode, in Mozilla Firebird 0.6.1, can not type any text.
> Have this error in the JavaScript Console:
> 
> Error: [Exception... "'Permission denied to get property
> HTMLDivElement.parentNode' when calling method:
> [nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001e
> (NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]
> 
> Exact same error as 23, but Mozilla 1.5 beta works, oddly enough.  NOTE,
> this may be an instance that correlates with my earlier inability to type
> CTRL-W to close the window in Mozilla Firebird 0.6.1.  I am unable to type
> CTRL-W now.  I maybe didn't notice the JavaScript error then as I wasn't
> looking.  ;-)  This is probably how to reproduce that condition, by
> triggering the known race condition bug.
> 
> 25) In Texter Document Mode, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1.
> Same error as reported in 23) and 24).  The only difference, in Mozilla 1.5
> beta, the error is seen once on mouse over the text area, and once on mouse
> out.  In Mozilla Firebird 0.6.1, the error is seen three times on mouse
> over, three times on mouse out.  Mozilla 1.5 beta allows text typing, and
> Mozilla 0.6.1 does not, same as in errors 23) and 24) above.  However!  I
> /WAS/ able to use CTRL-W to close Mozilla Firebird 0.6.1 (this time).
> Further inspection, sometimes Mozilla Firebird 0.6.1 throws one or three of
> the mentioned errors.  Odd...

23,24,25) Yes! I can not fix this.


Regarding Viewer Class
The viewer is in development and will be rewritten
All you suggestions are noted.


> 26) In Viewer Quicktime, in all browsers, when resizing the DynAPI window
> container thing, the Quicktime plugin does not reesize.  Maybe no need to
> have the DynAPI window resizable if the underlying plugin isn't capable.
> 27) In Viewer Quicktime, in all browsers, when using the "minimize to
> titlebar" (I know it's a MAC thing, there's no windows equivalent, and it's
> NOT the same thing as a windows minimize, so that's why I call it minimize
> to titlebar, as opposed to the assumed taskbar in windows nomenclature), the
> DynAPI window minimizes nicely but it leaves the plugin visible on the
> screen.  This is a bit silly.  Maybe shouldn't be minimizable.
> 
> 28) In Viewer Quicktime, in Mozilla 1.5 beta, when dragging the DynAPI
> window after clicking the Quicktime Plugin's play button, the image skips to
> the (first or last, not sure, they're both the same) image even though the
> sound still plays through the other frames.  Maybe the window should not be
> draggable while a movie is playing, if there's any possible way to detect
> the play status.
> 
> 29) In Viewer Quicktime, in Mozilla 1.5 beta, somehow by playing, dragging,
> and minimizing to titlebar, I managed to make the Quicktime Plugin go on top
> on the title bar, and now it's stuck half way up.  It moves when I move the
> titlebar.  Kind of comical.  :D  Have to see the screenshot to believe it I
> guess.
> http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/Viewe
> r_QuickTime_bug.gif
> 
> 30) In Viewer Quicktime, in all browsers, you can resize the DynAPI window
> so it's smaller than the Quicktime plugin, then you can't make it bigger,
> unless you Maximize, close, and reopen to exploit problem in 5) above, OR if
> you drag the DynAPI window off the browser, let go of the mouse button,
> return the mouse over the browser and click.  Then the DynAPI window appears
> saying the Quicktime plugin is hidden.  You can then get one click anywhere
> on that DynAPI window, then the plugin appears.  But if you click on the
> lower-right corner for resizing, you can make the DynAPI window bigger
> again.  OR you can make it go hidden just by clicking anywhere else on the
> browser... so that's easier.  But maybe there should be a restriction on how
> small you can make a window, and never make it smaller than the plugin.  And
> if the plugin is not scalable, don't allow resizing at all.
> 
> 31) In Viewer Flash, in all browsers, same issue as 30).
> 
> 32) In Viewer Image, in all browsers, suggested idea, underneath the
> titlebar, where the menubar would be, there's no menu header items, so is
> there any option to disable menubars?  Likewise with the bottom, where there
> is a long narrow reectangular area across the bottom, caused by the offset
> of the <-> arrows in the lower-right hand corner, this user interface
> realestate is being unused.  Perharps this realestate can be reclaimed by
> folding in the <-> when considering 22) above.  Or perhaps more useful info
> about the image could be displayed in the bottom, call it a "status bar",
> with original image dimensions, current dimensions, and ratio in either (or
> both, having an option to change it) ratio or percentage.  Have the status
> bar be dockable, with options accessible by the menu bar header item
> "View" -> status bar.
> 
> 33) In Viewer Image, in all browsers, perhaps have an option to scale X and
> Y independently (maybe beyond the scope of what we want to do, but just an
> idea), and have independent X/Y ratio and percentage in the status bar.
> 
> 34) In Viewer Image, in all browsers, suggested idea, [got distracted,
> sidetracked, tired, braindead, forgot] ... oh, have a popup dialog if you
> want to resize the image or something, with units in pixels, width and
> height, and constrain proportions checkbox, etc., and other options like
> that.










> 35) In Snake, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1, Game Control ->
> Help and Help button don't work.  Arrow keys don't work.  Not sure what to
> do to play the game.  Related JavaScript Console error:
> 
> ScrollPane not found in file /ios/dynapi/src/lib/snake/snake.js at line 88
> column 5:
> 
> this.sp = new ScrollPane(dynapi.librarypath+"/snake/files/help.html")
> 
> 36) In Snake, in Internet Explorer 6, Game Control -> Help does not work.
> Help button acts as the same as Start button.

I will have to look at this on a real window machine not VPC



> 37) In Tetris, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, 'h' doesn't
> work for help.  No Javascript Console errors.  Seems no key input works
> (unless I missed something).

Hmmm again have to look on a real Windows machine


> 38) In Tetris, in Internet Explorer 6, h alerts the help as expected.
> However, game requires 100(!) images or so to be reloaded every time
> something changes position on the DynAPI window.  The demo is unusable.
> Images are tricky to be cached in IE6.  See 4) above.

I forgot to preload the images this will be fixed


> 39) In Tetris, in all browsers, feature suggestion.  Add "help" to the "menu
> bar" as a "meanu header item".  Help -> Keys (for instance).

Yes noted I wanted to add this but was tooooo lazy added to the board

> 40) In Everything, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, in the
> Javascript Console, syntax error due to 404 file not found document where
> JavaScript code expected.
> 
> File not found: /ios/dynapi/src/lib/bystrom/util/marker.js

Yes this file has been removed will be added to dyneditor.
I will check the html files and remove


> 41) In Everything, in Internet Explorer 6, same issue as 4).  App is
> unusable as it's too slow.  The image caching is vital.
Read 4)


> 42) In Everything, in all browsers, feature suggestion.  Something like the
> windows "Arrange Icons", to automatically position all icons, i.e.
> alphabetically on the IOS desktop, from left top to bottom, right bottom to
> top, right right to left, etc..

Yes Good Ide will put on board.


Leif Thanks for your input very helpful, thanks a million. Really :)
A little sad that you think it's unusable (but if it is because image cache,
this will be fixed)

IOS was written on a 300hz Macintosh powerbook and all of the examples are
work perfectly fine and fast. (on mozilla, it does not matter what api you
use or if you hard code on IE5, it does not handle complex dhtml very
well... And this will NEVER change since Microsoft has discontinued the
browser) 

I know that IOS and DynEditor can work perfect on Windows too, I just have
to get my hands on one of those machines

Now I going to crawl under my house and install a new antenna system. I just
installed a brand new (read HUGE THX 3 preamps and 4 tvs) Hometheater and my
girlfriend finally got that tv in our bathroom.

Life is sweet
Michael


> 
> ----- Original Message -----
> From: Michael Bystrom
> To: dyn...@li...
> Sent: Monday, September 08, 2003 9:48 AM
> Subject: [Dynapi-Dev] Hello List
> 
> 
> Hi there dynapi folks
> 
> I just signed on and wanted to let you guys know that I've been playing
> around with dynapi for a while now and the result is IOS (internet operating
> system)
> 
> IOS is a virtual OS. It creates a virtual desktop in your browser window.
> You can drag, drop, move, open, close, type and more
> 
> I'm using a older version 2.55 ( I now see that you have a version 3 :)
> nice )  that has been modified for the Macintosh platform, the dynapi is NOT
> Mac friendly.
> 
> I only using the dynapi for object creation and events
> 
> I've written a written a bunch of new widgets that works fine on the
> Macintosh and windows for that matter.... :)
> 
> I've just released the first version and would like you guys to help out
> with some debugging, code suggestions, new widgets etc...
> 
> I got some cool ideas for IOS in the future and would like to see it grow.
> 
> Go to http://www.michaelbystrom.com download and play
> 
> I could say a million more things but I'll save it for a another day.
> 
> Nice day...
> Michael

Re: [Dynapi-Dev] Hello List

[Leif W <war...@us...>]

Forgot one thing,

42) In Everything, in all browsers, feature suggestion.  Something like the
windows "Arrange Icons", to automatically position all icons, i.e.
alphabetically on the IOS desktop, from left top to bottom, right bottom to
top, right right to left, etc..

Leif

----- Original Message ----- 
From: "Leif W" <war...@us...>
To: <dyn...@li...>
Sent: Wednesday, September 10, 2003 11:37 PM
Subject: Re: [Dynapi-Dev] Hello List


> Hello ListHere's my long-awaited QA review of all the "demo" pages.
Again,
> I wouldn't have spent about 12 hours today doing this if I didn't think it
> was worthwhile for the IOS and the DynAPI in general.  So keep that in
mind
> as you get all these critiques.  I don't think I missed anything.  ;-)
One
> thing, since I am often saying "in all browsers", it's a good sign,
because
> even if there's a problem, at least it's consistent behaviour in all the
> browsers.
>
> Without further ado, my QA review, analysis, and report.
>
> 1) There's no BGCOLOR setting the background to white, so in my browser
> where the default background isn't white, the pages look a bit odd.  ;-)
>
> 2) On the first page, the content is centered in IE 6 only, and is not
> centered in the other 3 browsers.
>
> 3) When looking into the above issue, there's a <div> tag before the
<body>
> tag.
>
> 4) In the HTML Document demo, in IE 6, when dragging the "txt1.html" icon,
> the image disappears, then IE starts transferring data, gets the image,
then
> displays it.  I seem to remember some recent discussion about this issue
> (how to cache images in IE using the DynAPI).  The whole experience in IE
is
> affected by this.  Every time anything changes, all images are either
> reloaded or compared to the server, and it's slow. * Note: when looking at
> the more complex things, the entire demo is so slow I'd call it unusable
or
> unacceptable in a real-world setting.
>
> 5) In the HTML Document demo, in Mozilla 1.5 beta, IE 6, and Mozilla
> Firebird 0.6.1, after "maximizing" the txt1.html window, and then closing
it
> (upper-left corner diagonal arrow), further opening is no longer the
> original size but nearly the maximized size.  Size isn't reset on close?
> Could be a good feature.  But maybe should have a "maximize" flag/size,
and
> if it's closed while maximized, also save the unmaximized size, and reopen
> in the maximized state, but allow it to be unmaximized to the previous
size.
>
> 6) HTML Document demo does not work in Opera 7.11 browser.  Now I think I
> remember Opera 7 support was added in DynAPI 3, so I won't test Opera 7.11
> anymore.  Further references to "all browsers" means all except Opera
7.11.
>
> 7) In the HTML Document demo, in all browsers: After maximizing the HTML
> Document, scrollbars extend beyond the screen, when they probably should
> not.  After minimizing, the scrollbars still remain, as if there's still
> content going past the browser's viewable area. * Note, in Folders in
Symbol
> Mode, I noticed if I expand a folder window beyond the endge of the
> browser's viewable area, scrollbars appear in the browser, and the mouse
> becomes "detached" from the window resize (letting up the mouse button
while
> outside the browser window doesn't cancel the resizing, so moving the
> mouuuse back over the window causes the resizing to continue until the
mouse
> is clicked and released).  When I shrink the folder window again, the
> browser's scrollbars go away.  This is the behaviour I'd expect with the
> HTML Document maximize/minimize/close.  HTML Document resizing works as
> expected, with browser scrollbars appearing and disappearing as needed.
>
> 8) In Folder in Symbol Mode, in all browsers, there's no "taskbar" so it's
> difficult to get to windows that lie underneath other windows, unless
moving
> or minimizing all windows above the target window.  This quickly becomes
> cumbersome.
>
> 9) In Folder in Symbol Mode (and probably anything with a DynAPI window
with
> scrollbars), can't scroll with the mousewheel.  It scrolls the entire
> browser window, not the DynAPI window.
>
> 10) In Folder in List Mode, in all browsers, a user interface suggestion,
is
> to put the files and folders on the right, (M$ Explorer style), and only
> Folder tree on the left side.  Since I'm very familiar with windows
> explorer, and it's one of the good things about M$ Windoze, I'd find the
> Folder in List Mode much easier to use if it was set up this way, with
> option to choose view type (icons and filename text only, or with columns
> with file info (size, last modified, or whatever JavaScript has access to,
> which I understand it may not have much access), and sortable by clicking
on
> the column header.  Also the grid lines are somewhat distracting.  Maybe
an
> option to turn them on or off.  And what about in column view mode,
vertical
> grids as well?
>
> 11) In all demos, in all browsers, double clicking on the text label of
> something selects the text in addition to the expected behaviour or
opening
> the file, folder, or starting the app.
>
> 12) In Calendar, in all browsers, has "this is not ready".  Would be nice
to
> enter some data here.
>
> 13) In ColorRGB, all browsers.  Browser's scrollbars show that there's
more
> content on the page, but there's no visible elements and there should be
no
> scrollbars expected.
>
> 14) In ColorRGB, in all browsers.  Can't type numbers into the hex value
or
> R, G or B fields.
>
> 15) In ColorRGB, in Mozilla Firebird 0.6.1, after trying to type into the
> text fields, can't type CTRL-W to close the window.  Somehow the key
events
> are being captured and ignored?
>
> 16) In ColorPicker, in all browsers, the slidebar labels aren't in
English,
> so I don't know what they do.  :-)  Maybe a "language" option should be
> considered for GUIs -- internationalization, localization, globalization,
> locales, whatever buzzword fits best? -- so the user can choose the
desired
> language.
>
> 17) In ColorPicker (and possibly others, just noticed now), in Mozilla 1.5
> beta.  There's a message in the JavaScript console after page load, before
> anything user input:
>
> Warning: The stylesheet http://cyclone.he.net/cgi-bin/error404 was loaded
as
> CSS even though its MIME type, "text/html", is not "text/css".
>
> 18) In ColorPicker, in all browsers.  The new color is not remembered
after
> clicking "ok".  When opening the ColorPicker by double clicking, the old
and
> new colors are both cyan (pale blue).
>
> 19) In ColorPicker (and probably any other draggable DynAPI window), I can
> drag the window to the bottom of the screen, a scrollbar appear, drag it
> back up, disappears.  Same with the right side.  But not when dragging to
> the left or top of the browser.  This can make it hard to grab a window if
> you've shoved it too far to the top or left.  There's no way to scroll in
> those directions.
>
> There's maybe three options that would be good.  First option is the
> default, as it is now.  Second and third, have boundaries where you can
> specify the top-right-bottom-left 'softness' or 'hardness', to either be
> soft or hard, hard being like a brick wall, and not allowing the dragged
> window to go beyond visible space, or soft being like mush, allowing a
> DynAPI window to be dragged anywhere, and automatically resize the
viewable
> area in the browser and scroll the viewable area to where the dragged
dynapi
> window will end up.  (Not sure if this is possible or the complexity, but
> from a GUI standpoint it would be more consistent with the behaviour
> observed in the other two browser borders).
>
> Maybe a fourth option, is to have something like an taskbar (autohide
> option, always on top option), that is a dock, and have DynAPI windows be
> dockable and get minimized to icons with (optional text labels).
>
> 20) In ColorPicker, in all browsers, clicking in the color plane area
> (largest square with continuous color variations) does not move the
circular
> color selector until the click is released.  This prohibits the user from
> clicking anywhere and starting to drag immediately and see the colors he's
> currently dragging over.  The user must click the circle first.  It would
be
> more user friendly to have the circle snap into place underneath the
click,
> so dragging can continue seamlessly.
>
> 21) In Texter App Mode (and all other dragable / resiable elements), in
all
> browsers.    All four size should allow resizing of the window in the
> specified direction only.  All 4 corners should allow simultaneous
resizing
> in both directions specified.  Currently only the lower-right is
resizable.
>
> 22) In Texter App Mode (and all other dragable / resiable elements), in
all
> browsers.      There needs to be an indication when the mouse is over a
> button, or a draggable area.  Maybe change to a reverse highlight for menu
> buttons, or like any apps in Windows, a little box with shading appears
> around the items in the menu bar.  In windows when moving the mouse over a
> resizable element, the mouse pointer changes to some arrows.  While this
may
> not be easy to do in all browsers, you can change the thing underneath the
> mouse i.e. make the left border change highlighted colors when mouse over,
> etc..  Also, having "resizable" or "draggable" hotspots look "grippy"
> somehow, instead of all the same grey, might be an option, or might not.
>
> 23) In Texter App Mode, in Mozilla 1.5 beta, get this silent JavaScript
> error in the console when mousing over the text area.  Thinking it's due
to
> the Mozilla race condition bug or something.
>
> Error: [Exception... "'Permission denied to get property
> HTMLDivElement.parentNode' when calling method:
> [nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001e
> (NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]
>
> 24) In Texter App Mode, in Mozilla Firebird 0.6.1, can not type any text.
> Have this error in the JavaScript Console:
>
> Error: [Exception... "'Permission denied to get property
> HTMLDivElement.parentNode' when calling method:
> [nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001e
> (NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]
>
> Exact same error as 23, but Mozilla 1.5 beta works, oddly enough.  NOTE,
> this may be an instance that correlates with my earlier inability to type
> CTRL-W to close the window in Mozilla Firebird 0.6.1.  I am unable to type
> CTRL-W now.  I maybe didn't notice the JavaScript error then as I wasn't
> looking.  ;-)  This is probably how to reproduce that condition, by
> triggering the known race condition bug.
>
> 25) In Texter Document Mode, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1.
> Same error as reported in 23) and 24).  The only difference, in Mozilla
1.5
> beta, the error is seen once on mouse over the text area, and once on
mouse
> out.  In Mozilla Firebird 0.6.1, the error is seen three times on mouse
> over, three times on mouse out.  Mozilla 1.5 beta allows text typing, and
> Mozilla 0.6.1 does not, same as in errors 23) and 24) above.  However!  I
> /WAS/ able to use CTRL-W to close Mozilla Firebird 0.6.1 (this time).
> Further inspection, sometimes Mozilla Firebird 0.6.1 throws one or three
of
> the mentioned errors.  Odd...
>
> 26) In Viewer Quicktime, in all browsers, when resizing the DynAPI window
> container thing, the Quicktime plugin does not reesize.  Maybe no need to
> have the DynAPI window resizable if the underlying plugin isn't capable.
>
> 27) In Viewer Quicktime, in all browsers, when using the "minimize to
> titlebar" (I know it's a MAC thing, there's no windows equivalent, and
it's
> NOT the same thing as a windows minimize, so that's why I call it minimize
> to titlebar, as opposed to the assumed taskbar in windows nomenclature),
the
> DynAPI window minimizes nicely but it leaves the plugin visible on the
> screen.  This is a bit silly.  Maybe shouldn't be minimizable.
>
> 28) In Viewer Quicktime, in Mozilla 1.5 beta, when dragging the DynAPI
> window after clicking the Quicktime Plugin's play button, the image skips
to
> the (first or last, not sure, they're both the same) image even though the
> sound still plays through the other frames.  Maybe the window should not
be
> draggable while a movie is playing, if there's any possible way to detect
> the play status.
>
> 29) In Viewer Quicktime, in Mozilla 1.5 beta, somehow by playing,
dragging,
> and minimizing to titlebar, I managed to make the Quicktime Plugin go on
top
> on the title bar, and now it's stuck half way up.  It moves when I move
the
> titlebar.  Kind of comical.  :D  Have to see the screenshot to believe it
I
> guess.
>
http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/Viewer_QuickTime_bug.gif
>
> 30) In Viewer Quicktime, in all browsers, you can resize the DynAPI window
> so it's smaller than the Quicktime plugin, then you can't make it bigger,
> unless you Maximize, close, and reopen to exploit problem in 5) above, OR
if
> you drag the DynAPI window off the browser, let go of the mouse button,
> return the mouse over the browser and click.  Then the DynAPI window
appears
> saying the Quicktime plugin is hidden.  You can then get one click
anywhere
> on that DynAPI window, then the plugin appears.  But if you click on the
> lower-right corner for resizing, you can make the DynAPI window bigger
> again.  OR you can make it go hidden just by clicking anywhere else on the
> browser... so that's easier.  But maybe there should be a restriction on
how
> small you can make a window, and never make it smaller than the plugin.
And
> if the plugin is not scalable, don't allow resizing at all.
>
> 31) In Viewer Flash, in all browsers, same issue as 30).
>
> 32) In Viewer Image, in all browsers, suggested idea, underneath the
> titlebar, where the menubar would be, there's no menu header items, so is
> there any option to disable menubars?  Likewise with the bottom, where
there
> is a long narrow reectangular area across the bottom, caused by the offset
> of the <-> arrows in the lower-right hand corner, this user interface
> realestate is being unused.  Perharps this realestate can be reclaimed by
> folding in the <-> when considering 22) above.  Or perhaps more useful
info
> about the image could be displayed in the bottom, call it a "status bar",
> with original image dimensions, current dimensions, and ratio in either
(or
> both, having an option to change it) ratio or percentage.  Have the status
> bar be dockable, with options accessible by the menu bar header item
> "View" -> status bar.
>
> 33) In Viewer Image, in all browsers, perhaps have an option to scale X
and
> Y independently (maybe beyond the scope of what we want to do, but just an
> idea), and have independent X/Y ratio and percentage in the status bar.
>
> 34) In Viewer Image, in all browsers, suggested idea, [got distracted,
> sidetracked, tired, braindead, forgot] ... oh, have a popup dialog if you
> want to resize the image or something, with units in pixels, width and
> height, and constrain proportions checkbox, etc., and other options like
> that.
>
> 35) In Snake, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1, Game Control ->
> Help and Help button don't work.  Arrow keys don't work.  Not sure what to
> do to play the game.  Related JavaScript Console error:
>
> ScrollPane not found in file /ios/dynapi/src/lib/snake/snake.js at line 88
> column 5:
>
> this.sp = new ScrollPane(dynapi.librarypath+"/snake/files/help.html")
>
> 36) In Snake, in Internet Explorer 6, Game Control -> Help does not work.
> Help button acts as the same as Start button.
>
> 37) In Tetris, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, 'h' doesn't
> work for help.  No Javascript Console errors.  Seems no key input works
> (unless I missed something).
>
> 38) In Tetris, in Internet Explorer 6, h alerts the help as expected.
> However, game requires 100(!) images or so to be reloaded every time
> something changes position on the DynAPI window.  The demo is unusable.
> Images are tricky to be cached in IE6.  See 4) above.
>
> 39) In Tetris, in all browsers, feature suggestion.  Add "help" to the
"menu
> bar" as a "meanu header item".  Help -> Keys (for instance).
>
> 40) In Everything, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, in the
> Javascript Console, syntax error due to 404 file not found document where
> JavaScript code expected.
>
> File not found: /ios/dynapi/src/lib/bystrom/util/marker.js
>
> 41) In Everything, in Internet Explorer 6, same issue as 4).  App is
> unusable as it's too slow.  The image caching is vital.
>
> Leif
>
> ----- Original Message ----- 
> From: Michael Bystrom
> To: dyn...@li...
> Sent: Monday, September 08, 2003 9:48 AM
> Subject: [Dynapi-Dev] Hello List
>
>
> Hi there dynapi folks
>
> I just signed on and wanted to let you guys know that I've been playing
> around with dynapi for a while now and the result is IOS (internet
operating
> system)
>
> IOS is a virtual OS. It creates a virtual desktop in your browser window.
> You can drag, drop, move, open, close, type and more
>
> I'm using a older version 2.55 ( I now see that you have a version 3 :)
> nice )  that has been modified for the Macintosh platform, the dynapi is
NOT
> Mac friendly.
>
> I only using the dynapi for object creation and events
>
> I've written a written a bunch of new widgets that works fine on the
> Macintosh and windows for that matter.... :)
>
> I've just released the first version and would like you guys to help out
> with some debugging, code suggestions, new widgets etc...
>
> I got some cool ideas for IOS in the future and would like to see it grow.
>
> Go to http://www.michaelbystrom.com download and play
>
> I could say a million more things but I'll save it for a another day.
>
> Nice day...
> Michael
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>

Re: [Dynapi-Dev] Hello List

[Raymond I. <xw...@ya...>]

Very good Leif, very good.

Keep up the good work :)

--
Raymond Irving

--- Leif W <war...@us...> wrote:
> Hello ListHere's my long-awaited QA review of all
> the "demo" pages.  Again,
> I wouldn't have spent about 12 hours today doing
> this if I didn't think it
> was worthwhile for the IOS and the DynAPI in
> general.  So keep that in mind
> as you get all these critiques.  I don't think I
> missed anything.  ;-)  One
> thing, since I am often saying "in all browsers",
> it's a good sign, because
> even if there's a problem, at least it's consistent
> behaviour in all the
> browsers.
> 
> Without further ado, my QA review, analysis, and
> report.
> 
> 1) There's no BGCOLOR setting the background to
> white, so in my browser
> where the default background isn't white, the pages
> look a bit odd.  ;-)
> 
> 2) On the first page, the content is centered in IE
> 6 only, and is not
> centered in the other 3 browsers.
> 
> 3) When looking into the above issue, there's a
> <div> tag before the <body>
> tag.
> 
> 4) In the HTML Document demo, in IE 6, when dragging
> the "txt1.html" icon,
> the image disappears, then IE starts transferring
> data, gets the image, then
> displays it.  I seem to remember some recent
> discussion about this issue
> (how to cache images in IE using the DynAPI).  The
> whole experience in IE is
> affected by this.  Every time anything changes, all
> images are either
> reloaded or compared to the server, and it's slow. *
> Note: when looking at
> the more complex things, the entire demo is so slow
> I'd call it unusable or
> unacceptable in a real-world setting.
> 
> 5) In the HTML Document demo, in Mozilla 1.5 beta,
> IE 6, and Mozilla
> Firebird 0.6.1, after "maximizing" the txt1.html
> window, and then closing it
> (upper-left corner diagonal arrow), further opening
> is no longer the
> original size but nearly the maximized size.  Size
> isn't reset on close?
> Could be a good feature.  But maybe should have a
> "maximize" flag/size, and
> if it's closed while maximized, also save the
> unmaximized size, and reopen
> in the maximized state, but allow it to be
> unmaximized to the previous size.
> 
> 6) HTML Document demo does not work in Opera 7.11
> browser.  Now I think I
> remember Opera 7 support was added in DynAPI 3, so I
> won't test Opera 7.11
> anymore.  Further references to "all browsers" means
> all except Opera 7.11.
> 
> 7) In the HTML Document demo, in all browsers: After
> maximizing the HTML
> Document, scrollbars extend beyond the screen, when
> they probably should
> not.  After minimizing, the scrollbars still remain,
> as if there's still
> content going past the browser's viewable area. *
> Note, in Folders in Symbol
> Mode, I noticed if I expand a folder window beyond
> the endge of the
> browser's viewable area, scrollbars appear in the
> browser, and the mouse
> becomes "detached" from the window resize (letting
> up the mouse button while
> outside the browser window doesn't cancel the
> resizing, so moving the
> mouuuse back over the window causes the resizing to
> continue until the mouse
> is clicked and released).  When I shrink the folder
> window again, the
> browser's scrollbars go away.  This is the behaviour
> I'd expect with the
> HTML Document maximize/minimize/close.  HTML
> Document resizing works as
> expected, with browser scrollbars appearing and
> disappearing as needed.
> 
> 8) In Folder in Symbol Mode, in all browsers,
> there's no "taskbar" so it's
> difficult to get to windows that lie underneath
> other windows, unless moving
> or minimizing all windows above the target window. 
> This quickly becomes
> cumbersome.
> 
> 9) In Folder in Symbol Mode (and probably anything
> with a DynAPI window with
> scrollbars), can't scroll with the mousewheel.  It
> scrolls the entire
> browser window, not the DynAPI window.
> 
> 10) In Folder in List Mode, in all browsers, a user
> interface suggestion, is
> to put the files and folders on the right, (M$
> Explorer style), and only
> Folder tree on the left side.  Since I'm very
> familiar with windows
> explorer, and it's one of the good things about M$
> Windoze, I'd find the
> Folder in List Mode much easier to use if it was set
> up this way, with
> option to choose view type (icons and filename text
> only, or with columns
> with file info (size, last modified, or whatever
> JavaScript has access to,
> which I understand it may not have much access), and
> sortable by clicking on
> the column header.  Also the grid lines are somewhat
> distracting.  Maybe an
> option to turn them on or off.  And what about in
> column view mode, vertical
> grids as well?
> 
> 11) In all demos, in all browsers, double clicking
> on the text label of
> something selects the text in addition to the
> expected behaviour or opening
> the file, folder, or starting the app.
> 
> 12) In Calendar, in all browsers, has "this is not
> ready".  Would be nice to
> enter some data here.
> 
> 13) In ColorRGB, all browsers.  Browser's scrollbars
> show that there's more
> content on the page, but there's no visible elements
> and there should be no
> scrollbars expected.
> 
> 14) In ColorRGB, in all browsers.  Can't type
> numbers into the hex value or
> R, G or B fields.
> 
> 15) In ColorRGB, in Mozilla Firebird 0.6.1, after
> trying to type into the
> text fields, can't type CTRL-W to close the window. 
> Somehow the key events
> are being captured and ignored?
> 
> 16) In ColorPicker, in all browsers, the slidebar
> labels aren't in English,
> so I don't know what they do.  :-)  Maybe a
> "language" option should be
> considered for GUIs -- internationalization,
> localization, globalization,
> locales, whatever buzzword fits best? -- so the user
> can choose the desired
> language.
> 
> 17) In ColorPicker (and possibly others, just
> noticed now), in Mozilla 1.5
> beta.  There's a message in the JavaScript console
> after page load, before
> anything user input:
> 
> Warning: The stylesheet
> http://cyclone.he.net/cgi-bin/error404 was loaded as
> CSS even though its MIME type, "text/html", is not
> "text/css".
> 
> 18) In ColorPicker, in all browsers.  The new color
> is not remembered after
> clicking "ok".  When opening the ColorPicker by
> double clicking, the old and
> new colors are both cyan (pale blue).
> 
> 19) In ColorPicker (and probably any other draggable
> DynAPI window), I can
> drag the window to the bottom of the screen, a
> scrollbar appear, drag it
> back up, disappears.  Same with the right side.  But
> not when dragging to
> the left or top of the browser.  This can make it
> hard to grab a window if
> you've shoved it too far to the top or left. 
> There's no way to scroll in
> those directions.
> 
> There's maybe three options that would be good. 
> First option is the
> default, as it is now.  Second and third, have
> boundaries where you can
> specify the top-right-bottom-left 'softness' or
> 'hardness', 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] WYSIWYG editor for the DynAPI

[Raymond I. <xw...@ya...>]

--- Michael Bystrom <mi...@mi...>
wrote:
> 
> Well first of I would like the DynAPI Community to
> help with it,

Great! Do you plan on:

1) Keeping the source on your website? Or
2) Starting a new SourceForge Project or similar? Or
3) Have us create a CVS module (similat to the logo
module/directory) on the DynAPI Project for the
source?

I prefer #3 as dynapi developers will not have to join
Yet-Another-Project to help out with the development
of the editor. Would could all decide what we want to
do right here. Changes made to the DynAPI can be
easily reflected inside the editor.

>... I wrote
> this application for the DynAPI as a tool to create
> websites fast and easy.

I think it will certainly make life easier for some.

> To get Widget and Events included is not easy BUT it
> is doable... 

I think I can find a way how to get the events to be
linked to the layers, but first I'm looking at how to
make a properies window to edit the properties of the
layer.

>...I know we
> can create FLASH like web sites online fast and on
> the GO (on your laptop in
> an airport) for that meeting later that afternoon.
> How's that for a start :)

Yea, the editor is a sure start for some "create your
own Dyn(API)amic web site online"
 
--
Raymond Irving

> Michael
> 
> > --- Michael Bystrom <mi...@mi...>
> > wrote:
> >> I decided to release the DynEditor.
> >> The DynEditor is a WYSIWYG editor for the DynAPI
> >> library.
> >> 
> >> For more info go http://www.michaelbystrom.com
> >> 
> >> Please let me know what you think
> >> 
> >> Enjoy
> >> Michael
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] Unload problem with latest CVS code

[Raymond I. <xw...@ya...>]

Check out cvs for the latest version. This should have
been fixed

--
Raymond Irving

--- ml...@id... wrote:
> 
> 
> #0: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js>
> line 57
> #1: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js>
> line 145
> #2: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js>
> line 102
> #3: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js>
> line 122
> #4: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js>
> line 100
> #5: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dyndocument.js>
> line 147
> #6: function anonymous() in
>
<http://kshama/~jason/dynapi3x/src/api/dyndocument.js>
> line 153
> #7: function anonymous() in
> <http://kshama/~jason/dynapi3x/src/dynapi.js> line
> 109
> 
> 
> #0
> 
> var p =
> dynapi.setPrototype('DynLayer','DynElement');
>      49 p._adjustSize=function(){
>  -   50     var aw=this._aSzW;
>  -   51     var ah=this._aSzW;
>  -   52     if(this._created && (aw||ah)) {
>  -   53         var i,c,w=0,h=0;
>      54         // get furthest child
>  -   55         for
> (i=0;i<this.children.length;i++){
>  -   56             c=this.children[i];
>  -   57             if(w<(c.x+c.w)) w=c.x+c.w;
>  -   58             if(h<(c.y+c.h)) h=c.y+c.h;
>      59         }
> 
> 
> children has length 5, but no element 0, only 1,2,3
> and 4, most
> probably because we delete the array element in
> destroy all children
> 
> p.destroyAllChildren = function() {
>  -  146     for (var i=0;i<this.children.length;i++)
> {
>  -  147         this.children[i]._destroy();
> >>  148         delete this.children[i];
>     149     }
>  -  150     this.children = [];
>     151 };
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] Hello List

[Leif W <war...@us...>]

Hello ListHere's my long-awaited QA review of all the "demo" pages.  Again,
I wouldn't have spent about 12 hours today doing this if I didn't think it
was worthwhile for the IOS and the DynAPI in general.  So keep that in mind
as you get all these critiques.  I don't think I missed anything.  ;-)  One
thing, since I am often saying "in all browsers", it's a good sign, because
even if there's a problem, at least it's consistent behaviour in all the
browsers.

Without further ado, my QA review, analysis, and report.

1) There's no BGCOLOR setting the background to white, so in my browser
where the default background isn't white, the pages look a bit odd.  ;-)

2) On the first page, the content is centered in IE 6 only, and is not
centered in the other 3 browsers.

3) When looking into the above issue, there's a <div> tag before the <body>
tag.

4) In the HTML Document demo, in IE 6, when dragging the "txt1.html" icon,
the image disappears, then IE starts transferring data, gets the image, then
displays it.  I seem to remember some recent discussion about this issue
(how to cache images in IE using the DynAPI).  The whole experience in IE is
affected by this.  Every time anything changes, all images are either
reloaded or compared to the server, and it's slow. * Note: when looking at
the more complex things, the entire demo is so slow I'd call it unusable or
unacceptable in a real-world setting.

5) In the HTML Document demo, in Mozilla 1.5 beta, IE 6, and Mozilla
Firebird 0.6.1, after "maximizing" the txt1.html window, and then closing it
(upper-left corner diagonal arrow), further opening is no longer the
original size but nearly the maximized size.  Size isn't reset on close?
Could be a good feature.  But maybe should have a "maximize" flag/size, and
if it's closed while maximized, also save the unmaximized size, and reopen
in the maximized state, but allow it to be unmaximized to the previous size.

6) HTML Document demo does not work in Opera 7.11 browser.  Now I think I
remember Opera 7 support was added in DynAPI 3, so I won't test Opera 7.11
anymore.  Further references to "all browsers" means all except Opera 7.11.

7) In the HTML Document demo, in all browsers: After maximizing the HTML
Document, scrollbars extend beyond the screen, when they probably should
not.  After minimizing, the scrollbars still remain, as if there's still
content going past the browser's viewable area. * Note, in Folders in Symbol
Mode, I noticed if I expand a folder window beyond the endge of the
browser's viewable area, scrollbars appear in the browser, and the mouse
becomes "detached" from the window resize (letting up the mouse button while
outside the browser window doesn't cancel the resizing, so moving the
mouuuse back over the window causes the resizing to continue until the mouse
is clicked and released).  When I shrink the folder window again, the
browser's scrollbars go away.  This is the behaviour I'd expect with the
HTML Document maximize/minimize/close.  HTML Document resizing works as
expected, with browser scrollbars appearing and disappearing as needed.

8) In Folder in Symbol Mode, in all browsers, there's no "taskbar" so it's
difficult to get to windows that lie underneath other windows, unless moving
or minimizing all windows above the target window.  This quickly becomes
cumbersome.

9) In Folder in Symbol Mode (and probably anything with a DynAPI window with
scrollbars), can't scroll with the mousewheel.  It scrolls the entire
browser window, not the DynAPI window.

10) In Folder in List Mode, in all browsers, a user interface suggestion, is
to put the files and folders on the right, (M$ Explorer style), and only
Folder tree on the left side.  Since I'm very familiar with windows
explorer, and it's one of the good things about M$ Windoze, I'd find the
Folder in List Mode much easier to use if it was set up this way, with
option to choose view type (icons and filename text only, or with columns
with file info (size, last modified, or whatever JavaScript has access to,
which I understand it may not have much access), and sortable by clicking on
the column header.  Also the grid lines are somewhat distracting.  Maybe an
option to turn them on or off.  And what about in column view mode, vertical
grids as well?

11) In all demos, in all browsers, double clicking on the text label of
something selects the text in addition to the expected behaviour or opening
the file, folder, or starting the app.

12) In Calendar, in all browsers, has "this is not ready".  Would be nice to
enter some data here.

13) In ColorRGB, all browsers.  Browser's scrollbars show that there's more
content on the page, but there's no visible elements and there should be no
scrollbars expected.

14) In ColorRGB, in all browsers.  Can't type numbers into the hex value or
R, G or B fields.

15) In ColorRGB, in Mozilla Firebird 0.6.1, after trying to type into the
text fields, can't type CTRL-W to close the window.  Somehow the key events
are being captured and ignored?

16) In ColorPicker, in all browsers, the slidebar labels aren't in English,
so I don't know what they do.  :-)  Maybe a "language" option should be
considered for GUIs -- internationalization, localization, globalization,
locales, whatever buzzword fits best? -- so the user can choose the desired
language.

17) In ColorPicker (and possibly others, just noticed now), in Mozilla 1.5
beta.  There's a message in the JavaScript console after page load, before
anything user input:

Warning: The stylesheet http://cyclone.he.net/cgi-bin/error404 was loaded as
CSS even though its MIME type, "text/html", is not "text/css".

18) In ColorPicker, in all browsers.  The new color is not remembered after
clicking "ok".  When opening the ColorPicker by double clicking, the old and
new colors are both cyan (pale blue).

19) In ColorPicker (and probably any other draggable DynAPI window), I can
drag the window to the bottom of the screen, a scrollbar appear, drag it
back up, disappears.  Same with the right side.  But not when dragging to
the left or top of the browser.  This can make it hard to grab a window if
you've shoved it too far to the top or left.  There's no way to scroll in
those directions.

There's maybe three options that would be good.  First option is the
default, as it is now.  Second and third, have boundaries where you can
specify the top-right-bottom-left 'softness' or 'hardness', to either be
soft or hard, hard being like a brick wall, and not allowing the dragged
window to go beyond visible space, or soft being like mush, allowing a
DynAPI window to be dragged anywhere, and automatically resize the viewable
area in the browser and scroll the viewable area to where the dragged dynapi
window will end up.  (Not sure if this is possible or the complexity, but
from a GUI standpoint it would be more consistent with the behaviour
observed in the other two browser borders).

Maybe a fourth option, is to have something like an taskbar (autohide
option, always on top option), that is a dock, and have DynAPI windows be
dockable and get minimized to icons with (optional text labels).

20) In ColorPicker, in all browsers, clicking in the color plane area
(largest square with continuous color variations) does not move the circular
color selector until the click is released.  This prohibits the user from
clicking anywhere and starting to drag immediately and see the colors he's
currently dragging over.  The user must click the circle first.  It would be
more user friendly to have the circle snap into place underneath the click,
so dragging can continue seamlessly.

21) In Texter App Mode (and all other dragable / resiable elements), in all
browsers.    All four size should allow resizing of the window in the
specified direction only.  All 4 corners should allow simultaneous resizing
in both directions specified.  Currently only the lower-right is resizable.

22) In Texter App Mode (and all other dragable / resiable elements), in all
browsers.      There needs to be an indication when the mouse is over a
button, or a draggable area.  Maybe change to a reverse highlight for menu
buttons, or like any apps in Windows, a little box with shading appears
around the items in the menu bar.  In windows when moving the mouse over a
resizable element, the mouse pointer changes to some arrows.  While this may
not be easy to do in all browsers, you can change the thing underneath the
mouse i.e. make the left border change highlighted colors when mouse over,
etc..  Also, having "resizable" or "draggable" hotspots look "grippy"
somehow, instead of all the same grey, might be an option, or might not.

23) In Texter App Mode, in Mozilla 1.5 beta, get this silent JavaScript
error in the console when mousing over the text area.  Thinking it's due to
the Mozilla race condition bug or something.

Error: [Exception... "'Permission denied to get property
HTMLDivElement.parentNode' when calling method:
[nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001e
(NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]

24) In Texter App Mode, in Mozilla Firebird 0.6.1, can not type any text.
Have this error in the JavaScript Console:

Error: [Exception... "'Permission denied to get property
HTMLDivElement.parentNode' when calling method:
[nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001e
(NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]

Exact same error as 23, but Mozilla 1.5 beta works, oddly enough.  NOTE,
this may be an instance that correlates with my earlier inability to type
CTRL-W to close the window in Mozilla Firebird 0.6.1.  I am unable to type
CTRL-W now.  I maybe didn't notice the JavaScript error then as I wasn't
looking.  ;-)  This is probably how to reproduce that condition, by
triggering the known race condition bug.

25) In Texter Document Mode, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1.
Same error as reported in 23) and 24).  The only difference, in Mozilla 1.5
beta, the error is seen once on mouse over the text area, and once on mouse
out.  In Mozilla Firebird 0.6.1, the error is seen three times on mouse
over, three times on mouse out.  Mozilla 1.5 beta allows text typing, and
Mozilla 0.6.1 does not, same as in errors 23) and 24) above.  However!  I
/WAS/ able to use CTRL-W to close Mozilla Firebird 0.6.1 (this time).
Further inspection, sometimes Mozilla Firebird 0.6.1 throws one or three of
the mentioned errors.  Odd...

26) In Viewer Quicktime, in all browsers, when resizing the DynAPI window
container thing, the Quicktime plugin does not reesize.  Maybe no need to
have the DynAPI window resizable if the underlying plugin isn't capable.

27) In Viewer Quicktime, in all browsers, when using the "minimize to
titlebar" (I know it's a MAC thing, there's no windows equivalent, and it's
NOT the same thing as a windows minimize, so that's why I call it minimize
to titlebar, as opposed to the assumed taskbar in windows nomenclature), the
DynAPI window minimizes nicely but it leaves the plugin visible on the
screen.  This is a bit silly.  Maybe shouldn't be minimizable.

28) In Viewer Quicktime, in Mozilla 1.5 beta, when dragging the DynAPI
window after clicking the Quicktime Plugin's play button, the image skips to
the (first or last, not sure, they're both the same) image even though the
sound still plays through the other frames.  Maybe the window should not be
draggable while a movie is playing, if there's any possible way to detect
the play status.

29) In Viewer Quicktime, in Mozilla 1.5 beta, somehow by playing, dragging,
and minimizing to titlebar, I managed to make the Quicktime Plugin go on top
on the title bar, and now it's stuck half way up.  It moves when I move the
titlebar.  Kind of comical.  :D  Have to see the screenshot to believe it I
guess.
http://dynapi.kicks-ass.net/DynAPI_CVSROOT/test/Michael_Bystrom_IOS_-_QA/Viewer_QuickTime_bug.gif

30) In Viewer Quicktime, in all browsers, you can resize the DynAPI window
so it's smaller than the Quicktime plugin, then you can't make it bigger,
unless you Maximize, close, and reopen to exploit problem in 5) above, OR if
you drag the DynAPI window off the browser, let go of the mouse button,
return the mouse over the browser and click.  Then the DynAPI window appears
saying the Quicktime plugin is hidden.  You can then get one click anywhere
on that DynAPI window, then the plugin appears.  But if you click on the
lower-right corner for resizing, you can make the DynAPI window bigger
again.  OR you can make it go hidden just by clicking anywhere else on the
browser... so that's easier.  But maybe there should be a restriction on how
small you can make a window, and never make it smaller than the plugin.  And
if the plugin is not scalable, don't allow resizing at all.

31) In Viewer Flash, in all browsers, same issue as 30).

32) In Viewer Image, in all browsers, suggested idea, underneath the
titlebar, where the menubar would be, there's no menu header items, so is
there any option to disable menubars?  Likewise with the bottom, where there
is a long narrow reectangular area across the bottom, caused by the offset
of the <-> arrows in the lower-right hand corner, this user interface
realestate is being unused.  Perharps this realestate can be reclaimed by
folding in the <-> when considering 22) above.  Or perhaps more useful info
about the image could be displayed in the bottom, call it a "status bar",
with original image dimensions, current dimensions, and ratio in either (or
both, having an option to change it) ratio or percentage.  Have the status
bar be dockable, with options accessible by the menu bar header item
"View" -> status bar.

33) In Viewer Image, in all browsers, perhaps have an option to scale X and
Y independently (maybe beyond the scope of what we want to do, but just an
idea), and have independent X/Y ratio and percentage in the status bar.

34) In Viewer Image, in all browsers, suggested idea, [got distracted,
sidetracked, tired, braindead, forgot] ... oh, have a popup dialog if you
want to resize the image or something, with units in pixels, width and
height, and constrain proportions checkbox, etc., and other options like
that.

35) In Snake, in Mozilla 1.5 beta, Mozilla Firebird 0.6.1, Game Control ->
Help and Help button don't work.  Arrow keys don't work.  Not sure what to
do to play the game.  Related JavaScript Console error:

ScrollPane not found in file /ios/dynapi/src/lib/snake/snake.js at line 88
column 5:

this.sp = new ScrollPane(dynapi.librarypath+"/snake/files/help.html")

36) In Snake, in Internet Explorer 6, Game Control -> Help does not work.
Help button acts as the same as Start button.

37) In Tetris, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, 'h' doesn't
work for help.  No Javascript Console errors.  Seems no key input works
(unless I missed something).

38) In Tetris, in Internet Explorer 6, h alerts the help as expected.
However, game requires 100(!) images or so to be reloaded every time
something changes position on the DynAPI window.  The demo is unusable.
Images are tricky to be cached in IE6.  See 4) above.

39) In Tetris, in all browsers, feature suggestion.  Add "help" to the "menu
bar" as a "meanu header item".  Help -> Keys (for instance).

40) In Everything, in Mozilla 1.5 beta and Mozilla Firebird 0.6.1, in the
Javascript Console, syntax error due to 404 file not found document where
JavaScript code expected.

File not found: /ios/dynapi/src/lib/bystrom/util/marker.js

41) In Everything, in Internet Explorer 6, same issue as 4).  App is
unusable as it's too slow.  The image caching is vital.

Leif

----- Original Message ----- 
From: Michael Bystrom
To: dyn...@li...
Sent: Monday, September 08, 2003 9:48 AM
Subject: [Dynapi-Dev] Hello List


Hi there dynapi folks

I just signed on and wanted to let you guys know that I've been playing
around with dynapi for a while now and the result is IOS (internet operating
system)

IOS is a virtual OS. It creates a virtual desktop in your browser window.
You can drag, drop, move, open, close, type and more

I'm using a older version 2.55 ( I now see that you have a version 3 :)
nice )  that has been modified for the Macintosh platform, the dynapi is NOT
Mac friendly.

I only using the dynapi for object creation and events

I've written a written a bunch of new widgets that works fine on the
Macintosh and windows for that matter.... :)

I've just released the first version and would like you guys to help out
with some debugging, code suggestions, new widgets etc...

I got some cool ideas for IOS in the future and would like to see it grow.

Go to http://www.michaelbystrom.com download and play

I could say a million more things but I'll save it for a another day.

Nice day...
Michael

Re: [Dynapi-Dev] WYSIWYG editor for the DynAPI

[Michael B. <mi...@mi...>]

Raymond,

> What are your plans for the WYSIWYG editor? What are
> your plans for DynAPI? Will you be contributing some
> of your enhancements (debugger, etc) to DynAPI 3.0?

I think the DynAPI is a fantastic building block. Like most of you I've
built my own api versions that incorporate most of the things that the
DynAPI does but what I fell for in the DynAPI was the event handling. It's
real easy to create layers, but to connect them all and make sense of them
is an art... This applies to all programs languishes :) The DynAPI Event
class made this possible.

I could not have written IOS or DynEditor without the brilliant construction
of the event handle. Kudos to you all or the one who wrote it :)

As for version 3 I just started to look at it, there are many changes and a
lot to look at. But what I like most right now is the before onload
thing.... Brilliant.

Yes! I think will port all my work over to 3x version, I will also help in
the development of the Macintosh side of it.

> I have a few suggestions for the editor but those will
> come in time. My dream is to one day help to create a
> Visual DynAPI Editor :) What do you think?

I'm a 100% sure that this will happen. The DynEditor was a easy to create
compare to the IOS. The inheritance problems I had and to build a new tree
pane, list pane AND to be able to move ALL folders between the desktop and
other folder was a times confusing state of mind... And is still :P

> The editor surely makes creating DynAPI objects a
> snap! I'm beginning to as it I can create anything in
> less than a few minutes!

Yes a offline/online Macromedia dreamweaver DynAPI.

> Ok. Let's take me not get excited here. Michael, where
> do we go from here with this amazing tool?

Well first of I would like the DynAPI Community to help with it, I wrote
this application for the DynAPI as a tool to create websites fast and easy.
To get Widget and Events included is not easy BUT it is doable... I know we
can create FLASH like web sites online fast and on the GO (on your laptop in
an airport) for that meeting later that afternoon.
How's that for a start :)

Michael

> --- Michael Bystrom <mi...@mi...>
> wrote:
>> I decided to release the DynEditor.
>> The DynEditor is a WYSIWYG editor for the DynAPI
>> library.
>> 
>> For more info go http://www.michaelbystrom.com
>> 
>> Please let me know what you think
>> 
>> Enjoy
>> Michael

[Dynapi-Dev] Unload problem with latest CVS code

[<ml...@id...>]

#0: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js> line 57
#1: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js> line 145
#2: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js> line 102
#3: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js> line 122
#4: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dynlayer_base.js> line 100
#5: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dyndocument.js> line 147
#6: function anonymous() in <http://kshama/~jason/dynapi3x/src/api/dyndocument.js> line 153
#7: function anonymous() in <http://kshama/~jason/dynapi3x/src/dynapi.js> line 109


#0

var p = dynapi.setPrototype('DynLayer','DynElement');
     49 p._adjustSize=function(){
 -   50     var aw=this._aSzW;
 -   51     var ah=this._aSzW;
 -   52     if(this._created && (aw||ah)) {
 -   53         var i,c,w=0,h=0;
     54         // get furthest child
 -   55         for (i=0;i<this.children.length;i++){
 -   56             c=this.children[i];
 -   57             if(w<(c.x+c.w)) w=c.x+c.w;
 -   58             if(h<(c.y+c.h)) h=c.y+c.h;
     59         }


children has length 5, but no element 0, only 1,2,3 and 4, most
probably because we delete the array element in destroy all children

p.destroyAllChildren = function() {
 -  146     for (var i=0;i<this.children.length;i++) {
 -  147         this.children[i]._destroy();
>>  148         delete this.children[i];
    149     }
 -  150     this.children = [];
    151 };

Re: [Dynapi-Dev] IO Element and Images

[Raymond I. <xw...@ya...>]

This is a problem with IE. It fails to load the
<images> inside html after a page load or during an
ioelement (iframe) call.

In the future we'll find a way to preload images from
a string. Hint:

var html = '<img src="m.gif">ddew<img src="a.gif">'
dynapi.functions.preLoadImages(html)
// ^ loads both m.gif and a.gif

or

var imgAr=['m.gif','a.gif'];
dynapi.functions.preLoadImages(imgAr);


--
Raymond Irving


--- Daniel Tiru <de...@ti...> wrote:
> Hi!
> 
> I just have a bit of advice for everyone using
> IO-Element. If you wish
> to create content with images from the answer file,
> always use:
> 
> io.execInParent(function(){
> 
>
ImgTrans=dynapi.functions.getImage('/images/trans.gif',1,1);
>  	//code for showing the images
> })
> 
> I mean all images, including transparent gifs,
> everything...
> 
> This means that when using the io-element, the <img>
> tag  will become
> banned, and i will explain why this is.
> 
> If you forget say one <img> tag, the rest of the
> images, will not be
> loaded properly. About 10% of the images will load
> and display properly,
> the rest wont.
> 
> I dont have a clue how to solve this in any other
> way, but one idee
> would be to remove all <img> tags in the
> io.execInParent function maybee
> and replace them with the dynapi getImage function.
> I dont know if this
> is efficient, probably not.. But its the only idee i
> have :)
> 
> Feedback is appreciated.
> 
> Best Regards
> Daniel Tiru
> 
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com