Yes, I totally agree.
I spent the past two days trying to figure out why Turbine didn't work for
me ... I tried calling other screens directly, still no response. Yes, this
is very disillusionary to what may be a very good system. I am still in he
process of reviewing Turbine for our own internal projects, and I must say
that so far, my impression is not all that fanstastic - maybe 'coz I can't
seem to get it started!! Also, even the build scripts in the CVS seem
broken ... I had to manually set my classpath and run ant dircetly for it to
build.
Cheers,
--
Manik Surtani
Chief Technology Officer
Espada (Private) Limited
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nissim
> Sent: Friday, August 11, 2000 5:23 AM
> To: Turbine
> Subject: Re: something is wrong
>
>
> Josh Lucas wrote:
> >
> > Daniel Rall wrote:
> > >
> >
> > > Daniel, as noted alreday upwards of 20 times, the Login screen is not
> > > currently distributed with Turbine, as it is being rewritten
> from an ECS
> > > to WebMacro implementation. Please search the mailing list archive
> > > *first* next time you have a question, *then* post if you can't find
> > > what you need. Thanks!
> > >
> >
> > While I agree that it has been discussed at length, the Login screen is
> > still the default screen within TurbineResource. We should either
> > change the default or include some sort of Login screen.
> >
> > If I missed this in the earlier discussions, my apologies.
> >
> > josh
> >
>
> Yeah, I think that it's *not a good thing* that the answer to this
> current FAQ is "we're in a state of flux" or "A bunch of stuff has
> changed so the CVS code doesn't function out of the box. I think that a
> lot of people might be turned away from *this great system* if that is
> how we're responding, and that would be a shame.
>
> We should figure out what we need to put into CVS to have something
> happen when someone installs turbine (that's not an error msg :-)
>
> So, here are our options to fix this as I see them:
>
> 1) Make WebmacroSitePage the default, and have the default page be the
> sample index.wm. Since that sample doesn't really do anything, it's not
> the best, but it'll work right now with only a change to TR.properties,
> and maybe WM.properties or some of the documentation.
>
> 2) Make some more functional samples and have them linked from that
> index.wm, which could include Sean's user management code when it's
> done, and some more little samples a la Tomcat's JSP sample apps.
>
> 3) Continue to have a broken product in CVS until the WM user management
> app is done.
>
> I think we should do Option 1, and then move to option 2 if someone
> makes some sample apps.
>
> -Nissim
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
