JS Canvas - Simplistic demo of Processing.js library is drawn badly
Arioch //BDV/
http://hyper-metrix.blogspot.com/2009/08/testing-processingjs-in-blogger.html?showComment=1253610694062#c1530875285648358471
Here is demo from http://processingjs.org/
It is rendered with error (described as 1st comment)
I hope to see Canvas tag vastly used and Processing.js is expected to
be popular language for Canvas.
So be it the bug in Opera itself (probably) or in process.js library
(possibly) it is better to find and fix before it would affect many
images on many pages.
Remco Lanting
> Affects both Opera 10.final and 10.10 weekly on Win32 at least
>
> http://hyper-metrix.blogspot.com/2009/08/testing-processingjs-in-blogger.html?showComment=1253610694062#c1530875285648358471
> Here is demo from http://processingjs.org/
> It is rendered with error (described as 1st comment)
http://www.robodesign.ro/paintweb/trunk/demos/demo1.html
1) Click edit image
2) Click circle/ellipse
3) Click the ellipse tab
4) Set border width to 30px
5) Draw an ellipse
Doing it this way gets you a nice shape.
6) Click the main tab
7) Click line
8) Click line tab
9) Set line cap to "butt" or "square"
10) Click main
11) Click ellipse
12) Draw ellipse
When set to "butt" there is an opening at the top, when set to square
there is a weird shape at the top.
In firefox I only get an abnormal shape when the ellipse is small and the
line cap is set to "square"
> I hope to see Canvas tag vastly used and Processing.js is expected to
> be popular language for Canvas.
> So be it the bug in Opera itself (probably) or in process.js library
> (possibly) it is better to find and fix before it would affect many
> images on many pages.
In this case I would say it's a bug in both Opera and the library,
although how the end cap stuff should behave eludes me :)
--
Remco Lanting
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Rijk van Geijtenbeek
<the_A...@nm.ru>:
This stuff is beyond me, but I can see the problem... I hope you file a
bug report?
--
Rijk van Geijtenbeek
Opera Software ASA, Documentation & QA
Tweak: http://my.opera.com/Rijk/blog/
"The most common way to get usability wrong is to listen to what users
say rather than actually watching what they do." - J.Nielsen
Arioch
> bug report?
I don't know, because Opera UI does never tells, if commit succeded or
not, when you engage Help|Malfunctioning Site menu.
It should i think use some checksum or whatever, so that it will tell if
the site report is 100% inserted into database, or was filtered by some
firewall or connection error.
However, all i can do is try and hope it works :-)
Rijk van Geijtenbeek
<the_A...@nm.falsedomain.ru>:
Please use https://bugs.opera.com/wizard/ to report bugs.
--
Rijk van Geijtenbeek
Opera Software ASA
Arioch
<ri...@opera.removethiz.com> сообщал:
> Please use https://bugs.opera.com/wizard/ to report bugs.
Sorry, Rijk, but why should i bother ?
As a user i could benefit in Opera's support for vast number of sites i
surf.
- yet Canvas and Processing.js would not be in vast usae anytime soon.
As a community part i could benefit from having list of Opera bugs and
seeing progress over them.
- but Opera Software ASA always denied that feasability. Community tried
to settle alternative tracker with auto-sync with your tracker - seems it
failed, never managed to get it working. Though that tracker, be it
functional, i might bother filling.
As a loyal user i already reported twice, via Opera built-in UI and via
this forum. And sparkled one more report in discussion. I've done my duty.
All the rest is inside Opera Software ASA. You (most probably) have record
for that site, marked with beta version of browser. So, there'd be some
person reviewing that database. And there is to be one-click button, if
needed, to copy that my report from that dabase into bug-tracker. That's
in the hands of your programmers, if you (Opera) need it.
Same for the forum, you (Opera) may make cusomized Opera M2, integrated
with bug-tracker. Or even simplier - make a special e-mail adress, so you
would only need to forward my message to such an internal address to make
it entered into bug tracker.
If Opera wants to spent time of its programmers for exploration of an
ambitious interesting new lands, like Torrent, like Unite, rather than
enhancing internal infrastructure, then be it. You know better what should
them spend their time on. If that is not important for Opera, then so it
is.
But just like that i would spend my time on things, interesting for me. I
made my duty twice and don't want to make it yet again.
If Opera Software counts such reports important, it can benefit from it,
either by your manuall dull work or by implementing semi-automatical
import into bugtracker from this forum and malfunctioning site database.
If it does not, then be it so.