waves / edge Goto Github PK

Looked awful copy-pasted, so I'm linking to the gist:

http://gist.github.com/187008

The Accept[..] headers allow defining relative priorities for their contents. For both Requested and Accept, we currently order the types in parsing, but the order is not used in matching. Matching still only follows the normal last-definition semantics. This should possibly be fixed, but it may be prohibitively expensive (N*M matches)?

Cassandra, as a gem name, is now being used by something else. We need to give Cassandra a new gem name and make sure it is installable and documented.

lib/waves/ext/object.rb line 8 ...

I'm currently up through the 'helpers' directory. The basic idea is to stick to commenting the basic purpose of classes or methods and leave the expository stuff (tutorials, long explanations with examples, etc.) to external content (the Web site, wiki, etc.). A lot of the docs are already fairly decent, so it is mostly just added / tweaking.

I've added a variety of form helpers for Hoshi-based views, but these need to have some tutorial-style docs, sample apps, and tests. Also, some helpers haven't yet been coded (such as date).

Also: is it ready to be used?

Right now, Hoshi is a working prototype, but needs to support / validate all the various different doctypes, as well as some of the quirkier things in HTML 4, like the fact that you can't have a self-closing script tag, or that link tags MUST be self-closing (can't have ).

Autocode usage in Sequel orm layer and classic foundation overrides certain applications default controller methods and its very hard to debug. Will attach an example soon.

I've tried this on literally every Ruby platform I've had available. No matter what, I cannot get waves to generate a new project:

-- Sample output --

daenerys% waves generate jaunt
** Waves 0.9.3 **
Usage: waves [-otn]
    --help                       Show this message
    -o, --orm=ORM                    Select an ORM (currently supported: active_record,   filebase, sequel, data_mapper )
    -t, --template=TEMPLATE          Select a template for your app (options: classic, compact).
    -n, --name                       Select a name for the application. Use only letters, numbers, dashes, or underscores.

and

daenerys% waves -o sequel jaunt
** Waves 0.9.3 **
Usage: waves [ generate | server | console ] [ options ]
Run a waves command with the given options. Use --help with any command to learn more about that command. EXAMPLE: waves generate --help
daenerys% ruby -v
ruby 1.8.7 (2009-12-24 patchlevel 248) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2010.01

I think choices is an old gem and not doing what we need to. Perhaps a boson based solution would work?

I fixed this problem by calling app.database in my application code.

this is esp. important since it isn't in rubyforge

Once Waves 0.9 is ready to go, make sure to update all the Waves gems (filebase, functor, autocode, etc.) on both GemCutter and RubyForge.