----- Original Message ----- From: "Michael Bystrom" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 12, 2003 5:59 AM Subject: Re: [Dynapi-Dev] Hello List
> Den 03-09-11 05.37, skrev "Leif W" <[EMAIL PROTECTED]>: > > 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: [EMAIL PROTECTED] > > 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 > [EMAIL PROTECTED] > http://www.mail-archive.com/[EMAIL PROTECTED]/ > ------------------------------------------------------- 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]/
