3 There are many pending classes that need to be implemented. Those have
4 the highest impact in the Mono project: the sooner they are done,
5 the sooner we can start using this platform to create new and
8 That being said, if you are not very excited about working on class
9 libraries, here is a list of other related projects or tools that might
10 be useful to the Mono project.
12 Here are a few ideas of tools, classes and projects that you
13 could start. More are forthcoming.
22 * Implement a JXTA protocol implementation:
23 <a href="http://www.jxta.org">http://www.jxta.org</a>
25 * Implement a Mail API, similar to Camel or JavaMail (Camel has
26 significant architecture features that are required on a real
29 You can check the current C
30 <a href="http://cvs.gnome.org/bonsai/rview.cgi?dir=evolution%2Fcamel">
31 Camel implementation</a>.
33 Such an implementation could be used both with
34 Microsoft .NET and Mono.
36 * Interfacing to Multimedia systems. You might want
37 to look into the Quicktime API. I know <a
38 href="mailto:vladimir@ximian.com">Vladimir</a> has
39 researched the problem before
46 This list of projects ideas is outdated
48 * Once <a href="http://remoting-corba.sourceforge.net/">CORBA</a> is done, implement the Bonobo interfaces
49 to allow people to use Bonobo components in Mono and
50 Mono components with Bonobo. The best of both worlds!
52 * A naming space for Mono. An object naming space is
53 a very powerful tool. Bonobo implements a moniker
54 system that is more powerful than the original
55 moniker concept that was pioneered by COM/OLE in the
58 Our implementation builds on a concept, and we have
59 made it simpler, more powerful, more extensible and
60 a much better mechanism than the equivalent monikers
63 Implementing Mono monikers would benefit both
64 Windows users using .NET and Mono users on Unix and
68 href="http://primates.ximian.com/~miguel/monikers.html">an
69 overview of the moniker system</a> in Bonobo.