Re: [whatwg] fxCanvas 0.2 and some remarks about canvas spec

2010-11-15 Thread Samuel Ytterbrink
hmm... Can you explain the path-object more in detail. It sounds
interesting... but why shouldn't i just create a function that takes a
context and do the same path commands on it instead of having a context
taking a path object?

/Samuel Ytterbrink

2010/11/13 Evgeny Burzak buzz...@gmail.com

 Hi,
 I have just published new Canvas stub for IE (based on flash).  I'm
 using it in another my project - Drawform, to make it working under
 IE.
 Drawform: http://burzak.com/proj/drawform/
 fxCanvas: http://burzak.com/proj/fxcanvas/

 So I have some remarks about Canvas spec.

 I faced some troubles when using default image data, because of in old
 Explorers used extremely ineffective memory manager, so that  I made
 some tests and figure out that fastest and less memory consumption is
 array with pixel colors encoded in 32-bit integer. Here is the test:
 http://burzak.com/proj/fxcanvas/tests/data-structure-comparison.html

 But , the test results looks  similar for all vendors! On average the
 difference in processing speed is about 2-3 times (five times in
 Firefox 4). This is due to the fact that loops take less time (width x
 height * 4 vs. width x height) and arrays with less elements take less
 memory.  Though I realize that main idea for data structure was
 simplicity, but in this case it seems simplicity is evil, not good.

 Another thing is reusable canvas path.  I've added experimental class
 CanvasPath and and some related methods to Canvas context.
 For example:
 var p = new CanvasPath() // I think first argument can be string from
 SVG d attribute
 p.moveTo(0, 0)
 p.lineTo(10, 20)
 ctx.beginPath()
 ctx.appendPath(p)
 ... and so on. If you are interested in it, I can describe my idea
 futher...
 This is quite useful thing, at least for me.

 Evgeny



Re: [whatwg] Inline Web Worker

2010-10-16 Thread Samuel Ytterbrink
Good news. :D

But then i got another problem, why is not
file:///some_directory_where_the_html_are/ not the same domain as
file:///some_directory_where_the_html_are/child_directory_with_ajax_stuff/.
I understand if it was not okay to go closer to root when ajax,
file:///where_all_secrete_stuff_are/ or /../../.

You see i wonder why i need a web-server to try some things. And I'm sure
that there are more developers than me that thinks that local single page
Ajaxs applications have a  future. One thing that could probably solve this
is if the File API will support folders. Then the user could select the
files for the program...

/Samuel Ytterbrink

2010/10/16 Simon Pieters sim...@opera.com

 On Sat, 16 Oct 2010 03:12:38 +0200, Jonas Sicking jo...@sicking.cc
 wrote:

  Allowing both blob URLs and data URLs for workers sounds like a great
 idea.


 FWIW, Opera supports data URLs for Worker (but not SharedWorker since it
 could be used to cross the same-origin policy if two pages opened a
 SharedWorker with the same data URL -- this could be solved while still
 supporting data URLs but we decided to just drop it for now).

 --
 Simon Pieters
 Opera Software



[whatwg] Inline Web Worker

2010-10-15 Thread Samuel Ytterbrink
Hi I have found something really frustrating with the specs. to show that I
at least read the blog about proposing features here is the questions and
answers:

*What is the problem you are trying to solve?*
To create sophisticated single file webpages.
*What is the feature you are suggesting to help solve it?*
Some sort of inline Web Worker. Using Data URL is what i have in mind or by
creating a class.
*What is the processing model for that feature, including error handling?
This should be very clear, including things such as event timing if the
feature involves events, how to create graphs representing the data in the
case of semantic proposals, etc.*
Well the same as for other URLs, except that it inherit its location
information from its creator.
*Why do you think browsers would implement this feature?*
To make standalone local webpages easier to be used by users. And in some
cases faster dl of large pages.
*Why do you think authors would use this feature?*
Webpages are more then just information, its programs. Programs in one file
is easier to have. And also for testing quick things, inline is a Bliss.
*What evidence is there that this feature is desparately needed?*
I only have my own, trying to build a more optimal standalone DAISY player
(would be nice if i could rewrite it with web workers). And that google
gears seems to support it.


So is this a totally bad idea?

//Samuel Ytterbrink

p.s. hope i posted it in the correct Mailing list. and that my spelling
isn't that bad.