At 09:04 AM 11/14/2006, Philip Covington wrote:
>On 11/14/06, Bob McGwier <[EMAIL PROTECTED]> wrote:
>
> > I am very wary of using Mono for a major development until ALL of the
> > implications of the MS/Novell situation fall out. I am personally
> > concerned that with the Mono development being
While "competition"
Ridicule;
FUD;
Embrace and Extend;
Inject IP;
Litigate;
Eliminate;
I would guess we are at the start of the "embrace and extend" clause.
> ...
> I am very wary of using Mono for a major development until ALL of the
> implications of the MS/Novell situation fall
On 11/14/06, Bob McGwier <[EMAIL PROTECTED]> wrote:
> I am very wary of using Mono for a major development until ALL of the
> implications of the MS/Novell situation fall out. I am personally
> concerned that with the Mono development being hosted at Novell, and the
> potential problems they have
Bob McGwier wrote:
> I am very wary of using Mono for a major development until ALL of the
> implications of the MS/Novell situation fall out. I am personally
> concerned that with the Mono development being hosted at Novell, and the
> potential problems they have caused for themselves with re
I whipped up a twenty button GUI and picture box using Monodevelop and
GTK# and the stetic form developer in about 20 minutes. 15 of those
were learning my way around the toolbars, etc. However, anyone doing
it will find it has a familiar feel if they have used VS before. It is
the same kin
Mono 1.2 has been released with almost full support for Winforms. I
say almost because I have found that about 90% of my Winforms code
compiled for .NET also runs under Mono 1.2 without recompiling. This
is much better than a few months ago when I did the same test. There
are a few Winforms comp
6 matches
Mail list logo
