#896 closed defect (wontfix)
[widgets] Rounded: anti-alias does not work properly
Reported by: | rsaccon [at] gmail [dot] com | Owned by: | Tom Trenka |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Widgets | Version: | 0.3 |
Keywords: | Cc: | [email protected]… | |
Blocked By: | Blocking: |
Description
I experimented at dojo-trunk/demos/widget/rounded.html to set antialias true/false. When set antialias to true, the image quality gets only a very little bit better. Comparing with the antialiased rounded corners from the orignial curvyconers.net code, there is a huge visual quality difference. The corners from the curvycorners.net code are much smoother.
Change History (8)
comment:1 Changed 15 years ago by
Milestone: | → 0.4 |
---|---|
Status: | new → assigned |
Version: | → 0.3 |
comment:2 Changed 15 years ago by
Owner: | changed from anonymous to Tom Trenka |
---|---|
Status: | assigned → new |
comment:3 Changed 15 years ago by
Cc: | [email protected]… added |
---|
Thanks Tom. If you are going to update that widget then I'd suggest splitting out that whole "Rounded" function and putting it in the src/html directory.
comment:4 Changed 15 years ago by
One more:
dojo.widget.tags.addParseTreeHandler("dojo:rounded");
should be placed somewhere AFTER the line
dojo.require("dojo.widget.*");
comment:5 Changed 15 years ago by
This widget is going to end up going way and being replaced (by version 0.4) by a function in dojo.html that can be applied to any node.
comment:6 Changed 15 years ago by
Summary: | Antialiasing at Rounded Widget does not work propperly → [widgets] Rounded: anti-alias does not work properly |
---|
comment:7 Changed 15 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I've added a whole-scale refactor of the curvyCorners script to dojo.lfx (dojo.lfx.rounded); because of that, I've deprecated the Rounded widget for removal in 0.5.
I'm going to close this bug and the other Rounded bug in favor of the new behavior; any issues with that code should have a new bug filed against it.
I'll take this one on; it looks like the code has a few infrastructure improvements that could be made as it is.