[Springframework-developer] Re: Spring demo & tutorial : comments invited

[Isabelle M. <isa...@me...>]

Hi Ken,

Sounds good to me. As a matter of fact, my next step was going to be writing the use cases and scenarios for the demo. But if you want to do it, fine, and I'll review them. We have received a one-month license for MagicDraw (www.nomagic.com), and will probably be getting complimentary permanent licences after that. I'll send you the license in a separate mail.
I think we should aim to both keep the demo simple as far as business logic goes, and professional as far as the code goes. So we are definitely on the same wavelength on that matter.

Isabelle

On Fri, Apr 25, 2003 at 03:43:06PM -0500, Ken Krebs wrote:
> Isabelle,
> 
> This works well for me. I have been using Tomcat (4.1.18) and mySQL 
> (3.23.53) for my own experimentations with Spring using Java 1.4.1_01. I 
> think it is a good idea to stay away from advanced database features and 
> use only very basic, least common denominator SQL for this demo/tutorial 
> as much as possible. This would make it easy for potential users to 
> modify it for use with their own preferred database.
> 
> I understand perfectly the need to build the demo in an incremental fashion.
> 
> I think we need to have a good idea of what it is we want to accomplish 
> in each of the stages and in the demo/tutorial as a whole. It seems to 
> me that the demo/tutorial is an important sales tool for the framework. 
> As such, we should have some pretty clear goals of what features and 
> advantages of using the framework are to be demonstrated in the 
> demo/tutorial. It should reinforce whatever is going to be in the Spring 
> Introduction and/or Mission Statement page at the website.
> 
> I will get started by laying out an application file/directory structure 
> and Ant build script. I will also start listing display pages and use cases.
> 
> 
> 
> I will assume the following unless it is otherwise agreed:
> 
> The view technology will be JSP and JSTL (no scriptlets).
> Production quality code and exception handling should be the rule.
> The pages, at least in the initial stage will be very simple views 
> without style sheets, headers/footers/menus, or internationalization.
> 
> 
> Comments please.
> 
> Ken
> 
> 
> 
> Isabelle Muszynski wrote:
> 
> >Hi Ken,
> >
> >If you feel up to it, get started on the petclinic. The idea is to develop 
> >something a la Petstore, only it's a pet clinic this time. I have the 
> >tables script for Oracle, but actually I feel it would be better to do the 
> >demo on mySQL primarily. I can get you a tables script for mySQL by 
> >tomorrow evening my time.
> >The table structure so far is not complete, as it doesn't allow for owners 
> >to make appointments for their pets. But we should start out simply, so 
> >from the point of view of the vets treating animals.
> >Since we are not going to be using beans and complex transactions in the 
> >beginning, I think we could go for tomcat as a web container.
> >It's important that you build the demo in incremental steps called stages, 
> >and that each stage consist of a set of source code, build files and 
> >documentation. You can do the documentation free form in a text file, and 
> >I'll take care of incorporating it into the master set of docs. Make sure 
> >you explain everything you do in code, it's better to have too much 
> >explanations than too little.
> >
> >Isabelle
> >
> >On Fri, Apr 25, 2003 at 08:50:00AM -0500, Ken Krebs wrote:
> > 
> >
> >>Isabelle,
> >>
> >>Rod has OK'ed me to work on the project. How can I get started helping 
> >>you ?
> >>
> >>Regards,
> >>Ken
> >>
> >>
> >>
> >>   
> >>
> >
> > 
> >
> 
> 
> 
> 

-- 
Isabelle Muszynski
Software Engineer
Zandweellaan 4
2660 Antwerpen
Belgium
Tel. 32-(0)3-830 18 54
Mobile: 32-(0)485 49 50 89
Email: isa...@me...
Website: www.meta-logix.com