On Feb 25, 7:24 am, asbjornu <
asbjo...@gmail.com> wrote:
> On 8 Feb, 18:32, "Sandy Armstrong" <
sanfordarmstr...@gmail.com> wrote:
>
> > I think SD has dependencies on Windows- or MS.NET-only libraries. For
> > them, it is probably not acceptable to be restricted to the features
> > available in Mono.
>
> Hm, ok. Wouldn't it be possible to only have two separate builds,
> then? You'd need that for targeting specific platform GUI frameworks
> anyway. What specific Windows-only libraries are SD using?
The difference between using System.Windows.Forms+System.Drawing and
GTK#+GDK# represents a huge change to the codebase. Maybe 30% of our
code -- maximum -- is cleanly GUI-free, and we've put some effort into
maintaining a GUI/non-GUI split where possible.
The bits we could in theory share are mostly difficult to coordinate
sharing, because any changes to non-GUI code would have to be
reflected in both sets of GUI code. All developers would have to be
completely familiar with both GTK# and SWF. It would make coding very
frustrating, always waiting for the developers of the other GUI.
> > This is aside from the fact that they are each designed to fit into
> > their native platforms.
>
> From a GUI standpoint, I get this. What I'm interested in seeing
> shared is the underlying codebase, with regards to code lexing,
> parsing, compiling, syntax highlighting, intellisense, refactoring,
We do use #Develop's NRefactory C# and
VB.NET parser, and contribute
changes back. We're certainly interested in sharing components that
can be isolated like this.
> documentation, etc. I'm positive that the MD and SD codebases could be
> harmonized and the GUIs made independent enough to be able to
> accommodate both groups and platforms equally and satisfactory. It's
> obviously not a simple task, but considering the extremely bright
> minds working on both projects, I'd think it should be more a question
> about "time" and "when" than about "if" and "how".
I think you strongly underestimate the difficulties -- of isolating
enough of the non-GUI layer to make it worth sharing, maintaining two
GUI whenever this layer is changed, and of merging codebases that have
been independent for four years.
> > I'm curious to see how Mac enthusiasts adapt MD to fit better into
> > OS X.
>
> If MD and SD shared the underlying codebase and had a more independent
> GUI layer, this would be a matter of creating a new GUI layer
> specifically for Cocoa. As you can see from the MD on OS X
> screenshots, it looks rather bastardized with the menu bar inside the
> application instead of top-aligned, etc. It's a great step in the
> right direction, but without a special-tailored GUI, MD will probably
> never look like a native OS X application.
Geoff already has code to fix the menu bar. With a good GTK# theme, we
can at least make it feel comfortable, even if not native.
Michael