Re: [Sunuml-developers] Language?

[Steven G. <laz...@gm...>]

Hello all,


2008/10/8 Matthew Slane <m....@bl...>

> > IMO both C+ and Python have advantages and disadvantages
>
> I'm advocating a bit of both.  Get something up and running in python.
> For a lot of the code, python will do, this is after all a GUI based
> program that will spend most of it's time waiting for user input.  Where
> things feel sluggish, reimplement in C++ to take advantage of the speed
> that C++ offers. Eventually, maybe move the whole codebase to C++?
> Something like Mcmillan or freeze could be used to
> distribute the app where python isn't already installed?


It seems the Python first and C++ later (or when needed) is slowly gaining
momentum.


> Can you all give an estimate on the level of commitment you can provide?
> >
> This is a difficult question for me to answer.  I've got an 8 week old
> son and am a father for the first time, so I don't know how much time I
> can dedicate.


I have boys of 4 and 2 years and I try to work at home since one year.
So by experience this means you still have about one year
where you can have some free time (of course it depends on the child
character).



> A "simple copy" of StarUML or should we add features?
> > Which ones?
> I haven't checked the code any further than skimming over a source
> file.  But I'd like to ensure a good separation of UI and core, so we
> can decide on a GUI library to use for the main project, but other
> people could implement their own using a different toolkit.  Maybe look
> at using MVC patterns to acheive this (if not already used)?  We could
> really take this to the limits and develop an ajax front end ;)
>

By experience once we choose a gui it will stick for a long time :)

As we all seem to agree we will use wxWidget (either the c++ or the Pyhton
version http://www.wxpython.org/)



I don't like the default single file structure, I'd prefer a project
> directory with separate files in.


It should be possible to have both and set it via an editor option.

I see several advantages of one big file: easy to
move/deploy/backup/transfer/email .. :D

But mostly it is easier to synchronise the content in a collaborative
project.
For example if you change a class name you must first lock all files on
writing
so that nobody else can modify a file before your changes or they might be
inconsistencies.


Anyway if we plan to support collaborative work I think we should use a
database from the start. MySql ?

I would love to support the *SQLite* but it doesn't support concurrent
access (except via database-wide lock on writing) so if we use it we must
first setup a "server" to handle user modifications. But badder it doesn't
have right management so we can't simply set the rights on table at the
database level (which would be safer).

What do you think? MySQL?



The current way diagrams are drawn feels clunky to me, this is a big
> area for improvement.


We wait your suggestions on the wiki :)



> > *@Matthew *Do you want to be developer ?
> > Or do you wait we decide for Python?
> >
> I'd love to, but see above!!


Done - don't worry to much we will certainly find tasks for you :)


Steven