Nitro on SWiK

Curl, Inc. - Richer Internet Applications

Wed, 13 Aug 2008 14:05:05 -0700

Curl Nitro Demo Application Visualizes Facebook Social Graphs @ AJAX & RIA JOURNAL

Tue, 24 Jun 2008 01:05:27 -0700

[from bushwald] Curl Nitro Demo Application Visualizes Facebook Social Graphs @ AJAX & RIA JOURNAL

Tue, 24 Jun 2008 01:05:13 -0700

Application Development Trends - Curl Announces RIA Dev Tools Beta for Eclipse

Fri, 13 Jun 2008 12:19:40 -0700

By combining the highest-performing enterprise RIA platform, Curl, with the best general-purpose IDE, Eclipse, we are giving programmers with an updated set of development tools,

Internet Evolution - Richard Monson-Haefel - The Return of Client/Server Architecture

Fri, 13 Jun 2008 11:20:57 -0700

Today, the use of rich Internet application (RIA) technologies is planting the seeds for a return to client/server architectures where large clients are installed on the desktop.

The Universal Desktop - The ever-changing definition of RIAs and how people are killing it

Mon, 21 Apr 2008 07:25:12 -0700

Ryan Stewart react to eWeek's "RIA War is Brewing" article

Happy Birthday Oxyliquit!

Wed, 27 Feb 2008 12:46:37 -0800

It now has been 2 years since Oxyliquit first breathed the air.

Oxyliquit has been the idea of a community platform, however - the diminishing positive response in large attributable to the withering of Nitro and Og support in general leaves me with one laughing and one crying eye.

As this is a completely community driven application, it lives and dies with its community.

That said, I still think Oxyliquit is a good source for Nitro, so it will stay as long as there are still interested people browsing through it, it might however reopen in a slightly different form.

I thank everyone who has ever contributed to Oxyliquit in any way. Thank you.

Nitro and Og

Fri, 04 Jan 2008 07:16:48 -0800

RSCDS

Fri, 30 Nov 2007 10:21:34 -0800

I'm terribly sorry for showing this RSCDS page the whole week. I do not plan to discontinue serving the Nitro Q&A system anytime soon.

I apologize again for the inconvenience.

Jonathan Buch

Element content

Fri, 30 Nov 2007 10:21:34 -0800

The Nitro concept of elements is terribly flexible. Whatever you put inside the elements tag is available through the content method. You could for instance parse this as YAML and take it as configuration for how the element should render.

variant: big background: #3f7 no-footer: true

class SomeElement def render opt = YAML::load(content) if opt['variant'] == 'big' ... end end

$KCODE="UTF8"

Fri, 30 Nov 2007 10:21:34 -0800

If you're using any characters beside those uses in 7-bit ASCII you'll have to think about character encodings. The easiest thing nowadays is usually to make every subsystem use UTF-8. To make Ruby use UT8 add $KCODE="UTF8" to app.rb. Make sure to add it all the way at the top, before loading Nitro. Then "charset=utf-8" will be added to the headers of a html response. If you set $KCODE after requiring Nitro this does not work!

Sinatra - Lightweight Ruby web framework

Sat, 17 Nov 2007 16:29:53 -0800

Running Nitro with FastCGI and Lighttpd

Fri, 19 Oct 2007 09:14:20 -0700

I'm assuming you've installed Lighttpd with the package manager of your distribution of choice. Next you need to enable the fastcgi module.

If you're using Debian or a variant (like Ubuntu) you can use the lighty-enable-mod script:

lighty-enable-mod fastcgi

This will create a symlink from /etc/lighttpd/conf-available/10-fastcgi.conf to /etc/lighttpd/conf-enabled/10-fastcgi.conf. Open this file in your editor. If this doesn't work for you simply edit the main configuration file /etc/lighttpd/lighttpd.conf.

To enable the module you need this line:

server.modules = ( "mod_fastcgi" )

If you find any fastcgi.server portions in the configuration comment them out, we won't be needing them. Now add a fresh portion: fastcgi.server = ("" => (( "bin-path" => "/path/to/app.rb", "socket" => "/tmp/nitro.socket", "check-local" => "disable", "max-procs" => 1, "bin-environment" => ("RUBYOPT" => "-rubygems -I/path/nitro_repo/script -rlib/glycerin") )) )

