Mariusz, After reviewing your readme, webmake looks pretty nice!
One idea, if you made your API signature use function (require, exports, module) then it would be compatible with AMD's commonjs signature, and there could be some nice ways to integrate with AMD modules and tools. Just something to consider. I like the elegance of your approach, seems to really make things easy. I will have to give it a try soon. All the best, Jeff On Monday, 13 August 2012 05:36:38 UTC-5, Mariusz Nowak wrote: > > See also https://github.com/medikoo/modules-webmake the idea is to use > same module "format" on server and client side, so you can easily share > same code on both sides. > I use it with success. Currently I work with application for which > client-side code is built of over 200 Node.js style modules and 60% of > those modules are also used on server-side. > > -- > Mariusz Nowak > http://github.com/medikoo > http://twitter.com/medikoo > > On Saturday, June 2, 2012 3:20:29 PM UTC+2, al-Amjad Tawfiq Isstaif wrote: >> >> Thank you very much everybody for your notes! >> >> @Martin >> I tried to have a fast look at YUI. What gives YUI the ability to run >> client code on the server? I mean what makes it different from other >> Javascript "MVC" frameworks such as Backbone.js? >> >> >> >> On Thu, May 31, 2012 at 6:43 AM, Martin Cooper <[email protected]> wrote: >> >>> On Wed, May 30, 2012 at 4:58 AM, Amjad <[email protected]> wrote: >>> > Hello everybody! >>> > >>> > I'm new to the great world of Node.js and have been playing around with >>> > different modules and frameworks. However, there seems a lot of >>> methods for >>> > sharing server code with the client, and there are no default way for >>> doing >>> > that. >>> >>> That's in part because it rather depends on what you're trying to do. >>> For example, you might be: >>> >>> * trying to take existing code written for Node and run it in the browser >>> * trying to take existing code written for the browser and run it in Node >>> * trying to write a new codebase that will run in both places >>> >>> As has been mentioned, browserify is probably the best solution for >>> the first of these. I think it's safe to say that it garners the most >>> attention, in part because it's good at what it does. >>> >>> For the last case, you might want to take a look at YUI, which >>> provides the abstractions to let you write your code once and run it >>> in both places. Yahoo! has built Mojito on top of YUI and is using >>> that to create multi-device apps that transparently share code between >>> client and server. (BTW, you'll likely find that YUI is much more >>> lightweight and modular than you think.) >>> >>> -- >>> Martin Cooper >>> >>> >>> > I have come across many ideas: >>> > >>> > express-expose: this is a nice replacement for parsing JSON objects >>> rendered >>> > by the the server. >>> > https://github.com/visionmedia/express-expose >>> > >>> > This article exposes a hack to share backbone models on the Node >>> server, and >>> > they are trying to neat their hack with their Capsule and Thoonk >>> frameworks: >>> > >>> http://andyet.net/blog/2011/feb/15/re-using-backbonejs-models-on-the-server-with-node/ >>> > >>> > Syncrhonizing Backbone model using socket.io >>> > https://github.com/scttnlsn/backbone.io >>> > >>> > DNode and RPC as a method to use server methods on the client and vice >>> versa >>> > https://github.com/substack/dnode >>> > >>> > I know I've mixed a lot of topics, I thought sharing my confusion >>> would help >>> > to get more clarification, especially that there are a lot of >>> production >>> > projects based on Node, andI think that the community certainly have >>> reached >>> > a good collection of concepts and tools for sharing code between the >>> server >>> > and client. I would be very grateful for sharing your thoughts about >>> that. >>> > >>> > Best regards, >>> > >>> > Amjad >>> > >>> > >>> > -- >>> > 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 [email protected] >>> > To unsubscribe from this group, send email to >>> > [email protected] >>> > For more options, visit this group at >>> > http://groups.google.com/group/nodejs?hl=en?hl=en >>> >>> -- >>> 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 [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en?hl=en >>> >> >> -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
