[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
How about vmware and Linux as your dev platform? Just askin'
On Tue, Jun 16, 2009 at 12:16 AM, marius d. wrote:
>
> two things:
>
> 1. Hate msysgit
> 2. Thanks to Jorge for his help in committing the file
>
>
> Marius
>
> On Jun 16, 9:41 am, "marius d." wrote:
> > yes yes yes ... entirely my bad as I missed that out ...
> >
> > I'll correct it very soon.
> >
> > Marius
> >
> > On Jun 16, 3:07 am, "Bryan." wrote:
> >
> > > Hi Marius,
> >
> > > I just updated to the tip and got a build failure:
> >
> > > [WARNING] /home/bryan/public-repos/git/liftweb/sites/example/src/main/
> > > scala/net/liftweb/example/snippet/Ajax.scala:65: error: value
> > > autocomplete is not a member of object net.liftweb.http.jquery.JqSHtml
> > > [WARNING] "auto" -> JqSHtml.autocomplete("", buildQuery _, _
> > > => ()))
> >
> > > --Bryan
> >
> > > On Jun 15, 2:16 pm, "marius d." wrote:
> >
> > > > Folks,
> >
> > > > I just made the autocomplete a Lift widget so it does not exist
> > > > anymore in JqShtml object. Here is an example on how to use it:
> >
> > > > - For Ajax autocomplete
> > > > AutoComplete("", (current, limit) => {
> > > > println("current = " + current)
> > > > (1 to limit).map(v => "Value_" + v)
> > > > }, s => println("submit " + s))
> >
> > > > - For pre-provided options list
> > > >AutoComplete.autocompleteObj(/*same params as bfore*/)
> >
> > > > This may break your app but I think it is very easy to update it.
> >
> > > > I also fixed some bugs:
> > > > 1. It didn;t work if the container cookies were turned off
> > > > 2. hovering on the options list did not work on Ubuntu FF3 at least
> > > > due to a capitalizated LI equality test.
> >
> > > > If you encounter any problems, please let me know.
> >
> > > > Br's,
> > > > Marius
> >
> > > > On Jun 8, 12:34 pm, Kevin Wright
> > > > wrote:
> >
> > > > > +1
> >
> > > > > As an evolving framework, it definitely makes more sense to favour
> > > > > consistency over backward compatibility at this stage
> >
> > > > > On Mon, Jun 8, 2009 at 9:00 AM, marius d.
> wrote:
> >
> > > > > > Other folks, please speak up ! :) ... I will soon migrate this
> into a
> > > > > > Lift widget.
> >
> > > > > > Br's,
> > > > > > Marius
> >
> > > > > > On Jun 6, 4:53 pm, David Pollak
> wrote:
> > > > > > > I think I'm using in one place in one project so my api
> breakage factor
> > > > > > is
> > > > > > > low. I'm okay with moving it unless someone else is going to
> feel real
> > > > > > > pain.
> >
> > > > > > > On Jun 6, 2009 12:24 AM, "Marius"
> wrote:
> >
> > > > > > > Is there a reason why the JQuery autocomplete is not a Lift
> widget but
> > > > > > > instead it lives in http/jquery package? .. I remember a long
> time ago
> > > > > > > me putting it in the jquery package to separate SHtml stuff
> that is
> > > > > > > dependent on JQuery to the others.
> >
> > > > > > > Thoughts?
> >
> > > > > > > Br',
> > > > > > > Marius
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
Whenever I see "msys" I hear "emesis" in my head. Emesis is the medical term
for vomiting.
On 6/16/09, marius d. wrote:
>
>
> two things:
>
> 1. Hate msysgit
> 2. Thanks to Jorge for his help in committing the file
>
>
>
> Marius
>
>
> On Jun 16, 9:41 am, "marius d." wrote:
> > yes yes yes ... entirely my bad as I missed that out ...
> >
> > I'll correct it very soon.
> >
> > Marius
> >
> > On Jun 16, 3:07 am, "Bryan." wrote:
> >
> > > Hi Marius,
> >
> > > I just updated to the tip and got a build failure:
> >
> > > [WARNING] /home/bryan/public-repos/git/liftweb/sites/example/src/main/
> > > scala/net/liftweb/example/snippet/Ajax.scala:65: error: value
> > > autocomplete is not a member of object net.liftweb.http.jquery.JqSHtml
> > > [WARNING] "auto" -> JqSHtml.autocomplete("", buildQuery _, _
> > > => ()))
> >
> > > --Bryan
> >
> > > On Jun 15, 2:16 pm, "marius d." wrote:
> >
> > > > Folks,
> >
> > > > I just made the autocomplete a Lift widget so it does not exist
> > > > anymore in JqShtml object. Here is an example on how to use it:
> >
> > > > - For Ajax autocomplete
> > > > AutoComplete("", (current, limit) => {
> > > > println("current = " + current)
> > > > (1 to limit).map(v => "Value_" + v)
> > > > }, s => println("submit " + s))
> >
> > > > - For pre-provided options list
> > > >AutoComplete.autocompleteObj(/*same params as bfore*/)
> >
> > > > This may break your app but I think it is very easy to update it.
> >
> > > > I also fixed some bugs:
> > > > 1. It didn;t work if the container cookies were turned off
> > > > 2. hovering on the options list did not work on Ubuntu FF3 at least
> > > > due to a capitalizated LI equality test.
> >
> > > > If you encounter any problems, please let me know.
> >
> > > > Br's,
> > > > Marius
> >
> > > > On Jun 8, 12:34 pm, Kevin Wright
> > > > wrote:
> >
> > > > > +1
> >
> > > > > As an evolving framework, it definitely makes more sense to favour
> > > > > consistency over backward compatibility at this stage
> >
> > > > > On Mon, Jun 8, 2009 at 9:00 AM, marius d.
> wrote:
> >
> > > > > > Other folks, please speak up ! :) ... I will soon migrate this
> into a
> > > > > > Lift widget.
> >
> > > > > > Br's,
> > > > > > Marius
> >
> > > > > > On Jun 6, 4:53 pm, David Pollak
> wrote:
> > > > > > > I think I'm using in one place in one project so my api
> breakage factor
> > > > > > is
> > > > > > > low. I'm okay with moving it unless someone else is going to
> feel real
> > > > > > > pain.
> >
> > > > > > > On Jun 6, 2009 12:24 AM, "Marius"
> wrote:
> >
> > > > > > > Is there a reason why the JQuery autocomplete is not a Lift
> widget but
> > > > > > > instead it lives in http/jquery package? .. I remember a long
> time ago
> > > > > > > me putting it in the jquery package to separate SHtml stuff
> that is
> > > > > > > dependent on JQuery to the others.
> >
> > > > > > > Thoughts?
> >
> > > > > > > Br',
> > > > > > > Marius
> >
>
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
On Tue, Jun 16, 2009 at 9:16 AM, marius d. wrote:
>
> two things:
>
> 1. Hate msysgit
+Long.MAX_VALUE
>
> 2. Thanks to Jorge for his help in committing the file
>
>
> Marius
>
> On Jun 16, 9:41 am, "marius d." wrote:
> > yes yes yes ... entirely my bad as I missed that out ...
> >
> > I'll correct it very soon.
> >
> > Marius
> >
> > On Jun 16, 3:07 am, "Bryan." wrote:
> >
> > > Hi Marius,
> >
> > > I just updated to the tip and got a build failure:
> >
> > > [WARNING] /home/bryan/public-repos/git/liftweb/sites/example/src/main/
> > > scala/net/liftweb/example/snippet/Ajax.scala:65: error: value
> > > autocomplete is not a member of object net.liftweb.http.jquery.JqSHtml
> > > [WARNING] "auto" -> JqSHtml.autocomplete("", buildQuery _, _
> > > => ()))
> >
> > > --Bryan
> >
> > > On Jun 15, 2:16 pm, "marius d." wrote:
> >
> > > > Folks,
> >
> > > > I just made the autocomplete a Lift widget so it does not exist
> > > > anymore in JqShtml object. Here is an example on how to use it:
> >
> > > > - For Ajax autocomplete
> > > > AutoComplete("", (current, limit) => {
> > > > println("current = " + current)
> > > > (1 to limit).map(v => "Value_" + v)
> > > > }, s => println("submit " + s))
> >
> > > > - For pre-provided options list
> > > >AutoComplete.autocompleteObj(/*same params as bfore*/)
> >
> > > > This may break your app but I think it is very easy to update it.
> >
> > > > I also fixed some bugs:
> > > > 1. It didn;t work if the container cookies were turned off
> > > > 2. hovering on the options list did not work on Ubuntu FF3 at least
> > > > due to a capitalizated LI equality test.
> >
> > > > If you encounter any problems, please let me know.
> >
> > > > Br's,
> > > > Marius
> >
> > > > On Jun 8, 12:34 pm, Kevin Wright
> > > > wrote:
> >
> > > > > +1
> >
> > > > > As an evolving framework, it definitely makes more sense to favour
> > > > > consistency over backward compatibility at this stage
> >
> > > > > On Mon, Jun 8, 2009 at 9:00 AM, marius d.
> wrote:
> >
> > > > > > Other folks, please speak up ! :) ... I will soon migrate this
> into a
> > > > > > Lift widget.
> >
> > > > > > Br's,
> > > > > > Marius
> >
> > > > > > On Jun 6, 4:53 pm, David Pollak
> wrote:
> > > > > > > I think I'm using in one place in one project so my api
> breakage factor
> > > > > > is
> > > > > > > low. I'm okay with moving it unless someone else is going to
> feel real
> > > > > > > pain.
> >
> > > > > > > On Jun 6, 2009 12:24 AM, "Marius"
> wrote:
> >
> > > > > > > Is there a reason why the JQuery autocomplete is not a Lift
> widget but
> > > > > > > instead it lives in http/jquery package? .. I remember a long
> time ago
> > > > > > > me putting it in the jquery package to separate SHtml stuff
> that is
> > > > > > > dependent on JQuery to the others.
> >
> > > > > > > Thoughts?
> >
> > > > > > > Br',
> > > > > > > Marius
> >
>
--
Viktor Klang
Scala Loudmouth
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
two things:
1. Hate msysgit
2. Thanks to Jorge for his help in committing the file
Marius
On Jun 16, 9:41 am, "marius d." wrote:
> yes yes yes ... entirely my bad as I missed that out ...
>
> I'll correct it very soon.
>
> Marius
>
> On Jun 16, 3:07 am, "Bryan." wrote:
>
> > Hi Marius,
>
> > I just updated to the tip and got a build failure:
>
> > [WARNING] /home/bryan/public-repos/git/liftweb/sites/example/src/main/
> > scala/net/liftweb/example/snippet/Ajax.scala:65: error: value
> > autocomplete is not a member of object net.liftweb.http.jquery.JqSHtml
> > [WARNING] "auto" -> JqSHtml.autocomplete("", buildQuery _, _
> > => ()))
>
> > --Bryan
>
> > On Jun 15, 2:16 pm, "marius d." wrote:
>
> > > Folks,
>
> > > I just made the autocomplete a Lift widget so it does not exist
> > > anymore in JqShtml object. Here is an example on how to use it:
>
> > > - For Ajax autocomplete
> > > AutoComplete("", (current, limit) => {
> > > println("current = " + current)
> > > (1 to limit).map(v => "Value_" + v)
> > > }, s => println("submit " + s))
>
> > > - For pre-provided options list
> > > AutoComplete.autocompleteObj(/*same params as bfore*/)
>
> > > This may break your app but I think it is very easy to update it.
>
> > > I also fixed some bugs:
> > > 1. It didn;t work if the container cookies were turned off
> > > 2. hovering on the options list did not work on Ubuntu FF3 at least
> > > due to a capitalizated LI equality test.
>
> > > If you encounter any problems, please let me know.
>
> > > Br's,
> > > Marius
>
> > > On Jun 8, 12:34 pm, Kevin Wright
> > > wrote:
>
> > > > +1
>
> > > > As an evolving framework, it definitely makes more sense to favour
> > > > consistency over backward compatibility at this stage
>
> > > > On Mon, Jun 8, 2009 at 9:00 AM, marius d.
> > > > wrote:
>
> > > > > Other folks, please speak up ! :) ... I will soon migrate this into a
> > > > > Lift widget.
>
> > > > > Br's,
> > > > > Marius
>
> > > > > On Jun 6, 4:53 pm, David Pollak wrote:
> > > > > > I think I'm using in one place in one project so my api breakage
> > > > > > factor
> > > > > is
> > > > > > low. I'm okay with moving it unless someone else is going to feel
> > > > > > real
> > > > > > pain.
>
> > > > > > On Jun 6, 2009 12:24 AM, "Marius" wrote:
>
> > > > > > Is there a reason why the JQuery autocomplete is not a Lift widget
> > > > > > but
> > > > > > instead it lives in http/jquery package? .. I remember a long time
> > > > > > ago
> > > > > > me putting it in the jquery package to separate SHtml stuff that is
> > > > > > dependent on JQuery to the others.
>
> > > > > > Thoughts?
>
> > > > > > Br',
> > > > > > Marius
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
yes yes yes ... entirely my bad as I missed that out ...
I'll correct it very soon.
Marius
On Jun 16, 3:07 am, "Bryan." wrote:
> Hi Marius,
>
> I just updated to the tip and got a build failure:
>
> [WARNING] /home/bryan/public-repos/git/liftweb/sites/example/src/main/
> scala/net/liftweb/example/snippet/Ajax.scala:65: error: value
> autocomplete is not a member of object net.liftweb.http.jquery.JqSHtml
> [WARNING] "auto" -> JqSHtml.autocomplete("", buildQuery _, _
> => ()))
>
> --Bryan
>
> On Jun 15, 2:16 pm, "marius d." wrote:
>
> > Folks,
>
> > I just made the autocomplete a Lift widget so it does not exist
> > anymore in JqShtml object. Here is an example on how to use it:
>
> > - For Ajax autocomplete
> > AutoComplete("", (current, limit) => {
> > println("current = " + current)
> > (1 to limit).map(v => "Value_" + v)
> > }, s => println("submit " + s))
>
> > - For pre-provided options list
> > AutoComplete.autocompleteObj(/*same params as bfore*/)
>
> > This may break your app but I think it is very easy to update it.
>
> > I also fixed some bugs:
> > 1. It didn;t work if the container cookies were turned off
> > 2. hovering on the options list did not work on Ubuntu FF3 at least
> > due to a capitalizated LI equality test.
>
> > If you encounter any problems, please let me know.
>
> > Br's,
> > Marius
>
> > On Jun 8, 12:34 pm, Kevin Wright
> > wrote:
>
> > > +1
>
> > > As an evolving framework, it definitely makes more sense to favour
> > > consistency over backward compatibility at this stage
>
> > > On Mon, Jun 8, 2009 at 9:00 AM, marius d. wrote:
>
> > > > Other folks, please speak up ! :) ... I will soon migrate this into a
> > > > Lift widget.
>
> > > > Br's,
> > > > Marius
>
> > > > On Jun 6, 4:53 pm, David Pollak wrote:
> > > > > I think I'm using in one place in one project so my api breakage
> > > > > factor
> > > > is
> > > > > low. I'm okay with moving it unless someone else is going to feel
> > > > > real
> > > > > pain.
>
> > > > > On Jun 6, 2009 12:24 AM, "Marius" wrote:
>
> > > > > Is there a reason why the JQuery autocomplete is not a Lift widget but
> > > > > instead it lives in http/jquery package? .. I remember a long time ago
> > > > > me putting it in the jquery package to separate SHtml stuff that is
> > > > > dependent on JQuery to the others.
>
> > > > > Thoughts?
>
> > > > > Br',
> > > > > Marius
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
Hi Marius,
I just updated to the tip and got a build failure:
[WARNING] /home/bryan/public-repos/git/liftweb/sites/example/src/main/
scala/net/liftweb/example/snippet/Ajax.scala:65: error: value
autocomplete is not a member of object net.liftweb.http.jquery.JqSHtml
[WARNING] "auto" -> JqSHtml.autocomplete("", buildQuery _, _
=> ()))
--Bryan
On Jun 15, 2:16 pm, "marius d." wrote:
> Folks,
>
> I just made the autocomplete a Lift widget so it does not exist
> anymore in JqShtml object. Here is an example on how to use it:
>
> - For Ajax autocomplete
> AutoComplete("", (current, limit) => {
> println("current = " + current)
> (1 to limit).map(v => "Value_" + v)
> }, s => println("submit " + s))
>
> - For pre-provided options list
> AutoComplete.autocompleteObj(/*same params as bfore*/)
>
> This may break your app but I think it is very easy to update it.
>
> I also fixed some bugs:
> 1. It didn;t work if the container cookies were turned off
> 2. hovering on the options list did not work on Ubuntu FF3 at least
> due to a capitalizated LI equality test.
>
> If you encounter any problems, please let me know.
>
> Br's,
> Marius
>
> On Jun 8, 12:34 pm, Kevin Wright
> wrote:
>
> > +1
>
> > As an evolving framework, it definitely makes more sense to favour
> > consistency over backward compatibility at this stage
>
> > On Mon, Jun 8, 2009 at 9:00 AM, marius d. wrote:
>
> > > Other folks, please speak up ! :) ... I will soon migrate this into a
> > > Lift widget.
>
> > > Br's,
> > > Marius
>
> > > On Jun 6, 4:53 pm, David Pollak wrote:
> > > > I think I'm using in one place in one project so my api breakage factor
> > > is
> > > > low. I'm okay with moving it unless someone else is going to feel real
> > > > pain.
>
> > > > On Jun 6, 2009 12:24 AM, "Marius" wrote:
>
> > > > Is there a reason why the JQuery autocomplete is not a Lift widget but
> > > > instead it lives in http/jquery package? .. I remember a long time ago
> > > > me putting it in the jquery package to separate SHtml stuff that is
> > > > dependent on JQuery to the others.
>
> > > > Thoughts?
>
> > > > Br',
> > > > Marius
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
Folks,
I just made the autocomplete a Lift widget so it does not exist
anymore in JqShtml object. Here is an example on how to use it:
- For Ajax autocomplete
AutoComplete("", (current, limit) => {
println("current = " + current)
(1 to limit).map(v => "Value_" + v)
}, s => println("submit " + s))
- For pre-provided options list
AutoComplete.autocompleteObj(/*same params as bfore*/)
This may break your app but I think it is very easy to update it.
I also fixed some bugs:
1. It didn;t work if the container cookies were turned off
2. hovering on the options list did not work on Ubuntu FF3 at least
due to a capitalizated LI equality test.
If you encounter any problems, please let me know.
Br's,
Marius
On Jun 8, 12:34 pm, Kevin Wright
wrote:
> +1
>
> As an evolving framework, it definitely makes more sense to favour
> consistency over backward compatibility at this stage
>
> On Mon, Jun 8, 2009 at 9:00 AM, marius d. wrote:
>
> > Other folks, please speak up ! :) ... I will soon migrate this into a
> > Lift widget.
>
> > Br's,
> > Marius
>
> > On Jun 6, 4:53 pm, David Pollak wrote:
> > > I think I'm using in one place in one project so my api breakage factor
> > is
> > > low. I'm okay with moving it unless someone else is going to feel real
> > > pain.
>
> > > On Jun 6, 2009 12:24 AM, "Marius" wrote:
>
> > > Is there a reason why the JQuery autocomplete is not a Lift widget but
> > > instead it lives in http/jquery package? .. I remember a long time ago
> > > me putting it in the jquery package to separate SHtml stuff that is
> > > dependent on JQuery to the others.
>
> > > Thoughts?
>
> > > Br',
> > > Marius
--~--~-~--~~~---~--~~
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...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
+1 As an evolving framework, it definitely makes more sense to favour consistency over backward compatibility at this stage On Mon, Jun 8, 2009 at 9:00 AM, marius d. wrote: > > Other folks, please speak up ! :) ... I will soon migrate this into a > Lift widget. > > > Br's, > Marius > > On Jun 6, 4:53 pm, David Pollak wrote: > > I think I'm using in one place in one project so my api breakage factor > is > > low. I'm okay with moving it unless someone else is going to feel real > > pain. > > > > On Jun 6, 2009 12:24 AM, "Marius" wrote: > > > > Is there a reason why the JQuery autocomplete is not a Lift widget but > > instead it lives in http/jquery package? .. I remember a long time ago > > me putting it in the jquery package to separate SHtml stuff that is > > dependent on JQuery to the others. > > > > Thoughts? > > > > Br', > > Marius > > > --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Lift Jquery autocomplete *** API CHANGE CANDIDATE ***
Other folks, please speak up ! :) ... I will soon migrate this into a Lift widget. Br's, Marius On Jun 6, 4:53 pm, David Pollak wrote: > I think I'm using in one place in one project so my api breakage factor is > low. I'm okay with moving it unless someone else is going to feel real > pain. > > On Jun 6, 2009 12:24 AM, "Marius" wrote: > > Is there a reason why the JQuery autocomplete is not a Lift widget but > instead it lives in http/jquery package? .. I remember a long time ago > me putting it in the jquery package to separate SHtml stuff that is > dependent on JQuery to the others. > > Thoughts? > > Br', > Marius --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
