Hi Miguel,
Is there an ETA on merging your large fork. I don't want to get started
on anything that you guys have already done?
Or could you tell us which areas to stay away from for now? Personally, I
would want to look at some of the system.web things.
Thanks
Martin
On 15 Nov 2014 03:07,
I've been working on C# bingings for Qt at https://github.com/ddobrev/QtSharp .
They are not complete yet, I've been looking for funding so that I can focus on
them full time.
On Saturday, November 15, 2014 3:55 AM, Brandon Perry
bperry.volat...@gmail.com wrote:
Xwt aims to be a
Hello Atsushi Eno,
When will Mono be replacing its library with the MS's contribution?
MarL
--
View this message in context:
http://mono.1490590.n4.nabble.com/Mono-Net-difference-handling-xs-extension-please-help-tp4664552p4664621.html
Sent from the Mono - Dev mailing list archive at
Hello,
We worked only on System.Configuration, regex, the crypto and web stack.
The rest you can do, including the web stack.
I took a look at asp.net. I think in the long term we want to replace
most of it, but it needs to be done in stages, as it still contains a bunch
of native stuff.m
So has it been merged yet?
I'm going to look at the Buffer stuff I shy'd away from before. Then look
at the MachineKey.Protect stuff to implement the things I missed.
I've got a separate question around the mismatch in conventions, but I'll
ask that on a different thread.
I'm struggling to
It hasn't. When we do, we will announce.
Two issues: we worked with reference source and the github push is only
slowly getting the bits. And the second is that the layout they are
pushing is different.
On Saturday, November 15, 2014, Martin Thwaites monofo...@my2cents.co.uk
wrote:
So has
Hi All,
I'm looking into porting some code over from the reference source, and I've
noticed that it doesn't match the mono coding conventions.
Things like spaces instead of tabs, no space before the opening bracket in
a method call etc.
They seem like minor things, so I'm curious what the
What's the plan on where there are differences in behavior? An example of
this would be uri matching. I would guess it makes sense to use the ms
stuff moving forward, how will changes in current behavior be communicated
On Saturday, November 15, 2014, Miguel de Icaza mig...@xamarin.com wrote:
Each one needs to be discussed
Some of the Ms behaviors don't work on Unix, so not only we shouldn't bring
it, we should work towards a better shared set of new Apis
Not sure what you meant in this specific case.
On Saturday, November 15, 2014, Greg Young gregoryyou...@gmail.com wrote:
What's
Most of the time we just reference the file, so we shouldn't make style
changes to it.
In the cases where we only bring bits, we have a spectrum of options from
using partial classes to having to copy-paste and only in hat case we would
reformat
On Saturday, November 15, 2014, Martin Thwaites
A planning process will take time. Or you can step up and do the work and
contribute it
On Saturday, November 15, 2014, MarLOne infoseeker...@gmail.com wrote:
Hello Atsushi Eno,
When will Mono be replacing its library with the MS's contribution?
MarL
--
View this message in context:
Given these obstacles, I think that going forward with the originally
announced plan of removing non-4.5 profile support from the current Mono
code base - without introducing MS code yet - would make the gradual
adoption of MS code much easer.
On 11/15/2014 2:11 PM, Miguel de Icaza wrote:
It
Hey,
It is a tangential problem.
The big problem with removing the profile right now, is that removing it
causes F# to fail building.
We are trying to fix that.
Miguel
On Sat, Nov 15, 2014 at 10:05 AM, Kornel Pal kornel...@gmail.com wrote:
Given these obstacles, I think that going forward
Let me give more color on the situation.
Tasks:
- *Not building the 2.0 Profile*: while this is a very simple change, it
currently breaks the F# compilation. I have to dig out the reasons, I can
not remember why, but it does. Something related to MSBuild targets or
something.
So is the plan to pull the repository in as a submodule to reference the
files? Maybe we could that part committed so we can start referencing the
files?
I'm not sure how a partial class approach would work (all the MS Classes
seem to not be partials), so if you could maybe provide some examples
Thanks Miguel,
That clears up a lot. I'll wait until Monday before I ask more questions
:-D enjoy the weekend.
Martin
On 15 November 2014 15:58, Miguel de Icaza mig...@xamarin.com wrote:
Let me give more color on the situation.
Tasks:
- *Not building the 2.0 Profile*: while this is a
I think that what Miguel intended to say is to use Microsoft source only as
reference.
-Original Message-
From: Martin Thwaites monofo...@my2cents.co.uk
Sent: 11/15/2014 2:15 PM
To: Miguel de Icaza mig...@xamarin.com
Cc: mono-devel-list mono-devel-list@lists.ximian.com
Subject: Re:
I have found GTK# to be more than adequate, and it is possible to ship your
binary with it embedded for Windows.
Johnnie Odom
Brief, because this message was written on my iPhone.
On Nov 14, 2014, at 9:35 PM, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
I'm aware of
Yes, that is the idea.
But work can start without the sub module.
As for partials: it is easy, just patch the source to add partials where
necessary
On Saturday, November 15, 2014, Martin Thwaites monofo...@my2cents.co.uk
wrote:
So is the plan to pull the repository in as a submodule to
From: Brandon Perry [mailto:bperry.volat...@gmail.com]
Xwt aims to be a solution to this.
https://github.com/mono/xwt
Thanks for the suggestion.
Sent from a computer
No way...;-)
___
Mono-devel-list mailing list
Does this announcement mean that people who have seen parts of rotor in the
past will no longer be prevented from contributing to Mono?
Stan
From: Miguel de Icaza mig...@xamarin.com
To: mono-l...@lists.ximian.com mono-l...@lists.ximian.com; mono-devel
mono-devel-list@lists.ximian.com
21 matches
Mail list logo
