After DevMeeting

DevMeeting is after us, and only thing I can say after it is "more". Meeting started at 9 a.m. and we worked with short breaks till 9 p.m. Whole meeting was leaded by David de Rosier and I must say that I have been under deep impression how big and broad knowledge he has.

We started with JavaScript refreshing - quick review of JavaScript magick. As a exercise we got task to implement elements of Aspect Programming in JavaScript.

Next we jumped to NodeJS and I must say that this was the most interesting part of whole meeting. His callback approach provide really powerful way for creating server-side code. After theoretical part we started implementation of chat - part of online code editor that was ours goal on this meeting. It was rally amazing to see that the same library (Socket.IO) is used on client and server side, JSON is transparent for both sides and all was running in less than 15 minutes.

As last element we explore RingoJS - MVC Server framework. It wasn't impressive - yet another framework. Only interesting thing in it is possibility of Java libraries usage. But there is no "magic" that NodeJS is offering and there is a lot of much better frameworks around in any other language.

Whole meeting was really successful, it has given me wider look on server side JavaScript, and I am definitely recommending it any one who want to learn something interesting.

Pre DevMeeting

On 14 May in Poznan there will be interesting meeting (with I hope to take part) about RingoJS, V8cgi and NodeJS. I am still confused with "server side JavaScript" concept and I hope to clarify my point of view after this meeting. Meanwhile I strongly recommend two videos where Ryan Dahl is explaining why he has created NodeJS, it general architecture and for what and where NodeJS can be used.

JavaScriptMVC and

My another friend has asked my to update his portfolio. And again I have chosen JavaScriptMVC as client side framework. I think that final effect is more than good. If you want to check it, visit I strongly recommend to check also Piotr private gallery under

JavaScript prototyping shortest explanation

  2. // Without prototyping
  4. function Foo() {
  5. = function(){
  6. }
  7. }
  9. var f1 = new Foo()
  10. var f2 = new Foo()
  11. == // FALSE
  13. // With prototyping:
  15. function Bar(){
  16. }
  18. = function(){
  19. }
  21. var b1 = new Bar()
  22. var b2 = new Bar()
  23. == // TRUE

JavaScriptMVC – simplified client side

Recently my friend ask me, to rewrite his home page with additional CMS functionality. Because there wasn't any interesting thing in backend i choose simplest (and quite ugly) PHP framework CodeIginiter with some modifications made by me to increase its usability.

So nothing exciting, but still, I wanted to play with something new so I chose something that i wanted to test for some time: JavaScriptMVC framework.

JavaScriptMVC, as you probably guess, is MVC framework for fronted web app development. It use JQuery as a base engine, provide nice separation of layers in your app, bunch of plugins that simplify your every day developer works (like History plugin) and test engine. Command line tools helps you to generate required elements and compress your app to one file. Looks good, isn't it?

And how looks work with framework? Beginning is quite hard - documentation is quite good but there is not too much about plugins in it. But active mailing list group react very fast and helps with problems. Working with framework is very smooth, code is nicely separated and its easy to maintenance it. Usage of OpenAjax allows to create components that will communicate with each other by publishing messages - so no tight code coupling. JSMVC provide also powerfull documentation engine (home page of version 2.0 was generated by it) so we can create spec. for ours app in the fly.

In my opinion, this framework is irreplaceable for any app that use more JS in the frontend than simple usage of lightbox.

O3D – the future is near

On one of my interviews I have had question "which programing language will be the most important in future". My answer was ActionScript, but at this moment, knowing what google have in they backyard I say: JavaScript. Why? My answer is O3D:

O3D is an open-source JavaScript API for creating interactive 3D graphics applications that run in a browser window: games, ads, 3D model viewers, product demos, virtual worlds.

Yes, they preparing engine that allow to create whole 3d realms. All you need, is to download plug-in and we could create 3d environment in pure JavaScript.

The O3D JavaScript application code is completely contained in an HTML document that is loaded into a web browser. To develop a O3D application, all you need is the O3D plug-in and a text editor for writing JavaScript code.

Sounds great, isn't it?

Powered by WordPress with GimpStyle Theme design by Horacio Bella.
Entries and comments feeds. Valid XHTML and CSS.