[Lift] Re: Wiki Articles
Hey Alex, > - Templating > * Snippets etc. You might want to checkout my article here: http://is.gd/sfyT As for the rest of your list, I agree these need documenting in fair detail. I can certainly contribute from a localization and REST perspective - i'll try and crank something out onto my blog. Cheers, Tim --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Wiki Articles
On Tue, Jul 14, 2009 at 6:19 PM, Xavi Ramirez wrote: > > Thanks Alex! That exactly what we need. Over the next couple of > days, I'm going to start organizing the existing wiki articles around > this outline. > > In the mean time, is there a chance someone could help me get any of > the following done? > - Replace the wiki logo with the lift logo > - Add syntax highlighting > - Open up registration (I'll monitor the recently modified page daily > to keep the spam down) > You have the same rights on the wiki as I do (everything) If there are things that need to be done in the filesystem or on the RDBMS, please send me direct email with clear instructions on exactly what to do. > > > Thanks, > Xavi > > On Tue, Jul 14, 2009 at 1:47 PM, Alex Cruise wrote: > > > > Jeremy Day wrote: > >> 1. Logging in using various methods, i.e. basic authentication, > >> OpenID, etc. > >> 2. Displaying or hiding information based on user credentials. > >> 3. Setting up simple AJAX calls, such as getting a list of search > >> results based on and entered keyword. > > These are great suggestions for Examples that we'd like someone to > > build/identify; we can wire them up to Features as required. > > > > What's the feature tree? Here's a strawman that will hopefully prompt > > further discussion. > > > > - Templating > > * Snippets etc. > > > > - Sitemap/Menus > > * Conditional display > > * Access control (does authn/authz belong in its own topic?) > > > > - Client-side interactivity > > * Comet > > * AJAX > > > > - Forms > > * Security > > * Callback validation > > * File upload > > > > - ORM > > * Mapper > > * Record > > > > - Services > > * REST > >^ XML > >^ JSON > > > > - I18n/L10n > > * In templates > > * ? > > > > - ...? > > > > -0xe1a > > > > > > > > > > > -- 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: Wiki Articles
Thanks Alex! That exactly what we need. Over the next couple of days, I'm going to start organizing the existing wiki articles around this outline. In the mean time, is there a chance someone could help me get any of the following done? - Replace the wiki logo with the lift logo - Add syntax highlighting - Open up registration (I'll monitor the recently modified page daily to keep the spam down) Thanks, Xavi On Tue, Jul 14, 2009 at 1:47 PM, Alex Cruise wrote: > > Jeremy Day wrote: >> 1. Logging in using various methods, i.e. basic authentication, >> OpenID, etc. >> 2. Displaying or hiding information based on user credentials. >> 3. Setting up simple AJAX calls, such as getting a list of search >> results based on and entered keyword. > These are great suggestions for Examples that we'd like someone to > build/identify; we can wire them up to Features as required. > > What's the feature tree? Here's a strawman that will hopefully prompt > further discussion. > > - Templating > * Snippets etc. > > - Sitemap/Menus > * Conditional display > * Access control (does authn/authz belong in its own topic?) > > - Client-side interactivity > * Comet > * AJAX > > - Forms > * Security > * Callback validation > * File upload > > - ORM > * Mapper > * Record > > - Services > * REST > ^ XML > ^ JSON > > - I18n/L10n > * In templates > * ? > > - ...? > > -0xe1a > > > > --~--~-~--~~~---~--~~ 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: Wiki Articles
Jeremy Day wrote: > 1. Logging in using various methods, i.e. basic authentication, > OpenID, etc. > 2. Displaying or hiding information based on user credentials. > 3. Setting up simple AJAX calls, such as getting a list of search > results based on and entered keyword. These are great suggestions for Examples that we'd like someone to build/identify; we can wire them up to Features as required. What's the feature tree? Here's a strawman that will hopefully prompt further discussion. - Templating * Snippets etc. - Sitemap/Menus * Conditional display * Access control (does authn/authz belong in its own topic?) - Client-side interactivity * Comet * AJAX - Forms * Security * Callback validation * File upload - ORM * Mapper * Record - Services * REST ^ XML ^ JSON - I18n/L10n * In templates * ? - ...? -0xe1a --~--~-~--~~~---~--~~ 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: Wiki Articles
All, I'd like to see: 1. Logging in using various methods, i.e. basic authentication, OpenID, etc. 2. Displaying or hiding information based on user credentials. 3. Setting up simple AJAX calls, such as getting a list of search results based on and entered keyword. I'm looking at this from the perspective of a complete newbie, which I happen to be. Jeremy On Tue, Jul 14, 2009 at 12:29 PM, Timothy Perrett wrote: > > Alex, > > Sounds like a good plan - so, lets get the ball rolling... what topics > are lacking and what need completly rewriting? > > Part of me is happy to disregard the entire wiki content and just draw > up a list of what needs documenting, then as a community we can > hopefully move forward and get some of this written down. > > So, im all ears - what do you guys want to see? > > Cheers, Tim > > On Jul 14, 6:12 pm, Alex Cruise wrote: > > The approach I'd humbly suggest for improving the wiki is to focus on > > example coverage, which in some ways is to documentation what code > > coverage is to code. Specifically, for every substantial feature of > > lift, is it demonstrated in some clear way in an example that's as > > simple and comprehensible as possible? > > > > For most of these (feature, example) tuples there will be some example > > code but no corresponding wiki page. Any sufficiently smart person who > > reads the example code can write up a quick and dirty wiki page that > > outlines the structure of the sample, then annotate it with questions > > for committers about the motivation or other background for the specific > > details of the example. Then, when each one of these example pages is > > alpha quality, post the URL to the list and the rest of us can > > criticize/edit it. :) > > > > I find that for forensic documentation projects like this one, it's > > easiest to hit the ground running when you start by documenting > > extremely concrete use cases, then work your way "up" to architecture by > > observing patterns in the examples. > > > > -0xe1a > > > --~--~-~--~~~---~--~~ 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: Wiki Articles
Alex, Sounds like a good plan - so, lets get the ball rolling... what topics are lacking and what need completly rewriting? Part of me is happy to disregard the entire wiki content and just draw up a list of what needs documenting, then as a community we can hopefully move forward and get some of this written down. So, im all ears - what do you guys want to see? Cheers, Tim On Jul 14, 6:12 pm, Alex Cruise wrote: > The approach I'd humbly suggest for improving the wiki is to focus on > example coverage, which in some ways is to documentation what code > coverage is to code. Specifically, for every substantial feature of > lift, is it demonstrated in some clear way in an example that's as > simple and comprehensible as possible? > > For most of these (feature, example) tuples there will be some example > code but no corresponding wiki page. Any sufficiently smart person who > reads the example code can write up a quick and dirty wiki page that > outlines the structure of the sample, then annotate it with questions > for committers about the motivation or other background for the specific > details of the example. Then, when each one of these example pages is > alpha quality, post the URL to the list and the rest of us can > criticize/edit it. :) > > I find that for forensic documentation projects like this one, it's > easiest to hit the ground running when you start by documenting > extremely concrete use cases, then work your way "up" to architecture by > observing patterns in the examples. > > -0xe1a --~--~-~--~~~---~--~~ 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: Wiki Articles
The approach I'd humbly suggest for improving the wiki is to focus on example coverage, which in some ways is to documentation what code coverage is to code. Specifically, for every substantial feature of lift, is it demonstrated in some clear way in an example that's as simple and comprehensible as possible? For most of these (feature, example) tuples there will be some example code but no corresponding wiki page. Any sufficiently smart person who reads the example code can write up a quick and dirty wiki page that outlines the structure of the sample, then annotate it with questions for committers about the motivation or other background for the specific details of the example. Then, when each one of these example pages is alpha quality, post the URL to the list and the rest of us can criticize/edit it. :) I find that for forensic documentation projects like this one, it's easiest to hit the ground running when you start by documenting extremely concrete use cases, then work your way "up" to architecture by observing patterns in the examples. -0xe1a --~--~-~--~~~---~--~~ 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: Wiki Articles
Sounds like a good proposal - I cant help but think that the wiki should provide most of this functionality however... Personally, i've never been a fan of our media wiki but i guess the question here is weather or not we should be using a wiki for this stuff or if an ancillary system is truly required. Cheers, Tim On Jul 14, 1:34 pm, Jeremy Day wrote: > All, > > How about putting together a little cookbook application in Lift with > "recipes" describing how the various and sundry parts were put together? > For instance, the application could have the following pieces: > > 1. Log in piece so that users can log in and create new recipes (and maybe > save their favorites). > 2. Search functionality so that users can find recipes. > 3. Some sort of simple browsing structure for users who just want to peruse > what has been submitted. > > Jeremy --~--~-~--~~~---~--~~ 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: Wiki Articles
All, How about putting together a little cookbook application in Lift with "recipes" describing how the various and sundry parts were put together? For instance, the application could have the following pieces: 1. Log in piece so that users can log in and create new recipes (and maybe save their favorites). 2. Search functionality so that users can find recipes. 3. Some sort of simple browsing structure for users who just want to peruse what has been submitted. Jeremy On Tue, Jul 14, 2009 at 3:43 AM, Timothy Perrett wrote: > > Right now, I see a need for starter documentation and some more > advanced how-to's. Unfortunately its a mammoth task and we (the commit > team) need as much community help as possible. > > I agree with the ideas about a cookbook - let me propose this: > > If you guys are prepared to start making sample applications, and > documenting them as you go writing tutorials on the wiki, then we'll > do our absolute best to answer your questions if and may you have them > when your writing your sample applications. > > We know there is a big need for documentation - I've personally been > trying to cover this on my blog with several articles: > > http://blog.getintheloop.eu/tags/lift > > What things would you guys say is specifically missing? What would you > like to see articles on? > > Cheers, Tim > > On Jul 14, 7:19 am, Jeppe Nejsum Madsen wrote: > > Naftoli Gugenhem writes: > > > Not speaking for anyone else, but currently what I would like most is > information on lift's internals. > > > > Me too :-) Don't know how stable this information will be though. > > > > But in the larger scheme where, I believe, the goal is to attract people > > to using Lift, I think good howtos and cookbooks could help people > > getting started. > > > > /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: Wiki Articles
Right now, I see a need for starter documentation and some more advanced how-to's. Unfortunately its a mammoth task and we (the commit team) need as much community help as possible. I agree with the ideas about a cookbook - let me propose this: If you guys are prepared to start making sample applications, and documenting them as you go writing tutorials on the wiki, then we'll do our absolute best to answer your questions if and may you have them when your writing your sample applications. We know there is a big need for documentation - I've personally been trying to cover this on my blog with several articles: http://blog.getintheloop.eu/tags/lift What things would you guys say is specifically missing? What would you like to see articles on? Cheers, Tim On Jul 14, 7:19 am, Jeppe Nejsum Madsen wrote: > Naftoli Gugenhem writes: > > Not speaking for anyone else, but currently what I would like most is > > information on lift's internals. > > Me too :-) Don't know how stable this information will be though. > > But in the larger scheme where, I believe, the goal is to attract people > to using Lift, I think good howtos and cookbooks could help people > getting started. > > /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: Wiki Articles
Does anyone else see a strong need for a few "cookbook" examples? I think it could really help if we explain some of the idioms that David & Co had in mind when designing the framework. On Tue, Jul 14, 2009 at 5:54 AM, DFectuoso wrote: > > I would love to help making how-to's for simple stuff i think every > webapp creator needs to start coding! > > > > On Jul 13, 8:06 pm, Peter Robinett wrote: > > I think that would be nice, for instance pointing out to newcomers how > > many methods of common Lift objects can be overloaded. > > > > Speaking of fellow beginners, I would like to see authoritative How > > Tos and recipes for common tasks such as requiring a user to be logged > > in to access and page and making a REST API (perhaps this could even > > become a trait like CRUDify?). > > > > Please let me know how I can help. > > > > Peter Robinett > > > > On Jul 13, 7:10 pm, Naftoli Gugenhem wrote: > > > > > Not speaking for anyone else, but currently what I would like most is > information on lift's internals. > > > > > - > > > > > Xavi Ramirez wrote: > > > > > Hello, > > > > > I've volunteered as a wiki gardener, and I'm looking for suggestions > > > on how to improve the liftwiki. > > > > > I personally feel that developing a comprehensive set of HowTo > > > articles (aka Cookbook receipts) is a worthwhile goal. This type of > > > format has been suggested several times on the mailing list and it has > > > been very successful in other communities. To that end, I feel that > > > we should start by improving these two pages: > http://wiki.liftweb.net/index.php/Lift_Tutorialshttp://wiki.liftweb.n... > > > > > That said, I'm very open to suggestions. Do you think our time is > > > better spend creating detailed write ups on working examples? Or > > > writing articles on the internals of lift? Please let me know! > > > > > Thanks, > > > Xavi > > > > > P.S. To help keep our efforts focus, I'll suggest 5 pages that could > > > use some attention each Monday. > > > P.P.S.S Here's a list of some quick wins I can think of: > > > - Replace the wiki logo with the lift logo > > > - Add syntax highlighting > > > - Open up registration (I'll monitor the recently modified page daily > > > to keep the spam down) > > > > > Unfortunately, I can't implement any of these myself. I'll need > > > someone with admin access to help me out. > > > > --~--~-~--~~~---~--~~ 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: Wiki Articles
I would love to help making how-to's for simple stuff i think every webapp creator needs to start coding! On Jul 13, 8:06 pm, Peter Robinett wrote: > I think that would be nice, for instance pointing out to newcomers how > many methods of common Lift objects can be overloaded. > > Speaking of fellow beginners, I would like to see authoritative How > Tos and recipes for common tasks such as requiring a user to be logged > in to access and page and making a REST API (perhaps this could even > become a trait like CRUDify?). > > Please let me know how I can help. > > Peter Robinett > > On Jul 13, 7:10 pm, Naftoli Gugenhem wrote: > > > Not speaking for anyone else, but currently what I would like most is > > information on lift's internals. > > > - > > > Xavi Ramirez wrote: > > > Hello, > > > I've volunteered as a wiki gardener, and I'm looking for suggestions > > on how to improve the liftwiki. > > > I personally feel that developing a comprehensive set of HowTo > > articles (aka Cookbook receipts) is a worthwhile goal. This type of > > format has been suggested several times on the mailing list and it has > > been very successful in other communities. To that end, I feel that > > we should start by improving these two > > pages:http://wiki.liftweb.net/index.php/Lift_Tutorialshttp://wiki.liftweb.n... > > > That said, I'm very open to suggestions. Do you think our time is > > better spend creating detailed write ups on working examples? Or > > writing articles on the internals of lift? Please let me know! > > > Thanks, > > Xavi > > > P.S. To help keep our efforts focus, I'll suggest 5 pages that could > > use some attention each Monday. > > P.P.S.S Here's a list of some quick wins I can think of: > > - Replace the wiki logo with the lift logo > > - Add syntax highlighting > > - Open up registration (I'll monitor the recently modified page daily > > to keep the spam down) > > > Unfortunately, I can't implement any of these myself. I'll need > > someone with admin access to help me out. --~--~-~--~~~---~--~~ 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: Wiki Articles
Naftoli Gugenhem writes: > Not speaking for anyone else, but currently what I would like most is > information on lift's internals. Me too :-) Don't know how stable this information will be though. But in the larger scheme where, I believe, the goal is to attract people to using Lift, I think good howtos and cookbooks could help people getting started. /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: Wiki Articles
I think that would be nice, for instance pointing out to newcomers how many methods of common Lift objects can be overloaded. Speaking of fellow beginners, I would like to see authoritative How Tos and recipes for common tasks such as requiring a user to be logged in to access and page and making a REST API (perhaps this could even become a trait like CRUDify?). Please let me know how I can help. Peter Robinett On Jul 13, 7:10 pm, Naftoli Gugenhem wrote: > Not speaking for anyone else, but currently what I would like most is > information on lift's internals. > > - > > Xavi Ramirez wrote: > > Hello, > > I've volunteered as a wiki gardener, and I'm looking for suggestions > on how to improve the liftwiki. > > I personally feel that developing a comprehensive set of HowTo > articles (aka Cookbook receipts) is a worthwhile goal. This type of > format has been suggested several times on the mailing list and it has > been very successful in other communities. To that end, I feel that > we should start by improving these two > pages:http://wiki.liftweb.net/index.php/Lift_Tutorialshttp://wiki.liftweb.net/index.php/CookBook > > That said, I'm very open to suggestions. Do you think our time is > better spend creating detailed write ups on working examples? Or > writing articles on the internals of lift? Please let me know! > > Thanks, > Xavi > > P.S. To help keep our efforts focus, I'll suggest 5 pages that could > use some attention each Monday. > P.P.S.S Here's a list of some quick wins I can think of: > - Replace the wiki logo with the lift logo > - Add syntax highlighting > - Open up registration (I'll monitor the recently modified page daily > to keep the spam down) > > Unfortunately, I can't implement any of these myself. I'll need > someone with admin access to help me out. --~--~-~--~~~---~--~~ 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: Wiki Articles
Not speaking for anyone else, but currently what I would like most is information on lift's internals. - Xavi Ramirez wrote: Hello, I've volunteered as a wiki gardener, and I'm looking for suggestions on how to improve the liftwiki. I personally feel that developing a comprehensive set of HowTo articles (aka Cookbook receipts) is a worthwhile goal. This type of format has been suggested several times on the mailing list and it has been very successful in other communities. To that end, I feel that we should start by improving these two pages: http://wiki.liftweb.net/index.php/Lift_Tutorials http://wiki.liftweb.net/index.php/CookBook That said, I'm very open to suggestions. Do you think our time is better spend creating detailed write ups on working examples? Or writing articles on the internals of lift? Please let me know! Thanks, Xavi P.S. To help keep our efforts focus, I'll suggest 5 pages that could use some attention each Monday. P.P.S.S Here's a list of some quick wins I can think of: - Replace the wiki logo with the lift logo - Add syntax highlighting - Open up registration (I'll monitor the recently modified page daily to keep the spam down) Unfortunately, I can't implement any of these myself. I'll need someone with admin access to help me out. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
