October 2010 - web-devel

Re: [web-devel] Including saltPass in the Auth2.Email API
by Michael Snoyman 19 Oct '10

19 Oct '10

Well, there's setCreds[1], is that what you're looking for? It's what the individual authentication backends (email, openid, rpxnow, facebook) each call. [1] http://hackage.haskell.org/packages/archive/yesod-auth/0.1.4/doc/html/Yesod… On Tue, Oct 19, 2010 at 10:44 AM, Max Cantor <mxcantor(a)gmail.com> wrote: > Furthermore, a programmatic way to login besides redirecting to the login route would be helpful.. > > Max > > On Oct 19, 2010, at 1:30 PM, Michael Snoyman wrote: > >> On Tue, Oct 19, 2010 at 7:18 AM, Max Cantor <mxcantor(a)gmail.com> wrote: >>> Michael, >>> >>> What do you think about exporting the saltPass function in the Auth2.Email plugin. The reason I would want this would be so that passwords could be set programmatically as opposed to solely via the current form. Currently, I just cut and pasted the code into my code, but it doesn't seem like this is a particularly sane/future-proof way to work. Any thoughts? >> >> Sounds great, I've justed pushed a commit to Git. By the way, starting >> with yesod 0.6/yesod-auth 0.2, the code lives under >> Yesod.Helpers.Auth.*, as it should. The Auth2 namespace was only to >> avoid conflicts with yesod 0.5. You mind waiting till 0.6 is released >> to have access to this function? >> >> By the way, porting to 0.6 should be a piece of cake. >> >> Michael > >

1 0

Fwd: [web-devel] Including saltPass in the Auth2.Email API
by Michael Snoyman 19 Oct '10

19 Oct '10

Sorry, forgot to Reply All: ---------- Forwarded message ---------- From: Michael Snoyman <michael(a)snoyman.com> Date: Tue, Oct 19, 2010 at 7:30 AM Subject: Re: [web-devel] Including saltPass in the Auth2.Email API To: Max Cantor <mxcantor(a)gmail.com> On Tue, Oct 19, 2010 at 7:18 AM, Max Cantor <mxcantor(a)gmail.com> wrote: > Michael, > > What do you think about exporting the saltPass function in the Auth2.Email plugin. The reason I would want this would be so that passwords could be set programmatically as opposed to solely via the current form. Currently, I just cut and pasted the code into my code, but it doesn't seem like this is a particularly sane/future-proof way to work. Any thoughts? Sounds great, I've justed pushed a commit to Git. By the way, starting with yesod 0.6/yesod-auth 0.2, the code lives under Yesod.Helpers.Auth.*, as it should. The Auth2 namespace was only to avoid conflicts with yesod 0.5. You mind waiting till 0.6 is released to have access to this function? By the way, porting to 0.6 should be a piece of cake. Michael

1 0

Including saltPass in the Auth2.Email API
by Max Cantor 19 Oct '10

19 Oct '10

Michael, What do you think about exporting the saltPass function in the Auth2.Email plugin. The reason I would want this would be so that passwords could be set programmatically as opposed to solely via the current form. Currently, I just cut and pasted the code into my code, but it doesn't seem like this is a particularly sane/future-proof way to work. Any thoughts? Max

1 0

Yesod-0.5.4 linking problem
by Max Cantor 17 Oct '10

17 Oct '10

Has anyone on the list had trouble building yesod-0.5.4? I'm getting the same linker error as interferon described here: http://hpaste.org/40633/ I tried all the usual suspects.. cabal install --reinstall <every relevant package> Seems to be a conflict between zlib and zlib-bindings. Thanks, Max

2 1

Yesod: generating code for optional vs required fields.
by Matt Brown 15 Oct '10

15 Oct '10

Hello all, I'm new to Yesod, and I'm trying to render my forms like this: http://www.stylephreak.com/uploads/source/cssforms/cssform.php. This has two main requirements: Use divs instead of tables, and specify whether the field is required or optional. This is what I have so far: fieldsToDivs :: FormField sub y a -> Form sub y a fieldsToDivs = mapFormXml $ mapM_ go where go fi = do let cls = string $ if fieldRequired fi then "fm-req" else "fm-opt" wrapWidget (fiInput fi) $ \w -> [$hamlet| %div!class=$cls$ %label!for=$fiIdent.fi$ $fiLabel.fi$ .tooltip $fiTooltip.fi$ ^w^ $maybe fiErrors.fi err %div.errors $err$ |] fieldRequired _ = True I'm not sure how to implement fieldRequired. Is there a way to infer required/optional from FieldInfo? Would it make sense to add fiRequired :: Bool to FieldInfo? thanks, -matt

2 2

Yesod: embedding the output of a route in hamlet
by Max Cantor 14 Oct '10

14 Oct '10

Is it possible, without using AJAX, to easily embed the output of a route in Hamlet? For instance: getItemDataR :: String -> Handler RepHtml getItemDataR = defaultLayout $ addBody [$hamlet| .... getAllItemsR :: Handler RepHtml getAllItemsR = defaultLayout $ addBody [$hamlet| $forall ls i ^ItemDataR.i^ where ls = ["a","b","c"] something like that? Thanks, Max

1 0

Yesod and Tables vs Divs
by Max Cantor 14 Oct '10

14 Oct '10

Just throwing out every feature req that pops into my head now.. Some features of Yesod sort of require tables (fieldsToTable function in the Forms module for instance. Although there is a FieldsToPlain function, you lose a lot when you use it. Given that the trend in web design is away from tables and towards divs+CSS, will this be a problem? Even a generic fieldsWithFxn :: (form element -> rephtml) -> GForm -> GWidget (pardon my pseudo code) might solve this particular problem. Just a thought, let me know if these brainstorms are getting too spammy, I'll stop. Max

2 1

Persistent Feature Request
by Max Cantor 10 Oct '10

10 Oct '10

Just a thought, but the it would be nice if the $persist QQ could also generate some sort of generic migrate function which will migrate all of your tables instead of having to do that manually as in the examples. If you forget a migrate statement, it unfortunately wont raise an error until runtime. As haskellers, we live and die by compile time errors.. Max

2 1

Web wiki page
by John Lenz 09 Oct '10

09 Oct '10

Hi, The past few days I have been investigating the various options for web programming in Haskell and when I first started looking it was pretty confusing. The existing wiki pages weren't really organised to help a newcomer see the various options and which libraries are supposed to work together, since the existing wiki pages basically just list of all the libraries and frameworks. So I edited the Web page on the wiki to list the various options, each of which contain pointers to the various libraries which are meant to work together. I would appreciate help completing the page (any options I didn't list?) since I have only been looking at the various options for a couple of days now. Thanks, John PS: I haven't picked which option I will use for my website yet, still evaluating. But having a list of options is helpful.

2 1

Re: [web-devel] Web wiki page
by John Lenz 08 Oct '10

08 Oct '10

On 10/08/2010 04:59 PM, Jeremy Shaw wrote: > Could you provide a link to the specific wiki page you are referring > to -- I believe there is (or was) more than one page, some better than > others. Just wanted to make sure we are all (literally) on the same > page. > http://www.haskell.org/haskellwiki/Web

1 0