Hi Glen... I actually do a lot of this - we have a product at work and i've just written a bunch of abstractions for work which just require me to do:
MyLib.init In the boot file of a new application and then everything wires up - I couldn't think of anything more straightforward? The vast majority of stuff in lift is done with PF's, so you can pretty much just write them in external jars, and import them - my 3rd part stuff usually has a lift-webkit dependency so that I can just do the LiftRules.disptach.append stuff directly in the init method, but its really no biggy and saves boilerplate. So given your example, this scheme should work right? Cheers, Tim On Jul 27, 11:52 pm, glenn <gl...@exmbly.com> wrote: > I'm interested in abstracting out useful features from my Lift > applications for ease of reuse, but I haven't found an easy way to do > it. I find myself creating a new Lift aplication for each feature, > with all the baggage (bootstrapping, etc.), and I then have to do a > lot of code modification to the application I'm adding the feature to > in order to get it to work. > > For example, suppose I want to add role-based user login to an > application that already has a User model just by dropping in a jar > file with the new feature. I don't see how to do it without some > boostrapping modifications. > > Has anyone really tried to modularize their Lift development. I'd be > very interested in some suggestions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
