May 2007 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Thu May 3 15:11:57 EDT 2007
Ending: Wed May 30 16:25:50 EDT 2007
Messages: 9

• [Facets] Facets 2.0 Home Stretch   Trans
• [Facets] Facets 2.0 Home Stretch   Trans
• [Facets] Unique Names vs Uniform Names Unique names provide maximum independence. This allows for greater flexability in mixing and matching tools to requirements. However they require greater familiarity b/c various names must be remembered. In addition, this puts pressure on each package to only contain files that partake in a more cohesive application. In this case, parts of Facets might end-up in packages such as: kickstand (additions to standard library) annotate (annotations) taopoint (aop library) fileshell (file tools) freeload (net-based require and module tools) comrade (command line tools) magicdot (functor) The names are light and entertainting, but their usage is not immediately evident just by the names. Of course, we can use names that are less entertaining and more to the point, such as "cliutils" instead of "comrade". But this doesn't change much as far as library usage. While it is easier to recognize for what it is, it likewise looses brandability. Gogin further, uniform names allow a large support library like Facets to be broken down into categories. This makes them more convenient in that they are easier to recall. Plus the files within these catagories do not neccessiarily need to be as cohesive. Facets categories could be: facets-core facets-meta facets-file facets-math facets-cli facets-aop facets-ann facets-mix facets-struct facets-open facets-misc Most of these are fairly self-explanitory. It is interesting to note that one of the categories is so small and cohesive that it isn't really a category at all, but rather has the feel of an independent library (namely 'ann'). Indeed, if we continued to break down these categories further, each part would eventually fall out as it's own fully independent library --for example: ansicode and multition. But that would entail a huge set of libraries, each of which seems too small to fully warrant the many packages. One of the downsides of categorization is that pressure for cohesion lies between the whole library, not just the pacakged parts. Clearly it is expected that every part of Facets will work well with the rest. In addition, marketing/branding is hurt since there are no coined names to "sell". We have only "Facets", which is good in itself, but it's not well directed to specific problems. Someone in the market for a CLI tool will not be as easily taken with a lib called Facets-CLI, since it suggests the "baggage" of the other Facets tools (even if it is not necessarily the case). Unique vs Uniform   Trans
• [Facets] Unique Names vs. Uniform Names   Trans
• [Facets] Unique Names vs. Uniform Names   Trans
• [Facets] Unique Names vs. Uniform Names   Trans
• [Facets] Facets 2.0 Home Stretch   Trans
• [Facets] Facets 2.0 Home Stretch   Trans
• [Facets] [ facets-Bugs-10561 ] Dictionary#delete_if does not yield iterated keys/values to block   noreply at rubyforge.org

Last message date: Wed May 30 16:25:50 EDT 2007
Archived on: Wed May 30 16:25:53 EDT 2007

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...