[Lift] Re: Mapper to Record ORM
As far as I remember David said once, that Mapper will be anyway a part of Lift and it will be not deprecated. Regards, Mateusz On Thu, Mar 19, 2009 at 8:31 PM, Alex wrote: > > I have been looking through Lift documents trying to figure out what > to do about an ORM for my first Lift app. The migration from Mapper > to Record also adds uncertainty. I don't really want to commit to an > ORM that will be deprecated in 2 months. Is there somewhere I can > read about the design goals, migration path, and development status of > Record? > > > > > --~--~-~--~~~---~--~~ 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-friendly Web Hosting
I recommed http://www.slicehost.com/I have not done any serious Lift work there, but I have checked that Lift works well on the 256 slice. It's quite cheap and the first service I found to work "out of the box" without any problems for such money. I did install ubuntu, then apt-get ant, maven, java, jetty, etc Cheers, Mateusz On Tue, Mar 10, 2009 at 11:37 AM, Timothy Perrett wrote: > > Generally, we run our own servers with root access and configure > Jetty, or another servlet container to host the lift app. Its no > different than hosting any other JVM based web application in that > sense. > > Cheers, Tim > > > > On Tue, Mar 10, 2009 at 1:03 AM, Jeff Chen >wrote: > > > > > Any suggestion/experience on a lift-friendly web hosting service? > Thanks. > > > > --~--~-~--~~~---~--~~ 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: Can or Box or something else
If Maybe should be not used because of possible name clash in Scala library then how about considering synonyms: Possible and Perhaps? On Fri, Dec 26, 2008 at 10:31 AM, Caoyuan wrote: > > and "Pack" ? > > On Fri, Dec 26, 2008 at 8:35 AM, Marc Boschma > > > wrote: > > > > I know David has resigned to keeping 'Can', but wouldn't 'Jar' be an > > alternative? That way Empty and Full still make sense... > > > > Initially I thought 'Tin' sounded better but I recognise that term > > wouldn't be as universal. > > > > Marc > > > > On 26/12/2008, at 4:14 AM, Michael Campbell wrote: > > > >> > >> David Pollak wrote: > >>> Folks, > >>> > >>> Over the year that Lift has had Can[T] as a replacement for Scala's > >>> Option[T], the name "Can" has required a lot of explaining. > >> > >> > >> I've never liked "Can" as a name; always thinking that the opposite > >> of one > >> should be a "Can't". I'm sure it's my own issue to solve, but it's > >> cognitively dissonant to me. > >> > >> Any other container name works better for me, although of the ones > >> you listed, > >> I like "Box". > >> > >> > >> -- > >> Twitter: http://twitter.com/campbellmichael > >> > >> > > > > > > > > > > > > > > --~--~-~--~~~---~--~~ 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: Can or Box or something else
Result +1 Quite short, only one selfexplaining imo and describes the purpose it serves well. The only downsides of this name is +3 characters and the fact that the class could be used also as non result but for other purpose. On Sun, Dec 21, 2008 at 3:32 PM, Derek Chen-Becker wrote: > I think that the previously mentioned "Box" would be the only other thing > that has > >1. The same semantic meaning of "container". Well, as Tim pointed out >this is a US thing for Can... >2. The same brevity. I agree with David that commonly used constructs >should be short > > If it was going to change at all, this would be it. > > Derek > > > On Sat, Dec 20, 2008 at 11:13 PM, Josh Suereth > wrote: > >> >> >> On Sat, Dec 20, 2008 at 2:37 PM, Oliver Lambert wrote: >> >>> Yup, when you chose the original name, you did a good job - why second >>> guess yourself now. Can we just leave it the way it is. >>> >> >> Pun intended >> >> >> As to my vote (if I'm allowed one)... >> >> Can was slightly confusing, but looking at it vs Option makes a lot of >> sense. Option is also slightly confusing, because I expected it to behave >> like Either. Either is a great name, as you can tell what it's doing. >> >> Result seems ok, but I would vote for something more like Storage. Can >> is pretty succinct, and once you know how to use it, it's not hard to >> remember the convention. >> >> So I'd swing on the side of sticking with Can unless a really good name is >> discovered. >> >> >> > > > > --~--~-~--~~~---~--~~ 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: The first Lift tutorial: a ToDo application
The IdPK paragraph explains trait behaviour in Scala but doesn't say what does this trait mean. One can suspect it flags the class to have primary key but it is not obvious. lift:Util.out I think the name is too generic. I know it is a tutorial but it may be seen as kind of small "code smell". How about sticking to the meaning? TodoApp:whenLogged .. or sth like this? "Lift will convert underscore separated names to CamelCase names when it looks up classes". Some small example maybe also useful. This paragraph contains lot of rules which could be expressed better as a list .. maybe with a title: Things to remember when binding tags to classes. Regards, Mateusz On Sat, Dec 6, 2008 at 3:42 AM, Kris Nuttycombe <[EMAIL PROTECTED]>wrote: > Also, for consistency: > > > > > David > Pollak > > > > > => > > > > > David > Pollak > > > > > > On Fri, Dec 5, 2008 at 7:36 PM, Kris Nuttycombe <[EMAIL PROTECTED] > > wrote: > >> Very nice! On the minor typo front: >> >> >> Please Log In Dude >> >> >> Should be >> >> >> Please Log In Dude >> >> >> Kris >> >> >> On Fri, Dec 5, 2008 at 7:18 PM, TylerWeir <[EMAIL PROTECTED]> wrote: >> >>> >>> Looks good Dave, good clear explanations. >>> >>> 2 suggestions: >>> 1. >>> 1.13 Display and Editting to do items --> >>> 1.13 Display and Editing to do items >>> >>> 2. >>> You may want to toss in a few screenshots of the app. >>> >>> Ty >>> >>> On Dec 5, 8:09 pm, "David Pollak" <[EMAIL PROTECTED]> >>> wrote: >>> > Folks, >>> > >>> > I've got a first draft of the first Lift tutorial: a ToDo application. >>> > >>> > The application demonstrates creating a new Lift project, creating a >>> model, >>> > linking the view to logic, adding validation and form input to the >>> model, >>> > creating forms, and doing Ajax calls. >>> > >>> > I'm enclosing the PDF of the tutorial along with the resulting >>> application. >>> > >>> > Please let me know if you've got feedback on it. >>> > >>> > Thanks, >>> > >>> > David >>> > >>> > -- >>> > Lift, the simply functional web frameworkhttp://liftweb.net >>> > Collaborative Task Managementhttp://much4.us >>> > Follow me:http://twitter.com/dpp >>> > Git some:http://github.com/dpp >>> > >>> > todo_steps.pdf >>> > 206KViewDownload >>> > >>> > todo.tgz >>> > 9KViewDownload >>> >>> >> > > > > --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: JPA and Record
I'm not sure if my idea is good but I think that wrong ideas are better the none so I post it. Some time ago there was a discussion about using scala compiler plugins to simplify lift users experience. I'm not sure what are your opinions about using it in lift, however I guess it could help alot in this case. Class extending Record could be specially treated by compiler and thus record objects could be specified in a very simple way. I know there is added dependency to the build process but imho it's much better then using code generators because it is one of the compilation phases and it must be run for the code to compile. On Tue, Nov 25, 2008 at 10:29 PM, Kris Nuttycombe <[EMAIL PROTECTED] > wrote: > Ah, right, so if you're using property-based inference anyway, it's not an > issue. Never mind. > > > On Tue, Nov 25, 2008 at 2:26 PM, Derek Chen-Becker <[EMAIL PROTECTED]>wrote: > >> On Tue, Nov 25, 2008 at 1:40 PM, Kris Nuttycombe < >> [EMAIL PROTECTED]> wrote: >>> >>> Remember that additionally in JPA, a bare unannotated field on an object >>> will be inferred as persistent unless annotated @Transient (or, in java, >>> unless it is declared with the "transient" modifier) >>> >> >> My reading of the JPA spec, section 2.1.1 is that persistent state is >> either field-based or property-based, and is determined by where you place >> your annotations. The @Transient is required for either method where you >> have a field or property that isn't supposed to be part of the state. >> >> Derek >> >> >> > > > > --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Query param for SQL "like"?
So you mean I can start my weekend now ;) ? On Fri, Nov 21, 2008 at 8:06 PM, David Pollak <[EMAIL PROTECTED] > wrote: > I've just committed up a Like operator in Mapper. Please give it a try and > let me know how it works. > > > On Fri, Nov 21, 2008 at 8:02 AM, David Pollak < > [EMAIL PROTECTED]> wrote: > >> I'll try to add the feature this weekend. >> >> >> On Fri, Nov 21, 2008 at 7:19 AM, Joachim A. <[EMAIL PROTECTED] >> > wrote: >> >>> >>> Hi, >>> I'm using 0.10-SNAPSHOT and it's mapper classes. >>> >>> I"m wondering how I can do something like "select * from Test t where >>> t.name LIKE '%test%. >>> >>> I've found the classes QueryParam, OprEnum and Cmp. I've read in the >>> source code but can't see a way to extend this mechanism wih new >>> operators. >>> I've also found BySql and InThing but I don't know what they do :) >>> >>> Can I do SQL's Like operator with the mapper classes? If yes, how? >>> >>> Thank you very much! >>> Joachim >>> >>> >>> >> >> >> -- >> Lift, the simply functional web framework http://liftweb.net >> Collaborative Task Management http://much4.us >> Follow me: http://twitter.com/dpp >> Git some: http://github.com/dpp >> > > > > -- > Lift, the simply functional web framework http://liftweb.net > Collaborative Task Management http://much4.us > 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: lift:surround and multiple templates
I also lost half a day with this error. Is this rule at least documented anywhere? Regards, Mateusz On Thu, Sep 25, 2008 at 9:38 PM, Charles F. Munat <[EMAIL PROTECTED]> wrote: > > Ah, ha! I knew it had to be something simple like that. Good to know > that hidden-templates can't reuse the names of directories. Thanks! > > Chas. > > David Pollak wrote: > > Charles, > > > > The "admin" template was conflicting with the /admin/ directory. Change > > the name of the template to admin2.html rather than admin.html and > > change your 'with="admin"' to 'with="admin2"' and it'll work. > > > > Thanks, > > > > David > > > > Charles F. Munat wrote: > >> I changed the calling template to (exactly): > >> > >> > >> > >> I changed admin.html to (exactly): > >> > >> > >> > >> I did mvn clean and mvn jetty:run -U. > >> > >> I get the same error: > >> > >> Exception occured while processing / > >> > >> Message: java.lang.IllegalArgumentException: line 6 does not exist > >> scala.io.Source.getLine(Source.scala:280) > >> scala.io.Source.report(Source.scala:368) > >> scala.io.Source.reportError(Source.scala:355) > >> scala.io.Source.reportError(Source.scala:344) > >> > > scala.xml.parsing.MarkupParser$class.reportSyntaxError(MarkupParser.scala:1113) > >> > > net.liftweb.util.PCDataXmlParser.reportSyntaxError(PCDataMarkupParser.scala:77) > >> > > scala.xml.parsing.MarkupParser$class.reportSyntaxError(MarkupParser.scala:1117) > >> > > net.liftweb.util.PCDataXmlParser.reportSyntaxError(PCDataMarkupParser.scala:77) > >> > scala.xml.parsing.MarkupParser$class.document(MarkupParser.scala:186) > >> > net.liftweb.util.PCDataXmlParser.document(PCDataMarkupParser.scala:77) > >> > net.liftweb.util.PCDataXmlParser$.apply(PCDataMarkupParser.scala:88) > >> > > net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1$$anonfun$apply$49.apply(LiftSession.scala:1036) > >> > > net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1$$anonfun$apply$49.apply(LiftSession.scala:1036) > >> net.liftweb.util.Full.flatMap(Can.scala:266) > >> > > net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1.apply(LiftSession.scala:1036) > >> > > net.liftweb.http.TemplateFinder$$anonfun$findAnyTemplate$1.apply(LiftSession.scala:1036) > >> scala.Function1$$anonfun$andThen$1.apply(Function1.scala:48) > >> scala.Stream$class.flatMap(Stream.scala:430) > >> scala.List$$anon$1.flatMap(List.scala:1307) > >> scala.Stream$$anonfun$flatMap$1.apply(Stream.scala:435) > >> scala.Stream$$anonfun$flatMap$1.apply(Stream.scala:435) > >> scala.Stream$class.append(Stream.scala:255) > >> scala.List$$anon$1.append(List.scala:1307) > >> scala.Stream$class.flatMap(Stream.scala:435) > >> scala.List$$anon$1.flatMap(List.scala:1307) > >> scala.Stream$$anonfun$flatMap$1.apply(Stream.scala:435) > >> scala.Stream$$anonfun$flatMap$1.apply(Stream.scala:435) > >> scala.Stream$class.append(Stream.scala:255) > >> scala.List$$anon$1.append(List.scala:1307) > >> scala.Stream$class.flatMap(Stream.scala:435) > >> scala.List$$anon$1.flatMap(List.scala:1307) > >> scala.List$$anon$1.flatMap(List.scala:1307) > >> net.liftweb.util.ListHelpers$class.first(ListHelpers.scala:35) > >> net.liftweb.util.Helpers$.first(Helpers.scala:26) > >> > net.liftweb.http.TemplateFinder$.findAnyTemplate(LiftSession.scala:1036) > >> net.liftweb.http.LiftSession.findTemplate(LiftSession.scala:509) > >> net.liftweb.http.LiftSession.findAndMerge(LiftSession.scala:819) > >> net.liftweb.http.LiftSession.net > $liftweb$http$LiftSession$$processSurroundElement(LiftSession.scala:813) > >> > > net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:653) > >> > > net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:647) > >> scala.PartialFunction$$anon$1.apply(PartialFunction.scala:38) > >> > > net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$35.apply(LiftSession.scala:671) > >> > > net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$35.apply(LiftSession.scala:671) > >> net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24) > >> net.liftweb.http.S$.setVars(S.scala:589) > >> > > net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1.apply(LiftSession.scala:671) > >> > > net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1.apply(LiftSession.scala:668) > >> scala.Seq$class.flatMap(Seq.scala:267) > >> scala.xml.NodeSeq.flatMap(NodeSeq.scala:34) > >> > net.liftweb.http.LiftSession.processSurroundAndInclude(LiftSession.scala:667) > >> > net.liftweb.http.LiftSession$$anonfun$8.apply(LiftSession.scala:344) > >> > net.liftweb.http.LiftSession$$anonfun$8.apply(LiftSession.scala:344) > >> net.liftweb.util.Full.map(Can.scala:264) > >> net.liftweb.http.LiftSession.processReques
[Lift] Re: JPA w/Scala
http://www.oracle.com/technology/products/ias/toplink/jpa/howto/id-generation.html
On Mon, Sep 8, 2008 at 4:43 PM, Tim Perrett <[EMAIL PROTECTED]> wrote:
>
> Hmmm, I've tried:
>
> @Id
> @GeneratedValue(){val strategy = GenerationType.AUTO}
> @Column(){val insertable = false}
> var id : Long = _
>
> But yet its still being included in the query, any ideas?
>
> Cheers, Tim
> >
>
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: SiteMaps and multiple menus
Just a guess. The "hidden" part?
On Mon, Sep 8, 2008 at 1:34 AM, Charles F. Munat <[EMAIL PROTECTED]> wrote:
>
> Hmm. This isn't working. When I put on
> the page, I get blank output, i.e. this:
>
>
>
> Becomes this:
>
>
>
> I notice that in your thread you say:
>
> "If the menu item can be displayed, an href="...">text will be generated, otherwise a blank will be returned."
>
> What does "if the menu item can be displayed" mean? Here is the relevant
> portion of the site map:
>
> Menu(Loc("home", List("index"), "Home", Hidden))
>
> Where am I going wrong?
>
> Chas.
>
>
>
> David Pollak wrote:
> > Make the "top of the page" sitemap elements Hidden. This means they
> > will not be displayed by default, but are accessible as long as the
> > access control rules are me. On the top bar, do > name="about"/> etc. to display the items. For more, see
> >
> http://groups.google.com/group/liftweb/browse_thread/thread/dbdf6a17b9704c99/30f5168e87161f74?hl=en&lnk=gst&q=new+sitemap%2Fmenu+features
> > <
> http://groups.google.com/group/liftweb/browse_thread/thread/dbdf6a17b9704c99/30f5168e87161f74?hl=en&lnk=gst&q=new+sitemap%2Fmenu+features
> >
> >
> >
> > On Sat, Sep 6, 2008 at 10:54 PM, Charles F. Munat <[EMAIL PROTECTED]
> > > wrote:
> >
> >
> > So how would one create a site map and then break it into two or more
> > pieces and show those pieces on different parts of the page?
> >
> > I want one menu across the top of the page for certain pages (home,
> > about, contact, login, etc.), then a general navigation bar down the
> > left side of the page, and finally a couple of links (terms of use,
> > privacy policy, maybe a help link that's only visible when logged in)
> at
> > the bottom of the page.
> >
> > Is there an easy way to do this? It seems like there's only room for
> one
> > site map.
> >
> > Chas.
> >
> > Derek Chen-Becker wrote:
> > > Another note, you can put conditionals on whether to show menu
> > items via
> > > the If, Test and Unless clauses :)
> > >
> > > On Sat, Sep 6, 2008 at 11:09 PM, Derek Chen-Becker
> > > <[EMAIL PROTECTED]
> > >>
> wrote:
> > >
> > > Thanks, I'll add that in. You can also craft a link so that
> > entire
> > > subdirectory trees are permitted based on matching the head
> > of the list.
> > >
> > > Derek
> > >
> > >
> > > On Sat, Sep 6, 2008 at 6:57 PM, Tim Perrett
> > <[EMAIL PROTECTED]
> > > >>
> > wrote:
> > >
> > >
> > > Oh yes of course!
> > >
> > > Ergo, the sitemap should be:
> > >
> > >val entries = SiteMap(Menu(Loc("Home", "index" :: Nil ,
> ?
> > > ("Home"))),
> > > Menu(Loc("Authors", "authors" :: "list"
> > :: Nil, ?
> > > ("Author List"))),
> > > Menu(Loc("Add Author", "authors" ::
> > "add" :: Nil, ?
> > > ("Add Author"), Hidden)),
> > > Menu(Loc("Books", "books" :: "list" ::
> > Nil, ?("Book
> > > List"))),
> > > Menu(Loc("Add Book", "books" :: "add" ::
> > Nil,
> > > ?("Add
> > > Book"), Hidden)),
> > > Menu(Loc("BookSearch", "books" ::
> > "search" ::
> > > Nil, ?
> > > ("Book Search"
> > >
> > > Cheers
> > >
> > > Tim
> > >
> > >
> > >
> > >
> > > >
> >
> >
> >
> >
> >
> > --
> > Lift, the simply functional web framework http://liftweb.net
> > Collaborative Task Management http://much4.us
> > 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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
