> Aman and I spent a fair chunk of time since yesterday hacking on the
> plugins.
Great work!
> We have now defined what Sequel plugins will look like, and how they
> will be distributed and included. Plugins are rubygems, which means
> that users can simply require "sequel-orderable" for example and be
> able to use the orderable plugin since it's already wrapped in the
> Sequel::Plugins namespace. (note: gem names will use snake case)
Can plugins be loaded automagically on demand? It should be quite easy
to do that.
>
> From within a sequel model, a simple use case is:
>
> class LineItem < Sequel::Model
> is :Orderable
> end
>
Can we use lowercase (with underscores) to make it more Ruby-like?
e.g.:
is :orderable
> suggestions and feedback are greatly appreciated.
I think it would be wise to have the plugin implementation broken down
to class methods, dataset methods and instance methods (in a similar
fashion to ActiveRecord plugins), e.g.:
module Sequel::Plugins::Tree
module ClassMethods
def root
...
end
end
module InstanceMethods
def parent
...
end
def children
...
end
end
end
end
best
Sharon
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sequel-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
