> This isn't a critic of erlyweb, but rather a laundry list of things
> that I need to be able to "easily" do in order to port my app from
> Rails to erlyweb.

Why port it if it works?

> 1 - full text search.  I have some recent experience with Sphinx
> http://www.sphinxsearch.com/.  Sphinx is a good match for erlang since
> it runs as a nice stand-alone daemon and doesn't require the weight of
> installing a Java system like Lucene requires.  Rails has good plug-
> ins and tutorials for using Sphinx.  Erlang / erlyweb has nothing.

Erlyweb supports (at the moment) 3 DBMSs, one of which (mnesia) varies  
vastly from the other two (Postgres and MySQL). I suppose you'd have  
to find something for your DBMS.

> 2 - PayPal or Amazon or Google Payment.  An erlang library for _any_
> payment gateway is needed.

Agreed

> 3 - Current tutorials.  The API docs on erlyweb are ok, but we need
> real-world tutorials using the latest erlyweb.

I'm working on some sample code, and I hear someone else is writing a  
tutorial. It's all very young at the moment.

> There are lots of little things, like good date and time pretty
> printing.  Ruby does have tons of libraries.  We need to identify the
> most needed ones for webapp dev.

Just identify the "little things" and people can get to work :) Just  
writing "tonnes of libraries" is hard without some direction. PayPal/ 
Amazon and date/time pretty-printing sound like good places to start.

This might help for date-formatting. It's a little verbose, but works:

format_date(calendar:universal_time()) ->  "Sat, 22 Dec 2007 00:52:52  
GMT"

format_date({{_,_,_},{_,_,_}}=DateTime) ->
  httpd_util:rfc1123_date(DateTime).


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to