Issue

sudo /etc/init.d/lighttpd force-reload

and you should be all set. Keep an eye on /var/log/lighttpd/error.log in case stuff doesn't work right.

Adapt bin-environment to whatever is necessary on your site to get nitro running. I'm assuming you're using the repo version. Otherwise a simply "-rubygems" might suffice.

Installing Nitro on Windows in 11 steps

Fri, 05 Oct 2007 15:06:23 -0700

Assuming that you've already installed Ruby and MySQL on your system

1) Download Darcs from www.darcs.net and decompress it in any directory

2*) Add the darcs root folder in the PATH environmental variable (i.e. C:\Darcs;)

3) Download the latest Nitro version from the repository through darcs by: going to the directory you want to store nitro and typing in command line: darcs get --partial http://repo.nitroproject.org nitro

4) Find the RUBYOPTS environmental variable (it should already contain -rubygems in it and after it add the following:

-I(NITRO)\nitro\lib -I(NITRO)\nitro\vendor -I(NITRO)\og\lib -I(NITRO)\glue\lib -I(NITRO)\raw\lib

replace (NITRO) with the path to your nitro folder (example: C:\nitro). Note that -I is Capital i, and not lowercase L.

5) Add the same directories in the PATH environmental variable as well (ex. C:\nitro\nitro\lib;C:\nitro\nitro\vendor;C:\nitro\og\lib;C:\nitro\glue\lib;C:\nitro\raw\lib)

6) Go to the Nitro root directory and type: darcs pull and select "yes" to all patch prompts

7) Install the "facets" gem (gem install facets)

8) Install the "redcloth" gem (gem install redcloth)

9) Install the "xmlSimple" gem (gem install xml-simple)

10) Install the "mysql" gem (gem install mysql) [Select option 1]

11) Install the "uuidtools" gem (gem install uuidtools)

In order to get to your system's environmental variables, right click on your "My Computer" icon and select Properties. Select the Advanced Tab and on the bottom click on the Environmental Variables button.

Apache 2.0/2.2 Reverse Proxy

Wed, 03 Oct 2007 06:59:08 -0700

h2. Configuration

# # Using Apache 2.0 and 2.2 as a reverse proxy # for a Nitro application. # # Note that Apache 2.2 offers a load balancing # proxy. Oxyliquit tutorial forthcoming... # # This scheme is based on Apache's NameVirtualHost # feature. The following line should appear # in your httpd.conf file: # # NameVirtualHost *:80 # # Next, add the following. # # You *could* put this directly in httpd.conf. # # But with large numbers of virtual hosts, # it makes sense to have an include directory # under your_apache_install/conf and add this # to httpd.conf: # # Include conf/vhosts/* # # or # # Include conf/vhosts/foo.com # Include conf/vhosts/bar.com # ServerName myhost.com ServerAlias www.myhost.com ServerAlias myalias.net ServerAlias www.myalias.net RewriteEngine On ProxyRequests off ProxyPass / http://127.0.0.1:9001/ ProxyPassReverse / http://127.0.0.1:9001/ ProxyPreserveHost on # If your application exposes administrative URLs that # you want to protect, then you can redirect to an ssl # port on the server. RewriteRule ^/admin(.*) https://admin.myhost.com/admin$1 [L,R] RewriteRule ^/(.*) http://127.0.0.1:9001/$1 [L,P] # # If you want an SSL port for secure URLs for your app, # create an additional vhost # # Again, remember to add this somewhere before it: # # NameVirtualHost *:443 # ServerName admin.myhost.com ServerAlias topsecret.myhost.com ProxyRequests off ProxyPass / http://127.0.0.1:9001/ ProxyPassReverse / http://127.0.0.1:9001/ ProxyPreserveHost on AuthName "Restricted Access" AuthType Basic Require user YoursTruly AuthUserFile /top/secret/path/htpasswd AuthName "Restricted Access" AuthType Basic Require group SiteEditors AuthUserFile /top/secret/path/htpasswd SSLEngine on SSLCipherSuite ALL:!ADH:!EXPORT56:RC4 RSA: HIGH: MEDIUM: LOW: SSLv2: EXP: eNULL SSLCertificateFile /path-to-cert-files/ssl.crt/self_signed.cert SSLCertificateKeyFile /path-to-cert-files/ssl.key/self_signed.key SSLOptions FakeBasicAuth ExportCertData CompatEnvVars StrictRequire

