- web-devel - Haskell.org

Yesod routes and Persistent entities in separate files
by Michael Snoyman 05 Jan '11

05 Jan '11

Hi all, The Yesod scaffolding tool currently does precisely one thing: produce a scaffolded site. It does *not* provide any facilities for adding new routes or entities after the fact, or creating basic CRUD interfaces the way Rails or Django do. Nubis has proposed adding this functionality. The current roadblock is that the Yesod routes and Persistent entities are defined with quasi-quotation within the code. I believe that technically speaking it should be possible to make this kind of feature work, but it would make more sense to do it as a separate file. I think the proposal would essentially change: mkYesod "MyApp" [$parseRoutes|...|] to mkYesod "MyApp" "MyApp.routes" with the ... being in MyApp.routes, and a similar change for the $persist quasi-quotation. What does everyone think of this? I see the following advantages: * Makes it more straight-forward to write these kinds of scaffolding tools. * Gets away from quasi-quotation for those who have an aversion to it. On the other hand, the downsides are: * One more file to deal with. * The standard issue of Haskell files not automatically recompiling when an external files are changed. This can be worked around with wai-handler-devel. Another possibility is offering *both* options, but as much as possible I'm trying to avoid creating multiple approaches. Michael

2 2

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

04 Jan '11

Exactly! I was looking for addWidget. I'll give it a shot at providing my own html also, I'll let you know my final solution. Thank you all guys. cheers ----nubis :) On Tue, Jan 4, 2011 at 9:29 AM, Matt Brown <matt(a)softmechanics.net> wrote: > Regarding your error, I think you want addWidget instead of addHamlet. > This compiles for me: > > loginHandler = do > let tm = liftHandler getRouteToMaster > let email = tm >>= apLogin authEmail > defaultLayout $ do > setTitle $ string "Login" > addWidget $(hamletFile "login") > > -matt > >

1 0

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