Great stuff. Could you please describe "more complex scenarios" ? I mean let's start from some step-by-step use-case/workflow definitions that you're looking for and we'll try to provide different approaches, and potentially put them on the wiki for future reference.
Br's, Marius On Dec 26, 6:27 pm, greekscala <hellectro...@gmail.com> wrote: > Hello, > > It would be great to see some more bind examples in more > complex scenarios and how different snippets can work > together. How to build fragments and replace fragments > for ajax. I think the people that do a lot with lift have some > patterns for this. Are there any Idioms out. > > This is my problem area. > > with best regards > > On 26 Dez., 15:30, Marius <marius.dan...@gmail.com> wrote: > > > While I admit that there is not yet enough documentation material or > > at least probably not in a single place I disagree with some > > complaints. The Lift book for example describes in quite detail that > > request processing lifecycle, disspath functions, rendering pipeline, > > LiftRules, S, SHtml, LiftResponse-s, binds, JavaScript abstraction > > and many others etc. Sure new things came up in the mean time and > > we're trying to document them as time permits in many cases. > > > About the Lift structure being too messy, what do you actually mean? > > AFAIK historically, people (a many newbies) asserted the contrary that > > they really liked the Lift concepts, the ease of use and understand > > how it works. For naming conventions there was a project opened and > > even discussed on this public list about renaming API's but AFAIK > > there was not a whole lot of feedback on this list so unless I'm > > wrong, the decision was to do ad-hoc renaming as we work on various > > things. This may mean deprecation of old names so there will be a > > smooth transition to "better" names. > > > So I believe it is much more constructive for ALL of us to ask > > concrete questions, described concrete problems and let's see how we > > can fix it. Many things though may be subjective and leading to > > endless discussions without substance. > > > Br's, > > Marius > > > On Dec 26, 2:51 am, Erkki Lindpere <vill...@gmail.com> wrote: > > > > I think the best things I think you could do to help newbies is > > > document in a well-structured way: > > > > * all the conventions over configuration rules > > > * what classes to use for the basic stuff (what is S for and how it > > > should be used, all the things you can do with LiftRules, etc.) > > > * more advanced uses of bind(...) in snippets > > > * better docs for the Lift tags. > > > > On Dec 25, 9:09 pm, Timothy Perrett <timo...@getintheloop.eu> wrote: > > > > > It would be really good for us as a team to know what it is you *dont* > > > > get? Is it conceptual? code? If we can understand what is daunting for > > > > newbies that would really be helpful. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
