> > Oh? What was wrong with Simon's proposal? I see no reason that we > > couldn't do that. > Redundancy, for starters.
I explained in a previous email how this can be achieved elegantly, and without two progress bars. What is wrong with my proposal? > Without using javascript? Remember, we advise users to disable > javascript in their web browsers if they can, because something may > always get through the filter. If they did, then it will appear in a browser window as normal - larger than we intended, but it will work just fine. Personally, I doubt even 5% of our users follow our advice with Javascript anyway - and Javascript is one of the easier things to filter for, since there is a finite number of ways to embed Javascript in a HTML document. > > Not really, it is possible to make most graphical representations look > > ok in text if you are smart about it - but I don't think you can ever do > > that with frames. > Or tables. Or anything. Bullshit, it is relatively easy to make a website, whether it uses tables or not, to look ok in lynx or links - hell, you don't even need to look further than our own project website if you don't believe me. > lynx... [GOT ][GOT ][NOTGOT][NOTGOT][NOTGOT]... is the best we can > hope to achieve without browser specific code (yuck). If it is done using tables and cell background images, then a lynx user won't even see the progress bar. All they really need to see is the % complete. > Simon's proposal is not a solution, it is a half-baked idea. You keep saying that - but I haven't seen a shread of support. WHAT IS WRONG WITH SIMON'S IDEA? > But we would end up with > two bars, organized the same way Bombe's cellular system works. In other > words, we have a plain progress bar, which fills from one end and > represents the total blocks downloaded, and we have a color coded strip > that represents all available blocks (as slices) - one color for > fetching, one color for failed permanently, one color for failed but going > to retry, and one color for not tried yet. It isn't necessary to have two progress bars. All we need is an arrow or some indicator on the single progress bar indicating where the download will be complete - but which moves to the right one block every time a block download fails. > > I ment a browser window with no tool-bar, not completely borderless. > The question stands. It will use JavaScript, but will fail gracefully if it isn't present. Ian. -- Ian Clarke ian@[freenetproject.org|locut.us|cematics.com] Latest Project http://cematics.com/kanzi Personal Homepage http://locut.us/
msg05904/pgp00000.pgp
Description: PGP signature
