On Dec 1, 2007 10:24 PM, Robin <[EMAIL PROTECTED]> wrote: > > Here are some ideas: > > * Flexible routes
What do flexible routes do exactly? I know that Rails has some routes config file, but ErlyWeb gives you full control -- in Erlang -- over how requests are routed using the app controller. You also have the before_call controller hook. Is there anything missing? > * Standardized script interface (for migrations, generators/templates, > tests, maintenance tasks ) I'm open to suggestions here. > > I know a bit about Rails plugins...the main benefit is providing a > standard way for people to share functionality in the vein of > "convention over configuration". > > Plugins are created with "script/generate plugin my_widget", which > creates a default plugin structure under vendor/plugins/my_widget. > > Plugins have standard hooks like install.rb which is run when the > plugin is installed, and init.rb which is run when the plugin is > initialized. > > A plugin's lib/ is automatically added to the include path, tasks/ are > automatically added to rake's include path, and test/ is added to the > test suite. > > Plugins are stored in svn and you can install third party plugins with > "script/plugin install http://site.com/my_widget"; which does an svn > checkout to your app's vendor/plugins directory. > > Plugins are good for quick code sharing where someone publishes a blog > post explaining their new plugin, and you can easily install and > evaluate it. > > The downside of plugins is that most are generally unversioned, and > most developers serve plugins directly from trunk/ so it is hard to > track dependencies, compatibility, and updates. > > The Merb framework which attempts the be Rails only faster and better > uses ruby gems (gems are ruby packages) for plugins which provides for > versioning an dependencies. > > > For Erlyweb, instead of creating a one-off plugin system like Rails, > it might be better to use a package system to handle dependencies and > provide versioning. These sound like good features. I guess the only "plugin" ErlyWeb currently has is the erlang2facebook library, which you have to install manually in your app directory (which is pretty easy, actually). I think a fully fledged plugin system would be useful if people started creating more and more such addons and maintenance became a problem, but I'm not seeing a lot of other addons being developed so a full plugin system may not be needed right now. That said, if more people start creating such addons I'll be happy to make their integration easier in ErlyWeb. Also, don't some plugins rely on migration support to modify the schema on installation? Thanks, Yariv > > Robin > > > > > On Dec 1, 8:42 pm, David King <[EMAIL PROTECTED]> wrote: > > > Also, we should start planning the next release. What features do you > > > think will be most useful (web services support is on the list)? > > > > * Database migrations > > > > * Plugin support > > > > Rails has the ability to plug in an entire login system, or OpenID > > system, or forum system, into your app all at once, by installing it > > and setting up the hooks. This would make it easier to write this > > code once. I'm not a heavy user of Rails, so I don't know how this > > works. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" 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/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
