Re: [JSPDBAdmin-Developers] [Targets]

[Adrian A. <aal...@ca...>]

>
>  1.- Before starting we need to select what databases we are going to
> cover.
> > I propose ORACLE, MySQL, Postgress. (I think those are the most used and
a
> > little bit difficult to administrate).
>
> This list is OK.

Great.

>
> > 2.- Select the build tool we are going to use. I propose jakarta-ant
cause
> > it almost always make the work.
>
> Ant is a powerful tool for build process. We can use this once a basic
> structure of the
> codebase is ready.

I Agree.

>
> > 3.- In general select the tools and technologies we need to work
(Logging,
> > Database Pool (If we are going to use it), Taglibs).
>
> What are the various API's availbale for creating Database Pools? Logging
> framework
> needs to be thought over and has to the implemented from the beggining.
The
> logging
> framework should help both while development as well as in maintenance.
>

I propose for logging, jakarta-Log4J its great framework for development and
maintenance.

>
>
> > 4.- Make a multiple API to handle all kind of databases getting the most
> > similar features to make right now the core.
> This is a critical aspect. The design framework here I propose is
"Abstract
> Factory".

Great, its closely of what i thinked but i see this aproach maybe its
better.

>
>
> > 5.- After we have the core, then make extensions to every database
> specific
> > features like DB File size, % of data occupied, and things like that.
> OK. This anyhow is coming later.
>
>
> > 6.- Make a web interface to use this api, this interface must be for
every
> > database we are going to cover can have extensions that are going to be
> > activated on the build process. (We are going to need a lot of
properties
> or
> > XML files to achieve that).,
> A simple UI should act as a refrence point for the database API. I can
> prepare
> the reference HTML screens. Alamanar, I need your help here.

I was thinking to make WEB development is Struts, it think we are going to
handle things very easy if we use an MVC model for this.

Can you explain me what can i do to help you ?

>
> > 7.- The web interface must be interesting if it has i18n on it, would be
> > great, and can have a lot of users cause not everyone can handle
english.
> i18n definitely increases the usability of the system.
>
> >
> > By the way, the priority is the core, and the tools we are going to use.
> >
> > If anyone has anithing to add, your request would be welcome.
> >
> > Cheers,
> >
> > Adrian
> >
> >
> >
> >
>
> My idea now is to first come up with some screens(may not be aesthetic) to
> act as reference point to prepare the database API. What do others say?
> Alamanar, can u create a file  JSPDBADMIN-PLAN.TXT  in the CVS and add
this
> list.

Yeah tomorrow i will have CVS access, so i can do that.

>
> Ramana.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JSPDBAdmin-Developers mailing list
> JSP...@li...
> https://lists.sourceforge.net/lists/listinfo/jspdbadmin-developers