- web-devel - Haskell.org

Re: [web-devel] Wrapping the widget generated by the authEmail backend.
by Christian Klauser 04 Jan '11

04 Jan '11

---------- Forwarded message ---------- From: Christian Klauser <ch27k89(a)gmail.com> Date: 4 January 2011 11:35 Subject: Re: [web-devel] Wrapping the widget generated by the authEmail backend. To: Nubis <nubis(a)woobiz.com.ar> Hi, I hit the very same problem a couple of days ago. You can certainly just build a "compatible" form (with the same field names) and that will just work fine. If you want to use the hamlet provided by the plugins, here is what I did: loginHandler = defaultLayout $ do setTitle $ string "Login" tm <- liftHandler getRouteToMaster let renderPlugin :: AuthPlugin YourSiteHere -> SubWidget Auth () -- necessary renderPlugin = flip apLogin tm openidForm = renderPlugin authOpenId emailForm = renderPlugin authEmail addWidget $(widgetFile "login") In 'login.hamlet' I can then use ^openidForm^ and ^emailForm^ like any other widget. Neat as it is, you'll still have a hard time styling these login forms, as don't have any CSS classes assigned to them. It will be difficult to distinguish between %input!type=text and %input!type=submit, so you might end up re-creating those forms anyway :-( Hope this helps Regards Chris On 4 January 2011 03:38, Nubis <nubis(a)woobiz.com.ar> wrote: > Hi guys, > I'm trying to build a good looking login page, but I noticed the > loginHandler that comes with yesod-auth just concatenates all the widgets > from all the used auth backends. To make matters worse, the markup some of > the backends generate is not even my preferred brand! :) > > So I try to at least wrap the authEmail widget inside my own html, with a > login.hamlet file that looks a bit like this: > .box > %h1 Login > .wrapper > ^email^ > > I manage to get the widget out of the authEmail backend, but then I can't > use it inside my hamlet file that I add using addHamlet b/c it doesn't > typecheck. > > loginHandler = do > let tm = liftHandler getRouteToMaster > let email = tm >>= apLogin authEmail > defaultLayout $ do > setTitle $ string "Login" > addHamlet $(Settings.hamletFile "login") > > Is there any way around this? Am I approaching this the wrong way? > This could also be solved if instead of a widget I could get the url and > fieldname information from the backend, so I can use those things inside my > ad-hoc html. > Moreso, as a way to customize the html I'm tempted to override or redefine > apLogin inside my app's domain so I can customize the html it generates. But > just to keep taking advantage of haskell's strenghts it would be nice to > formalize this idea a bit more (and I don't know how to approach that). > > thanks in advance for your help > cheers! > ----nubis :) > > _______________________________________________ > web-devel mailing list > web-devel(a)haskell.org > http://www.haskell.org/mailman/listinfo/web-devel > >

2 1

Wrapping the widget generated by the authEmail backend.
by Nubis 03 Jan '11

03 Jan '11

Hi guys, I'm trying to build a good looking login page, but I noticed the loginHandler that comes with yesod-auth just concatenates all the widgets from all the used auth backends. To make matters worse, the markup some of the backends generate is not even my preferred brand! :) So I try to at least wrap the authEmail widget inside my own html, with a login.hamlet file that looks a bit like this: .box %h1 Login .wrapper ^email^ I manage to get the widget out of the authEmail backend, but then I can't use it inside my hamlet file that I add using addHamlet b/c it doesn't typecheck. loginHandler = do let tm = liftHandler getRouteToMaster let email = tm >>= apLogin authEmail defaultLayout $ do setTitle $ string "Login" addHamlet $(Settings.hamletFile "login") Is there any way around this? Am I approaching this the wrong way? This could also be solved if instead of a widget I could get the url and fieldname information from the backend, so I can use those things inside my ad-hoc html. Moreso, as a way to customize the html I'm tempted to override or redefine apLogin inside my app's domain so I can customize the html it generates. But just to keep taking advantage of haskell's strenghts it would be nice to formalize this idea a bit more (and I don't know how to approach that). thanks in advance for your help cheers! ----nubis :)

2 1

Hamlet variables: (foo bar) baz or foo (bar baz)
by Michael Snoyman 03 Jan '11

03 Jan '11

I thought I would start this in a separate thread. Right now in Hamlet, $foo.bar.baz$ (or equivalently $foo bar baz$ gets converted to the Haskell code "foo (bar baz)". This makes a fair bit of sense for the period-delimited syntax, but feels very wrong for the space-delimited syntax. So the question is: should we change things around? That would mean we would need to modify our current templates to include extra parentheses, eg: $foo.bar.baz$ -> $foo (bar baz)$ $a.b.c.d$ -> $a (b (c d))$ I suppose that, in theory, if we actually change the variable interpolation character to a percent sign, we could take back the dollar sign to work like Haskell, eg: $a.b.c.d$ -> %a $ b $ c d% And just since I brought *that* up: we could consider using a different symbol for variable interpolation than the percent sign, such as a hash or ampersand. However, both of those already have special meaning (hash == id, ampersand == HTML escape character), so I don't know how well that would work. There was talk once upon a time of merging the syntax for dollar-sign and caret interpolation, which now that we've added some more polymorphism it might be possible. Caveat: I haven't actually written any code for this, so I don't know how feasible it is. I'm basically throwing out ideas as they come to me. Michael

5 6

help with fileField
by Knut Olav Bøhmer 02 Jan '11

02 Jan '11

Hi, Can anyone help me extend the "Random bananas" example from http://docs.yesodweb.com/book/forms/ to include a fileField, so that I can understand how to use the fileField. I have tried something like this: data Params = Params { minNumber :: Int , maxNumber :: Int , singleWord :: String , pluralWord :: String , fileTest :: FileInfo } paramsFormlet :: Maybe Params -> Form s m Params -- Same as: paramsFormlet :: Formlet s m Params paramsFormlet mparams = fieldsToTable $ Params <$> intField "Minimum number" (fmap minNumber mparams) <*> intField "Maximum number" (fmap maxNumber mparams) <*> stringField "Single word" (fmap singleWord mparams) <*> stringField "Plural word" (fmap pluralWord mparams) <*> fileField "test" (fmap fileTest mparams) I have problems understanding what's going on here. Regards -- Knut Olav Bøhmer

2 1

Yesod internal error reporting
by Aur Saraf 02 Jan '11

02 Jan '11

Hi, Yesod currently reports internal server errors in a way that is very hard to debug, in my opinion - with many "..." instead of text (I am thinking specifically about the SQL error I have in front of my eyes, but I'm pretty sure I've seen it with other errors too). How hard would it be to improve this? Or was this fixed in a newer version than I'm using? Thanks, Aur

1 0

rendering hamlet (esp julius) manually
by Max Cantor 01 Jan '11

01 Jan '11

I was wondering how to render a hamlet template (I'm specifically interested in julius - more on that later) outside of the context of a Handler handling a web request. The reason I want to do this is I have come client side javascript (for android and ios + phonegap) and it would be nice to use julius to automatically generate some javascript code for the xcode project. To be specific, i have a .js file like this: var URL_HOME = "http://localhost"; // var URL_HOME = "http://myhost"; var URL_PROFILE = URL_HOME + "/boo"; If its possible to render julius without a request, then I could do this: var URL_HOME = @HomeR@; var URL_PROFILE = @ProfileR@; and add a small executable to generate the JS file. So, how would one do this? Sorry if this is obvious, i spent some time trying and digging around the haddocks, didn't find an answer. happy new years, max

2 1

yesod-devel
by Christopher Done 31 Dec '10

31 Dec '10

This list only ever contains yesod posts and little else. Seeing as neither interest me I'm unsubscribing. FWIW.

1 0

Request body parsing in Yesod
by Michael Snoyman 31 Dec '10

31 Dec '10

One of the major changes coming in WAI 0.3 is how the request body is dealt with. I figure this is also a good time to address request body parsing in Yesod. I've put up a Wiki page[1] to describe my ideas. Input again is appreciated. Michael [1] http://wiki.yesodweb.com/Proper%20request%20body%20parsing

1 0

Hamlet variable interpolation syntax [previously: A few questions about Yesod]
by Alexander Dunlap 31 Dec '10

31 Dec '10

2010/12/30 Michael Snoyman <michael(a)snoyman.com>: > On Thu, Dec 30, 2010 at 3:31 PM, Iustin Pop <iustin(a)google.com> wrote: >> On Thu, Dec 30, 2010 at 03:09:16PM +0200, Michael Snoyman wrote: >>> Very good questions, answers below. >>> >>> On Thu, Dec 30, 2010 at 1:01 PM, Iustin Pop <iustin(a)google.com> wrote: >>> > Hi all, >>> > >>> > I just started looking at Yesod and its associated libs (hamlet, etc.) >>> > and it is very interesting, thanks. >>> > >>> > However, I'm confused by a few things and the docs are not helping, so >>> > please bear my beginner questions. >>> > >>> > First: hamlet uses '.' as function application, instead of the usual >>> > space. How can I then use a qualified name (e.g. Data.List.nub)? If I >>> > use it normally, it errors out on me. Must be something very trivial but >>> > I cannot find a way. >>> >>> Hamlet uses both '.' and space as function application, and therefore >>> qualified names are not supported. I work around this usually by >>> creating an alias for the function I want locally. I know this can be >>> inelegant; if you have any ideas, I'm all ears. >> >> Yep, that's what I'm using too now, but it becomes cumbersome quickly, >> especially when using records… >> >> I'm not sure what was the original impetus to use . (too) as function >> application if space is accepted too. I'm thinking reverting that >> decision would make the code look more like regular Haskell. >> >> A simpler alternative (not sure if easily doable) would be to allow >> escaping of the dot, e.g. $Data\.List\.nub.mylist$; it's ugly, but… > > It actually went the other way: period first, and space added by > request. Originally, Hamlet variables were not directly mapped to > Haskell function calls. Instead, it was meant to parallel variable > lookup in common template languages from the object-oriented world. > Another impetus is because of statements like forall and maybe: > > $forall allPeople.myFamily person > %li $person name$ > > This can also be written as > > $forall (allPeople myFamily) person > > You could argue that the latter is more legible; my problem with the > space is for cases with more than two functions in the chain. $foo bar > baz$ gets converted to the Haskell code "foo (bar baz)". > > I'll admit that this whole situation bothers me as well. Hamlet 0.7 is > currently in the works, and I don't mind introducing some major > changes. I think this issue deserves some attention: what does > everyone else think? Maybe we should start a separate thread to > discuss this issue in particular. > Would there be a problem with removing the dot syntax entirely and just having regular Haskell syntax for variable interpretation? That might be more flexible and easier to learn. Alexander

6 11

A few questions about Yesod
by Iustin Pop 30 Dec '10

30 Dec '10

Hi all, I just started looking at Yesod and its associated libs (hamlet, etc.) and it is very interesting, thanks. However, I'm confused by a few things and the docs are not helping, so please bear my beginner questions. First: hamlet uses '.' as function application, instead of the usual space. How can I then use a qualified name (e.g. Data.List.nub)? If I use it normally, it errors out on me. Must be something very trivial but I cannot find a way. Second: Yesod.Json says “Due to the limited nature of the JSON format, you can create any valid JSON document you wish using only jsonScalar, jsonList and jsonMap”. This seems false to me, as jsonScalar only deals with JSON strins, and not JSON numbers or the constants (true, false, null). In the meantime I'm using a hack for numbers using jsonRaw, but I think some more functionality needs to be added to it for non-trivial usage. And last: I don't understand how runDB and the persistent framework is supposed to do error handling. Case in point: let's say one tries to insert a duplicate unique key in a table, which fails as expected "user error (SQLite3 returned ErrorConstraint while attempting to perform step.)". The problem is any other use of that particular REST resource, even with different parameters, results in "user error (SQLite3 returned ErrorMisuse while attempting to perform bind text.)", and I don't know if this is due to my usage of the framework or due to something else. The interesting part is that other resources are working fine. Thanks again, iustin

2 3