Tue 24 Apr 2007 02:57:48 PM UTC, comment #11:
I attached another patch that should take care of your personal CSS.
|
Mon 25 Sep 2006 10:41:45 PM UTC, comment #10:
There is also the bar of file chunks (that shows which chunks are available, downloaded, etc); It too suffers from the same affliction -- it uses the background color of table cells to fill the bar.
The problem with my solution is that several colors are required here. Images are the only way to go in this case.
I'm playing again with the idea of using 1x1 images (embedded in css, or otherwise) to fill the cells instead. It can work except I don't think there is any way to programmatically define their colors. Using PPMs could be programmable, but I don't know of any browser that supports them :(.
Would anyone have a problem if this chunk-bar became a fixed color bar? Because, otherwise, I don't think there is any way for users like me to see it :(.
|
Sat 12 Aug 2006 05:58:56 PM UTC, comment #9:
Dennis,
I can confirm that your "new" progress bar works well in Opera and Firefox, but not in Elinks -- as you said.
|
Fri 14 Jul 2006 03:48:50 AM UTC, comment #8:
I've attached a sample.html with yet another way to implement the progress bar -- via the border of an empty DIV element. It will work when browsers force system colors -- but not in text browsers. It should also display better under Opera, etc.? Confirmation?
Regarding the HR implementation, I believe it was the font-size:1px (setting an absolute value for font-size) that confused Opera -- perhaps giving it a relative or percentage value could also work?
|
Wed 12 Jul 2006 03:09:39 AM UTC, comment #7:
Did I mention it's possible to view this patched progress bar in links, and other such text-based web browsers? :]
I really wish other browser users would help out a little (cough zet cough). How hard can it be to have a Hard Rule progress bar display the same in Opera/Konqueror as in Firefox :\
|
Mon 12 Jun 2006 08:25:05 PM UTC, comment #6:
Closed because of lack of updates to this patch.
If you would like to update it please drop a note,
i will re-open it.
|
Mon 20 Mar 2006 12:56:39 AM UTC, comment #5:
i don't mind not applying the patch as is, since there are minor issues with other browsers (i'm sure it's some small bit of non-fully-compliant css code), but, once they're resolved, i think it's a serious issue. i'm sure there are enough other people that surf the web as i do, for which the current interface is very hard to read.
and, on that note, i would really like users of the other browsers to point out what is causing the problem in rendering the bar. since i don't use them. i (naively) assumed that the css code i used was a standard.
|
Fri 17 Mar 2006 07:15:57 PM UTC, comment #4:
Try it in Opera as well. All rows become too fat, and the colour of the bar is incorrect.
When making a major change like this you really must test IE, Opera, Mozilla and Konqueror to make sure there are no regressions.
|
Fri 17 Mar 2006 06:53:06 PM UTC, comment #3:
regarding making my own html_theme, i don't think i'd be able to replace the old table with my hard rule, since the table code is generated by mlnet -- and not, as far as i can see, by some html template. before i settled on the HR idea, i was playing around with having a 1x1 image (an embedded png in the SRC of an image tag), and then resizing that to the right percentage. this would surely produce the same results across all browsers (although i still think the HR method should as well) ... but it too would require a patch, and not just a tweaking of the css style. this should be the simplest, cleanest way to do it.
|
Fri 17 Mar 2006 06:27:41 PM UTC, comment #2:
people still use IE ? :(
how does it look there? what do you mean by "bad"? i thought HR was supposed to be a standard html object. maybe you can figure out what is making it look bad -- cuz it looks exactly the same here =\. maybe you can post a small screenshot of how it renders there?
and, on a side note, i think it "forcing own colors" should be the standard way of browsing the web. since when were we (the users) supposed to bow down to the (ugly) styling whims of web designers? content before design is my philosophy. also, having a standard color scheme across all pages really helps readability, i have found. :). enough preaching.
|
Fri 17 Mar 2006 05:56:55 PM UTC, comment #1:
This looks bad on IE, so it certainly does make a difference.
Your specialized use of "forcing own colors" is not standard, so it isn't really a target of mldonkey. The current code has been tested and used for a long time across browsers. If you want a custom look, you can create your own html_theme with its own CSS.
|
Fri 17 Mar 2006 06:28:45 AM UTC, original submission:
in mldonkey's web interface, a table with two cells was used to display download progress (with widths corresponding to the completed and remaining percentages). this patch simplifies the html by displaying progress as a single HR element, left aligned. effectively, it will look almost exactly as before, albeit the code will be cleaner.
BUT, the main purpose of this patch is to have the download progress bars displayable when users have their browsers set to force their own colors (ie, mine forces /all/ pages to have black backgrounds and gray text). unfortunately, this eliminates all background-color style elements (bgcolors, etc), which is what the previous table implementation was using (the bar was the background color of the table cell). so, without this patch, i cannot see the progress bar at all! using this method, the bar is an actual line, and displays fine :)
and, did i mention it cleans up the code? it also eliminates the color_vd_remaining style variable, which was pretty useless anyways, since it was pretty much always the background color (ie, effectively transparent).
for users who force their own colors, this patch is essential -- and for others, it makes no difference, besides simplifying the style a bit. actually, the /only/ display difference is that the bar is rendered with rounded edges here (in my firefox) ... which is a positive side-effect, i think, since if a style declares a larger bar size, it becomes nice and rounded -- very good looking (although, i prefer the small default of 2px).
|