[Lift] Re: Question about Lift/Scala Lift Discussion Board
My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago and have been messing around with it a lot! I am a Ruby on Rails programmer and it seems like Ruby is doing a fine job serving the web programmers community. Recently, I read an article about Twitter running RoR and it crashing after a while. They decided to switch to Scala because it's scalable unlike Ruby. I am planning on developing a large website that will require lots of CPU/Database usage and I was wondering if Scala/Lift is the way to do it? I'm not a fan of Google Groups, they are not very user friendly, so I created a forum specially for Lift developers that like to discuss topics about the Scala/Lift programming language. If you want to help start the forum and post a couple topics I would greatly appreciate it. The link ishttp://www.liftforum.com. It's a new forum so there isn't much content on it yet. 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: self-reference relationship
Are your objects persisted, and, if so, are you using Mapper or JPA/Hibernate (or something else)? Chas. surfman wrote: I spent two days finishing following todo and pocketchange. Both apps run well on my machine, and I understand I need more helpful tutorial, but no idea where to find them. I googled for a while, nothing more helpful. I want to know how to handle a self-reference relationship in Lift. and I also appreciate if anyone let me know where I may find more practical tutorial or get further steps onto Lift? Thanks in advance. --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago and have been messing around with it a lot! I am a Ruby on Rails programmer and it seems like Ruby is doing a fine job serving the web programmers community. Recently, I read an article about Twitter running RoR and it crashing after a while. They decided to switch to Scala because it's scalable unlike Ruby. I am planning on developing a large website that will require lots of CPU/Database usage and I was wondering if Scala/Lift is the way to do it? I'm not a fan of Google Groups, they are not very user friendly, so I created a forum specially for Lift developers that
[Lift] Re: Question about Lift/Scala Lift Discussion Board
I really don't like Google Groups because it's a mess. Posts on here are hard to read and unorganized. I'm typing this post right now and I don't have any options for formatting. I think we should have a forum for Lift to get more people interested. When I first saw this group here on google, I was like are you serious?. Do you know any other programming language that has an active google group? Another thing is that it's hard to search the group. Forums are made to be searchable and easily indexed by search engines. On Aug 30, 9:20 am, Naftoli Gugenheim naftoli...@gmail.com wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm,
[Lift] Re: self-reference relationship
my case will be simple like this, a user table has column manager where could holding another user's id. rails and grails both have special syntax to create this kind of self-reference when creating the model. I want to know how Lift handle this? Thanks. On Aug 30, 2:43 am, Charles F. Munat c...@munat.com wrote: Are your objects persisted, and, if so, are you using Mapper or JPA/Hibernate (or something else)? Chas. surfman wrote: I spent two days finishing following todo and pocketchange. Both apps run well on my machine, and I understand I need more helpful tutorial, but no idea where to find them. I googled for a while, nothing more helpful. I want to know how to handle a self-reference relationship in Lift. and I also appreciate if anyone let me know where I may find more practical tutorial or get further steps onto Lift? Thanks in advance. --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
What? ... Is there on ONE forum about Java, Scala, Spring, Rail etc? ... did all Java forums needed James Gosling approval ? .. Come on .. So yes people can talk about it make they own wikis,forums,blogs ... internet is free you know. I have tons of respect for David and this community and I don't need to write this down here but IMO let people know about Lift Scala by whatever means. It doesn't have to be a single information channel. I hate when I see such a dictatorial attitude about things ... Br's, Marius On Aug 30, 4:20 pm, Naftoli Gugenheim naftoli...@gmail.com wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem
[Lift] Re: authentication and access control
Thanks David,
That does help, yes. My first toy app, which I wrote for a company demo,
used lift 1.0 and mapper. I dug into the MegaProtoUser source and
remember how it worked (providing its own site menu configurations with
access control there). Role-based restrictions could be done much the
same way. Part of my issue with that is probably invalid - I'm
accustomed to the practice of such configurations being stored outside
of application code (XML).
Having known that, I guess my question was focused more on how lift
remembers the user. I think it was using the S object, which ultimately
stores keyed objects on the session, right?
Thanks again for your dedication and commitment to the lift community.
chris
David Pollak wrote:
On Thu, Aug 27, 2009 at 6:42 PM, Chris Lewis burningodzi...@gmail.com
mailto:burningodzi...@gmail.com wrote:
Lift users,
I'm curious what you all are using for user access control (Mapper users
excluded). I'm seriously evaluating lift for a project that will use
JPA. My full time job uses Spring Security, which while nice in that it
stays out of the way, is too clunky for my tastes. I haven't dissected
how lift implements it with Mapper, but wanted to ask the group first.
Thanks!
For HTML access control, Lift's SiteMap offers URL level protection of
pages (and menu generation based on the access control rules.) For each
Loc (location) in your sitemap, you can chain together If() and Unless()
clauses to define what rules are applied to each page. These rules are
based on invoking functions (e.g., User.superUser_?) and can be
arbitrarily complex.
For protecting non-sitemap resources (stuff that's served up via a
custom dispatch [DispatchPF]), it's best practice to put a guard in the
partial function:
{
case Req(api :: accounts :: Nil, _, GetRequest) if
currentUserCanViewAccounts_? = renderAccounts _
}
Hope this helps.
chris
--
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] Dependency Injection in Lift
I like the Lift framework. It has its rough edges, but it's a great way to get into web app development using scala. It borrows many good ideas from other frameworks, most notably its convention over configuration structure (rails) and its scriptless view layer (wicket). One thing I'm not a big fan of is its baked-in database layer, the Mapper (now in flux and being reborn as Record), and so was pleased to find the JPA archetype in the 1.1 tree. Using this archetype, you get a barebones but functioning lift app using pure JPA. This is a great start, but when I poked around the snippets I saw two things that troubled me: The underlying entity manager API leaks directly into what would be the service layer API; a single object exposed as Model. The snippet code is hardwired to Model, which uses it directly as a global DAO. This archetype is still in development, and it very well may change. It's carries a nature of being experimental; showing you how it can be done, but probably not how it should be done. However, it highlighted an issue I have with Lift, one that the boring enterprise crowd has solved: dependency injection. I have an admittedly specific idea in mind for what I want to implement in my would-be Lift app: I want to be able to declare a few fields and annotate them so that a layer above will provide me with acceptable instances. Yeah, I want to inject DAOs in the oh-so-familiar Guice/Spring/T5 IoC way. I like this partially because it's familiar, but also because it provides me with loosely coupled code. There's been some good discussion on the subject of implementing dependency injection in Scala using mere language constructs. I dove into this subject, starting with chapter 27 of [http://www.artima.com/shop/programming_in_scala]: Modular Programming Using Objects. It's a good read, and I recommend the book. After that I found my way to some relevant posts in the blogs of Debasish Ghosh and Jonas Boner, respectively: http://debasishg.blogspot.com/2008/02/scala-to-di-or-not-to-di.html http://jonasboner.com/2008/10/06/real-world-scala-dependency-injection-di.html Very cool indeed, but I've slightly digressed. What I want to explore is how to loosely couple the persistence implementation (be it JPA, JDO, or a baked in model) with the accessing of persistent objects. I don't see how the aforementioned technique (the cake pattern) would help in the case of lift snippets, because we don't have any kind of hooks where we can provide configuration of snippets (at least, not that I know of). This is exactly the issue that DI solves. So what are the thoughts of the lift-power users? Is there a way to get this in lift, or would you say that I am doing it wrong? sincerely, chris --~--~-~--~~~---~--~~ 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: Dependency Injection in Lift
Most of DI of Lift is currently done using PartialFunction-s and Function lists that people can set in Boot or for snippets in case on binding functions usign SHtml helpers etc. Personally I'm not at all a fan of Pojo/Poji DI by annotations especially in Scala realm where there are other artifacts such as function composition, monads, mixin composition, higher order functions etc. The other problem with annotations is that we can't currently build annotations in Scala to be visible at runtime, so we'd probably have to code them in Java or use some existent Java annotations ... but this already smells hacky IMHO. If enterprise folks solve one problem by DI by annotation it doesn't mean that this fits in all contexts.Persistence loosely coupling can be achieved in many ways: 1. Implement your own persistence semantic on top of Record 2. Implement your own traits hence your own abstractions 3. etc What we've learned with Lift is the it is OK to give to persistence objects understanding of rendering. Having dumb objects that carry on just data and rely of layers that can do different jobs (render, persist) is IMO not a very good design approach. Having snippets invoking the persistence layer is ok, in fact it is natural for applications. Of course with a proper level of persistence abstraction IF there are chances for the application to use a different persistence mechanism then say JDBC. But many application don't really need such a rigorous decoupling so using mapper/record from snippets makes a lot of sense. Br's, Marius On Aug 30, 6:21 pm, Chris Lewis burningodzi...@gmail.com wrote: I like the Lift framework. It has its rough edges, but it's a great way to get into web app development using scala. It borrows many good ideas from other frameworks, most notably its convention over configuration structure (rails) and its scriptless view layer (wicket). One thing I'm not a big fan of is its baked-in database layer, the Mapper (now in flux and being reborn as Record), and so was pleased to find the JPA archetype in the 1.1 tree. Using this archetype, you get a barebones but functioning lift app using pure JPA. This is a great start, but when I poked around the snippets I saw two things that troubled me: The underlying entity manager API leaks directly into what would be the service layer API; a single object exposed as Model. The snippet code is hardwired to Model, which uses it directly as a global DAO. This archetype is still in development, and it very well may change. It's carries a nature of being experimental; showing you how it can be done, but probably not how it should be done. However, it highlighted an issue I have with Lift, one that the boring enterprise crowd has solved: dependency injection. I have an admittedly specific idea in mind for what I want to implement in my would-be Lift app: I want to be able to declare a few fields and annotate them so that a layer above will provide me with acceptable instances. Yeah, I want to inject DAOs in the oh-so-familiar Guice/Spring/T5 IoC way. I like this partially because it's familiar, but also because it provides me with loosely coupled code. There's been some good discussion on the subject of implementing dependency injection in Scala using mere language constructs. I dove into this subject, starting with chapter 27 of [http://www.artima.com/shop/programming_in_scala]: Modular Programming Using Objects. It's a good read, and I recommend the book. After that I found my way to some relevant posts in the blogs of Debasish Ghosh and Jonas Boner, respectively: http://debasishg.blogspot.com/2008/02/scala-to-di-or-not-to-di.htmlhttp://jonasboner.com/2008/10/06/real-world-scala-dependency-injectio... Very cool indeed, but I've slightly digressed. What I want to explore is how to loosely couple the persistence implementation (be it JPA, JDO, or a baked in model) with the accessing of persistent objects. I don't see how the aforementioned technique (the cake pattern) would help in the case of lift snippets, because we don't have any kind of hooks where we can provide configuration of snippets (at least, not that I know of). This is exactly the issue that DI solves. So what are the thoughts of the lift-power users? Is there a way to get this in lift, or would you say that I am doing it wrong? sincerely, chris --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
I agree with marius. On Aug 30, 11:01 am, marius d. marius.dan...@gmail.com wrote: What? ... Is there on ONE forum about Java, Scala, Spring, Rail etc? ... did all Java forums needed James Gosling approval ? .. Come on .. So yes people can talk about it make they own wikis,forums,blogs ... internet is free you know. I have tons of respect for David and this community and I don't need to write this down here but IMO let people know about Lift Scala by whatever means. It doesn't have to be a single information channel. I hate when I see such a dictatorial attitude about things ... Br's, Marius On Aug 30, 4:20 pm, Naftoli Gugenheim naftoli...@gmail.com wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir
[Lift] Re: Question about Lift/Scala Lift Discussion Board
On Sat, Aug 29, 2009 at 3:59 PM, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago and have been messing around with it a lot! I am a Ruby on Rails programmer and it seems like Ruby is doing a fine job serving the web programmers community. Recently, I read an article about Twitter running RoR and it crashing after a while. They decided to switch to Scala because it's scalable unlike Ruby. I am planning on developing a large website that will require lots of CPU/Database usage and I was wondering if Scala/Lift is the way to do it? I'm not a fan of Google Groups, they are not very user friendly, so I created a forum specially for Lift developers that like to discuss topics about the Scala/Lift programming language. If you want to help start the forum and post a couple topics I would greatly appreciate it. The link is http://www.liftforum.com . It's a new forum so there isn't much content on it yet. I am totally cool with different forums for discussion Lift and Scala. That's all cool. I will continue to treat this forum as my primary place to help folks and I will encourage the Lift committers to support newbies on this forum and to have Lift related discussions (what features, how we add them, etc.) on this forum. Personally, I have not had a lot of issues with repeat questions. The more times people ask the same questions, the more it points out that either (1) we didn't do a particular feature correctly or (2) we need to add something to the Lift wiki or other documentation. I am personally not a fan of forum software... I find that mailing lists (via gmail) with a web-basic history to be ideal and thus Google groups was my choice. I'm open to other options for the primary Lift support forum. We've moved source repositories and wikis a few times. Moving this forum elsewhere is not off the table. In terms of the use of the term Lift, I want to let you know that there will probably be some trademark assertions on the word Lift related to computer programs (I'm not sure the exact trademark category.) So, in the near future, I may ask you not to use the work Lift as a primary designator for the forum. I don't see a split as a bad thing. The Lift community numbers 1,300 people and is the largest Scala-related community. We may not be optimal for providing support to all users of Lift and I welcome other ways to help people build great web sites with Lift. By all means, find ways to help people do better thing with Lift. Thanks, David Thanks. -- 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: Overriding widgets stylesheets
4. Additionally, you have to add this in Boot environment. Often we
end up missing out on this step, or don't get the pattern right :)
ResourceServer.allow {
case _ :: style.css :: Nil = true
}
Of course, you can narrow the PF argument to better adjust to the
need.
Cheers, Indrajit
On Aug 27, 9:06 pm, Marius marius.dan...@gmail.com wrote:
Someone encountered the problem where he couldn't override the
stylesheet used by some widget. Damn I can't find any more that
thread ...
Anyways here it is:
1. Include the widget in your application say monthview.
2. The url to the stylesheet is: /classpath/calendars/monthview/
style.css
3. In order to override this put your changed style.css in WEB-INF/
classes/toserve/calendars/monthview/style.css
This works for me.
Br's,
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: Overriding widgets stylesheets
No you don't have to do this because In Boot you are already calling
CalendarMonthlyView.init
Br's,
Marius
On Aug 30, 7:22 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
4. Additionally, you have to add this in Boot environment. Often we
end up missing out on this step, or don't get the pattern right :)
ResourceServer.allow {
case _ :: style.css :: Nil = true
}
Of course, you can narrow the PF argument to better adjust to the
need.
Cheers, Indrajit
On Aug 27, 9:06 pm, Marius marius.dan...@gmail.com wrote:
Someone encountered the problem where he couldn't override the
stylesheet used by some widget. Damn I can't find any more that
thread ...
Anyways here it is:
1. Include the widget in your application say monthview.
2. The url to the stylesheet is: /classpath/calendars/monthview/
style.css
3. In order to override this put your changed style.css in WEB-INF/
classes/toserve/calendars/monthview/style.css
This works for me.
Br's,
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: Question about Lift/Scala Lift Discussion Board
I agree. I can't imagine starting something like this without first approaching David. Having said that, and pehaps contradictorily, I welcome any initiatives that will further Lift/Scala. On Aug 30, 9:20 am, Naftoli Gugenheim naftoli...@gmail.com wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago and have been messing around with it a lot! I am a Ruby on Rails programmer and it seems like Ruby is doing a fine job serving the web programmers community. Recently, I read an article about Twitter running RoR and it crashing after a while.
[Lift] Re: Overriding widgets stylesheets
Oops, I didn't follow that this is about the bundled
CalendarMonthView.
I stand corrected, ResourceServer.allow {} isn't necessary because
CalendarMonthlyView.init does the needful.
Cheers, Indrajit
On Aug 30, 9:32 pm, marius d. marius.dan...@gmail.com wrote:
No you don't have to do this because In Boot you are already calling
CalendarMonthlyView.init
Br's,
Marius
On Aug 30, 7:22 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
4. Additionally, you have to add this in Boot environment. Often we
end up missing out on this step, or don't get the pattern right :)
ResourceServer.allow {
case _ :: style.css :: Nil = true
}
Of course, you can narrow the PF argument to better adjust to the
need.
Cheers, Indrajit
On Aug 27, 9:06 pm, Marius marius.dan...@gmail.com wrote:
Someone encountered the problem where he couldn't override the
stylesheet used by some widget. Damn I can't find any more that
thread ...
Anyways here it is:
1. Include the widget in your application say monthview.
2. The url to the stylesheet is: /classpath/calendars/monthview/
style.css
3. In order to override this put your changed style.css in WEB-INF/
classes/toserve/calendars/monthview/style.css
This works for me.
Br's,
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: Overriding widgets stylesheets
Yeah ... in general all existent lift widgets have an init method that
needs to be called in boot.
On Aug 30, 8:39 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
Oops, I didn't follow that this is about the bundled
CalendarMonthView.
I stand corrected, ResourceServer.allow {} isn't necessary because
CalendarMonthlyView.init does the needful.
Cheers, Indrajit
On Aug 30, 9:32 pm, marius d. marius.dan...@gmail.com wrote:
No you don't have to do this because In Boot you are already calling
CalendarMonthlyView.init
Br's,
Marius
On Aug 30, 7:22 pm, Indrajit Raychaudhuri indraj...@gmail.com wrote:
4. Additionally, you have to add this in Boot environment. Often we
end up missing out on this step, or don't get the pattern right :)
ResourceServer.allow {
case _ :: style.css :: Nil = true
}
Of course, you can narrow the PF argument to better adjust to the
need.
Cheers, Indrajit
On Aug 27, 9:06 pm, Marius marius.dan...@gmail.com wrote:
Someone encountered the problem where he couldn't override the
stylesheet used by some widget. Damn I can't find any more that
thread ...
Anyways here it is:
1. Include the widget in your application say monthview.
2. The url to the stylesheet is: /classpath/calendars/monthview/
style.css
3. In order to override this put your changed style.css in WEB-INF/
classes/toserve/calendars/monthview/style.css
This works for me.
Br's,
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: Dependency Injection in Lift
I am specifically talking about decoupling my web logic, ie, event handlers for forms in lift snippets, from the persistence layer. As currently implemented, snippets know exactly what persistence mechanism is in use because there is no intermediary API. If I'm using Mapper, my snippets must use the Mapper api. If JPA, the global EM wrapper Model. The same, I imagine, holds true for the Record api. This makes the persistence layer a Leaky Abstraction (http://en.wikipedia.org/wiki/Leaky_abstraction), and I want to avoid that. Most of DI of Lift is currently done using PartialFunction-s and Function lists that people can set in Boot or for snippets in case on binding functions usign SHtml helpers etc. Ok, but how does that help me decouple my web logic from the persistence details? What we've learned with Lift is the it is OK to give to persistence objects understanding of rendering. Having dumb objects that carry on just data and rely of layers that can do different jobs (render, persist) is IMO not a very good design approach. I disagree. An entity, like Author, is nothing more than an expression of a real-world concept modeled in code. It should know about itself, its direct constituents (like a Book collection), anything else that defines its own semantics, and nothing more. How it is stored is none of its business. Don't misunderstand me - I accept that I may be missing something. We agree that the concept of DI is valuable because it helps us keep abstractions loosely coupled. I don't see the problem with annotations, but I am not at all married to them. You point at partial functions and traits to implement abstractions over the persistence layer, but what is missing is how to apply that to snippets. Yes, I could abstract the layer however I want, but my snippets we still be required to get at the layer by calling it directly, instead of having it provided. Can you share some input on that part? Thanks for the discussion, chris marius d. wrote: Most of DI of Lift is currently done using PartialFunction-s and Function lists that people can set in Boot or for snippets in case on binding functions usign SHtml helpers etc. Personally I'm not at all a fan of Pojo/Poji DI by annotations especially in Scala realm where there are other artifacts such as function composition, monads, mixin composition, higher order functions etc. The other problem with annotations is that we can't currently build annotations in Scala to be visible at runtime, so we'd probably have to code them in Java or use some existent Java annotations ... but this already smells hacky IMHO. If enterprise folks solve one problem by DI by annotation it doesn't mean that this fits in all contexts.Persistence loosely coupling can be achieved in many ways: 1. Implement your own persistence semantic on top of Record 2. Implement your own traits hence your own abstractions 3. etc What we've learned with Lift is the it is OK to give to persistence objects understanding of rendering. Having dumb objects that carry on just data and rely of layers that can do different jobs (render, persist) is IMO not a very good design approach. Having snippets invoking the persistence layer is ok, in fact it is natural for applications. Of course with a proper level of persistence abstraction IF there are chances for the application to use a different persistence mechanism then say JDBC. But many application don't really need such a rigorous decoupling so using mapper/record from snippets makes a lot of sense. Br's, Marius On Aug 30, 6:21 pm, Chris Lewis burningodzi...@gmail.com wrote: I like the Lift framework. It has its rough edges, but it's a great way to get into web app development using scala. It borrows many good ideas from other frameworks, most notably its convention over configuration structure (rails) and its scriptless view layer (wicket). One thing I'm not a big fan of is its baked-in database layer, the Mapper (now in flux and being reborn as Record), and so was pleased to find the JPA archetype in the 1.1 tree. Using this archetype, you get a barebones but functioning lift app using pure JPA. This is a great start, but when I poked around the snippets I saw two things that troubled me: The underlying entity manager API leaks directly into what would be the service layer API; a single object exposed as Model. The snippet code is hardwired to Model, which uses it directly as a global DAO. This archetype is still in development, and it very well may change. It's carries a nature of being experimental; showing you how it can be done, but probably not how it should be done. However, it highlighted an issue I have with Lift, one that the boring enterprise crowd has solved: dependency injection. I have an admittedly specific idea in mind for what I want to implement in my would-be Lift app: I want to be able to declare a few fields and
[Lift] Re: Question about Lift/Scala Lift Discussion Board
Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago and have been messing around with it a lot! I am a Ruby on Rails programmer and it seems like Ruby is doing a fine job serving the web programmers community. Recently, I read an article about Twitter running RoR and it crashing after a while. They decided to switch to Scala because it's scalable unlike Ruby. I am planning on developing a large website that will require lots of
[Lift] Re: Modularization of Lift code
David, For all that you've said in defense of Lift's extensibility, answer one question: Could you override def _showAllTemplate in Crudify, without having the source at your disposal? And, this is not an isolated example. Glenn... On Aug 28, 12:05 pm, AlBlue alex.blew...@gmail.com wrote: On Jul 29, 12:55 pm, Heiko Seeberger heiko.seeber...@googlemail.com wrote: Just a quick and dirty reply: In order to get OSGi support LiftRules should delegate *everything* to a Collection of LiftModules. LiftModules can be added to and removed from this collection anytime. Yup, maintaining a collection is the easiest way to use dynamic updates in the future. That said, I've been discussing modularity of scala code generally recently: http://alblue.blogspot.com/2009/08/modularity-for-scala.html If anyone's interested helping out then please drop me a note on my blog. Hopefully we'll be able to extend the work that Heiko has already done and use that to modularise the core library. If successful, this could be used as an approach for both the lift code and apps that depend on lift. Alex --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
I agree that it's kind of silly to talk about DPP's approval. This isn't source code related. Anyone can establish any forum he or she wants to, and if someone wants a separate Lift forum . . . The question, then, in my mind is whether adding a forum adds some needed capability (or visibility) or whether it just splits the group unnecessarily. As for mailing lists, I'm on several for a variety of languages and applications. What exactly does a forum get us? And if that's worth having, then is it better to have the forum in addition to the mailing list, or instead of it? Chas. marius d. wrote: What? ... Is there on ONE forum about Java, Scala, Spring, Rail etc? ... did all Java forums needed James Gosling approval ? .. Come on .. So yes people can talk about it make they own wikis,forums,blogs ... internet is free you know. I have tons of respect for David and this community and I don't need to write this down here but IMO let people know about Lift Scala by whatever means. It doesn't have to be a single information channel. I hate when I see such a dictatorial attitude about things ... Br's, Marius On Aug 30, 4:20 pm, Naftoli Gugenheim naftoli...@gmail.com wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I
[Lift] Re: Question about Lift/Scala Lift Discussion Board
More than 1300 people? Really? Wow. Well, then maybe a second forum isn't premature. Man, I had no idea. When did that happen? Chas. David Pollak wrote: On Sat, Aug 29, 2009 at 3:59 PM, Artem art...@gmail.com mailto:art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago and have been messing around with it a lot! I am a Ruby on Rails programmer and it seems like Ruby is doing a fine job serving the web programmers community. Recently, I read an article about Twitter running RoR and it crashing after a while. They decided to switch to Scala because it's scalable unlike Ruby. I am planning on developing a large website that will require lots of CPU/Database usage and I was wondering if Scala/Lift is the way to do it? I'm not a fan of Google Groups, they are not very user friendly, so I created a forum specially for Lift developers that like to discuss topics about the Scala/Lift programming language. If you want to help start the forum and post a couple topics I would greatly appreciate it. The link is http://www.liftforum.com . It's a new forum so there isn't much content on it yet. I am totally cool with different forums for discussion Lift and Scala. That's all cool. I will continue to treat this forum as my primary place to help folks and I will encourage the Lift committers to support newbies on this forum and to have Lift related discussions (what features, how we add them, etc.) on this forum. Personally, I have not had a lot of issues with repeat questions. The more times people ask the same questions, the more it points out that either (1) we didn't do a particular feature correctly or (2) we need to add something to the Lift wiki or other documentation. I am personally not a fan of forum software... I find that mailing lists (via gmail) with a web-basic history to be ideal and thus Google groups was my choice. I'm open to other options for the primary Lift support forum. We've moved source repositories and wikis a few times. Moving this forum elsewhere is not off the table. In terms of the use of the term Lift, I want to let you know that there will probably be some trademark assertions on the word Lift related to computer programs (I'm not sure the exact trademark category.) So, in the near future, I may ask you not to use the work Lift as a primary designator for the forum. I don't see a split as a bad thing. The Lift community numbers 1,300 people and is the largest Scala-related community. We may not be optimal for providing support to all users of Lift and I welcome other ways to help people build great web sites with Lift. By all means, find ways to help people do better thing with Lift. Thanks, David Thanks. -- 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] Redirecting wiki.liftweb.net to github starting Oct1
Hello, In an effort to consolidate the lift wiki information, we are planning to permanently redirecting wiki.liftweb.net to http://wiki.github.com/dpp/liftweb. However before the switch is made, we are going grab various bits of content off wiki.liftweb and move it over to github. If you have any suggestions for which articles should be migrate, please let me know. Thanks, Xavi --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a
[Lift] Re: Dependency Injection in Lift
Chris Lewis burningodzi...@gmail.com writes: I am specifically talking about decoupling my web logic, ie, event handlers for forms in lift snippets, from the persistence layer. As currently implemented, snippets know exactly what persistence mechanism is in use because there is no intermediary API. Chris, I'm sharing the same concerns as you about the decoupling. For now, I've just accepted it to get started with Lift. But now that our app starts to grow, I think we'll need to find a good solution for this in order to 1) Maintain a good test suite (I'm a strong believer in TDD and automated testing in general. I don't think that having type safety and FP makes tests obsolete). 2) Loosely couple the code to make it maintainable over time One of my big issues right now is how to test snippets that access the persistence/business layer. This is trivial if snippets has some kind of DI, as you could just inject mock objects instead of the real thing. Alas, I haven't found a good solution yet. I do think that Scala provides some language support for this (ie. the articles you linked to) and I would like to pursue this first, before using more heavyweight solutions such as Spring/Guice etc. /Jeppe --~--~-~--~~~---~--~~ 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: Deleting elements after a modal confirmation dialog
Thank you both for your reply but I have to admit that it was an error in my javascript that was preventing my code from working. Apologies for wasting your time. --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
Artem art...@gmail.com writes: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. Probably depends on your definition of user friendly. Personally, I would never frequent a forum on a regular basis (if it turns up in a google search, fine!). I follow quite a few mailing lists and, being email, they all appear to me in a uniform way, in my mail client (I don't use the google groups web interface). But if a new forum pops up and can answer some Lift questions that is great. The more the merrier! There does seem to be a problem with search on google groups though :-) /Jeppe --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
Personally I like mailing lists .. I find it easier for me to try to help people then a traditional forum. For someone who wants to lear Lit perhaps a more traditional forum is more helpful? ... don't really know .. I guess it depends on the person. Br's, Marius On Aug 30, 10:10 pm, Artem art...@gmail.com wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) -
[Lift] Re: Dependency Injection in Lift
One option might be implicit parameters, but it doesn't seem as clean
(could be a knee jerk). I tried defining an implicit param on the form
handler, but then lift couldn't find the mapped handler. Doing this I
believe changes the function signature, and so the reflective call
doesn't see it.
However, you can define a method on your snippet that takes an implicit.
Consider a simple snippet:
trait UserService {
def findByUserName(userName: String) : String
}
object Config {
implicit val us = new UserService() {
def findByUserName(userName: String) = userName
}
}
import Config._
class MySnippet {
def userService(implicit us: UserService) = us
def login(xhtml : NodeSeq) : NodeSeq = {
var userName =
var password =
def doLogin() = {
println(userName + ; + userService.findByUserName(userName))
}
bind(user, xhtml,
userName - SHtml.text(userName, userName = _),
password - SHtml.password(password, password = _),
submit - SHtml.submit(?(Save), doLogin _)
)
}
}
Notice the part in the doLogin closure:
userService.findByUserName(userName)
Because of the universal access principal, we can treat userService, a
single argument function that returns type UserService (a trait), as an
object. Also see how the userService method receives an implicit
parameter. Because we define an object (Config) that provides an
implicit value of that type, and we import that value, the compiler can
provide it implicitly.
One thing about this method is that we have to have a satisfying
implicit value in scope. In a unit test we could easily do it on the
fly, but for normal execution I'm not sure where you can plug something in.
I'd still love to hear more thoughts, and if this method could be at all
usable.
sincerely,
chris
Jeppe Nejsum Madsen wrote:
Chris Lewis burningodzi...@gmail.com writes:
I am specifically talking about decoupling my web logic, ie, event
handlers for forms in lift snippets, from the persistence layer. As
currently implemented, snippets know exactly what persistence mechanism
is in use because there is no intermediary API.
Chris, I'm sharing the same concerns as you about the decoupling. For
now, I've just accepted it to get started with Lift.
But now that our app starts to grow, I think we'll need to find a
good solution for this in order to
1) Maintain a good test suite (I'm a strong believer in TDD and
automated testing in general. I don't think that having type safety and
FP makes tests obsolete).
2) Loosely couple the code to make it maintainable over time
One of my big issues right now is how to test snippets that access the
persistence/business layer. This is trivial if snippets has some kind of
DI, as you could just inject mock objects instead of the real
thing. Alas, I haven't found a good solution yet. I do think that Scala
provides some language support for this (ie. the articles you linked to)
and I would like to pursue this first, before using more heavyweight
solutions such as Spring/Guice etc.
/Jeppe
--~--~-~--~~~---~--~~
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: Dependency Injection in Lift
On Aug 30, 9:03 pm, Chris Lewis burningodzi...@gmail.com wrote:
I am specifically talking about decoupling my web logic, ie, event
handlers for forms in lift snippets, from the persistence layer. As
currently implemented, snippets know exactly what persistence mechanism
is in use because there is no intermediary API. If I'm using Mapper, my
snippets must use the Mapper api. If JPA, the global EM wrapper Model.
The same, I imagine, holds true for the Record api.
Why do you say this holds true about Record? ... Recourd is not bound
to any persistence technology. If you are concerned about Mapper,
means to me that you want a complete abstraction such that you can
replace JDBC with something totally different. Ok, but what stops you
from invoking the Mapper from layer abstracted by application specific
traits?
This makes the
persistence layer a Leaky Abstraction
(http://en.wikipedia.org/wiki/Leaky_abstraction), and I want to avoid that.
Most of DI of Lift is currently done using PartialFunction-s and
Function lists that people can set in Boot or for snippets in case on
binding functions usign SHtml helpers etc.
Ok, but how does that help me decouple my web logic from the persistence
details?
The statement was about Lift's DI beyond the context of persistence.
If you want your snippets to not know about Mapper abstract the Mapper
wok with your own traits ... could use a Factory pattern or something
similar.
What we've learned with Lift is the it is OK to give to persistence
objects understanding of rendering. Having dumb objects that carry on
just data and rely of layers that can do different jobs (render,
persist) is IMO not a very good design approach.
I disagree. An entity, like Author, is nothing more than an expression
of a real-world concept modeled in code. It should know about itself,
its direct constituents (like a Book collection), anything else that
defines its own semantics, and nothing more. How it is stored is none of
its business.
I didn't quite expect that you would :). We found Lift's approach to
be quite productive in real life apps.
Don't misunderstand me - I accept that I may be missing something. We
agree that the concept of DI is valuable because it helps us keep
abstractions loosely coupled. I don't see the problem with annotations,
but I am not at all married to them.
No worries I think your approach for a debate is a very healthy one.
Having different opinions is OK. I explained one of the problems with
annotations in Scala
* The other problem with annotations is that we can't currently
build annotations in Scala to be visible at runtime, so we'd probably
have to code them in Java or use some existent Java annotations ...
but this already smells hacky IMHO.
You point at partial functions and traits to implement abstractions over
the persistence layer, but what is missing is how to apply that to
snippets. Yes, I could abstract the layer however I want, but my
snippets we still be required to get at the layer by calling it
directly, instead of having it provided. Can you share some input on
that part?
def mySnipetFunc(xhtml: NodeSeq) : NodeSeq = {
val persistence = MyPersistenceFactory.getPersistence();
...
persistence.getBy( --- some predicate ---)
...
}
This is a trivial model ... but in most cases this would be enough. In
many cases I don't really need something that injects a reference to
an annotated class member.
One other approach would be to use a RequestVar or a SessionVar to
hold a Persistence reference and you can access it from different
places. You could set the proper context for such var-s from from our
LoanWrapper added in boot by calling S.addAround.
Thanks for the discussion,
chris
marius d. wrote:
Most of DI of Lift is currently done using PartialFunction-s and
Function lists that people can set in Boot or for snippets in case on
binding functions usign SHtml helpers etc.
Personally I'm not at all a fan of Pojo/Poji DI by annotations
especially in Scala realm where there are other artifacts such as
function composition, monads, mixin composition, higher order
functions etc. The other problem with annotations is that we can't
currently build annotations in Scala to be visible at runtime, so we'd
probably have to code them in Java or use some existent Java
annotations ... but this already smells hacky IMHO.
If enterprise folks solve one problem by DI by annotation it doesn't
mean that this fits in all contexts.Persistence loosely coupling can
be achieved in many ways:
1. Implement your own persistence semantic on top of Record
2. Implement your own traits hence your own abstractions
3. etc
What we've learned with Lift is the it is OK to give to persistence
objects understanding of rendering. Having dumb objects that carry on
just data and rely of layers that can do different jobs (render,
persist) is IMO not a very good design approach.
[Lift] Re: Question about Lift/Scala Lift Discussion Board
So is that an instead of argument? Or an in addition to? Chas. Artem wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59 pm, Artem art...@gmail.com wrote: Hey! I stumbled on Lift a couple weeks ago
[Lift] Re: Question about Lift/Scala Lift Discussion Board
- Charles F. Munatc...@munat.com wrote: So is that an instead of argument? Or an in addition to? Chas. Artem wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you go right to left you get more dynamic/on the fly--you just write a question without worrying about organization or formatting. Does that make sense? - Xavi Ramirezxavi@gmail.com wrote: I applaud Artem's initiative! The mailing list has undoubtedly been an extremely helpful resource. That said, a mailing lists in general have several short comings: - Hard to search through - Many duplicate questions - No stickies - No syntax highlighting and few formatting options - Little to no message organization - Few moderation tools A forum could be a nice way to address these issues, so it might be worth a try. Also I think introducing a forum is anymore likely to splinter than an IRC chat room. Just my two cents. -Xavi On Sat, Aug 29, 2009 at 8:22 PM, Timothy Perretttimo...@getintheloop.eu wrote: Agreed (and +1) - Personally I actually prefer mailing lists full stop because it involves no web site trawling to get to the topics one is after... Cheers, Tim On 30/08/2009 01:20, TylerWeir tyler.w...@gmail.com wrote: I'm not really sure how splintering the community is going to help. I feel the google group has been fine. On Aug 29, 6:59
[Lift] Re: Question about Lift/Scala Lift Discussion Board
We recently went through such a debate at work trying to decide between web forum vs mailing list and the end result for us at least was it depends. A lot of this is all highly subjective, there is no right or wrong - both sides need to remember that what works for them might not work for others. Personally, i prefer mailing lists but am happy to accept that some people cant / wont / dont use mailing lists for whatever reasons. From a project perspective, I think google groups rocks for the following reasons: - its a mailing list - its a forum of sorts (i.e. you can interact purely from a browser if you wish) - it has RSS feeds - its hosted remotely, for free. - you just need a google account rather than another stupid login Like i said, there is no right or wrong in the general battle, however for lift I think that for the outlined reasons above it works and thats the way it should stay IMO. Cheers, Tim On 30 Aug 2009, at 20:48, marius d. wrote: Personally I like mailing lists .. I find it easier for me to try to help people then a traditional forum. For someone who wants to lear Lit perhaps a more traditional forum is more helpful? ... don't really know .. I guess it depends on the person. Br's, Marius On Aug 30, 10:10 pm, Artem art...@gmail.com wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting; organization - the way I see it, you can draw a continuum with IRC being the most transient and a Wiki etc. the most permanent, with a mailing list, a Google Groups mailng list, and a forum falling in between, in increasing order of permanence/organizability. As you go from left to right you get more of these features, but a forum is still less than a Wiki. On the other hand as you
[Lift] Re: about QueryParams
thanks a lot, David On Aug 27, 9:11 pm, David Pollak feeder.of.the.be...@gmail.com wrote: On Thu, Aug 27, 2009 at 2:12 AM, XiaomingZheng xiaomingzhen...@gmail.comwrote: there are two kinds of QueryParams in Lift, one uses raw sql clauses and the other not. My question is, when using the raw sql clauses, the security must be checked by programmer self, and declare safety by IHaveValidatedThisSQL, but when using the now raw methods, does Lift framework checks safety for us? These queries use prepared statements and uses setString/setInt/etc. to set each of the parameters. This means that SQL injection attacks are impossible unless there is a bug in the underlying JDBC driver. When you create your own String for a query and do some thing like: select * from foo where name = '+name+', you've created a huge SQL injection hole. If someone entered their name as fred' or id = 33 or name = 'fred then they could fish for record 33. If the query is built using By() (e.g., By(Foo.name, name)), then no matter what the name, you're not going to get an SQL injection attack. -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://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: Question about Lift/Scala Lift Discussion Board
Apparently there is a Google Group for Google Groups: the Google Groups Help Forum http://groups.google.com/group/Google-Groups-Guidehttp://groups.google.com/group/Google-Groups-GuideIt seems many people have noticed the search bug. Maybe if a lot of people post over there complaining it will help get a response from Google faster... On Sun, Aug 30, 2009 at 6:03 PM, Timothy Perrett timo...@getintheloop.euwrote: We recently went through such a debate at work trying to decide between web forum vs mailing list and the end result for us at least was it depends. A lot of this is all highly subjective, there is no right or wrong - both sides need to remember that what works for them might not work for others. Personally, i prefer mailing lists but am happy to accept that some people cant / wont / dont use mailing lists for whatever reasons. From a project perspective, I think google groups rocks for the following reasons: - its a mailing list - its a forum of sorts (i.e. you can interact purely from a browser if you wish) - it has RSS feeds - its hosted remotely, for free. - you just need a google account rather than another stupid login Like i said, there is no right or wrong in the general battle, however for lift I think that for the outlined reasons above it works and thats the way it should stay IMO. Cheers, Tim On 30 Aug 2009, at 20:48, marius d. wrote: Personally I like mailing lists .. I find it easier for me to try to help people then a traditional forum. For someone who wants to lear Lit perhaps a more traditional forum is more helpful? ... don't really know .. I guess it depends on the person. Br's, Marius On Aug 30, 10:10 pm, Artem art...@gmail.com wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow
[Lift] what's in Classpath?
How can we know what is included in Lift's classpath for javascript and css files? I see src=/classpath/jquery.js and src=/classpath/json.js in the example template, and even lift:CSS.blueprint / and lift:CSS.fancyType /. Where can I see exactly what we are getting 'for free', so I will know what I have to load explicitly into html? Thanks as always! --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
People have different preferences so you can decide to stay on Google Groups or help start the forum. If you want to help out, the forum URL is www.liftforum.com. If you have other questions about the forum, give me a shout at art...@gmail.com. Thanks. On Aug 30, 6:03 pm, Timothy Perrett timo...@getintheloop.eu wrote: We recently went through such a debate at work trying to decide between web forum vs mailing list and the end result for us at least was it depends. A lot of this is all highly subjective, there is no right or wrong - both sides need to remember that what works for them might not work for others. Personally, i prefer mailing lists but am happy to accept that some people cant / wont / dont use mailing lists for whatever reasons. From a project perspective, I think google groups rocks for the following reasons: - its a mailing list - its a forum of sorts (i.e. you can interact purely from a browser if you wish) - it has RSS feeds - its hosted remotely, for free. - you just need a google account rather than another stupid login Like i said, there is no right or wrong in the general battle, however for lift I think that for the outlined reasons above it works and thats the way it should stay IMO. Cheers, Tim On 30 Aug 2009, at 20:48, marius d. wrote: Personally I like mailing lists .. I find it easier for me to try to help people then a traditional forum. For someone who wants to lear Lit perhaps a more traditional forum is more helpful? ... don't really know .. I guess it depends on the person. Br's, Marius On Aug 30, 10:10 pm, Artem art...@gmail.com wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax
[Lift] who can give me some case?
who are using lift web now? - mawei...@gmail.com 13585201588 http://maweis.com --~--~-~--~~~---~--~~ 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: Question about Lift/Scala Lift Discussion Board
- mawei...@gmail.com 13585201588 http://maweis.com On Mon, Aug 31, 2009 at 6:31 AM, Artemart...@gmail.com wrote: People have different preferences so you can decide to stay on Google Groups or help start the forum. If you want to help out, the forum URL is www.liftforum.com. If you have other questions about the forum, give me a shout at art...@gmail.com. Thanks. On Aug 30, 6:03 pm, Timothy Perrett timo...@getintheloop.eu wrote: We recently went through such a debate at work trying to decide between web forum vs mailing list and the end result for us at least was it depends. A lot of this is all highly subjective, there is no right or wrong - both sides need to remember that what works for them might not work for others. Personally, i prefer mailing lists but am happy to accept that some people cant / wont / dont use mailing lists for whatever reasons. From a project perspective, I think google groups rocks for the following reasons: - its a mailing list - its a forum of sorts (i.e. you can interact purely from a browser if you wish) - it has RSS feeds - its hosted remotely, for free. - you just need a google account rather than another stupid login Like i said, there is no right or wrong in the general battle, however for lift I think that for the outlined reasons above it works and thats the way it should stay IMO. Cheers, Tim On 30 Aug 2009, at 20:48, marius d. wrote: Personally I like mailing lists .. I find it easier for me to try to help people then a traditional forum. For someone who wants to lear Lit perhaps a more traditional forum is more helpful? ... don't really know .. I guess it depends on the person. Br's, Marius On Aug 30, 10:10 pm, Artem art...@gmail.com wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as
[Lift] Re: who can give me some case?
Novell, Xerox, and SAP... so name a few big companies. InnovationGames.com to name a small (but very cool) company. On Sun, Aug 30, 2009 at 7:37 PM, Margaret mawei...@gmail.com wrote: who are using lift web now? - mawei...@gmail.com 13585201588 http://maweis.com -- 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: authentication and access control
On Sun, Aug 30, 2009 at 8:21 AM, Chris Lewis burningodzi...@gmail.comwrote:
Thanks David,
That does help, yes. My first toy app, which I wrote for a company demo,
used lift 1.0 and mapper. I dug into the MegaProtoUser source and
remember how it worked (providing its own site menu configurations with
access control there). Role-based restrictions could be done much the
same way. Part of my issue with that is probably invalid - I'm
accustomed to the practice of such configurations being stored outside
of application code (XML).
Having known that, I guess my question was focused more on how lift
remembers the user. I think it was using the S object, which ultimately
stores keyed objects on the session, right?
The MegaProtoUser keeps the primary key of the current user around in a
SessionVar.
SessionVars are a strongly typed layer on top of a hashtable that's secretly
stored in the LiftSession.
Thanks again for your dedication and commitment to the lift community.
Sure thing... I'd great to have lots of people learning Lift and building
cool things and driving the requirements...
chris
David Pollak wrote:
On Thu, Aug 27, 2009 at 6:42 PM, Chris Lewis burningodzi...@gmail.com
mailto:burningodzi...@gmail.com wrote:
Lift users,
I'm curious what you all are using for user access control (Mapper
users
excluded). I'm seriously evaluating lift for a project that will use
JPA. My full time job uses Spring Security, which while nice in that
it
stays out of the way, is too clunky for my tastes. I haven't
dissected
how lift implements it with Mapper, but wanted to ask the group
first.
Thanks!
For HTML access control, Lift's SiteMap offers URL level protection of
pages (and menu generation based on the access control rules.) For each
Loc (location) in your sitemap, you can chain together If() and Unless()
clauses to define what rules are applied to each page. These rules are
based on invoking functions (e.g., User.superUser_?) and can be
arbitrarily complex.
For protecting non-sitemap resources (stuff that's served up via a
custom dispatch [DispatchPF]), it's best practice to put a guard in the
partial function:
{
case Req(api :: accounts :: Nil, _, GetRequest) if
currentUserCanViewAccounts_? = renderAccounts _
}
Hope this helps.
chris
--
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
--
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: Question about Lift/Scala Lift Discussion Board
I would split out JPA and Mapper. Chas. Artem wrote: People have different preferences so you can decide to stay on Google Groups or help start the forum. If you want to help out, the forum URL is www.liftforum.com. If you have other questions about the forum, give me a shout at art...@gmail.com. Thanks. On Aug 30, 6:03 pm, Timothy Perrett timo...@getintheloop.eu wrote: We recently went through such a debate at work trying to decide between web forum vs mailing list and the end result for us at least was it depends. A lot of this is all highly subjective, there is no right or wrong - both sides need to remember that what works for them might not work for others. Personally, i prefer mailing lists but am happy to accept that some people cant / wont / dont use mailing lists for whatever reasons. From a project perspective, I think google groups rocks for the following reasons: - its a mailing list - its a forum of sorts (i.e. you can interact purely from a browser if you wish) - it has RSS feeds - its hosted remotely, for free. - you just need a google account rather than another stupid login Like i said, there is no right or wrong in the general battle, however for lift I think that for the outlined reasons above it works and thats the way it should stay IMO. Cheers, Tim On 30 Aug 2009, at 20:48, marius d. wrote: Personally I like mailing lists .. I find it easier for me to try to help people then a traditional forum. For someone who wants to lear Lit perhaps a more traditional forum is more helpful? ... don't really know .. I guess it depends on the person. Br's, Marius On Aug 30, 10:10 pm, Artem art...@gmail.com wrote: The problem is that this Google Group is not user friendly and not organized. I think it will be better to have a user friendly forum where everything is organized according to its category and easily accessible. This group is hard to find and hard to search. On Aug 30, 3:00 pm, Charles F. Munat c...@munat.com wrote: Just my two cents, but I think establishing a separate forum at this point is a mite premature. What problem, exactly, is it that we're trying to solve? Chas. Naftoli Gugenheim wrote: Once again, I don't see how you can discuss it until you know that David's fine with it. Personally I haven't read any concrete benefit (I don't know what take the load off or get more sites out there mean practically) that isn't available now between the list an the wiki---certainly not to outweigh the very clear disadvantage to both posters, who have that much less of a chance getting an answer in any one place and may have to ask twice, as well as to experts who can either only monitor one site and leave the other site with fewer experts; or be inconvenienced to monitor both. How many members are there of the Google Group currently? And what percentage ever offer answers? Regularly? The lift community is not as large as many other communities. Does Scala itself have other forums besides its own lists? If so what is their state? Certainly the Scala community is much larger than lift's. (Maybe you should make your forum be a Scala forum, and have a lift category... But again, I think it's only fair to ask lift's mastermind first!) - marius d.marius.dan...@gmail.com wrote: My 2 cents if I may ... Although I love this list and this is the official Lift list and support I think it is important to also have other wiki's, forums etc. out there. Personally I don't see this as a community split. More and more people are becoming pretty knowledgeable with Lift Scala sharing information about Lift on other channels ... is nothing wrong with that .. .quite the opposite. In fact this may take some of the load on this list as community grows. Would be nice though to have a central place where all other wiki's/ forums can be found. For instance serious forums/wikis could be references from lift web-site or even fromthis list in the header section. Br's, Marius On Aug 30, 8:37 am, Naftoli Gugenheim naftoli...@gmail.com wrote: The lift community is not huge. It's David Pollak's brainchild, and I don't see how you can discuss creating a forum (after the fact) without his okaying it. How can you compare it to an IRC? A forum fills much of the same purpose as the list, much more than IRC. Some of the advantages mentioned are better solved by a Wiki. (Your volunteering to help with it is much appreciated.) Searchability - sounds like a bug on Google's part, no? Is there a Group for discussing Google Groups? In any case, it's addressed by services like MarkMail. Isn't Nabbles searchable? Duplicate questions - forums don't completely solve this. Searchability would help, as will the Wiki as it grows. Stickies - Google Groups doesn't allow stickies? Syntax highlighting/formatting;
