Nitro Screencast: Web 2.0, Flickr ignited


#1

Dear devs,

as the first two videos were well received, I decided to make on more:

http://www.nitrohq.com/videos/nitro4.html

This time some sophisticated Web2.0 features of the Nitro framework
are demonstrated. The demo is based on the concept of a similar Rails
screencast (the flickr video). However, please note:

  • no generator is used.
  • ajax code and templates are cleanly separated.
  • standard html tags are naturally extended to support client side
    actions using
    Nitro’s powerful morphing technology.
  • Draggable and autocomplete effects as well as the programmatic render
    are also demonstrated.

This is a simple demo, and does not demonstrate the full power of
Nitro. To feel the magic give it a try yourself:

gem install nitro

For more information browse: www.nitrohq.com or join the Nitro mailing
list.

enjoy,
George.


#2

Hi George,

On 28/12/05, George M. removed_email_address@domain.invalid wrote:

as the first two videos were well received, I decided to make on more:

http://www.nitrohq.com/videos/nitro4.html

As a suggestion for future video’s how about copy & pasting chunks of
pre-prepared code? I know it looks more authentic to see you type it
out but I found it quite frustrating watching the code appear
one-character-at-a-oops-typo-delete-delete-pause-time and gave up
watching.

I would much rather see a block of code appear, pause for a few
seconds while I digest it, then move on to see what it does. Pause
and forward/backward controls here would help.

Regards,

Matt


#3

As a suggestion for future video’s how about copy & pasting chunks of

watching.

You are right, I will improve on this aspect in the future. I will
also use a proper editor
with autocomplete to improve thigs… However I hope you made it to
the end (where the really nice things happen ;-))

seconds while I digest it, then move on to see what it does. Pause
and forward/backward controls here would help.

If you view the video with firefox you can see a slider and a pause
button.

George.


#4

the for attribute is ‘morphed’ at compile time…

the #{…} interpolates the value of the standard src attribute at run
time
(this is similar to <%= … %> in fact you can use <% … %> in Nitro as
well…

-g.


#5

Another interesting screencast. I don’t mind the format so much,
however the controls you mentioned on Firefox are not visible. I can
see the hint of some sort of controls at the bottom of the screencast,
but they are obscured (I am running Windows XP, btw).

Anyways, feedback on Nitro from what I see here. I really like the way
XHTML attributes connect naturally to the controller code. However, one
thing did strike me as odd:

The way the “for” attribute and the “src” attribute are used seems
inconsistent, especially because “src” uses “embedded” ruby while the
other seems to be specially parsed. I haven’t used the framework,only
seen these screencasts, so take that for what it’s worth. Thanks for
making these available!