[MonoDevelop] SourceEditor: ideas

[John Luke]

On Wed, 2005-03-02 at 01:39 +0100, Ben Motmans wrote:
>On Tue, 01 Mar 2005 18:46:32 -0500, John Luke <john.luke@gmail.com> wrote:
>> I was just kind of cautioning you against confusing the base texteditor
>> infrastucture with parsing/other related features that would likely be
>> agnostic to an editor.  For example, C# 2 support is irrelevent here but
>> easy access to the document structure for refactoring isn't (and
>> something I agree we need).
>> 
>i am merely trying to create a list of features, ... that need to be
>taken into account when designing the editor, so i think all parts of
>MD that are somehow linked to the source editor are worth mentioning
>right now
>
>the more things we can think of now, the more flexible the design can be

I think I am not communicating this well, but I think coming up with
this list is likely to end with the conclusion 'we need to write
an(other) editor', which already happened once and was not really
completed.  Whereas approaching with "I know these are the specific
problems that cannot ever work this way" should be the first step.
Since we know the parser (with and without C# 2) will work with both the
SD editor and our current one it is likely to confuse this issue.

But, if the only real problem is having better control of things
internal to gtksourceview we know the answer is port it to C# so we
can integrate with the parser, override the menus, etc.

The original text editor was very flexible and the only reason I
remember being valid for switching from it was accessibility and
right-to-left support (surely I am forgetting something important).
It was perhaps slow and buggy because it was only an initial port.
At some point I hope someone revives it.

Hope that helps.
 
>> Ok, I was just trying to help you in gathering information while
>> recommending a course of action that is reasonable (i.e. where to look
>> archives & code).  Much of this was previously discussed in some detail
>> and some of us have already formed opinions on what is the best way to
>> go.
>> 
>> Keep in mind it is just my opinion after all.
>> 
>> 
>last couple of weeks, i studied some parts of SD/MD and eclipse source
>code, to see how things are done
>if you have some more information about older discussions about the
>source editor, please let me know
>
>i really appreciate your feedback, keep it coming :)
>
>-- Ben

Most of it should be captured in this lists archives, about 1 year ago I
think. It should be rather easy to find (google at least).