Thanks for the link. That guy's done a lot of work on his canvas library, but it seems like overkill to me. After all you're recreating a widget library, which you already get for free with HTML, not to mention the endless HTML/CSS/Javascript components available on the web. Redoing everything on the canvas seems like a lot of work to me!
Besides, my approach of manipulating the DOM does not preclude inserting a canvas and manipulating it via Javascript sent over from the server - so it's a more general approach. Does anyone know of any libraries that already assist you in doing this? I am really surprised that there's nothing (mature) which fills this niche. It's sort of like meteor <http://www.meteor.com/> and derby<http://derbyjs.com/>, but those seem to be more fully-fledged web frameworks optimized for production websites, not for local rapid (inelegant) development. On Friday, 18 October 2013 12:07:14 UTC+2, ajlopez wrote: > > Hi! > > Loosely related, the other day I found: > > http://www.codeproject.com/Articles/410856/Canvas-Control-Library-and-New-Forms-Based-System > https://github.com/akshaysrin/CanvasControlLibrary > > > On Fri, Oct 18, 2013 at 4:18 AM, Eric Reynolds > <eric.remo...@gmail.com<javascript:> > > wrote: > >> That sounds great, I am just wondering though, that would require you to >> redevelop a library of widgets to be able to set up a GUI, so why not use >> HTML? >> >> How do you do the code caching and hot fixing? Have you packaged your >> code into a module on npm? >> >> Eric. >> >> >> On Thursday, 17 October 2013 18:53:25 UTC+2, David Goehrig wrote: >> >>> I do something similar, but rather than the DOM, I use canvas and the >>> only bit of frontend is the code to open the websocket and compile and run >>> each drawing function sent by the server. Once a drawing function is >>> compiled on the client side, it is cached and reused. All image, sound, >>> and video assets cache by the browser normally. >>> >>> Works beautifully, and even allows for upgrading the user experience >>> (bug fix) on the fly w/o reloading. >>> >>> Dave >>> >>> -=-=- da...@nexttolast.com -=-=- >>> >>> On Oct 17, 2013, at 9:45 AM, Eric Reynolds <eric.remo...@gmail.com> >>> wrote: >>> >>> In the last few days I have been experimenting with a new project I have >>> called browsy <https://npmjs.org/package/browsy>. I am posting here >>> because, being a node.js novice, I'd like to find out whether my idea is >>> wrong, and why, or if actually it would generate some interest. >>> >>> So the concept is: *rather than writing client and server code, the >>> server contains all the logic and it directly manipulates the client DOM >>> using low-level constructs over socket.io*. >>> >>> The disadvantage of this is performance. The big advantage is ease of >>> development - when you write an app it feels like it's a stand-alone >>> desktop app with multiple windows (instead of 'clients'). The target use >>> case is where (a) there's a fast connection between the server and the >>> client, say a LAN (b) you don't have a bajillion users and (c) you want to >>> get it working really really quickly. So something like basic multi-user >>> office automation, for example, or quick development of GUI interfaces for >>> a server app. >>> >>> An initial version of the library is available on >>> npm<https://npmjs.org/package/browsy>, >>> it's already got enough functionality to build a simple chat application >>> (see the package readme <https://npmjs.org/package/browsy#readme> for a >>> tutorial). >>> >>> I'd really appreciate any feedback! >>> >>> -- >>> -- >>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-* >>> *Posting-Guidelines<https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines> >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To post to this group, send email to nod...@googlegroups.com >>> >>> To unsubscribe from this group, send email to >>> nodejs+un...@**googlegroups.com >>> >>> For more options, visit this group at >>> http://groups.google.com/**group/nodejs?hl=en?hl=en<http://groups.google.com/group/nodejs?hl=en?hl=en> >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to nodejs+un...@**googlegroups.com. >>> >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nod...@googlegroups.com<javascript:> >> To unsubscribe from this group, send email to >> nodejs+un...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+un...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.