Stop HTML markup from being stripped from Og text fields

Mon, 01 Oct 2007 14:10:21 -0700

Is there a simple way to get the Og admin part to stop stripping HTML markup from submitted text fields?

Nitro and Og

Fri, 28 Sep 2007 14:03:08 -0700

How to switch session stores?

Mon, 10 Sep 2007 19:13:15 -0700

By default cookie session store is used in Nitro pre-0.50

The line in application.rb that does this is

@session_store ||= Raw::CookieSessionStore.new

In my app setup I tried this:

require 'raw/context/session/memory'

app.session_store = Raw::MemorySessionStore.new

The problem with that is the 'require' looks like it digs a little deeper into the Raw framework than it should. Shouldn't there be a simpler way to do this?

thx.

Testing Nitro

Sat, 01 Sep 2007 02:26:55 -0700

For external tests using WWW::Mechanize might be just what you need. It's really good at 'emulating' a browser. Testing like that makes you work on your actual HTML output to produce good easy html, so it can be easily screen-scraped.

I really liked it, it doesn't take too much work to recreate a 'browser visit'. Another benefit is, it makes sure your app also works with 'web 1.0' type browsers, not having Javascript.

If you have big tests though, take into account that Mechanize is very ressource hungry and eats your RAM alive.

News! (alive!)

Sat, 04 Aug 2007 18:54:21 -0700

The head of this side is going for a vacation for a week, and I use the brief time before that to make a little more news:

Nitro 0.49 (beta release before 0.50) will be coming out after Facets 2.0
That release will have many Nitro improvements as well as a much better testing structure due to RSpec.

I thank the many visitors of this page, which despite the site not having recieved much content in the last few decades keep coming back. I bow before the community, thanks to you I'm alive.

So, if you are one of those coming back often (you know who you are) looking for content: if you have an idea what that content should be, why don't you just ask for it? :) (me don't bite. promis. will work for food!)

Your neighbourhood Oxywtf admin.

Legacy Databases / Schema

Mon, 21 May 2007 09:06:03 -0700

What do i need to do to tell Og to be careful with pre-existing ('legacy') databases, so that: 1) the schema does not get changed 2) no columns / rows / tables get dropped

Can Og determine the schema of a given MySQL Database, and automatically create a skeleton of matching Class definitions? (without relations ..)

Such a reverse engineered mode would be good for people who want to use a legacy database with Og

Using id instead of oid / ActiveRecord backwards-compatiblity

Sun, 20 May 2007 14:05:26 -0700

I need to stay backwards-compatible to ActiveRecord..

How can I use 'id' instead of 'oid' in MySQL Tables created by Og?

What other gotcha's do I need to be aware of?

thanks

how are multi-threads handled in Og

Tue, 15 May 2007 07:01:18 -0700

Is Og using connection-pool to database or single connection ?

Validators for Og

Mon, 14 May 2007 09:01:56 -0700

I was wondering if there are validators for Og, similar to activerecords validation.

Nitro and Og

Sat, 12 May 2007 06:54:38 -0700

How use Annotation?

Mon, 15 Jan 2007 11:05:37 -0800

Hi, I have seen this into the "nitro real example"

def index #... end ann :index, :title => 'All categories'

but I don't understand how use it. Is it correlated with the helper :sitemap? Where I find a small example?

Thanks

LoxAuth

Sat, 06 Jan 2007 15:57:18 -0800

LoxAuth

LoxAuth is a dropin solution for basic authentication for Nitro apps. Can be used to login your users as well as registering them. It's customizable by settings if you need registering for example, since this is deactivated by default.

Requirements

Nitro 0.40.0
Og 0.40.0

May work with other versions with small adjustments

USAGE:

in your run.rb:

require 'part/auth' Nitro::Server.map['/auth'] = AuthController

before your controllers and models!

in your Controller

class MainController [:edit, :add] # This action is now protected. When someone tries to # go to /edit while not being logged in, he will be # redirected to a login screen and after having logged # in he will be redirected to `edit` again. # The same happens with `add` and any other protected # action. def edit(id) # do something end end

