nitro-devel

This group looks dead but I thought I'd ask anyways. How do I perform an http get request?

I just added a new, useful feature in normal-template. From the updated docs (http://www.nitrojs.org/

I'm developing fine using windows. The nitro blog example that uses app.yaml is all I needed to

So to get it right. The goal of Nitro is to leverage the power of Ringo in favor of Standards,

Yes that fixed the problem. Thanks. On Sun, Jul 4, 2010 at 2:24 AM, George Moschovitis <george-

thanks, that helped. On Mar 30, 4:15 am, George Moschovitis <george-moschovi...@gmosx.com>

hmm the '.' in .well-known is problematic. -g. On Mon, Mar 22, 2010 at 8:00 PM, Roberto

you should serve: /example.xml the default extension is .html so /example is really /example.html if

pnewhook wrote: > I turned on debugging and I noticed that pkg[undefined] gets printed > out a

In the next update I will include GAE users functionality (author), the feed and will fix the

OK, I added the change... Perhaps we need better default paths, perhaps: 4xx.html 5xx.html will have

I haven't added the atom feed in the new example. will add it and update the code. thanks for

ah, great, now I see that everything needed is actually there already ! thanks a lot -- Roberto On

that works great, thanks -- Roberto On Feb 12, 3:55 pm, George Moschovitis <george-moschovi...@

I pushed a patch that makes normal-template the default template engine for Nitro. Moreover, Render

ah, wait for the next push, you will have to provide a custom template manager that loads from db...

I have the changes integrated, but I haven't updated the blog example yet (and some docs). I

I am thinking about allowing for custom 'commands'/'tags' like the custom filters. If

OK I added a minimal example to the appengine repo. A plain and simple guestbook. In the README you

Some more tips: The Render middleware works in tandem with the Dispatcher middleware: request path: /

The Nitro ecosystem has a new member: http://github.com/gmosx/htmlparser an HTML parser compatible

<property environment="env"/> <property name="sdk.dir" location="${

I think they the images after transformation are to be stored in the datastore, and because this only

the forthcoming 1.2.8 api will automatically execute tasks in the dev server. -g. On Thu, Dec 3, 2009

George, thanks, with that trick it works. -- Roberto On Nov 25, 3:19 pm, George Moschovitis <

Hmm I haven't tackled this yet... At some point I will implement a more sophisticated 'upload

On Wed, Nov 11, 2009 at 7:37 PM, pnewhook <peter....@gmail.com> wrote: > > Should

I am only testing nitro / appengine with the patched versions, so it is better to use those. the

Great, I like the db API much more now. Nice, if you have an idea how to better emulate the Python

thanks, now things make a bit more sense and will wait for the updated example On Oct 25, 11:03 am,