--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
Given that Lift is a very mature tool it's highly unlikely to catch fire again.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to a topic in the Google Groups "Lift" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/liftweb/8wyFHy7aNtM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to liftweb+u...@googlegroups.com.
I just need a way in. What's our current best location for:
1) A high level onboarding that includes best practices like data-lift tags
2) A set of strategies and practices like how to separate class names between lift binding anchors and designer style expressions
3) A deep dive into Wizard, LiftScreen and Field structure and extension
These are all resources I'm building/have built. Some of them clearly fit neatly into missing sections of the Lift Cookbook, some of them seem to be edits to other documents.
I'm happy to express them in markdown. Can anyone chime in as to where I can fit them and how I can obtain the necessary access, please? I've been waiting a long time to be able to do this!
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
I'm assuming that the end result needs to be publishable as a pdf or as html. Im not sure whether it has a hard copy publishing path as well?
I don't want to try to unmake any prior decisions. But if there happen to be different constraints in play than there were initially I'd like to get a read on those.
Additionally, and crucially, I don't want to try to coopt anyone who has an ownership of this material. But I'm willing to step into a primary role and if I were to do so I'd need to understand the pipeline deeply, potentially even to the point of porting the content.
But not as a reactive "I can't get this to work" step.
Long story short, any help on the lyx pipeline welcome ;)