Part Auth has its own User model, if it's not sufficient for you, just extend it by monkey patching. Currently the User has the properties :name, :email and :password, so if you need it to have an additional age do the following in your own User model:

class User property :age, Integer end

Same goes for relations:

class User has_many :articles, Article end

If your application defines a Page skin class (Element) it'll integrate nicely into your Page design.

Configuration

To enable Registering:

LoxAuthPart.register_enabled = true LoxAuthPart.register_welcome_msg = "Successfully registered. You're logged in now!"

To disable Roles:

LoxAuthPart.roles_enabled = false

Adapting LoxAuth

Apart from adding additional properties to User or Role you can also modify how it looks.

Copy the xhtml templates from the LoxAuth template folder to auth/ (subfolder of your template folder, standard is template, modifyable by the setting Nitro::Template.root = 'template').

Having the .xhtml now in yout template/auth folder, you can modify them just like all your other templates.

Contributors

Fabian Buch (fabian@fabian-buch.de)
Jonathan Buch (john@oxyliquit.de)

Samples/Examples for 0.41.0

Sat, 06 Jan 2007 15:57:18 -0800

Which versions of flare/spark are supposed to work with the latest nitro release (0.41.0)? And where is examples-0.41.0?

Part Guideline

Mon, 04 Dec 2006 12:44:30 -0800

In other systems you'd maybe call them Plug-ins, but in Nitro they are called "parts". These parts can be dropped into your Nitro Web-Application and extend your Application with fully functional app parts. You could for example add a Blog to your current Application by adding a Blog Part.

This guideline will show you how to make a Nitro Part at a kinda general example. It uses "partname" or PartName as the name of your Part, so you'd typically replace that with the actual name of your Part.

Directory Layout

The directory layout of a typical Nitro Part looks as follows.

part/partname.rb part/partname/ part/partname/controller/ part/partname/helper/ part/partname/model/ part/partname/public/ part/partname/template/

Helper, model and public directory are optional of course, if your Part doesn't need them.

It's recommended to use this layout for all parts, even if Nitro's layouts can be done in any way the developer chooses, it'll be easier to integrate your part in other applications, especially utilizing "gen part".

partname.rb

This is the main file of your part, kinda the equivalent of the run.rb of typical Nitro apps. Parts usually don't have a run.rb.

Require everything your part needs in here. Try to avoid requireing in other files (like your models and controllers). Take into account that a part will be required as follows in a random app:

require 'part/partname'

So requireing controllers, models of your part in your partname.rb:

require 'part/partname/helper/something' require 'part/partname/model/user' require 'part/partname/model/article' require 'part/partname/controller/main'

Additionally this file is for a standard Nitro::Server.map, even though this will probably be overridden by a Nitro app.

PartnamePart class

Usually directly in partname.rb too, there can be a PartnamePart class, which you can use for various settings you can use later on in your Part. Thistime my example is of a BlogPart:

class PartnamePart setting :title, :default => "Lox Blog" setting :subtitle, :default => "My life with Lox" setting :entries_per_page, :default => 10 setting :trackback, :default => false # Trackback can lead to lots of spam setting :tags, :default => true setting :categories, :default => true setting :version, :default => '0.9.0' setting :public_root, :default => '/part/partname' setting :charset, :default => 'utf-8' end

All these settings are optional of course. But if you incorporate stylesheets or pictures in your Part, using the public/ directory, you should probably set "setting :publicroot" to '/part/partname', since that's the directory "gen part" is creating for you in a random Nitro app, so you can use "PartnamePart.publicroot" for links and such in your Part.

Controller

Every controller of a Part should have the following method, so that the right templates are found:

def self.setup_template_root(path) super @template_root



Share

After you created a nice Part, think about sharing it with others on LoxParts.



nitro form
Mon, 04 Dec 2006 12:44:30 -0800
I was trying out tutotial from nitroproject.org with Nitro 0.4. In that tutorial, there is one form, to search for Users. User has three properties: name,description and age. In my xhtml page, to display current users, i wanted to add one form to search for users. so I added this line: #{formfor User.findby_name(@name)} and in controller I added helper :form, but it didnot work. The page doesnt display the form. It says undefined method 'formfor'. How can I solve this in Nitro 0.4?
Thanks