I'm playing around with CRUDify and to some extent it is flexible. However, requirements for more flexibility made me extend the CRUDify, but finally I ended up having all the impl on my own.
So I have a couple of questions about Mapper design strategies. For example, I want some MappedFields to not to show on lists - do I have to extend all fields now and supply showOnList_? and more control methods or it's better to have a marker trait and filter them ? Or maybe introduce listFieldOrder for MetaMapper ? How about finer grained validations - for now I have a ValRequired and similar traits that use abstract override to alter MapperString behavior... I also use a trait and abstract override to localize field descriptions based on singleton names. But growing number of traits for this usage kind of smells... I guess that I'm accidentally leaning towards something like rails http://activescaffold.com/. Any opinions on that ? Marcin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---