Working Version? (Mono.TextEditor/Gui/TextArea.cs(3241,22): error CS0101)

[sushihangover]

I was wondering if there is something I was missing in getting a lib compiled for the master branch or if this is still a 'work in progress'? I have been using the Mono.TextEditor under GTK# but have a need to get multi-line text editing with highlighting (an OMeta grammar workbench) within an XWT app. Thanks in advance for any help with this :-)

Cloned it and init'd/updated the nrefactory & xwt submodules, but get a compile error:

…
Mono.TextEditor/Gui/TextArea.cs(3241,22): error CS0101: The namespace `Mono.TextEditor' already contains a definition for `PaintEventArgs'
                Mono.TextEditor/Gui/PaintEventArgs.cs(32,15): (Location of the symbol related to previous error)
...

Just doing a xbuild on the Mono.TextEditor.XWT.sln.

I was hoping not to have to do complete conversion of Mono.TextEditor to XWT as Lluis Sanchez Gual recommend in an email….but...

Mono JIT compiler version 3.2.5 ((no/964e8f0 Thu Nov 14 14:48:50 EST 2013)
OS-X 10.8.5 

[aBothe]

I'm sorry to disappoint you, but this is still a work in progress and can't be compiled - anyway, if you want to continue the work, feel free to copypaste the code and get it to work :)

Originally I planned this to be a project for my university - but I think I'll continue to work on it next february

[sushihangover]

Thanks for the reply. I'll have to see if I have the time to go this route, or drop XWT totally and redo it for GTK# (GTK2.x yuk!, if GTK3.x was supported…).

Thanks again…

[aBothe]

Please NOT GTK! :o - It's MD worst troublemaker

[sushihangover]

LOL!!!! GTK sucks under MD/Xamarin….

If you use Stetic designer and save a source file with a syntax error, your event links to the designer are gone, that is an on-going bug for 4+ years!!!!…

Need to embed a widget inside another widget in GTK2? Well, is it a container or not? odds are NOT, your screwed…

Need to capture an event but it is gets consumed within GTK itself? re-parent that tree of widgets to an event-box, apply the prior attribute to the event capture and write filters to handle/re-dispatch the event(s) you care about (WTF?)

GTK3 fixed most(all?) of the low level items and works really well under C++… look at how well (and easy) it works under the Python bindings, but Xamarin will never move off of GTK#/GTK2.x until the entire MD GUI is XWT based and that is really really really low on their list… Mobile first, XWT only for ''new" work and when they have the time/money they will get to the other areas…

I could go on and on about GTK… but I would just end up balled up in corner crying (again). ;-)

-R

On Fri, Dec 6, 2013 at 1:27 PM, Alexander Bothe notifications@github.comwrote:

Please NOT GTK! :o - It's MD worst troublemaker

— Reply to this email directly or view it on GitHubhttps://github.com/aBothe/Mono.TextEditor.XWT/issues/1#issuecomment-30030883 .

[aBothe]

"Mobile first, XWT only for ''new" work"

This is something which lets me fear the future of XS - Will there be ever a full re-base to e.g. XWT or at least gtk3?

[sushihangover]

From what I seen in the blog posts/mailing list, GTK3 will not happen until "everything" is on top of XWT and thus you can just write a new XWT engine to point at GTK3 (for Linux at least). This means a lot of work needs to be done, XWT designer needs to be written, etc… There is a list of long term goals/milestone posted somewhere for XWT (without any dates).

The work that they are doing for mobile GUI designers is based on XWT and works/looks great since it is rendered natively on Windows/OS-X as that is their company focus for XS and the VS plugin. Of course this code base is not open-source and I understand that from a profit center viewpoint… they are really making in-roads with Microsoft and .Net developers due to their CLR code reuse across mobile devices, Azure support, iOS, Andriod/Glass, WinPHone, added portable assembly support for iOS/Android, etc… BUT that leaves the XS desktop application devs feeling abandoned, but they are not making money from that market (i.e.: me, as their Xam.Mac offering is not compiling enough for me to pay for).

If I was not a cross platform and C# coder kind-of guy, I would have dropped using Xamarin/Mono totally by now…. VS, while a huge pig of an IDE now (I consider it an Eclipse that actually works) is the best and only place desktop GUI based applications for the CLR can be written with an type of productively (I mean look at the GTK# widget selection under XS… , really sad, need a grid that you can get a 'cell' base mouse click event from? it does not exist.., out of the box under WPF, need nice business style charting, not in GTK#, browser widget? forget it in a cross platform way, etc...… it is there just not any $$$ there for Xamarin. i.e: How many Linux based devs paid for any of the toolsets/toolkits they are using right now?

I think a full GUI rebase of XS will happen at sometime in the future, but believe it will be the end of MonoDevelop without community support (IMHO) as XS will go Windows/OS-X only and just drop GTK… You can question even Windows support as their plugins for Visual Studio remove the need for a full XS install there… "If" Apple ever extended Xcode to allow a full plugin framework to support third party GUI editors and 'non-native' languages/toolchains, XS would become just a bunch of plugins and XS would not be needed at all. MonoDevelop would be orphaned at that point…

-R

On Fri, Dec 6, 2013 at 1:50 PM, Alexander Bothe notifications@github.comwrote:

"Mobile first, XWT only for ''new" work"

This is something which lets me fear the future of XS - Will there be ever a full re-base to e.g. XWT or at least gtk3?

— Reply to this email directly or view it on GitHubhttps://github.com/aBothe/Mono.TextEditor.XWT/issues/1#issuecomment-30032528 .

[aBothe]

Thanks for the notes! - Yeah, Linux is definitely not a 'target market' for Xamarin (anymore?). But well, it'll obviously take them a while in order to get XS rebased - and even if it was Xwt-based then, it might just take a while until some Wayland binding to XWT gets published..or not, if Mono/MonoDevelop should ever be that important to Linux (again)..kinda sad but perhaps a rational way to go. Btw, "I consider it an Eclipse that actually works" - true story :-D

A glimpse of hope could be that Linux is probably becoming more and more important (in the declining demand though) for desktops/laptops - so being the first with a VS-like coding environment that is not Java-oriented could have its advantages then. In combination with Wayland, probably Ubuntu's Mir or similar interfaces a better environment for coding games and..other stuff :)