Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gmt-dev] Initial CVS structure

Not saying that re-factoring is easy. Precisely because it's not easy,
larger pieces of initial code should be parked outside the core structure,
so that the core structure stays clean and does not have to be re-factored
all the time.

The suggested approach gives everyone a chance to evaluate the initial
assets that are submitted. The initial submissions from various corners may
not be compatible amongst each other and may - in parts - be in conflict
with the intended GMT architecture. Let's discuss the core tool architecture
in the form of UML diagrams first, before we jump in and carve out elaborate
directory structures.


----- Original Message -----
From: "Jeff Hoare" <jhoare@xxxxxxxxxxxxxxxx>
To: <gmt-dev@xxxxxxxxxxx>
Sent: Wednesday, May 28, 2003 9:53 AM
Subject: Re: [gmt-dev] Initial CVS structure

This link to some project guidelines may help

I suggest that before anything is added to cvs you consider what
(a) Your main "areas" are
(b) the appropriate sub categories within each level will be (see below).
(c) The appropriate level for commit access (see the guidelines above)

Its easy  to say "As we make progress on the four core components, the
existing code can be refactored to reside in the appropriate places..."
However, it might not be as painless as you make it seem, especially as you
get further on into the project.

Also consider such things as:
(a) location of documentation, ie will there be a central location for all
a documentation project if you like), or will each component provide this,
perhaps we have a combination of both.
(b) The build structure (which may affect the structure within each


On Wed, 28 May 2003 05:55, Willink, Ed wrote:
> Hi All
> I would like to put my current code under Eclipse CVS as soon as
> possible. Below is an indication of my first stab at a directory
> structure, with an indication of what I actually have to populate
> it.
> gmt-home
> doc
> umlx (UmlxGraphicalLanguage.pdf)
> org.eclipse.gmt
> binaries
> NT (XmiEmitter.dll,
> UmlxDecorator.dll)
> doc
> umlx (UmlxGraphicalLanguage.doc)
> examples
> compiled
> models
> libraries (nicexsl.jar, saxon.jar)
> tools
> gme
> XmiEmitter (~20 DevStudio sources)
> UmlxDecorator (~20 DevStudio sources)
> transforms
> compiled
> models
> umlx
> bootstrap (~20 NiceXSL, XSLT sources)
> compiled
> xslt
> java
> ...
> language (Umlx.mga, Umlx.xmp)
> models (UmlxCompiler.mga)
> Comments?
> I had a rummage around to find typical copyrights, they're
> generally missing on low level stuff, but otherwise it seems to always
> be IBM et al. So I plan to put something like
>* ****
>  * XMI 2.0 Emitter for GME
>  *
>  * Copyright (c) 2003 IBM Corporation and others.
>  * All rights reserved. This program and the accompanying materials
>  * are made available under the terms of the Common Public License v1.0
>  * which accompanies this distribution, and is available at
>  *
>  *
>  * Contributors: E.D.Willink
>  *EDW  2-Dec-2002 Original
>  *EDW 27-May-2003 Change xmi:type to xsi:type
>* ***/
> on files with a non-trivial manual contribution.
> Regards
> Ed Willink
> ------------------------------------------------------------------------
> E.D.Willink,                             Email: mailto:EdWillink@xxxxxxx
> Thales Research and Technology (UK) Ltd, Tel:  +44 118 923 8278 (direct)
> Worton Drive,                            or  +44 118 986 8601 (ext 8278)
> Worton Grange Business Park,             Fax:  +44 118 923 8399
> Reading,   RG2 0SB
> ------------------------------------------------------------------------
> (formerly Racal Research and Thomson-CSF)
> As the originator, I grant the addressee permission to divulge
> this email and any files transmitted with it to relevant third parties.
> _______________________________________________
> gmt-dev mailing list
> gmt-dev@xxxxxxxxxxx

gmt-dev mailing list

Back to the top