[Mono-list] Components, Controls, and Code

[Rob.Tillie@Student.tUL.EDU]

Hello,

> > Now that Mono is becoming highly functional, has anyone
> > considered doing an analysis to see what the most needed
> > components/controls might be
> None that I know of.
> >  and starting a group to
> > develop these controls. For example, a reporting tool like
> > Crystal Reports would probably be high on the list.
> Crystal Reports is HUGE, I think it needs to be tackled by its own
> development team.

Mono is becoming highly functional, but by no means finished. Of course it
is a good idea, but wouldn't these resources be better spent on the mono
project itself?

> I think one of the major steps can actually be taken quicker, and
> involves virtually 0 effort. Right now there are 100's of C# projects on
> SourceForge. We really need a team to look at the ones that are
> alpha/beta/production quality, and attempt to get them running on Mono.
> I know that in one weekend I was able to catch 3 or 4 bugs just by
> trying to get BlogX running on Mono (it now works great, thanks to our
> friend Gonzalo!). These apps are test cases waiting for use. Also,
> GotDotNet workspaces would provide a source of possible test cases.
> 
> As well, it would be nice if we could lean a bit on the C# Open Source
> community and request that they include makefiles with their apps and
> attempt to make them Mono friendly. I think the best way to go about
> this might be to create a set of "Mono QuickStarts" that spotlight Open
> Source software that works out-of-the-box on Mono -- alot of projects
> will try to meet that description.

Now this is a wonderful idea! A sort of "Mono-certified ;) " projects
gallery :). That would be a splendid idea indeed.

Greetz,
-- Rob.