Menu
▾
▴
dynapi-dev
|
From: Michael B. <mi...@mi...> - 2003-09-09 00:43:10
|
Hi there dynapi folks I just signed on and wanted to let you guys know that I=B9ve been playing around with dynapi for a while now and the result is IOS (internet operatin= g 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=B9m using a older version 2.55 ( I now see that you have a version 3 :) nic= e ) that has been modified for the Macintosh platform, the dynapi is NOT Mac friendly.=20 I only using the dynapi for object creation and events I=B9ve written a written a bunch of new widgets that works fine on the Macintosh and windows for that matter.... :) I=B9ve 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=B9ll save it for a another day. Nice day... Michael |
|
From: Leif W <war...@us...> - 2003-09-09 03:29:37
|
Hello ListHi Michael. It's cool to have new enthusiastic developers. :) I'm looking over the site with what browsers I have available (Internet Explorer 6, Mozilla 1.5, Mozilla Firebird 0.6.1, Opera 7.11), all on win32 platform. I'd strongly suggest you do one (or maybe both) of these things... either post your patches against the "newest" 2.5.7 build (which I'm not too familiar with, and there's someone else on the list whose company has patches to 2.5.7), or better, focus on the new 3.0.x library, find and fix bugs there, port apps over to that. Unfortunately I must sleep now, so I can't do an exhaustive look. 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 |
|
From: Michael B. <mi...@mi...> - 2003-09-09 07:06:12
|
My version of the 2.55 is fairly modified and I will not port it over to 2.5.7 but I just downloaded the 3x version and will start to play with it, there are some mac problems here to but I don't think there will be a problem. Cool it can create layers before load WAY cool!! I see what I can do Michael > Hello ListHi Michael. > > It's cool to have new enthusiastic developers. :) I'm looking over the > site with what browsers I have available (Internet Explorer 6, Mozilla 1.5, > Mozilla Firebird 0.6.1, Opera 7.11), all on win32 platform. I'd strongly > suggest you do one (or maybe both) of these things... either post your > patches against the "newest" 2.5.7 build (which I'm not too familiar with, > and there's someone else on the list whose company has patches to 2.5.7), or > better, focus on the new 3.0.x library, find and fix bugs there, port apps > over to that. > > Unfortunately I must sleep now, so I can't do an exhaustive look. > > Leif > 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 |
|
From: Raymond I. <xw...@ya...> - 2003-09-09 03:39:15
|
Hi Michael, Wow! Awesome! The demo is look really nice (very nice). You've got to look into DynAPI 3.0 as it has a lot of new features that will help you to create more complex component. Check out the lastest snapshot here: http://dynapi.sourceforge.net/doccenter/index.php?Snapshots PS. You need to suncribe to the mailing list with using mi...@mi.... http://dynapi.sourceforge.net/doccenter/index.php?MailingLists Keep up the good work. -- Raymond Irving --- Michael Bystrom <mi...@mi...> wrote: > 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 > > > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
|
From: Michael B. <mi...@mi...> - 2003-09-09 06:54:28
|
Raymond, Yes I'm downloading it now and will take a look at it. I'm glad you like it :) There are some cool stuff you can do with it Michael > Hi Michael, > > Wow! Awesome! > > The demo is look really nice (very nice). > > You've got to look into DynAPI 3.0 as it has a lot of > new features that will help you to create more complex > component. > > Check out the lastest snapshot here: > > http://dynapi.sourceforge.net/doccenter/index.php?Snapshots > Keep up the good work. > > > -- > Raymond Irving > --- Michael Bystrom <mi...@mi...> > wrote: >> 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 |
|
From: Leif W <war...@us...> - 2003-09-10 15:24:23
|
Hello ListHi, Overall everything looks really cool so far. I like the "shadow" effect when moving or resizing a DynAPI window. This is exactly what I need to implement a suggested enhancement to my SnapX class in DynAPI3. But I think a more general solution would be to have a "shadow" effect class, and enable it with a flag, so other classes (like my SnapX) could use the shadow, but other classes could either use it or not. Not sure how you've implemented it in DynAPI 2.5.5, maybe I'll take a look. Right now I'm doing a more comprehensive QA-type test on Win2k with Mozilla 1.5 beta, IE 6, Mozilla Firebird 0.6.1, and Opera 7.11 [non-java], where I'll just try all the demos and comment on anything that could be a problem, either programmatically or in terms of user interface or features. Again I strongly hope that you port all this stuff over to DynAPI3. After that, then maybe you could work on enhancements to the DynAPI3 version. 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 |
|
From: Leif W <war...@us...> - 2003-09-11 03:36:33
|
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 |
|
From: Raymond I. <xw...@ya...> - 2003-09-11 13:17:40
|
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 |
|
From: Leif W <war...@us...> - 2003-09-11 22:37:26
|
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.../ > |
|
From: Michael B. <mi...@mi...> - 2003-09-12 10:00:15
|
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
|
|
From: Leif W <war...@us...> - 2003-09-14 16:11:15
|
----- 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.../ > |
|
From: Michael B. <mi...@mi...> - 2003-09-15 09:07:50
|
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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X