To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
I appreciate the suggestion, I did think of that, but one of my goals
is to keep the XHTML out of my code..!
This seems a tough problem in general.. Ideally in snippets there
would be no presentation, just data I think, e.g. in this case a
boolean. The XHTML template would then form the presentation of that
data, whether it be a checkbox or whatever.
Perhaps I'm approaching this from the wrong angle?
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
Using the latest and greatest (master branch), I can't reproduce the MatchError but I can reproduce the issue with the attribute being generated if the value is null.
On Sun, Dec 6, 2009 at 7:25 PM, Alex Boisvert <alex.b...@gmail.com> wrote:Using the latest and greatest (master branch), I can't reproduce the MatchError but I can reproduce the issue with the attribute being generated if the value is null.
How about adding a Box alternative rather than perpetuating a paradigm based on null?
alex
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.