Re: Status thingy.

[Dave Camp <dave ximian com>]

On Tue, 2002-06-04 at 12:15, Johannes Schmid wrote:
> On anjuta-devel lists sourceforge net we have discussed a new template
> system for project and file generation. There does not exist any code
> and even when we start coding it will be mostly anjuta independent but
> it might be useful if you participate in the design decisions. The core
> is by Biswa, here is a copy:

This looks nice.  The project wizard I wrote is much more limited in
scope, and is slightly less or more flexible, depending on your point of
view :)

The way mine works is that there is a GbfDruidProject class that can be
derived from for specific types of projects.  It has methods like
get_druid_pages() (returns a list of GnomeDruidPages to place in the
druid) and write_files() (writes the files to the project directory). 

This is more flexible because you can write a C project generator that
can do basically anything.  This is less flexible because you have to
write a C project generator to do anything.

I'd be happy to switch to a project wizard using your approach. 


> Well that's about it - the so-called grand plan :-) Greatly in need of
> discussion, refinements, ideas, flames, etc ;-). If you noitice, I've
> deliberately kept this as Anjuta-independent as possible, since, as you
> say, the PM of Anjuta (and Anjuta itself, what with Anjuta2, etc.) is in
> a state of flux and our goal should be to create something which can be
> used in both the 1.x as well as the 2.x code base.

That's a good design choice in general anyway.  Even if things aren't in
flux, there's no reason to have unneccessary coupling in your code.

Sounds great.

-dave