Very good Leif, very good. Keep up the good work :)
-- Raymond Irving --- Leif W <[EMAIL PROTECTED]> 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[EMAIL PROTECTED]/
