This might shape up to be fun. C# it is.
My question about, "Why a thing should not be done..." is to get people to approach a problem solution from all the angles. Usually when you have a problem you are attempting to solve the first solution that comes to mind is what most people go for. If you can stop yourself and ask, "Why should I not solve this problem?" Invariably what happens is that you wind up proving why your first solution is good or you lead yourself to another better solution.
Someone might have replied and said, "We don't need a graphical editor at all. I've been working a long time on one that runs using PHP and MySQL it's almost done. Have a look." In this case, we just saved ourselves some work. Another example might be, "I've tried this in the past with other things and it wound up not working. Here's why..."
As you all know developing software is expensive. I have people that pay me $100 an hour to write systems for them. So I think it's good for us to go slow as suggested. I also think it's always a good thing to stop peridically and take an assessment of what has been accomplished. Have we met our goals? Are we doing what we set out to do? I always try to attack and rip apart my own design's and solutions to make sure I'm really developing a refined product or solution.
As to needing a special place to work on this I'd have to say that depends on how this thing evolves. The prudent part of me says that nobody should do much of anything until we have a little more than something.

So in time we may need a better infrastructure to support the work on this. For now let's keep foot-loose and fancy-free here in this thread. I'll start working on a design. The design is going to take some time as I need to look over the entire milonic property list and get familiar with it. Let's say by Sunday (02-20-05) that will be done. Once that is done I will start to put together a design. That should not take more than about 7 days. So by 02-27-05 we should have something to discuss in greater detail.
Now some other questions.
I have Visual Studio .Net but I'm guessing that not everyone does. If everyone does have VS .Net then no problem. If they don't I suggest that the project be done entirely in Mono that way anybody can participate who wants to. Which leads to the next question. At this point who is planning on joining in the fray

and what tools do you have?
{Edit} I just realized this thread got moved to a fine home. Seems like it will work just fine for the moment. {/Edit}
- Rex
Windows XP SP1a all updates, Toshiba Satellite Pro 1955-S805; 1 Gig Ram; 2.53 Gig Processor