[MonoDevelop] Assembly reorganization
monoman at gmail.com
Mon Jul 25 16:16:18 EDT 2005
On 7/25/05, Lluis Sanchez <lluis at ximian.com> wrote:
> > Also I disliked the IdeApplication name, I would prefer just
> > MonoDevelop.Application.
> I also don't like IdeApplication too much as well. However, I don't
> think that MonoDevelop.Application is also good enough since, as I said,
> there can be other MD based applications in the future. The namespace
> should differentiate the IDE application from other applications.
I know it is long but certainly the class name is seldom used/typed,
and the using clauses for the namespace are normally 'autocompleted',
It is the kind of name my classes and methods get as I deem
clarity/precision as much more important than source file size (look
at Mono.GetOptions sources to verify that).
Your definition for IdeApplication was worded as
> > * The Ide class: a root class for accessing all IDE
> > services (like we have Runtime for the core services).
And I think my long suggestion fits the "root class" concept well.
Also IdeApplication , in truth, didn't convey the "access to IDE
services" part so well, it kind of looked like an standalone/closed
The derived namespaces would have to be adjusted as well
Obviously there is the short form
MonoDevelop.IDE (I would abandon the norm of 'proper-casing' even
acronyms, for this case, as it brings enhanced recognizability for any
user of a modern IDE).
But I still prefer the longer form, just that no confusion with the
hardware meaning of IDE (Integrated/Intelligent Drive Electronics) can
take place, ever.
Rafael "Monoman" Teixeira
I'm trying to become a "Rosh Gadol" before my own eyes.
See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment.
More information about the Monodevelop-list