From george.moschovitis at gmail.com Wed Nov 1 01:16:59 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 08:16:59 +0200 Subject: [Nitro] SQLite working In-Reply-To: References: Message-ID: Can you please adapt to sqlite adapter to properly report that it requires why's version of the driver (if not driver is found?) thanks, George. On 10/31/06, Jonathan Buch wrote: > Hi, > > just tested SQLite after getting this: > > http://redhanded.hobix.com/cult/sqlite3Gem_whySSensibilitiesRepack.html > > Works flawless (except with my tc_evolution, which you don't have anyway). > > So, everyone who wants to use SQLite and Og, this is now tested and > should work for almost any case (don't use multiple stores). > > Have fun! > > Jo > > -- > Feel the love > http://pinkjuice.com/pics/ruby.png > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Wed Nov 1 01:20:32 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 08:20:32 +0200 Subject: [Nitro] Whitespace In-Reply-To: <45479706.3020300@lassoweb.se> References: <20061031102539.GA30141@oxyliquit.de> <3ff63f9b0610310436p6f0dff1bha2e45423da7bba9d@mail.gmail.com> <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> Message-ID: > No problem there. REXML already supports DOCTYPEs. The problem is that > Nitro strips the DOCTYPE *after* REXML has processed the template. Since > some XML tools require this type of information in order to function > they are unable to parse pages rendered by Nitro. This is *very* bad in > my opinion (luckily there are workarounds). can you (or someone else) provide a patch for this? -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Wed Nov 1 03:13:45 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 10:13:45 +0200 Subject: [Nitro] Dedicated Hosting Message-ID: Dear devs, I am looking for a dedicated server provider. Can anyone recomment a dedicated hosting service? thanks, George. -- http://www.gmosx.com http://www.nitroproject.org From wyhaines at gmail.com Wed Nov 1 04:52:46 2006 From: wyhaines at gmail.com (Kirk Haines) Date: Wed, 1 Nov 2006 02:52:46 -0700 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: On 11/1/06, George Moschovitis wrote: > Dear devs, > > I am looking for a dedicated server provider. Can anyone recomment a > dedicated hosting service? Depends on what you need. For a good and very inexpensive host for Europe-centered traffic, consider http://hetzner.de/rootserver_en.html Compare especially the DS5000 and DS7000 to US providers. Hetzner compares extremely well on price, even considering the less generous bandwidth allotments than the next two that I will suggest. For more US centered traffic, I use ServerBeach quite happily. They have a pretty good balance of price and service with a generous bandwidth allotment. If you won't need a bandwidth allotment that high, though, take a look at cari.net for an inexpense US centered provider with a lot of options and good support. Kirk Haines From fabian at fabian-buch.de Wed Nov 1 06:41:40 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Wed, 1 Nov 2006 12:41:40 +0100 Subject: [Nitro] SQLite working In-Reply-To: References: Message-ID: <2951B7CB-A9A8-469C-A0A4-7F65EB4149E9@fabian-buch.de> Am 01.11.2006 um 07:16 schrieb George Moschovitis > Can you please adapt to sqlite adapter to properly report that it > requires why's version of the driver (if not driver is found?) Not necessary. Just tested with normal sqlite driver, testcases run just as nice. So it's the users choice whether to use why's or the normal sqlite. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Wed Nov 1 07:15:37 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 14:15:37 +0200 Subject: [Nitro] SQLite working In-Reply-To: <2951B7CB-A9A8-469C-A0A4-7F65EB4149E9@fabian-buch.de> References: <2951B7CB-A9A8-469C-A0A4-7F65EB4149E9@fabian-buch.de> Message-ID: oh, great! ;-) On 11/1/06, Fabian Buch wrote: > > Am 01.11.2006 um 07:16 schrieb George Moschovitis > > Can you please adapt to sqlite adapter to properly report that it > > requires why's version of the driver (if not driver is found?) > > Not necessary. Just tested with normal sqlite driver, testcases run > just as nice. So it's the users choice whether to use why's or the > normal sqlite. > > Fabian > > > > > > -- > Nitro Q&A: http://oxyliquit.de/ > Blog: http://blog.fabian-buch.de > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From eduardorochabr at gmail.com Wed Nov 1 07:19:06 2006 From: eduardorochabr at gmail.com (Eduardo Rocha) Date: Wed, 1 Nov 2006 10:19:06 -0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: RailsPlayground.com :) 2006/11/1, George Moschovitis : > > Dear devs, > > I am looking for a dedicated server provider. Can anyone recomment a > dedicated hosting service? > > thanks, > George. > > -- > http://www.gmosx.com > http://www.nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061101/1d1fba7d/attachment.html From alexandru at globalterrasoft.ro Wed Nov 1 07:19:01 2006 From: alexandru at globalterrasoft.ro (Alexandru E. Ungur) Date: Wed, 1 Nov 2006 14:19:01 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: <20061101121901.GA19450@globalterrasoft.ro> >>> sender: "George Moschovitis" date: "Wed, Nov 01, 2006 at 10:13:45AM +0200" << Dear devs, > > I am looking for a dedicated server provider. Can anyone recomment a > dedicated hosting service? Hi, I have experience with FastServers.net, LayeredTech.com, 800hosting.com, Managed.com, Rackspace.com, ThePlanet.com, MaxNet.com and a few others. I had some really bad experience with some of them... like they were unable to setup the IPs/routing properly, nor were they able to debug the issue fast (as in: not even in a week). Once I was given the wrong server :) and they simply cut the access to it AND took them one whole week to figure out why I "lost" access to the server..... :) Oh well, I will not name the companies to avoid from those, maybe it's just my bad experience, I'll just tell you from all of them which one I'd recommend: FastServers by ***far***. Highly capable (and fast) tech support, decent prices. The only tech support that was as good was the one from Rackspace, but for much higher prices. Good luck, Alex From george.moschovitis at gmail.com Wed Nov 1 07:43:10 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 14:43:10 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: Thanks for the detailed email. I am looking for a server to host a high-traffic web site. (But I would like to see affordable options as well). Btw, can someone understand what the (mt) GridServer really is? Which linux distribution it supports and if I can compile and install my own software in the container? regards, George. On 11/1/06, Kirk Haines wrote: > On 11/1/06, George Moschovitis wrote: > > Dear devs, > > > > I am looking for a dedicated server provider. Can anyone recomment a > > dedicated hosting service? > > Depends on what you need. > > For a good and very inexpensive host for Europe-centered traffic, consider > > http://hetzner.de/rootserver_en.html > > Compare especially the DS5000 and DS7000 to US providers. Hetzner > compares extremely well on price, even considering the less generous > bandwidth allotments than the next two that I will suggest. > > For more US centered traffic, I use ServerBeach quite happily. They > have a pretty good balance of price and service with a generous > bandwidth allotment. > > If you won't need a bandwidth allotment that high, though, take a look > at cari.net for an inexpense US centered provider with a lot of > options and good support. > > > Kirk Haines > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Wed Nov 1 07:44:09 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 14:44:09 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: I would also like the server to support ubuntu (or at least debian). -g. On 11/1/06, George Moschovitis wrote: > Thanks for the detailed email. I am looking for a server to host a > high-traffic web site. (But I would like to see affordable options as > well). > > Btw, can someone understand what the (mt) GridServer really is? Which > linux distribution it supports and if I can compile and install my own > software in the container? > > regards, > George. > > On 11/1/06, Kirk Haines wrote: > > On 11/1/06, George Moschovitis wrote: > > > Dear devs, > > > > > > I am looking for a dedicated server provider. Can anyone recomment a > > > dedicated hosting service? > > > > Depends on what you need. > > > > For a good and very inexpensive host for Europe-centered traffic, consider > > > > http://hetzner.de/rootserver_en.html > > > > Compare especially the DS5000 and DS7000 to US providers. Hetzner > > compares extremely well on price, even considering the less generous > > bandwidth allotments than the next two that I will suggest. > > > > For more US centered traffic, I use ServerBeach quite happily. They > > have a pretty good balance of price and service with a generous > > bandwidth allotment. > > > > If you won't need a bandwidth allotment that high, though, take a look > > at cari.net for an inexpense US centered provider with a lot of > > options and good support. > > > > > > Kirk Haines > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > > -- > http://www.gmosx.com > http://www.nitroproject.org > -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Wed Nov 1 08:17:34 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 15:17:34 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: > RailsPlayground.com :) naah, I don't like the name :P -g. -- http://www.gmosx.com http://www.nitroproject.org From eduardorochabr at gmail.com Wed Nov 1 09:25:01 2006 From: eduardorochabr at gmail.com (Eduardo Rocha) Date: Wed, 1 Nov 2006 12:25:01 -0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: :) Well, it seems I was the only one not to justify my recommendation. Though I am a kind of newbie using dedicated hosting services, I was more than satisfied using RailsPlayground. The support is just amazing, I felt like it was personal. We got some issues solved and discussed like chating via email, very impressive, and they handled my urgent issues at a very special way. Besides, I gave a look around at other suggested hostings, and the hardware/price combination seems decent compared to them. 2006/11/1, George Moschovitis : > > > RailsPlayground.com :) > > naah, I don't like the name :P > > -g. > > -- > http://www.gmosx.com > http://www.nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061101/74fc15de/attachment-0001.html From ralph.amissah at gmail.com Wed Nov 1 10:05:40 2006 From: ralph.amissah at gmail.com (Ralph Amissah) Date: Wed, 1 Nov 2006 15:05:40 +0000 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: On 01/11/06, George Moschovitis wrote: > I would also like the server to support ubuntu (or at least debian). > > -g. > For a Debian base Black Cat (UK) have consistently been highly recommended over the years: http://www.blackcatnetworks.co.uk/ a discussion thread: http://www.chiark.greenend.org.uk/pipermail/debian-uk/2005-November/thread.html#10647 That said, more general information about available Debian hosting is available here: http://wiki.debian.org/DebianHosting Ralph Amissah From wyhaines at gmail.com Wed Nov 1 10:25:04 2006 From: wyhaines at gmail.com (Kirk Haines) Date: Wed, 1 Nov 2006 08:25:04 -0700 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: On 11/1/06, George Moschovitis wrote: > Thanks for the detailed email. I am looking for a server to host a > high-traffic web site. (But I would like to see affordable options as > well). Unless the extra 100ms latency on packets is going to impose a significant problem for the site, I have seen nothing better than the hetzner.de offering. $79 euros/month gets one a AMD Athlon 64 X2 4200+ Dual Core with 2Gb of ram and 2 300Gb drives with 1000Gb of bandwidth on a gigabit NIC, running Ubuntu. If one exceeds that 1000Gb in a month, they throttle you back to a 10mbit port speed but don't charge you extra. Compare to a leading US company, like ServerBeach. Their offering with the closes specs is $259/month USD, which is about $200 EUR. Same RAM, same CPU, 2 x 160Gb drives. 2000Gb/month, but on a 10mbit port. Really compare that to the US companies. You won't find a single one of them that comes close to this. If there is one, I'd love to hear about it! I have customers for whom a US based hosting company is important, from the point of view of their corporate policies (a very large US bank and a whole bunch of US mutual fund companies), but on several new, hopefully high traffic sites that are going to be coming online soon, where that consideration isn't an issue, I'm personally going with hetzner machines. They've been strongly suggested to me by Stefan Schmiedl. If you are going to Euruko this week, ask him about his experiences with them. Kirk Haines From george.moschovitis at gmail.com Wed Nov 1 11:08:43 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 1 Nov 2006 18:08:43 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: Thanks, hetzner.de is quite interesting indeed. > Unless the extra 100ms latency on packets is going to impose a what is this latency? > significant problem for the site, I have seen nothing better than the > hetzner.de offering. best regards, George. -- http://www.gmosx.com http://www.nitroproject.org From wyhaines at gmail.com Wed Nov 1 12:19:35 2006 From: wyhaines at gmail.com (Kirk Haines) Date: Wed, 1 Nov 2006 10:19:35 -0700 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: On 11/1/06, George Moschovitis wrote: > Thanks, > > hetzner.de is quite interesting indeed. > > > Unless the extra 100ms latency on packets is going to impose a > > what is this latency? Just an artifact of the fact that the servers are in Europe, so for traffic coming from the US, when those packets travel across the atlantic ocean, it adds some milliseconds to the round trip time. It seems to be around 100ms from the tests I have done. However, you, being in Europe, undoubtedly experience the same latency all the time when interacting with servers in the US, so you know that for most things it's not a significant issue. Kirk Haines From dan at tastapod.com Wed Nov 1 18:22:00 2006 From: dan at tastapod.com (Dan North) Date: Wed, 01 Nov 2006 23:22:00 +0000 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: <45492C18.6000702@tastapod.com> Full disclosure: I get no kickback from this - I'm just a happy customer. But if you mention me when you order I might get something nice :) I've been using Solar VPS for the last few months (http://solarvps.com). They're inexpensive ($30/month for my needs), they provide a debian image (which I immediately dist-upgraded to debian/testing). They have a European datacentre as well as one in the US. When I dist-upgraded, I was getting gigabit speeds to the German debian mirrors! And their support guys are pretty decent too. I'm running several wordpress blogs, several wikis, mysql, postfix mail server, courier imap server, the usual stuff. Not super high traffic, so I don't know how they will cope under real stress, but I've been very happy so far. Oh, it's a VPS with full root access (via ssh), and basic, web-based start/stop/reboot/recover. Can't remember if they offer an Ubuntu image. My package guarantees 256Mb of memory, but for the last couple of months I've had most of 4Gb! (Of course this will reduce over time as they add more nodes). hth, Dan George Moschovitis wrote: > Thanks for the detailed email. I am looking for a server to host a > high-traffic web site. (But I would like to see affordable options as > well). > > Btw, can someone understand what the (mt) GridServer really is? Which > linux distribution it supports and if I can compile and install my own > software in the container? > > regards, > George. > > On 11/1/06, Kirk Haines wrote: > >> On 11/1/06, George Moschovitis wrote: >> >>> Dear devs, >>> >>> I am looking for a dedicated server provider. Can anyone recomment a >>> dedicated hosting service? >>> >> Depends on what you need. >> >> For a good and very inexpensive host for Europe-centered traffic, consider >> >> http://hetzner.de/rootserver_en.html >> >> Compare especially the DS5000 and DS7000 to US providers. Hetzner >> compares extremely well on price, even considering the less generous >> bandwidth allotments than the next two that I will suggest. >> >> For more US centered traffic, I use ServerBeach quite happily. They >> have a pretty good balance of price and service with a generous >> bandwidth allotment. >> >> If you won't need a bandwidth allotment that high, though, take a look >> at cari.net for an inexpense US centered provider with a lot of >> options and good support. >> >> >> Kirk Haines >> _______________________________________________ >> Nitro-general mailing list >> Nitro-general at rubyforge.org >> http://rubyforge.org/mailman/listinfo/nitro-general >> >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061101/3ed1dc84/attachment.html From zedshaw at zedshaw.com Wed Nov 1 21:00:11 2006 From: zedshaw at zedshaw.com (Zed A. Shaw) Date: Wed, 1 Nov 2006 18:00:11 -0800 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: Message-ID: <20061101180011.40ff6465.zedshaw@zedshaw.com> On Wed, 1 Nov 2006 10:13:45 +0200 "George Moschovitis" wrote: > Dear devs, > > I am looking for a dedicated server provider. Can anyone recomment a > dedicated hosting service? Hey George, have you considered Amazon EC2 or Media Temple's Grid thing (I forget the name)? EC2 is interesting in that you can actually use it to "prototype" your deployment. You set everything up on your computer at home, then when you need to test stuff you kick on the EC2 instance, rsync or S3 the changes over, and play with it. Once everything is working great, you just turn the EC2 image on full time. I believe running it full time costs around 70/month USD. Downside: No static IP addresses. You'd probably have to get some DNS hosting or such. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://safari.oreilly.com/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. From james.britt at gmail.com Thu Nov 2 01:43:54 2006 From: james.britt at gmail.com (James Britt) Date: Wed, 01 Nov 2006 23:43:54 -0700 Subject: [Nitro] Dedicated Hosting In-Reply-To: <20061101180011.40ff6465.zedshaw@zedshaw.com> References: <20061101180011.40ff6465.zedshaw@zedshaw.com> Message-ID: <454993AA.1040303@gmail.com> Zed A. Shaw wrote: > On Wed, 1 Nov 2006 10:13:45 +0200 > "George Moschovitis" wrote: > > >>Dear devs, >> >>I am looking for a dedicated server provider. Can anyone recomment a >>dedicated hosting service? > > > Hey George, have you considered Amazon EC2 or Media Temple's > Grid thing (I forget the name)? EC2 is interesting in that you > can actually use it to "prototype" your deployment. You set everything > up on your computer at home, then when you need to test stuff you kick > on the EC2 instance, rsync or S3 the changes over, and play with it. > There's a lot to be said for running under a VM, though the overhead of being virtual might be too much. I've only recently started looking at Xen and EC2, though. > Once everything is working great, you just turn the EC2 image on full > time. I believe running it full time costs around 70/month USD. Plus storage and bandwidth costs. I was considering that myself, but decided I was better off with what I have now from EV1Servers.net > > Downside: No static IP addresses. You'd probably have to get some > DNS hosting or such. Other downside: it's in beta. -- James Britt http://www.rubyaz.org - Hacking in the Desert http://www.artima.com/rubycs/ - The Journal By & For Rubyists http://www.rubystuff.com - The Ruby Store for Ruby Stuff http://www.jamesbritt.com - Playing with Better Toys From george.moschovitis at gmail.com Thu Nov 2 03:43:53 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 10:43:53 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: <20061101180011.40ff6465.zedshaw@zedshaw.com> References: <20061101180011.40ff6465.zedshaw@zedshaw.com> Message-ID: > Hey George, have you considered Amazon EC2 or Media Temple's Grid thing (I forget the about EC2 still waiting for invitations.. and i think it is kindof expensive. about (mt) Grid Server. I think you dont have full permissions to compile and install your software. From what I understand I cannot install Ruby, imagemagick, RMagick and stuff like that. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Thu Nov 2 03:55:48 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 10:55:48 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: <45492C18.6000702@tastapod.com> References: <45492C18.6000702@tastapod.com> Message-ID: > I've been using Solar VPS for the last few months (http://solarvps.com). > They're inexpensive ($30/month for my needs), they provide a debian image > (which I immediately dist-upgraded to debian/testing). are you able to compile and install your own stuff on this server? (ruby, apache, mysql, imagemagick etc etc?) -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Thu Nov 2 04:04:07 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 11:04:07 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: <45492C18.6000702@tastapod.com> Message-ID: > > (which I immediately dist-upgraded to debian/testing). which command do you use for this? -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Thu Nov 2 07:11:57 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 14:11:57 +0200 Subject: [Nitro] JQuery questions Message-ID: Dear devs, I have a jquery question. Is it possible to emulate (programmatically force) a click on a button from the even handler of another button? Ie something like: $('#srcbutton').click(function() { $('#targetbutton').force_click(); }); thanks in advance for your help, -g. -- http://www.gmosx.com http://www.nitroproject.org From john at oxyliquit.de Thu Nov 2 09:40:10 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 02 Nov 2006 15:40:10 +0100 Subject: [Nitro] Roadmap 0.40 Message-ID: Hi, George, please update this roadmap: Roadmap 0.40 5th November - make tests pass Almost done[1][2] - make postgres adapter run Done - make sqlite adapter run Done - make examples run Done - introduce new system part / get rid of old scaffolding. Done - introduce more patches from manveru's repository. Done for this release. - cleanup code Done, more cleanup in future versions. - update docs Should be done now Jonathan 1. Please remove those two patches: Thu Nov 2 08:24:17 CET 2006 George Moschovitis * Don't save the target of refers_to (but we have to rethink this, check the comments). Thu Nov 2 08:14:30 CET 2006 George Moschovitis * Optimize sql queries when setting refers_to/belongs_to relations (less saves). More to come. These are merely enhancements and let one testcase fail. (I'm pretty much certain that this change has other implications which I fail to see atm and this area is not quite fully tested.) It's a little late in the dev cycle to integrate untested optimizations I think. 2. How far are you with parameters, any way my changes can actually go into this release without me pestering you even more? :P -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Thu Nov 2 10:19:26 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 17:19:26 +0200 Subject: [Nitro] Some cleanup Message-ID: Dear devs, I am thinking of moving the flare and spark directories inside examples to cleanup the root directory. moreover, I am thinking about removing gen alltogether. I don't think anyone is using it, so it does not justify the effort to keep this updated. Plus, it makes nitro more confusing to beginers. I would like to hear your opinion on these two issues. regards, George. -- http://www.gmosx.com http://www.nitroproject.org From john at oxyliquit.de Thu Nov 2 12:57:26 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 2 Nov 2006 18:57:26 +0100 Subject: [Nitro] Some cleanup In-Reply-To: References: Message-ID: <20061102175726.GA7468@oxyliquit.de> Hi, > I am thinking of moving the flare and spark directories inside > examples to cleanup the root directory. Sure, go ahaid. (But use `darcs mv` and not just move it :P) > moreover, I am thinking about removing gen alltogether. I don't think > anyone is using it, so it does not justify the effort to keep this > updated. Plus, it makes nitro more confusing to beginers. Uh, I use it, and I don't think it's confusing to newcomers. In fact I use it in my tutorials to create some 'cushion' for beginners to show them some stuff and tell them the 'standard' nitro project layout. Mainly I myself use it to recreate the basic directories. I remove basically all files though... Doing a `gen app foo` is easier than looking up where to get a `fcgi.rb` for use with apache... So, my vote is for not removing it completely unless something similar is provided. Jonathan From riku.raisanen at walkingwoods.com Thu Nov 2 13:28:59 2006 From: riku.raisanen at walkingwoods.com (=?ISO-8859-1?Q?Riku_R=E4is=E4nen?=) Date: Thu, 02 Nov 2006 20:28:59 +0200 Subject: [Nitro] JQuery questions In-Reply-To: References: Message-ID: <454A38EB.7030202@walkingwoods.com> Hello George. I have a bad email client here, thus I can't easily quote you. Anyway. What you speak of is not really DOM or AJAX related, which is what jQuery is built for. And it is not clear to me what you're after at all. is "button" a button? or is it a link? and as I said, it doesn't IMO really fit into context of jQuery, but is more "general" javascript. Where jQuery can help you, is giving you easy access to the links/buttons (and their attributes/values) you speak of and either: a) get the HREF attribute of the link ( $('#id_of_link').attr('href') ) and forward the user to there. b) submit the form the (target) button belongs to. Please be more specific in terms of button and what you want to do. (GET/POST? can it be AJAX request?) and I'll try to help you as much of possible. -Riku R?is?nen From transfire at gmail.com Thu Nov 2 13:30:56 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Thu, 02 Nov 2006 18:30:56 -0000 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <3ff63f9b0610290623t4eb88bf6w59245f4553028ea4@mail.gmail.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <3ff63f9b0610290623t4eb88bf6w59245f4553028ea4@mail.gmail.com> Message-ID: <1162492256.223163.200880@i42g2000cwa.googlegroups.com> Jonas Pfenniger wrote: > Perhaps the real problem is that Annotation is just too generic. You > can 't keep it simple and have all the features. Especially the > inheritance. So what are the boundaries of the annotation system ? > > * inheritance ? > * type-casting system ? > * central storage ? > * default settings ? > * description ? > > What do you envision it beeing used for ? Perhaps you are suggesting that the annotations system not be a single univeral interface? Martin Fowler is thinking along these lines at http://martinfowler.com/bliki/RubyAnnotations.html. So rather then say: ann :x, :doc => "This is helpful", :class => Integer, :default => 0 One would have: doc :x, "This is helpful" default :x, 0 classify :x, Integer I've brought this up before, and it's actually not incompatible if done a little bit differently: ann :x do doc "This is helpful" end In anycase, by making the annotation a class method one does have more control over what that annotation does via the standard Ruby metaprogramming techinuqes. On the downside there the potential for contention in the class-level namespace. T. From zimba.tm at gmail.com Thu Nov 2 14:38:37 2006 From: zimba.tm at gmail.com (Jonas Pfenniger) Date: Thu, 2 Nov 2006 20:38:37 +0100 Subject: [Nitro] JQuery questions In-Reply-To: References: Message-ID: <3ff63f9b0611021138t4c2adda3q2143399b47bea121@mail.gmail.com> On 02/11/06, George Moschovitis wrote: > I have a jquery question. Is it possible to emulate (programmatically > force) a click on a button from the even handler of another button? Ie > something like: > > $('#srcbutton').click(function() { > $('#targetbutton').force_click(); > }); Hi George, Go to http://www.visualjquery.com/index.xml , Events -> Mouse -> click() Last time I've tried (v1.0.2) this didn't work but now it may. I suspect it now working like you want if you're using the event object in the callback function. So your code should look like that : $('#srcbutton').click(function() { $('#targetbutton').click(); }); If it doesn't work, here is what I usually do : var do_something = function() { alert('this is the element's callback') } $('#targetbutton').click(do_something) $('#srcbutton').click(do_something} -- Cheers, zimbatm http://zimbatm.oree.ch From zimba.tm at gmail.com Thu Nov 2 14:48:19 2006 From: zimba.tm at gmail.com (Jonas Pfenniger) Date: Thu, 2 Nov 2006 20:48:19 +0100 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <1162492256.223163.200880@i42g2000cwa.googlegroups.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <3ff63f9b0610290623t4eb88bf6w59245f4553028ea4@mail.gmail.com> <1162492256.223163.200880@i42g2000cwa.googlegroups.com> Message-ID: <3ff63f9b0611021148m4fe0be1bj665eaa2624fe3594@mail.gmail.com> On 02/11/06, transfire at gmail.com wrote: > > Jonas Pfenniger wrote: > > Perhaps the real problem is that Annotation is just too generic. You > > can 't keep it simple and have all the features. Especially the > > inheritance. So what are the boundaries of the annotation system ? > > > > * inheritance ? > > * type-casting system ? > > * central storage ? > > * default settings ? > > * description ? > > > > What do you envision it beeing used for ? > > Perhaps you are suggesting that the annotations system not be a single > univeral interface? Martin Fowler is thinking along these lines at > http://martinfowler.com/bliki/RubyAnnotations.html. No, what I'm saying is that you're trying to solve too many problems at the same time. That makes annotations not really usefull. Nitro is full of them and I'm not convinced that if wouldn't look better without them or with a more targetted configuration system. I don't have real arguments but it's a kind of feeling. Most of all I think that it encourages a style of code that I'm not particularily fond of. If you want I can elaborate. -- Cheers, zimbatm http://zimbatm.oree.ch From george.moschovitis at gmail.com Thu Nov 2 15:31:05 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 22:31:05 +0200 Subject: [Nitro] Some cleanup In-Reply-To: <20061102175726.GA7468@oxyliquit.de> References: <20061102175726.GA7468@oxyliquit.de> Message-ID: > Sure, go ahaid. (But use `darcs mv` and not just move it :P) is darcs mv needed? > So, my vote is for not removing it completely unless something similar > is provided. what do others think? Indeed genis useful for tutorials and stuff like this. -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Thu Nov 2 15:34:26 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 22:34:26 +0200 Subject: [Nitro] JQuery questions In-Reply-To: <3ff63f9b0611021138t4c2adda3q2143399b47bea121@mail.gmail.com> References: <3ff63f9b0611021138t4c2adda3q2143399b47bea121@mail.gmail.com> Message-ID: > $('#srcbutton').click(function() { > $('#targetbutton').click(); > }); hmm tried, this i think it didn't work. I will try again. > var do_something = function() { alert('this is the element's callback') } > $('#targetbutton').click(do_something) > $('#srcbutton').click(do_something} I can't see how this is useful for my scenario. -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Thu Nov 2 15:45:49 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 2 Nov 2006 22:45:49 +0200 Subject: [Nitro] Roadmap 0.40 In-Reply-To: References: Message-ID: The biggest problem at the moment is building the gems. I found a solution (I have a working reap installation on an older computer). Regarding the parameters patch I cannot promise you it will be in 0.40.0. I really need that release out. I will probably flag the current repo as RC in the next couple of days so you could grab it and do some final testing. I aim for a final release on next Tuesday. Then, we will have all the time to fix pending problems like params, annotations etc. BTW, I *will* try to fix your params problems and thoroughly review your patch before release, but I cannot promise you this will be in. regards, George. On 11/2/06, Jonathan Buch wrote: > Hi, > > George, please update this roadmap: > > Roadmap 0.40 5th November > > - make tests pass > Almost done[1][2] > - make postgres adapter run > Done > - make sqlite adapter run > Done > - make examples run > Done > - introduce new system part / get rid of old scaffolding. > Done > - introduce more patches from manveru's repository. > Done for this release. > - cleanup code > Done, more cleanup in future versions. > - update docs > Should be done now > > Jonathan > > 1. Please remove those two patches: > > Thu Nov 2 08:24:17 CET 2006 George Moschovitis > * Don't save the target of refers_to (but we have to rethink this, check the comments). > > Thu Nov 2 08:14:30 CET 2006 George Moschovitis > * Optimize sql queries when setting refers_to/belongs_to relations (less saves). More to come. > > These are merely enhancements and let one testcase fail. (I'm pretty much > certain that this change has other implications which I fail to see atm and > this area is not quite fully tested.) It's a little late in the dev cycle to > integrate untested optimizations I think. > > 2. How far are you with parameters, any way my changes can actually go into > this release without me pestering you even more? :P > > -- > Feel the love > http://pinkjuice.com/pics/ruby.png > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From zedshaw at zedshaw.com Thu Nov 2 17:09:03 2006 From: zedshaw at zedshaw.com (Zed A. Shaw) Date: Thu, 2 Nov 2006 14:09:03 -0800 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: <20061101180011.40ff6465.zedshaw@zedshaw.com> Message-ID: <20061102140903.5e9ce31b.zedshaw@zedshaw.com> On Thu, 2 Nov 2006 10:43:53 +0200 "George Moschovitis" wrote: > > Hey George, have you considered Amazon EC2 or Media Temple's Grid thing (I forget the > > about EC2 still waiting for invitations.. and i think it is kindof expensive. > > about (mt) Grid Server. I think you dont have full permissions to > compile and install your software. From what I understand I cannot > install Ruby, imagemagick, RMagick and stuff like that. All good points. One thing though, you should seriously look at some of the rails hosting companies like Rails Machine, Rails Playground and Engine Yard. Yeah, yeah they're "rails". But, even more importantly they're *RUBY* hosting. You don't have to run Rails, and I'm sure if you talked with one of them they'd be interested in expanding their business to encompass other frameworks. Especially since all of them use Mongrel, and you use Mongrel, and they could care less what runs inside Mongrel. Food for thought. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://safari.oreilly.com/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. From zedshaw at zedshaw.com Thu Nov 2 17:12:49 2006 From: zedshaw at zedshaw.com (Zed A. Shaw) Date: Thu, 2 Nov 2006 14:12:49 -0800 Subject: [Nitro] Some cleanup In-Reply-To: References: <20061102175726.GA7468@oxyliquit.de> Message-ID: <20061102141249.1e674965.zedshaw@zedshaw.com> On Thu, 2 Nov 2006 22:31:05 +0200 "George Moschovitis" wrote: > > Sure, go ahaid. (But use `darcs mv` and not just move it :P) > > is darcs mv needed? > > > So, my vote is for not removing it completely unless something similar > > is provided. > > what do others think? Indeed genis useful for tutorials and stuff like this. > Just as an indirectly contributing Nitro observer, I'd say keep gen since it does make things easier on beginners, but more importantly just pick one layout and use it consistently. Uber-wizard-DIY types could obviously still go build their own layouts and avoid gen, but it's really confusing for Nitro newbies to have six different tutorials with six different ways to organize, name, and layout files. Just pick one that's reasonable, use gen to implicitly enforce it, and then make sure folks know they don't *have* to use this, it's just easier if you don't care. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://safari.oreilly.com/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. From transfire at gmail.com Thu Nov 2 17:13:17 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Thu, 02 Nov 2006 22:13:17 -0000 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <3ff63f9b0611021148m4fe0be1bj665eaa2624fe3594@mail.gmail.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <3ff63f9b0610290623t4eb88bf6w59245f4553028ea4@mail.gmail.com> <1162492256.223163.200880@i42g2000cwa.googlegroups.com> <3ff63f9b0611021148m4fe0be1bj665eaa2624fe3594@mail.gmail.com> Message-ID: <1162505597.923232.82750@m73g2000cwd.googlegroups.com> Jonas Pfenniger wrote: > No, what I'm saying is that you're trying to solve too many problems > at the same time. That makes annotations not really usefull. Nitro is > full of them and I'm not convinced that if wouldn't look better > without them or with a more targetted configuration system. I don't > have real arguments but it's a kind of feeling. Most of all I think > that it encourages a style of code that I'm not particularily fond of. > If you want I can elaborate. Please do. I'm not sure yet what you mean. And what would you replace them with? T. From vikingtux at gmail.com Thu Nov 2 18:49:28 2006 From: vikingtux at gmail.com (Alexandre Gravem) Date: Thu, 2 Nov 2006 20:49:28 -0300 Subject: [Nitro] JQuery questions In-Reply-To: References: Message-ID: <40b05ebe0611021549vc188297l47e61157f415e3a2@mail.gmail.com> I should do $('#srcbutton').click(function() { > $('#targetbutton').trigger('click'); > > }); On 11/2/06, George Moschovitis wrote: > > Dear devs, > > I have a jquery question. Is it possible to emulate (programmatically > force) a click on a button from the even handler of another button? Ie > something like: > > $('#srcbutton').click(function() { > $('#targetbutton').force_click(); > }); > > thanks in advance for your help, > -g. > > > -- > http://www.gmosx.com > http://www.nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061102/f6113d26/attachment.html From vikingtux at gmail.com Thu Nov 2 18:50:08 2006 From: vikingtux at gmail.com (Alexandre Gravem) Date: Thu, 2 Nov 2006 20:50:08 -0300 Subject: [Nitro] JQuery questions In-Reply-To: <40b05ebe0611021549vc188297l47e61157f415e3a2@mail.gmail.com> References: <40b05ebe0611021549vc188297l47e61157f415e3a2@mail.gmail.com> Message-ID: <40b05ebe0611021550u705b06b5p7bb5b7470e322f02@mail.gmail.com> Sorry ... *You* should do ... On 11/2/06, Alexandre Gravem wrote: > > I should do > > $('#srcbutton').click(function() { > > > $('#targetbutton').trigger('click'); > > > > }); -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061102/17407127/attachment.html From vikingtux at gmail.com Thu Nov 2 18:55:50 2006 From: vikingtux at gmail.com (Alexandre Gravem) Date: Thu, 2 Nov 2006 20:55:50 -0300 Subject: [Nitro] Some cleanup In-Reply-To: <20061102175726.GA7468@oxyliquit.de> References: <20061102175726.GA7468@oxyliquit.de> Message-ID: <40b05ebe0611021555n1ef18d62n7f9b21d6d49f8b1e@mail.gmail.com> > > So, my vote is for not removing it completely unless something similar > is provided. > > +1 A. Gravem -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061102/b1de77a9/attachment.html From fabian at fabian-buch.de Thu Nov 2 18:58:03 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Fri, 3 Nov 2006 00:58:03 +0100 Subject: [Nitro] Some cleanup In-Reply-To: References: <20061102175726.GA7468@oxyliquit.de> Message-ID: Am 02.11.2006 um 21:31 schrieb George Moschovitis: >> Sure, go ahaid. (But use `darcs mv` and not just move it :P) > > is darcs mv needed? it's much better than moving by hand and doesn't confuse darcs so much. >> So, my vote is for not removing it completely unless something >> similar >> is provided. > > what do others think? Indeed gen is useful for tutorials and stuff > like this. And for 'gen part'. I wouldn't want to do that by hand all the time. But if Rachets is out I think gen could be replaced by ratchets tasks or similar. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Fri Nov 3 00:56:55 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 07:56:55 +0200 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> Message-ID: > harp:~ > cat a.rb > ... > :baz} > > Now this implementatin leaves out some of the needed shortcuts (like > implied class annotation) and it also leaves out the BIG issue of > inheritance, but those can of course can be worked in. The main thing > here is the simplicty of the interface. I realize it's a big change but > I think Ara has a point. The simplicy, uniformity and consistancy has > it's own merits over the elegance of the magic dot notation. Well I like this simplicity as well. Could you introduce the inheritance feature? And what is implied class annotation? I would like to replace nitro's annotation with this simpler version. If you remember, I was always worried about the performance (and complexity) issues of the current implementation. -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Fri Nov 3 00:59:06 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 07:59:06 +0200 Subject: [Nitro] Some cleanup In-Reply-To: <20061102141249.1e674965.zedshaw@zedshaw.com> References: <20061102175726.GA7468@oxyliquit.de> <20061102141249.1e674965.zedshaw@zedshaw.com> Message-ID: > easier on beginners, but more importantly just pick one layout and use it consistently. I am pretty sure I have found a layout that I am happy with this (after 2 years ;-)) Have a look at the redesigned flare/spark/blog examples. -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Fri Nov 3 00:59:47 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 07:59:47 +0200 Subject: [Nitro] Some cleanup In-Reply-To: <40b05ebe0611021555n1ef18d62n7f9b21d6d49f8b1e@mail.gmail.com> References: <20061102175726.GA7468@oxyliquit.de> <40b05ebe0611021555n1ef18d62n7f9b21d6d49f8b1e@mail.gmail.com> Message-ID: On 11/3/06, Alexandre Gravem wrote: > > > So, my vote is for not removing it completely unless something similar > > is provided. > > > > > +1 Ok, this stays ;-) thanks for your input ;-) -g. -- http://www.gmosx.com http://www.nitroproject.org From al-nitrogen at none.at Fri Nov 3 02:23:55 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Fri, 3 Nov 2006 08:23:55 +0100 Subject: [Nitro] Some cleanup In-Reply-To: <20061102141249.1e674965.zedshaw@zedshaw.com> References: <20061102175726.GA7468@oxyliquit.de> <20061102141249.1e674965.zedshaw@zedshaw.com> Message-ID: <20061103072355.GA10673@none.at> Hi, sorry for the late replay. On Don 02.11.2006 14:12, Zed A. Shaw wrote: >On Thu, 2 Nov 2006 22:31:05 +0200 >"George Moschovitis" wrote: > >> > Sure, go ahaid. (But use `darcs mv` and not just move it :P) >> >> is darcs mv needed? >> >> > So, my vote is for not removing it completely unless something similar >> > is provided. >> >> what do others think? Indeed genis useful for tutorials and stuff like this. >> > >Just as an indirectly contributing Nitro observer, I'd say keep gen >since it does make things easier on beginners, but more importantly >just pick one layout and use it consistently. > >Uber-wizard-DIY types could obviously still go build their own layouts >and avoid gen, but it's really confusing for Nitro newbies to have six >different tutorials with six different ways to organize, name, and >layout files. Full ack, without the gen I is much harder to start with nitro, from my point of view. Regards Aleks From george.moschovitis at gmail.com Fri Nov 3 05:40:19 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 12:40:19 +0200 Subject: [Nitro] Facets + Multibytes Message-ID: Tom, I would like to suggest that you include the ActiveSupport::Multibytes functionality in facets. It is extremely useful. regards, George. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Fri Nov 3 05:45:14 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 12:45:14 +0200 Subject: [Nitro] Roadmap 0.40 In-Reply-To: References: Message-ID: > 1. Please remove those two patches: > > Thu Nov 2 08:24:17 CET 2006 George Moschovitis > * Don't save the target of refers_to (but we have to rethink this, check the comments). > > Thu Nov 2 08:14:30 CET 2006 George Moschovitis > * Optimize sql queries when setting refers_to/belongs_to relations (less saves). More to come. > > These are merely enhancements and let one testcase fail. (I'm pretty much > certain that this change has other implications which I fail to see atm and > this area is not quite fully tested.) It's a little late in the dev cycle to > integrate untested optimizations I think. nope these patches are needed. For example they fix a common bug. Consider this code: def save_article a = Article.new.assign(request) a.author = User.current a.something_else = 'initialize something else' a.save end without the patch Og saves behind the scenes the article before 'something_else' is initialized. Moreover it also saves the user. Both queries are not needed and break this example. Am I missing something? regards, George. -- http://www.gmosx.com http://www.nitroproject.org From transfire at gmail.com Fri Nov 3 07:42:55 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Fri, 03 Nov 2006 12:42:55 -0000 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> Message-ID: <1162557775.989709.22560@h54g2000cwb.googlegroups.com> George Moschovitis wrote: > > harp:~ > cat a.rb > > ... > > :baz} > > > > Now this implementatin leaves out some of the needed shortcuts (like > > implied class annotation) and it also leaves out the BIG issue of > > inheritance, but those can of course can be worked in. The main thing > > here is the simplicty of the interface. I realize it's a big change but > > I think Ara has a point. The simplicy, uniformity and consistancy has > > it's own merits over the elegance of the magic dot notation. > > Well I like this simplicity as well. Could you introduce the > inheritance feature? > And what is implied class annotation? Oh, just: ann :x, String implies ann :x, :class=>String T. From john at oxyliquit.de Fri Nov 3 08:28:27 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 3 Nov 2006 14:28:27 +0100 Subject: [Nitro] Roadmap 0.40 In-Reply-To: References: Message-ID: <20061103132826.GA13978@oxyliquit.de> Hi, > nope these patches are needed. For example they fix a common bug. > Consider this code: > > def save_article > a = Article.new.assign(request) > a.author = User.current > a.something_else = 'initialize something else' > a.save > end > > without the patch Og saves behind the scenes the article before > 'something_else' is initialized. Moreover it also saves the user. Both > queries are not needed and break this example. > > Am I missing something? Not sure, I've been thinking about this a bit more. Using your example: If User.current is a not saved yet, has no oid, then this will fail. Please describe that 'something_else' which has to be initialized before the Article gets it's oid. Where I know that your way might be the better one: In Orderable, which can be quite ugly if something is or is not saved on some very constrained condition. When removing the implicit saves, there have to be explicit .save's all over the place. I've seen one example from Rayman where he literarily saved every other line or it wouldn't work, pretty ugly. It would be good to have testcases specifying the appropriate behaviour. Again like with params, this might just be another way of thinking. :P Jonathan From george.moschovitis at gmail.com Fri Nov 3 09:01:03 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 16:01:03 +0200 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <1162557775.989709.22560@h54g2000cwb.googlegroups.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <1162557775.989709.22560@h54g2000cwb.googlegroups.com> Message-ID: ah ;-) that is nice too, but not too important. Inheritance is extremely important though. -g. > Oh, just: > > ann :x, String > > implies > > ann :x, :class=>String -- http://www.gmosx.com http://www.nitroproject.org From john at oxyliquit.de Fri Nov 3 09:02:45 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 03 Nov 2006 15:02:45 +0100 Subject: [Nitro] Some cleanup In-Reply-To: References: <20061102175726.GA7468@oxyliquit.de> Message-ID: Hi, >> Sure, go ahaid. (But use `darcs mv` and not just move it :P) >is darcs mv needed? yes it is, if you want to retain the history of those files and want to accept patches in that area from someone who is not completely up to date with your repo. Jonathan -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Fri Nov 3 11:09:02 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 18:09:02 +0200 Subject: [Nitro] Roadmap 0.40 In-Reply-To: <20061103132826.GA13978@oxyliquit.de> References: <20061103132826.GA13978@oxyliquit.de> Message-ID: > If User.current is a not saved yet, has no oid, then this will fail. nah, it doesn't make much sense to attach a non saved user. > Where I know that your way might be the better one: In Orderable, which > can be quite ugly if something is or is not saved on some very > constrained condition. can you elaborate? > When removing the implicit saves, there have to be explicit .save's all > over the place. I've seen one example from Rayman where he literarily > saved every other line or it wouldn't work, pretty ugly. can you elabotate? I appreicate your input on this, would be better if we got more opinions on this important matter. -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Fri Nov 3 11:09:38 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 18:09:38 +0200 Subject: [Nitro] Some cleanup In-Reply-To: References: <20061102175726.GA7468@oxyliquit.de> Message-ID: > yes it is, if you want to retain the history of those files and want > to accept patches in that area from someone who is not completely up > to date with your repo. ok will use darcs mv from now on! thanks for mentioning this! -g. -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Fri Nov 3 11:32:04 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 3 Nov 2006 18:32:04 +0200 Subject: [Nitro] Dedicated Hosting In-Reply-To: <20061102140903.5e9ce31b.zedshaw@zedshaw.com> References: <20061101180011.40ff6465.zedshaw@zedshaw.com> <20061102140903.5e9ce31b.zedshaw@zedshaw.com> Message-ID: They seem interesting but kindof expensive. Btw, virtual servers seem to be more expensive than plain dedicated servers, strange. -g. On 11/3/06, Zed A. Shaw wrote: > On Thu, 2 Nov 2006 10:43:53 +0200 > "George Moschovitis" wrote: > > > > Hey George, have you considered Amazon EC2 or Media Temple's Grid thing (I forget the > > > > about EC2 still waiting for invitations.. and i think it is kindof expensive. > > > > about (mt) Grid Server. I think you dont have full permissions to > > compile and install your software. From what I understand I cannot > > install Ruby, imagemagick, RMagick and stuff like that. > > All good points. One thing though, you should seriously look at some of the rails hosting companies like Rails Machine, Rails Playground and Engine Yard. Yeah, yeah they're "rails". But, even more importantly they're *RUBY* hosting. You don't have to run Rails, and I'm sure if you talked with one of them they'd be interested in expanding their business to encompass other frameworks. > > Especially since all of them use Mongrel, and you use Mongrel, and they could care less what runs inside Mongrel. > > Food for thought. > > -- > Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu > http://www.zedshaw.com/ > http://safari.oreilly.com/0321483502 -- The Mongrel Book > http://mongrel.rubyforge.org/ > http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From m.fellinger at gmail.com Fri Nov 3 13:46:43 2006 From: m.fellinger at gmail.com (Michael Fellinger) Date: Sat, 4 Nov 2006 03:46:43 +0900 Subject: [Nitro] Roadmap 0.40 In-Reply-To: References: Message-ID: <9c00d3e00611031046q4f3c47e9x3132ba17c95155e9@mail.gmail.com> On 11/3/06, George Moschovitis wrote: > The biggest problem at the moment is building the gems. I found a > solution (I have a working reap installation on an older computer). > Regarding the parameters patch I cannot promise you it will be in > 0.40.0. I really need that release out. I will probably flag the > current repo as RC in the next couple of days so you could grab it and > do some final testing. I aim for a final release on next Tuesday. > Then, we will have all the time to fix pending problems like params, > annotations etc. > > BTW, I *will* try to fix your params problems and thoroughly review > your patch before release, but I cannot promise you this will be in. I would really, really appreciate it being in :) would get me rid of some nasty hacks of parsing the request myself to find them > regards, > George. > > > On 11/2/06, Jonathan Buch wrote: > > Hi, > > > > George, please update this roadmap: > > > > Roadmap 0.40 5th November > > > > - make tests pass > > Almost done[1][2] > > - make postgres adapter run > > Done > > - make sqlite adapter run > > Done > > - make examples run > > Done > > - introduce new system part / get rid of old scaffolding. > > Done > > - introduce more patches from manveru's repository. > > Done for this release. > > - cleanup code > > Done, more cleanup in future versions. > > - update docs > > Should be done now > > > > Jonathan > > > > 1. Please remove those two patches: > > > > Thu Nov 2 08:24:17 CET 2006 George Moschovitis > > * Don't save the target of refers_to (but we have to rethink this, check the comments). > > > > Thu Nov 2 08:14:30 CET 2006 George Moschovitis > > * Optimize sql queries when setting refers_to/belongs_to relations (less saves). More to come. > > > > These are merely enhancements and let one testcase fail. (I'm pretty much > > certain that this change has other implications which I fail to see atm and > > this area is not quite fully tested.) It's a little late in the dev cycle to > > integrate untested optimizations I think. > > > > 2. How far are you with parameters, any way my changes can actually go into > > this release without me pestering you even more? :P > > > > -- > > Feel the love > > http://pinkjuice.com/pics/ruby.png > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > > -- > http://www.gmosx.com > http://www.nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From john at oxyliquit.de Fri Nov 3 14:04:40 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 03 Nov 2006 20:04:40 +0100 Subject: [Nitro] Roadmap 0.40 In-Reply-To: References: Message-ID: > The biggest problem at the moment is building the gems. I found a > solution (I have a working reap installation on an older computer). > Regarding the parameters patch I cannot promise you it will be in > 0.40.0. I really need that release out. I will probably flag the > current repo as RC in the next couple of days so you could grab it and > do some final testing. I aim for a final release on next Tuesday. > Then, we will have all the time to fix pending problems like params, > annotations etc. > BTW, I *will* try to fix your params problems and thoroughly review > your patch before release, but I cannot promise you this will be in. Yes thank you. but if it comes to the worst, I already agreed on moving back to the 0.31 params before. Jonathan -- Feel the love http://pinkjuice.com/pics/ruby.png From transfire at gmail.com Sat Nov 4 00:26:32 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Sat, 04 Nov 2006 05:26:32 -0000 Subject: [Nitro] Facets + Multibytes In-Reply-To: References: Message-ID: <1162617992.364017.78260@i42g2000cwa.googlegroups.com> George Moschovitis wrote: > Tom, > > I would like to suggest that you include the ActiveSupport::Multibytes > functionality in facets. It is extremely useful. > i'll look into it as soon as i can. t. From lasso at lassoweb.se Sat Nov 4 04:17:53 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Sat, 04 Nov 2006 10:17:53 +0100 Subject: [Nitro] Whitespace In-Reply-To: References: <20061031102539.GA30141@oxyliquit.de> <3ff63f9b0610310436p6f0dff1bha2e45423da7bba9d@mail.gmail.com> <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> Message-ID: <454C5AC1.4060302@lassoweb.se> Hello, I found the bug. In /nitro/compiler/elements.rb the doctype method is missing. It should be added. The one from /nitro/compiler/morphing.rb works just fine: (from nitro/compiler/morphing.rb, Listener class) def doctype(name, pub_sys, long_name, uri) @buffer << "" end (you might just want to add a newline at the end. DOCTYPEs generally stand on its own line.) Btw, The fix above works with the default transformation pipeline. There *might* be some other compiler classes (not in the default pipeline) that need that method added too. Sincerely /lasso ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ George Moschovitis skrev: >> No problem there. REXML already supports DOCTYPEs. The problem is that >> Nitro strips the DOCTYPE *after* REXML has processed the template. Since >> some XML tools require this type of information in order to function >> they are unable to parse pages rendered by Nitro. This is *very* bad in >> my opinion (luckily there are workarounds). > > > can you (or someone else) provide a patch for this? > > -g. > From george.moschovitis at gmail.com Sat Nov 4 09:45:51 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 4 Nov 2006 16:45:51 +0200 Subject: [Nitro] Facets + Multibytes In-Reply-To: <1162617992.364017.78260@i42g2000cwa.googlegroups.com> References: <1162617992.364017.78260@i42g2000cwa.googlegroups.com> Message-ID: thanks ;-) -g. On 11/4/06, transfire at gmail.com wrote: > > George Moschovitis wrote: > > Tom, > > > > I would like to suggest that you include the ActiveSupport::Multibytes > > functionality in facets. It is extremely useful. > > > > i'll look into it as soon as i can. > > t. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Sat Nov 4 09:47:02 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 4 Nov 2006 16:47:02 +0200 Subject: [Nitro] Whitespace In-Reply-To: <454C5AC1.4060302@lassoweb.se> References: <20061031102539.GA30141@oxyliquit.de> <3ff63f9b0610310436p6f0dff1bha2e45423da7bba9d@mail.gmail.com> <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> <454C5AC1.4060302@lassoweb.se> Message-ID: Thanks for this bug fix. How about sending me a proper darcs patch. This way you will get properly credited in the Changelog. thanks, George. On 11/4/06, Lars Olsson wrote: > Hello, > > I found the bug. In /nitro/compiler/elements.rb the doctype method is > missing. It should be added. The one from /nitro/compiler/morphing.rb > works just fine: > > (from nitro/compiler/morphing.rb, Listener class) > > def doctype(name, pub_sys, long_name, uri) > @buffer << "" > end > > (you might just want to add a newline at the end. DOCTYPEs generally > stand on its own line.) > > Btw, The fix above works with the default transformation pipeline. There > *might* be some other compiler classes (not in the default pipeline) > that need that method added too. > > Sincerely > > /lasso > > > ________________________________________ > Lars Olsson > lasso at lassoweb.se > http://www.lassoweb.se/ > > > > George Moschovitis skrev: > >> No problem there. REXML already supports DOCTYPEs. The problem is that > >> Nitro strips the DOCTYPE *after* REXML has processed the template. Since > >> some XML tools require this type of information in order to function > >> they are unable to parse pages rendered by Nitro. This is *very* bad in > >> my opinion (luckily there are workarounds). > > > > > > can you (or someone else) provide a patch for this? > > > > -g. > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://www.gmosx.com http://www.nitroproject.org From george.moschovitis at gmail.com Sun Nov 5 04:02:19 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 5 Nov 2006 11:02:19 +0200 Subject: [Nitro] Patches Message-ID: Dear devs, if anyone has any patches to send me before 0.40.0, now is the time! (I am aware of the pending params patch of Jonathan). Manv, what about your autoreload patch? regards, George. -- http://www.gmosx.com http://www.nitroproject.org From lasso at lassoweb.se Sun Nov 5 04:15:43 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Sun, 05 Nov 2006 10:15:43 +0100 Subject: [Nitro] Whitespace In-Reply-To: References: <20061031102539.GA30141@oxyliquit.de> <3ff63f9b0610310436p6f0dff1bha2e45423da7bba9d@mail.gmail.com> <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> <454C5AC1.4060302@lassoweb.se> Message-ID: <454DABBF.4070903@lassoweb.se> Hi! (Confession: I've never ever used darcs before! Please correct my errors gently! :) ) Here's the patch (against repo.nitroproject.org). Sincerely /lasso ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ George Moschovitis skrev: > Thanks for this bug fix. How about sending me a proper darcs patch. > This way you will get properly credited in the Changelog. > > thanks, > George. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: compiler_doctype_fix Url: http://rubyforge.org/pipermail/nitro-general/attachments/20061105/2945e662/attachment-0001.ksh From george.moschovitis at gmail.com Sun Nov 5 06:11:42 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 5 Nov 2006 13:11:42 +0200 Subject: [Nitro] Whitespace In-Reply-To: <454DABBF.4070903@lassoweb.se> References: <3ff63f9b0610310436p6f0dff1bha2e45423da7bba9d@mail.gmail.com> <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> <454C5AC1.4060302@lassoweb.se> <454DABBF.4070903@lassoweb.se> Message-ID: Hello Lars, the patch seems ok, please send this as an attachment (zipped/or targz'ed) Gmail seems to f*ck up darcs patches. thanks! -g. On 11/5/06, Lars Olsson wrote: > Hi! > > (Confession: I've never ever used darcs before! Please correct my errors > gently! :) ) > > Here's the patch (against repo.nitroproject.org). > > > Sincerely > > /lasso > > ________________________________________ > Lars Olsson > lasso at lassoweb.se > http://www.lassoweb.se/ > > > > George Moschovitis skrev: > > Thanks for this bug fix. How about sending me a proper darcs patch. > > This way you will get properly credited in the Changelog. > > > > thanks, > > George. > > > > New patches: > > [compiler_doctype_fix > Lars Olsson **20061105090533 > Adds handling of DOCTYPEs to elements compiler and adds a newline to the doctype handler for the morphing compiler. > ] { > hunk ./nitro/lib/nitro/compiler/elements.rb 146 > + end > + > + def doctype(name, pub_sys, long_name, uri) > + @buffer << "\n" > hunk ./nitro/lib/nitro/compiler/morphing.rb 212 > - @buffer << "" > + @buffer << "\n" > } > > Context: > > [Updated docs > George Moschovitis **20061104150045] > [Moved flash/spark into examples to cleanup top level dir. > George Moschovitis **20061103103357] > [Don't save the target of refers_to (but we have to rethink this, check the comments). > George Moschovitis **20061102072417] > [Optimize sql queries when setting refers_to/belongs_to relations (less saves). More to come. > George Moschovitis **20061102071430] > [System part saving handles relations now. > George Moschovitis **20061102061122] > ['prevent overwriting an existing cache via Global.setup > manveru at weez-int.com**20061031094720] > [fix small typo in why_wiki > manveru at weez-int.com**20061031094457] > [Reverted to facets 1.4.3 > George Moschovitis **20061030071924] > [move private statement in sqlite below query() > Jonathan Buch **20061027130302 > fixes at least one testcase > ] > [Fix rescues > Jonathan Buch **20061027122853 > These `rescue => ex` blocks only catch certain errors, they didn't > catch errors from PGError when the -pr postgres extension is used. > Rewrote all those rescues to `rescue Object => ex`. > ] > [Fix table_info(), return only first row > Jonathan Buch **20061026083933] > [Add table_exists? and table_info for psql/mysql/sqlite > Jonathan Buch **20061024190843] > [Use a local version of annotation, in an attempt to upgrade to the latest version of facets. > George Moschovitis **20061028083612] > [Minor cleanup. > George Moschovitis **20061028083517] > [Fix an exploitable bug in CGI multipart parsing which affects Ruby <= 1.8.5 > manveru at weez-int.com**20061025083802 > when the input stream returns "" (empty string) instead of nil on EOF. > Certain malformed multipart requests leave the parser in a non-terminating > state, leaving the program vulnerable to denial of service attack. The fix > more carefully checks for input stream EOF. > affected: standalone CGI, Mongrel > unaffected: FastCGI, mod_ruby, WEBrick > > found and fixed by zedas > ] > [more checks in get/put_store > Jonathan Buch **20061024184343 > The original can lead to weird errors when Og.start gets called many times > and many stores are used concurrently. > ] > [Change manage_classes, use less .managed_classes calls, add check for manageable? > Jonathan Buch **20061024181904] > [Add compatibility layer for postgres-pr and early postgres lib versions > Jonathan Buch **20061024175727] > [Rework Og.start() a little, add m.manage_classes(options[:classes]) > Jonathan Buch **20061024174637] > [Updated why_wiki. > George Moschovitis **20061024154145] > [Updated CHANGELOG. > George Moschovitis **20061024124642] > [You guessed it, more changes to examples ;-) > George Moschovitis **20061024082500] > [More changes to examples, even more to come. > George Moschovitis **20061024082419] > [Many changes to examples, flare, spark to convert to latest code, more to come. > George Moschovitis **20061024082333] > [Moved system view dirs to template dirs. > George Moschovitis **20061024062032] > [Adde set_attributes, instace_attribute_set methods in entity, for easy (and fast) update+save of attributes. Custom Mysql quote. > George Moschovitis **20061023115253] > [Some work on dispatcher for tc_params. > George Moschovitis **20061023115213] > [Updates in TODO. > George Moschovitis **20061023115147] > [Multiple fixes to make Nitro tests pass. All pass except tc_session with Og cachse and tc_controller_params. Can anyone help with these two? > George Moschovitis **20061019152957] > [More flexible controller_map setting. Allows presetting of controller maps in parts. Have a look at the system part for an example. > George Moschovitis **20061019092453] > [Minor. > George Moschovitis **20061018074820] > [More effective $cache.cleanup > George Moschovitis **20061018074708] > [Many changes to make all Og tests pass with MySQL, yeah! Anyone can try prostgres/sqlite? > George Moschovitis **20061017191259] > [All Glue tests pass cleanly. > George Moschovitis **20061016082957] > [Added doc/TODO to offer a glimpse to the future of Nitro. > George Moschovitis **20061016071926] > [Skip redirects on ajax/rpc requests. Allows to write more reusable code. > George Moschovitis **20061016071453] > [Removed all Admin/Scaffolding stuff. Lets clear the directory structure a bit ;-) > George Moschovitis **20061014170714] > [Added new System part that will replace old Admin part. The implementation is much simpler, it supports plugins and more. In general it is a better place for improvment. Ooh, and should startup faster too ;-) > George Moschovitis **20061014165130] > [Mark instances started by the bin/nitro command with the application name for easy identification when running ps. > George Moschovitis **20061013132756] > [Improved handling of index params in dispatcher, fixes bug when only template exists and no action (tiny example runs now ;-)) > George Moschovitis **20061013074907] > [Fix in Global. > George Moschovitis **20061013064758] > [Converted blog example. > George Moschovitis **20061013063711] > [Fix: Made sweeper compatible with new cache scheme. > George Moschovitis **20061013060625] > [Fix in feed link calculation (no '//') > George Moschovitis **20061011081124] > [Fix in mailer outgoing. > George Moschovitis **20061011081100] > [Fix Glue testcases, many failing though > Jonathan Buch **20060930150921] > [Revamp tc params to also allow POST requests, add POST multipart test > Jonathan Buch **20060929134324] > [Add test to tc params for action_methods / module including > Jonathan Buch **20060928142918] > [repair Controller.action_methods > Jonathan Buch **20060928142621] > [Insert testcase for params, bugreport ray > Jonathan Buch **20060928133450] > [Change the way /index with parameters handled > Jonathan Buch **20060927223815 > This behaviour is documented in tc_controller_params.rb in the two tcs > test_index_handling and test_index_handling_bad. > ] > [Replace refs to the old 9999 port with the new 9000 port. > George Moschovitis **20061010111635] > [Removed some obsolete files. > George Moschovitis **20061010111154] > [More flexible elements namespace selection, you can easier have multiple skins in your web app, per controller, per controller group etc. Read the source for more details. A low level example: ann :self, :elements => CustomSkin. I will add some DSL macro for this though. > George Moschovitis **20061010084527] > [this allows you to use the sqlite-memory-store (sqlite3) by setting the :name to ':memory:' > manveru at weez-int.com**20060929075743] > [Fix sti bug, used subclass name for foreign_key > Jonathan Buch **20061003103231 > Foo has_many Bar; User has_many Foo; Admin < User; Admin.foos #=> SQL > ERROR: DB error no such column: admin_oid, [SELECT * FROM ogcustomer WHERE admin_oid = 1] > > Thx to Rayman for catching that bug, added testcase as well > ] > [Small tc reverse fix, also works on psql now! > Jonathan Buch **20060929174147] > [Fixed emit labels in relation controls. > George Moschovitis **20061009193439] > [Another cool flash helper, concat. Useful for error handling in cooperation with the new form builder features. > George Moschovitis **20061009192031] > [Nitro unescapes request params (even for nice urls), more cases handled. > George Moschovitis **20061009161125] > [Improved form builder error handling, more intuitive implementation of flash.push. > George Moschovitis **20061009160120] > [Fix in text_key/key annotation, it is handles correctly now. > George Moschovitis **20061009072919] > [Form helper should ignore polymorphic_marker relations. > George Moschovitis **20061008085628] > [When deleting an Og entity load the object, so og_delete aspects can access instance variables. Useful for sophisticated cache sweepers. > George Moschovitis **20061008080957] > [Updated scaffold model to use the new OgSystem stuff. > George Moschovitis **20061008080926] > [WebFile.override_files = true by default. > George Moschovitis **20061008072452] > [Made strange router urls more compatible with Apache. > George Moschovitis **20061008072113] > [At last, output caching generates files, not directories. Improved apache/webrick/mongrel rewrite rules. > George Moschovitis **20061008071447] > [Added a nasty hack that fixes a truly nasty bug. For details read in the webrick/mongrel adapters. We must find a better solution though. > George Moschovitis **20061007173056] > [Reverted some changes in compiler/dispatcher, cleaned up the mess. Sorry Fabian, your changes where invalid, but I will make your updated testcases pass. Gimme some more time ;-) > George Moschovitis **20061007153307] > [More correct calculation of managed_classes. > George Moschovitis **20061007070202] > [Added some comments. > George Moschovitis **20061005182903] > [Added useful handle_static_files setting in Server. When running in production mode set to false (the frontend webserver should handle static files). Allows an ingenious rewrite rule to handle admin servers ;-) > George Moschovitis **20061005182522] > [added nitro/tc_template for coming move of Glue::Template -> Nitro::Template > manveru at weez-int.com**20060925203752] > [added nitro/tc_markup (this will become important after the Glue::Markup -> Nitro::Markup move > manveru at weez-int.com**20060925203051] > [Make OgCache faster by adding primary_key index > Jonathan Buch **20060929164816] > [ The huge Template|Markup move from Glue to Nitro > manveru at weez-int.com**20060928092324] > [Fix tc_validation_loop > Jonathan Buch **20060928112058] > [Fix tc_reverse > Jonathan Buch **20060928111438] > [Add psql rollback/savepoints for transactions > Jonathan Buch **20060928111226] > [Try fix sti, ogtype resolution for mysql < 5, -pr psql > Jonathan Buch **20060928105756] > [add fatal failed testcases to the failed testcases :) > manveru at weez-int.com**20060927223059] > [Fix bug, used String for primary_key for psql auto generated values. > Jonathan Buch **20060927224042] > [Fix tc has_many > Jonathan Buch **20060927212206] > [Fix param handling and param testcases > Jonathan Buch **20060927212044] > [Fix tc controller, remove unnessessary action_methods > Jonathan Buch **20060927210246] > [Fix tc multi_validation and tc kirby. > Jonathan Buch **20060927160905] > [Fix tc primary key for psql, change sequence handling > Jonathan Buch **20060927160518 > Moves sequence description to a annotation for the primary key instead of > using a constant in the class. Only uses sequences if the sql for the > pk includes the keyword SERIAL. This does not account for manually > created sequences, TODO. > ] > [Fix reverse tc, makes it pass for mysql > Jonathan Buch **20060927133118] > [Fix inheritance tc > Jonathan Buch **20060927132223] > [Fix sti for psql > Jonathan Buch **20060927132149] > [retry when sqlite database locked > Alex Pooley **20060908140800] > [Make inline C in tc_cgi more robust > Jonathan Buch **20060927122119] > [Add more tests to tc param > Jonathan Buch **20060926205950] > [More and better testcases for params > Jonathan Buch **20060926124647] > [More testcases for tc_controller_params, refactor > Jonathan Buch **20060926114453] > [support for request.local_net? to check if a request comes from a local network [3] > Fabian Buch **20060925210146 > (RFC1918 + localhost) including testcase > idea by Manveru, algorithm by Jonathan and implementation by Fabian > ] > [update to nitro/tc_dispatcher > manveru at weez-int.com**20060925210647] > [just a typo in nitro/tc_session > manveru at weez-int.com**20060925203734] > [updated to nitro/tc_render to reflect lots of changes in nitro-source > manveru at weez-int.com**20060925203647] > [updated nitro/tc_controller - will reflect the current ways of nitro a lot better > manveru at weez-int.com**20060925202935] > [updated nitro/tc_cgi (kashia added ruby-inline to make it faster) and some other fixes for it > manveru at weez-int.com**20060925202725] > [updated nitro/helper/tc_table > manveru at weez-int.com**20060925202300] > [add testcase for nitros parameter-handling (finally) [2] > Fabian Buch **20060925195011 > original by Manveru > ] > [gen part uses lib/ directory now > Fabian Buch **20060913094740 > so parts reside in lib/part/partname > public stuff of parts are still in public/part/partname/ > ] > [Removed scgi adapter. This is not maintained anymore by the original author. You are advised to use the mongrel adapter instead. > George Moschovitis **20061003203706] > [Added nitro restart command. > George Moschovitis **20060925135127] > [Nitro cluster command spawns correct number of app servders and implies daemon mode. > George Moschovitis **20060925131813] > [Fixed response cookies problem od the Mongrel adapter. > George Moschovitis **20060924202240] > [Added part callbacks for more structures and flexible part initialization. > George Moschovitis **20060923024859] > [Improved Global initialization, more flexible, in sync with session. > George Moschovitis **20060923024711] > [Improved handling of Session.cache_type for flexible initialization. > George Moschovitis **20060923022541] > [Updated configuration system to make more flexible, imporved drb sessions and Nitro initialization in general. Still some related work to do though (especially update the examples). Warning this patch will break your apps. Some text that will explain the small changes needed is forthcoming. > George Moschovitis **20060922184512] > [Improved nitro command to handle state server, added kill option. > George Moschovitis **20060921204412] > [Added some initial cache management (from the console) features. > George Moschovitis **20060921185724] > [Make YAML-properties with postgresql work again > manveru at weez-int.com**20060914091150] > [notice about new script/test :) > manveru at weez-int.com**20060912105803] > [Huge refactoring of script/test.rb, to use the new capability just 'gem install popen4' > manveru at weez-int.com**20060912070838] > [added tc_primary_key (which fails right now, like every good tc should ;) > manveru at weez-int.com**20060908022410] > [fix little bug with parse_timestamp (utils.rb) > manveru at weez-int.com**20060906093558] > [Og close_store fix > nusgnaf at gmail.com**20060826205335 > We use @store to maintain database connection when Og.thread_safe is false and @pool when Og.thread_safe is > true. Right now in close_store, we fall back to @store.close when @pool.empty? is true, that not correct, the > following patch fixes this. > ] > [fixed bug in tc_store.rb > Fabian Buch **20060828075201] > [making some other testcases pass again (issue with result of psql) > manveru at weez-int.com**20060825172828] > [making tc_build.rb pass again > manveru at weez-int.com**20060825142113] > [make aggregations work again (tc_aggregations_calculations) > manveru at weez-int.com**20060824235925] > [fixing STI > manveru at weez-int.com**20060824142441] > [adding some raise "Not implemented" in og/store.rb for empty methods > manveru at weez-int.com**20060824114541] > [minor change in tc_scope, still doesn't pass though > manveru at weez-int.com**20060822122540] > [changed script/test.rb so it runs the tests seperate (useful for og, if one test fails, not all others blow up) > manveru at weez-int.com**20060822090716] > [Fix scope bug in collection.rb, use count for finding number of joins_many relations > Jonathan Buch **20060912124344] > [Fix for deleting has_many belongs/refers_to relations > Jonathan Buch **20060911144233] > [fix for deleting belongs_to relationships > Jonathan Buch **20060911122205] > [add testcase for deleting relations > Jonathan Buch **20060911112315] > [More small og test fixes > Jonathan Buch **20060906214008] > [Fix more og testcases > Jonathan Buch **20060906211602] > [.save returns affected rows again, fix subclass creation in relation.rb > Jonathan Buch **20060906210953] > [Enable object annotating for custom styles in form attributes. > Jonathan Buch **20060903154923 > > Can be used like following: > > flash[:VERROR].errors.each do |sym,msg| > @obj.annotation sym => {:control_style => 'border:1px solid red;'} > end if flash[:VERROR] > ?> > > This traverses over validation errors and sets a red border around those > attributes with errors. > > ] > [Replace pk.inspects by quote(pk) > Jonathan Buch **20060903112405 > > Fixes problems with text/integer keys. > ] > [One line fix for 'Various Changes' patch > Jonathan Buch **20060903111201] > [Various changes > Jonathan Buch **20060902224949 > > * Revise resolve_polymorphic_relations, remove FIXME, change the > eval to const_set. > * Change symbol_to_class to return nil when no matching class was > found. > * Fix aggregation code, only use order_by when group_by is given. > ] > [minor fix for manage_classes > Jonathan Buch **20060902164458] > [remove ObjectSpace search in manage_classes when classes are specified > Jonathan Buch **20060902163817] > [OgKlass.create_with is now able to accept arrays for collections > Jonathan Buch **20060830180923] > [Fix bug with Pager and aggregations > Jonathan Buch **20060828221005 > > The option array got changed by the new aggregation code and in `paginate` the array got reused. Testcase also attached. > > This patch also makes an alias named :limit for :per_page. Makes paginate more compatible to other sql based functions. > ] > [minor testcase bugfixes > Jonathan Buch **20060827232013] > [only use transactions in og_delete when cascading is activated > Jonathan Buch **20060827231901] > [Automatic deletion of many2many relationships when one side gets removed > Jonathan Buch **20060827231733] > [add testcase for many to many relationships and deleting one side of the relationship > Jonathan Buch **20060827231057] > [prop_accessor -> attr_accessor > Jonathan Buch **20060827230931] > [fix taggable, reload needed when deleting tag > Jonathan Buch **20060827223558] > [change all prop_accessor to attr_accessor > Jonathan Buch **20060825230930] > [patch for many postgresql store errors, makes more tests pass > Jonathan Buch **20060825224327 > > Most importantly this changes the lookup rule for symbol_to_class in relation.rb, changes annotating of primary keys when invoked by `set_primary_key :name, String`. > > Minor enhanced test files, updated to new syntax etc. > ] > [Add transaction, commit, rollback to psql adapter > Jonathan Buch **20060825172522] > [Let `def aggregation` use `resolve_options` > Jonathan Buch **20060825155121 > > It duplicated functionality already available in `resolve_options` and didn't know about join tables etc. > ] > [Add Fabian Buch as contributor, rename nick Kashia to Jonathan > Jonathan Buch **20060831181201] > [Minor fixes. > George Moschovitis **20060912152127] > [removed unmatched require in server.rb > Fabian Buch **20060911155626] > [fixed call/answer (render.rb) to work correctly [2] > Fabian Buch **20060911155557] > [FeedHelper fix that lets its unit test pass again [2] > Fabian Buch **20060911155026] > [removing "nil"-Strings from has_many and refers_to controls [2] > Fabian Buch **20060911154851 > since you don't want "nil" for NULL in your database > ] > [webfile bugfix and to-be-improved tc_webfile.rb added [2] > Fabian Buch **20060911154544 > also: don't override files by default > and more logical file permissions > ] > [adding generator for parts (gen part) [2] > Fabian Buch **20060911153811 > > gen part partname > copies the given part to the current folder (so you should be > in your applications main folder) and moves the part's > public files to public/part/partname > ] > [let mongrels request_uri and query_string behave like the ones of webrick and fcgi > Fabian Buch **20060911205524] > [Cleaned up many files. > George Moschovitis **20060910192003] > [Test for :serializable_attributes in Manager#manageable? > Pangloss **20060909212814] > [Update Og::Cacheable to use facets 1.4.5 > Pangloss **20060909212038] > [Small fix in exclude patch to get rid fo the warning. > George Moschovitis **20060910084803] > [adding option[:exclude] to all_attributes in form helper > Fabian Buch **20060908182429 > now you can exclude single attribute > for example: > f.attributes(:exclude => :password) or > f.attributes(:exclude => [:password, :name]) > ] > [Allow label override in form helper. > George Moschovitis **20060909070515] > [Minor stuff. > George Moschovitis **20060909065751] > [Some improvements in caching and scaffolding. > George Moschovitis **20060907195840] > [Access server from context (req/res) > George Moschovitis **20060905200321] > [New cluster friendly nitro script. > George Moschovitis **20060905200208] > [fix latest Runner bugs > Fabian Buch **20060831134122 > ruby run.rb -m for example didn't work, it always used webrick unless Nitro.adapter was set > ] > [Some more fixes in the the new param parser, it works better with the router now. > George Moschovitis **20060831173030] > [FileControl and PasswordControl added > Fabian Buch **20060830191849] > [Added support for mongrel, execution modes and more in the nitro startup script (bin/nitro). > George Moschovitis **20060828212153] > [Minor stuff. > George Moschovitis **20060828171549] > [Alexander Lazic's Mongrel Adapter changes + mine > Fabian Buch **20060826102734 > it uses Mongrel::Configurator to setup mongrel > Logger for a more unified look > fixes trap to use stop() > ] > [Fixed 'true' bug in sub-elements. > George Moschovitis **20060826074839] > [Small improvements in taggable. > George Moschovitis **20060826074740] > [Improved sub-element functionality, add some comments to explain the usage. > George Moschovitis **20060825195559] > [Removed src dir, moved path into lib. Cleaner layout and trnsparently supports my new webapp deployment script. nice ;-) > George Moschovitis **20060824175446] > [tell evolution to accept the properties of its relatives > manveru at weez-int.com**20060824143623] > [Added more FIXMEs for rescue Object and removed a few > Jonathan Buch **20060822123730] > [removing spurious "p" > rff.rff at gmail.com**20060819140258] > [better error handling for helper.rb > ?rff.rff at gmail.com**20060819134639] > [Some improvements in the new scaffolding code, auto detection of per model controllers. > George Moschovitis **20060822150735] > [Misc small changes for improved robustness. > George Moschovitis **20060820093250] > [Various validation related fixes and small improvements. > George Moschovitis **20060817071240] > [Default error page sets 501 status > George Moschovitis **20060817060455] > [This patch contains the following changes: > rff.rff at gmail.com**20060729141757 > > M ./nitro/lib/nitro/helper/form.rb +8 > ] > [This patch refactors the code used in the scaffolded view to be usable as a single helper. > rff.rff at gmail.com**20060729141306 > It basically creates a div containing a list of li tags, each of one contains a message for each error in flash[:ERRORS] > > This patch contains the following changes: > > M ./nitro/lib/nitro/helper/form.rb +12 > ] > [Intuitive handling of text keys, allows code like u = User['gmosx'] and u = User[1] at the same time. > George Moschovitis **20060801203732] > [encode_url better handles index actions. > George Moschovitis **20060801203714] > [Some small fixes. > George Moschovitis **20060730132126] > [bugfix-glue-validate_value > bryan.a.soto at gmail.com**20060717205050 > Ticket #44: http://devlab.oree.ch/trac/glycerin/ticket/44 > Credit to matt DOT moriarity AT gmail DOT com. > ] > [fix conflict mongrel adapter > rff.rff at gmail.com**20060729105408] > [bugfix-nitro-mongrel-adapter > bryan.a.soto at gmail.com**20060717060648 > Fixes multi-part form processing, which was broken by my previous patch. Basically, image uploads work now for mongrel. > ] > [fix conflict on "undescore" typo > rff.rff at gmail.com**20060729104933] > [bugfix-nitro-ticket-43 > bryan.a.soto at gmail.com**20060711010702 > Fixed a bug/type as suggested by rff_rff AT yahoo DOT it > http://devlab.oree.ch/trac/glycerin/ticket/43 > ] > [bugfix-nitro-ticket-34 > bryan.a.soto at gmail.com**20060711010350 > Fixed as per billk AT cts DOT com suggestion on Ticket #34. > http://devlab.oree.ch/trac/glycerin/ticket/34 > ] > [navigation menu helper > rff_rff at yahoo.it**20060705193224 > This helper allows easy creation of xhtml/css based navigation menus, producing an xhtml that is suitable to be used with examples found at listamatic, and with automatic handling of "current page" highliting, setting proper xhtml for it. > > The helper adds two methods, one allows to create a menu like > menu_for(HomeController, Pages, Feed) > and the other gives more fine grained control through: > menu_from_hash('/home'=>'Home Page', '/pages'=>'Wiki', '/feed/rss'=>'RSS2.0') > > ] > [hack-enh-fcgi-rewind > bryan.a.soto at gmail.com**20060609220620 > A small hack to ensure that you can access the raw_body of a request, by converting the incoming stream to a StringIO if it doesn't respond to :rewind. > ] > [test-fix-og-tc_ez > bryan.a.soto at gmail.com**20060518001436 > Fixes up the ez testcase Manveru submitted to make it run and pass. > ] > [ez-fix for trueclass and testcase for it > m.fellinger at gmail.com**20060513111040] > [error-page-fix for source-preview > m.fellinger at gmail.com**20060513110945] > [test-fix-nitro-tc_render > bryan.a.soto at gmail.com**20060517223259 > Makes the TestController subclass Nitro::Controller so it get's the #encode_url method. > ] > [adds-some-blank-lines-to-og-tc_setup > bryan.a.soto at gmail.com**20060517222452] > [gabrielle-renzis-linefeeds > bryan.a.soto at gmail.com**20060517221725 > Switches line endings from Dos to Unix. > ] > [solves the conflict between repo and devlab (Og.setup now handles arguments in > rff.rff at gmail.com**20060729102534 > a saner way and crashes ASAP when there is no chance to recover > > ] > [crash-early Og.setup > surrender_it at yahoo.it**20060505123051 > This patch removed the Exception handling routine from Og.setup. > With the current code if an exception is raised during the execution of > the method there is no crash, but the crash will happen every time someone references Og.manager, cause that variable won't be initialized . > This patch makes Og.setup crash as soon as possible, thus allowing faster diagnostics. > > The patch also adds a simple test case for Og.setup, which seem not tested anywhere, but the test case may need some love for proper setup (it relies on glycerin as of now, cause loading CONFIG.rb seem to raise a strange exception related to mixed use of facets 1.3 and 1.0 on my box) > > ] > [better test logging > surrender_it at yahoo.it**20060505010206 > As of now tests for Og swallow every error ingormation while not in $DBG mode, > this one-line patch allows visualization of logged informations at WARN level and more, which has little impact on the visualization of the tests and still allows quick diagnostics while staying out of $DBG > ] > [add-ostruct-require > bryan.a.soto at gmail.com**20060512060511 > Adds missing ostruct require to testcase.rb. > ] > [nitro-proto-page > bryan.a.soto at gmail.com**20060510060546 > Updates the intro page with a link to the rubyforge page for examples to be downloaded as suggested by James Britt. > ] > [Made redirect_on_empty (buffer) true by default. > George Moschovitis **20060729083954] > [More fault tolerant populate_attributes. > George Moschovitis **20060727192802] > [Added objects_to_options helper. > George Moschovitis **20060726115346] > [Hack fixed fcgi/console Og polymorphic bug, will investigate later. > George Moschovitis **20060726115238] > [Minor fixes and cleanup. > George Moschovitis **20060723141916] > [fragments_fix > nusgnaf at gmail.com**20060720211817 > kill the usage of @@cache in nitro/lib/nitro/caching/framents.rb, > use self.cache instead. > ] > [Minor. > George Moschovitis **20060720182002] > [Improved postgreslq adapter. > George Moschovitis **20060720180657] > [form.fix > nusgnaf at gmail.com**20060721015451 > ensure we render all_attributes before we yield to block. > ] > [MysqlAdapter database creation > Jonas Pfenniger **20060720133458] > [More cleanup in Og files. > George Moschovitis **20060719214222] > [Small updates in source files, removed some obsolete files. > George Moschovitis **20060719203755] > [Better refactoring of last_insert_id/insert_sql. > George Moschovitis **20060719170347] > [Further Og adapter refactoring. > George Moschovitis **20060719163823] > [Mongrel large file fix. [fang sun] > George Moschovitis **20060719153444] > [Updated source. > George Moschovitis **20060718202542] > [Added postgresql.rb main adapter file. > George Moschovitis **20060718174745] > [Updated RELEASES. > George Moschovitis **20060718174725] > [More source/doc updates. > George Moschovitis **20060718155406] > [Misc doc/source updates. > George Moschovitis **20060718154516] > [Reimplemented postgresql adapter (not fully working yet). > George Moschovitis **20060717220903] > [Further refactoring/cleanup of the Og adapter code. > George Moschovitis **20060717220831] > [Small fixes in examples to make work with latest code. > George Moschovitis **20060717220750] > [Added special resolve_polymorphic behaviour to many_to_many/joins_many relations. > George Moschovitis **20060716164436] > [Even more intelligent dispatches, handles some more useful nice url cases. It rocks! > George Moschovitis **20060716160628] > [More flexible resolve_polymorphic_relations. > George Moschovitis **20060716154721] > [Check for join tables even if main table exists to be make Og more self-healing (and adaptive to changin schemas). > George Moschovitis **20060716145000] > [Polymorphic relations use again Owner::Class subclasses, but they are more flexible, there is no more the need for foreign_name declarations, plus cleaned up some Og code. > George Moschovitis **20060716130632] > [Virtualized table_already_exists? for mysql and sqlite3 to allow a single create table method for both adapters (!!!). > George Moschovitis **20060713172658] > [Reimplemented the sqlite adapter under the new model. > George Moschovitis **20060713171143] > [Remarkable refactoring/simplification of the Og adapter model. Cleaned up Mysql Adapter, more robust code. > George Moschovitis **20060713171040] > [Options control now takes reverse dictonary as a parameter, more useful. > George Moschovitis **20060712164255] > [MAJOR, BACKWARDS UNCOMPATIBLE CHANGE: Polymorphic classes are not nested. Ie now ArticleComment is created instead of Article::Comment. > George Moschovitis **20060710210736] > [Added rename_schema method in Og evolution. > George Moschovitis **20060710190814] > [Removed og evolution from og main dir to avoid confusion with store/evolution (renamed to dump.rb) > George Moschovitis **20060710155539] > [Misc form helper and controls improvements. > George Moschovitis **20060709164509] > [Improved StaticInclude compiler to handle recursive static includes (extremely useful). > George Moschovitis **20060709164423] > [Minor > George Moschovitis **20060709083138] > [Some fixes in the admin templates. > George Moschovitis **20060709082357] > [Removed old form helper code, added float control, some cleanup. > George Moschovitis **20060709080905] > [Added OptionsControl for attributes that take discreet options. > George Moschovitis **20060708082406] > [Updated contributors. > George Moschovitis **20060708082323] > [Extacted publishable.rb from controller.rb, added mount_path helper to publishable. [renzi] > George Moschovitis **20060708073814] > [Minor. > George Moschovitis **20060706204217] > [Small render fix. > George Moschovitis **20060706204140] > [Added support for nested controllers, cleaned up render (no base), updated admin part to work with changes. > George Moschovitis **20060706203550] > [Added initial versions of scaffold/controller, scaffold/model. > George Moschovitis **20060706155447] > [Changed render_template (for the moment uses a 'hack' implementation, but it works!) [james_b] > George Moschovitis **20060705193130] > [Og load/reload handle nil primary keys (by returning nil). > George Moschovitis **20060705181328] > [Simplified hidden method in xhtml helper. > George Moschovitis **20060701072425] > [Applied james britt's mongrel patch. > George Moschovitis **20060630190711] > [author backwards compatibility (atom) > Kashia Buch **20060622175214 > > Request by Fabian > ] > [Added handle_sql_exception for MysqlAdapter#create_table > Jonas Pfenniger **20060627135225] > [Added String to Car's property in tc_inheritance.rb > Jonas Pfenniger **20060627132219] > [Removed Glue::Flexob testcase since it does't exist anymore > Jonas Pfenniger **20060627132017] > [Fixed add_rule in dispatcher [james_b] > George Moschovitis **20060629151558] > [Removed paramix-fix, not needed in facets 1.4.3 > George Moschovitis **20060629151520] > [Argh and again argh, extend OpenStruct instead of OpenObject in FileTemplate to fix weird and NASTY eval bug. > George Moschovitis **20060626191414] > [consoleapp -> command. > George Moschovitis **20060626172152] > [Changes to make compatible with 1.4.2 > George Moschovitis **20060626163705] > [Added some new files. > George Moschovitis **20060620065144] > [Applied patches by neokolor at gmx.de, plus some minor stuff. [neokolor at gmx.de] > George Moschovitis **20060620064746] > [Deprecated RSS helper (use the new feed helper instead). > George Moschovitis **20060618102546] > [Updated spark and flare examples to use the feed helper. > George Moschovitis **20060618102431] > [Updated blog example to work with latest, slightly improved feed parser in the process. > George Moschovitis **20060618101830] > [Allow override of style in controls (+ minor fixes). > George Moschovitis **20060618090054] > [bugfix-mongrel-adapter-request-uri > bryan.a.soto at gmail.com**20060605211152 > Removes REQUEST_URI header manipulation and accomodates an upcoming change in Mongrel 0.3.13. An ugly class check... Lovely. > ] > [more-mongrel-adapter-fixes > bryan.a.soto at gmail.com**20060510222051 > Fixes up static file serving. > ] > [mongrel-fixes > bryan.a.soto at gmail.com**20060510060439 > Gives the Mongrel adapter some need updating. > ] > [Fixed Orderable to work with latest Og. > George Moschovitis **20060616082740] > [Allow for relative/absolute expiration of affected cached pages for extra flexibity. > George Moschovitis **20060614071336] > [Fixes in output caching (root setting). > George Moschovitis **20060614070409] > [Renamed evolution.rb to dump.rb to avoid confusion with the dynamic schema evolution feature. > George Moschovitis **20060614061620] > [Refactored og cloning to a separate file to keep entity.rb cleaner. > George Moschovitis **20060614061451] > [Added sendfile support to render. [jlambert] > George Moschovitis **20060613175624] > [Taggable tagstring_linked. > George Moschovitis **20060613175606] > [Small changes in FeedHelper. > George Moschovitis **20060613060649] > [Removed deprecated and buggy static include code from Template, the StaticInclude compiler is used instead. > George Moschovitis **20060612083733] > [Added {{..}} and #<..> aliases to #{R ..}. > George Moschovitis **20060609083834] > [Refactored webrick vcr functionality to a separate file. > George Moschovitis **20060609081950] > [Added again examples, flare, spark > George Moschovitis **20060607152438] > [Using the new building code, fixed the admin hasmany/joinsmany control. > George Moschovitis **20060607011350] > [Implemented collection build mode for efficient object relation initialization w/o excessive saves. > George Moschovitis **20060607005902] > [Small fix in template_for_action to avoid unhelpful error message on missing action (and symbol passed). > George Moschovitis **20060606075731] > [Added many new files. > George Moschovitis **20060605182624] > [Many many changes (New control system, Emit labels in the controls, Relation controls (hack fix), Show form errors in admin screens, Removed credit lines, Updated docs, Og.destroy_schema, and more...) under heavy construction. > George Moschovitis **20060605182411] > [Honour port in Mysql create/destroy [james_b] > George Moschovitis **20060528072603] > [Updated docs. > George Moschovitis **20060526094620] > [Minor. > George Moschovitis **20060522103204] > [Refactored and rationalized evolution support for sql stores. > George Moschovitis **20060522102946] > [Introduced new control system. Still under construction. > George Moschovitis **20060522064146] > [Fixes in validation and scaffolding. > George Moschovitis **20060521090718] > [After some more fixes tc_store.rb passes ;-) > George Moschovitis **20060520093243] > [Fixes in mysql insert. > George Moschovitis **20060520092051] > [Fixed finders. > George Moschovitis **20060520085837] > [Fixed some more problems. > George Moschovitis **20060520084729] > [Added join support, rationalized primary key setup. > George Moschovitis **20060520081153] > [Better support for non integer primary keys. > George Moschovitis **20060519074722] > [More fixes to support update. > George Moschovitis **20060519074304] > [Rationalized og_delete. > George Moschovitis **20060519072950] > [More fixes to support reading. > George Moschovitis **20060519072248] > [After some more changes, a small example works ;-) > George Moschovitis **20060519063007] > [Rationalized sql index definition: attr_accessor :age, Fixnum, :index => true, :pre_index => ..., :post_index => ... > George Moschovitis **20060519061721] > [Major Og rewrite, updating to the new attribute system, cleaning the code and migrating to the new adapter model. Many many more changes. In progress. > George Moschovitis **20060519060701] > [Removed alpha og stores. > George Moschovitis **20060518070101] > [Many changes to support the switch to attributes instead of properties. > George Moschovitis **20060518065907] > [Minor. > George Moschovitis **20060516150705] > [Moved examples, spark, flare to a separate repository. > George Moschovitis **20060516073246] > [Removed wee helper and example. Not really useful in Nitro, better use wee standalone + Og if you like Wee components (or wait for a Nitro solution). > George Moschovitis **20060516072823] > [Removed controller_name from Render, user controller.mount_path instead. > George Moschovitis **20060516072350] > [Fixed: dont overwrite already defined methods in the new scaffold code. > George Moschovitis **20060516071615] > [Improved R (encode_url) handles strings and entities. Redirect implicitly uses R. Form builder implicitly uses R for form actions. > George Moschovitis **20060516071508] > [Fixed name_to_jsfile (absolute url). > George Moschovitis **20060515065439] > [Reenabled format in Logger. > George Moschovitis **20060513042251] > [Added some :nodoc: all to cleanup generated RDocs. > George Moschovitis **20060513034929] > [Bumbed version number in many files. > George Moschovitis **20060512154849] > [Wrote a detailed parts howto in RDoc form in parts.rb as requested by Jonas. To be improved after community feedback. > George Moschovitis **20060512153754] > [Initial code for the new scaffolding system, *very* under construction, ignore for the moment. > George Moschovitis **20060511101456] > [Added a model macro to controllers that links related classes. At the moment it is used in the sweeper do delete cached pages from the linked controller base directory. > George Moschovitis **20060510102836] > [Fixed Session.current and Controller.current > George Moschovitis **20060508075645] > [Store current context in a thread local variable, accesible through Context.current > George Moschovitis **20060507160715] > [Removed glue/attribute, use Facet's cattr instead. Updated nitro/og source to make compatible. > George Moschovitis **20060507085703] > [Added script adapter file. > George Moschovitis **20060507062034] > [Removed flexob and references to it, use Facet's OpenObject instead. > George Moschovitis **20060507061555] > [Renamed to ScriptAdapter, keep ConsoleAdapter alias. > George Moschovitis **20060506103921] > [Yeah, the ConsoleAdapter kinda works now ;-) > George Moschovitis **20060506102010] > [Introduced new nitro command/runner that will replace the current spaghetti code. Based on facetes Console::Command. Also introduced the ConsoleAdapter. > George Moschovitis **20060506095503] > [Removed accumulate (in facets). > George Moschovitis **20060506080052] > [Some small updates. > George Moschovitis **20060506075526] > [TAG 0.30.0 > George Moschovitis **20060506075053] > Patch bundle hash: > 302309cabc40dc12ab92aefe103721d5f8f494d1 > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://www.gmosx.com http://www.nitroproject.org From lasso at lassoweb.se Sun Nov 5 08:13:25 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Sun, 05 Nov 2006 14:13:25 +0100 Subject: [Nitro] Whitespace In-Reply-To: References: <3ff63f9b0610310436p6f0dff1bha2e45423da7bba9d@mail.gmail.com> <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> <454C5AC1.4060302@lassoweb.se> <454DABBF.4070903@lassoweb.se> Message-ID: <454DE375.1090006@lassoweb.se> Hi, here you go. /lasso ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ George Moschovitis skrev: > Hello Lars, > > the patch seems ok, please send this as an attachment (zipped/or > targz'ed) Gmail seems to f*ck up darcs patches. > > thanks! > -g. -------------- next part -------------- A non-text attachment was scrubbed... Name: compiler_doctype_fix.tar.gz Type: application/gzip Size: 14208 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061105/3737438f/attachment.bin From george.moschovitis at gmail.com Sun Nov 5 08:34:58 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 5 Nov 2006 15:34:58 +0200 Subject: [Nitro] Whitespace In-Reply-To: <454DE375.1090006@lassoweb.se> References: <37728.192.176.230.1.1162307759.squirrel@webmail.lassoweb.se> <3ff63f9b0610310837p11a479dof825912de6453634@mail.gmail.com> <45479706.3020300@lassoweb.se> <454C5AC1.4060302@lassoweb.se> <454DABBF.4070903@lassoweb.se> <454DE375.1090006@lassoweb.se> Message-ID: > here you go. thanks! -g. -- http://gmosx.com/com http://nitroproject.org From m.fellinger at gmail.com Sun Nov 5 17:12:05 2006 From: m.fellinger at gmail.com (Michael Fellinger) Date: Mon, 6 Nov 2006 07:12:05 +0900 Subject: [Nitro] Patches In-Reply-To: References: Message-ID: <9c00d3e00611051412g2f399333ydc0247e9d9701b69@mail.gmail.com> On 11/5/06, George Moschovitis wrote: > Dear devs, > > if anyone has any patches to send me before 0.40.0, now is the time! > (I am aware of the pending params patch of Jonathan). Manv, what about > your autoreload patch? the autoreload has to wait until after the release, sorry, but i don't want to introduce more problems than it solves ;) > > regards, > George. > > -- > http://www.gmosx.com > http://www.nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From george.moschovitis at gmail.com Mon Nov 6 06:24:22 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 6 Nov 2006 13:24:22 +0200 Subject: [Nitro] Patches In-Reply-To: <9c00d3e00611051412g2f399333ydc0247e9d9701b69@mail.gmail.com> References: <9c00d3e00611051412g2f399333ydc0247e9d9701b69@mail.gmail.com> Message-ID: > the autoreload has to wait until after the release, sorry, but i don't > want to introduce more problems than it solves ;) Ok. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 6 07:50:03 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 6 Nov 2006 14:50:03 +0200 Subject: [Nitro] System -> Admin Message-ID: Dear devs, I am thinking about keeping the old name for the auto-admin part before the (imminent) 0.40.0 release. I will rename it from System again to Admin. This will be one less migration hurdle. What do you think? -g. -- http://gmosx.com/blog http://nitroproject.org From jeff.barczewski at gmail.com Mon Nov 6 11:48:02 2006 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Mon, 6 Nov 2006 10:48:02 -0600 Subject: [Nitro] Whitespace - xhtml doctype - are you using REXML sax2 parser/listener to read doctype? I had found a bug in REXML Message-ID: <19cda190611060848x3016c802g433febc0c3332982@mail.gmail.com> On 11/4/06, Lars Olsson wrote: > > Hello, > > I found the bug. In /nitro/compiler/elements.rb the doctype method is > missing. It should be added. The one from /nitro/compiler/morphing.rb > works just fine: > > (from nitro/compiler/morphing.rb, Listener class) > > def doctype(name, pub_sys, long_name, uri) > @buffer << "" > end > > (you might just want to add a newline at the end. DOCTYPEs generally > stand on its own line.) > > Btw, The fix above works with the default transformation pipeline. There > *might* be some other compiler classes (not in the default pipeline) > that need that method added too. > > Sincerely > > /lasso > > > ________________________________________ > Lars Olsson > lasso at lassoweb.se > http://www.lassoweb.se/ > > > > George Moschovitis skrev: > >> No problem there. REXML already supports DOCTYPEs. The problem is that > >> Nitro strips the DOCTYPE *after* REXML has processed the template. > Since > >> some XML tools require this type of information in order to function > >> they are unable to parse pages rendered by Nitro. This is *very* bad in > >> my opinion (luckily there are workarounds). > > > George and Lars, Are you using the REXML sax2 parser/listener to read doctypes? If so, then I would be suprised if the above code (using REXML 3.1.5 or less) would work. I also use REXML and was trying to read the doctype using the sax2 parser/listener and after much debugging I found that there were a few bugs in REXML code that prevented it from ever calling the doctype method. Further investigation showed that there were no test cases around this either. I had tested on 3.1.3 (that came with Ruby 1.8.4) and the latest version 3.1.5 but defect exists in both places. So I put together a test case for REXML and submitted a patch (fix) along with my bug report about a week ago, but no one from REXML has responded or applied it. http://www.germane-software.com/projects/rexml/ticket/92 So I was just curious how this could work for you with an unpatched REXML, unless maybe you weren't using the sax2 parser/listener. Also the documentation around the sax2 listener for doctype is a little vague regarding the long_name and uri. I believe the intention of the API is that the long_name and uri would be provided without the surrounding quotes. So this is the way my patch is written (to provide the contents from inside of the quotes) when doctype listener method is called. If this is correct then your above Nitro fix should turn around and quote those two variables when outputting. Anyway, I just wanted to ask whether you were indeed using sax2 parser/listener and if so share my experience and patch if it would be useful. If you don't have the same issue then could you tell me what parser/listener you are using, etc. Blessings, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061106/89bbebb2/attachment.html From john at oxyliquit.de Mon Nov 6 11:49:22 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Mon, 6 Nov 2006 17:49:22 +0100 Subject: [Nitro] System -> Admin In-Reply-To: References: Message-ID: <20061106164921.GA32163@oxyliquit.de> Hi, > I am thinking about keeping the old name for the auto-admin part > before the (imminent) 0.40.0 release. I will rename it from System > again to Admin. This will be one less migration hurdle. > > What do you think? yes, good idea Jo From lasso at lassoweb.se Mon Nov 6 14:41:37 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Mon, 06 Nov 2006 20:41:37 +0100 Subject: [Nitro] Whitespace - xhtml doctype - are you using REXML sax2 parser/listener to read doctype? I had found a bug in REXML In-Reply-To: <19cda190611060848x3016c802g433febc0c3332982@mail.gmail.com> References: <19cda190611060848x3016c802g433febc0c3332982@mail.gmail.com> Message-ID: <454F8FF1.1000107@lassoweb.se> Hi! No, Nitro uses REXML::Parsers::StreamParser, not REXML::Parsers::Sax2Parser. The StreamParser seems to work ok. Kindly /lasso ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ > Jeff Barczewski skrev: > George and Lars, > > Are you using the REXML sax2 parser/listener to read doctypes? > > If so, then I would be suprised if the above code (using REXML 3.1.5 or > less) would work. I also use REXML and was trying to read the doctype > using the sax2 parser/listener and after much debugging I found that > there were a few bugs in REXML code that prevented it from ever calling > the doctype method. Further investigation showed that there were no test > cases around this either. I had tested on 3.1.3 (that came with Ruby > 1.8.4) and the latest version 3.1.5 but defect exists in both places. > > So I put together a test case for REXML and submitted a patch (fix) > along with my bug report about a week ago, but no one from REXML has > responded or applied it. > http://www.germane-software.com/projects/rexml/ticket/92 > > So I was just curious how this could work for you with an unpatched > REXML, unless maybe you weren't using the sax2 parser/listener. > > Also the documentation around the sax2 listener for doctype is a little > vague regarding the long_name and uri. I believe the intention of the > API is that the long_name and uri would be provided without the > surrounding quotes. So this is the way my patch is written (to provide > the contents from inside of the quotes) when doctype listener method is > called. If this is correct then your above Nitro fix should turn around > and quote those two variables when outputting. > > Anyway, I just wanted to ask whether you were indeed using sax2 > parser/listener and if so share my experience and patch if it would be > useful. If you don't have the same issue then could you tell me what > parser/listener you are using, etc. > > Blessings, > > Jeff > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From transfire at gmail.com Mon Nov 6 15:55:49 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Mon, 06 Nov 2006 20:55:49 -0000 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> Message-ID: <1162846549.399984.109300@i42g2000cwa.googlegroups.com> George Moschovitis wrote: > > harp:~ > cat a.rb > > ... > > :baz} > > > > Now this implementatin leaves out some of the needed shortcuts (like > > implied class annotation) and it also leaves out the BIG issue of > > inheritance, but those can of course can be worked in. The main thing > > here is the simplicty of the interface. I realize it's a big change but > > I think Ara has a point. The simplicy, uniformity and consistancy has > > it's own merits over the elegance of the magic dot notation. > > Well I like this simplicity as well. Could you introduce the > inheritance feature? > And what is implied class annotation? I would like to replace nitro's > annotation with this simpler version. If you remember, I was always > worried about the performance (and complexity) issues of the current > implementation. Your wish is my command. Here it is. The just about the most straight-foward and concise implementation of Annotations possible. I have only two outstanding issues with it. 1) Whether to use the global variable or not (see remarks for the difference); and 2) Whether #heritage should remain it's own method or be integrated into #ann itself, or perhaps just rename it? FYI heritage returns the complete inheritance chain of annotations. I'm sure other improvments are possible. Please let me know it you have any suggestions. Thanks. # --- ann.rb require 'facets/core/hash/to_h' require 'facets/core/hash/symbolize_keys' require 'facets/core/hash/op_add' # By using a global veriable rather the definining a class instance variable # for each class/module, it is possible to quicky scan all annotations for the # entire system. To do the same without this would require scanning through # the ObjectSpace. (Still which is better?) #$annotations = Hash.new { |h,k| h[k] = {} } class Module def annotations #$annotations[self] # global? @annotations ||= {} end def heritage(ref) ref = ref.to_sym ancestors.inject({}) { |memo, ancestor| ancestor.annotations[ref] ||= {} ancestor.annotations[ref] + memo } end # Set or read annotations. def ann( ref, keys_or_class=nil, keys=nil ) return heritage(ref) unless keys_or_class or keys if Class === keys_or_class keys ||= {} keys[:class] = keys_or_class else keys = keys_or_class end if Hash === keys ref = ref.to_sym annotations[ref] ||= {} annotations[ref].update(keys.symbolize_keys) else key = keys.to_sym heritage(ref)[key] end end # To change an annotation's value in place for a given class or module # it first must be duplicated, otherwise the change may effect annotations # in the class or module's ancestors. def ann!( ref, keys_or_class=nil, keys=nil ) return heritage(ref) unless keys_or_class or keys if Class === keys_or_class keys ||= {} keys[:class] = keys_or_class else keys = keys_or_class end if Hash === keys ref = ref.to_sym annotations[ref] ||= {} annotations[ref].update(keys.symbolize_keys) else key = keys.to_sym annotations[ref][key] = heritage(ref)[key].dup end end end From nusgnaf at gmail.com Tue Nov 7 05:00:19 2006 From: nusgnaf at gmail.com (Fang Sun) Date: Tue, 7 Nov 2006 18:00:19 +0800 Subject: [Nitro] System -> Admin In-Reply-To: <20061106164921.GA32163@oxyliquit.de> References: <20061106164921.GA32163@oxyliquit.de> Message-ID: <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> +1 On 11/7/06, Jonathan Buch wrote: > Hi, > > > I am thinking about keeping the old name for the auto-admin part > > before the (imminent) 0.40.0 release. I will rename it from System > > again to Admin. This will be one less migration hurdle. > > > > What do you think? > > yes, good idea > > Jo > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From george.moschovitis at gmail.com Tue Nov 7 13:10:41 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 7 Nov 2006 20:10:41 +0200 Subject: [Nitro] System -> Admin In-Reply-To: <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> Message-ID: Ok, please give me a couple more days to package 0.40.0. I have some unexpected extra work for a client these days. -g. On 11/7/06, Fang Sun wrote: > +1 > > On 11/7/06, Jonathan Buch wrote: > > Hi, > > > > > I am thinking about keeping the old name for the auto-admin part > > > before the (imminent) 0.40.0 release. I will rename it from System > > > again to Admin. This will be one less migration hurdle. > > > > > > What do you think? > > > > yes, good idea > > > > Jo > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 7 13:12:15 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 7 Nov 2006 20:12:15 +0200 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <1162846549.399984.109300@i42g2000cwa.googlegroups.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <1162846549.399984.109300@i42g2000cwa.googlegroups.com> Message-ID: Thanks! I will have a look at this imediately after the 0.40.0 release (will happen this week) -g. On 11/6/06, transfire at gmail.com wrote: > > George Moschovitis wrote: > > > harp:~ > cat a.rb > > > ... > > > :baz} > > > > > > Now this implementatin leaves out some of the needed shortcuts (like > > > implied class annotation) and it also leaves out the BIG issue of > > > inheritance, but those can of course can be worked in. The main thing > > > here is the simplicty of the interface. I realize it's a big change but > > > I think Ara has a point. The simplicy, uniformity and consistancy has > > > it's own merits over the elegance of the magic dot notation. > > > > Well I like this simplicity as well. Could you introduce the > > inheritance feature? > > And what is implied class annotation? I would like to replace nitro's > > annotation with this simpler version. If you remember, I was always > > worried about the performance (and complexity) issues of the current > > implementation. > > Your wish is my command. Here it is. The just about the most > straight-foward and concise implementation of Annotations possible. I > have only two outstanding issues with it. 1) Whether to use the global > variable or not (see remarks for the difference); and 2) Whether > #heritage should remain it's own method or be integrated into #ann > itself, or perhaps just rename it? FYI heritage returns the complete > inheritance chain of annotations. > > I'm sure other improvments are possible. Please let me know it you have > any suggestions. Thanks. > > > # --- ann.rb > > require 'facets/core/hash/to_h' > require 'facets/core/hash/symbolize_keys' > require 'facets/core/hash/op_add' > > # By using a global veriable rather the definining a class instance > variable > # for each class/module, it is possible to quicky scan all annotations > for the > # entire system. To do the same without this would require scanning > through > # the ObjectSpace. (Still which is better?) > > #$annotations = Hash.new { |h,k| h[k] = {} } > > class Module > > def annotations > #$annotations[self] # global? > @annotations ||= {} > end > > def heritage(ref) > ref = ref.to_sym > ancestors.inject({}) { |memo, ancestor| > ancestor.annotations[ref] ||= {} > ancestor.annotations[ref] + memo > } > end > > # Set or read annotations. > > def ann( ref, keys_or_class=nil, keys=nil ) > return heritage(ref) unless keys_or_class or keys > > if Class === keys_or_class > keys ||= {} > keys[:class] = keys_or_class > else > keys = keys_or_class > end > > if Hash === keys > ref = ref.to_sym > annotations[ref] ||= {} > annotations[ref].update(keys.symbolize_keys) > else > key = keys.to_sym > heritage(ref)[key] > end > end > > # To change an annotation's value in place for a given class or > module > # it first must be duplicated, otherwise the change may effect > annotations > # in the class or module's ancestors. > > def ann!( ref, keys_or_class=nil, keys=nil ) > return heritage(ref) unless keys_or_class or keys > > if Class === keys_or_class > keys ||= {} > keys[:class] = keys_or_class > else > keys = keys_or_class > end > > if Hash === keys > ref = ref.to_sym > annotations[ref] ||= {} > annotations[ref].update(keys.symbolize_keys) > else > key = keys.to_sym > annotations[ref][key] = heritage(ref)[key].dup > end > end > > end > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From dan at tastapod.com Wed Nov 8 05:25:34 2006 From: dan at tastapod.com (Dan North) Date: Wed, 08 Nov 2006 10:25:34 +0000 Subject: [Nitro] Dedicated Hosting In-Reply-To: References: <45492C18.6000702@tastapod.com> Message-ID: <4551B09E.2030402@tastapod.com> 1. Edit /etc/apt/sources.list to say "testing" instead of "stable". 2. Run apt-get dist-upgrade. 3. Then, because I'm paranoid, I reboot. To answer your other question, I can install and build anything I like. It's like having your own linux server with full root access. So I've set up a bunch of accounts for people, locked it down to only allow key-authenticated ssh, disabled /bin/su so you can only use sudo, set up a firewall (using firehol), it's great fun! Basically I have free run of the server. And if I make too much of a mess, I can always blast it and start over with a fresh image. The best part is the warm glow I get when my local cable company messes up my broadband connection /yet again/ and I know that my server is still available out there. Cheers, Dan George Moschovitis wrote: >>> (which I immediately dist-upgraded to debian/testing). >>> > > which command do you use for this? > > -g. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061108/66b4f5e9/attachment.html From fabian at fabian-buch.de Wed Nov 8 05:28:36 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Wed, 8 Nov 2006 11:28:36 +0100 Subject: [Nitro] System -> Admin In-Reply-To: References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> Message-ID: <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> Am 07.11.2006 um 19:10 schrieb George Moschovitis: > please give me a couple more days to package 0.40.0. I have some > unexpected extra work for a client these days. Please take a few more days for the release and include Jonathan's params handling in 0.40.0 Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Wed Nov 8 07:49:35 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 8 Nov 2006 14:49:35 +0200 Subject: [Nitro] System -> Admin In-Reply-To: <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> Message-ID: I will try! -g. On 11/8/06, Fabian Buch wrote: > > Am 07.11.2006 um 19:10 schrieb George Moschovitis: > > please give me a couple more days to package 0.40.0. I have some > > unexpected extra work for a client these days. > > Please take a few more days for the release and include Jonathan's > params handling in 0.40.0 > > Fabian > > > > > > -- > Nitro Q&A: http://oxyliquit.de/ > Blog: http://blog.fabian-buch.de > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Fri Nov 10 03:26:21 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 10 Nov 2006 10:26:21 +0200 Subject: [Nitro] Params in repo Message-ID: Dear devs, it looks like jonathan's params patch works great, so I added this in the repo. Seems that all missing bits are in place for the release of Nitro 0.40.0 ;-) There is some minor work to be done on the example, tests and docs. regards, -g. -- http://gmosx.com/blog http://nitroproject.org From aglarond at gmail.com Fri Nov 10 05:50:20 2006 From: aglarond at gmail.com (Dimitri Aivaliotis) Date: Fri, 10 Nov 2006 11:50:20 +0100 Subject: [Nitro] System -> Admin In-Reply-To: <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> Message-ID: <55c107bf0611100250v164bc932x8e74706468af0dc8@mail.gmail.com> On 11/8/06, Fabian Buch wrote: > > > Please take a few more days for the release and include Jonathan's > params handling in 0.40.0 > Let me voice my opinion here, too. :) Jonathan's patch is comprehensive in that he provides for both methods of handling the parameters. If one wishes to use a different way, it's only a setting away. His patch helped me to cleanly handle a problem I had in a project last night. The current handling in 0.31.0 just didn't fit my needs. He's also included documentation and tests, so I really don't see anything standing in the way of applying it. - Dimitri -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061110/9ec07ee1/attachment.html From george.moschovitis at gmail.com Fri Nov 10 06:34:32 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 10 Nov 2006 13:34:32 +0200 Subject: [Nitro] System -> Admin In-Reply-To: <55c107bf0611100250v164bc932x8e74706468af0dc8@mail.gmail.com> References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> <55c107bf0611100250v164bc932x8e74706468af0dc8@mail.gmail.com> Message-ID: As I already said, Jonathan's patch is APPLIED. Grab the latest repo version for some final testing! big thanks to Jonathan for his hard work btw :) -g. On 11/10/06, Dimitri Aivaliotis wrote: > On 11/8/06, Fabian Buch wrote: > > > > Please take a few more days for the release and include Jonathan's > > params handling in 0.40.0 > > > > Let me voice my opinion here, too. :) > > Jonathan's patch is comprehensive in that he provides for both methods of > handling the parameters. If one wishes to use a different way, it's only a > setting away. His patch helped me to cleanly handle a problem I had in a > project last night. The current handling in 0.31.0 just didn't fit my > needs. > > He's also included documentation and tests, so I really don't see anything > standing in the way of applying it. > > - Dimitri > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Fri Nov 10 06:35:26 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 10 Nov 2006 13:35:26 +0200 Subject: [Nitro] System -> Admin In-Reply-To: References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> <55c107bf0611100250v164bc932x8e74706468af0dc8@mail.gmail.com> Message-ID: > As I already said, Jonathan's patch is APPLIED. Grab the latest repo > version for some final testing! I just made my preferred way the default :) -g. -- http://gmosx.com/blog http://nitroproject.org From aglarond at gmail.com Fri Nov 10 07:18:43 2006 From: aglarond at gmail.com (Dimitri Aivaliotis) Date: Fri, 10 Nov 2006 13:18:43 +0100 Subject: [Nitro] System -> Admin In-Reply-To: References: <20061106164921.GA32163@oxyliquit.de> <716700c90611070200w1e7f079nf57ac15ed00ec88a@mail.gmail.com> <86B56CE2-94A5-47CE-BB73-F98260BE1026@fabian-buch.de> <55c107bf0611100250v164bc932x8e74706468af0dc8@mail.gmail.com> Message-ID: <55c107bf0611100418sdde5bd3me62e27abdbe79afe@mail.gmail.com> On 11/10/06, George Moschovitis wrote: > > As I already said, Jonathan's patch is APPLIED. Grab the latest repo > version for some final testing! Sorry about that then. It takes entirely too long for a mail to get out to the list... Be assured, had I read your mail before I sent my last message, I wouldn't have written it. :) > big thanks to Jonathan for his hard work btw :) > Yes, *big* thanks. - Dimitri -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061110/ea513561/attachment.html From john at oxyliquit.de Fri Nov 10 08:32:06 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 10 Nov 2006 14:32:06 +0100 Subject: [Nitro] Params in repo In-Reply-To: References: Message-ID: <20061110133203.GA3811@oxyliquit.de> Hi, > it looks like jonathan's params patch works great, so I added this in > the repo. Seems that all missing bits are in place for the release of > Nitro 0.40.0 ;-) There is some minor work to be done on the example, > tests and docs. Great ^____^ Thank you very much for the inclusion and bearing with my rantings. ;D Jo From george.moschovitis at gmail.com Fri Nov 10 10:50:31 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 10 Nov 2006 17:50:31 +0200 Subject: [Nitro] Params in repo In-Reply-To: <20061110133203.GA3811@oxyliquit.de> References: <20061110133203.GA3811@oxyliquit.de> Message-ID: > Thank you very much for the inclusion and bearing with my rantings. ;D nah, thanks for your great work :) -g. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Fri Nov 10 11:08:13 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 10 Nov 2006 18:08:13 +0200 Subject: [Nitro] Test Message-ID: Did someone add this test in tc_logger recently? # bug: Binding.of_caller thinks Logger is the caller. a = 14 b = 13 Logger.trace 'a * b' assert_equal(" INFO: hello\nDEBUG: a * b = 182\n", @io.string) -g. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Fri Nov 10 12:05:46 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 10 Nov 2006 19:05:46 +0200 Subject: [Nitro] Nitro build system Message-ID: Dear devs, because I cannot understand which version of Reap/Sow/Roll/Facets works with each other to build nitro, I just added a collection of gemspecs and updated the build script: ruby script/build.rb creates the distirbution in the dist directory. I would appreciate it if you could test this (and the rest of Nitro) over the weekend. If no problems are found, I will release it on Monday. regards, George. -- http://gmosx.com/blog http://nitroproject.org From fabian at fabian-buch.de Sat Nov 11 04:31:35 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Sat, 11 Nov 2006 10:31:35 +0100 Subject: [Nitro] Nitro build system In-Reply-To: References: Message-ID: Am 10.11.2006 um 18:05 schrieb George Moschovitis: > ruby script/build.rb > I would appreciate it if you could test this (and the rest of Nitro) > over the weekend. If no problems are found, I will release it on > Monday. Two things I found: 1. I only had facets 1.4.5 which worked good with nitro all the time, but for installing nitro I had to install 1.4.3 now. Not a big issue though. 2. "nitro requires RedCloth >= 3.1.3", but lates version is 3.0.4 (see http://rubyforge.org/projects/redcloth/) Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From fabian at fabian-buch.de Sat Nov 11 04:37:54 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Sat, 11 Nov 2006 10:37:54 +0100 Subject: [Nitro] Test In-Reply-To: References: Message-ID: <29534F2E-CA45-4401-8C29-A8A08FAD9E2A@fabian-buch.de> Am 10.11.2006 um 17:08 schrieb George Moschovitis: > Did someone add this test in tc_logger recently? > > # bug: Binding.of_caller thinks Logger is the caller. > a = 14 > b = 13 > Logger.trace 'a * b' > assert_equal(" INFO: hello\nDEBUG: a * b = 182\n", @io.string) I don't think so. See "darcs annotate glue/test/glue/ tc_logger.rb" (you're the only one who touched this file). Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From fabian at fabian-buch.de Sat Nov 11 05:13:43 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Sat, 11 Nov 2006 11:13:43 +0100 Subject: [Nitro] Nitro build system In-Reply-To: References: Message-ID: Facets 1.4.3 might be a problem for previous users of Nitro, since Nitro 0.31.0 was released with requirements for Facets 1.4.5. I'd suggest using facets 1.4.5 (gem install facets --version '= 1.4.5') Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Sun Nov 12 04:50:26 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 12 Nov 2006 11:50:26 +0200 Subject: [Nitro] Nitro build system In-Reply-To: References: Message-ID: Ok, thanks for the info! -g. On 11/11/06, Fabian Buch wrote: > Facets 1.4.3 might be a problem for previous users of Nitro, since > Nitro 0.31.0 was released with requirements for Facets 1.4.5. I'd > suggest using facets 1.4.5 (gem install facets --version '= 1.4.5') > > Fabian > > > > > > -- > Nitro Q&A: http://oxyliquit.de/ > Blog: http://blog.fabian-buch.de > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Sun Nov 12 06:18:54 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 12 Nov 2006 13:18:54 +0200 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <1162846549.399984.109300@i42g2000cwa.googlegroups.com> Message-ID: Hello Tom, I had a look at your new annotation implementation. The main thing that concerns me is how an annotation lookup relates to a plain hash lookup. In Nitro and Og we are mainly reading the annotation (the writes are very infrequent, typically on application startup). I am worried that the search in heritage on every read introduces a time penalty. Perhaps you should copy annotations from the heritage in the current class to avoid the 'deep' search the next time, something like a cache. You could set a dirty flag on annotation write and purge this annotation 'cache'. I guess we should profile the current annotation lookup against a plain hash lookup. Perhaps the speed penalty is not much after all. About the global variable. I don't mind having global variables but why would we need to scan all annotations? BTW, please notice that the code in 'ann' and 'ann!' is essentially the same, perhaps you could refactor this? In any case, thanks for your hard work. I really hope we can have the annotation issue resolved the coming week, so I can port Nitro to the new implementation. regards, George On 11/7/06, George Moschovitis wrote: > Thanks! > > I will have a look at this imediately after the 0.40.0 release (will > happen this week) > > -g. > > On 11/6/06, transfire at gmail.com wrote: > > > > George Moschovitis wrote: > > > > harp:~ > cat a.rb > > > > ... > > > > :baz} > > > > > > > > Now this implementatin leaves out some of the needed shortcuts (like > > > > implied class annotation) and it also leaves out the BIG issue of > > > > inheritance, but those can of course can be worked in. The main thing > > > > here is the simplicty of the interface. I realize it's a big change but > > > > I think Ara has a point. The simplicy, uniformity and consistancy has > > > > it's own merits over the elegance of the magic dot notation. > > > > > > Well I like this simplicity as well. Could you introduce the > > > inheritance feature? > > > And what is implied class annotation? I would like to replace nitro's > > > annotation with this simpler version. If you remember, I was always > > > worried about the performance (and complexity) issues of the current > > > implementation. > > > > Your wish is my command. Here it is. The just about the most > > straight-foward and concise implementation of Annotations possible. I > > have only two outstanding issues with it. 1) Whether to use the global > > variable or not (see remarks for the difference); and 2) Whether > > #heritage should remain it's own method or be integrated into #ann > > itself, or perhaps just rename it? FYI heritage returns the complete > > inheritance chain of annotations. > > > > I'm sure other improvments are possible. Please let me know it you have > > any suggestions. Thanks. > > > > > > # --- ann.rb > > > > require 'facets/core/hash/to_h' > > require 'facets/core/hash/symbolize_keys' > > require 'facets/core/hash/op_add' > > > > # By using a global veriable rather the definining a class instance > > variable > > # for each class/module, it is possible to quicky scan all annotations > > for the > > # entire system. To do the same without this would require scanning > > through > > # the ObjectSpace. (Still which is better?) > > > > #$annotations = Hash.new { |h,k| h[k] = {} } > > > > class Module > > > > def annotations > > #$annotations[self] # global? > > @annotations ||= {} > > end > > > > def heritage(ref) > > ref = ref.to_sym > > ancestors.inject({}) { |memo, ancestor| > > ancestor.annotations[ref] ||= {} > > ancestor.annotations[ref] + memo > > } > > end > > > > # Set or read annotations. > > > > def ann( ref, keys_or_class=nil, keys=nil ) > > return heritage(ref) unless keys_or_class or keys > > > > if Class === keys_or_class > > keys ||= {} > > keys[:class] = keys_or_class > > else > > keys = keys_or_class > > end > > > > if Hash === keys > > ref = ref.to_sym > > annotations[ref] ||= {} > > annotations[ref].update(keys.symbolize_keys) > > else > > key = keys.to_sym > > heritage(ref)[key] > > end > > end > > > > # To change an annotation's value in place for a given class or > > module > > # it first must be duplicated, otherwise the change may effect > > annotations > > # in the class or module's ancestors. > > > > def ann!( ref, keys_or_class=nil, keys=nil ) > > return heritage(ref) unless keys_or_class or keys > > > > if Class === keys_or_class > > keys ||= {} > > keys[:class] = keys_or_class > > else > > keys = keys_or_class > > end > > > > if Hash === keys > > ref = ref.to_sym > > annotations[ref] ||= {} > > annotations[ref].update(keys.symbolize_keys) > > else > > key = keys.to_sym > > annotations[ref][key] = heritage(ref)[key].dup > > end > > end > > > > end > > > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > > -- > http://gmosx.com/blog > http://nitroproject.org > -- http://gmosx.com/blog http://nitroproject.org From transfire at gmail.com Sun Nov 12 15:21:53 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 12 Nov 2006 20:21:53 -0000 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <1162846549.399984.109300@i42g2000cwa.googlegroups.com> Message-ID: <1163362913.122731.7560@h48g2000cwc.googlegroups.com> George Moschovitis wrote: > Hello Tom, > > I had a look at your new annotation implementation. The main > thing that concerns me is how an annotation lookup relates to > a plain hash lookup. Cool. I'm glad you were able to have a look. > In Nitro and Og we are mainly reading the > annotation (the writes are very infrequent, typically on > application startup). I am worried that the search in heritage > on every read introduces a time penalty. Perhaps you should copy > annotations from the heritage in the current class to avoid the > 'deep' search the next time, something like a cache. You could > set a dirty flag on annotation write and purge this annotation > 'cache'. Yea. There is a penalty here, though I would expect it not to be too too bad -- the typical class has only three or four inheritance layers. We could do as you suggest, but to ensure correct behavior would require that when ever a classes annotation is changed all it's subclass must also be scanned and updated if need be. I realize reading is more common than writing, but this kind of writing overhead would likely be orders of magnitude greater than the current read overhead. So it might not actually be worth it. It might just be better for Og to cache annotation reads, when possible, in areas of performance concern. Of course I'll look at the code again and see if I can lower the read overhead further. There is one other possiblity however, while it still would incur some penalty I expect it would be fairly lower. Instead of storing annotations in a hash, we could store them in class methods. Eg. Bar.ann :foo, :class => Integer could translate into def Bar.ann_foo super + @ann_foo end @ann_foo += {:class => Integer} where #+ is an alias for Hash#merge. This essentially utilizes Ruby's internal inheritance features to do the the same thing my implementation does manually. So although it's doing the same thing, it should be fairly faster. It also means the basic notation for annotation lookup is: C.ann_foo[:class] 'ann :foo, :class' notatio would of course translate into this. > I guess we should profile the current annotation lookup against > a plain hash lookup. Perhaps the speed penalty is not much after > all. Hmm... I could put that together -- if you don't beat me to it first ;) > About the global variable. I don't mind having global variables > but why would we need to scan all annotations? Not sure -- I at least consider every possibility I can think of. Perhaps someone's using it for a micro test suite, or an aop thingy and they need to scan them all before the rest of the main code exectues? In any case it isn't a big deal obviously as there is a very good chance of YAGNI. So the class instance variable is probably best. > BTW, please notice that the code in 'ann' and 'ann!' is essentially > the same, perhaps you could refactor this? Yes, probably could, I just didn't see an easy way off hand w/o adding another method which I wanted to avoid --just as I may get rid of #heritage itself mergin it into #ann. > In any case, thanks for your hard work. I really hope we can have > the annotation issue resolved the coming week, so I can port Nitro > to the new implementation. Me. Too. Facets has come a long way since 1.4+ series (now going on 1.8+). And it's ready to take another big step too. So I want to get Nitro/Og over to the latest and greatest before I start moving toward teh coold new features of 2.0. (2.0 might just blow people's minds ;) T. From transfire at gmail.com Sun Nov 12 15:34:07 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 12 Nov 2006 20:34:07 -0000 Subject: [Nitro] Nitro build system In-Reply-To: References: Message-ID: <1163363647.412184.156690@e3g2000cwe.googlegroups.com> George Moschovitis wrote: > Dear devs, > > because I cannot understand which version of Reap/Sow/Roll/Facets > works with each other to build nitro, I just added a collection of > gemspecs and updated the build script: > > ruby script/build.rb > > creates the distirbution in the > > dist > > directory. > > I would appreciate it if you could test this (and the rest of Nitro) > over the weekend. If no problems are found, I will release it on > Monday. My apologies on the delays here. I'm still working away on Ratchets. Nearly all the functionality has been in place for some time, but I just wasn't happy with the overall design. I spent the last fews weeks pounding at it and have finally gotten it all looking shiny as spit. I still have a few details but mostly I'm debugging at this point. Oh, one of those details: I still have to write an emulation of Rakes rule method (any hints on how best to do that are greatly appreciated!) Anyhow as soon as I get it out I'll fix up Nitro's ProjectInfo files. I won't make any predictions about the release date. I think I cursed myself with that a couple of weeks ago ;) But.... T. From george.moschovitis at gmail.com Mon Nov 13 03:46:38 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 13 Nov 2006 10:46:38 +0200 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <1163362913.122731.7560@h48g2000cwc.googlegroups.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <1162846549.399984.109300@i42g2000cwa.googlegroups.com> <1163362913.122731.7560@h48g2000cwc.googlegroups.com> Message-ID: > So it might not actually be worth it. It might just be better for Og to > cache annotation reads, when possible, in areas of performance concern. Ok, lets leave this to that. > There is one other possiblity however, while it still would incur some > penalty I expect it would be fairly lower. Instead of storing > annotations in a hash, we could store them in class methods. Eg. > > Bar.ann :foo, :class => Integer > > could translate into > > def Bar.ann_foo > super + @ann_foo > end > > @ann_foo += {:class => Integer} > > where #+ is an alias for Hash#merge. > > This essentially utilizes Ruby's internal inheritance features to do > the the same thing my implementation does manually. So although it's > doing the same thing, it should be fairly faster. It also means the > basic notation for annotation lookup is: > > C.ann_foo[:class] > > 'ann :foo, :class' notatio would of course translate into this. very interesting idea, though I dont like the notation much. Let's profile the current implementation first :) > Me. Too. Facets has come a long way since 1.4+ series (now going on > 1.8+). And it's ready to take another big step too. So I want to get > Nitro/Og over to the latest and greatest before I start moving toward > teh coold new features of 2.0. (2.0 might just blow people's minds ;) Agreed ;-) -g. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 13 05:22:05 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 13 Nov 2006 12:22:05 +0200 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 Message-ID: Hello everyone, New versions of Nitro (Web Application Framework) and Og (Object Relational Mapping) were released: Homepage: http://www.nitroproject.org Download: http://rubyforge.org/projects/ nitro Mailing List: http://rubyforge.org/mailman/l istinfo/nitro-general This is the biggest release yet! Tons of new wonderful features, code refactoring, bug fixes, documentation improvements and so much more. Special thanks for this release fly to Jonas Pfeniger, Jonathan/Fabian Buch and Michael Fellinger. Most notable changes: * Fully transparent Og managed objects. No need to use the special property notation. Just use the standard attr_accessor macro: class User attr_accessor :name, String, :sql => 'VARCHAR(32) attr_accessor :password, String attr_accessor :age, :login_count, Fixnum belongs_to :group has_many :comments joins_many :categories end Og automatically detects and manages this class! * The Og adapter model was re-engineered from scratch. The new adapter code is better refactored. It is now extremely easy to write new adapters for various RDBMS systems. * Og build mode. This avoids multiple sql queries when you are 'building' (ie attaching related objects) a new object. * You can now easily lookup Og entities by name: u = User[1] # classic or u = User['gmosx'] # this works as well! for the new method to work you need to annotate the attribute to use for named lookups: class User attr_accessor :name, String, :key => true .. end * Og set attribute, a nice helper to set only some attributes. b = Book[1] b.set_attribute :title => 'Hello' # updates only title in the DB b.instance_attribute_set '@title', 'Hello' # Ruby style b.set_attributes :title => '1', :hits => 3 * Much more intelligent dispatcher now handles nested controllers and many 'edge' cases. For example: Server.map = { '/' => SiteController, '/users' => UserController, '/users/categories' => UserCategoryController, '/users/comments' => UserCommentController ... } * Introduced the notion of Controls as extensions of the Elements feature. The auto administration part was recoded to utilize the Controls system. Ooh, and the admin screens now display validation errors. * Introduced Console/Script adapter. This is a new adapter that allows you to programmatically send http requests to Nitro. You can send GET/POST/etc request to any action you like with any request parameters. This adapter is used in the console mode. You can access it through the $app variable. You can also use this adapter to perform sophisticated testing, our specialized automation scripts. * New and improved nitro command. Among many new features the new command supports: * Easy setup of clusters: nitro --cluster 3 if the default port is 9000 starts 3 instances of the application listening on 9000, 9001, 9002. This command is smart enough to also name the instances for easy identification when you give 'ps aux'. Useful for Mongrel/FastCGI deployment. * Automatic start of state servers. You need a 'state' server if tou use Mongrel/Nitro to keep the distributed session and global variables and any other common data you want to use. * Output cache cleanup. Just start the console nitro console and give: $cache.cleanup * More flexible elements namespace selection, you can easier have multiple skins in your web app, per controller, per controller group etc. A low level example: class MyController ann :self, :elements => CustomSkin end * More flexible configuration system. See the updated examples for the details. * Further improvements in the form builder. Among other things, it now works better with flash parameters and handle errors. * Greatly improved the Mongrel adapter. In fact nitro+mongrel running behind apache is now the reference deployment method. We have removed the unsupported SCGI adapter, please use Mongrel instead. * The StaticInclude compiler now handles recursive includes. * Brand new automatic administration part.The new implementation is much simpler, elegant and easier to extend. * Many more bug fixes and smaller improvements. Nitro provides everything you need to develop professional Web applications using Ruby and Javascript. Nitro redefines Rapid Application Development by providing a clean, yet efficient API, a layer of domain specific languages implemented on top of Ruby and the most powerful and elegant object relational mapping solution available everywhere. have fun, Nitro Team -- http://gmosx.com/blog http://nitroproject.org From john at oxyliquit.de Mon Nov 13 10:23:54 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Mon, 13 Nov 2006 16:23:54 +0100 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: References: Message-ID: On Mon, 13 Nov 2006 11:22:05 +0100, George Moschovitis wrote: > Hello everyone, > > New versions of Nitro (Web Application Framework) and Og (Object > Relational Mapping) were released: yaaaay! Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From transfire at gmail.com Mon Nov 13 12:32:53 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Mon, 13 Nov 2006 17:32:53 -0000 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: References: Message-ID: <1163439173.174226.24570@e3g2000cwe.googlegroups.com> Wow. Very impressive release! From james.britt at gmail.com Mon Nov 13 13:57:18 2006 From: james.britt at gmail.com (James Britt) Date: Mon, 13 Nov 2006 11:57:18 -0700 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: References: Message-ID: <4558C00E.1060608@gmail.com> George Moschovitis wrote: > Hello everyone, > > New versions of Nitro (Web Application Framework) and Og (Object > Relational Mapping) were released: > > Homepage: http://www.nitroproject.org > Download: http://rubyforge.org/projects/ nitro > Mailing List: http://rubyforge.org/mailman/l istinfo/nitro-general > > This is the biggest release yet! Tons of new wonderful features, code > refactoring, bug fixes, documentation improvements and so much more. > > Special thanks for this release fly to Jonas Pfeniger, Jonathan/Fabian > Buch and Michael Fellinger. > > Most notable changes: > > * Fully transparent Og managed objects. No need to use the special > property notation. Just use the standard attr_accessor macro: Sweet. That kicks ass. Question: How much has the overall API changed? Hal Fulton's new release of The Ruby Way, 2nd ed. has a section on Nitro (written by me, as it happens). It is, I think, the only book that covers Nitro or Og in any depth. I hoping that this Nitro release still plays well with the information in that section, for people reading the book and getting their interest piqued. -- James Britt "Hackers will be expelled" - The Breakfast Club (1985) From vikingtux at gmail.com Mon Nov 13 16:01:56 2006 From: vikingtux at gmail.com (Alexandre Gravem) Date: Mon, 13 Nov 2006 19:01:56 -0200 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <4558C00E.1060608@gmail.com> References: <4558C00E.1060608@gmail.com> Message-ID: <40b05ebe0611131301l7f83fff5s63843bae2f991137@mail.gmail.com> I have "helper Sitemap not found (module not defined), check name" when trying to use the new admin system. I installed via "$ gem install nitro" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061113/fd8dd8c8/attachment.html From fabian at fabian-buch.de Mon Nov 13 16:59:26 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Mon, 13 Nov 2006 22:59:26 +0100 Subject: [Nitro] removed working call/answer implementation? Message-ID: Sun Nov 12 21:20:48 CET 2006 George Moschovitis * Removed non-working call/answer implementation. George: Why? A few seconds before release you remove working (it's not non- working, it works) functionality from Nitro without asking on the ML whether someone is using it. Why? It wouldn't've hurt to ask and not either to leave it in, since it's not making other stuff of Nitro buggy or something. The implementation might not be perfect, but I used it for an Auth system of mine and it worked quite nice (didn't use or test deep stack levels though). Nitro 0.40.0 is out now and I again have to either use my own version of Nitro or make my Auth system more complicated. George, you're the boss, you're probably also the biggest user of your child "Nitro". But you are not the only user and developer. Could you at least ask in the future whether someone else needs a certain functionality before you silently remove it seconds before a release (ok, the night before)? If you think some features are badly implemented they can be reimplemented by someone if you tell the list (something like call/ answer isn't that difficult) and until that's done even a partly buggy thing can be left in till a reimplementation in a future release. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From fabian at fabian-buch.de Mon Nov 13 17:08:05 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Mon, 13 Nov 2006 23:08:05 +0100 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <4558C00E.1060608@gmail.com> References: <4558C00E.1060608@gmail.com> Message-ID: <1D58C1F0-206B-4C03-9497-44E926E9B3D4@fabian-buch.de> Am 13.11.2006 um 19:57 schrieb James Britt: > Question: How much has the overall API changed? Hal Fulton's new > release of The Ruby Way, 2nd ed. has a section on Nitro (written by > me, > as it happens). It is, I think, the only book that covers Nitro or Og > in any depth. I hoping that this Nitro release still plays well with > the information in that section, for people reading the book and > getting > their interest piqued. Og's API could be seen as "extended", so old apps should still work and if someone tries to build an Og app with these chapters it should work (if the book was written for Og 0.31.0). For Nitro though quite some API changes happend that won't let old apps work unfortunately. These API changes are nice in itself and it's not very hard to adapt the new things, but old Nitro apps definitely won't work: From memory: - run.rb changed quite a bit - form helper (form_for()) is replaced (now form()) and works differently - scgi vanished - some store adapters for Og vanished too (working Og adapters: postgresql, mysql, sqlite) There might be some more. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From transfire at gmail.com Mon Nov 13 22:21:56 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Tue, 14 Nov 2006 03:21:56 -0000 Subject: [Nitro] Serious discussion on Annotaitons - Part II In-Reply-To: <1163362913.122731.7560@h48g2000cwc.googlegroups.com> References: <1162124667.089192.148110@e64g2000cwd.googlegroups.com> <1162846549.399984.109300@i42g2000cwa.googlegroups.com> <1163362913.122731.7560@h48g2000cwc.googlegroups.com> Message-ID: <1163474516.778699.46960@e3g2000cwe.googlegroups.com> transfire at gmail.com wrote: > There is one other possiblity however, while it still would incur some > penalty I expect it would be fairly lower. Instead of storing > annotations in a hash, we could store them in class methods. Eg. > > Bar.ann :foo, :class => Integer > > could translate into > > def Bar.ann_foo > super + @ann_foo > end > > @ann_foo += {:class => Integer} > > where #+ is an alias for Hash#merge. > > This essentially utilizes Ruby's internal inheritance features to do > the the same thing my implementation does manually. So although it's > doing the same thing, it should be fairly faster. It also means the > basic notation for annotation lookup is: I further consideratioj of this idea, It seesm to a have one fatal flaw. Modules qua class aren;t inherited. So super won't catch those. So the implemention I last posted stands. T. From george.moschovitis at gmail.com Tue Nov 14 03:35:52 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 10:35:52 +0200 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <40b05ebe0611131301l7f83fff5s63843bae2f991137@mail.gmail.com> References: <4558C00E.1060608@gmail.com> <40b05ebe0611131301l7f83fff5s63843bae2f991137@mail.gmail.com> Message-ID: Oops, my mistake! Please remove the line helper Sitemap and it will work! -g. On 11/13/06, Alexandre Gravem wrote: > I have "helper Sitemap not found (module not defined), check name" when > trying to use the new admin system. > > I installed via "$ gem install nitro" > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 14 03:38:46 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 10:38:46 +0200 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <4558C00E.1060608@gmail.com> References: <4558C00E.1060608@gmail.com> Message-ID: > Question: How much has the overall API changed? Hal Fulton's new Not that much. There is also a file called: doc/MIGRATION with some related info. > release of The Ruby Way, 2nd ed. has a section on Nitro (written by me, > as it happens). It is, I think, the only book that covers Nitro or Og > in any depth. I hoping that this Nitro release still plays well with > the information in that section, for people reading the book and getting > their interest piqued. Many thanks for this chapter. Is this book released? -g. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 14 03:42:34 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 10:42:34 +0200 Subject: [Nitro] removed working call/answer implementation? In-Reply-To: References: Message-ID: Hello Fabian, this is a total surprise for me. I haven't thought that anyone used this! I started coding this, but left this half-finished. In fact, I cannot understand how this works for you. This code doesnt handle cases like multiple windows, tabbed windows and stuff like that. It is broken, I am very courious how you used this. Btw,I will release version 0.41.0 next Monday (there seem to be some bugs in 0.40.0) I will get this back in. But, If you could provide a working implementation it would be nice. The old implementation works with only one window openned in the application. sorry for the inconvienience, George. On 11/13/06, Fabian Buch wrote: > Sun Nov 12 21:20:48 CET 2006 George Moschovitis > > * Removed non-working call/answer implementation. > > George: > > Why? A few seconds before release you remove working (it's not non- > working, it works) functionality from Nitro without asking on the ML > whether someone is using it. Why? It wouldn't've hurt to ask and not > either to leave it in, since it's not making other stuff of Nitro > buggy or something. > > The implementation might not be perfect, but I used it for an Auth > system of mine and it worked quite nice (didn't use or test deep > stack levels though). Nitro 0.40.0 is out now and I again have to > either use my own version of Nitro or make my Auth system more > complicated. > > George, you're the boss, you're probably also the biggest user of > your child "Nitro". But you are not the only user and developer. > Could you at least ask in the future whether someone else needs a > certain functionality before you silently remove it seconds before a > release (ok, the night before)? > > If you think some features are badly implemented they can be > reimplemented by someone if you tell the list (something like call/ > answer isn't that difficult) and until that's done even a partly > buggy thing can be left in till a reimplementation in a future release. > > Fabian > > > -- > Nitro Q&A: http://oxyliquit.de/ > Blog: http://blog.fabian-buch.de > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 14 03:54:39 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 10:54:39 +0200 Subject: [Nitro] removed working call/answer implementation? In-Reply-To: References: Message-ID: > George, you're the boss, you're probably also the biggest user of > your child "Nitro". But you are not the only user and developer. This is not fair... I removed this because I thought it didn't work at all. One day I started writting the code and never actually finished it. I am not the Boss, I just tried to cleanup the code. I am sorry for the inconvienience, and I want to work with you to rectify this. regards, George. -- http://gmosx.com/blog http://nitroproject.org From lasso at lassoweb.se Tue Nov 14 04:58:34 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Tue, 14 Nov 2006 09:58:34 -0000 (UTC) Subject: [Nitro] removed working call/answer implementation? In-Reply-To: References: Message-ID: <45090.192.176.230.1.1163498314.squirrel@webmail.lassoweb.se> Hi, > Btw,I will release version 0.41.0 next Monday (there seem to be some > bugs in 0.40.0) Well, it kind of broke half my pages instantly...Easily fixed though :) Btw, my DOCTYPE fix for the elements compiler doesn't seem included with 0.40. Any partical reason why it was rejected? Sincerely /lasso From george.moschovitis at gmail.com Tue Nov 14 05:46:51 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 12:46:51 +0200 Subject: [Nitro] removed working call/answer implementation? In-Reply-To: <45090.192.176.230.1.1163498314.squirrel@webmail.lassoweb.se> References: <45090.192.176.230.1.1163498314.squirrel@webmail.lassoweb.se> Message-ID: > Btw, my DOCTYPE fix for the elements compiler doesn't seem included with > 0.40. Any partical reason why it was rejected? Oops, I forgot this :( Will add the fix right now! -g. -- http://gmosx.com/blog http://nitroproject.org From aglarond at gmail.com Tue Nov 14 06:24:39 2006 From: aglarond at gmail.com (Dimitri Aivaliotis) Date: Tue, 14 Nov 2006 12:24:39 +0100 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: References: <4558C00E.1060608@gmail.com> <40b05ebe0611131301l7f83fff5s63843bae2f991137@mail.gmail.com> Message-ID: <55c107bf0611140324l39911157pf39eb312380397e@mail.gmail.com> On 11/14/06, George Moschovitis wrote: > > > my mistake! Please remove the line helper Sitemap and it will work! > Or better yet: releasing the Sitemap helper. ;) - Dimitri -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061114/31ca0eb2/attachment.html From george.moschovitis at gmail.com Tue Nov 14 07:12:39 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 14:12:39 +0200 Subject: [Nitro] Fixes in repo Message-ID: Dear devs, fixes for all reported problems are already in the Repo. -g. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 14 07:14:54 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 14:14:54 +0200 Subject: [Nitro] Next version roadmap Message-ID: Dear devs, I am trying to come up with a roadmap for the next version of Nitro+Og. One thing is for sure, I want a new version released before Dec 15. I would like to hear your opinions and suggestions regarding our targets for the next release. thanks, George. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 14 07:29:25 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 14:29:25 +0200 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <55c107bf0611140324l39911157pf39eb312380397e@mail.gmail.com> References: <4558C00E.1060608@gmail.com> <40b05ebe0611131301l7f83fff5s63843bae2f991137@mail.gmail.com> <55c107bf0611140324l39911157pf39eb312380397e@mail.gmail.com> Message-ID: > Or better yet: releasing the Sitemap helper. ;) hmm, I probably bundle the helper in the next version. Even though I dont like it that much, perhaps it will be useful to someone. regards, George. -- http://gmosx.com/blog http://nitroproject.org From james.britt at gmail.com Tue Nov 14 10:02:48 2006 From: james.britt at gmail.com (James Britt) Date: Tue, 14 Nov 2006 08:02:48 -0700 Subject: [Nitro] Next version roadmap In-Reply-To: References: Message-ID: <4559DA98.60406@gmail.com> George Moschovitis wrote: > Dear devs, > > I am trying to come up with a roadmap for the next version of > Nitro+Og. One thing is for sure, I want a new version released before > Dec 15. I would like to hear your opinions and suggestions regarding > our targets for the next release. Docs! At the Phoenix Ruby Users Group meeting last night we talked a bit about Nitro, and a people said that they were interested in trying out Nitro but the lack of docs and examples made it hard for them. Thanks, -- James Britt "Discover the recipes you are using and abandon them." - Brian Eno and Peter Schmidt, Oblique Strategies From james.britt at gmail.com Tue Nov 14 10:03:47 2006 From: james.britt at gmail.com (James Britt) Date: Tue, 14 Nov 2006 08:03:47 -0700 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: References: <4558C00E.1060608@gmail.com> Message-ID: <4559DAD3.8040801@gmail.com> George Moschovitis wrote: >>Question: How much has the overall API changed? Hal Fulton's new > > > Not that much. There is also a file called: doc/MIGRATION with some > related info. > > >>release of The Ruby Way, 2nd ed. has a section on Nitro (written by me, >>as it happens). It is, I think, the only book that covers Nitro or Og >>in any depth. I hoping that this Nitro release still plays well with >>the information in that section, for people reading the book and getting >>their interest piqued. > > > Many thanks for this chapter. Is this book released? Yes. I received a copy from the publisher about a week ago. -- James Britt "Discover the recipes you are using and abandon them." - Brian Eno and Peter Schmidt, Oblique Strategies From transfire at gmail.com Tue Nov 14 11:35:16 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Tue, 14 Nov 2006 16:35:16 -0000 Subject: [Nitro] Next version roadmap In-Reply-To: References: Message-ID: <1163522116.888345.42960@i42g2000cwa.googlegroups.com> George Moschovitis wrote: > Dear devs, > > I am trying to come up with a roadmap for the next version of > Nitro+Og. One thing is for sure, I want a new version released before > Dec 15. I would like to hear your opinions and suggestions regarding > our targets for the next release. I would go for a bug-fix release first. Just work on that and other minor things, maybe improving some docs and ease onubies to get started. Then after that work on using latest Facets and new annotations. Where does Glue stand at this point btw? T. From Reid.Thompson at ateb.com Tue Nov 14 11:37:31 2006 From: Reid.Thompson at ateb.com (Reid Thompson) Date: Tue, 14 Nov 2006 11:37:31 -0500 Subject: [Nitro] Next version roadmap In-Reply-To: <4559DA98.60406@gmail.com> References: <4559DA98.60406@gmail.com> Message-ID: <1163522251.4251.0.camel@jhereg> On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: > Docs! > ++Docs From lionel.orry at gmail.com Tue Nov 14 12:07:23 2006 From: lionel.orry at gmail.com (Lionel Orry) Date: Tue, 14 Nov 2006 18:07:23 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: <1163522251.4251.0.camel@jhereg> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> Message-ID: <4559F7CB.8040401@gmail.com> Reid Thompson a ?crit : > On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: >> Docs! >> > ++Docs +++Docs+++ !!! > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From george.moschovitis at gmail.com Tue Nov 14 12:22:25 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 19:22:25 +0200 Subject: [Nitro] Next version roadmap In-Reply-To: <1163522251.4251.0.camel@jhereg> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> Message-ID: On 11/14/06, Reid Thompson wrote: > On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: > > Docs! > > > ++Docs noted :) -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Tue Nov 14 13:52:26 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 14 Nov 2006 20:52:26 +0200 Subject: [Nitro] Next version roadmap In-Reply-To: <4559F7CB.8040401@gmail.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> Message-ID: Ok given the fact that I am relatively happy with the current version of Nitro, how about freezing the codebase till the end of november and work on: - add rdoc comments in the sources - add more tests - code cleanup - remove obsolete features - improve the docs - improve the examples - make nitro work with latest facets - improve nitroproject.org - create some screencasts But I need more help. Can anyone help me with any of these tasks? regards, George. On 11/14/06, Lionel Orry wrote: > > > Reid Thompson a ?crit : > > On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: > >> Docs! > >> > > ++Docs > > +++Docs+++ !!! > > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From olle at olleolleolle.dk Tue Nov 14 16:29:33 2006 From: olle at olleolleolle.dk (Olle Jonsson) Date: Tue, 14 Nov 2006 22:29:33 +0100 Subject: [Nitro] Next version roadmap Message-ID: <896063DE-FAE4-4B5F-BCAC-80F0909EE8A9@olleolleolle.dk> Documentation shopping list: * Examples/use-cases for the crunchier parts of Og. * Conceptual wholeness of examples. Shy away from corny, empty examples like "class Thingamajic < Hamburglar". Try to reuse concepts from other parts of the manual. Re-using the Pet Store or the Elven Army Registry, or a Registry of Alleged War Criminals (saw that in a book on PL/SQL for Oracle [1]) will focus the reader. Perhaps going so far as to use a standard app database, for the examples (like Microsoft Access has its "Northwind" and MySQL its "Sakila")? * Examples on smart dispatching (I'd love to see a gallery of user- submitted dispatching rules) of different kinds * General design hints on how a Nitro app is "often" designed. "You'll start out with a handful of database objects, and then add controllers for one of them. Add tests (like this, see other section) early. Break up long methods out to helper methods (or pack them up in Helpers [are there Nitro Helpers?])" How to use Nitro "going with the grain". Understanding what patterns Nitro helps solve is very much a part of the learning process. * API documentation (These are just shots in the dark, but *my* shots, in *my* dark.) thanks for listening, Olle Jonsson Copenhagen [1]: Oh, it was Feuerstein, check his article/thinkpiece out: http://www.oreillynet.com/pub/a/oreilly/news/feuerstein_1000.html From john at oxyliquit.de Tue Nov 14 17:13:12 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 14 Nov 2006 23:13:12 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: References: Message-ID: Hi, > I am trying to come up with a roadmap for the next version of > Nitro+Og. One thing is for sure, I want a new version released before > Dec 15. I would like to hear your opinions and suggestions regarding > our targets for the next release. yes, next release as cleanup and fix release is a good plan. Rayman had a few problems I think, one of them could be with my Dictionary use inside the cgi.rb and with params like 'arg[hh]', which I completely forgot to test in my testcase. I will try to get Riku to reproduce that problem and post it here as response. Another error found by ray: http://oxyliquit.de/question/83 And this question would be best answered by you (George) as well: http://oxyliquit.de/question/85 The question about form helpers (http://oxyliquit.de/question/84) can probably answered by Fabian. Thank you everyone for using Oxy! (Rayman said on irc: "it seems kinda dead", I don't know if I like to hear that. :P So please, if you have any questions, please take your time to ask them on the mailing list as well as Oxy so I don't get to hear that oxy seems dead. This helps poor kittens! :) ) Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From fabian at fabian-buch.de Tue Nov 14 17:18:18 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Tue, 14 Nov 2006 23:18:18 +0100 Subject: [Nitro] removed working call/answer implementation? In-Reply-To: References: Message-ID: <0DE4EB50-49DB-4D1B-9A82-53444247F3D6@fabian-buch.de> Am 14.11.2006 um 09:42 schrieb George Moschovitis: > this is a total surprise for me. I haven't thought that anyone used > this! I started coding this, but left this half-finished. In fact, I > cannot understand how this works for you. This code doesnt handle > cases like multiple windows, tabbed windows and stuff like that. It is > broken, I am very courious how you used this. Never thought of such cases/usages. I simply use it for a login system like this: in an action that requires login I do: unless logged_in? flash[:ERROR] = 'Login first!' call R(AuthController, :login) end in the login action I log the user in and after that go back to from where the login action was called: answer() This is just one level and enough for the usual login situation. What doesn't work are probably more complicated things with multiple stacked calls or something. I don't know what you mean with multiple windows and tabs. I don't use call/answer the way you might want to use it in a wee-like framework. > Btw,I will release version 0.41.0 next Monday (there seem to be some > bugs in 0.40.0) I will get this back in. But, If you could provide a > working implementation it would be nice. The old implementation works > with only one window openned in the application. Good to hear that it'll come back, thanks. Well, I didn't look into it too deeply yet, since it worked for my usecase which is maybe a little different from what you initially intended (or the way other frameworks implement call/answer), but I can have a look tomorrow and at least provide a testcase for my usecase. If I find some more time I might look for other usecases too. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From mattrose at folkwolf.net Tue Nov 14 18:02:18 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Tue, 14 Nov 2006 18:02:18 -0500 Subject: [Nitro] Next version roadmap In-Reply-To: References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> Message-ID: On 14-Nov-06, at 1:52 PM, George Moschovitis wrote: > Ok given the fact that I am relatively happy with the current version > of Nitro, how about freezing the codebase till the end of november and > work on: > > - add rdoc comments in the sources I can do this, I think. I'm not that familiar with the source code, but I can definitely submit patches where I can track stuff down. > - add more tests > - code cleanup > - remove obsolete features > - improve the docs I was thinking of doing this already. > - improve the examples > - make nitro work with latest facets > - improve nitroproject.org I was also thinking of doing this. There's one or two great bits of documentation well hidden within the Wiki on the site, but it needs serious fleshing out. > - create some screencasts > > > But I need more help. Can anyone help me with any of these tasks? > > regards, > George. > > > > On 11/14/06, Lionel Orry wrote: >> >> >> Reid Thompson a ?crit : >>> On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: >>>> Docs! >>>> >>> ++Docs >> >> +++Docs+++ !!! >> >>> _______________________________________________ >>> Nitro-general mailing list >>> Nitro-general at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/nitro-general >>> >> _______________________________________________ >> Nitro-general mailing list >> Nitro-general at rubyforge.org >> http://rubyforge.org/mailman/listinfo/nitro-general >> > > > -- > http://gmosx.com/blog > http://nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From mattrose at folkwolf.net Tue Nov 14 21:48:21 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Tue, 14 Nov 2006 21:48:21 -0500 Subject: [Nitro] nitro 0.40.0 changes? Message-ID: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> I just installed the new nitro, and it absolutely broke the app I was working on. I tried running it as is, and I got this error: matt-roses-computer:~/ruby/start mattrose$ nitro /Users/mattrose/ruby/start/model.rb:2: undefined method `prop_accessor' for Master:Class (NoMethodError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:in `gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:in `require' from run.rb:10 Then, when I changed all of the prop_accessor to attr_accessor, I get this error instead, which I don't entirely get. matt-roses-computer:~/ruby/start mattrose$ nitro /Users/mattrose/ruby/start/model.rb:28: uninitialized constant User::Article (NameError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:in `gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:in `require' from run.rb:10 Here's the code. Can someone tell me what I'm doing wrong? This used to work fine. class Blog attr_accessor :title, String attr_accessor :description, String has_many :users, User has_many :articles, Article def initialize(title,description) @title, at description = title,description end def to_s @title end end class User attr_accessor :username attr_accessor :password has_many :articles, Article belongs_to :blog, Blog def initialize(username,password,blog) @username, at password, at blog_oid = username,password,blog end def to_s @username end end class Article attr_accessor :title attr_accessor :body #has_many :comments belongs_to :blog, Blog belongs_to :user, User def initialize(title,body,user,blog) @title, at body, at user_oid, at blog_oid = title,body,user,blog end def to_s @title end end Matt From george.moschovitis at gmail.com Wed Nov 15 05:18:47 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 15 Nov 2006 12:18:47 +0200 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> Message-ID: please post your run.rb for more details, have a look at the run.rb's or app.rbs in the examples and flare/spark. regards, George. On 11/15/06, Matt Rose wrote: > I just installed the new nitro, and it absolutely broke the app I was > working on. > > I tried running it as is, and I got this error: > > matt-roses-computer:~/ruby/start mattrose$ nitro > /Users/mattrose/ruby/start/model.rb:2: undefined method > `prop_accessor' for Master:Class (NoMethodError) > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `gem_original_require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `require' > from run.rb:10 > > Then, when I changed all of the prop_accessor to attr_accessor, I get > this error instead, which I don't entirely get. > > matt-roses-computer:~/ruby/start mattrose$ nitro > /Users/mattrose/ruby/start/model.rb:28: uninitialized constant > User::Article (NameError) > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `gem_original_require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `require' > from run.rb:10 > > Here's the code. Can someone tell me what I'm doing wrong? This > used to work fine. > > class Blog > attr_accessor :title, String > attr_accessor :description, String > has_many :users, User > has_many :articles, Article > def initialize(title,description) > @title, at description = title,description > end > def to_s > @title > end > end > class User > attr_accessor :username > attr_accessor :password > has_many :articles, Article > belongs_to :blog, Blog > def initialize(username,password,blog) > @username, at password, at blog_oid = username,password,blog > end > def to_s > @username > end > end > > class Article > attr_accessor :title > attr_accessor :body > #has_many :comments > belongs_to :blog, Blog > belongs_to :user, User > def initialize(title,body,user,blog) > @title, at body, at user_oid, at blog_oid = title,body,user,blog > end > def to_s > @title > end > end > > Matt > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From fabian at fabian-buch.de Wed Nov 15 06:49:09 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Wed, 15 Nov 2006 12:49:09 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: References: Message-ID: <0FE04204-16C2-4C13-B5B8-17A1332C53DF@fabian-buch.de> Am 14.11.2006 um 23:13 schrieb Jonathan Buch: > The question about form helpers (http://oxyliquit.de/question/84) can > probably answered by Fabian. done: http://oxyliquit.de/question/84 Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From john at oxyliquit.de Wed Nov 15 07:32:33 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 15 Nov 2006 13:32:33 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> Message-ID: <20061115123233.GA7287@oxyliquit.de> Hi, please look at http://oxyliquit.de/tip/32 for more extensive pointers on how to migrate from 0.31 to 0.40. Jo From fabian at fabian-buch.de Wed Nov 15 07:38:12 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Wed, 15 Nov 2006 13:38:12 +0100 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <4558C00E.1060608@gmail.com> References: <4558C00E.1060608@gmail.com> Message-ID: <4D170040-B0D3-4764-A743-2B62552B4216@fabian-buch.de> Tip 32 (http://oxyliquit.de/tip/32) on Oxyliquit now covers most of the changes that either got to my mind or got already reported by users on #nitro for a Migration from 0.31.0 to 0.40.0. This document will be enhanced when problems arise reported by users, so it's a good link for everyone migrating a Nitro or Og application from older versions to 0.40.0. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Wed Nov 15 07:53:50 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 15 Nov 2006 14:53:50 +0200 Subject: [Nitro] Nitro + Facets Message-ID: Dear devs, it seems that Nitro does require facets 1.4.3 and not 1.4.5 after all. The nitro binary uses facets/command which seems to be missing from 1.4.5 :( One more bug to fix for 0.41.0. Please report more bugs to me ASAP, I would like to release the bug-fixed version next monday. regards, George. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Wed Nov 15 08:05:49 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 15 Nov 2006 15:05:49 +0200 Subject: [Nitro] [ANN] Nitro + Og 0.40.0 In-Reply-To: <4D170040-B0D3-4764-A743-2B62552B4216@fabian-buch.de> References: <4558C00E.1060608@gmail.com> <4D170040-B0D3-4764-A743-2B62552B4216@fabian-buch.de> Message-ID: thanks, thats GREAT :) -g. On 11/15/06, Fabian Buch wrote: > Tip 32 (http://oxyliquit.de/tip/32) on Oxyliquit now covers most of > the changes that either got to my mind or got already reported by > users on #nitro for a Migration from 0.31.0 to 0.40.0. > > This document will be enhanced when problems arise reported by users, > so it's a good link for everyone migrating a Nitro or Og application > from older versions to 0.40.0. > > Fabian > > > > -- > Nitro Q&A: http://oxyliquit.de/ > Blog: http://blog.fabian-buch.de > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Wed Nov 15 08:08:13 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 15 Nov 2006 15:08:13 +0200 Subject: [Nitro] Nitro + Facets In-Reply-To: References: Message-ID: > it seems that Nitro does require facets 1.4.3 and not 1.4.5 after all. hmm, please ignore that... -g. -- http://gmosx.com/blog http://nitroproject.org From transfire at gmail.com Wed Nov 15 08:41:41 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Wed, 15 Nov 2006 13:41:41 -0000 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> Message-ID: <1163598101.495434.32530@f16g2000cwb.googlegroups.com> Matt Rose wrote: > I just installed the new nitro, and it absolutely broke the app I was > working on. > > I tried running it as is, and I got this error: > > matt-roses-computer:~/ruby/start mattrose$ nitro > /Users/mattrose/ruby/start/model.rb:2: undefined method > `prop_accessor' for Master:Class (NoMethodError) > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `gem_original_require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `require' > from run.rb:10 > > Then, when I changed all of the prop_accessor to attr_accessor, I get > this error instead, which I don't entirely get. > > matt-roses-computer:~/ruby/start mattrose$ nitro > /Users/mattrose/ruby/start/model.rb:28: uninitialized constant > User::Article (NameError) > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `gem_original_require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:27:in `require' > from run.rb:10 > > Here's the code. Can someone tell me what I'm doing wrong? This > used to work fine. > > class Blog > attr_accessor :title, String > attr_accessor :description, String > has_many :users, User > has_many :articles, Article > def initialize(title,description) > @title, at description = title,description > end > def to_s > @title > end > end > class User > attr_accessor :username > attr_accessor :password > has_many :articles, Article > belongs_to :blog, Blog > def initialize(username,password,blog) > @username, at password, at blog_oid = username,password,blog > end > def to_s > @username > end > end > > class Article > attr_accessor :title > attr_accessor :body > #has_many :comments > belongs_to :blog, Blog > belongs_to :user, User > def initialize(title,body,user,blog) > @title, at body, at user_oid, at blog_oid = title,body,user,blog > end > def to_s > @title > end > end Am I right in thinking that if you want Og to persist an attribute you _must_ give the class annotation? I think that's part of the change from prop to attr. T. From john at oxyliquit.de Wed Nov 15 08:58:09 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 15 Nov 2006 14:58:09 +0100 Subject: [Nitro] Fixes in repo In-Reply-To: References: Message-ID: <20061115135808.GA1374@oxyliquit.de> Hi, > fixes for all reported problems are already in the Repo. Please look at taggable, add this to the top of the testcase below the article. class Second attr_accessor :haha, String is Taggable end $og1.manage_classes(Article, Tag, Second) By adding this second class and running the testcase again, you will see that it always uses the second class gets the tags.. very weird. Can't follow this further right now, fixing Oxy to get it out to the public as soon as possible. Jo From george.moschovitis at gmail.com Wed Nov 15 10:46:15 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 15 Nov 2006 17:46:15 +0200 Subject: [Nitro] Fixes in repo In-Reply-To: <20061115135808.GA1374@oxyliquit.de> References: <20061115135808.GA1374@oxyliquit.de> Message-ID: please send a proper patch, at least including the test case. -g. On 11/15/06, Jonathan Buch wrote: > Hi, > > > fixes for all reported problems are already in the Repo. > > Please look at taggable, add this to the top of the testcase below the article. > > class Second > attr_accessor :haha, String > is Taggable > end > > $og1.manage_classes(Article, Tag, Second) > > By adding this second class and running the testcase again, you will see > that it always uses the second class gets the tags.. very weird. > Can't follow this further right now, fixing Oxy to get it out to the > public as soon as possible. > > Jo > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://gmosx.com/blog http://nitroproject.org From john at oxyliquit.de Wed Nov 15 10:46:44 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 15 Nov 2006 16:46:44 +0100 Subject: [Nitro] Brand New Oxyliquit! Message-ID: Hi, the new design is made with readability in mind (see also new design for Tutorials). As noted sometimes back by James Britt and others the old design wasn't too readable; I hope the new one is. Feedback is appreciated, so it can be improved. Please tell me (Jonathan) or Fabian if you like the new design! This new version of Oxyliquit runs on brand new Nitro 0.40 and uses a new Authentication scheme. Everything should work as before though. Please tell us of any irrgeularities you find here and enjoy your stay. Your friendly neighbourhood Oxyliquit hosts, Fabian and Jonathan -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Wed Nov 15 11:07:22 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 15 Nov 2006 18:07:22 +0200 Subject: [Nitro] Oxywtf rocks ;-) Message-ID: The title says it all ;-) The new version rocks :) -g. -- http://gmosx.com/blog http://nitroproject.org From al-nitrogen at none.at Wed Nov 15 12:29:37 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Wed, 15 Nov 2006 18:29:37 +0100 Subject: [Nitro] Brand New Oxyliquit! In-Reply-To: References: Message-ID: <20061115172937.GB15738@none.at> Hi, On Mit 15.11.2006 16:46, Jonathan Buch wrote: > >the new design is made with readability in mind (see also new design >for Tutorials). As noted sometimes back by James Britt and others the >old design wasn't too readable; I hope the new one is. Feedback is >appreciated, so it can be improved. I must say ;-)) Suuuuuuuuuuper nice switch ;-))))))) Thanks guies ;-)) Aleks ;-) From john at oxyliquit.de Wed Nov 15 13:14:53 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 15 Nov 2006 19:14:53 +0100 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: References: Message-ID: Hi, oxy is out, so a little time for other stuff. I also packed 3 other patches into it you might want to integrate. I had them ready since a few weeks, didn't want to push them into the release though. You can ignore them for now if you see 'danger ahaid'. * add testcase for taggable, failing This one is the important one. 1) Failure: test_all(TestOgTaggable) [/Volumes/Data/build/cvs/nitro/nitro-0.40-own/og/test/glue/tc_taggable.rb:52]: <1> expected but was <0>. This is the error I get. I hope you can find the error! Thank you very much! Jo Thu Oct 26 10:41:31 CEST 2006 Jonathan Buch * Refactor SchemaInheritance This patch avoids messing around with :ogtype within create_table(), the property gets included into the class when SchemaInheritanceBase is included into the base class. This has a slight problem, it doesn't assure that the ogtype is the first field in the database. To accomodate for that, the eval_og_allocate() method has been adapted. This has to be revisited later, the current approach is too inefficient. It also removes the eval_og_allocate from the postgres adapter, the one in sql.rb is the same. Shall I send this patch? (1/5) [ynWvpxqadjk], or ? for help: y Thu Oct 26 10:58:14 CEST 2006 Jonathan Buch * Alternative create_with(hash) method # An alternative creation helper, does _not_ call the # initialize method when there are mandatory elements. Shall I send this patch? (2/5) [ynWvpxqadjk], or ? for help: y Thu Oct 26 11:04:49 CEST 2006 Jonathan Buch * Extended entity .finder method Can now handle relations. Post.find_by_title_and_forum_name(title,forumName) class Forum property :name, String has_many :posts, Post end class Post property :title, String property :message, String belongs_to :forum, Forum end 'forum' is the :forum from belongs_to, 'name' is a property from the relations. It creates a SQL subquery to find the correct forum_oid. Shall I send this patch? (3/5) [ynWvpxqadjk], or ? for help: y Wed Nov 15 19:07:09 CET 2006 Jonathan Buch * add testcase for taggable, failing Shall I send this patch? (5/5) [ynWvpxqadjk], or ? for help: y -- Feel the love http://pinkjuice.com/pics/ruby.png -------------- next part -------------- A non-text attachment was scrubbed... Name: taggabletc_fail.patch.tar.bz2 Type: application/bzip2 Size: 2591 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061115/2b9860db/attachment-0001.bin From john at oxyliquit.de Wed Nov 15 13:21:01 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 15 Nov 2006 19:21:01 +0100 Subject: [Nitro] Oxywtf rocks ;-) In-Reply-To: References: Message-ID: <20061115182100.GA20026@oxyliquit.de> Glad you like it ^___^ > The title says it all ;-) The new version rocks :) Jo From fabian at fabian-buch.de Wed Nov 15 14:31:00 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Wed, 15 Nov 2006 20:31:00 +0100 Subject: [Nitro] removed working call/answer implementation? In-Reply-To: <0DE4EB50-49DB-4D1B-9A82-53444247F3D6@fabian-buch.de> References: <0DE4EB50-49DB-4D1B-9A82-53444247F3D6@fabian-buch.de> Message-ID: <83AE111C-0547-4C28-8639-3A2A4DC49455@fabian-buch.de> Found it again. I fixed call/answer somewhen in September already which also got into the repo with one of the bigger bundles probably, so didn't get noticed probably. It indeed didn't work without that patch correctly which it doesn't now either. Attached to this mail is a patch that lets call/answer work correctly again (for my usecases) and includes a small testcase too. Fabian -------------- next part -------------- A non-text attachment was scrubbed... Name: call_answer.patch.gz Type: application/x-gzip Size: 1090 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061115/d64a59fc/attachment.gz From mattrose at folkwolf.net Wed Nov 15 22:10:44 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Wed, 15 Nov 2006 22:10:44 -0500 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <1163598101.495434.32530@f16g2000cwb.googlegroups.com> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> Message-ID: <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> Where is this documented? I have to say, I'm not very impressed right now. right now, it looks like all my work has to be re-written from scratch. I've finally figured out how to get my app to start, and the console is great to work with, but I still can't get past the starting gate. I have two classes. Master is just a one-off table that holds some meta-information. It has no relations to any other table. But while I can use other models, I can't use this one. here's the class. class Master attr_accessor :title attr_accessor :description attr_accessor :user attr_accessor :pass def initialize(title,desc,user,pass) @title, at description, at user, at pass = title,desc,user,pass end def to_s @title end end class Blog attr_accessor :title, String attr_accessor :description, String has_many :users, User has_many :articles, Article def initialize(title,description) @title, at description = title,description end def to_s @title end end and here's the output. >> matt-roses-computer:~/ruby/start mattrose$ nitro console INFO: Og uses the Sqlite store. /usr/local/lib/ruby/1.8/logger.rb:525:in `initialize':Errno::ENOENT: No such file or directory - log/app.log >> Blog.all => >> Master.all NoMethodError: undefined method `all' for Master:Class from (irb):2 from :0 On 15-Nov-06, at 8:41 AM, transfire at gmail.com wrote: > > Matt Rose wrote: >> I just installed the new nitro, and it absolutely broke the app I was >> working on. >> >> I tried running it as is, and I got this error: >> >> matt-roses-computer:~/ruby/start mattrose$ nitro >> /Users/mattrose/ruby/start/model.rb:2: undefined method >> `prop_accessor' for Master:Class (NoMethodError) >> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ >> custom_require.rb:27:in `gem_original_require' >> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ >> custom_require.rb:27:in `require' >> from run.rb:10 >> >> Then, when I changed all of the prop_accessor to attr_accessor, I get >> this error instead, which I don't entirely get. >> >> matt-roses-computer:~/ruby/start mattrose$ nitro >> /Users/mattrose/ruby/start/model.rb:28: uninitialized constant >> User::Article (NameError) >> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ >> custom_require.rb:27:in `gem_original_require' >> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ >> custom_require.rb:27:in `require' >> from run.rb:10 >> >> Here's the code. Can someone tell me what I'm doing wrong? This >> used to work fine. >> >> class Blog >> attr_accessor :title, String >> attr_accessor :description, String >> has_many :users, User >> has_many :articles, Article >> def initialize(title,description) >> @title, at description = title,description >> end >> def to_s >> @title >> end >> end >> class User >> attr_accessor :username >> attr_accessor :password >> has_many :articles, Article >> belongs_to :blog, Blog >> def initialize(username,password,blog) >> @username, at password, at blog_oid = username,password,blog >> end >> def to_s >> @username >> end >> end >> >> class Article >> attr_accessor :title >> attr_accessor :body >> #has_many :comments >> belongs_to :blog, Blog >> belongs_to :user, User >> def initialize(title,body,user,blog) >> @title, at body, at user_oid, at blog_oid = title,body,user,blog >> end >> def to_s >> @title >> end >> end > > Am I right in thinking that if you want Og to persist an attribute you > _must_ give the class annotation? I think that's part of the change > from prop to attr. > > T. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From transfire at gmail.com Wed Nov 15 23:08:18 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Thu, 16 Nov 2006 04:08:18 -0000 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> Message-ID: <1163650098.170150.160640@f16g2000cwb.googlegroups.com> Matt Rose wrote: > Where is this documented? > > I have to say, I'm not very impressed right now. right now, it looks > like all my work has to be re-written from scratch. I've finally > figured out how to get my app to start, and the console is great to > work with, but I still can't get past the starting gate. I understand the feeling. It can be frustrating. And Nitro's been going through a lot of changes over the last year. But thankfully with this and the next release that looks to finally settle down. > I have two classes. Master is just a one-off table that holds some > meta-information. It has no relations to any other table. But while > I can use other models, I can't use this one. > > here's the class. > > class Master > attr_accessor :title > attr_accessor :description > attr_accessor :user > attr_accessor :pass > def initialize(title,desc,user,pass) > @title, at description, at user, at pass = title,desc,user,pass > end > def to_s > @title > end > end > > class Blog > attr_accessor :title, String > attr_accessor :description, String > has_many :users, User > has_many :articles, Article > def initialize(title,description) > @title, at description = title,description > end > def to_s > @title > end > end > > and here's the output. > > > >> matt-roses-computer:~/ruby/start mattrose$ nitro console > INFO: Og uses the Sqlite store. > /usr/local/lib/ruby/1.8/logger.rb:525:in `initialize':Errno::ENOENT: > No such file or directory - log/app.log > >> Blog.all > => > >> Master.all > NoMethodError: undefined method `all' for Master:Class > from (irb):2 > from :0 I'm thinking Master is not getting "enchanted" by Og. Try adding the class types: class Master attr_accessor :title, String attr_accessor :description, String attr_accessor :user, String attr_accessor :pass, String def initialize(title,desc,user,pass) @title, at description, at user, at pass = title,desc,user,pass end def to_s @title end end And see how that effects it. T. From aglarond at gmail.com Thu Nov 16 03:33:48 2006 From: aglarond at gmail.com (Dimitri Aivaliotis) Date: Thu, 16 Nov 2006 09:33:48 +0100 Subject: [Nitro] Brand New Oxyliquit! In-Reply-To: References: Message-ID: <55c107bf0611160033s56379bfbid7d318a006d56206@mail.gmail.com> On 11/15/06, Jonathan Buch wrote: > > > Please tell me (Jonathan) or Fabian if you like the new design! > I do. Great job, guys! Thanks for all your hard work. - Dimitri -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061116/8b7dce0f/attachment.html From john at oxyliquit.de Thu Nov 16 03:59:47 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 16 Nov 2006 09:59:47 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> Message-ID: <20061116085946.GA9278@oxyliquit.de> Hi, > Where is this documented? apparently we're suffering of the syndom called "Betriebsblindheit" in germany. This means that we use the new system for a very long time now and already forgot about how we actually do things and how we did them before. > > Am I right in thinking that if you want Og to persist an attribute you > > _must_ give the class annotation? I think that's part of the change > > from prop to attr. I now highlighted this in: http://oxyliquit.de/tip/32 Trans was very much right, the type now always has to be specified or it won't be able to distinguish between the normal attr_accessor and the modified one from Og. For the log error, you have to create a folder called 'log' in your application folder when you use the live mode. Any error messages saying that .ogmanager or .all or .find can't be found always say, that Og didn't enchant the model yet or the database connection has been dropped somehow. Also watch out for Og silently swallowing errors when you are in live mode. To the topic of enchanting a model, you have a few options there, refer to http://oxyliquit.de/tip/33 for details. Jonathan From george.moschovitis at gmail.com Thu Nov 16 04:09:34 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 16 Nov 2006 11:09:34 +0200 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: References: Message-ID: ok, thanks for the pass, I will process this today. Please remember, only patches that dont change the API of nitro//og are accepted for 0.41.0, 0.41.0 should be fully backwards compatible with 0.40.0 -g. On 11/15/06, Jonathan Buch wrote: > Hi, > > oxy is out, so a little time for other stuff. > > I also packed 3 other patches into it you might want to integrate. > I had them ready since a few weeks, didn't want to push them into > the release though. > You can ignore them for now if you see 'danger ahaid'. > > * add testcase for taggable, failing > > This one is the important one. > > 1) Failure: > test_all(TestOgTaggable) [/Volumes/Data/build/cvs/nitro/nitro-0.40-own/og/test/glue/tc_taggable.rb:52]: > <1> expected but was > <0>. > > This is the error I get. > I hope you can find the error! > > Thank you very much! > > Jo > > > Thu Oct 26 10:41:31 CEST 2006 Jonathan Buch > * Refactor SchemaInheritance > This patch avoids messing around with :ogtype within create_table(), the > property gets included into the class when SchemaInheritanceBase is > included into the base class. > This has a slight problem, it doesn't assure that the ogtype is the first > field in the database. To accomodate for that, the eval_og_allocate() > method has been adapted. This has to be revisited later, the current > approach is too inefficient. > It also removes the eval_og_allocate from the postgres adapter, the one > in sql.rb is the same. > Shall I send this patch? (1/5) [ynWvpxqadjk], or ? for help: y > > Thu Oct 26 10:58:14 CEST 2006 Jonathan Buch > * Alternative create_with(hash) method > # An alternative creation helper, does _not_ call the > # initialize method when there are mandatory elements. > Shall I send this patch? (2/5) [ynWvpxqadjk], or ? for help: y > > Thu Oct 26 11:04:49 CEST 2006 Jonathan Buch > * Extended entity .finder method > Can now handle relations. > Post.find_by_title_and_forum_name(title,forumName) > > class Forum > property :name, String > has_many :posts, Post > end > > class Post > property :title, String > property :message, String > belongs_to :forum, Forum > end > > 'forum' is the :forum from belongs_to, 'name' is a property from the > relations. It creates a SQL subquery to find the correct forum_oid. > Shall I send this patch? (3/5) [ynWvpxqadjk], or ? for help: y > > Wed Nov 15 19:07:09 CET 2006 Jonathan Buch > * add testcase for taggable, failing > Shall I send this patch? (5/5) [ynWvpxqadjk], or ? for help: y > > > -- > Feel the love > http://pinkjuice.com/pics/ruby.png > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > > -- http://gmosx.com/blog http://nitroproject.org From john at oxyliquit.de Thu Nov 16 04:34:44 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 16 Nov 2006 10:34:44 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> Message-ID: <20061116093443.GB9278@oxyliquit.de> Hi, > > - add rdoc comments in the sources > > I can do this, I think. I'm not that familiar with the source code, > but I can definitely submit patches where I can track stuff down. The rdocs aren't really bad, and almost every method has a comment. If you come about a function which doesn't, it would be very nice if you can do something about it and provide a patch. > > - improve nitroproject.org > > I was also thinking of doing this. There's one or two great bits of > documentation well hidden within the Wiki on the site, but it needs > serious fleshing out. Yes, definitly do this, I'm not one for wikis, they need constant caretaking like a little kittens in your bedroom. :P So yeah, it would be really cool if you can do a little docs if you get past your initial problems with Og. ;) Also take note of http://oxyliquit.de as a platform for information. We definitly need more people adding questions (and rating the answers, yes I keep an eye on you hit'n runners ;/), tips and tutorials. If you have any ideas on how oxywtf could be enhanced or on what topics you want a tip, I listen to requests. Jo From john at oxyliquit.de Thu Nov 16 04:38:56 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 16 Nov 2006 10:38:56 +0100 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: References: Message-ID: <20061116093856.GC9278@oxyliquit.de> Hi, > ok, thanks for the pass, I will process this today. Please remember, > only patches that dont change the API of nitro//og are accepted for > 0.41.0, 0.41.0 should be fully backwards compatible with 0.40.0 only apply the .finder patch. It only adds another functionality and doesn't touch any functionality already available and is really a neat feature. The others can wait for next release and can be enhanced further. Jo From fabian at fabian-buch.de Thu Nov 16 04:53:03 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 16 Nov 2006 10:53:03 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> Message-ID: <641424EA-5539-4B15-9A25-1C551B4E4654@fabian-buch.de> Am 16.11.2006 um 04:10 schrieb Matt Rose: > >>> matt-roses-computer:~/ruby/start mattrose$ nitro console > INFO: Og uses the Sqlite store. > /usr/local/lib/ruby/1.8/logger.rb:525:in `initialize':Errno::ENOENT: > No such file or directory - log/app.log >>> Blog.all > => >>> Master.all > NoMethodError: undefined method `all' for Master:Class > from (irb):2 > from :0 Master is only Og managed if it's attributes have types, like Trans already said. And for the logger: just create a log/ directory. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From al-nitrogen at none.at Thu Nov 16 05:19:08 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Thu, 16 Nov 2006 11:19:08 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <20061116085946.GA9278@oxyliquit.de> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <20061116085946.GA9278@oxyliquit.de> Message-ID: <20061116101908.GA16172@none.at> On Don 16.11.2006 09:59, Jonathan Buch wrote: >I now highlighted this in: http://oxyliquit.de/tip/32 Sorry that but: --- Application error Nitro failed to start properly --- Regards Aleks From al-nitrogen at none.at Thu Nov 16 05:54:20 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Thu, 16 Nov 2006 11:54:20 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <20061116101908.GA16172@none.at> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <20061116085946.GA9278@oxyliquit.de> <20061116101908.GA16172@none.at> Message-ID: <20061116105420.GA18781@none.at> On Don 16.11.2006 11:19, Aleksandar Lazic wrote: >On Don 16.11.2006 09:59, Jonathan Buch wrote: >>I now highlighted this in: http://oxyliquit.de/tip/32 > >Sorry that but: Please ignore it I was to fast ;-) BTW.: It looks faster to me have you make more then a upgrade to the new nitro?! ;-) Regards Aleks From george.moschovitis at gmail.com Thu Nov 16 07:04:52 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 16 Nov 2006 14:04:52 +0200 Subject: [Nitro] Next version roadmap In-Reply-To: <20061116093443.GB9278@oxyliquit.de> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> Message-ID: > > > - improve nitroproject.org In fact, I think this should be the first step, before working on documentation. Improve nitroproject.org to server as the infrastructure for the Nitro community. I will work actively on this during the next week. -g. -- http://gmosx.com/blog http://nitroproject.org From george.moschovitis at gmail.com Thu Nov 16 07:16:13 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 16 Nov 2006 14:16:13 +0200 Subject: [Nitro] Article about nitro... Message-ID: Check this out: http://www.infoq.com/news/2006/11/NitroOgRelease -g. -- http://gmosx.com/blog http://nitroproject.org From transfire at gmail.com Thu Nov 16 08:02:18 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Thu, 16 Nov 2006 13:02:18 -0000 Subject: [Nitro] Next version roadmap In-Reply-To: <20061116093443.GB9278@oxyliquit.de> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> Message-ID: <1163682138.601819.277650@h54g2000cwb.googlegroups.com> Jonathan Buch wrote: > Hi, > > > > - add rdoc comments in the sources > > > > I can do this, I think. I'm not that familiar with the source code, > > but I can definitely submit patches where I can track stuff down. > > The rdocs aren't really bad, and almost every method has a comment. If > you come about a function which doesn't, it would be very nice if you > can do something about it and provide a patch. > > > > - improve nitroproject.org > > > > I was also thinking of doing this. There's one or two great bits of > > documentation well hidden within the Wiki on the site, but it needs > > serious fleshing out. > > Yes, definitly do this, I'm not one for wikis, they need constant > caretaking like a little kittens in your bedroom. :P > > So yeah, it would be really cool if you can do a little docs if you get > past your initial problems with Og. ;) > Also take note of http://oxyliquit.de as a platform for information. We > definitly need more people adding questions (and rating the answers, yes > I keep an eye on you hit'n runners ;/), tips and tutorials. Is there a way to see a list of users? (It's telling me I'm not a user though I thought for sure that I had registered). > If you have any ideas on how oxywtf could be enhanced or on what topics > you want a tip, I listen to requests. An oxywtf for Facets could be cool, if not it's own system, maybe a categorized branch within NItro's T. From fabian at fabian-buch.de Thu Nov 16 10:13:58 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 16 Nov 2006 16:13:58 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <20061116105420.GA18781@none.at> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <20061116085946.GA9278@oxyliquit.de> <20061116101908.GA16172@none.at> <20061116105420.GA18781@none.at> Message-ID: <2B41A91E-EE0E-4F4A-A1D8-1801435F1889@fabian-buch.de> Am 16.11.2006 um 11:54 schrieb Aleksandar Lazic: > BTW.: It looks faster to me have you make more then a upgrade to > the new > nitro?! ;-) In the past it always ran in debug mode. Finally I convinced Kashia to let it run in live-mode :). Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From fabian at fabian-buch.de Thu Nov 16 10:16:42 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 16 Nov 2006 16:16:42 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> Message-ID: Am 16.11.2006 um 13:04 schrieb George Moschovitis: >>>> - improve nitroproject.org > > In fact, I think this should be the first step, before working on > documentation. Improve nitroproject.org to server as the > infrastructure for the Nitro community. I will work actively on this > during the next week. For that look at some of the tickets. For my part I'd like you to fix the easy-to-fix Feed tickets. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From fabian at fabian-buch.de Thu Nov 16 13:22:39 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 16 Nov 2006 19:22:39 +0100 Subject: [Nitro] Article about nitro... In-Reply-To: References: Message-ID: Am 16.11.2006 um 13:16 schrieb George Moschovitis: > Check this out: > > http://www.infoq.com/news/2006/11/NitroOgRelease cool! Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From fabian at fabian-buch.de Thu Nov 16 14:54:17 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 16 Nov 2006 20:54:17 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: <1163682138.601819.277650@h54g2000cwb.googlegroups.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> <1163682138.601819.277650@h54g2000cwb.googlegroups.com> Message-ID: <9E9EA3C4-50BD-4A99-99C4-E43FC308E86A@fabian-buch.de> Am 16.11.2006 um 14:02 schrieb transfire at gmail.com: > Is there a way to see a list of users? (It's telling me I'm not a user > though I thought for sure that I had registered). Just skimmed over the names and email addresses of the 60 registered Oxyliquit users. None seems to have a connection to you. So I guess you haven't registered yet. Brings me to the idea of letting users login with their name or email- address (whatever the user puts in the login-box). Will look how to implement that. > An oxywtf for Facets could be cool, if not it's own system, maybe a > categorized branch within NItro's Hmm.. nice idea. Main problem here: the virtual server where oxy runs on is on its limits already. We'll think about it. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From mattrose at folkwolf.net Thu Nov 16 20:20:06 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Thu, 16 Nov 2006 20:20:06 -0500 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <1163650098.170150.160640@f16g2000cwb.googlegroups.com> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> Message-ID: <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> Sorry to be a bother about this guys, but now I'm getting an error message. I kind of suspected this would happen, because of the params. How did we decide parameters would be called now in the action now? I have a setup page that takes form input, and passes it as GET params back to the same page. When I pass it no params, it works great, but when I try and pass it params via a GET request, I get this: http://localhost:9000/setup?title=masterblog&desc=master +blog&user=matt&pass=pass Path: /setup Wrong parameter count for setup(). the setup function in the controller looks like this: def setup p request.params blogs = Blog.all p @blogs #should only be able to go here when there's nothing setup if request.params.empty? && Master.all.empty? @render_master_form = true end if request.params.values.length == 4 && Master.all.empty? Master.create(*request.params.values) end p Master.find_one @master = Master.find_one if request.params.length == 2 Blog.create(*request.params.values) end end The request.params hash even shows up in the webrick output when I issue the GET request, but I still get that error. TIA. Again. This code *used* to work fine. I looked through the migration document, and even took an admittedly cursory look through the source code, and mailing list archives to figure out how to fix this. Sigh. I know everybody's trying their damnedest, and I know that Nitro is kind of a moving target right now, but, damn. Off to pore through Nitro code. I'll learn all this shit somehow. Boy I'm whiny this week :) On 15-Nov-06, at 11:08 PM, transfire at gmail.com wrote: > > Matt Rose wrote: >> Where is this documented? >> >> I have to say, I'm not very impressed right now. right now, it looks >> like all my work has to be re-written from scratch. I've finally >> figured out how to get my app to start, and the console is great to >> work with, but I still can't get past the starting gate. > > I understand the feeling. It can be frustrating. And Nitro's been > going > through a lot of changes over the last year. But thankfully with this > and the next release that looks to finally settle down. > >> I have two classes. Master is just a one-off table that holds some >> meta-information. It has no relations to any other table. But while >> I can use other models, I can't use this one. >> >> here's the class. >> >> class Master >> attr_accessor :title >> attr_accessor :description >> attr_accessor :user >> attr_accessor :pass >> def initialize(title,desc,user,pass) >> @title, at description, at user, at pass = title,desc,user,pass >> end >> def to_s >> @title >> end >> end >> >> class Blog >> attr_accessor :title, String >> attr_accessor :description, String >> has_many :users, User >> has_many :articles, Article >> def initialize(title,description) >> @title, at description = title,description >> end >> def to_s >> @title >> end >> end >> >> and here's the output. >> >> >>>> matt-roses-computer:~/ruby/start mattrose$ nitro console >> INFO: Og uses the Sqlite store. >> /usr/local/lib/ruby/1.8/logger.rb:525:in `initialize':Errno::ENOENT: >> No such file or directory - log/app.log >>>> Blog.all >> => >>>> Master.all >> NoMethodError: undefined method `all' for Master:Class >> from (irb):2 >> from :0 > > I'm thinking Master is not getting "enchanted" by Og. Try adding the > class types: > > class Master > attr_accessor :title, String > attr_accessor :description, String > attr_accessor :user, String > attr_accessor :pass, String > def initialize(title,desc,user,pass) > @title, at description, at user, at pass = title,desc,user,pass > end > def to_s > @title > end > end > > And see how that effects it. > > T. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From transfire at gmail.com Thu Nov 16 22:10:33 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Fri, 17 Nov 2006 03:10:33 -0000 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> Message-ID: <1163733033.933920.158400@b28g2000cwb.googlegroups.com> Matt Rose wrote: > Sorry to be a bother about this guys, but now I'm getting an error > message. I kind of suspected this would happen, because of the params. > > How did we decide parameters would be called now in the action now? > > I have a setup page that takes form input, and passes it as GET > params back to the same page. When I pass it no params, it works > great, but when I try and pass it params via a GET request, I get this: > > http://localhost:9000/setup?title=masterblog&desc=master > +blog&user=matt&pass=pass > > Path: /setup > Wrong parameter count for setup(). > > the setup function in the controller looks like this: > > def setup > p request.params > blogs = Blog.all > p @blogs > #should only be able to go here when there's nothing setup > if request.params.empty? && Master.all.empty? > @render_master_form = true > end > if request.params.values.length == 4 && Master.all.empty? > Master.create(*request.params.values) > end > p Master.find_one > @master = Master.find_one > if request.params.length == 2 > Blog.create(*request.params.values) > end > end I think that there was a move toward "meta-handling" the parameters. Try adding arguments to setup method rather then using request.params. I'm not certain about it but maybe one of these will work? def setup( title, desc ) def setup( params ) def setup( *params ) Again I could be comepletely wrong about this but I'm making a guestimation based on recent conversations and the error you got. T. From mattrose at folkwolf.net Thu Nov 16 22:17:51 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Thu, 16 Nov 2006 22:17:51 -0500 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> Message-ID: <47F29C00-DADA-4E48-856C-4E9004565342@folkwolf.net> Well, I found a semi handy comment in the code. From compiler.rb # Call action with given parameters, raises ActionError when the params # are wrong. I still don't know how params are wrong, or how to make them right. On 16-Nov-06, at 8:20 PM, Matt Rose wrote: > > Sorry to be a bother about this guys, but now I'm getting an error > message. I kind of suspected this would happen, because of the > params. > > How did we decide parameters would be called now in the action now? > > I have a setup page that takes form input, and passes it as GET > params back to the same page. When I pass it no params, it works > great, but when I try and pass it params via a GET request, I get > this: > > http://localhost:9000/setup?title=masterblog&desc=master > +blog&user=matt&pass=pass > > Path: /setup > Wrong parameter count for setup(). > > the setup function in the controller looks like this: > > def setup > p request.params > blogs = Blog.all > p @blogs > #should only be able to go here when there's nothing setup > if request.params.empty? && Master.all.empty? > @render_master_form = true > end > if request.params.values.length == 4 && Master.all.empty? > Master.create(*request.params.values) > end > p Master.find_one > @master = Master.find_one > if request.params.length == 2 > Blog.create(*request.params.values) > end > end > > The request.params hash even shows up in the webrick output when I > issue the GET request, but I still get that error. > > TIA. > > Again. This code *used* to work fine. I looked through the > migration document, and even took an admittedly cursory look through > the source code, and mailing list archives to figure out how to fix > this. > > Sigh. I know everybody's trying their damnedest, and I know that > Nitro is kind of a moving target right now, but, damn. > > Off to pore through Nitro code. I'll learn all this shit somehow. > > Boy I'm whiny this week :) > > > > > On 15-Nov-06, at 11:08 PM, transfire at gmail.com wrote: > >> >> Matt Rose wrote: >>> Where is this documented? >>> >>> I have to say, I'm not very impressed right now. right now, it >>> looks >>> like all my work has to be re-written from scratch. I've finally >>> figured out how to get my app to start, and the console is great to >>> work with, but I still can't get past the starting gate. >> >> I understand the feeling. It can be frustrating. And Nitro's been >> going >> through a lot of changes over the last year. But thankfully with this >> and the next release that looks to finally settle down. >> >>> I have two classes. Master is just a one-off table that holds some >>> meta-information. It has no relations to any other table. But >>> while >>> I can use other models, I can't use this one. >>> >>> here's the class. >>> >>> class Master >>> attr_accessor :title >>> attr_accessor :description >>> attr_accessor :user >>> attr_accessor :pass >>> def initialize(title,desc,user,pass) >>> @title, at description, at user, at pass = title,desc,user,pass >>> end >>> def to_s >>> @title >>> end >>> end >>> >>> class Blog >>> attr_accessor :title, String >>> attr_accessor :description, String >>> has_many :users, User >>> has_many :articles, Article >>> def initialize(title,description) >>> @title, at description = title,description >>> end >>> def to_s >>> @title >>> end >>> end >>> >>> and here's the output. >>> >>> >>>>> matt-roses-computer:~/ruby/start mattrose$ nitro console >>> INFO: Og uses the Sqlite store. >>> /usr/local/lib/ruby/1.8/logger.rb:525:in `initialize':Errno::ENOENT: >>> No such file or directory - log/app.log >>>>> Blog.all >>> => >>>>> Master.all >>> NoMethodError: undefined method `all' for Master:Class >>> from (irb):2 >>> from :0 >> >> I'm thinking Master is not getting "enchanted" by Og. Try adding the >> class types: >> >> class Master >> attr_accessor :title, String >> attr_accessor :description, String >> attr_accessor :user, String >> attr_accessor :pass, String >> def initialize(title,desc,user,pass) >> @title, at description, at user, at pass = title,desc,user,pass >> end >> def to_s >> @title >> end >> end >> >> And see how that effects it. >> >> T. >> >> _______________________________________________ >> Nitro-general mailing list >> Nitro-general at rubyforge.org >> http://rubyforge.org/mailman/listinfo/nitro-general > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From mattrose at folkwolf.net Thu Nov 16 22:30:13 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Thu, 16 Nov 2006 22:30:13 -0500 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <1163733033.933920.158400@b28g2000cwb.googlegroups.com> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> <1163733033.933920.158400@b28g2000cwb.googlegroups.com> Message-ID: <99CFFC19-8E23-4FBD-88AF-736E14D153AF@folkwolf.net> On 16-Nov-06, at 10:10 PM, transfire at gmail.com wrote: > > Matt Rose wrote: >> Sorry to be a bother about this guys, but now I'm getting an error >> message. I kind of suspected this would happen, because of the >> params. >> >> How did we decide parameters would be called now in the action now? >> >> I have a setup page that takes form input, and passes it as GET >> params back to the same page. When I pass it no params, it works >> great, but when I try and pass it params via a GET request, I get >> this: >> >> http://localhost:9000/setup?title=masterblog&desc=master >> +blog&user=matt&pass=pass >> >> Path: /setup >> Wrong parameter count for setup(). >> >> the setup function in the controller looks like this: >> >> def setup >> p request.params >> blogs = Blog.all >> p @blogs >> #should only be able to go here when there's nothing setup >> if request.params.empty? && Master.all.empty? >> @render_master_form = true >> end >> if request.params.values.length == 4 && Master.all.empty? >> Master.create(*request.params.values) >> end >> p Master.find_one >> @master = Master.find_one >> if request.params.length == 2 >> Blog.create(*request.params.values) >> end >> end > > I think that there was a move toward "meta-handling" the parameters. > Try adding arguments to setup method rather then using request.params. > I'm not certain about it but maybe one of these will work? > > def setup( title, desc ) > def setup( params ) > def setup( *params ) > > Again I could be comepletely wrong about this but I'm making a > guestimation based on recent conversations and the error you got. > Well, this is interesting, I changed the setup method to setup (params) and now I get this error message: Wrong parameter count for setup(masterblog, master blog). when passing in the same get string, which means it seems to be reading only the first two params. Now I'm really stumped. > T. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From fabian at fabian-buch.de Fri Nov 17 04:57:27 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Fri, 17 Nov 2006 10:57:27 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> Message-ID: <3079958A-B759-467C-AC0E-CFA9F3B9CDE4@fabian-buch.de> Am 17.11.2006 um 02:20 schrieb Matt Rose: > Sorry to be a bother about this guys, but now I'm getting an error > message. I kind of suspected this would happen, because of the > params. > > How did we decide parameters would be called now in the action now? The settings for param handling are: Nitro::Compiler.mixin_get_parameters = true Nitro::Compiler.non_strict_action_calling = false Don't see how this could be a problem with your code, but you could try playing with these two settings. (btw. there are generally two groups in Nitro, G prefers the above true/false, Jo and me false/false) > I have a setup page that takes form input, and passes it as GET > params back to the same page. When I pass it no params, it works > great, but when I try and pass it params via a GET request, I get > this: > > http://localhost:9000/setup?title=masterblog&desc=master > +blog&user=matt&pass=pass Just tested your action in a testapp here. Works both with and without your extra GET params here. How does your Server.map look like? Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Fri Nov 17 08:17:07 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 17 Nov 2006 15:17:07 +0200 Subject: [Nitro] Annotations Message-ID: Hello Tom, I would like to make Og work like this: class Article attr_accessor :title attr_accessor :hits end class Article ann :title, String ann :hits, Fixnum end be equivalent to: class Article attr_accessor :title, String attr_accessor :hits, Fixnum end I would appreciate it if you had a look at: glue/attribute.rb glue/attributeutils.rb and suggest ideas how this could be elegantly done. thanks in advance, George -- http://blog.gmosx.com http://nitroproject.org From john at oxyliquit.de Fri Nov 17 08:48:50 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 17 Nov 2006 14:48:50 +0100 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: References: <20061115135808.GA1374@oxyliquit.de> Message-ID: Hi, > please send a proper patch, at least including the test case. this took me an hour to find out what went wrong, see appended patch file. Fixes the taggable issue and remomves a TODO by implemention the Tag#tagged method. Jo -- Feel the love http://pinkjuice.com/pics/ruby.png -------------- next part -------------- A non-text attachment was scrubbed... Name: tags.patch.tar.bz2 Type: application/bzip2 Size: 1463 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061117/235e1ecd/attachment.bin From george.moschovitis at gmail.com Fri Nov 17 09:14:29 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 17 Nov 2006 16:14:29 +0200 Subject: [Nitro] removed working call/answer implementation? In-Reply-To: <83AE111C-0547-4C28-8639-3A2A4DC49455@fabian-buch.de> References: <0DE4EB50-49DB-4D1B-9A82-53444247F3D6@fabian-buch.de> <83AE111C-0547-4C28-8639-3A2A4DC49455@fabian-buch.de> Message-ID: ok thanks... -g. On 11/15/06, Fabian Buch wrote: > Found it again. I fixed call/answer somewhen in September already > which also got into the repo with one of the bigger bundles probably, > so didn't get noticed probably. It indeed didn't work without that > patch correctly which it doesn't now either. > > Attached to this mail is a patch that lets call/answer work correctly > again (for my usecases) and includes a small testcase too. > > Fabian > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Fri Nov 17 09:15:12 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 17 Nov 2006 16:15:12 +0200 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: <20061116093856.GC9278@oxyliquit.de> References: <20061116093856.GC9278@oxyliquit.de> Message-ID: Ok! perhaps I will add them all ;-) -g. On 11/16/06, Jonathan Buch wrote: > Hi, > > > ok, thanks for the pass, I will process this today. Please remember, > > only patches that dont change the API of nitro//og are accepted for > > 0.41.0, 0.41.0 should be fully backwards compatible with 0.40.0 > > only apply the .finder patch. > > It only adds another functionality and doesn't touch any functionality > already available and is really a neat feature. > > The others can wait for next release and can be enhanced further. > > Jo > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://nitroproject.org From transfire at gmail.com Fri Nov 17 18:39:17 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Fri, 17 Nov 2006 23:39:17 -0000 Subject: [Nitro] ratchets, parts and plugins Message-ID: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> hi-- was looking at rails plugin script this evening and thinking about what they are doing. my understanding is this: each rails app has a vendor/plugins directory, where plugins are installed via the plugin script or the rapt utility. (assuming i got this right) while i see the point considering the deployment limitations of web apps, doesn't it seem rather amazing that essentially copy-and-paste reusability is getting so much play? i developed my own "plugin" system (before i knew how rails' worked) and it functions as an indirect require. so you do: require_plugin 'someapp/pluginname' and this refernce file is read from a shared store which simply contains a list of lib files to actually require. the system is extremely simple, effective, versitle and reusable, and w/o copy-and-paste --plugins are just installed like any other app. of course I understand that there is a need for reusable copied parts and ratchets has a feature for that, which naturally fell out of reap's seed tool, eg. scaffolding a project. if you think about it, scaffolding a project is essentially copy-and-paste reusability. so i was able to integrate the two concepts. one can do: project scaffold --part part_name_or_url to add a pre-packaged part to a project. for a completely new project it's project scaffold --part new though one can just use 'project scaffold' b/c new is the default part in none is given. but now that i look at what rails is doing it appears i perhaps reversed the concepts. is a plugina part and a part a plugin ... had you all been talking about parts as analogous to rails' plugins, or different in regards to their reuse? myself, i sort of prefer the term 'scaffolding parts' (or just 'parts') for copy-and-paste reusability, and plugins for the other. one thing i did learn from rails plugin system is i need a way to unistall parts too. since ratchets is more flexible, in that in can install files anywhere within a project layout, its not as simple as removing a plugin folder, so i'll have work that out via some for of manifest --and it may have to wait for a later release. any thoughts on all this? T. From m.fellinger at gmail.com Sat Nov 18 04:41:13 2006 From: m.fellinger at gmail.com (Michael Fellinger) Date: Sat, 18 Nov 2006 18:41:13 +0900 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> Message-ID: <9c00d3e00611180141y289899f2ib53e2b74848b2e9e@mail.gmail.com> On 11/17/06, Matt Rose wrote: > > Sorry to be a bother about this guys, but now I'm getting an error > message. I kind of suspected this would happen, because of the params. > > How did we decide parameters would be called now in the action now? > > I have a setup page that takes form input, and passes it as GET > params back to the same page. When I pass it no params, it works > great, but when I try and pass it params via a GET request, I get this: > > http://localhost:9000/setup?title=masterblog&desc=master > +blog&user=matt&pass=pass > > Path: /setup > Wrong parameter count for setup(). > > the setup function in the controller looks like this: > > def setup > p request.params > blogs = Blog.all > p @blogs > #should only be able to go here when there's nothing setup > if request.params.empty? && Master.all.empty? > @render_master_form = true > end > if request.params.values.length == 4 && Master.all.empty? > Master.create(*request.params.values) > end > p Master.find_one > @master = Master.find_one > if request.params.length == 2 > Blog.create(*request.params.values) > end > end Well, now to something completely different: class FooController < Nitro::Controller def setup params = request.params #making things nicer ;) if Master.all.empty? @render_master_form = true if params.empty? Master.create_with(params) if params.size == 4 end @master = Master.find_one Blog.create_with(params) if params.size == 2 end end This will also spare you the unnecessary initialize-code in the model, as long as the form-fields have the correct name. also, just to play save, disable the buggy mode in Nitro-params-parsing ::Nitro::Compiler.mixin_get_parameters = false that should be all. hope it works ;) > > The request.params hash even shows up in the webrick output when I > issue the GET request, but I still get that error. > > TIA. > > Again. This code *used* to work fine. I looked through the > migration document, and even took an admittedly cursory look through > the source code, and mailing list archives to figure out how to fix > this. > > Sigh. I know everybody's trying their damnedest, and I know that > Nitro is kind of a moving target right now, but, damn. > > Off to pore through Nitro code. I'll learn all this shit somehow. > > Boy I'm whiny this week :) > > > > > On 15-Nov-06, at 11:08 PM, transfire at gmail.com wrote: > > > > > Matt Rose wrote: > >> Where is this documented? > >> > >> I have to say, I'm not very impressed right now. right now, it looks > >> like all my work has to be re-written from scratch. I've finally > >> figured out how to get my app to start, and the console is great to > >> work with, but I still can't get past the starting gate. > > > > I understand the feeling. It can be frustrating. And Nitro's been > > going > > through a lot of changes over the last year. But thankfully with this > > and the next release that looks to finally settle down. > > > >> I have two classes. Master is just a one-off table that holds some > >> meta-information. It has no relations to any other table. But while > >> I can use other models, I can't use this one. > >> > >> here's the class. > >> > >> class Master > >> attr_accessor :title > >> attr_accessor :description > >> attr_accessor :user > >> attr_accessor :pass > >> def initialize(title,desc,user,pass) > >> @title, at description, at user, at pass = title,desc,user,pass > >> end > >> def to_s > >> @title > >> end > >> end > >> > >> class Blog > >> attr_accessor :title, String > >> attr_accessor :description, String > >> has_many :users, User > >> has_many :articles, Article > >> def initialize(title,description) > >> @title, at description = title,description > >> end > >> def to_s > >> @title > >> end > >> end > >> > >> and here's the output. > >> > >> > >>>> matt-roses-computer:~/ruby/start mattrose$ nitro console > >> INFO: Og uses the Sqlite store. > >> /usr/local/lib/ruby/1.8/logger.rb:525:in `initialize':Errno::ENOENT: > >> No such file or directory - log/app.log > >>>> Blog.all > >> => > >>>> Master.all > >> NoMethodError: undefined method `all' for Master:Class > >> from (irb):2 > >> from :0 > > > > I'm thinking Master is not getting "enchanted" by Og. Try adding the > > class types: > > > > class Master > > attr_accessor :title, String > > attr_accessor :description, String > > attr_accessor :user, String > > attr_accessor :pass, String > > def initialize(title,desc,user,pass) > > @title, at description, at user, at pass = title,desc,user,pass > > end > > def to_s > > @title > > end > > end > > > > And see how that effects it. > > > > T. > > > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From rob at robmela.com Sat Nov 18 17:59:38 2006 From: rob at robmela.com (Robert Mela) Date: Sat, 18 Nov 2006 17:59:38 -0500 Subject: [Nitro] rdocs broken on nitroproject.org? In-Reply-To: <1163682138.601819.277650@h54g2000cwb.googlegroups.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> <1163682138.601819.277650@h54g2000cwb.googlegroups.com> Message-ID: <455F905A.60109@robmela.com> http://nitroproject.org/rdoc/nitro/index.html returns only a 7-byte HTML document consisting of "(error)", with no markup or anything... Is anyone else seeing this? -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061118/9464985d/attachment.vcf From dan at tastapod.com Sun Nov 19 17:39:43 2006 From: dan at tastapod.com (Dan North) Date: Sun, 19 Nov 2006 22:39:43 +0000 Subject: [Nitro] nitroproject.org bug and a change request Message-ID: <1163975984.9918.19.camel@localhost> Hi folks. On the nitroproject.org site, when I go to docs and click on any of the screencast links, I get a page that simply contains the text: (error) This is in Firefox 2.0 on Ubuntu 6.10, but it was happening before in Firefox 1.5.x in Ubuntu 6.06. Also, can I request that the command line utilities are renamed to start nitro-* (eg. nitro-gen). That way I can type nitro-[tab] and see the binaries/scripts it installed. (Plus, nitro-gen is kinda cool :) Thanks, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061119/c90b1497/attachment.html From dan at tastapod.com Sun Nov 19 17:19:51 2006 From: dan at tastapod.com (Dan North) Date: Sun, 19 Nov 2006 22:19:51 +0000 Subject: [Nitro] Next version roadmap In-Reply-To: <4559F7CB.8040401@gmail.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> Message-ID: <1163974791.9918.13.camel@localhost> There's docs and there's docs. To make nitro+og compelling (especially in the face of the "Rails is everything" pushback I'm getting from people I speak to) the following would be really helpful for me: - a 2-minute tutorial (the "elevator pitch" for nitro+og, especially compared to rails) - a 30-minute tutorial implementing a "basic" app, so: - authentication (logging in), users & groups - flow, e.g. multi-stage wizard with session state stored on the server - caching 101 (session level, user level, application level) for read-mostly apps - using css with nitro to style standard page elements - tables, lists etc - an ajax tutorial for muppets like me - asynch update of a page fragment - a "please wait" thing while something slow happens on the server - one of those cool fadey things that wordpress does when you update a setting - basically some eye candy! - an overview of the "preferred" JS library/libraries for doing funky web 2.0 apps Thanks for listening, Dan ps. Full disclosure: I want to write a couple of web apps and I know I want to use nitro, so this level of intro documentation would be exactly what I need to avoid trawling google and the source code! pps. To be honest, I haven't looked at the nitrohq site for a while, so please correct me if much of this is already in place. On Tue, 2006-11-14 at 18:07 +0100, Lionel Orry wrote: > > Reid Thompson a ?crit : > > On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: > >> Docs! > >> > > ++Docs > > +++Docs+++ !!! > > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061119/df90f18c/attachment.html From transfire at gmail.com Sun Nov 19 21:25:37 2006 From: transfire at gmail.com (TRANS) Date: Sun, 19 Nov 2006 21:25:37 -0500 Subject: [Nitro] 1 2 3 Testing Message-ID: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> Something's wrong with the list. This is just a test post. I thought the problem might have been just the with google-groups, but it looks like it may be the list after all since only a couple posts have gotten through in days. T. From george.moschovitis at gmail.com Mon Nov 20 03:20:59 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 20 Nov 2006 10:20:59 +0200 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: References: <20061115135808.GA1374@oxyliquit.de> Message-ID: thanks, On 11/17/06, Jonathan Buch wrote: > Hi, > > > please send a proper patch, at least including the test case. > > this took me an hour to find out what went wrong, see appended > patch file. > Fixes the taggable issue and remomves a TODO by implemention > the Tag#tagged method. > > Jo > > -- > Feel the love > http://pinkjuice.com/pics/ruby.png > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > > -- http://blog.gmosx.com http://nitroproject.org From john at oxyliquit.de Mon Nov 20 03:45:01 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Mon, 20 Nov 2006 09:45:01 +0100 Subject: [Nitro] nitro 0.40.0 changes? In-Reply-To: <99CFFC19-8E23-4FBD-88AF-736E14D153AF@folkwolf.net> References: <4AECB25C-6794-4802-9C87-08B0E68A4E65@folkwolf.net> <1163598101.495434.32530@f16g2000cwb.googlegroups.com> <3A6B2974-DE51-49BB-8AB1-C0D7F7EC3B1C@folkwolf.net> <1163650098.170150.160640@f16g2000cwb.googlegroups.com> <5999BB9D-0FC2-4925-96FE-6B45948CE299@folkwolf.net> <1163733033.933920.158400@b28g2000cwb.googlegroups.com> <99CFFC19-8E23-4FBD-88AF-736E14D153AF@folkwolf.net> Message-ID: Hi, >>> http://localhost:9000/setup?title=masterblog&desc=master >>> +blog&user=matt&pass=pass >>> Path: /setup >>> Wrong parameter count for setup(). This shouldn't happen at all, methods/actions without arguments are just called like that (regardless of any arguments). >> def setup( title, desc ) >> def setup( params ) >> def setup( *params ) Assuming the default: Nitro::Compiler.mixin_get_parameters = true you will probably want the method to like like: def setup(title, desc, user, pass) this 'should' get you all your needed arguments. > setup(params) and now I get this error message: > Wrong parameter count for setup(masterblog, master blog). This is weird, dunno how that can happen. If you have a little time, could you try to recreate that error as a testcase? In nitro/test/nitro/tc_controller_params.rb you will find a few controllers, and many testcases to look on how to build just another testcase. > when passing in the same get string, which means it seems to be > reading only the first two params. *scratch head* not following you there, mate :) > Wrong parameter count for setup(masterblog, master blog) should this be setup(masterblog, master, blog) ? Not getting that.. Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Mon Nov 20 09:06:17 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Mon, 20 Nov 2006 15:06:17 +0100 Subject: [Nitro] [PATCH] Fixes in repo In-Reply-To: References: <20061116093856.GC9278@oxyliquit.de> Message-ID: <20061120140616.GA32095@oxyliquit.de> Hi, > Ok! > > perhaps I will add them all ;-) sure, go ahaid ;D They all don't hurt much and are quite the right direction I think :P Jo From dan at tastapod.com Mon Nov 20 09:51:31 2006 From: dan at tastapod.com (Dan North) Date: Mon, 20 Nov 2006 14:51:31 +0000 Subject: [Nitro] nitroproject.org bug and a change request Message-ID: <4561C0F3.2050802@tastapod.com> Hi folks. On the nitroproject.org site, when I go to docs and click on any of the screencast links, I get a page that simply contains the text: (error) This is in Firefox 2.0 on Ubuntu 6.10, but it was happening before in Firefox 1.5.x in Ubuntu 6.06. Also, can I request that the command line utilities are renamed to start nitro-* (eg. nitro-gen). That way I can type nitro-[tab] and see the binaries/scripts it installed. (Plus, nitro-gen is kinda cool :) Thanks, Dan From dan at tastapod.com Mon Nov 20 09:57:39 2006 From: dan at tastapod.com (Dan North) Date: Mon, 20 Nov 2006 14:57:39 +0000 Subject: [Nitro] Next version roadmap In-Reply-To: <4559F7CB.8040401@gmail.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> Message-ID: <4561C263.8060301@tastapod.com> There's docs and there's docs. To make nitro compelling (especially in the face of the "Rails is everything" pushback I'm getting from people I speak to) the following would be really helpful for me: - a 2-minute tutorial (the "elevator pitch" for nitro, especially compared to rails) - a 30-minute tutorial implementing a "basic" app, so: - authentication (logging in), users & groups - flow, e.g. multi-stage wizard with session state stored on the server - persisting an object model, with common scenarios (e.g. the n+1 problem) - caching 101 (session level, user level, application level) for read-mostly apps - using css with nitro to style standard page elements - tables, lists etc - an ajax tutorial for muppets like me - asynch update of a page fragment - a "please wait" thing while something slow happens on the server - one of those cool fadey things that wordpress does when you update a setting - basically some eye candy! - an overview of the "preferred" JS library/libraries for doing funky web 2.0 apps Thanks for listening, Dan ps. Full disclosure: I want to write a couple of web apps and I /know/ I want to use nitro and og, so this level of intro documentation would be exactly what I need to avoid trawling google and the source code! pps. To be honest, I haven't looked at the nitrohq site for a while, so please correct me if much of this is already in place. Lionel Orry wrote: > Reid Thompson a ?crit : > >> On Tue, 2006-11-14 at 08:02 -0700, James Britt wrote: >> >>> Docs! >>> >>> >> ++Docs >> > > +++Docs+++ !!! > > >> _______________________________________________ >> Nitro-general mailing list >> Nitro-general at rubyforge.org >> http://rubyforge.org/mailman/listinfo/nitro-general >> >> > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061120/a7ce6b24/attachment.html From transfire at gmail.com Mon Nov 20 10:04:07 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Mon, 20 Nov 2006 15:04:07 -0000 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> Message-ID: <1164035047.762909.319810@m7g2000cwm.googlegroups.com> transfire at gmail.com wrote: > hi-- > > was looking at rails plugin script this evening and thinking about what > they are doing. my understanding is this: each rails app has a > vendor/plugins directory, where plugins are installed via the plugin > script or the rapt utility. (assuming i got this right) while i see the > point considering the deployment limitations of web apps, doesn't it > seem rather amazing that essentially copy-and-paste reusability is > getting so much play? > > i developed my own "plugin" system (before i knew how rails' worked) > and it functions as an indirect require. so you do: > > require_plugin 'someapp/pluginname' > > and this refernce file is read from a shared store which simply > contains a list of lib files to actually require. the system is > extremely simple, effective, versitle and reusable, and w/o > copy-and-paste --plugins are just installed like any other app. > > of course I understand that there is a need for reusable copied parts > and ratchets has a feature for that, which naturally fell out of reap's > seed tool, eg. scaffolding a project. if you think about it, > scaffolding a project is essentially copy-and-paste reusability. so i > was able to integrate the two concepts. one can do: > > project scaffold --part part_name_or_url > > to add a pre-packaged part to a project. for a completely new project > it's > > project scaffold --part new > > though one can just use 'project scaffold' b/c new is the default part > in none is given. > > but now that i look at what rails is doing it appears i perhaps > reversed the concepts. is a plugina part and a part a plugin ... had > you all been talking about parts as analogous to rails' plugins, or > different in regards to their reuse? myself, i sort of prefer the term > 'scaffolding parts' (or just 'parts') for copy-and-paste reusability, > and plugins for the other. > > one thing i did learn from rails plugin system is i need a way to > unistall parts too. since ratchets is more flexible, in that in can > install files anywhere within a project layout, its not as simple as > removing a plugin folder, so i'll have work that out via some for of > manifest --and it may have to wait for a later release. > > any thoughts on all this? Due to the mailing list issues I imagine few if any of you have had a chance to read this yet. Well, maybe that's a good thing. I've been thinking about it some more and have concluded that it is a mistake to further promote copy-and-paste reusability. Not only does it lead to a great deal of wasted memory/storage space, it encourages bad non-reuable design, which further exaserbates the problem. The upshot is that I removed the parts scaffolding I mentioned before from ratchets. (There's still the ability to create new project scaffolding of course.) If you want to make a nitro plugin, this is how it can work: just create a normal project, then add to the project: data/ ruby/ plugins/ nitro/ myplugin Where 'myplugin' is simply a text file with a list of files to require from the myplugin project. Eg. myplugin/foo.rb myplugin/bar.rb ... Then in a nitro app you can simply use: require_plugin 'nitro/myplugin' This doesn't handle plugin versioning at this point but that can be integrated in the future. One of the nice things about this too is that it works just as well with or without RubyGems . Are there any conditions in which this would not be enough to handle plugins for nitro? If so, it should be easy enough to build a wrapper around this basic functionality. But I would like to know what they would be, b/c maybe there are some general improvements that can be to this plugin system. T. From vikingtux at gmail.com Mon Nov 20 10:17:47 2006 From: vikingtux at gmail.com (Alexandre Gravem) Date: Mon, 20 Nov 2006 12:17:47 -0300 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> Message-ID: <40b05ebe0611200717l6ae35592r8d800c6823f4f2c3@mail.gmail.com> I think Nitro's parts are more alike to Rails' engines ( http://rails-engines.org/) as they can bring up complete applications (e.gthe Admin part, a Blog part, a Wiki part, ...) The plugins fells more loke extensions to the existent applications. If you have your own Og Mixin you could use and/or distribute this as a plugin. cheers, A. Gravem -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061120/da3e8964/attachment.html From george.moschovitis at gmail.com Mon Nov 20 11:04:33 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 20 Nov 2006 18:04:33 +0200 Subject: [Nitro] nitroproject.org bug and a change request In-Reply-To: <4561C0F3.2050802@tastapod.com> References: <4561C0F3.2050802@tastapod.com> Message-ID: Dan, thanks for the np.org tip. Until we fix this, you can check the videos from the links in the homepage. about the nitro commands I kindof agree with your proposal. This will have to wait because the next release will be 100% backwards compatible, unly fixes, optimizations, cleanups and docs are allowed. thanks, George. On 11/20/06, Dan North wrote: > Hi folks. > > On the nitroproject.org site, when I go to docs and click on any of the > screencast links, I get a page that simply contains the text: > > (error) > > This is in Firefox 2.0 on Ubuntu 6.10, but it was happening before in > Firefox 1.5.x in Ubuntu 6.06. > > Also, can I request that the command line utilities are renamed to start > nitro-* (eg. nitro-gen). That way I can type nitro-[tab] and see the > binaries/scripts it installed. (Plus, nitro-gen is kinda cool :) > > Thanks, > Dan > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 20 11:05:19 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 20 Nov 2006 18:05:19 +0200 Subject: [Nitro] 1 2 3 Testing In-Reply-To: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> References: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> Message-ID: Yeah, Tom... seems to me the list was down, but now things seem to be good ok. regards, George. On 11/20/06, TRANS wrote: > Something's wrong with the list. This is just a test post. > > I thought the problem might have been just the with google-groups, but > it looks like it may be the list after all since only a couple posts > have gotten through in days. > > T. > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 20 11:39:57 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 20 Nov 2006 18:39:57 +0200 Subject: [Nitro] nitroproject.org bug and a change request In-Reply-To: <1163975984.9918.19.camel@localhost> References: <1163975984.9918.19.camel@localhost> Message-ID: > (Plus, nitro-gen is kinda cool :) i know, (nitro)gen was the original name for my enhanced nitro (now called plasma) ;-) -g. -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 20 11:40:23 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 20 Nov 2006 18:40:23 +0200 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: <40b05ebe0611200717l6ae35592r8d800c6823f4f2c3@mail.gmail.com> References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> <40b05ebe0611200717l6ae35592r8d800c6823f4f2c3@mail.gmail.com> Message-ID: exactly. -g. On 11/20/06, Alexandre Gravem wrote: > I think Nitro's parts are more alike to Rails' engines > (http://rails-engines.org/) as they can bring up complete applications (e.g > the Admin part, a Blog part, a Wiki part, ...) > > The plugins fells more loke extensions to the existent applications. If you > have your own Og Mixin you could use and/or distribute this as a plugin. > > cheers, > A. Gravem > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 20 11:53:12 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 20 Nov 2006 18:53:12 +0200 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> <40b05ebe0611200717l6ae35592r8d800c6823f4f2c3@mail.gmail.com> Message-ID: This may help (copied from nitro/part.rb): # A part is a module of reusable functionality encapsulated as # a mini site/app. You can require (include) multiple parts in # your application. A part is in essence a high level component. # # The directory structure of a part mirrors the structure # of a typicall web application. By conventions we put the # main directories of parts in a root directory called 'part'. # # Let's demonstrate the above with an example. Two parts are # defined here. A user management part (users) and a CMS # (content). A typical dir structure goes like this ($ is a # directory in the load path, this means you can put parts in # multiple places as long as the are in the load path): # # $/part # parts will be stored here. # # $/part/users.rb # helper file used to 'require' the part. # $/part/users/public/ # $/part/users/controller.rb # $/part/users/controller/xml.rb # $/part/users/model/user.rb # $/part/users/model/acl.rb # $/part/users/template/login.xhtml # $/part/users/template/form.xinc # $/part/users/run.rb # starts an 'example' application for this part. # # $/part/content.rb # $/part/content/controller.rb # $/part/content/model.rb # ... # # Given this direcotry structure you can 'require' a part # like this: # # require 'part/users' # require 'part/content' # # The helper files (for example the file part/users.rb) typically # require the part files needed by default. # # The 'example' application start files (for example part/users/run.rb) # are optional. If present, they start a small application that # demonstrates the usage of the part. In the example app, the main # part controller is mounted at the root ('/'). Typically, in # your own applications, you will mount the controller as needed, # (for example: 'users' => UsersController, # 'blog' => 'ContentController') # # The files that reside in the public directory are typically # copied by a code generator to your application public dir. # # Part controllers setup the template root stack to lookup # templates in their local template dir (for example part/users/template) # if a template is not found in the applications normal template # root. In essence, by requiring a part a target application, # 'inherits' its templates. If you want to customize (override) # one template, just place a template with the same name in the # respective directory in the application template root. -g. -- http://blog.gmosx.com http://nitroproject.org From fabian at fabian-buch.de Mon Nov 20 13:08:34 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Mon, 20 Nov 2006 19:08:34 +0100 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: <1164035047.762909.319810@m7g2000cwm.googlegroups.com> References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> <1164035047.762909.319810@m7g2000cwm.googlegroups.com> Message-ID: Am 20.11.2006 um 16:04 schrieb transfire at gmail.com: > Are there any conditions in which this would not be enough to handle > plugins for nitro? If so, it should be easy enough to build a wrapper > around this basic functionality. But I would like to know what they > would be, b/c maybe there are some general improvements that can be to > this plugin system. Parts are indeed a little bit different to usual plugins. They are not like usual libraries. Imagine the following usecase: a Blogsystem (like flare) could be implemented as Part. Integrating it into several other of my nitro apps (for example extending Oxyliquit with a Blog), could be done via requiring this part into these apps. Now some of these apps might need a little bit customized blog system and would use this blog part just as basis, build up on it, change it and customize it. That's easily done, if you copy the Part to the app. Not so with a library that's used by all of the apps in the same way (except configurations and such). Additionally imagine I share this Part and release new versions over time. People will have integrated it into their apps and customized it to their needs, maybe in a way that makes it incompatible with newer versions released by me. Maybe some users like to stick to their customized one for some apps, but use a new version for newer apps (again likely to customize it). In these cases copying is the preferable way. Additionally take into account that Parts can include stylesheets, images and similar that have to be in a folder accessable by the webserver (in Nitro public/). These two things are what "gen part" handles via copying at the moment. If your ratchets could to this (how exactly could that be "wrapped around this basic functionality"?) it'd be great to replace gen. External helpers (discussed a month ago or so, then called "components") are more like pure libraries and probably would fit perfectly into your ratchets plugin grid. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From transfire at gmail.com Mon Nov 20 14:51:35 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Mon, 20 Nov 2006 19:51:35 -0000 Subject: [Nitro] rdocs broken on nitroproject.org? In-Reply-To: <455F905A.60109@robmela.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> <1163682138.601819.277650@h54g2000cwb.googlegroups.com> <455F905A.60109@robmela.com> Message-ID: <1164052295.788352.58820@m7g2000cwm.googlegroups.com> Yes From transfire at gmail.com Mon Nov 20 18:43:07 2006 From: transfire at gmail.com (transfire at gmail.com) Date: Mon, 20 Nov 2006 23:43:07 -0000 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> <1164035047.762909.319810@m7g2000cwm.googlegroups.com> Message-ID: <1164066187.876582.4820@h54g2000cwb.googlegroups.com> Fabian Buch wrote: > Am 20.11.2006 um 16:04 schrieb transfire at gmail.com: > > Are there any conditions in which this would not be enough to handle > > plugins for nitro? If so, it should be easy enough to build a wrapper > > around this basic functionality. But I would like to know what they > > would be, b/c maybe there are some general improvements that can be to > > this plugin system. > > Parts are indeed a little bit different to usual plugins. They are > not like usual libraries. > > Imagine the following usecase: a Blogsystem (like flare) could be > implemented as Part. Integrating it into several other of my nitro > apps (for example extending Oxyliquit with a Blog), could be done via > requiring this part into these apps. > Now some of these apps might need a little bit customized blog system > and would use this blog part just as basis, build up on it, change it > and customize it. That's easily done, if you copy the Part to the > app. Not so with a library that's used by all of the apps in the same > way (except configurations and such). > > Additionally imagine I share this Part and release new versions over > time. People will have integrated it into their apps and customized > it to their needs, maybe in a way that makes it incompatible with > newer versions released by me. Maybe some users like to stick to > their customized one for some apps, but use a new version for newer > apps (again likely to customize it). > > In these cases copying is the preferable way. > > Additionally take into account that Parts can include stylesheets, > images and similar that have to be in a folder accessable by the > webserver (in Nitro public/). > > These two things are what "gen part" handles via copying at the > moment. If your ratchets could to this (how exactly could that be > "wrapped around this basic functionality"?) it'd be great to replace > gen. > > External helpers (discussed a month ago or so, then called > "components") are more like pure libraries and probably would fit > perfectly into your ratchets plugin grid. Thanks Fabian. That really helped clarify things for me. I see your point about the the need for parts. In an ideal world all "parts" would be require-reusable, but obviously reality is often quite a bit messier. So it makes sense to also have more malliable copy-and-paste pieces. Let's do this, I'll put the Parts Tool on the todo list and return to it after the initial release of Ratchets. I'm getting damn close to release (finally) and I don't want to hold it up further at the moment. Then we can come back to the topic and give it more time and thought to make sure we can get a good general purpose utility that does the job well. T. From mattrose at folkwolf.net Mon Nov 20 18:27:27 2006 From: mattrose at folkwolf.net (Matt Rose) Date: Mon, 20 Nov 2006 18:27:27 -0500 Subject: [Nitro] 1 2 3 Testing In-Reply-To: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> References: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> Message-ID: I've noticed that the list got hung up there for a while. I sent out a message, and the replies went to the server, and to others, as I noticed replies in the archives, but I didn't get the replies for days. Matt On 19-Nov-06, at 9:25 PM, TRANS wrote: > Something's wrong with the list. This is just a test post. > > I thought the problem might have been just the with google-groups, but > it looks like it may be the list after all since only a couple posts > have gotten through in days. > > T. > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From itsme213 at hotmail.com Tue Nov 21 00:48:41 2006 From: itsme213 at hotmail.com (itsme213) Date: Mon, 20 Nov 2006 23:48:41 -0600 Subject: [Nitro] Article Message-ID: http://www.infoq.com/news/2006/11/NitroOgRelease was a nice article, but when someone goes to try the snippets shown they will get frustrated: - "require" missing - don't know what to do or expect after Nitro.start or Og.start Hth. From george.moschovitis at gmail.com Tue Nov 21 03:36:59 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 21 Nov 2006 10:36:59 +0200 Subject: [Nitro] rdocs broken on nitroproject.org? In-Reply-To: <1164052295.788352.58820@m7g2000cwm.googlegroups.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <20061116093443.GB9278@oxyliquit.de> <1163682138.601819.277650@h54g2000cwb.googlegroups.com> <455F905A.60109@robmela.com> <1164052295.788352.58820@m7g2000cwm.googlegroups.com> Message-ID: Ok will fix... check the docs from the homepage links for the moment... -g. On 11/20/06, transfire at gmail.com wrote: > Yes > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://nitroproject.org From fabian at fabian-buch.de Tue Nov 21 04:00:13 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Tue, 21 Nov 2006 10:00:13 +0100 Subject: [Nitro] ratchets, parts and plugins In-Reply-To: <1164066187.876582.4820@h54g2000cwb.googlegroups.com> References: <1163806757.358765.301810@b28g2000cwb.googlegroups.com> <1164035047.762909.319810@m7g2000cwm.googlegroups.com> <1164066187.876582.4820@h54g2000cwb.googlegroups.com> Message-ID: Am 21.11.2006 um 00:43 schrieb transfire at gmail.com: > Let's do this, I'll put the Parts Tool on the todo list and return to > it after the initial release of Ratchets. I'm getting damn close to > release (finally) and I don't want to hold it up further at the > moment. > Then we can come back to the topic and give it more time and > thought to > make sure we can get a good general purpose utility that does the job > well. Sounds great. Looking forward to the initial release of Ratchets. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From john at oxyliquit.de Tue Nov 21 13:09:58 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 21 Nov 2006 19:09:58 +0100 Subject: [Nitro] Article In-Reply-To: References: Message-ID: Hi, > http://www.infoq.com/news/2006/11/NitroOgRelease was a nice article, but > when someone goes to try the snippets shown they will get frustrated: > > - "require" missing > - don't know what to do or expect after Nitro.start or Og.start when I read that article, I got the impression that the examples were not to show how it works, but rather what a Nitro/Og program actually looks like (possibly to show differences to other frameworks). I hope that the other readers got this impression as well, since I don't really like frustrated people. :P Jo PS: (Gets me pretty frustrated that Oxyliquit takes around 4 seconds for a single reply... I apologize again for the outages and the crappy speed atm, looking for solutions.) -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Tue Nov 21 13:13:10 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 21 Nov 2006 19:13:10 +0100 Subject: [Nitro] 1 2 3 Testing In-Reply-To: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> References: <4b6f054f0611191825q77e5f04bs37a80347ab9ca187@mail.gmail.com> Message-ID: Hi, > Something's wrong with the list. This is just a test post. > > I thought the problem might have been just the with google-groups, but > it looks like it may be the list after all since only a couple posts > have gotten through in days. yeah yeah... got the impression that the list hang the whole weekend there.... Which makes the 20+ hour outage from Oxy kind of.. relative. yay! :P Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From itsme213 at hotmail.com Tue Nov 21 14:27:35 2006 From: itsme213 at hotmail.com (itsme213) Date: Tue, 21 Nov 2006 13:27:35 -0600 Subject: [Nitro] Article References: Message-ID: "Jonathan Buch" wrote > when I read that article, I got the impression that the examples were not > to show how it works, but rather what a Nitro/Og program actually looks > like (possibly to show differences to other frameworks). That's true. But it does not even tell me what wonders I will see when I do the magical Nitro.start or Og.start. e.g. I would guess the methods of the first HelloWorld magically become page urls, and the math(x,y) translates into a page with two fields in a form that, on submit, returns the interpolated string. I don't know if I guessed right, and if I try it out myself (which I did), I do not know what path and port to browse to on my localhost (please let me know ,btw). And the rdocs on nitroproject say Nitro 0.30.0; and the rdocs for 0.40 failed to install successfully on my PC ... Fewer barriers to interested users would probably help, is this getting closer? From john at oxyliquit.de Tue Nov 21 17:09:36 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 21 Nov 2006 23:09:36 +0100 Subject: [Nitro] Article In-Reply-To: References: Message-ID: <20061121220859.GA23937@oxyliquit.de> Hi, > That's true. But it does not even tell me what wonders I will see when I do > the magical Nitro.start or Og.start. Yes, like I said, I don't think that page aimed at information on how to use Nitro. It just tells readers that it exists, how it looks like and where to get further information. Giving a complete cut'n paste tutorial is beyond that simple article and I think it's unfair to treat the writer in this way. :) > e.g. I would guess the methods of the first HelloWorld magically become page > urls, and the math(x,y) translates into a page with two fields in a form > that, on submit, returns the interpolated string. I don't know if I guessed > right, and if I try it out myself (which I did), I do not know what path and > port to browse to on my localhost (please let me know ,btw). And the rdocs > on nitroproject say Nitro 0.30.0; and the rdocs for 0.40 failed to install > successfully on my PC ... If I interpret the example (never having used any web framework) I would guess, that 'index' and 'math' would print a string to stdout and that 'hello' returns a string. On how to call that from the browser side, I would have no idea, this should be clearly documented in the first tutorial you get to see when you enter the nitro world. > Fewer barriers to interested users would probably help, is this getting > closer? I'm not sure that if I put an example IOWA or Rails snippet on a website without telling how to use it, people would actually grok it at first sight. Pat Eyler makes a fine point at the bottom of his article, "Do yourself a favor and go check them out. ". I understand that you're just put off by the lack of documentation, but I disagree on trashing the post of Pat Eyler and the simple examples from George. Jonathan From itsme213 at hotmail.com Tue Nov 21 17:27:51 2006 From: itsme213 at hotmail.com (itsme213) Date: Tue, 21 Nov 2006 16:27:51 -0600 Subject: [Nitro] Article References: <20061121220859.GA23937@oxyliquit.de> Message-ID: "Jonathan Buch" wrote in message > I understand that you're just put off by the lack of documentation, but > I disagree on trashing the post of Pat Eyler and the simple examples > from George. Sorry, it was not my intent to trash anything or anyone, incl Pat or George or Nitro, so I certainly apologize if it came across like that :-( fyi - I am just revisiting Nitro 0.40 after deciding I should wait for a while ... From rob at robmela.com Tue Nov 21 21:42:24 2006 From: rob at robmela.com (Robert Mela) Date: Tue, 21 Nov 2006 21:42:24 -0500 Subject: [Nitro] Nitro 0.40, spark In-Reply-To: <20061121220859.GA23937@oxyliquit.de> References: <20061121220859.GA23937@oxyliquit.de> Message-ID: <4563B910.1060806@robmela.com> I figured spark and flare would be the perfect apps to learn nitro from, better than reading the docs ;) I'm trying a few different ways to run it: 1) directly from repo.nitroproject.org Check out repo.nitroproject.org, cd to the spark directory, and run: ~/nitro/repo.nitroproject.org/spark robertmela$ ruby -I../nitro/lib -I../glue/lib -I../og/lib -I../gen/lib -I /usr/local/lib/ruby/gems/1.8/gems/facets-1.4.5/lib -rubygems app.rb It does at least start (after configuring the db in app.rb). It gets as far as an exception "*undefined local variable or method `ogmanager' for WikiPage:Class", *on the first page request, but that's enough to keep me happy for now ;) 2) install gems from rubyforge, incl. facets-1.4.5 dependency, and *uninstall* more recent versions of facets. I get as far as the exception with "helper Sitemap not found" as described in http://www.nitroproject.org/tickets/35 I'm a little uncomfortable with the quickfix, esp. as I don't understand what functionality might be lost with the "sitemap" line changes. So, what exactly does the quickfix do, and what's the general approach for the real fix ( and when will the real fix be released -- maybe as 0.40.1... )? Thanks in advance. --- Here's the exception: /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:149:in `activate': can't activate facets (= 1.4.5), already activated facets-1.7.46] (Gem::Exception) from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:167:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:166:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:167:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:166:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:167:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:166:in `activate' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:26:in `require' from app.rb:3 -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061121/51039265/attachment.vcf From rob at robmela.com Tue Nov 21 22:01:26 2006 From: rob at robmela.com (Robert Mela) Date: Tue, 21 Nov 2006 22:01:26 -0500 Subject: [Nitro] spark success In-Reply-To: <20061121220859.GA23937@oxyliquit.de> References: <20061121220859.GA23937@oxyliquit.de> Message-ID: <4563BD86.6010609@robmela.com> my bad on the og exception in running spark -- I'd configed the adapter in app.rb to be sqlite3, not sqlite. The following command will start spark in repo.nitroproject.org/spark: ruby -I../nitro/lib -I../glue/lib -I../og/lib -I../gen/lib -I /usr/local/lib/ruby/gems/1.8/gems/facets-1.4.5/lib -I../nitro/src -rubygems app.rb Just out of curiosity, how should I use glycerin.rb? Seems it would obviate the need for the -I switches in the above ruby invocation. -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061121/80491f04/attachment.vcf From george.moschovitis at gmail.com Wed Nov 22 06:21:46 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 22 Nov 2006 13:21:46 +0200 Subject: [Nitro] Taggable patch Message-ID: Jonathan, is the latest Taggable patch you submitted backward compatible? Ie if I apply this will an older app with an older database schema work? thanks, George. -- http://blog.gmosx.com http://nitroproject.org From john at oxyliquit.de Wed Nov 22 08:20:08 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 14:20:08 +0100 Subject: [Nitro] Next version roadmap In-Reply-To: <4561C263.8060301@tastapod.com> References: <4559DA98.60406@gmail.com> <1163522251.4251.0.camel@jhereg> <4559F7CB.8040401@gmail.com> <4561C263.8060301@tastapod.com> Message-ID: Hi, > - a 2-minute tutorial (the "elevator pitch" for nitro, especially > compared to rails) 2 minute doesn't sound too bad :) Do you have an example what it should contain? I don't know nothing about rails, so I don't know what I would have to explain. Any 'standard' tutorial like this in the rails world which could be translated? > - a 30-minute tutorial implementing a "basic" app, so: > - authentication (logging in), users & groups > - flow, e.g. multi-stage wizard with session state stored on the server > - persisting an object model, with common scenarios (e.g. the n+1 > problem) > - caching 101 (session level, user level, application level) for > read-mostly apps > - using css with nitro to style standard page elements - tables, > lists etc I promised dynamix to write a tutorial about authentication (used in Oxywtf). I might just integrate your ideas on a tutorial here. > - persisting an object model, with common scenarios (e.g. the n+1 > problem) Could you define that further? Having trouble to understand the 'n+1 problem'. I will probably not go deep into caching, as I don't know anything about it. I still wait for George (ping!) to write something about that. Not sure what you mean here with CSS. CSS is just about styling, which is pretty much dependand on what you write in your xhtml files and isn't really special (except that there is a CSS compiler... which I never used). There are three common places where I know that one will be using css: * paging * tables with alternating background * forms Want me to visit those, or did I misunderstood your intention? Nothing promised yet about that tutorial, but I will try to get into the mood to write this. Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Wed Nov 22 08:20:30 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 14:20:30 +0100 Subject: [Nitro] Taggable patch In-Reply-To: References: Message-ID: Hi, > is the latest Taggable patch you submitted backward compatible? Ie if > I apply this will an older app with an older database schema work? I have been unable to use the Taggable implementation fully since 0.29 and had workarounds in Oxyliquit to circumvent several issues. I wonder how anyone was actually able to use it at all. But yes, the taggable patch does not change the interface and also the database schema is still the same. The bug was purely based on a Ruby side effect. Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Wed Nov 22 08:20:23 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 14:20:23 +0100 Subject: [Nitro] spark success In-Reply-To: <4563BD86.6010609@robmela.com> References: <20061121220859.GA23937@oxyliquit.de> <4563BD86.6010609@robmela.com> Message-ID: Hi, glad you got it working! > my bad on the og exception in running spark -- I'd configed the adapter > in app.rb to be sqlite3, not sqlite. > > The following command will start spark in repo.nitroproject.org/spark: > > ruby -I../nitro/lib -I../glue/lib -I../og/lib -I../gen/lib -I > /usr/local/lib/ruby/gems/1.8/gems/facets-1.4.5/lib -I../nitro/src > -rubygems app.rb I think you need only need those include statements, if you installed a facets > 1.4.5. I `require_gem 'facets', '= 1.4.5'` in all of my projects before doing anything else, just as a security guard (I don't have any bigger facets version installed, but just in case...) > Just out of curiosity, how should I use glycerin.rb? Seems it would > obviate the need for the -I switches in the above ruby invocation. The glycerin is when you don't require Nitro or Og via rubygems. The top of my run.rb's look like: require '/path/to/nitro/glycerin' require 'rubygems' # a specific facets version require_gem 'facets', '= 1.4.5' require 'facets' require 'nitro' require 'og' I never use gem versions because I like messing with the nitro installation all the time. ;) The glycerin.rb only sets up the paths for nitro, it does nothing about facets btw. Hope that helps, Jonathan -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Wed Nov 22 08:20:27 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 14:20:27 +0100 Subject: [Nitro] Article In-Reply-To: References: <20061121220859.GA23937@oxyliquit.de> Message-ID: Hi, > Sorry, it was not my intent to trash anything or anyone, incl Pat or George > or Nitro, so I certainly apologize if it came across like that :-( aye, I might have been a little too defensive there. ;) > fyi - I am just revisiting Nitro 0.40 after deciding I should wait for a > while ... What changed, is: * More documentation about Nitro/Og on oxyliquit.de Everything else is basically still the same *g* Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Wed Nov 22 08:20:28 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 14:20:28 +0100 Subject: [Nitro] Nitro 0.40, spark In-Reply-To: <4563B910.1060806@robmela.com> References: <20061121220859.GA23937@oxyliquit.de> <4563B910.1060806@robmela.com> Message-ID: Hi, > I'm a little uncomfortable with the quickfix, esp. as I don't > understand what functionality might be lost with the "sitemap" > line changes. The functionality was never intended to go into the official Nitro distribution (as I understand George) as it isn't good enough for general consumption. So you are actually not missing much I guess. > So, what exactly does the quickfix do, and what's the general > approach for the real fix ( and when will the real fix be > released -- maybe as 0.40.1... )? The quickfix just removes a few dangling dependencies which shouldn't be there in the first place. A cleanup/bugfix release should be out soon. George, any status, roadmap update? Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Wed Nov 22 08:38:54 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 22 Nov 2006 15:38:54 +0200 Subject: [Nitro] Nitro 0.40, spark In-Reply-To: References: <20061121220859.GA23937@oxyliquit.de> <4563B910.1060806@robmela.com> Message-ID: > A cleanup/bugfix release should be out soon. George, any status, > roadmap update? I will release nitro 0.41.0 some time next week, containing mainly bug fixes and cleanup. Aiming for next Tuesday. -g. -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Wed Nov 22 08:39:31 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 22 Nov 2006 15:39:31 +0200 Subject: [Nitro] Taggable patch In-Reply-To: References: Message-ID: Ok, btw I am using tags on many sites for a long time... -g. On 11/22/06, Jonathan Buch wrote: > Hi, > > > is the latest Taggable patch you submitted backward compatible? Ie if > > I apply this will an older app with an older database schema work? > > I have been unable to use the Taggable implementation fully since 0.29 > and had workarounds in Oxyliquit to circumvent several issues. I wonder > how anyone was actually able to use it at all. > > But yes, the taggable patch does not change the interface and also the > database schema is still the same. The bug was purely based on a Ruby > side effect. > > Jo > > -- > Feel the love > http://pinkjuice.com/pics/ruby.png > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://nitroproject.org From john at oxyliquit.de Wed Nov 22 13:09:23 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 19:09:23 +0100 Subject: [Nitro] Taggable patch In-Reply-To: References: Message-ID: <20061122180922.GA9683@oxyliquit.de> Hi, > btw I am using tags on many sites for a long time... you seem to be using them differently than me then. ;) Just as an example which I tripped over many times: tags = request['tagstring'].split(/[\s._;]/) Question.find_with_tags(tags) This fails horribly with psql, yet looks so easy. :) Of course, the workaround is simple for that glitch, but in the long I used taggable, this has only been one of many things which didn't work like my mind wants things to. But, it always have been problems with 'getting' stuff with tags, 'putting' has never been a problem. Nontheless, the taggable is a great invention and now it even works! ;D Jo From localuser at gmail.com Wed Nov 22 13:28:41 2006 From: localuser at gmail.com (Ed Chang) Date: Wed, 22 Nov 2006 12:28:41 -0600 Subject: [Nitro] Help with form_to_ Message-ID: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> On the nitroproject wiki, there's a six step tutorial that was written with Nitro version 0.3x in mind. However with the update Nitro to version 0.40, the example in step 6 (http://www.nitroproject.org/wiki/pages/Documentation__Programming_Nitro__Nitro_in_Action_one__step_6) is no longer accurate, and results in an error. Specifically, this line in step 6 of the tutorial fails: #{form_for User.find_by_name( @name )} After a bit of googling, I found some help at Oxyliquit (http://oxyliquit.de/question/84) and tried to re-write the line for step 6 to look like the following: #{form(:object => User, :action => :find_by_name) do |f| f.attributes f.submit 'Save' end} Now the page is displayed in the browser, but the following error is displayed: Path: /find_by_name No action for path '/find_by_name' on 'Hello' Anyone willing to guide a Ruby/Nitro newbie so I can at least complete step 6 of the tutorial? Thanks, Ed From john at oxyliquit.de Wed Nov 22 16:06:11 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 22 Nov 2006 22:06:11 +0100 Subject: [Nitro] Help with form_to_ In-Reply-To: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> Message-ID: <20061122210611.GA15389@oxyliquit.de> Hi, > #{form(:object => User, :action => :find_by_name) do |f| > f.attributes > f.submit 'Save' > end} > > Now the page is displayed in the browser, but the following error is displayed: > > Path: /find_by_name > No action for path '/find_by_name' on 'Hello' I assume the form appeared as expected on the first page? The translation you did from form_for() to form() is slightly incorrect. #{form_for User.find_by_name( @name )} #{form(:object => User.find_by_name(@name), :action => :update) do |f| f.attributes f.submit 'Save' end} The :action is the method which will be called when you press the submit button. You then need to handle the request: def update user = User.find_or_create_by_name(request['name']) request.fill(user) user.save redirect_to R(:list) end Or at least something along these lines. I haven't actually tested this but it should work just like this. Hope this helps, Jonathan From localuser at gmail.com Thu Nov 23 10:48:28 2006 From: localuser at gmail.com (Ed Chang) Date: Thu, 23 Nov 2006 09:48:28 -0600 Subject: [Nitro] Help with form_to_ In-Reply-To: <20061122210611.GA15389@oxyliquit.de> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> Message-ID: <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> Thanks for your help Jonathan - it's good to get some direction when one feels like he is groping in the dark. I'd appreciate some additional help from anyone that's interested in getting step 6 of the Nitro tutorial to work. I've modified controller.rb by adding the following method as Jonathan described in a previous email: def update() user = User.find_or_create_by_name(request['name']) request.fill(user) user.save redirect_to R(:list) end #update After that change, this URL http://localhost:9000/update?oid=1&name=Terry+Tate&description=Footballer&age=32 produces the following error message: Error Path: /update Wrong parameter count for update(). Reload this page. Go to the referer or the home page. In file '(eval)' : Stack Trace (eval):28:in `update_action' ... Hmm, wrong parameter count...so I modify the update method to look like the following: def update( oid, name, description, age ) Unfortunately, this too generates an error message: Error Path: /update near " ": syntax error Reload this page. Go to the referer or the home page. In file 'C:/Ruby/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0.1-mswin32/lib/sqlite3/errors.rb' : Now I wonder if I'm calling the correct method to save a new user. I grep the Nitro directory for find_or_create_by_name and find that only the Tag class uses this method. Looks like I should instead, be using User.find_or_create_by_name_and_age. I'm confused. At this point, help is much appreciated. Ed On 11/22/06, Jonathan Buch wrote: > Hi, > > > #{form(:object => User, :action => :find_by_name) do |f| > > f.attributes > > f.submit 'Save' > > end} > > > > Now the page is displayed in the browser, but the following error is displayed: > > > > Path: /find_by_name > > No action for path '/find_by_name' on 'Hello' > > I assume the form appeared as expected on the first page? > > The translation you did from form_for() to form() is slightly incorrect. > > #{form_for User.find_by_name( @name )} > #{form(:object => User.find_by_name(@name), :action => :update) do |f| > f.attributes > f.submit 'Save' > end} > > The :action is the method which will be called when you press the submit > button. You then need to handle the request: > > def update > user = User.find_or_create_by_name(request['name']) > request.fill(user) > user.save > redirect_to R(:list) > end > > Or at least something along these lines. I haven't actually tested > this but it should work just like this. > > Hope this helps, > > Jonathan > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From george.moschovitis at gmail.com Fri Nov 24 05:18:12 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 24 Nov 2006 12:18:12 +0200 Subject: [Nitro] Problems with String#hash Message-ID: Dear devs, I am facing a very NASTY problem with String#hash Here is the same code that I run on 3 different computers: root at kosh:~ # irb irb(main):001:0> "User".hash => 690465448 irb(main):002:0> VERSION => "1.8.2" C:\Documents and Settings\drak>irb irb(main):001:0> "User".hash => 690465448 irb(main):002:0> VERSION => "1.8.4" http://tryruby.hobix.com/ Interactive ruby ready. >> "User".hash => 690465448 >> VERSION => "1.8" root at victory:~# irb irb(main):001:0> "User".hash => -1457018200 irb(main):002:0> VERSION => "1.8.4" Please nottice that on the last case I get a different result! Any idea why this happens? thanks in advance for any help! George. -- http://blog.gmosx.com http://nitroproject.org From dan at tastapod.com Fri Nov 24 11:18:52 2006 From: dan at tastapod.com (Dan North) Date: Fri, 24 Nov 2006 16:18:52 +0000 Subject: [Nitro] Problems with String#hash In-Reply-To: References: Message-ID: <45671B6C.2050500@tastapod.com> Hi George. The contract with String.hash is that two objects that are equal will hash to the same value. (Other objects can hash to the same value too, but two equal objects can never have different hash values). Different versions of Ruby - or the same version of Ruby on different systems - or even different invocations of the same Ruby interpreter - are all free to make up any values they like, as long as they do it consistently /within an invocation/. What that means is, you can guarantee that if you put something in a hash bucket (say a Set or using as a key in a Hash) you will find it when you look for it with another key with the same value. What you /can't/ do is use a hash as, say, an externalized form for a string (which wouldn't make sense anyway, because hashes are lossy by design). Thinking about it, this means you shouldn't use hashes in any kind of DRb distributed cache or remoting, because the server's hash representation is not guaranteed to be the same as the client's. What are you trying to do with hashes that's causing you trouble? Cheers, Dan George Moschovitis wrote: > Dear devs, > > I am facing a very NASTY problem with String#hash > > Here is the same code that I run on 3 different computers: > > root at kosh:~ # irb > irb(main):001:0> "User".hash > => 690465448 > irb(main):002:0> VERSION > => "1.8.2" > > C:\Documents and Settings\drak>irb > irb(main):001:0> "User".hash > => 690465448 > irb(main):002:0> VERSION > => "1.8.4" > > http://tryruby.hobix.com/ > Interactive ruby ready. > >>> "User".hash >>> > => 690465448 > >>> VERSION >>> > => "1.8" > > root at victory:~# irb > irb(main):001:0> "User".hash > => -1457018200 > irb(main):002:0> VERSION > => "1.8.4" > > Please nottice that on the last case I get a different result! Any > idea why this happens? > > thanks in advance for any help! > > George. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061124/7f52095e/attachment.html From john at oxyliquit.de Fri Nov 24 14:00:54 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 24 Nov 2006 20:00:54 +0100 Subject: [Nitro] Help with form_to_ In-Reply-To: <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> Message-ID: Hi, > Wrong parameter count for update(). ah ah.... this might be connected to param injecting somehow... please add those line to your run.rb before Nitro.start : Nitro::Compiler.mixin_get_parameters = false In short, this method prevents nitro from mixing in the get parameters into the argument list of the function. This could make my version of the method work. George: can you verify that the params are working correctly with the setting to true? I think I've seen this error message the second time now... > def update( oid, name, description, age ) > In file 'C:/Ruby/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0.1-mswin32/lib/sqlite3/errors.rb' Not sure, like you said, too generic error. Og is a bit fast at swallowing errors. Set `$DBG = true` in your run.rb to get Og to fail on bad sql and other errors, this should show you what went wrong. > Now I wonder if I'm calling the correct method to save a new user. I > grep the Nitro directory for find_or_create_by_name and find that only > the Tag class uses this method. Looks like I should instead, be using > User.find_or_create_by_name_and_age. This method is 'cought' in `method_missing` and redirected to the method `finder`. In the way I designed you the .update method the age and the rest gets set by request.fill(obj). It just uses the name to create a new one (and the name thus should be set unique in the model). Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From noe.rubinstein at gmail.com Sat Nov 25 03:09:48 2006 From: noe.rubinstein at gmail.com (=?UTF-8?Q?No=C3=A9_Rubinstein?=) Date: Sat, 25 Nov 2006 09:09:48 +0100 Subject: [Nitro] CDATA disappears Message-ID: Hello, world ! When I put a CDATA section in a Nitro .xhtml file, it is removed by Nitro's parser. example : I write : I get in the final page : Is there a way to put a CDATA section in a Nitro page without it being removed ? From lasso at lassoweb.se Sat Nov 25 03:54:10 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Sat, 25 Nov 2006 09:54:10 +0100 Subject: [Nitro] CDATA disappears In-Reply-To: References: Message-ID: <456804B2.5050303@lassoweb.se> Hi! It's probably caused by the omission of the cdata method (part of the REXML::StreamListener interface) in one or more of Nitro's compilers. I'll have a look and see if i'll can come up with a patch to fix it. Kindly /lasso -- ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ No? Rubinstein skrev: > Hello, world ! > > When I put a CDATA section in a Nitro .xhtml file, it is removed by > Nitro's parser. > > example : > I write : > > > I get in the final page : > > > Is there a way to put a CDATA section in a Nitro page without it being removed ? > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general From lasso at lassoweb.se Sat Nov 25 08:09:14 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Sat, 25 Nov 2006 14:09:14 +0100 Subject: [Nitro] CDATA disappears In-Reply-To: References: Message-ID: <4568407A.4090308@lassoweb.se> Attached patch fixes this issue. Can you apply this, George? Sincerely /lasso -- ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ No? Rubinstein skrev: > Hello, world ! > > When I put a CDATA section in a Nitro .xhtml file, it is removed by > Nitro's parser. > > example : > I write : > > > I get in the final page : > > > Is there a way to put a CDATA section in a Nitro page without it being removed ? > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general -------------- next part -------------- A non-text attachment was scrubbed... Name: nitro_compiler_cdata_fix.gz Type: application/gzip Size: 1425 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061125/9d9f731b/attachment-0001.bin From lasso at lassoweb.se Sat Nov 25 08:07:56 2006 From: lasso at lassoweb.se (Lars Olsson) Date: Sat, 25 Nov 2006 14:07:56 +0100 Subject: [Nitro] CDATA disappears In-Reply-To: References: Message-ID: <4568402C.1080808@lassoweb.se> Attached patch fixes this issue. Can you apply this, George? Sincerely /lasso -- ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ No? Rubinstein skrev: > Hello, world ! > > When I put a CDATA section in a Nitro .xhtml file, it is removed by > Nitro's parser. > > example : > I write : > > > I get in the final page : > > > Is there a way to put a CDATA section in a Nitro page without it being removed ? > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general -------------- next part -------------- A non-text attachment was scrubbed... Name: nitro_compiler_cdata_fix.gz Type: application/gzip Size: 1425 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061125/e6c188b0/attachment.bin From noe.rubinstein at gmail.com Sat Nov 25 12:59:11 2006 From: noe.rubinstein at gmail.com (=?UTF-8?Q?No=C3=A9_Rubinstein?=) Date: Sat, 25 Nov 2006 18:59:11 +0100 Subject: [Nitro] CDATA disappears In-Reply-To: <4568407A.4090308@lassoweb.se> References: <4568407A.4090308@lassoweb.se> Message-ID: Wow ! Only 5 hours between "report" and fix o_o You're amazing. Thank very much. 2006/11/25, Lars Olsson : > Attached patch fixes this issue. Can you apply this, George? > > > Sincerely > > /lasso > > -- > ________________________________________ > Lars Olsson > lasso at lassoweb.se > http://www.lassoweb.se/ > > > > No? Rubinstein skrev: > > Hello, world ! > > > > When I put a CDATA section in a Nitro .xhtml file, it is removed by > > Nitro's parser. > > > > example : > > I write : > > > > > > I get in the final page : > > > > > > Is there a way to put a CDATA section in a Nitro page without it being removed ? > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > > From george.moschovitis at gmail.com Sat Nov 25 13:01:10 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 25 Nov 2006 20:01:10 +0200 Subject: [Nitro] CDATA disappears In-Reply-To: <4568402C.1080808@lassoweb.se> References: <4568402C.1080808@lassoweb.se> Message-ID: Ok, will apply this. thanks! -g. On 11/25/06, Lars Olsson wrote: > Attached patch fixes this issue. Can you apply this, George? > > > Sincerely > > /lasso > > -- > ________________________________________ > Lars Olsson > lasso at lassoweb.se > http://www.lassoweb.se/ > > > > No? Rubinstein skrev: > > Hello, world ! > > > > When I put a CDATA section in a Nitro .xhtml file, it is removed by > > Nitro's parser. > > > > example : > > I write : > > > > > > I get in the final page : > > > > > > Is there a way to put a CDATA section in a Nitro page without it being removed ? > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Sat Nov 25 13:09:58 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 25 Nov 2006 20:09:58 +0200 Subject: [Nitro] Problems with String#hash In-Reply-To: <45671B6C.2050500@tastapod.com> References: <45671B6C.2050500@tastapod.com> Message-ID: > What are you trying to do with hashes that's causing you trouble? I am trying to move an old (4 years old) web application to a new server. The app stores some hashes in the database (bad design) and the problem now is that my data is useless. This seems to be a problem with 64bits. -g. -- http://blog.gmosx.com http://nitroproject.org From dan at tastapod.com Sat Nov 25 15:23:29 2006 From: dan at tastapod.com (Dan North) Date: Sat, 25 Nov 2006 20:23:29 +0000 Subject: [Nitro] Problems with String#hash In-Reply-To: References: <45671B6C.2050500@tastapod.com> Message-ID: <4568A641.2060302@tastapod.com> It sounds like you need to do a bit of data forensics - finding out which version of Ruby on which platform created those hashes. If you can get them back to the original strings (??) and then externalise them again as a standard hash - say an MD5 sum - then you're good again. If not, you'll need to excavate the algorithm that created the original hashes, and keep it somewhere as custom code. Otherwise, you're right - your data is useless... Good luck, Dan George Moschovitis wrote: >> What are you trying to do with hashes that's causing you trouble? >> > > I am trying to move an old (4 years old) web application to a new > server. The app stores some hashes in the database (bad design) and > the problem now is that my data is useless. This seems to be a problem > with 64bits. > > -g. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061125/35d72c52/attachment.html From al-nitrogen at none.at Sun Nov 26 04:29:20 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Sun, 26 Nov 2006 10:29:20 +0100 Subject: [Nitro] Bug and feature Request Message-ID: <20061126092920.GB21301@none.at> Hi, I have try to call nitro and have get the following error: --- /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.40.0/bin/nitro -help /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.40.0/bin/nitro:5:in `require': no such file to load -- facets/more/command (LoadError) from /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.40.0/bin/nitro:5 --- After I have add 'ruby -rubygems' before the nitro call it works ;-) Is it possible to add such a similar code to the nitro-cli: --- eval facets if ok => go further if nok => try with rubygems if ok => go further else by by baby! --- How about to add the '--help' option wich show all available options? Regards Aleks From m.fellinger at gmail.com Sun Nov 26 07:29:06 2006 From: m.fellinger at gmail.com (Michael Fellinger) Date: Sun, 26 Nov 2006 21:29:06 +0900 Subject: [Nitro] Bug and feature Request In-Reply-To: <20061126092920.GB21301@none.at> References: <20061126092920.GB21301@none.at> Message-ID: <9c00d3e00611260429t1e6869a6t26bf936e95fde23@mail.gmail.com> On 11/26/06, Aleksandar Lazic wrote: > Hi, > > I have try to call nitro and have get the following error: > > --- > /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.40.0/bin/nitro -help > > /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.40.0/bin/nitro:5:in > `require': no such file to load -- facets/more/command (LoadError) > from > /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.40.0/bin/nitro:5 > --- > > After I have add 'ruby -rubygems' before the nitro call it works ;-) > > Is it possible to add such a similar code to the nitro-cli: > > --- > eval facets > if ok => go further > if nok => try with rubygems > if ok => go further > else by by baby! > --- in actual ruby: begin require 'facets' rescue LoadError begin require 'rubygems' require 'facets' end end > > How about to add the '--help' option wich show all available options? > > Regards > > Aleks > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From al-nitrogen at none.at Sun Nov 26 08:31:09 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Sun, 26 Nov 2006 14:31:09 +0100 Subject: [Nitro] Bug and feature Request In-Reply-To: <9c00d3e00611260429t1e6869a6t26bf936e95fde23@mail.gmail.com> References: <20061126092920.GB21301@none.at> <9c00d3e00611260429t1e6869a6t26bf936e95fde23@mail.gmail.com> Message-ID: <20061126133109.GA3162@none.at> On Son 26.11.2006 21:29, Michael Fellinger wrote: >On 11/26/06, Aleksandar Lazic wrote: > >> Is it possible to add such a similar code to the nitro-cli: >> >> eval facets >> if ok => go further >> if nok => try with rubygems >> if ok => go further >> else by by baby! > >in actual ruby: > >begin > require 'facets' >rescue LoadError > begin > require 'rubygems' > require 'facets' > end >end Cool thanks ;-)))) For archive purpose: I have know this lines in bin/nitro: --- . . #require 'facets/more/command' begin require 'facets/more/command' rescue LoadError begin require 'rubygems' require 'facets/more/command' end end . . --- @George: how about to add this to 0.41.x ;-) Regards Aleks From rob at robmela.com Sun Nov 26 14:40:16 2006 From: rob at robmela.com (Robert Mela) Date: Sun, 26 Nov 2006 14:40:16 -0500 Subject: [Nitro] flare quickfix and question In-Reply-To: References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> Message-ID: <4569EDA0.6000506@robmela.com> Started flare and tried http://localhost:9000/admin Got "undefined local variable or method `sitepath' for #" Added this to to nitro/lib/part/admin/helper.rb, which fixes the problem, and puts something halfway appropriate in the title bar of the browser: def sitepath "#{@request.headers['REQUEST_URI']} on #{@request.headers['SERVER_NAME']}" end I can now manage the og database for flare. There is a class SitePath in skin.rb. SitePath's render produces a clickable sitepath ( breadcrumb ) trail. So should this 'sitepath' method in helper.rb should be called 'title_path' or something? Better yet, maybe templates could get request headers directly from the Request object, via methods like '@request.get_header_request_uri' -- methods dynamically added as they are needed ( kind of like ActiveRecord's find_by_.... ) FWIW, I'd be happy to file a ticket with a patch, but I keep getting that nearly-blank "(error)" page when i try to reset my password. *** Looked at the stack trace: * /Users/robertmela/nitro/src/nitro/lib/nitro/publishable.rb:109:in `method_missing' 104: base.module_eval do 105: def method_missing(action, *args) 106: if Compiler.new(self.class).compile(action) 107: send(action, *args) 108: else 109: super 110: end 111: end 112: end 113: 114: # Does this publishable respond to the given action? /Users/robertmela/nitro/src/nitro/lib/part/admin/template/index.xhtml:8:in `index_template' 1: @out << < 5: 6: 7: 8: 9: George Moschovitis 10: 11: (eval):33:in `index_action' /Users/robertmela/nitro/src/nitro/lib/nitro/publishable.rb:107:in `method_missing' 102: # for this controller. 103: 104: base.module_eval do 105: def method_missing(action, *args) 106: if Compiler.new(self.class).compile(action) 107: send(action, *args) 108: else 109: super 110: end 111: end 112: end /Users/robertmela/nitro/src/nitro/lib/nitro/render.rb:129:in `render' 124: 125: if self.class == @controller 126: self.send(action) 127: else 128: puts "context='#{@context}' action='#{action}'\n" 129: @controller.new(@context).send(action) 130: end 131: 132: Controller.replace_current(old_controller) 133: @context.level -= 1 134: /Users/robertmela/nitro/src/nitro/lib/nitro/adapter/webrick.rb:171:in `do_GET' 166: context.headers['REQUEST_URI'] = '/' + context.headers['REQUEST_URI'] 167: 168: Cgi.parse_params(context) 169: Cgi.parse_cookies(context) 170: 171: context.render(path) 172: 173: res.status = context.status 174: res.instance_variable_set(:@header, context.response_headers || {}) 175: res.instance_variable_set(:@cookies, context.response_cookies || {}) 176: res.body = context.out /usr/local/lib/ruby/1.8/webrick/httpservlet/abstract.rb:35:in `service' 30: end 31: 32: def service(req, res) 33: method_name = "do_" + req.request_method.gsub(/-/, "_") 34: if respond_to?(method_name) 35: __send__(method_name, req, res) 36: else 37: raise HTTPStatus::MethodNotAllowed, 38: "unsupported method `#{req.request_method}'." 39: end 40: end /usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' 99: raise HTTPStatus::NotFound, "`#{req.path}' not found." unless servlet 100: req.script_name = script_name 101: req.path_info = path_info 102: si = servlet.get_instance(self, *options) 103: @logger.debug(format("%s is invoked.", si.class.name)) 104: si.service(req, res) 105: end 106: 107: def do_OPTIONS(req, res) 108: res["allow"] = "GET,HEAD,POST,OPTIONS" 109: end /usr/local/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' 60: res.keep_alive = req.keep_alive? 61: server = lookup_server(req) || self 62: if callback = server[:RequestCallback] || server[:RequestHandler] 63: callback.call(req, res) 64: end 65: server.service(req, res) 66: rescue HTTPStatus::EOFError, HTTPStatus::RequestTimeout => ex 67: res.set_error(ex) 68: rescue HTTPStatus::Error => ex 69: @logger.error(ex.message) 70: res.set_error(ex) /usr/local/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' 168: rescue SocketError 169: @logger.debug "accept:
" 170: raise 171: end 172: call_callback(:AcceptCallback, sock) 173: block ? block.call(sock) : run(sock) 174: rescue Errno::ENOTCONN 175: @logger.debug "Errno::ENOTCONN raised" 176: rescue ServerError => ex 177: msg = "#{ex.class}: #{ex.message}\n\t#{ex.backtrace[0]}" 178: @logger.error msg /usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' 157: end 158: return sock 159: end 160: 161: def start_thread(sock, &block) 162: Thread.start{ 163: begin 164: Thread.current[:WEBrickSocket] = sock 165: begin 166: addr = sock.peeraddr 167: @logger.debug "accept: #{addr[3]}:#{addr[1]}" /usr/local/lib/ruby/1.8/webrick/server.rb:95:in `start' 90: begin 91: if svrs = IO.select(@listeners, nil, nil, 2.0) 92: svrs[0].each{|svr| 93: @tokens.pop # blocks while no token is there. 94: if sock = accept_client(svr) 95: th = start_thread(sock, &block) 96: th[:WEBrickThread] = true 97: thgroup.add(th) 98: else 99: @tokens.push(nil) 100: end /usr/local/lib/ruby/1.8/webrick/server.rb:92:in `start' 87: thgroup = ThreadGroup.new 88: @status = :Running 89: while @status == :Running 90: begin 91: if svrs = IO.select(@listeners, nil, nil, 2.0) 92: svrs[0].each{|svr| 93: @tokens.pop # blocks while no token is there. 94: if sock = accept_client(svr) 95: th = start_thread(sock, &block) 96: th[:WEBrickThread] = true 97: thgroup.add(th) /usr/local/lib/ruby/1.8/webrick/server.rb:23:in `start' 18: 19: class ServerError < StandardError; end 20: 21: class SimpleServer 22: def SimpleServer.start 23: yield 24: end 25: end 26: 27: class Daemon 28: def Daemon.start /usr/local/lib/ruby/1.8/webrick/server.rb:82:in `start' 77: 78: def start(&block) 79: raise ServerError, "already started." if @status != :Stop 80: server_type = @config[:ServerType] || SimpleServer 81: 82: server_type.start{ 83: @logger.info \ 84: "#{self.class}#start: pid=#{$$} port=#{@config[:Port]}" 85: call_callback(:StartCallback) 86: 87: thgroup = ThreadGroup.new /Users/robertmela/nitro/src/nitro/lib/nitro/adapter/webrick.rb:66:in `start' 61: 62: @webrick.mount('/', WebrickAdapter, server) 63: 64: initialize_webrick(server) 65: 66: @webrick.start 67: end 68: 69: # Stop the Webrick adapter. 70: 71: def stop /Users/robertmela/nitro/src/nitro/lib/nitro/server/runner.rb:323:in `invoke_server' 318: when :webrick 319: require 'nitro/adapter/webrick' 320: Logger.info "Starting Webrick on #{server.address}:#{server.port}" 321: Logger.info "Press Ctrl-C to shutdown; Run with --help for options." 322: Logger.info "" 323: Webrick.start(server) 324: 325: when :mongrel 326: require 'nitro/adapter/mongrel' 327: Logger.info "Starting Mongrel on #{server.address}:#{server.port}" 328: Logger.info "Press Ctrl-C to shutdown; Run with --help for options." /Users/robertmela/nitro/src/nitro/lib/nitro/server/runner.rb:282:in `invoke' 277: $server = server 278: $app = ConsoleAdapter.new(server) 279: $cache = Caching::Proxy 280: 281: else 282: invoke_server(server) 283: end 284: end 285: 286: # ... 287: /Users/robertmela/nitro/src/nitro/lib/nitro/server.rb:151:in `run' 146: Part.setup 147: 148: server = Server.new 149: server.start(options) 150: 151: runner.invoke(server) unless $NITRO_NO_INVOKE 152: 153: return server 154: end 155: 156: end /Users/robertmela/nitro/src/nitro/lib/nitro.rb:77:in `start' 72: attr_accessor :server 73: 74: # A helper method to start a Nitro application. 75: 76: def run(controller = nil) 77: @server = Server.run(controller) 78: end 79: alias_method :start, :run 80: 81: # A helper method. Will be deprecated, use 82: # Configuration.mode instead. app.rb:36 -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061126/4a0bf243/attachment-0001.vcf From rob at robmela.com Sun Nov 26 15:25:08 2006 From: rob at robmela.com (Robert Mela) Date: Sun, 26 Nov 2006 15:25:08 -0500 Subject: [Nitro] flare quickfix and question In-Reply-To: <4569EDA0.6000506@robmela.com> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> <4569EDA0.6000506@robmela.com> Message-ID: <4569F824.2090505@robmela.com> A sitepath method seems superfluous -- why not, in skin.rb, instead of calling sitepath, simply call context.host_url ? For now I've just made sitepath delegate to context.host_url def sitepath context.host_url end Robert Mela wrote: > Started flare and tried http://localhost:9000/admin > > Got "undefined local variable or method `sitepath' for > #" > > Added this to to nitro/lib/part/admin/helper.rb, which fixes the > problem, and puts something halfway appropriate in the title bar of > the browser: > > def sitepath > "#{@request.headers['REQUEST_URI']} on > #{@request.headers['SERVER_NAME']}" > end > > I can now manage the og database for flare. > > There is a class SitePath in skin.rb. SitePath's render produces a > clickable sitepath ( breadcrumb ) trail. So should this 'sitepath' > method in helper.rb should be called 'title_path' or something? > Better yet, maybe templates could get request headers directly from > the Request object, via methods like '@request.get_header_request_uri' > -- methods dynamically added as they are needed ( kind of like > ActiveRecord's find_by_.... ) > > FWIW, I'd be happy to file a ticket with a patch, but I keep getting > that nearly-blank "(error)" page when i try to reset my password. > *** > > Looked at the stack trace: > > * > /Users/robertmela/nitro/src/nitro/lib/nitro/publishable.rb:109:in > `method_missing' > 104: base.module_eval do > 105: def method_missing(action, *args) > 106: if Compiler.new(self.class).compile(action) > 107: send(action, *args) > 108: else > 109: super > 110: end > 111: end > 112: end > 113: > 114: # Does this publishable respond to the given action? > /Users/robertmela/nitro/src/nitro/lib/part/admin/template/index.xhtml:8:in > `index_template' > 1: @out << < 2: > 3: > 4: "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > 5: > 6: > 7: > 8: > 9: George Moschovitis > 10: > 11: > (eval):33:in `index_action' > /Users/robertmela/nitro/src/nitro/lib/nitro/publishable.rb:107:in > `method_missing' > 102: # for this controller. > 103: > 104: base.module_eval do > 105: def method_missing(action, *args) > 106: if Compiler.new(self.class).compile(action) > 107: send(action, *args) > 108: else > 109: super > 110: end > 111: end > 112: end > /Users/robertmela/nitro/src/nitro/lib/nitro/render.rb:129:in `render' > > 124: > 125: if self.class == @controller > 126: self.send(action) > 127: else > 128: puts "context='#{@context}' action='#{action}'\n" > 129: @controller.new(@context).send(action) > 130: end > 131: > 132: Controller.replace_current(old_controller) > 133: @context.level -= 1 > 134: > /Users/robertmela/nitro/src/nitro/lib/nitro/adapter/webrick.rb:171:in > `do_GET' > 166: context.headers['REQUEST_URI'] = '/' + > context.headers['REQUEST_URI'] > 167: > 168: Cgi.parse_params(context) > 169: Cgi.parse_cookies(context) > 170: > 171: context.render(path) > 172: > 173: res.status = context.status > 174: res.instance_variable_set(:@header, context.response_headers || {}) > 175: res.instance_variable_set(:@cookies, context.response_cookies || {}) > 176: res.body = context.out > /usr/local/lib/ruby/1.8/webrick/httpservlet/abstract.rb:35:in > `service' > 30: end > 31: > 32: def service(req, res) > 33: method_name = "do_" + req.request_method.gsub(/-/, "_") > 34: if respond_to?(method_name) > 35: __send__(method_name, req, res) > 36: else > 37: raise HTTPStatus::MethodNotAllowed, > 38: "unsupported method `#{req.request_method}'." > 39: end > 40: end > /usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' > > 99: raise HTTPStatus::NotFound, "`#{req.path}' not found." unless servlet > 100: req.script_name = script_name > 101: req.path_info = path_info > 102: si = servlet.get_instance(self, *options) > 103: @logger.debug(format("%s is invoked.", si.class.name)) > 104: si.service(req, res) > 105: end > 106: > 107: def do_OPTIONS(req, res) > 108: res["allow"] = "GET,HEAD,POST,OPTIONS" > 109: end > /usr/local/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' > > 60: res.keep_alive = req.keep_alive? > 61: server = lookup_server(req) || self > 62: if callback = server[:RequestCallback] || server[:RequestHandler] > 63: callback.call(req, res) > 64: end > 65: server.service(req, res) > 66: rescue HTTPStatus::EOFError, HTTPStatus::RequestTimeout => ex > 67: res.set_error(ex) > 68: rescue HTTPStatus::Error => ex > 69: @logger.error(ex.message) > 70: res.set_error(ex) > /usr/local/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' > > 168: rescue SocketError > 169: @logger.debug "accept:
" > 170: raise > 171: end > 172: call_callback(:AcceptCallback, sock) > 173: block ? block.call(sock) : run(sock) > 174: rescue Errno::ENOTCONN > 175: @logger.debug "Errno::ENOTCONN raised" > 176: rescue ServerError => ex > 177: msg = "#{ex.class}: #{ex.message}\n\t#{ex.backtrace[0]}" > 178: @logger.error msg > /usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' > > 157: end > 158: return sock > 159: end > 160: > 161: def start_thread(sock, &block) > 162: Thread.start{ > 163: begin > 164: Thread.current[:WEBrickSocket] = sock > 165: begin > 166: addr = sock.peeraddr > 167: @logger.debug "accept: #{addr[3]}:#{addr[1]}" > /usr/local/lib/ruby/1.8/webrick/server.rb:95:in `start' > > 90: begin > 91: if svrs = IO.select(@listeners, nil, nil, 2.0) > 92: svrs[0].each{|svr| > 93: @tokens.pop # blocks while no token is there. > 94: if sock = accept_client(svr) > 95: th = start_thread(sock, &block) > 96: th[:WEBrickThread] = true > 97: thgroup.add(th) > 98: else > 99: @tokens.push(nil) > 100: end > /usr/local/lib/ruby/1.8/webrick/server.rb:92:in `start' > > 87: thgroup = ThreadGroup.new > 88: @status = :Running > 89: while @status == :Running > 90: begin > 91: if svrs = IO.select(@listeners, nil, nil, 2.0) > 92: svrs[0].each{|svr| > 93: @tokens.pop # blocks while no token is there. > 94: if sock = accept_client(svr) > 95: th = start_thread(sock, &block) > 96: th[:WEBrickThread] = true > 97: thgroup.add(th) > /usr/local/lib/ruby/1.8/webrick/server.rb:23:in `start' > > 18: > 19: class ServerError < StandardError; end > 20: > 21: class SimpleServer > 22: def SimpleServer.start > 23: yield > 24: end > 25: end > 26: > 27: class Daemon > 28: def Daemon.start > /usr/local/lib/ruby/1.8/webrick/server.rb:82:in `start' > > 77: > 78: def start(&block) > 79: raise ServerError, "already started." if @status != :Stop > 80: server_type = @config[:ServerType] || SimpleServer > 81: > 82: server_type.start{ > 83: @logger.info \ > 84: "#{self.class}#start: pid=#{$$} port=#{@config[:Port]}" > 85: call_callback(:StartCallback) > 86: > 87: thgroup = ThreadGroup.new > /Users/robertmela/nitro/src/nitro/lib/nitro/adapter/webrick.rb:66:in > `start' > 61: > 62: @webrick.mount('/', WebrickAdapter, server) > 63: > 64: initialize_webrick(server) > 65: > 66: @webrick.start > 67: end > 68: > 69: # Stop the Webrick adapter. > 70: > 71: def stop > /Users/robertmela/nitro/src/nitro/lib/nitro/server/runner.rb:323:in > `invoke_server' > 318: when :webrick > 319: require 'nitro/adapter/webrick' > 320: Logger.info "Starting Webrick on #{server.address}:#{server.port}" > 321: Logger.info "Press Ctrl-C to shutdown; Run with --help for options." > 322: Logger.info "" > 323: Webrick.start(server) > 324: > 325: when :mongrel > 326: require 'nitro/adapter/mongrel' > 327: Logger.info "Starting Mongrel on #{server.address}:#{server.port}" > 328: Logger.info "Press Ctrl-C to shutdown; Run with --help for options." > /Users/robertmela/nitro/src/nitro/lib/nitro/server/runner.rb:282:in > `invoke' > 277: $server = server > 278: $app = ConsoleAdapter.new(server) > 279: $cache = Caching::Proxy > 280: > 281: else > 282: invoke_server(server) > 283: end > 284: end > 285: > 286: # ... > 287: > /Users/robertmela/nitro/src/nitro/lib/nitro/server.rb:151:in `run' > > 146: Part.setup > 147: > 148: server = Server.new > 149: server.start(options) > 150: > 151: runner.invoke(server) unless $NITRO_NO_INVOKE > 152: > 153: return server > 154: end > 155: > 156: end > /Users/robertmela/nitro/src/nitro/lib/nitro.rb:77:in `start' > > 72: attr_accessor :server > 73: > 74: # A helper method to start a Nitro application. > 75: > 76: def run(controller = nil) > 77: @server = Server.run(controller) > 78: end > 79: alias_method :start, :run > 80: > 81: # A helper method. Will be deprecated, use > 82: # Configuration.mode instead. > app.rb:36 > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061126/92a5a7da/attachment.vcf From rob at robmela.com Sun Nov 26 21:48:54 2006 From: rob at robmela.com (Robert Mela) Date: Sun, 26 Nov 2006 21:48:54 -0500 Subject: [Nitro] Tag cloud and calendar widgets? In-Reply-To: <4569F824.2090505@robmela.com> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> <4569EDA0.6000506@robmela.com> <4569F824.2090505@robmela.com> Message-ID: <456A5216.7080707@robmela.com> What are Nitroites using for tag cloud and calendar widgets? Are there parts libraries, or is everyone rolling their own? I've posted the question on oxyliquit.de but am casting a wider net. I'll post any responses back on oxyliquit. Thanks in advance. -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061126/2f05a5d4/attachment.vcf From george.moschovitis at gmail.com Mon Nov 27 04:44:19 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 27 Nov 2006 11:44:19 +0200 Subject: [Nitro] Tag cloud and calendar widgets? In-Reply-To: <456A5216.7080707@robmela.com> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> <4569EDA0.6000506@robmela.com> <4569F824.2090505@robmela.com> <456A5216.7080707@robmela.com> Message-ID: On 11/27/06, Robert Mela wrote: > What are Nitroites using for tag cloud and calendar widgets? Are there > parts libraries, or is everyone rolling their own? You can use the Taggable module for tag clouds (og/lib/glue/taggable.rb) Have a look at the spark source code for example usage. for calendar widgets oyu can use Jquery/Dojo widgets. -g. > > I've posted the question on oxyliquit.de but am casting a wider net. > I'll post any responses back on oxyliquit. > > Thanks in advance. > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Mon Nov 27 05:18:34 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 27 Nov 2006 12:18:34 +0200 Subject: [Nitro] Bug and feature Request In-Reply-To: <20061126133109.GA3162@none.at> References: <20061126092920.GB21301@none.at> <9c00d3e00611260429t1e6869a6t26bf936e95fde23@mail.gmail.com> <20061126133109.GA3162@none.at> Message-ID: > @George: how about to add this to 0.41.x ;-) I don't want to 'polute' the source code with so many checks. What do others think? -g. -- http://blog.gmosx.com http://nitroproject.org From fabian at fabian-buch.de Mon Nov 27 08:15:14 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Mon, 27 Nov 2006 14:15:14 +0100 Subject: [Nitro] Bug and feature Request In-Reply-To: References: <20061126092920.GB21301@none.at> <9c00d3e00611260429t1e6869a6t26bf936e95fde23@mail.gmail.com> <20061126133109.GA3162@none.at> Message-ID: <7490C1C2-A0F7-4994-9DCB-88B616958D5C@fabian-buch.de> Am 27.11.2006 um 11:18 schrieb George Moschovitis: >> @George: how about to add this to 0.41.x ;-) > > I don't want to 'polute' the source code with so many checks. What do > others think? I wouldn't do that either. People using RubyGems should know how to use RubyGems. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From rob at robmela.com Tue Nov 28 21:35:48 2006 From: rob at robmela.com (Robert Mela) Date: Tue, 28 Nov 2006 21:35:48 -0500 Subject: [Nitro] "magic" mapping of controllers possible? In-Reply-To: <200606231032.36346.manveru@weez-int.com> References: <44998E2F.2080007@lassoweb.se> <200606221151.11285.manveru@weez-int.com> <55c107bf0606221347i60811d95q4f4e8927c5f50357@mail.gmail.com> <200606231032.36346.manveru@weez-int.com> Message-ID: <456CF204.1030700@robmela.com> I've been getting folks impressed with Nitro by the videos under http://nitroproject.org/wiki/pages/Documentation__Programming_Nitro and http://nitroproject.com/videos/nitro.html Unfortunately they seem to be broken now -- the infamous "(error)" page. It's a great tool -- will it be back up any time soon? Could I mirror them until they are available? -------------- next part -------------- A non-text attachment was scrubbed... Name: rob.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20061128/068298fd/attachment.vcf From john at oxyliquit.de Tue Nov 28 17:40:46 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 28 Nov 2006 23:40:46 +0100 Subject: [Nitro] CDATA disappears In-Reply-To: References: <4568407A.4090308@lassoweb.se> Message-ID: Hi! > Wow ! Only 5 hours between "report" and fix o_o > You're amazing. > Thank very much. Indeed! Thx lasso for doing support. ^_^ Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Tue Nov 28 17:40:41 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 28 Nov 2006 23:40:41 +0100 Subject: [Nitro] Tag cloud and calendar widgets? In-Reply-To: <456A5216.7080707@robmela.com> References: <106a0270611221028m75a0df41x3208ee3d0110113e@mail.gmail.com> <20061122210611.GA15389@oxyliquit.de> <106a0270611230748l67de956ej5d6393fcb999eb9@mail.gmail.com> <4569EDA0.6000506@robmela.com> <4569F824.2090505@robmela.com> <456A5216.7080707@robmela.com> Message-ID: Hi, > What are Nitroites using for tag cloud and calendar widgets? Are there > parts libraries, or is everyone rolling their own? > > I've posted the question on oxyliquit.de but am casting a wider net. > I'll post any responses back on oxyliquit. sorry for Oxyliquit being down, the service is moving to a (hopefully) more stable server. Thank you for posting here as well as over there. To answer your first question: there ain't really any nitro libs yet, so everyone is rolling their own stuff. But, basically a tag cloud is really easy to build. Below working code from oxyliquit:

Tags

Not really pretty, but very neat. It just uses the 'sum' as the highest value and uses percentages of this to produce the cloud like look. The tag.popularity here is a value which you have to calculate. Just think of something clever. Oxyliquit for example uses clicks (page visits) to weigh the Tags. Again, working code from Oxywtf: def all_tags # This SQL query is used as a select statement for Tags # It first gets all sum'ed up clicks from questions/tips/tuts and adds # them together. This produces the popularity of a single Tag. sel = <<-SQL (SELECT SUM(clicks) FROM ( SELECT SUM(q.clicks) AS clicks FROM ogquestion q, ogj_question_tag tq WHERE q.oid = tq.question_oid AND tq.tag_oid = ogtag.oid UNION SELECT SUM(q.clicks) AS clicks FROM ogtutorial q, ogj_tag_tutorial tq WHERE q.oid = tq.tutorial_oid AND tq.tag_oid = ogtag.oid UNION SELECT SUM(q.clicks) AS clicks FROM ogtip q, ogj_tag_tip tq WHERE q.oid = tq.tip_oid AND tq.tag_oid = ogtag.oid ) AS foo ) AS popularity, * SQL @all_tags ||= Tag.find(:select => sel, :order => 'popularity DESC') end def right @wtags = all_tags.sort_by { |x| x.popularity.to_i }.reverse[0..30].sort_by {|x| x.name } end Not the most pretty code either, but very much does what I wanted. Note, this is just an example, the popularity of a single tag can be calculated of anything you like. The easiest is to just use the 'count' field of the tag. As I said, it's quite easy to roll yourself, so making a real lib out of that... I dunno. :) Feel free to use all code in here, have a nice evening. Jo PS: really really sorry for Oxy outages. Got word from the server support. Apparently a defect made the server reboot with the main disc mounted as readonly. I just wonder how that can happen twice in a row. ;/ PPS: working on a backup server, should be online soon. -- Feel the love http://pinkjuice.com/pics/ruby.png From william.full.moon at gmail.com Wed Nov 29 02:32:31 2006 From: william.full.moon at gmail.com (* William) Date: Wed, 29 Nov 2006 18:32:31 +1100 Subject: [Nitro] "magic" mapping of controllers possible? In-Reply-To: <456CF204.1030700@robmela.com> Message-ID: <00e801c71388$8b702110$0201a8c0@ghostgum> George is the man to pat on the back for the video I'm pleased to see the pages are useful and that Lionel has been doing such a grand effort to improve things. Much of the structural information will be change in new releases. Think of these notes as a starting point, and please UPDATE any things you come across in your travels. The wiki video link is broken. So are several other links. It might be a more fundamental thing. I notice that the updates are saying "two hours ago" for like the 6th of July. (hmmmm...) Aloha, Will -----Original Message----- From: nitro-general-bounces at rubyforge.org [mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Robert Mela Sent: Wednesday, 29 November 2006 13:36 To: General discussion about Nitro Subject: Re: [Nitro] "magic" mapping of controllers possible? Importance: Low I've been getting folks impressed with Nitro by the videos under http://nitroproject.org/wiki/pages/Documentation__Programming_Nitro and http://nitroproject.com/videos/nitro.html Unfortunately they seem to be broken now -- the infamous "(error)" page. It's a great tool -- will it be back up any time soon? Could I mirror them until they are available? -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.14.19/556 - Release Date: 28-Nov-2006 15:22 From al-nitrogen at none.at Wed Nov 29 05:29:49 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Wed, 29 Nov 2006 11:29:49 +0100 Subject: [Nitro] Caching question on oxyliquit.de Message-ID: <20061129102949.GB3465@none.at> Hi, I have looked on oxyliquit to deliver some renderd/cached files with nignx and found this without a answer. http://oxyliquit.de/question/17 Have anybody some hints to use the caching functions ;-) Regards Aleks From oliver.oli at gmail.com Wed Nov 29 05:54:26 2006 From: oliver.oli at gmail.com (oliver oli) Date: Wed, 29 Nov 2006 11:54:26 +0100 Subject: [Nitro] where is the documentation? Message-ID: the nitroproject.org website seems to quite broken for some time now? are there any efforts to fix it? a project without documentation is quite useless. should i expect the code as broken as the website? ;-) From john at oxyliquit.de Wed Nov 29 06:52:11 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 29 Nov 2006 12:52:11 +0100 Subject: [Nitro] Caching question on oxyliquit.de In-Reply-To: <20061129102949.GB3465@none.at> References: <20061129102949.GB3465@none.at> Message-ID: Hi, > I have looked on oxyliquit to deliver some renderd/cached files with > nignx and found this without a answer. > > http://oxyliquit.de/question/17 > > Have anybody some hints to use the caching functions ;-) Yes, George, please write something about that! Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Wed Nov 29 07:16:16 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 29 Nov 2006 14:16:16 +0200 Subject: [Nitro] "magic" mapping of controllers possible? In-Reply-To: <00e801c71388$8b702110$0201a8c0@ghostgum> References: <456CF204.1030700@robmela.com> <00e801c71388$8b702110$0201a8c0@ghostgum> Message-ID: Please use the links from the homepage. I will fix the rest of the links shortly. Moreover, Jonathan will host the videos on oxyliquid.de -g. On 11/29/06, * William wrote: > George is the man to pat on the back for the video > > I'm pleased to see the pages are useful and that Lionel has been doing such > a grand effort to improve things. Much of the structural information will > be change in new releases. Think of these notes as a starting point, and > please UPDATE any things you come across in your travels. > > The wiki video link is broken. So are several other links. It might be a > more fundamental thing. I notice that the updates are saying "two hours > ago" for like the 6th of July. (hmmmm...) > > Aloha, > Will > > -----Original Message----- > From: nitro-general-bounces at rubyforge.org > [mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Robert Mela > Sent: Wednesday, 29 November 2006 13:36 > To: General discussion about Nitro > Subject: Re: [Nitro] "magic" mapping of controllers possible? > Importance: Low > > I've been getting folks impressed with Nitro by the videos under > http://nitroproject.org/wiki/pages/Documentation__Programming_Nitro and > http://nitroproject.com/videos/nitro.html > > Unfortunately they seem to be broken now -- the infamous "(error)" page. > > It's a great tool -- will it be back up any time soon? Could I mirror them > until they are available? > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.430 / Virus Database: 268.14.19/556 - Release Date: 28-Nov-2006 > 15:22 > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://nitroproject.org From george.moschovitis at gmail.com Wed Nov 29 07:17:05 2006 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 29 Nov 2006 14:17:05 +0200 Subject: [Nitro] Caching question on oxyliquit.de In-Reply-To: References: <20061129102949.GB3465@none.at> Message-ID: > Yes, George, please write something about that! Ok, give me a day or two ;-) -g. -- http://blog.gmosx.com http://nitroproject.org From john at oxyliquit.de Wed Nov 29 07:29:58 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 29 Nov 2006 13:29:58 +0100 Subject: [Nitro] where is the documentation? In-Reply-To: References: Message-ID: Hi, > the nitroproject.org website seems to quite broken for some time now? Well, yes, had sadly always been a bit broken... > are there any efforts to fix it? George is just a human after all and I think he's quite busy with 'cleaning' up some stuff with some other applications he has to support. > a project without documentation is quite useless. I would argue against this, but this wouldn't convince you, would it. ;) > should i expect the code as broken as the website? ;-) Depends on whom you ask. :P But realistically, the code is less broken than the page. :) Mind you, that http://www.oxyliquit.de/ is another source and (although quite unstable atm due to a presumed hardware failure) also running quite non-broken on nitro. :P Look here at the screencast from George for a small introduction. http://www.oxyliquit.de/tip/35 Other than that, the people on the mailing list are quite happy to share information and help where they can, don't hesitate to ask. Enjoy your stay, Jonathan -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Wed Nov 29 07:31:08 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Wed, 29 Nov 2006 13:31:08 +0100 Subject: [Nitro] "magic" mapping of controllers possible? In-Reply-To: References: <456CF204.1030700@robmela.com> <00e801c71388$8b702110$0201a8c0@ghostgum> Message-ID: Hi, > Please use the links from the homepage. I will fix the rest of the > links shortly. Moreover, Jonathan will host the videos on oxyliquid.de aye, done, lookey here: http://www.oxyliquit.de/tip/35 Will try to keep that tip up to date. When you make a new screencast, please tell me! Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From al-nitrogen at none.at Wed Nov 29 08:02:37 2006 From: al-nitrogen at none.at (Aleksandar Lazic) Date: Wed, 29 Nov 2006 14:02:37 +0100 Subject: [Nitro] Caching question on oxyliquit.de In-Reply-To: References: <20061129102949.GB3465@none.at> Message-ID: <20061129130237.GB14844@none.at> On Mit 29.11.2006 14:17, George Moschovitis wrote: >> Yes, George, please write something about that! > >Ok, give me a day or two ;-) Take a week if you need ;-) Thanks for writeing Aleks From william.full.moon at gmail.com Thu Nov 30 06:15:32 2006 From: william.full.moon at gmail.com (* William) Date: Thu, 30 Nov 2006 22:15:32 +1100 Subject: [Nitro] where is the documentation? In-Reply-To: Message-ID: <017c01c71470$dd915390$0201a8c0@ghostgum> Hello hello ... I have updated at least the first page of the write-up to now point to Oxyliquit - "Geroge's Demo". Thanks to Jonathan for showing us the way. BUT -- the "step one" page disappeared !! The nitro project site is a wiki, the idea is for people to go in there and fix broken things. It is good to point out broken bits, so some will fix it. Of course it is much better when we are all part of the solution too! (where did the missing page go?) I'd like to ask too. Id the file known as "Georges' Demo" the same as the three videos that showed how from the project page? Any ideas how to get the page back? ... Will -----Original Message----- From: nitro-general-bounces at rubyforge.org [mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Jonathan Buch Sent: Wednesday, 29 November 2006 23:30 To: General discussion about Nitro Subject: Re: [Nitro] where is the documentation? Importance: Low Hi, > the nitroproject.org website seems to quite broken for some time now? Well, yes, had sadly always been a bit broken... > are there any efforts to fix it? George is just a human after all and I think he's quite busy with 'cleaning' up some stuff with some other applications he has to support. > a project without documentation is quite useless. I would argue against this, but this wouldn't convince you, would it. ;) > should i expect the code as broken as the website? ;-) Depends on whom you ask. :P But realistically, the code is less broken than the page. :) Mind you, that http://www.oxyliquit.de/ is another source and (although quite unstable atm due to a presumed hardware failure) also running quite non-broken on nitro. :P Look here at the screencast from George for a small introduction. http://www.oxyliquit.de/tip/35 Other than that, the people on the mailing list are quite happy to share information and help where they can, don't hesitate to ask. Enjoy your stay, Jonathan -- Feel the love http://pinkjuice.com/pics/ruby.png _______________________________________________ Nitro-general mailing list Nitro-general at rubyforge.org http://rubyforge.org/mailman/listinfo/nitro-general -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.14.19/556 - Release Date: 28-Nov-2006 15:22 From john at oxyliquit.de Thu Nov 30 06:49:28 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 30 Nov 2006 12:49:28 +0100 Subject: [Nitro] where is the documentation? In-Reply-To: <017c01c71470$dd915390$0201a8c0@ghostgum> References: <017c01c71470$dd915390$0201a8c0@ghostgum> Message-ID: <20061130114928.GA14218@oxyliquit.de> Hi, > ... I have updated at least the first page of the write-up to now point to > Oxyliquit - "Geroge's Demo". > > Thanks to Jonathan for showing us the way. You're welcome! > BUT -- the "step one" page disappeared !! > > The nitro project site is a wiki, the idea is for people to go in there and > fix broken things. It is good to point out broken bits, so some will fix > it. Of course it is much better when we are all part of the solution too! > (where did the missing page go?) > > I'd like to ask too. Id the file known as "Georges' Demo" the same as the > three videos that showed how from the project page? > > Any ideas how to get the page back? No, this is a reason why Oxyliquit isn't a wiki, too many people doing stuff to what you wrote can be quite... harmful. ;) As a matter of fact, I can't find the videos! You say that there are three videos? Plase give me the link to them and I will have a look which is which and what I have to integrate into my tip post. G gave me the link for the first video which is http://static.nitroproject.org/videos/nitro.html . Thanks for taking care of the wiki! Jonathan From william.full.moon at gmail.com Thu Nov 30 06:57:55 2006 From: william.full.moon at gmail.com (* William) Date: Thu, 30 Nov 2006 22:57:55 +1100 Subject: [Nitro] FW: Stroustrup speaks -- words to consider Message-ID: <018801c71476$c960f6e0$0201a8c0@ghostgum> Hi ho ... I thought I'd point people to this blog and the original Technology Review article: 'The Problem with Programming' HYPERLINK "http://www.technologyreview.com/InfoTech/17831/page1/"http://www.technology review.com/InfoTech/17831/page1/ " Other other hand, looking at "average" pieces of code can make me cry. The structure is appalling, and the programmers clearly didn't think deeply about correctness, algorithms, data structures, or maintainability. Most people don't actually read code; they just see Internet Explorer or Windows "freeze," have their cell phone drop a call, read the latest newspaper story about viruses, and they shudder." -- BS The blog discussion is very interesting. To me anyway. HYPERLINK "http://www.artima.com/forums/flat.jsp?forum=269&thread=186478"http://www.ar tima.com/forums/flat.jsp?forum=269&thread=186478 I was reading one of those things about six sigma ... in lay terms six sigma looks for 99.99% correctness. Enjoy, Will. MBA, B.Math, STI, NLP MP _My_Bright_Ideas____________________________________________________abn:7742 5560110_ "You must BE the change you want." ~ HYPERLINK "http://www.brainyquote.com/quotes/authors/m/mohandas_gandhi.html"Gandhi Success Coaching HYPERLINK "http://adroit-process.blogspot.com/"http://adroit-process.blogspot.com/ ph/sms: 041-476-1217 (?2006) Information proprietary and confidential intended for direct recipient(s) and mutually agreed correspondents. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.14.19/556 - Release Date: 28-Nov-2006 15:22 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.14.19/556 - Release Date: 28-Nov-2006 15:22 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061130/389cf083/attachment-0001.html From aglarond at gmail.com Thu Nov 30 07:56:49 2006 From: aglarond at gmail.com (Dimitri Aivaliotis) Date: Thu, 30 Nov 2006 13:56:49 +0100 Subject: [Nitro] FW: Stroustrup speaks -- words to consider In-Reply-To: <018801c71476$c960f6e0$0201a8c0@ghostgum> References: <018801c71476$c960f6e0$0201a8c0@ghostgum> Message-ID: <55c107bf0611300456w5f802979r4e1eeeff48df1ae7@mail.gmail.com> On 11/30/06, * William wrote: > > > I was reading one of those things about six sigma ... in lay terms six > sigma looks for 99.99% correctness. > six sigma[1], you say? Sorry, couldn't resist. :) - Dimitri [1] http://www.dilbert.com/comics/dilbert/archive/dilbert-20061126.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/nitro-general/attachments/20061130/efe9b293/attachment.html From john at oxyliquit.de Thu Nov 30 09:19:09 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 30 Nov 2006 15:19:09 +0100 Subject: [Nitro] FW: Stroustrup speaks -- words to consider In-Reply-To: <55c107bf0611300456w5f802979r4e1eeeff48df1ae7@mail.gmail.com> References: <018801c71476$c960f6e0$0201a8c0@ghostgum> <55c107bf0611300456w5f802979r4e1eeeff48df1ae7@mail.gmail.com> Message-ID: Hi, > Sorry, couldn't resist. :) > [1] http://www.dilbert.com/comics/dilbert/archive/dilbert-20061126.html Haha, yes, I thought of that too. Although I have no idea what six sigma actually is.... must've been before my time. :P Other than that, the interview with Stroustrup is quite interesting. The most interesting thing as I find is "We perform many minor miracles through trial and error, excessive use of brute force, and lots and lots of testing, but--so often--it's not enough." He's quite right there I think, and I'm one of those people. ;) I quite had this with the param stuff. I just don't have the energy to write a formal description for every single case how nitro can get called from outside. Replace 'energy' by time here and you'll get to what Stroustrup said. Happy hacking, Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From fabian at fabian-buch.de Thu Nov 30 10:22:43 2006 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 30 Nov 2006 16:22:43 +0100 Subject: [Nitro] FW: Stroustrup speaks -- words to consider In-Reply-To: <018801c71476$c960f6e0$0201a8c0@ghostgum> References: <018801c71476$c960f6e0$0201a8c0@ghostgum> Message-ID: <044371D9-544F-4C3C-98F4-07D6F8D2ADCF@fabian-buch.de> maybe an interesting read: http://books.slashdot.org/article.pl?sid=06/11/29/1449208 I didn't read the book yet, but will probably soon. Fabian -- Nitro Q&A: http://oxyliquit.de/ Blog: http://blog.fabian-buch.de From john at oxyliquit.de Thu Nov 30 10:36:04 2006 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 30 Nov 2006 16:36:04 +0100 Subject: [Nitro] where is the documentation? In-Reply-To: <20061130114928.GA14218@oxyliquit.de> References: <017c01c71470$dd915390$0201a8c0@ghostgum> <20061130114928.GA14218@oxyliquit.de> Message-ID: <20061130153604.GB15604@oxyliquit.de> Hi, > As a matter of fact, I can't find the videos! Thanks to Reid Thompson I now have the three videos. For the record, the three screencasts from George will probably only work with Nitro 0.31 so I tagged the tip accordingly. URL again: http://oxyliquit.de/tip/35 If you know of more screencasts or just did one yourself yesterday, please tell me! :P Jo