On 6/25/01 4:51 PM, "Shawn Dahlen" <[EMAIL PROTECTED]> wrote:
> Hello -
>
> I've been following the Turbine project for a few months now, and I am
> in the
> process of creating an web community platform that relies on Turbine as
> the
> web application framework.
>
> My current thoughts are as follows:
>
> The web community platform would consist of a Turbine-based web
> application
> called "community". It seems as though the Jetspeed project currently
> fills this
> role, however I do not have much experience with the project. Now, I
> would
> like developers to create sub-applications that can plug into this
> community
> application and seamlessly integrate with one another.
That's the plan. After the cleanup is done in HEAD discussions will
start as to the direction of 2.2. There are already two known functioning
application services that work with the current Turbine code plus
one in the fork that Rafal has done in the turbine-like framework.
The first subapp will more than likely be flux. It has been working
for several months but I would like to collaborate with Ilkka who
also has an application service that has been functioning even
longer. The application service will definitely be a big part
of Turbine 2.2. The cleanup will probably take another week and
then I think we will be in great shape to look at new features.
> One could imagine logging into the "community", where upon log in,
> numerous
> services (sub-applications) would be offered such as message boards,
> scheduling, and file management.
Definitely, that's what we want.
> These sub-applications would reduce the learning curve in building web
> applications,
> solve the namespace problem for modules, and take advantage of community
> functionality such as congregation, inter-community communication, and
> lookup.
>
> The proposed Turbine Application Service seems as though it will allow
> me to
> carry out this vision. What is the current status on this work if any,
> and what are people's
> ideas on this. I would love to contribute to this area. I've looked
> through the archives and
> this topic seems to occasionally be brought up.
What eventually becomes the application service will probably be
an amalgamation of the work that Ilkka and myself have done in
this area as I believe we have most of the kinks worked out. But
when the proposal code lands in the repository everyone is welcomed
in debugging the design before anything becomes permanent.
> Jetspeed's ApplicationPortlet could possibly be an answer as well,
> although I think the
> web application framework should hold this functionality.
Hopefully Jetspeed will eventually build on top of the application
service.
> Thoughts?
If you have any that aren't listed in the proposal then feel free to
post them to the list and I will add them to the proposal.
> Shawn Dahlen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
