From transfire at gmail.com Sat Jan 27 08:49:04 2007 From: transfire at gmail.com (TRANS) Date: Sat, 27 Jan 2007 08:49:04 -0500 Subject: [Facets] [ANN] Facets 1.8 RC Message-ID: <4b6f054f0701270549g32666ec2s3f3bcee9842b5a51@mail.gmail.com> Hi-- Wooh! It's been a long time since I made a release of Facets. Too long in fact --the tiny version made it all the way up 191 before I tagged it 1.8! Facets continues to mature, improving existing code and adding great new features. Have fun shifting thru this Changelog! And as always thanks to everyone who has contributed (knowingly and unknowingly). Here's the change log summary (in order from newest to oldest): 1.8 * added buildingblock.rb, replaced builderobject.rb * adjust require for "yored" files * HtmlBuilder and XMLBuilder aer now based on BuildingBlock * bug fix for command.rb * minor improvements to basic object (object_self to access kernel methods) * ostuct adjustment, use #instance_delegate to get underneth the open access * module/include_as is now based on module/namespace (thanks Pit!) * minor adjustments to methods for (class< NOTE: I'm corss posting this to Nitro list. if you would like to comment on it from that list please sign up for the Facets mailing list: http://rubyforge.org/mailman/listinfo/facets-universal. *** Shortly (once the new 1.8 has settled down a bit) I will tag Facets as 1.9 and work on it as a development version toward 2.0. I have some significant plans ahead for the 2.0 series. Here's waht it the works: * major code audit. i plan sift through most, if not all of code and make various decsions --is it even worth having, does the implementation need improvements, how about the docs, is it tested well enough, etc. and try to fix as much as possible in that regard * get rid of the self/ folders. i've come to the conclusion that the odds of a clash between an instance method and class method are low enough that it doesnt really matter. and when it does happen it's usually b/c there is a relationship between the methods -- so it's not big deal if you happen to get two methods for the require of one. this is how punctuated methods (!, ?, =) work too. * i want to get rid of the facet/ redirect folder (this is the one that redirects everything back to facets/core or facets/more). I could do this by merging core and more. into a single facets/ lib, but that would be harder to manage. howerver it's not quite as it seems b/c.... * i would like to give each more lib (or in some cases, closely related libs) their own project folder. in doing so, each can have it's own versioning and each can be packaged and distributed individually. of course, i still want to offer the full facets package too. so i have to figure out a reasonable way to have both. I've considered just allowing the subpackages to live in facets lib/ dir. Ie. facets/ ProjectInfo lib/ annotations/ ProjectInfo lib/ facets/ ann.rb then when using facets, require 'facets' would add to the $LOAD_PATH, eg $LOAD_PATH << 'facets/lib/annotations/lib'. but i'm not sure how good an idea this is. obviously it burdens the require system (which gems does too btw) and i'm not sure how well it will play with gems actually. any other ideas for how to do this in a DRY manner? any other suggestions for the future Facets 2.0 are very very welcome. thanks, T. From transfire at gmail.com Wed Jan 31 05:10:49 2007 From: transfire at gmail.com (TRANS) Date: Wed, 31 Jan 2007 05:10:49 -0500 Subject: [Facets] Facets 1.8.8 Message-ID: <4b6f054f0701310210n433cca4u3c9f1bba3ea2ce92@mail.gmail.com> Facets 1.8.8 just hit the rubyforge server. This is a second release candidate. T.