[Lift] Record-aware secondary menu?

, "edit"), "Edit")) and then use some pattern matching during dispatching to retrieve the record ID again? Thank you, Clemens --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" grou

[Lift] Re: Is Lift the right tool for us?

bines so many aspects, it might take a considerable amount of effort to isolate concerns when switching from mapper to JPA or similar. I will be switching to JPA in the next two weeks. Best, Clemens --~--~-~--~~~---~--~~ You received this message because you

[Lift] Re: (created|updated|deleted)_(by|at) trait

wnerType] with UserStamped[OwnerType] { self: OwnerType => // A lot more stuff here ... } Best, Clemens --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to

[Lift] Re: Rails -> Lift

> On Thu, Apr 9, 2009 at 9:42 AM, Clemens Oertel > wrote: > > I don't think it's necessary to make a final decision about your IDE > at any time. AFAIK, all major IDEs work quite well with Maven's pom > files, so it's very easy to switch IDEs at any

[Lift] Re: Rails -> Lift

st" IDE, it would probably be the only IDE (the causality goes both ways). It's always a matter of needs, prior experience, taste ... Best, Clemens On 9-Apr-09, at 5:38 AM, Alexander Kellett wrote: > > actually my biggest blocker (and still my blocker) is getting a > working

[Lift] Re: Good way to implement "cancel" links?

Thanks, David. Just for my understanding: Links generated by SHtml.link are valid throughout the entire session? For a multi-page form, storing the referrer in the first step in a RequestVar would then also work, I take it. Thank you, Clemens On 4-Apr-09, at 6:41 PM, David Pollak wrote

[Lift] Good way to implement "cancel" links?

cel link, and populate it using the linking page's URI: SHtml.link(editUrl, () => {...; cancelLinkRV(S.request.uri)}, Text("Edit")) Is the URI really reusable like this? Or is there already some better way provided by lift? Thanks, Clemens --~--~-~--~~-

[Lift] Re: Forms & validation formatter

my initial approach of having the mapper class (or it's companion object) fill out the forms itself. I'd be happy if someone could prove me wrong ... Best, Clemens PS: Exercise for the reader: Instead of selective linking, have only either A or B be displayed, depending on the embe

[Lift] MappedDateTime - Do we have a Date? Or is it a timestamp?

ted. Best, Clemens --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr

[Lift] Re: Forms & validation formatter

Marius: On 31-Mar-09, at 12:31 PM, marius d. wrote: > > > > On Mar 31, 5:06 pm, Clemens Oertel wrote: >> - Why not provide the same template mechanism used for forms for HTML >> output? This way I can reuse the same template for both - given that >> my records hav

[Lift] Re: Forms & validation formatter

complex applications; and B) that it is my understanding that overriding internal classes of a framework is a bad thing - I'd rather see a proper application of the Hollywood principle. Just wanted to provide an outsider's feedback. Overall, I think lift's just fantastic. Thank

[Lift] Re: Forms & validation formatter

various record fields (StringField, etc.) call upon this default "something" whenever their toForm-function is called, no one would notice something has changed. But I could also call toForm(formRenderer) for non-default rendering. > it's quire a par

[Lift] Re: Forms & validation formatter

nsistently provided by > Record. I think there is still some level of validation in mappers but > I haven't played with it yet ... Oh, the validation is working just fine with mapper. It's only the lack of flexibility with respect to a

[Lift] Re: Forms & validation formatter

ese boolean fields are to be displayed as 3 radio buttons. One of course wants to ensure that such a change only affects one area in the code base. That's what got me wondering: Is the toForm approach the best one for my case? Thanks for listening, Clemens On 18-Mar-09, at 3:18 AM, mar

[Lift] Forms & validation formatter

;form", html, "aField" -> aModelClass.aField. inputTypeCallback (inputFormatter)) ... Maybe a partial function, potentially on case classes, is better? Many options ... I'm looking forward to any feedback. Best, Clemens --~--~-~--~~~---~--~~ You received th

[Lift] Forms & validation formatter

aybe a partial function, potentially on case classes, is better? Many options ... I'm looking forward to any feedback. Best, Clemens --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift&quo

[Lift] Re: != ?

That's good to hear - I like orthogonality. I created a ticket for this, #21. Thanks Clemenns On Mar 17, 12:26 pm, David Pollak wrote: > == form="post"> > > If this is not the case, it's a Lift defect. > > > > > > On Tue, Mar 17, 2009

[Lift] != ?

ubmit" -> SHtml.submit("New", saveMe)) } newSite(form) } With the style tags, everything works as expected (form fields are populated after a failed validation). If I use , the form comes up empty after a failed validation. What am I getting wrong? Thanks in advance!