--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
I am happy to see your quest; it's not unlike mine; a non-profit with
a huge "need". In my case, the requirements are similar, except that
data entry takes a conversational perspective in which the primary
game is a kind of research, sensemaking over really complex,
frequently wicked, global issues. The "database" in my case is a very
large topic map. I'd very much like to see and participate in
conversations here and elsewhere that deal with the kinds of
development issues that arise in building such platforms. Thus far,
one of the most interesting examples is the microblog ESME at
apache.org that appears to have grown out of David's earlier
demonstrations with Lift, Skitter. ESME, in fact, satisfies some of my
use cases.
Cheers
Jack
> Hello,
>
[...]
> So here's a rough idea of what the app needs to do to replace the
> current functionality:
> 1. Two classes of users: admins (who can manage metadata like "reason
> codes"), and staffers (who do data entry and run reports)
> 2. Able to create and edit contacts (be it members or members of the
> public making enquiries)
> 3. Be able to log activity for each contact (such as when they pay
> membership dues, or call asking a question)
>
> It's not rocket science. BUT, it's also not "chat"...and I'm
> struggling to find Lift examples of enterprise-type "data entry and
> reporting" applications.
>
> So...with that introduction to my problem...where are the resources
> that I'm missing? I feel like there's a book in it...which I'm more
> than happy to help write but I also have a self-imposed timeline of
> getting a working replacement database app up and running in by
> Halloween.
We're doing the exact same thing (and has been for a few years now :-).
We started out by using the CRUDify trait to quickly get the data entry
up and running, coupled with some reporting using JQPlot
Starting out using Lift's Mapper ORM and the CRUDify trait should get
you the basics in a few hours :-)
We're gradually replacing the CRUDify screens with either custom forms
or LiftScreen forms (the latter is not quite up to what we need yet) and also
moving towards a more task based UI where CRUD is not really the best
option.
Currently doing advanced CRUD forms in Lift, while possible, is not as
efficient as it could be. Otoh, once done, it is easy to add more
advanced features, such as ajax controls, ajax validation etc....
/Jeppe