On Apr 2, 6:57 pm, Clemens Oertel wrote:
> One follow up question, relating to the contexts I mentioned earlier:
> Following my approach mentioned below, let's assume I have a template
> for embedding. This template contains the HTML code for a tabular
> list of data entities. Depending
>
> Most web sites I've worked on, there's a default way to display a form and
> that default is encapsulated in the model itself. This encapsulation does
> not bar you from building your own form renders, but it does give you nice
> default behavior.
>
I found it odd at first too, to find web re
On Tue, Mar 31, 2009 at 7:06 AM, Clemens Oertel wrote:
> Hello,
>
> Sorry for the delay in my response, but I only get to play with lift on the
> weekends, and I wanted to look into your suggestions in more detail.
>
> I ported the toForm code from Record to Mapper (and by port, I mean mostly
> cu
One follow up question, relating to the contexts I mentioned earlier:
Following my approach mentioned below, let's assume I have a template
for embedding. This template contains the HTML code for a tabular
list of data entities. Depending on where the template is embedded,
some of the enti
On Mar 31, 9:09 pm, Clemens Oertel wrote:
> 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 - give
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 have at least dozens, if not even
On Mar 31, 5:06 pm, Clemens Oertel wrote:
> Hello,
>
> Sorry for the delay in my response, but I only get to play with lift
> on the weekends, and I wanted to look into your suggestions in more
> detail.
>
> I ported the toForm code from Record to Mapper (and by port, I mean
> mostly cut'
Hello,
Sorry for the delay in my response, but I only get to play with lift
on the weekends, and I wanted to look into your suggestions in more
detail.
I ported the toForm code from Record to Mapper (and by port, I mean
mostly cut'n'paste). While doing so, I noticed 2 things:
- Why not pro
On Mar 19, 7:08 pm, "marius d." wrote:
> On Mar 18, 11:24 pm, Clemens wrote:
>
> > Thank you for your patience, Marius.
>
> > > Well you can use different RecordMeta implementations if you need to
> > > different representation of a record without sequential template
> > > change. So no state
On Mar 18, 11:24 pm, Clemens wrote:
> Thank you for your patience, Marius.
>
> > Well you can use different RecordMeta implementations if you need to
> > different representation of a record without sequential template
> > change. So no state dependency.
>
>, b I'm really not trying to be diffi
Thank you for your patience, Marius.
> Well you can use different RecordMeta implementations if you need to
> different representation of a record without sequential template
> change. So no state dependency.
I'm really not trying to be difficult, but having multiple RecordMeta
instances, for wh
On Mar 18, 8:54 pm, Clemens wrote:
> > Yes I am referring to toForm but note that you can provide your own
> > template. Please see formTemplate.
>
> I did, thanks for the pointer. formTemplate applies to the record as a
> whole, right? If I want to render a record differently, I could set
> di
> Yes I am referring to toForm but note that you can provide your own
> template. Please see formTemplate.
I did, thanks for the pointer. formTemplate applies to the record as a
whole, right? If I want to render a record differently, I could set
different templates one after the other - even thou
On Mar 18, 1:30 pm, Clemens Oertel wrote:
> I admit to only having worked with mapper. I will look closer into
> record, (quick glance: it comes with next-to-the-field messages, nice).
>
> Marius, are you referring to the toForm functions? I'm probably just
> not seeing how to use them in a
I admit to only having worked with mapper. I will look closer into
record, (quick glance: it comes with next-to-the-field messages, nice).
Marius, are you referring to the toForm functions? I'm probably just
not seeing how to use them in a flexible manner. With respect to
validation, I was w
FWIW please also take a look on Record and form&validation support.
Br's,
Marius
On Mar 17, 11:07 pm, Clemens Oertel wrote:
> Hello everybody,
>
> Still trying to learn how to use lift efficiently and effectively, I
> got a little bit confused about the toForm function in the model/
> mappers
16 matches
Mail list logo
