on 6/10/2000 3:21 AM, "Sean Legassick" <[EMAIL PROTECTED]> wrote:
> I've ported over the WM templates/screens/actions from Scarab to Turbine
> and they're working fine. Rather than just commit these though I have
> some thoughts about pulling stuff together:
Woo hoo!
> In the past when the possibility of making a WebMacro system the default
> out of the box config has come up, Jon particuarly has asserted that we
> need to be template-agnoistic. Whilst I feel it is important that
> Turbine continues to support various template engines (Freemarker & JSP
> particularly), are we still willing to take the cost in initial ease of
> use to avoid having a WebMacro setup be default?
I would actually go for making WM the default. In other words, essentially,
we are dropping ECS as the default for WM. That is cool with me.
Note, we need to document the hell out of the fact that just because WM is
the default it doesn't mean that Turbine can't be used in other ways.
What I am afraid of is some idiot coming along and making stupid claims
saying that Turbine only works with WM and that it sucks as a result of
that. Of course we would know this isn't true, it just needs to be stated. I
was burned with this with regards to ECS for a while there until we had a
working WM/FM integration.
> We make a WebMacro site the default for the various settings in
> TurbineResources.properties (with the non-WM alternatives specified in
> comments obviously).
+1
> We make all the default screens template driven (i.e. login & error
> screens). The templates, along with the admin templates from Scarab go
> in src/templates.
+1
> I'd like to see Rafal's proposed changes to our use of WM happen so that
> we can specify the location for the WM.properties file and the templates
> relative to the webapp root. Looking back it looks like Rafal is waiting
> on Kevin Burton's init API - how is that going Kevin?
>
> Then we amend the war-webmacro target of build.xml to take the template
> files from src/templates.
+1
> These changes together would bring us a whole lot closer to Dave's idea
> of a Turbine devkit. A new developer could download a Turbine tarball,
> build the war-webmacro target, set up their DB, point Tomcat at the
> turbine-war-webmacro directory and hey presto! a working Turbine
> install. The use of templates for all default screens means the new
> developer can start customising stuff straight away.
+1. That is entirely needed.
Note that this is a simpler version of what I really want to see which is a
downloadable package that includes Tomcat, Turbine and some Java based RDBMS
(ie: instantdb) all packaged together so that you execute tomcat/bin/startup
and off you go.
> I guess I need to change the licence on the Scarab code I'm porting to
> the Turbine licence. Any of the authors (Jon/Dave/Kevin) got any
> problems with that?
+1. Scarab is under a BSD license, that is fine with me.
> Jon, where did you get that crazy HTML? :-) Do you have a tool that
> generates that stuff (please, tell me you do and you didn't craft it by
> hand!). Anyway for the Turbine stuff I plan to make the navigations a
> lot more basic so people don't get lost in the details.
You mean the header/footer/nav stuff? I didn't do it by hand, I stole it
from someone elses website, and please don't commit that into CVS. :-) It is
missing the images which I haven't checked in anywhere.
I would like it if you or someone would come up with a nice default Turbine
look and feel for the header/footer/nav stuff.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
