From john at oxyliquit.de Thu Mar 1 00:06:45 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Thu, 01 Mar 2007 06:06:45 +0100 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: Message-ID: Hi, > attached to this email you will find the banner for the new nitro web > site I am working on. This is of course under construction. I would > like to hear ideas for a new Nitro moto/tagline to replace what you > can see in this image. > > I would *really* love to hear your suggestions... I find it a little... cheesy? So to say, the starship is 'cuddly' and the blue-star background go well along together. Looks a little like 'toy story', not sure what 'message' it conveys... But then, it's just me probably. :P Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Thu Mar 1 03:19:55 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 1 Mar 2007 10:19:55 +0200 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <45E6517A.5020705@gmail.com> References: <45E6517A.5020705@gmail.com> Message-ID: I know the image is nice (I painted it myself with inkscape the rocket and the box). I would like to hear suggestions about the text (the motto, the tagline). Any ideas? -g. On 3/1/07, James Britt wrote: > gabriele renzi wrote: > > George Moschovitis ha scritto: > >> oh, you can also have a peek at the new logo (look in the box ;-)) > >> > >> -g. > >> > >> On 2/28/07, George Moschovitis wrote: > >>> Dear devs, > >>> > >>> attached to this email you will find the banner for the new nitro web > >>> site I am working on. This is of course under construction. I would > >>> like to hear ideas for a new Nitro moto/tagline to replace what you > >>> can see in this image. > >>> > >>> I would *really* love to hear your suggestions... > > > > isn't it "state of the art" ? I thnk one "of" is missing. Other than > > that, the image is wonderful :) > > Yeah, quite the slickness. > > Very nice! > > I want to add Nitro %w{ shirt hat coffer_cup } stuff to rubystuff.com! > > -- > James Britt > > "Tear it up and start again." > - Anonymous > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From fabian at fabian-buch.de Thu Mar 1 05:14:14 2007 From: fabian at fabian-buch.de (Fabian Buch) Date: Thu, 1 Mar 2007 11:14:14 +0100 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: Message-ID: <23160E49-A0B4-46CD-ADC2-EBA2C7EDF050@fabian-buch.de> Where's Nitro? Like this it looks like the software you can download is called "Not Rocket Science". Fabian -- Nitro Q&A: http://oxyliquit.de LoxParts: http://loxparts.de Blog: http://blog.fabian-buch.de From george.moschovitis at gmail.com Thu Mar 1 05:26:05 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 1 Mar 2007 12:26:05 +0200 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <23160E49-A0B4-46CD-ADC2-EBA2C7EDF050@fabian-buch.de> References: <23160E49-A0B4-46CD-ADC2-EBA2C7EDF050@fabian-buch.de> Message-ID: Not Rocket Science (and all the text) is a placeholder. This image is embeded in the nitro homepage, there says nitro all over the place, so your point is not valid ;-) -g. On 3/1/07, Fabian Buch wrote: > Where's Nitro? Like this it looks like the software you can download > is called "Not Rocket Science". > > Fabian > > > -- > Nitro Q&A: http://oxyliquit.de > LoxParts: http://loxparts.de > Blog: http://blog.fabian-buch.de > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From william.full.moon at gmail.com Thu Mar 1 06:13:11 2007 From: william.full.moon at gmail.com (* William) Date: Thu, 1 Mar 2007 22:13:11 +1100 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <23160E49-A0B4-46CD-ADC2-EBA2C7EDF050@fabian-buch.de> References: <23160E49-A0B4-46CD-ADC2-EBA2C7EDF050@fabian-buch.de> Message-ID: <000c01c75bf2$a62fc430$0301a8c0@ghostgum> I thought it was really good! Although it looks like the local soccer team logo -- They did make the semi-final that's a good omen :-) -----Original Message----- From: nitro-general-bounces at rubyforge.org [mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Fabian Buch Sent: Thursday, 1 March 2007 21:14 To: General discussion about Nitro Subject: Re: [Nitro] Nitro homepage banner... Importance: Low Where's Nitro? Like this it looks like the software you can download is called "Not Rocket Science". Fabian -- Nitro Q&A: http://oxyliquit.de LoxParts: http://loxparts.de Blog: http://blog.fabian-buch.de _______________________________________________ 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.446 / Virus Database: 268.18.4/705 - Release Date: 27-Feb-2007 15:24 From james.britt at gmail.com Thu Mar 1 14:06:23 2007 From: james.britt at gmail.com (James Britt) Date: Thu, 01 Mar 2007 12:06:23 -0700 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: <45E6517A.5020705@gmail.com> Message-ID: <45E7242F.4030307@gmail.com> George Moschovitis wrote: > I know the image is nice (I painted it myself with inkscape the rocket > and the box). > > I would like to hear suggestions about the text (the motto, the > tagline). Any ideas? > Who are the target audience, and what is the message you want to convey? Having a distinct icon or logo can help brand the application/framework/whatever. Using a rocket is good; it conveys speed, movement, sleekness "Not rocket science" is interesting; if the idea is to compare Nitro to a rocket, then in a way it *is* rocket science, but it's rocket science made easy. But that's an awkward idea. Or, maybe, the message is that Nitro gives you rocket power and performance, but without the need for geeky, heavy-handed rocket science. Or I'm over-analyzing it. I liked it on first take. There is a certain cutesy element to the image; not sure if that is good or bad. I like the idea that Nitro is not super-serious, Enterprise 2.0, look-we-have-slick-corporate-logo. On the other hand, if it looks to much like a toy rocket, then it may seem to lightweight. But, overall, I like it. It feels fun, happy. And that's good. From noe.rubinstein at gmail.com Thu Mar 1 15:45:08 2007 From: noe.rubinstein at gmail.com (=?UTF-8?Q?No=C3=A9_Rubinstein?=) Date: Thu, 1 Mar 2007 21:45:08 +0100 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <45E7242F.4030307@gmail.com> References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> Message-ID: I dont'l like the "Web 2.0" buzzword. The first question one may ask, discovering Nitro, is "Why Nitro instead of Rails ?". Thus, the motto may be better answering this question. The motto should therefore convey the following ideas : - Ruby - simple - flexible - OMG, this ORM is bloody good ! - explosive (like nitroglycerin) power The drawing is wonderful :) From brian.william.davis at gmail.com Fri Mar 2 00:04:22 2007 From: brian.william.davis at gmail.com (Brian Davis) Date: Thu, 1 Mar 2007 21:04:22 -0800 Subject: [Nitro] Unintuitive Og modeling Message-ID: <20070301210422.4d33ad25@localhost.localdomain> NOTE: I posted this at the Google Groups interface, but my message has languished in the ether. I spoke with Kashia earlier about this and he encouraged me to post this to the mailing list. Consider the following model definition: -------------------- class User ... many_to_many :buddies, User, :foreign_name => :buddies many_to_many :buddies_pending_confirmation, User, :foreign_name => :buddies_requested many_to_many :buddies_requested, User, :foreign_name => :buddies_pending_confirmation ... end -------------------- This is a reflexive join with several distinct relationships that happen to join to objects of the same class. My issue is that, with Og, only one join table is created to model *all* of these relationship: og_user_user. Because of this, the relationships are essentially mirrored. Thus, if a user is added to my 'buddies_pending_confirmation' queue, they also appear in my 'buddies' and 'buddies_requested' lists, although this is precisely the opposite of the intended behavior. Kashia showed me a hack that circumvents this behavior (by defining a self-join class for each of the relationships above), but we both found it to be, well, a hack. It lacked the clarity and intuitiveness of the code above. My suggestion, then, is to perhaps name join tables not by their associated types, but by their given label (the first argument to 'many_to_many'). Thus, my 'og_user_user' table right now would actually be three tables, 'og_user_buddies', 'og_user_buddies_pending_confirmation' and 'og_user_buddies_requested'. Please let me know if this is unreasonable, stupid or unclear. Also, if there's something I'm just altogether missing, set me straight. Thanks, Brian From george.moschovitis at gmail.com Fri Mar 2 03:39:40 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 2 Mar 2007 10:39:40 +0200 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <45E7242F.4030307@gmail.com> References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> Message-ID: I am considering changing this to: Rocket Science Nitro provides everything you need to create state of the art applications for the emerging Web OS. the message is: - Nitro is the state of the art - Nitro creates applications for the Read/Write Web - Nitro is a complete solution So, can you help me rephrase the above ..phrase to be better english? -g. On 3/1/07, James Britt wrote: > George Moschovitis wrote: > > I know the image is nice (I painted it myself with inkscape the rocket > > and the box). > > > > I would like to hear suggestions about the text (the motto, the > > tagline). Any ideas? > > > > Who are the target audience, and what is the message you want to convey? > > Having a distinct icon or logo can help brand the > application/framework/whatever. > > Using a rocket is good; it conveys speed, movement, sleekness > > "Not rocket science" is interesting; if the idea is to compare Nitro to > a rocket, then in a way it *is* rocket science, but it's rocket science > made easy. But that's an awkward idea. Or, maybe, the message is that > Nitro gives you rocket power and performance, but without the need for > geeky, heavy-handed rocket science. > > Or I'm over-analyzing it. I liked it on first take. > > There is a certain cutesy element to the image; not sure if that is > good or bad. I like the idea that Nitro is not super-serious, > Enterprise 2.0, look-we-have-slick-corporate-logo. On the other hand, > if it looks to much like a toy rocket, then it may seem to lightweight. > > But, overall, I like it. It feels fun, happy. And that's good. > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Fri Mar 2 03:57:58 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 2 Mar 2007 10:57:58 +0200 Subject: [Nitro] Unintuitive Og modeling In-Reply-To: <20070301210422.4d33ad25@localhost.localdomain> References: <20070301210422.4d33ad25@localhost.localdomain> Message-ID: I think your suggested solution is reasonable. A problem is that it is backwards incompatible but I prefer something that works. I am wondering if Jonathan or Judson could provide a patch for this (as I am working on Nitro stuff at the moment). thanks, George. On 3/2/07, Brian Davis wrote: > NOTE: I posted this at the Google Groups interface, but my message has > languished in the ether. > > I spoke with Kashia earlier about this and he encouraged me to post > this to the mailing list. > > Consider the following model definition: > -------------------- > class User > ... > many_to_many :buddies, User, :foreign_name => :buddies > many_to_many :buddies_pending_confirmation, User, :foreign_name > => :buddies_requested > many_to_many :buddies_requested, User, :foreign_name > => :buddies_pending_confirmation > ... > end > -------------------- > > This is a reflexive join with several distinct relationships that > happen to join to objects of the same class. My issue is that, with > Og, only one join table is created to model *all* of these > relationship: og_user_user. Because of this, the relationships are > essentially mirrored. Thus, if a user is added to my > 'buddies_pending_confirmation' queue, they also appear in my 'buddies' > and 'buddies_requested' lists, although this is precisely the opposite > of the intended behavior. > > Kashia showed me a hack that circumvents this behavior (by defining a > self-join class for each of the relationships above), but we both > found it to be, well, a hack. It lacked the clarity and intuitiveness > of the code above. > > My suggestion, then, is to perhaps name join tables not by their > associated types, but by their given label (the first argument to > 'many_to_many'). Thus, my 'og_user_user' table right now would > actually be three tables, 'og_user_buddies', > 'og_user_buddies_pending_confirmation' and > 'og_user_buddies_requested'. > > Please let me know if this is unreasonable, stupid or unclear. Also, > if there's something I'm just altogether missing, set me straight. > > Thanks, > > Brian > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Fri Mar 2 04:52:05 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 2 Mar 2007 11:52:05 +0200 Subject: [Nitro] Quotes about Nitro Message-ID: Dear devs... I am looking for some quotes for the forthcoming update of nitroproject.org. If you have something nice/clever to say about Nitro/Og, reply to this post ;-) thanks, George. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From Reid.Thompson at ateb.com Fri Mar 2 09:08:49 2007 From: Reid.Thompson at ateb.com (Reid Thompson) Date: Fri, 02 Mar 2007 09:08:49 -0500 Subject: [Nitro] Quotes about Nitro In-Reply-To: References: Message-ID: <1172844529.21060.5.camel@localhost> Og -- ORM in two letters. On Fri, 2007-03-02 at 11:52 +0200, George Moschovitis wrote: > Dear devs... > > I am looking for some quotes for the forthcoming update of > nitroproject.org. If you have something nice/clever to say about > Nitro/Og, reply to this post ;-) > > thanks, > George. > From transfire at gmail.com Fri Mar 2 09:21:03 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Fri, 02 Mar 2007 14:21:03 -0000 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> Message-ID: <1172845263.688164.155640@p10g2000cwp.googlegroups.com> On Mar 2, 3:39 am, "George Moschovitis" wrote: > I am considering changing this to: > > Rocket Science > Nitro provides everything you need to create state of the art > applications for the emerging Web OS. Ixnay on the "emerging Web OS". T. From george.moschovitis at gmail.com Fri Mar 2 10:33:49 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 2 Mar 2007 17:33:49 +0200 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <1172845263.688164.155640@p10g2000cwp.googlegroups.com> References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: > Ixnay on the "emerging Web OS". Ixnay ? -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From wyhaines at gmail.com Fri Mar 2 11:17:34 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Fri, 2 Mar 2007 09:17:34 -0700 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: On 3/2/07, George Moschovitis wrote: > > Ixnay on the "emerging Web OS". > > > Ixnay ? Pig Latin is a language scrambling system that is sometimes used in English. One takes the first consonant or consonant cluster of the work, and moves it to the end of the word, adding the 'ay' sound after it. cat -> atcay dog -> ogday walrus -> alrusway nix -> ixnay ixnay and amscray (nix and scram), for whatever reason, are pretty well accepted as common English slang, now. Kirk Haines From george.moschovitis at gmail.com Fri Mar 2 12:19:52 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 2 Mar 2007 19:19:52 +0200 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: ok, what does nix mean then? -g. On 3/2/07, Kirk Haines wrote: > On 3/2/07, George Moschovitis wrote: > > > Ixnay on the "emerging Web OS". > > > > > > Ixnay ? > > Pig Latin is a language scrambling system that is sometimes used in English. > > One takes the first consonant or consonant cluster of the work, and > moves it to the end of the word, adding the 'ay' sound after it. > > cat -> atcay > dog -> ogday > walrus -> alrusway > nix -> ixnay > > ixnay and amscray (nix and scram), for whatever reason, are pretty > well accepted as common English slang, now. > > > Kirk Haines > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From wyhaines at gmail.com Fri Mar 2 12:51:27 2007 From: wyhaines at gmail.com (Kirk Haines) Date: Fri, 2 Mar 2007 10:51:27 -0700 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: On 3/2/07, George Moschovitis wrote: > ok, what does nix mean then? http://dictionary.reference.com/browse/nix Kirk Haines From nyarly at gmail.com Fri Mar 2 13:48:39 2007 From: nyarly at gmail.com (Judson Lester) Date: Fri, 2 Mar 2007 10:48:39 -0800 Subject: [Nitro] Nitro homepage banner... In-Reply-To: References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: <8905c87a0703021048t56e1e43o7987f195924ba105@mail.gmail.com> He means "don't use emerging Web OS" On 3/2/07, Kirk Haines wrote: > On 3/2/07, George Moschovitis wrote: > > ok, what does nix mean then? > > http://dictionary.reference.com/browse/nix > > > Kirk Haines > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From billk at cts.com Fri Mar 2 14:03:21 2007 From: billk at cts.com (Bill Kelly) Date: Fri, 2 Mar 2007 11:03:21 -0800 Subject: [Nitro] Nitro homepage banner... References: <45E6517A.5020705@gmail.com><45E7242F.4030307@gmail.com><1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: <059901c75cfd$729272b0$6442a8c0@musicbox> From: "Kirk Haines" > On 3/2/07, George Moschovitis wrote: > >>> From: >>>> Ixnay on the "emerging Web OS". >> >> ok, what does nix mean then? > > http://dictionary.reference.com/browse/nix In other words, the banner needs to depict a water spirit luring victims to its underwater emerging Web OS. :D Sorry could not resist, Bill From james.britt at gmail.com Fri Mar 2 15:02:52 2007 From: james.britt at gmail.com (James Britt) Date: Fri, 02 Mar 2007 13:02:52 -0700 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <1172845263.688164.155640@p10g2000cwp.googlegroups.com> References: <45E6517A.5020705@gmail.com> <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> Message-ID: <45E882EC.4020303@gmail.com> transfire at gmail.com wrote: > > On Mar 2, 3:39 am, "George Moschovitis" > wrote: >> I am considering changing this to: >> >> Rocket Science >> Nitro provides everything you need to create state of the art >> applications for the emerging Web OS. > > Ixnay on the "emerging Web OS". > I think that should be, "Ixnay on the Eb-oh-ess-way" With which I concur. Too buzzy. -- James Britt "Hackers will be expelled" - The Breakfast Club (1985) From george.moschovitis at gmail.com Fri Mar 2 15:22:01 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 2 Mar 2007 22:22:01 +0200 Subject: [Nitro] Nitro homepage banner... In-Reply-To: <059901c75cfd$729272b0$6442a8c0@musicbox> References: <45E7242F.4030307@gmail.com> <1172845263.688164.155640@p10g2000cwp.googlegroups.com> <059901c75cfd$729272b0$6442a8c0@musicbox> Message-ID: ok, got it :) -g. On 3/2/07, Bill Kelly wrote: > From: "Kirk Haines" > > On 3/2/07, George Moschovitis wrote: > > > >>> From: > >>>> Ixnay on the "emerging Web OS". > >> > >> ok, what does nix mean then? > > > > http://dictionary.reference.com/browse/nix > > In other words, the banner needs to depict a water spirit > luring victims to its underwater emerging Web OS. > > > :D > > Sorry could not resist, > > Bill > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Sat Mar 3 04:08:59 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 3 Mar 2007 11:08:59 +0200 Subject: [Nitro] Nitro sessions Message-ID: Dear devs, the latest repo version contains a new implementation of Nitro Sessions. The new default session store is a Cookie based store (with a twist ;-)). I have converted the old MemoryStore and DrbStore to the new system. If anyone wants to use the Memcached/File/Og stores then please submit a patch (have a look at DrbStore and you will see that this is EXTREMELY easy to do). I just want to see more contributors, and this is a very easy thing to do to contribute to this project. thanks, George. PS: I will demonstrate the 'twist' in examples/blog and/or my blog. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From transfire at gmail.com Sat Mar 3 15:26:22 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Sat, 03 Mar 2007 20:26:22 -0000 Subject: [Nitro] Facets instance_method? In-Reply-To: References: Message-ID: <1172953582.954385.180530@8g2000cwh.googlegroups.com> On Feb 27, 1:16 pm, "George Moschovitis" wrote: > Tom, > > how about including > > klass.instance_method? :meth Is this different from method_defined? T. From transfire at gmail.com Sat Mar 3 21:34:49 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 04 Mar 2007 02:34:49 -0000 Subject: [Nitro] Glue -> Facets In-Reply-To: References: <1172430483.482558.109540@p10g2000cwp.googlegroups.com> Message-ID: <1172975689.109167.91080@v33g2000cwv.googlegroups.com> On Feb 25, 4:58 pm, "Jonathan Buch" wrote: > Hi, > > > Well that's just > > great! I have to choose between a huge number of dependencies or > > screwed up docs. > > > unless someone has a bright idea.... > > no bright idea here, but I think broken docs on rubygems page are > less disturbing than to type 'y' 70 times. eeeeen-how :) > I love the 'spotlight' idea on the facets page btw.... When you > provide generated docs by yourself on rubyforge (in a better way > than rubygems does), wouldn't that be ok? (big link on the first > 'page' of the rubygems-generated rdocs to rubyforge) that's a good point/idea. for now i've made the More libs separate subprojects and use a custom task to bring them altogether into a single package for release. so yea, the rdocs of the single package will be garbled on install by gems, but i'll add a notice as you suggest about that. in making this change btw it became quite hard not to end up with two distinct projects, one for Core and another for More. as the repository currently stands, More isn't really recognizable as such b/ c Core is just a subproject along with all the others. it's kind of weird. i think it's progress though. at the very least the More libs are more managable, and now coders can depend on bits of pieces of facets without having to install the whole thing if they don't want. of course I prefer they just install the whole thing, but having the option is probably good --after all that's what facets is about, right? speaking of spotlights, i've been thinking of putting those on the wiki, so it's easier for others to contribute new spotlights. i'll also keep a page on the website itself that reflects these but formmated better. T. From george.moschovitis at gmail.com Sun Mar 4 03:19:08 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 4 Mar 2007 10:19:08 +0200 Subject: [Nitro] Facets instance_method? In-Reply-To: <1172953582.954385.180530@8g2000cwh.googlegroups.com> References: <1172953582.954385.180530@8g2000cwh.googlegroups.com> Message-ID: > Is this different from method_defined? ah, nice one... but an alias (instance_method?) would be nice. -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Sun Mar 4 05:05:56 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 4 Mar 2007 12:05:56 +0200 Subject: [Nitro] Ruby question... Message-ID: Dear devs, lets say I have the variable: base = Namespace::MyModule I need a method (lets call it extract) that works like this: extract(base) # => Namespace any ideas? -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From transfire at gmail.com Sun Mar 4 09:21:22 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 04 Mar 2007 14:21:22 -0000 Subject: [Nitro] Ruby question... In-Reply-To: References: Message-ID: <1173018082.027666.260780@8g2000cwh.googlegroups.com> On Mar 4, 5:05 am, "George Moschovitis" wrote: > Dear devs, > > lets say I have the variable: > > base = Namespace::MyModule > > I need a method (lets call it extract) that works like this: > > extract(base) # => Namespace > > any ideas? irb(main):005:0> require 'facets/core/module/dirname' => true irb(main):006:0> module X irb(main):007:1> module Y irb(main):008:2> end irb(main):009:1> end => nil irb(main):010:0> X::Y.basename NoMethodError: undefined method `basename' for X::Y:Module from (irb):10 from :0 irb(main):011:0> X::Y.dirname => "X" I know, the name 'dirname' is kind of odd, but I took the idea from File along with module/basename btw. Also X::Y.name.split('::') I'd make that a method of Module too if I could think of a good name for it. T. From transfire at gmail.com Sun Mar 4 09:42:14 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 04 Mar 2007 14:42:14 -0000 Subject: [Nitro] Ruby question... In-Reply-To: <1173018082.027666.260780@8g2000cwh.googlegroups.com> References: <1173018082.027666.260780@8g2000cwh.googlegroups.com> Message-ID: <1173019334.698087.68260@i80g2000cwc.googlegroups.com> On Mar 4, 9:21 am, transf... at gmail.com wrote: > NoMethodError: undefined method `basename' for X::Y:Module > from (irb):10 > from :0 oops. you have to require module/basename for that. T. From transfire at gmail.com Sun Mar 4 09:44:16 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 04 Mar 2007 14:44:16 -0000 Subject: [Nitro] Og on it's own Message-ID: <1173019456.929029.299780@n33g2000cwc.googlegroups.com> With the new layout will Og get it's own Darcs repo. I think Og is a great database interface and deserves to pushed on it's own merits independent of Nitro. Eg. it's own webpage, etc. T. From george.moschovitis at gmail.com Sun Mar 4 10:46:52 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 4 Mar 2007 17:46:52 +0200 Subject: [Nitro] Og on it's own In-Reply-To: <1173019456.929029.299780@n33g2000cwc.googlegroups.com> References: <1173019456.929029.299780@n33g2000cwc.googlegroups.com> Message-ID: I am not sure about this. Too much work to maintain a second webpage. But I will promote Og in the new website I am working on. In fact I will redesign it a little bit to make Og stand out. -g. On 3/4/07, transfire at gmail.com wrote: > With the new layout will Og get it's own Darcs repo. I think Og is a > great database interface and deserves to pushed on it's own merits > independent of Nitro. Eg. it's own webpage, etc. > > T. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Sun Mar 4 10:48:34 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 4 Mar 2007 17:48:34 +0200 Subject: [Nitro] Ruby question... In-Reply-To: <1173018082.027666.260780@8g2000cwh.googlegroups.com> References: <1173018082.027666.260780@8g2000cwh.googlegroups.com> Message-ID: dirname is strange indeed... how about namespace ? -g. PS: I think I had a namespace method in an older version of Glue, this must be somewhere in facets? On 3/4/07, transfire at gmail.com wrote: > > > On Mar 4, 5:05 am, "George Moschovitis" > wrote: > > Dear devs, > > > > lets say I have the variable: > > > > base = Namespace::MyModule > > > > I need a method (lets call it extract) that works like this: > > > > extract(base) # => Namespace > > > > any ideas? > > irb(main):005:0> require 'facets/core/module/dirname' > => true > irb(main):006:0> module X > irb(main):007:1> module Y > irb(main):008:2> end > irb(main):009:1> end > => nil > irb(main):010:0> X::Y.basename > NoMethodError: undefined method `basename' for X::Y:Module > from (irb):10 > from :0 > irb(main):011:0> X::Y.dirname > => "X" > > I know, the name 'dirname' is kind of odd, but I took the idea from > File along with module/basename btw. > > Also > > X::Y.name.split('::') > > I'd make that a method of Module too if I could think of a good name > for it. > > T. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From transfire at gmail.com Sun Mar 4 17:49:05 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Sun, 04 Mar 2007 22:49:05 -0000 Subject: [Nitro] Og on it's own In-Reply-To: References: <1173019456.929029.299780@n33g2000cwc.googlegroups.com> Message-ID: <1173048545.913081.195800@c51g2000cwc.googlegroups.com> On Mar 4, 10:46 am, "George Moschovitis" wrote: > I am not sure about this. Too much work to maintain a second webpage. > But I will promote Og in the new website I am working on. In fact I > will redesign it a little bit to make Og stand out. well, its a start. though I really think you should give Og it's own birthrights ;) maybe you put too much into the website? i don't think the website needs to be a wiki. a main website that rarely changes is good, the wiki secondary and thus can be more freeform. btw I notice a number of rmpty pages on nitro's which give a very unfinshed feel -- better not to even have links until the pages have content. thanks, t. From george.moschovitis at gmail.com Mon Mar 5 01:49:59 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 5 Mar 2007 08:49:59 +0200 Subject: [Nitro] Og on it's own In-Reply-To: <1173048545.913081.195800@c51g2000cwc.googlegroups.com> References: <1173019456.929029.299780@n33g2000cwc.googlegroups.com> <1173048545.913081.195800@c51g2000cwc.googlegroups.com> Message-ID: > better not to even have links until the pages have content. I am preparing a new site. Hopefully I will have a preview ready this week. -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From john at oxyliquit.de Mon Mar 5 02:19:29 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Mon, 05 Mar 2007 09:19:29 +0200 Subject: [Nitro] Quotes about Nitro In-Reply-To: References: Message-ID: Hi, > Dear devs... non devs included too! ;) > I am looking for some quotes for the forthcoming update of > nitroproject.org. If you have something nice/clever to say about > Nitro/Og, reply to this post ;-) My two favourite ones: :) damnit, nitro is better, than I though, but I really miss the docs... ehird: as usual with nitro, you can do whatever you want, no limits Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Mon Mar 5 02:39:41 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Mon, 5 Mar 2007 09:39:41 +0200 Subject: [Nitro] Quotes about Nitro In-Reply-To: References: Message-ID: I need full/last names... -.g On 3/5/07, Jonathan Buch wrote: > Hi, > > > Dear devs... > > non devs included too! ;) > > > I am looking for some quotes for the forthcoming update of > > nitroproject.org. If you have something nice/clever to say about > > Nitro/Og, reply to this post ;-) > > My two favourite ones: :) > > damnit, nitro is better, than I though, but I really miss the docs... > > ehird: as usual with nitro, you can do whatever you want, no limits > > 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://cull.gr http://www.joy.gr http://nitroproject.org From transfire at gmail.com Mon Mar 5 14:38:25 2007 From: transfire at gmail.com (TRANS) Date: Mon, 5 Mar 2007 14:38:25 -0500 Subject: [Nitro] Aspects and more... In-Reply-To: References: <4b6f054f0703051015o64714760u367b5c23a6a7291@mail.gmail.com> Message-ID: <4b6f054f0703051138xa4be21ahf031c2119054b76e@mail.gmail.com> "Jim! I am a web developer not a rocket scientist! ;-) T. From jos at catnook.com Mon Mar 5 17:14:06 2007 From: jos at catnook.com (Jos Backus) Date: Mon, 5 Mar 2007 14:14:06 -0800 Subject: [Nitro] Interesting web framework article In-Reply-To: <43579.192.176.230.1.1172075728.squirrel@webmaiil.lassoweb.se> References: <39131.192.176.230.1.1172046749.squirrel@webmail.lassoweb.se> <45DC6CC2.2030505@gmail.com> <43579.192.176.230.1.1172075728.squirrel@webmaiil.lassoweb.se> Message-ID: <20070305221406.GA42063@lizzy.catnook.local> Fwiw, I tried getting people insterested in the idea of being able to restrict class changes. So one could make it so that changes to String would only be visible within, say, Nitro. But it didn't go anywhere. Sadly, I think Python gets this right, as it makes scaling more difficult. See http://www.ruby-forum.com/topic/94327#new for the thread. -- Jos Backus jos at catnook.com From jos at catnook.com Mon Mar 5 19:45:32 2007 From: jos at catnook.com (Jos Backus) Date: Mon, 5 Mar 2007 16:45:32 -0800 Subject: [Nitro] Og, adapting postgresql to reorgnaization In-Reply-To: <8905c87a0702211633y39bbefb6icb6da828ca7dea5e@mail.gmail.com> References: <8905c87a0702211049x7c4f4795mceb0e5fef8dfab72@mail.gmail.com> <8905c87a0702211633y39bbefb6icb6da828ca7dea5e@mail.gmail.com> Message-ID: <20070306004532.GB42063@lizzy.catnook.local> On Wed, Feb 21, 2007 at 04:33:28PM -0800, Judson Lester wrote: > Why autoincrements weren't part of the original spec, I'll never know. But PostgreSQL has support for sequences, which are in SQL2003, unlike MySQL's proprietary autoincrement "feature". See http://www.varlena.com/GeneralBits/71.php and http://dev.mysql.com/tech-resources/faq.html#gen5 (Yes, I vastly prefer PostgreSQL over MySQL.) -- Jos Backus jos at catnook.com From nyarly at gmail.com Mon Mar 5 19:59:59 2007 From: nyarly at gmail.com (Judson Lester) Date: Mon, 5 Mar 2007 16:59:59 -0800 Subject: [Nitro] Isolated specs bundle Message-ID: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> The attached patch bundle changes the way specs run so that each spec gets it's own shot at the database - there shouldn't be any carryover, which is pretty crucial to proper testing. Also, Postgres is much quieter now. One issue with it right now is that each spec file needs to be run individually. If anyone can figure out why, I'd love it. -------------- next part -------------- A non-text attachment was scrubbed... Name: isolating-spec.bndl Type: application/octet-stream Size: 45609 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070305/2da20418/attachment-0001.obj From nyarly at gmail.com Mon Mar 5 20:02:31 2007 From: nyarly at gmail.com (Judson Lester) Date: Mon, 5 Mar 2007 17:02:31 -0800 Subject: [Nitro] Og, adapting postgresql to reorgnaization In-Reply-To: <20070306004532.GB42063@lizzy.catnook.local> References: <8905c87a0702211049x7c4f4795mceb0e5fef8dfab72@mail.gmail.com> <8905c87a0702211633y39bbefb6icb6da828ca7dea5e@mail.gmail.com> <20070306004532.GB42063@lizzy.catnook.local> Message-ID: <8905c87a0703051702l1d5618e4of1be2f955ded7862@mail.gmail.com> Oh, we're on the same page. I just wish that an auto-incrementing type was part of the SQL spec, so that we didn't have such vast variations between how databases handle a pretty basic operation. That said, I continue to examine how Postgres could usefully use it's sequence lookup safely. Judson On 3/5/07, Jos Backus wrote: > On Wed, Feb 21, 2007 at 04:33:28PM -0800, Judson Lester wrote: > > Why autoincrements weren't part of the original spec, I'll never know. > > But PostgreSQL has support for sequences, which are in SQL2003, unlike MySQL's > proprietary autoincrement "feature". See > http://www.varlena.com/GeneralBits/71.php and > http://dev.mysql.com/tech-resources/faq.html#gen5 > > (Yes, I vastly prefer PostgreSQL over MySQL.) > > -- > Jos Backus > jos at catnook.com > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From transfire at gmail.com Mon Mar 5 20:18:55 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Tue, 06 Mar 2007 01:18:55 -0000 Subject: [Nitro] Og, adapting postgresql to reorgnaization In-Reply-To: <8905c87a0703051702l1d5618e4of1be2f955ded7862@mail.gmail.com> References: <8905c87a0702211049x7c4f4795mceb0e5fef8dfab72@mail.gmail.com> <8905c87a0702211633y39bbefb6icb6da828ca7dea5e@mail.gmail.com> <20070306004532.GB42063@lizzy.catnook.local> <8905c87a0703051702l1d5618e4of1be2f955ded7862@mail.gmail.com> Message-ID: <1173143935.641803.117420@q40g2000cwq.googlegroups.com> On Mar 5, 8:02 pm, "Judson Lester" wrote: > Oh, we're on the same page. I just wish that an auto-incrementing > type was part of the SQL spec, so that we didn't have such vast > variations between how databases handle a pretty basic operation. > > That said, I continue to examine how Postgres could usefully use it's > sequence lookup safely. > > Judson > > On 3/5/07, Jos Backus wrote: > > > On Wed, Feb 21, 2007 at 04:33:28PM -0800, Judson Lester wrote: > > > Why autoincrements weren't part of the original spec, I'll never know. > > > But PostgreSQL has support for sequences, which are in SQL2003, unlike MySQL's > > proprietary autoincrement "feature". See > >http://www.varlena.com/GeneralBits/71.phpand > >http://dev.mysql.com/tech-resources/faq.html#gen5 > > > (Yes, I vastly prefer PostgreSQL over MySQL.) Think this has been discussed before and the solution is to not use autoincrement. There shoud be an adapter method #new_id(table). In PostgreSQL this would quesry the sequence. Can MySQL handles this? Other stores? T. From nyarly at gmail.com Mon Mar 5 20:35:07 2007 From: nyarly at gmail.com (Judson Lester) Date: Mon, 5 Mar 2007 17:35:07 -0800 Subject: [Nitro] SQL bundle Message-ID: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> Working towards removing the OGTABLE semi-constant in favor of class methods, and a first step towards better oid generation in postgres (and better basis for similar for other DBs) Judson -------------- next part -------------- A non-text attachment was scrubbed... Name: sql-cleanup.bndl Type: application/octet-stream Size: 27150 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070305/4bb00476/attachment-0001.obj From transfire at gmail.com Mon Mar 5 20:36:01 2007 From: transfire at gmail.com (transfire at gmail.com) Date: Tue, 06 Mar 2007 01:36:01 -0000 Subject: [Nitro] Interesting web framework article In-Reply-To: <20070305221406.GA42063@lizzy.catnook.local> References: <39131.192.176.230.1.1172046749.squirrel@webmail.lassoweb.se> <45DC6CC2.2030505@gmail.com> <43579.192.176.230.1.1172075728.squirrel@webmaiil.lassoweb.se> <20070305221406.GA42063@lizzy.catnook.local> Message-ID: <1173144961.296423.271350@c51g2000cwc.googlegroups.com> On Mar 5, 5:14 pm, Jos Backus wrote: > Fwiw, I tried getting people insterested in the idea of being able to restrict > class changes. So one could make it so that changes to String would only be > visible within, say, Nitro. But it didn't go anywhere. Sadly, I think Python > gets this right, as it makes scaling more difficult. > > Seehttp://www.ruby-forum.com/topic/94327#newfor the thread. Whiel ther are wasy to do this sort of thing, it's not a built-in part of Ruby so it's hacky. In fact Facets has a lib that comes damn close to allowing this scoping control and I've meaning to finish extending it to do so, BUT that's a far cry from something we'd want to use in everyday production code. It remains to be seen how efficient and reliable it would be. And of course there the other issue of the extra syntax invloved. Ideally Ruby would have a way to limit an extension to the current file. But that's not something one can code in pure Ruby however. Short of that I think the best we can do here is try to get ActiveSupport and Facets as compatiable as reasonablly possible. However ther may be one other option. I beleive _why developed something recently that might allow dynamic process swapping. In other words it's like having more than one ruby interpretor running at the same time (hence with differnt extensions) and flipping between them on the fly in the same program. At least, that's how it seemed to me. I have no idea what's involved in oding it though. T. From jos at catnook.com Mon Mar 5 22:06:29 2007 From: jos at catnook.com (Jos Backus) Date: Mon, 5 Mar 2007 19:06:29 -0800 Subject: [Nitro] Og, adapting postgresql to reorgnaization In-Reply-To: <8905c87a0703051702l1d5618e4of1be2f955ded7862@mail.gmail.com> References: <8905c87a0702211049x7c4f4795mceb0e5fef8dfab72@mail.gmail.com> <8905c87a0702211633y39bbefb6icb6da828ca7dea5e@mail.gmail.com> <20070306004532.GB42063@lizzy.catnook.local> <8905c87a0703051702l1d5618e4of1be2f955ded7862@mail.gmail.com> Message-ID: <20070306030629.GA52942@lizzy.catnook.local> On Mon, Mar 05, 2007 at 05:02:31PM -0800, Judson Lester wrote: > Oh, we're on the same page. I just wish that an auto-incrementing > type was part of the SQL spec, so that we didn't have such vast > variations between how databases handle a pretty basic operation. Agreed. But since the spec already has sequences, adding auto-incrementing types would be duplication of functionality. Besides, sequences are more powerful (but perhaps slighly less easy to use). If MySQL cared about standards they would simply implement them and make everybody's life a little easier. But given how popular MySQL is I doubt they'll feel a strong need; people will use their (mediocre) product anyway since it's the M in LAMP and ships with many distros. (Hm, I wonder how IE got so popular...) > That said, I continue to examine how Postgres could usefully use it's > sequence lookup safely. Thanks Judson! Jos > Judson > > On 3/5/07, Jos Backus wrote: > >On Wed, Feb 21, 2007 at 04:33:28PM -0800, Judson Lester wrote: > >> Why autoincrements weren't part of the original spec, I'll never know. > > > >But PostgreSQL has support for sequences, which are in SQL2003, unlike > >MySQL's > >proprietary autoincrement "feature". See > >http://www.varlena.com/GeneralBits/71.php and > >http://dev.mysql.com/tech-resources/faq.html#gen5 > > > >(Yes, I vastly prefer PostgreSQL over MySQL.) > > > >-- > >Jos Backus > >jos at catnook.com > >_______________________________________________ > >Nitro-general mailing list > >Nitro-general at rubyforge.org > >http://rubyforge.org/mailman/listinfo/nitro-general > > -- Jos Backus jos at catnook.com From george.moschovitis at gmail.com Tue Mar 6 01:59:06 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 6 Mar 2007 08:59:06 +0200 Subject: [Nitro] SQL bundle In-Reply-To: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> References: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> Message-ID: Thanks for the patches. I will consider them for inclusion. -g. On 3/6/07, Judson Lester wrote: > Working towards removing the OGTABLE semi-constant in favor of class > methods, and a first step towards better oid generation in postgres > (and better basis for similar for other DBs) > > Judson > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From john at oxyliquit.de Tue Mar 6 02:25:12 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 06 Mar 2007 09:25:12 +0200 Subject: [Nitro] Isolated specs bundle In-Reply-To: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> References: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> Message-ID: Hi, > The attached patch bundle changes the way specs run so that each spec > gets it's own shot at the database - there shouldn't be any carryover, > which is pretty crucial to proper testing. Also, Postgres is much > quieter now. in earlier days each test would open its own og connection, I had then (for myself) made a change so the og-stores would be reused. This had the huge advantage of the tests running much faster through. The tests itself will not interfere with each other (because of each test residing in its own class and so getting different table names. Maybe something similar can be done with Specs, just put every og class into a class called like the filename. Of course, the og startup is much better nowadays (at least when using Og.setup(:classes => [Klass]). > One issue with it right now is that each spec file needs to be run > individually. If anyone can figure out why, I'd love it. Maybe a test script (script/test.rb) can be created for specs as well? Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From george.moschovitis at gmail.com Tue Mar 6 02:32:56 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 6 Mar 2007 09:32:56 +0200 Subject: [Nitro] Isolated specs bundle In-Reply-To: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> References: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> Message-ID: Judson, if possible please break your specs in more specify blogs so that we get a better (more descriptive) implementation. For example: specify "should provide standard og features" do is too general and could possibly be splite in more blocks. thanks for your work, George. PS: btw, please use attr_accessor instead of property! -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Tue Mar 6 02:39:16 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 6 Mar 2007 09:39:16 +0200 Subject: [Nitro] SQL bundle In-Reply-To: References: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> Message-ID: Ok, I applied both your patches. Btw, In the future please pull the latest version of the repo before submitting your patches. This makes things easier (and safer) when I try to integrate them. thanks, George. On 3/6/07, George Moschovitis wrote: > Thanks for the patches. I will consider them for inclusion. > > -g. > > On 3/6/07, Judson Lester wrote: > > Working towards removing the OGTABLE semi-constant in favor of class > > methods, and a first step towards better oid generation in postgres > > (and better basis for similar for other DBs) > > > > Judson > > > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > > > > -- > http://blog.gmosx.com > http://cull.gr > http://www.joy.gr > http://nitroproject.org > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From john at oxyliquit.de Tue Mar 6 02:52:04 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 06 Mar 2007 09:52:04 +0200 Subject: [Nitro] SQL bundle In-Reply-To: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> References: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> Message-ID: Hi, > Working towards removing the OGTABLE semi-constant in favor of class > methods, > and a first step towards better oid generation in postgres > (and better basis for similar for other DBs) # raise StoreException, "Postgres stores need a sequence annotation for primary keys" I'm worried about this line. This will break custom primary key rows which is pretty much unacceptable. Think about textual pks for example. Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Tue Mar 6 03:03:27 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 06 Mar 2007 10:03:27 +0200 Subject: [Nitro] Og, adapting postgresql to reorgnaization In-Reply-To: <1173143935.641803.117420@q40g2000cwq.googlegroups.com> References: <8905c87a0702211049x7c4f4795mceb0e5fef8dfab72@mail.gmail.com> <8905c87a0702211633y39bbefb6icb6da828ca7dea5e@mail.gmail.com> <20070306004532.GB42063@lizzy.catnook.local> <8905c87a0703051702l1d5618e4of1be2f955ded7862@mail.gmail.com> <1173143935.641803.117420@q40g2000cwq.googlegroups.com> Message-ID: Hi, > Think this has been discussed before and the solution is to not use > autoincrement. There shoud be an adapter method #new_id(table). In > PostgreSQL this would quesry the sequence. yes, I think this would be the way to go... SELECT AUTO_INCREMENT FROM information_schema.tables WHERE TABLE_SCHEMA = 'test' AND TABLE_NAME = 'addresses'; maybe around those lines... Just now to find out how to actually increment the auto increment.. Well, how about: ALTER TABLE tbl AUTO_INCREMENT = 100; and just set that to one above and use the correct oid for inserting, should replicate the psql behaviour. Someone care to find out how to do that stuff for sqlite? Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From nyarly at gmail.com Tue Mar 6 03:59:14 2007 From: nyarly at gmail.com (Judson Lester) Date: Tue, 6 Mar 2007 00:59:14 -0800 Subject: [Nitro] SQL bundle In-Reply-To: References: <8905c87a0703051735l17ae9605m1cae08b5bec240ae@mail.gmail.com> Message-ID: <8905c87a0703060059y36e2946cncfb02452db241255@mail.gmail.com> > # raise StoreException, "Postgres stores need a sequence annotation for primary keys" > > I'm worried about this line. This will break custom primary key rows > which is pretty much unacceptable. Think about textual pks for example. Good point. With psql, though it seems reasonable then to either require a :sequence PK or an explicit value for the PK. Or am I still overlooking something? Judson > > 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 > From nyarly at gmail.com Tue Mar 6 04:04:58 2007 From: nyarly at gmail.com (Judson Lester) Date: Tue, 6 Mar 2007 01:04:58 -0800 Subject: [Nitro] Isolated specs bundle In-Reply-To: References: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> Message-ID: <8905c87a0703060104u6fb781aekcfef89b6b1bd8f60@mail.gmail.com> On 3/5/07, George Moschovitis wrote: > Judson, > > if possible please break your specs in more specify blogs so that we > get a better (more descriptive) implementation. For example: > > specify "should provide standard og features" do > > is too general and could possibly be splite in more blocks. Believe me, I agree. These are based on the test classes as originally written. I started to break them down, and realized they were all tangled up. I fully intend to go back and pick them apart. And one of my recent patches - I think it made it into a bundle - fixed the spec spec/* issue. And yeah, the setup is pretty quick now. From george.moschovitis at gmail.com Tue Mar 6 06:48:22 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Tue, 6 Mar 2007 13:48:22 +0200 Subject: [Nitro] Og test cases and specs Message-ID: Dear devs, Og needs a strong and up-to-date suite of specs. The repo currently contains many out-of-date tests. I need your help to rectify this. Here is a plan: * the tests must be updated: - require paths fixed - property converted to attr_accessor - ' converted to " - use correct name spaces. * Test cases must pass * Test cases should be converted to specs * specs need refactoring. Since many people on this list use Og and care about this library, I would expect to see some volunteers for this work. thanks, George. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From nyarly at gmail.com Tue Mar 6 12:50:23 2007 From: nyarly at gmail.com (Judson Lester) Date: Tue, 6 Mar 2007 09:50:23 -0800 Subject: [Nitro] Og test cases and specs In-Reply-To: References: Message-ID: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> On 3/6/07, George Moschovitis wrote: > Dear devs, > > Og needs a strong and up-to-date suite of specs. The repo currently > contains many out-of-date tests. I need your help to rectify this. Especially if you've ever had a favorite Og bug that you never want to see again. Writing a spec that would expose it is a great way to make sure it never happens. Note that there's a file now in the root of og called 'spec-helper.rb' that includes the functionality of CONFIG.rb plus some extras, like a single method to use in setup to manage the test classes and return a store. Take a look at it, there's not much there, but I'm pleased with it. Judson > Here is a plan: > > * the tests must be updated: > - require paths fixed > - property converted to attr_accessor > - ' converted to " > - use correct name spaces. > * Test cases must pass > * Test cases should be converted to specs > * specs need refactoring. > > Since many people on this list use Og and care about this library, I > would expect to see some volunteers for this work. > > thanks, > George. > > -- > http://blog.gmosx.com > http://cull.gr > http://www.joy.gr > http://nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From george.moschovitis at gmail.com Wed Mar 7 12:29:34 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 7 Mar 2007 19:29:34 +0200 Subject: [Nitro] Og test cases and specs In-Reply-To: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> References: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> Message-ID: > Note that there's a file now in the root of og called 'spec-helper.rb' > that includes the functionality of CONFIG.rb plus some extras, like a > single method to use in setup to manage the test classes and return a > store. Take a look at it, there's not much there, but I'm pleased > with it. I would prefer spec-helper.rb to be renamed to helper.rb and moved inside spec/ -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From nyarly at gmail.com Wed Mar 7 13:22:36 2007 From: nyarly at gmail.com (Judson Lester) Date: Wed, 7 Mar 2007 10:22:36 -0800 Subject: [Nitro] Og test cases and specs In-Reply-To: References: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> Message-ID: <8905c87a0703071022k7f235487t82cddf216e1c181d@mail.gmail.com> The only downside to that is that spec spec/* would load spec-helper.rb as well. On 3/7/07, George Moschovitis wrote: > > Note that there's a file now in the root of og called 'spec-helper.rb' > > that includes the functionality of CONFIG.rb plus some extras, like a > > single method to use in setup to manage the test classes and return a > > store. Take a look at it, there's not much there, but I'm pleased > > with it. > > I would prefer spec-helper.rb to be renamed to helper.rb and moved inside spec/ > > -g. > > -- > http://blog.gmosx.com > http://cull.gr > http://www.joy.gr > http://nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From george.moschovitis at gmail.com Wed Mar 7 14:01:24 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Wed, 7 Mar 2007 21:01:24 +0200 Subject: [Nitro] Og test cases and specs In-Reply-To: <8905c87a0703071022k7f235487t82cddf216e1c181d@mail.gmail.com> References: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> <8905c87a0703071022k7f235487t82cddf216e1c181d@mail.gmail.com> Message-ID: it is easy to remove this file though... -g. On 3/7/07, Judson Lester wrote: > The only downside to that is that spec spec/* would load spec-helper.rb as well. > > On 3/7/07, George Moschovitis wrote: > > > Note that there's a file now in the root of og called 'spec-helper.rb' > > > that includes the functionality of CONFIG.rb plus some extras, like a > > > single method to use in setup to manage the test classes and return a > > > store. Take a look at it, there's not much there, but I'm pleased > > > with it. > > > > I would prefer spec-helper.rb to be renamed to helper.rb and moved inside spec/ > > > > -g. > > > > -- > > http://blog.gmosx.com > > http://cull.gr > > http://www.joy.gr > > http://nitroproject.org > > _______________________________________________ > > 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://cull.gr http://www.joy.gr http://nitroproject.org From nyarly at gmail.com Wed Mar 7 17:35:25 2007 From: nyarly at gmail.com (Judson Lester) Date: Wed, 7 Mar 2007 14:35:25 -0800 Subject: [Nitro] Og test cases and specs In-Reply-To: References: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> <8905c87a0703071022k7f235487t82cddf216e1c181d@mail.gmail.com> Message-ID: <8905c87a0703071435l5ab1fa8eu579c83fe38f1ae53@mail.gmail.com> On 3/7/07, George Moschovitis wrote: > it is easy to remove this file though... > > -g. How do you mean? From nyarly at gmail.com Wed Mar 7 20:59:33 2007 From: nyarly at gmail.com (Judson Lester) Date: Wed, 7 Mar 2007 17:59:33 -0800 Subject: [Nitro] Spec splitting for spec/store Message-ID: <8905c87a0703071759u44b81541jdd4faac80a7dd41e@mail.gmail.com> Attached is a bundle of spec updates. There are 5 failures. The specs are an attempt at to translate the old tc_store.rb with fidelity, while trying to produce a useful spec. Exposing 5 failures seems like a useful spec to me! Judson -------------- next part -------------- A non-text attachment was scrubbed... Name: store-spec-split.bndl Type: application/octet-stream Size: 51574 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070307/029ec2e6/attachment-0001.obj From nyarly at gmail.com Wed Mar 7 21:13:56 2007 From: nyarly at gmail.com (Judson Lester) Date: Wed, 7 Mar 2007 18:13:56 -0800 Subject: [Nitro] Spec splitting for spec/store In-Reply-To: <8905c87a0703071759u44b81541jdd4faac80a7dd41e@mail.gmail.com> References: <8905c87a0703071759u44b81541jdd4faac80a7dd41e@mail.gmail.com> Message-ID: <8905c87a0703071813o36068d3cp150057ed297d4a7d@mail.gmail.com> THis is a newer bundle that incorporates a merge with the repo On 3/7/07, Judson Lester wrote: > Attached is a bundle of spec updates. There are 5 failures. The > specs are an attempt at to translate the old tc_store.rb with > fidelity, while trying to produce a useful spec. Exposing 5 failures > seems like a useful spec to me! > > Judson > > -------------- next part -------------- A non-text attachment was scrubbed... Name: store-spec-split.bndl Type: application/octet-stream Size: 52734 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070307/002be6d7/attachment-0001.obj From george.moschovitis at gmail.com Thu Mar 8 01:36:09 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 8 Mar 2007 08:36:09 +0200 Subject: [Nitro] Og test cases and specs In-Reply-To: <8905c87a0703071435l5ab1fa8eu579c83fe38f1ae53@mail.gmail.com> References: <8905c87a0703060950m58eb1a3r23526fa5ef2a6c10@mail.gmail.com> <8905c87a0703071022k7f235487t82cddf216e1c181d@mail.gmail.com> <8905c87a0703071435l5ab1fa8eu579c83fe38f1ae53@mail.gmail.com> Message-ID: Dir[..].except(...) -g. On 3/8/07, Judson Lester wrote: > On 3/7/07, George Moschovitis wrote: > > it is easy to remove this file though... > > > > -g. > > How do you mean? > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Thu Mar 8 01:36:45 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 8 Mar 2007 08:36:45 +0200 Subject: [Nitro] Spec splitting for spec/store In-Reply-To: <8905c87a0703071813o36068d3cp150057ed297d4a7d@mail.gmail.com> References: <8905c87a0703071759u44b81541jdd4faac80a7dd41e@mail.gmail.com> <8905c87a0703071813o36068d3cp150057ed297d4a7d@mail.gmail.com> Message-ID: Many thanks ;-) -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Thu Mar 8 11:52:53 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Thu, 8 Mar 2007 18:52:53 +0200 Subject: [Nitro] New implementation of Og Validations. (Help needed) Message-ID: Dear devs, I am trying to cleanup the validations implementation in Og. First of all I would like to remove validations.rb from the glue dir and keep a single file in Og. If you pull the latest and look at og/validations.rb you will see the new implementation. I think it is much simpler. I would like to hear suggestions (esp. from Tom) how this could be further improved. I have only re-implemented validate_value and validate_format at the moment. Converting the rest of the macros is quite straightforward so I would like to ask for a volunteer to convert the rest of the validation methods (so I can work on other parts in Og). This is supposed to be a public project, so some input AND help from the community is required. An additional validation spec would be quite nice to have. thanks, George. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From nyarly at gmail.com Thu Mar 8 12:59:46 2007 From: nyarly at gmail.com (Judson Lester) Date: Thu, 8 Mar 2007 09:59:46 -0800 Subject: [Nitro] moving /spec-helper.rb to /spec/helper.rb [was: Og test cases and specs] Message-ID: <8905c87a0703080959w7828493dq227019bba2f72429@mail.gmail.com> Right. So you're suggesting a spec wrapper script instead of the conventional "spec spec/*"? I suppose the other possibility would be to do a C style if defined? wrapper within helper.rb, so that it's contents get executed exactly once regardless... which also seems a little wonky. Judson On 3/7/07, George Moschovitis wrote: > Dir[..].except(...) > > -g. > > On 3/8/07, Judson Lester wrote: > > On 3/7/07, George Moschovitis wrote: > > > it is easy to remove this file though... > > > > > > -g. > > > > How do you mean? > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > > -- > http://blog.gmosx.com > http://cull.gr > http://www.joy.gr > http://nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From james.britt at gmail.com Thu Mar 8 15:45:20 2007 From: james.britt at gmail.com (James Britt) Date: Thu, 08 Mar 2007 13:45:20 -0700 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: References: Message-ID: <45F075E0.8010602@gmail.com> George Moschovitis wrote: > This is supposed to be a public project, so some input AND help from > the community is required. An additional validation spec would be > quite nice to have. Is there a document that clearly explains the steps needed to contribute? * How to get the current source - How to get and install darcs if you don't already have it * How the source code is structured * How to run the current code without unwanted interference from currently installed Nitro/Og libs * How to write comments * Coding style * How to create a patch - specific commands - How to write change log comments * How to submit a patch * Current issues that are more probably deserving of attention than others The folks on the ruby-doc list have been helping to assemble a document like this for the documentation of the base Ruby code. There are people who want to help improve the Ruby docs, but they don't know where to begin or what, exactly, to do. The easier it is for such people, the more they'll want to do, and the more will get done. I set up a document describing the process on Google docs, and shared with a few people who were interested in helping to edit it. I then set up a cron task on ruby-doc.org to fetch the page every so often and republish it on ruby-doc.org. (It's hackish but it was fairly easy to do; if I had to think about a more elegant solution I would never have gotten around to it.) The best part is that someone has stepped up to help really fix up that document; a great example of bootstrapping community involvement. -- James Britt "Hackers will be expelled" - The Breakfast Club (1985) From nyarly at gmail.com Thu Mar 8 19:09:43 2007 From: nyarly at gmail.com (Judson Lester) Date: Thu, 8 Mar 2007 16:09:43 -0800 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: <45F075E0.8010602@gmail.com> References: <45F075E0.8010602@gmail.com> Message-ID: <8905c87a0703081609i21ebb824n8318b50d66e8028f@mail.gmail.com> Between those two posts, I'm inclined to ask: Is it worth instating a test-first policy? In other words: no new code without a failing spec? Granted, this can't be applied to pure refactorings, but for new behaviors... If nothing else, it makes it very clear the behavior you're trying to instate, and there's the possibility that another dev will look at the test and say "I think you want (say) STI" There's also the advantage that it makes sure that there's solid specs, and that old bugs don't creep back in. Judson On 3/8/07, James Britt wrote: > George Moschovitis wrote: > > > This is supposed to be a public project, so some input AND help from > > the community is required. An additional validation spec would be > > quite nice to have. > > Is there a document that clearly explains the steps needed to contribute? > > * How to get the current source > - How to get and install darcs if you don't already have it > > * How the source code is structured > > * How to run the current code without unwanted interference from > currently installed Nitro/Og libs > > * How to write comments > > * Coding style > > * How to create a patch > - specific commands > - How to write change log comments > > * How to submit a patch > > * Current issues that are more probably deserving of attention than others > > > The folks on the ruby-doc list have been helping to assemble a document > like this for the documentation of the base Ruby code. There are people > who want to help improve the Ruby docs, but they don't know where to > begin or what, exactly, to do. The easier it is for such people, the > more they'll want to do, and the more will get done. > > > I set up a document describing the process on Google docs, and shared > with a few people who were interested in helping to edit it. I then > set up a cron task on ruby-doc.org to fetch the page every so often and > republish it on ruby-doc.org. (It's hackish but it was fairly easy to > do; if I had to think about a more elegant solution I would never have > gotten around to it.) > > The best part is that someone has stepped up to help really fix up that > document; a great example of bootstrapping community involvement. > > > > -- > James Britt > > "Hackers will be expelled" > - The Breakfast Club (1985) > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From rob at robmela.com Thu Mar 8 20:37:16 2007 From: rob at robmela.com (Robert Mela) Date: Thu, 08 Mar 2007 20:37:16 -0500 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: <45F075E0.8010602@gmail.com> References: <45F075E0.8010602@gmail.com> Message-ID: <45F0BA4C.5070407@robmela.com> Just curious... why d'yall use darcs, anyway? James Britt wrote: > > Is there a document that clearly explains the steps needed to contribute? > > * How to get the current source > - How to get and install darcs if you don't already have it > > -------------- 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/20070308/f832d28f/attachment.vcf From nyarly at gmail.com Thu Mar 8 21:03:17 2007 From: nyarly at gmail.com (Judson Lester) Date: Thu, 8 Mar 2007 18:03:17 -0800 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: <8905c87a0703081609i21ebb824n8318b50d66e8028f@mail.gmail.com> References: <45F075E0.8010602@gmail.com> <8905c87a0703081609i21ebb824n8318b50d66e8028f@mail.gmail.com> Message-ID: <8905c87a0703081803u69258a17hcdd513b1ded1c6a9@mail.gmail.com> Oh, and I'm picking up that gauntlet, by the way. I need validate_unique. Plus some DRYness in there, for extra niceness. Bundle soon. Judson From nyarly at gmail.com Thu Mar 8 21:49:50 2007 From: nyarly at gmail.com (Judson Lester) Date: Thu, 8 Mar 2007 18:49:50 -0800 Subject: [Nitro] Validation specs Message-ID: <8905c87a0703081849w30deee29ga4ad7d611e1ae97b@mail.gmail.com> Moved spec-helper to spec/helper.rb Added spec/validation.rb Added validation_unique validation_related isn't working yet, but there's a spec for how I understand it to work. It would probably help if someone took a look to see if that's what validation_related is supposed to do. Judson -------------- next part -------------- A non-text attachment was scrubbed... Name: validation-spec.bndl Type: application/octet-stream Size: 40051 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070308/0987a0b1/attachment-0001.obj From vikingtux at gmail.com Thu Mar 8 23:51:14 2007 From: vikingtux at gmail.com (Alexandre Gravem) Date: Fri, 9 Mar 2007 01:51:14 -0300 Subject: [Nitro] Validation specs In-Reply-To: <8905c87a0703081849w30deee29ga4ad7d611e1ae97b@mail.gmail.com> References: <8905c87a0703081849w30deee29ga4ad7d611e1ae97b@mail.gmail.com> Message-ID: <40b05ebe0703082051ob6930ccv9f10d390dc99ea20@mail.gmail.com> I like this "test first" approach!! If you write a spec of the desired feature it's easier to contribute. And you can be sure that the code sent really works. I am hoping that the new site to be up so I can contribute with docs, since I am not secure enough to contribute with code. On 3/8/07, Judson Lester wrote: > > Moved spec-helper to spec/helper.rb > > Added spec/validation.rb > > Added validation_unique > > validation_related isn't working yet, but there's a spec for how I > understand it to work. It would probably help if someone took a look > to see if that's what validation_related is supposed to do. > > Judson > > _______________________________________________ > 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/20070309/140890ab/attachment.html From george.moschovitis at gmail.com Fri Mar 9 02:18:42 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 9 Mar 2007 09:18:42 +0200 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: <8905c87a0703081803u69258a17hcdd513b1ded1c6a9@mail.gmail.com> References: <45F075E0.8010602@gmail.com> <8905c87a0703081609i21ebb824n8318b50d66e8028f@mail.gmail.com> <8905c87a0703081803u69258a17hcdd513b1ded1c6a9@mail.gmail.com> Message-ID: > Oh, and I'm picking up that gauntlet, by the way. I need validate_unique. Great. > Plus some DRYness in there, for extra niceness. Yeah, perhaps you can refactor the initialization code. One idea is to support only one attribute per validation macro, but perhaps the extra flexibility is needed. -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Fri Mar 9 02:21:03 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 9 Mar 2007 09:21:03 +0200 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: <45F075E0.8010602@gmail.com> References: <45F075E0.8010602@gmail.com> Message-ID: such a document is clearly in need, especially for the new np.org site I am preparing. But this is another issue where someone from this list can help. There are people that know the procedure and are better thant me in writing english docs. Plus I can use the time to further work on Og. regards, George. > Is there a document that clearly explains the steps needed to contribute? > > * How to get the current source > - How to get and install darcs if you don't already have it > > * How the source code is structured > > * How to run the current code without unwanted interference from > currently installed Nitro/Og libs > > * How to write comments > > * Coding style > > * How to create a patch > - specific commands > - How to write change log comments > > * How to submit a patch > > * Current issues that are more probably deserving of attention than others -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Fri Mar 9 02:21:57 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 9 Mar 2007 09:21:57 +0200 Subject: [Nitro] Validation specs In-Reply-To: <8905c87a0703081849w30deee29ga4ad7d611e1ae97b@mail.gmail.com> References: <8905c87a0703081849w30deee29ga4ad7d611e1ae97b@mail.gmail.com> Message-ID: Many thanks, I will review the patch ASAP. -g. On 3/9/07, Judson Lester wrote: > Moved spec-helper to spec/helper.rb > > Added spec/validation.rb > > Added validation_unique > > validation_related isn't working yet, but there's a spec for how I > understand it to work. It would probably help if someone took a look > to see if that's what validation_related is supposed to do. > > Judson > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From george.moschovitis at gmail.com Fri Mar 9 02:23:11 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 9 Mar 2007 09:23:11 +0200 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: <45F0BA4C.5070407@robmela.com> References: <45F075E0.8010602@gmail.com> <45F0BA4C.5070407@robmela.com> Message-ID: We all like Haskell. No, seriously, darcs is a great *distributed* version management system. -g. On 3/9/07, Robert Mela wrote: > Just curious... why d'yall use darcs, anyway? > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From john at oxyliquit.de Fri Mar 9 02:58:20 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 09 Mar 2007 09:58:20 +0200 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: <45F0BA4C.5070407@robmela.com> References: <45F075E0.8010602@gmail.com> <45F0BA4C.5070407@robmela.com> Message-ID: Hi, > Just curious... why d'yall use darcs, anyway? well, despite some 'awry' things with darcs, the main reason for me to use darcs is 'ease of use', it's just dead simple. I'm glad Nitro introduced it to me and use it on all my current projects. (There is talk though, about switching to SVK for Nitro/Og in the next iteration.) Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From john at oxyliquit.de Fri Mar 9 02:58:19 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 09 Mar 2007 09:58:19 +0200 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: References: <45F075E0.8010602@gmail.com> <8905c87a0703081609i21ebb824n8318b50d66e8028f@mail.gmail.com> <8905c87a0703081803u69258a17hcdd513b1ded1c6a9@mail.gmail.com> Message-ID: Hi, > Yeah, perhaps you can refactor the initialization code. One idea is to > support only one attribute per validation macro, but perhaps the extra > flexibility is needed. I think only supporting one attribute is fine. I never use more, just for clarity in the code. Of course, this is just my opinion. :P Jo -- Feel the love http://pinkjuice.com/pics/ruby.png From nyarly at gmail.com Fri Mar 9 03:00:16 2007 From: nyarly at gmail.com (Judson Lester) Date: Fri, 9 Mar 2007 00:00:16 -0800 Subject: [Nitro] New implementation of Og Validations. (Help needed) In-Reply-To: References: <45F075E0.8010602@gmail.com> <8905c87a0703081609i21ebb824n8318b50d66e8028f@mail.gmail.com> <8905c87a0703081803u69258a17hcdd513b1ded1c6a9@mail.gmail.com> Message-ID: <8905c87a0703090000r45c253b8s6b799b25c3bf9748@mail.gmail.com> The bundle I sent uses a single method approach for validate_unique and validate_relation. value and format would be even easier to use for that. Still not sure about validate_relation, though. Judson On 3/8/07, George Moschovitis wrote: > > Oh, and I'm picking up that gauntlet, by the way. I need validate_unique. > > Great. > > > Plus some DRYness in there, for extra niceness. > > Yeah, perhaps you can refactor the initialization code. One idea is to > support only one attribute per validation macro, but perhaps the extra > flexibility is needed. > > -g. > > -- > http://blog.gmosx.com > http://cull.gr > http://www.joy.gr > http://nitroproject.org > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From nyarly at gmail.com Fri Mar 9 03:42:50 2007 From: nyarly at gmail.com (Judson Lester) Date: Fri, 9 Mar 2007 00:42:50 -0800 Subject: [Nitro] Contribution Guidelines Message-ID: <8905c87a0703090042k3f8bbb5cld1a4e00064cbf728@mail.gmail.com> I would have liked to see this went I got started with Og, so I'll write what I know. If Jo, Tom or George want to add to it, I'm not going to say anything. On 3/8/07, James Britt wrote: > * How to get the current source > - How to get and install darcs if you don't already have it Get darcs: http://darcs.net/DarcsWiki/CategoryBinaries Then: darcs get http://repo.nitroproject.org My quick caveat: darcs is a little testy. Expect to occassionally trash your local repo and start over. Keep your repo current with frequent pulls, and work in small, short intervals. > * How the source code is structured Within the repo there's three important directories: nitro, og and raw. There's a legacy directory called "glue" which was essentially for common code. There's a direction of the project to reduce and remove the glue files, either by finding their proper place within one of the subprojects or promote them into Tom Sawyer's Facets library, upon with Nitro depends strongly. > * How to run the current code without unwanted interference from > currently installed Nitro/Og libs The easiest way is to either set RUBYLIB, or use the -I option to ruby. Myself, I've got repo.nitroproject.org/og added to my RUBYLIB in my profile. Which is certainly an incentive to make sure it stays reasonably stable. > * How to write comments The preference is for rdoc style comments, with examples and explanation of arguments ahead of all API methods. Honestly, anyone looking to be helpful but less than confident about the code could do well by writing rdoc comments. > * Coding style Two space indents. No indent except for modules that the actually classes or modules being defined in the file. In other words: module Nitro class Feature def method(arg1, arg2) end end end " is preferred over ' > > * How to create a patch > - specific commands > - How to write change log comments The command you'll want is "darcs record" For most things, the short entry is enough. You might want to use a common prefix for related patches, as darcs does provide a feature called "spontaneous branches" that's potentially interesting. > * How to submit a patch darcs send -o something.bndl Attach the resulting bundle file to an email to the list, and George will apply it to the main repo. > * Current issues that are more probably deserving of attention than others I'll leave this area mostly up to George. I know that we're moving to using rspec over Test::Unit, so the old test cases need to be converted to specs, and need to be updated. If you're considering developing something, make sure there's a spec for it first. If you're up to it, writing a spec for a feature that you'd like to see is a really good way to set it up to get written. > James Britt James, thanks for laying out specific questions to cue the answers. Judson From george.moschovitis at gmail.com Fri Mar 9 04:20:00 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 9 Mar 2007 11:20:00 +0200 Subject: [Nitro] Contribution Guidelines In-Reply-To: <8905c87a0703090042k3f8bbb5cld1a4e00064cbf728@mail.gmail.com> References: <8905c87a0703090042k3f8bbb5cld1a4e00064cbf728@mail.gmail.com> Message-ID: Once again thanks for this nice post. I will use this as the basis for a page in the new np.org site. -g. On 3/9/07, Judson Lester wrote: > I would have liked to see this went I got started with Og, so I'll > write what I know. If Jo, Tom or George want to add to it, I'm not > going to say anything. > > On 3/8/07, James Britt wrote: > > * How to get the current source > > - How to get and install darcs if you don't already have it > > Get darcs: > http://darcs.net/DarcsWiki/CategoryBinaries > > Then: > darcs get http://repo.nitroproject.org > > My quick caveat: darcs is a little testy. Expect to occassionally > trash your local repo and start over. Keep your repo current with > frequent pulls, and work in small, short intervals. > > > * How the source code is structured > > Within the repo there's three important directories: nitro, og and > raw. There's a legacy directory called "glue" which was essentially > for common code. There's a direction of the project to reduce and > remove the glue files, either by finding their proper place within one > of the subprojects or promote them into Tom Sawyer's Facets library, > upon with Nitro depends strongly. > > > * How to run the current code without unwanted interference from > > currently installed Nitro/Og libs > > The easiest way is to either set RUBYLIB, or use the -I option to > ruby. Myself, I've got repo.nitroproject.org/og added to my RUBYLIB > in my profile. Which is certainly an incentive to make sure it stays > reasonably stable. > > > * How to write comments > > The preference is for rdoc style comments, with examples and > explanation of arguments ahead of all API methods. Honestly, anyone > looking to be helpful but less than confident about the code could do > well by writing rdoc comments. > > > * Coding style > > Two space indents. No indent except for modules that the actually > classes or modules being defined in the file. In other words: > > module Nitro > class Feature > def method(arg1, arg2) > end > end > end > > " is preferred over ' > > > > > * How to create a patch > > - specific commands > > - How to write change log comments > > The command you'll want is "darcs record" > For most things, the short entry is enough. You might want to use a > common prefix for related patches, as darcs does provide a feature > called "spontaneous branches" that's potentially interesting. > > > * How to submit a patch > > darcs send -o something.bndl > Attach the resulting bundle file to an email to the list, and George > will apply it to the main repo. > > > * Current issues that are more probably deserving of attention than others > > I'll leave this area mostly up to George. I know that we're moving to > using rspec over Test::Unit, so the old test cases need to be > converted to specs, and need to be updated. If you're considering > developing something, make sure there's a spec for it first. If > you're up to it, writing a spec for a feature that you'd like to see > is a really good way to set it up to get written. > > > James Britt > > James, thanks for laying out specific questions to cue the answers. > > Judson > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From manveru at weez-int.com Fri Mar 9 05:59:14 2007 From: manveru at weez-int.com (Michael Fellinger) Date: Fri, 09 Mar 2007 19:59:14 +0900 Subject: [Nitro] Isolated specs bundle In-Reply-To: References: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> Message-ID: On Tue, 06 Mar 2007 16:32:56 +0900, George Moschovitis wrote: > Judson, > > if possible please break your specs in more specify blogs so that we > get a better (more descriptive) implementation. For example: > > specify "should provide standard og features" do > > is too general and could possibly be splite in more blocks. > Please note that you can nest the contexts... which gives you something like "Og PostgreSQL Model should create_with" for: context "Og" do context "PostgreSQL" do context "Model" do specify "should create_with" do user = User.create_with :age => 42 user.age.should == 42 end end end end nothing big, just wanted to point it out (one can generate nicer docs from the specs afterwards and they just look better on errors) ^ manveru > thanks for your work, > George. > > > PS: btw, please use attr_accessor instead of property! > > > > From george.moschovitis at gmail.com Fri Mar 9 08:21:06 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Fri, 9 Mar 2007 15:21:06 +0200 Subject: [Nitro] Javascript quote Message-ID: Dear devs, can anyone point me to a piece of javascript code to implement post quoting in a fourm software? thanks in advance, George. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From john at oxyliquit.de Fri Mar 9 09:05:25 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Fri, 09 Mar 2007 16:05:25 +0200 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: References: <45F075E0.8010602@gmail.com> <45F0BA4C.5070407@robmela.com> Message-ID: Hi, > We all like Haskell. No, seriously, darcs is a great *distributed* > version management system. actually quite the opposite, I _loathe_ Haskells compiling speed. With my little computer Haskell almost needed 2 days! to fully compile (because it broke in the middle once). Compiling darcs was no fun either. That said, I know nothing else of Haskell at all so this statement is quite uneducated. ;) Jo From Reid.Thompson at ateb.com Fri Mar 9 11:51:15 2007 From: Reid.Thompson at ateb.com (Reid Thompson) Date: Fri, 09 Mar 2007 11:51:15 -0500 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: References: <45F075E0.8010602@gmail.com> <45F0BA4C.5070407@robmela.com> Message-ID: <1173459075.2171.15.camel@localhost> On Fri, 2007-03-09 at 16:05 +0200, Jonathan Buch wrote: > Hi, > > > We all like Haskell. No, seriously, darcs is a great *distributed* > > version management system. > > actually quite the opposite, I _loathe_ Haskells compiling speed. With > my little computer Haskell almost needed 2 days! to fully compile > (because it broke in the middle once). Compiling darcs was no fun either. > How 'little` is your computer? From nyarly at gmail.com Fri Mar 9 13:17:51 2007 From: nyarly at gmail.com (Judson Lester) Date: Fri, 9 Mar 2007 10:17:51 -0800 Subject: [Nitro] Isolated specs bundle In-Reply-To: References: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> Message-ID: <8905c87a0703091017s69c2c627s8bc16090344de7a1@mail.gmail.com> Is there a point to that other than the output? Because you can just as easily do context "Og PostgreSQL Model" do end It does bring up the question that lingers with me: is there a more flexible way to test different stores? I suppose creating a bunch of files with "config=:storename" and then requiring them, a la -rdebug or whatnot. I just think it'd be extra cool to be able to run the specs against all the DB types that you have ready for it. Judson On 3/9/07, Michael Fellinger wrote: > On Tue, 06 Mar 2007 16:32:56 +0900, George Moschovitis > wrote: > > > Judson, > > > > if possible please break your specs in more specify blogs so that we > > get a better (more descriptive) implementation. For example: > > > > specify "should provide standard og features" do > > > > is too general and could possibly be splite in more blocks. > > > > Please note that you can nest the contexts... > which gives you something like "Og PostgreSQL Model should create_with" > for: > > context "Og" do > context "PostgreSQL" do > context "Model" do > specify "should create_with" do > user = User.create_with :age => 42 > user.age.should == 42 > end > end > end > end > > nothing big, just wanted to point it out (one can generate nicer docs from > the specs afterwards and they just look better on errors) > > ^ manveru > > > thanks for your work, > > George. > > > > > > PS: btw, please use attr_accessor instead of property! > > > > > > > > > > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From nyarly at gmail.com Fri Mar 9 13:27:23 2007 From: nyarly at gmail.com (Judson Lester) Date: Fri, 9 Mar 2007 10:27:23 -0800 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: References: <45F075E0.8010602@gmail.com> <45F0BA4C.5070407@robmela.com> Message-ID: <8905c87a0703091027q76ceb42crc33daf6e42e50723@mail.gmail.com> On 3/9/07, Jonathan Buch wrote: > Hi, > > > We all like Haskell. No, seriously, darcs is a great *distributed* > > version management system. I continue to question the "great" in that statement. For all the "intelligent patch algebra," my short experience with darcs is that it falls down in some pretty basic requirements of a CMS. That any pull or send could result in needing to discard work and start over is not really satisfactory. >From the Darcs wiki: "Also, very large conflicts and complex conflicts can cause darcs to use an expontential amount of CPU power" - which my experience requires two devs a day of moderate work to accomplish. Also, while the option to use an external merge tool exists, the darcs docco advises that you not use it (and instead deal with ambiguously marked up source files) for pulls. > actually quite the opposite, I _loathe_ Haskells compiling speed. With > my little computer Haskell almost needed 2 days! to fully compile > (because it broke in the middle once). Compiling darcs was no fun either. > > That said, I know nothing else of Haskell at all so this statement is > quite uneducated. ;) > > Jo > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > From brian.william.davis at gmail.com Fri Mar 9 19:35:02 2007 From: brian.william.davis at gmail.com (Brian Davis) Date: Fri, 9 Mar 2007 16:35:02 -0800 Subject: [Nitro] Unintuitive Og modeling In-Reply-To: References: <20070301210422.4d33ad25@localhost.localdomain> Message-ID: <20070309163502.613b81f9@localhost.localdomain> On Fri, 2 Mar 2007 10:57:58 +0200 "George Moschovitis" wrote: > I think your suggested solution is reasonable. A problem is that it is > backwards incompatible but I prefer something that works. I am > wondering if Jonathan or Judson could provide a patch for this (as I > am working on Nitro stuff at the moment). > > thanks, > George. > > > On 3/2/07, Brian Davis wrote: > > NOTE: I posted this at the Google Groups interface, but my message > > has languished in the ether. > > > > I spoke with Kashia earlier about this and he encouraged me to post > > this to the mailing list. > > > > Consider the following model definition: > > -------------------- > > class User > > ... > > many_to_many :buddies, User, :foreign_name => :buddies > > many_to_many :buddies_pending_confirmation, User, :foreign_name > > => :buddies_requested > > many_to_many :buddies_requested, User, :foreign_name > > => :buddies_pending_confirmation > > ... > > end > > -------------------- > > > > This is a reflexive join with several distinct relationships that > > happen to join to objects of the same class. My issue is that, with > > Og, only one join table is created to model *all* of these > > relationship: og_user_user. Because of this, the relationships are > > essentially mirrored. Thus, if a user is added to my > > 'buddies_pending_confirmation' queue, they also appear in my > > 'buddies' and 'buddies_requested' lists, although this is precisely > > the opposite of the intended behavior. > > > > Kashia showed me a hack that circumvents this behavior (by defining > > a self-join class for each of the relationships above), but we both > > found it to be, well, a hack. It lacked the clarity and > > intuitiveness of the code above. > > > > My suggestion, then, is to perhaps name join tables not by their > > associated types, but by their given label (the first argument to > > 'many_to_many'). Thus, my 'og_user_user' table right now would > > actually be three tables, 'og_user_buddies', > > 'og_user_buddies_pending_confirmation' and > > 'og_user_buddies_requested'. > > > > Please let me know if this is unreasonable, stupid or unclear. Also, > > if there's something I'm just altogether missing, set me straight. > > > > Thanks, > > > > Brian > > _______________________________________________ > > Nitro-general mailing list > > Nitro-general at rubyforge.org > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > Attached is a bundle I threw together during my lunch break. Please excuse me, as I'm new with Darcs and couldn't test the spec myself (I get a number of errors about the spec being unable to locate 'glue'). If this is inappropriate or unnecessary, please let me know. If nothing else, hopefully this will serve to demonstrate the issue I've been having with Og relations and how my proposed fix could help remedy things. Also attached is the spec itself, in case I muddled the Darcs procedure. Regards, Brian -- Brian Davis Project Manager FreezeCrowd, Inc. -------------- next part -------------- A non-text attachment was scrubbed... Name: many_to_many.rb Type: application/x-ruby Size: 2198 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070309/edd1cab6/attachment-0001.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: many_to_many-spec.bndl Type: application/octet-stream Size: 32548 bytes Desc: not available Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070309/edd1cab6/attachment-0001.obj From matt at kiatoa.com Fri Mar 9 23:35:16 2007 From: matt at kiatoa.com (Matthew Welland) Date: Fri, 9 Mar 2007 21:35:16 -0700 Subject: [Nitro] Semi-OT: Re: New implementation of Og Validations. (Help needed) In-Reply-To: <8905c87a0703091027q76ceb42crc33daf6e42e50723@mail.gmail.com> References: <8905c87a0703091027q76ceb42crc33daf6e42e50723@mail.gmail.com> Message-ID: <200703092135.16585.matt@kiatoa.com> On the subject of SCM's. After experimenting with as many of the various options available as I could I settled on Monotone. The initial ramp up is a bit steeper than darcs but it has been rock solid for my usage. There are some pretty big users of it (openembedded for one) and it seems to be improving pretty rapidly. Just my $0.02. Matt -- On Friday 09 March 2007 11:27, Judson Lester wrote: > On 3/9/07, Jonathan Buch wrote: > > Hi, > > > > > We all like Haskell. No, seriously, darcs is a great *distributed* > > > version management system. > > I continue to question the "great" in that statement. For all the > "intelligent patch algebra," > my short experience with darcs is that it falls down in some pretty > basic requirements of a CMS. That any pull or send could result in > needing to discard work and start over is not really satisfactory. > > >From the Darcs wiki: "Also, very large conflicts and complex conflicts > > can cause darcs to use an expontential amount of CPU power" - which my > experience requires two devs a day of moderate work to accomplish. > > Also, while the option to use an external merge tool exists, the darcs > docco advises that you not use it (and instead deal with ambiguously > marked up source files) for pulls. > > > actually quite the opposite, I _loathe_ Haskells compiling speed. With > > my little computer Haskell almost needed 2 days! to fully compile > > (because it broke in the middle once). Compiling darcs was no fun > > either. > > > > That said, I know nothing else of Haskell at all so this statement is > > quite uneducated. ;) > > > > 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://www.kiatoa.com, a self-governing site where *you* can be the boss! You make and choose the stories and the classifieds are always free. Also, many "best of" polls. Come join in the ballot stuffing! From george.moschovitis at gmail.com Sat Mar 10 03:05:58 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 10 Mar 2007 10:05:58 +0200 Subject: [Nitro] Unintuitive Og modeling In-Reply-To: <20070309163502.613b81f9@localhost.localdomain> References: <20070301210422.4d33ad25@localhost.localdomain> <20070309163502.613b81f9@localhost.localdomain> Message-ID: Brian, thanks for your first patch ;-) I added this to the repo. Hopefully someone can work on this and make this spec pass. -g. PS: there are still missing validations in the new implementation. It is very easy to contribute here (just copy/update code from the old files - still included in the repo, move everything to og/validation.rb so we can get rid of glue/validation.rb) On 3/10/07, Brian Davis wrote: > On Fri, 2 Mar 2007 10:57:58 +0200 > "George Moschovitis" wrote: > > > I think your suggested solution is reasonable. A problem is that it is > > backwards incompatible but I prefer something that works. I am > > wondering if Jonathan or Judson could provide a patch for this (as I > > am working on Nitro stuff at the moment). > > > > thanks, > > George. > > > > > > On 3/2/07, Brian Davis wrote: > > > NOTE: I posted this at the Google Groups interface, but my message > > > has languished in the ether. > > > > > > I spoke with Kashia earlier about this and he encouraged me to post > > > this to the mailing list. > > > > > > Consider the following model definition: > > > -------------------- > > > class User > > > ... > > > many_to_many :buddies, User, :foreign_name => :buddies > > > many_to_many :buddies_pending_confirmation, User, :foreign_name > > > => :buddies_requested > > > many_to_many :buddies_requested, User, :foreign_name > > > => :buddies_pending_confirmation > > > ... > > > end > > > -------------------- > > > > > > This is a reflexive join with several distinct relationships that > > > happen to join to objects of the same class. My issue is that, with > > > Og, only one join table is created to model *all* of these > > > relationship: og_user_user. Because of this, the relationships are > > > essentially mirrored. Thus, if a user is added to my > > > 'buddies_pending_confirmation' queue, they also appear in my > > > 'buddies' and 'buddies_requested' lists, although this is precisely > > > the opposite of the intended behavior. > > > > > > Kashia showed me a hack that circumvents this behavior (by defining > > > a self-join class for each of the relationships above), but we both > > > found it to be, well, a hack. It lacked the clarity and > > > intuitiveness of the code above. > > > > > > My suggestion, then, is to perhaps name join tables not by their > > > associated types, but by their given label (the first argument to > > > 'many_to_many'). Thus, my 'og_user_user' table right now would > > > actually be three tables, 'og_user_buddies', > > > 'og_user_buddies_pending_confirmation' and > > > 'og_user_buddies_requested'. > > > > > > Please let me know if this is unreasonable, stupid or unclear. Also, > > > if there's something I'm just altogether missing, set me straight. > > > > > > Thanks, > > > > > > Brian > > > _______________________________________________ > > > Nitro-general mailing list > > > Nitro-general at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/nitro-general > > > > > > > > > Attached is a bundle I threw together during my lunch break. Please > excuse me, as I'm new with Darcs and couldn't test the spec myself (I > get a number of errors about the spec being unable to locate 'glue'). > If this is inappropriate or unnecessary, please let me know. If nothing > else, hopefully this will serve to demonstrate the issue I've been > having with Og relations and how my proposed fix could help remedy > things. > > Also attached is the spec itself, in case I muddled the Darcs > procedure. > > Regards, > > Brian > > -- > Brian Davis > > Project Manager > FreezeCrowd, Inc. > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From james.britt at gmail.com Sat Mar 10 09:30:55 2007 From: james.britt at gmail.com (James Britt) Date: Sat, 10 Mar 2007 07:30:55 -0700 Subject: [Nitro] Javascript quote In-Reply-To: References: Message-ID: <45F2C11F.90107@gmail.com> George Moschovitis wrote: > Dear devs, > > can anyone point me to a piece of javascript code to implement post > quoting in a fourm software? What do you mean by "post quoting"? Automatically inserting content from one post when someone is writing a reply to that quote? > > thanks in advance, > George. > -- James Britt http://www.ruby-doc.org - Ruby Help & Documentation http://www.rubystuff.com - The Ruby Store for Ruby Stuff http://beginningruby.com - Beginning Ruby: The Online Book From george.moschovitis at gmail.com Sat Mar 10 11:04:30 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sat, 10 Mar 2007 18:04:30 +0200 Subject: [Nitro] Javascript quote In-Reply-To: <45F2C11F.90107@gmail.com> References: <45F2C11F.90107@gmail.com> Message-ID: yeap, and prepending a prefix (typically '>') to each line. -g. On 3/10/07, James Britt wrote: > George Moschovitis wrote: > > Dear devs, > > > > can anyone point me to a piece of javascript code to implement post > > quoting in a fourm software? > > What do you mean by "post quoting"? > > Automatically inserting content from one post when someone is writing a > reply to that quote? > > > > > > thanks in advance, > > George. > > > > > -- > James Britt > > http://www.ruby-doc.org - Ruby Help & Documentation > http://www.rubystuff.com - The Ruby Store for Ruby Stuff > http://beginningruby.com - Beginning Ruby: The Online Book > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From brian.william.davis at gmail.com Sat Mar 10 11:19:32 2007 From: brian.william.davis at gmail.com (Brian Davis) Date: Sat, 10 Mar 2007 08:19:32 -0800 Subject: [Nitro] Javascript quote In-Reply-To: <45F2C11F.90107@gmail.com> References: <45F2C11F.90107@gmail.com> Message-ID: <20070310081932.1e4e33db@localhost.localdomain> On Sat, 10 Mar 2007 07:30:55 -0700 James Britt wrote: > George Moschovitis wrote: > > Dear devs, > > > > can anyone point me to a piece of javascript code to implement post > > quoting in a fourm software? > > What do you mean by "post quoting"? > > Automatically inserting content from one post when someone is writing > a reply to that quote? > > > > > > thanks in advance, > > George. > > > > If this is the intent, then Eve Community seems to have a good quoting mechanism. Check out the boards at Ars Technica[1] or Eve Community's[2] home page for examples. To be honest, though, it doesn't seem too hard... Just wrap the content of a post in a
and harvest it with the "reply with quote" button (or whatever your aim is). I think Eve Community also has selection quoting, where, if you select a block of text and then hit "reply with quote", only that block is harvested and prepended to your reply. [1] http://arstechnica.com/ [2] http://support.evecommunity.com/eve -- Brian Davis Project Manager FreezeCrowd, Inc. From antoniolo at gmail.com Sat Mar 10 21:34:46 2007 From: antoniolo at gmail.com (Antoniolo) Date: Sat, 10 Mar 2007 23:34:46 -0300 Subject: [Nitro] many to many - advanced relationships In-Reply-To: <20070310081932.1e4e33db@localhost.localdomain> References: <45F2C11F.90107@gmail.com> <20070310081932.1e4e33db@localhost.localdomain> Message-ID: <001801c76385$e282c690$a78853b0$@com> Hi Nitro-People :) I've been developing a game server app and I'd really like to upgrade my models from active-record to Og. I'm fascinated with Nitro and specially Og :). However, before doing that, I only need to know how to manage advanced many-to-many relationships, I mean, a table not only with foreign ids, but also with some fields. In active-record, we use has_many/through(since many_to_many cannot handle that). Is there a similar alternative in Og? Sorry for asking a newbie question, but I tried to find an entry about that ... Cheers, Antonio From george.moschovitis at gmail.com Sun Mar 11 03:33:00 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 11 Mar 2007 09:33:00 +0200 Subject: [Nitro] many to many - advanced relationships In-Reply-To: <001801c76385$e282c690$a78853b0$@com> References: <45F2C11F.90107@gmail.com> <20070310081932.1e4e33db@localhost.localdomain> <001801c76385$e282c690$a78853b0$@com> Message-ID: Welcome to this list, Yeah, this more or less works like AR, ie: class Article joins_many :first_join, Category, :through => ArticleToCategory end for more examples check out, og/test/og/tc_join.rb regards, George. On 3/11/07, Antoniolo wrote: > Hi Nitro-People :) > > > I've been developing a game server app and I'd really like to upgrade my > models from active-record to Og. I'm fascinated with Nitro and specially Og > :). However, before doing that, I only need to know how to manage advanced > many-to-many relationships, I mean, a table not only with foreign ids, but > also with some fields. > > In active-record, we use has_many/through(since many_to_many cannot handle > that). Is there a similar alternative in Og? > > > Sorry for asking a newbie question, but I tried to find an entry about that > ... > > > > Cheers, Antonio > > _______________________________________________ > Nitro-general mailing list > Nitro-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/nitro-general > -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From d454d at web.de Sun Mar 11 03:46:07 2007 From: d454d at web.de (Stephan Mueller) Date: Sun, 11 Mar 2007 08:46:07 +0100 Subject: [Nitro] Router.strip_path and Nitro 0.41.0? Message-ID: <20070311074607.GC1429@X.thorsten.dyndns.org> Hi! in earlier versions of nitro Router had a method strip_path to adjust, well, the path. ;) In 0.41.0 this method seems to be gone. Is there a way to get it back or to work around it? Thanks and cheers, Steph. From george.moschovitis at gmail.com Sun Mar 11 04:26:26 2007 From: george.moschovitis at gmail.com (George Moschovitis) Date: Sun, 11 Mar 2007 10:26:26 +0200 Subject: [Nitro] Using ruby-openid/ruby-yadis w/o ruby gems Message-ID: Dear devs, I am trying to use the ruby-openid/ruby-yadis gems without ruby gems, ie I just copied the lib files in a local lib directory (and placed this in the LOAD_PATH). When running the application I get the following error: /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:188:in `remove_method': method `description=' not defined in Gem::Specification (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb: 188:in `overwrite_accessor' from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb: 331 from /usr/local/lib/site_ruby/1.8/rubygems.rb:502 from ./lib/openid/discovery.rb:7 from ./lib/openid/consumer.rb:7 from ./lib/openid.rb:2 The offending code is: require "openid/util" require "openid/service" require "openid/parse" # try and use the yadis gem, falling back to system yadis begin require 'rubygems' <-------------------------------- HERE ! require_gem 'ruby-yadis', ">=0.3.3" rescue LoadError require "yadis" end I am wondering if any rubygems guru can provide a solution. thanks in advance, -g. -- http://blog.gmosx.com http://cull.gr http://www.joy.gr http://nitroproject.org From william.full.moon at gmail.com Sun Mar 11 05:10:11 2007 From: william.full.moon at gmail.com (* William) Date: Sun, 11 Mar 2007 20:10:11 +1100 Subject: [Nitro] Isolated specs bundle In-Reply-To: <8905c87a0703091017s69c2c627s8bc16090344de7a1@mail.gmail.com> References: <8905c87a0703051659r4804b5ddlb88281e2267207de@mail.gmail.com> <8905c87a0703091017s69c2c627s8bc16090344de7a1@mail.gmail.com> Message-ID: <006c01c763bd$17cb0ba0$0301a8c0@ghostgum> Hi there ... I would love to support this comment. This falls into my peculiar want, to manage stores with a 'database' layer that is neutral about implementation, etc. j>> is there a more flexible way to test different stores? I ... j>> I just think it'd be extra cool to be able to run the specs j>> against all the DB types that you have ready for it. In fact, the idea in my mind is access to 'non-Og' tables (when asked) at some time. That will have to wait while I build my income stream. I am looking forward to the up coming release and a stable wiki (or docs) area. I found the best way in for us part-timers is to describe what is going on. I can also support the 'separation' of nitro-independent Og. Not every app -- and not all Nitro apps -- that are possible are 100% web based, and 'should' not be in some cases. Some commercial users are very sensitive about what it "connected" to the web. There are big opportunities for Og based "consumers" and "providers". Aloha, Will Regards, William, MBA, B.Math, STI, NLP MP _My_Bright_Ideas__________________________________________abn:77425560110_ "You must BE the change you want." ~ Gandhi Success Coaching http://adroit-process.blogspot.com ph/sms: 041-476-1217 (?2007) Information intended for direct recipient(s) and mutually agreed correspondents. -----Original Message----- From: nitro-general-bounces at rubyforge.org [mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Judson Lester Sent: Saturday, 10 March 2007 05:18 To: General discussion about Nitro Subject: Re: [Nitro] Isolated specs bundle Importance: Low Is there a point to that other than the output? Because you can just as easily do context "Og PostgreSQL Model" do end It does bring up the question that lingers with me: is there a more flexible way to test different stores? I suppose creating a bunch of files with "config=:storename" and then requiring them, a la -rdebug or whatnot. I just think it'd be extra cool to be able to run the specs against all the DB types that you have ready for it. Judson -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.8/714 - Release Date: 08-Mar-2007 10:58 From antoniolo at gmail.com Sun Mar 11 06:51:14 2007 From: antoniolo at gmail.com (Antoniolo) Date: Sun, 11 Mar 2007 07:51:14 -0300 Subject: [Nitro] RES: many to many - advanc