Folks,
Following up from the previous round, I am summarizing what we
discussed so far with an attempt to converge and move on to impl.
Would be keen to have feedback and possibly arrive at some resolution
on the outstanding items. (Meaty stuff below the module structure)
liftweb
- lift-core [H]
- lift-base [J]
- lift-util [J]
- lift-actor
- lift-json
- lift-webkit [K]
- lift-persistence
- lift-mapper
- lift-record
- lift-jpa
- lift-modules [L]
- lift-testkit
- lift-osgi
- lift-wizard
- lift-widgets
- lift-machine
- lift-textile
- lift-facebook
- lift-amqp
- lift-xmpp
- lift-openid
- lift-oauth
- lift-paypal
- lift-jta
- lift-archetypes
- ...
- lift-examples [M]
- ...
- lift-site
- lift-resources [N]
- lift-root-model
- lift-site-skin
- lift-installer
- misc config resources (scaladoc, javadoc etc.)
Resolved since:
[A] lift-* prefix is fine/preferred for top level categories (dir_name
== artifactId) [Heiko]
[B] For Lift users not using Maven these *-all.jars will be valuable.
Assembly preferred to meta [Heiko]
[C] lift-testkit to move to lift-modules. Applications would use it
under 'test' scope. [David]
[D] lift-json to be part of core [Marius]
[E] lift-persistence being separated from lift-core into it's own
category and made optional [Marius]
[F] No deep nesting within modules (no submodules) for now [Heiko]
[G] Presentations and docs to be in central repository for now
[+1:David/Tim/Derek, +0:Indrajit, -1:Heiko/Viktor].
Settling for central repo at the moment (a: least change, b: in a
hurry to converge, c: effect of living in largest democracy in the
world!). Later on, I'll attempt to make this part of site build and
make them more conveniently available.
Outstanding since:
[H] lift-core has to get a better and more appropriate name (and also
to avoid confusion since lift-core == 'everything lift' at the
moment).
Starting with two that come to my mind.
- lift-lite (Members of this category make up the lightweight,
minimalistic Lift distribution that would help you build a Lift based
application)
- lift-genesis (Members of this category make up the genesis of
your Lift based application)
- lift-mini (Minimal Lift distribution to get started with Lift)
- lift-minimal (Same as above)
[J] lift-base, lift-util needs more unambiguous names.
- lift-base -> lift-common [+1:Naftoli/Derek/Stuart/Marius/Tim/
Heiko/Viktor, +0:Indrajit -1:DavidB (very strong)] But still good to
have even better option.
- lift-util -> lift-util (no change) [+1:Marius/David (status
quo)]
- lift-util -> lift-webutil [+1:Naftoli/Derek/Stuart/Indrajit/Tim/
Heiko/Viktor]
[K] Splitting webkit, over dependence on webkit etc. Different options
have been discussed actively.
An possibility could be:
- lift-webkit as top level category (and concrete modules within)
- put the 'core' parts of webkit in the new lift-webutils (see
above) and non-core parts (Ajax, CSS etc.) in lift-webkit
- lift-widget, lift-wizard etc. can be folded into the non-core
part of lift-webkit
Having said them, Let the thoughts brew for sometime. I'm keeping
this "as is" for now. Would come back after I clean up my plate a
bit ;-)
[L] As stated earlier, I am putting 'everything else' here for lack of
better place. I have concern that this can turn out to be a place for
all the 'nowhere else to go' modules. But let's sleep on it till the
problem is big enough ;-)
[M] The example project names need to be rationalized, normalized.
examples/example doesn't qualify ;-)
[N] lift-resources should have meaningful name.
For start:
- lift-infra
- lift-infrastructure
- lift-project-resources
- lift-varia
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
