Fwd: [Mono-devel-list] How can Mono Existing if WinFX, Avalon, Indigio and Aero comes up with Longhorn and WinXP?

falkmilan at yahoo.de falkmilan at yahoo.de
Mon Sep 13 12:38:59 EDT 2004


Hi Simon,

I undestand your Point of View and i dont wanna compare Java and Mono.
I think the discussion started wrong up. I think, if Mono walks more 
idependant iit
is the better Solutions as trying to rewriting Code Monocode thadt was 
developed
by Microsoft.

A Mono with a VM Technology, thadt run independently on the most Target
Paltform has greater Advantages and a better overall Situation.

Falk

Simon Bain wrote:

> Falk hi.
>
> I am very impressed that you have made time to do so much research. 
> However the point remains that people in this newsgroup, are at this 
> moment interested generaly (big assumption sorry people) in discussion 
> about development with Mono.
>
> This is not to say that your discussion is not of interest, as I am 
> sure that their are poeple out there that will find it of interest. 
> But as you can see from the replies this is not the group. If you wish 
> to compare Sun and Novell then find another group, if you wish to 
> compare Java with C# I know that there are plenty of groups out there 
> doing just that. (Take a look at the borland newsgroups).
>
> However here as I have said generally people are looking to either
> Solve bug issues (yes there are some and the developers seem to be 
> very willing to admit it)
> Get help with coding issues
> Get help with XSP
> and other application development items.
>
> All the best and if I see a post on another group by you on the issues 
> of Where can Mono go, or Java vs C# or ... Then I will gladly take 
> them head on.
>
> Simon
> -- 
> Simon Bain
> TENdotZERO
> ----------
> XML Open Conference Speaker:- Data Integration with XML and Mono
> http://www.xmlopen.org
> ----------
> XML 2004 Conference Speaker:- e-Voting
> http://www.xmlconference.org/xmlusa/
>
> > Oh what iam reading on the Mono Roadmap an go-mono
> >
> >
> > Mono and WinFX: 2006
> >
> > WinFX is the name given to the new set of libraries that makes up .NET
> > in the Longhorn operating system: the existing .NET set of class
> > libraries, plus the new functionality available in the OS.
> >
> > WinFX adds things like storage facilities (WinFS), a new versatile
> > communications stack (Indigo) and a new eye-candy packed GUI 
> programming
> > system (Avalon).
> >
> > Although WinFS, Avalon and Indigo are very exciting components, at this
> > time it is too early to tell when those components will be available 
> for
> > Mono. Open source developers will very likely start work on these, but
> > since they are still far from being officially released, they are 
> not in
> > the radar at this point.
> >
> > Source:
> > http://www.go-mono.com/mono-roadmap.html
> >
> > I think is Time to wake up.
> >
> > Falk
> >
> >
> >
> > John Bailo wrote:
> >
> >>On Sunday 12 September 2004 05:59, falkmilan at yahoo.de wrote:
> >>
> >>
> >>>Hi Monofolks,
> >>>
> >>>In the Last Days i hve reading some Microsoft stuff about, chaning
> >>>WinForms to the new
> >>>managed Code API called WinFX. WinFX includes an .NET Managed 
> Windowing
> >>>Toolkit and
> >>>WinForms will be deprecated in Future (there are Statements on the
> >>>WinHEC thadt Microsoft takes
> >>>care for a Interoperatibility, but i dont know...).
> >>>
> >>>
> >>
> >>Well, you should read more recent news. WinFX has been scraped because
> >> M$ can
> >>barely get LongWait out the door.
> >>
> >>
> >>
> >>
> >>>The New GUI Windowing System is based on XML (a Subinterpreation 
> called
> >>>XAML) and should
> >>>allow more seamless Things between Documents and Application 
> Windows or
> >>>something like thadt.
> >>>
> >>>
> >>
> >>We heard it all before.
> >>
> >>
> >>
> >>>WinFX is integrated into Longhorn and it can be installed to WinFX and
> >>>is Microsoft longterm
> >>>Plan for .NET and Windows together (i think it is clear why they are
> >>>doing thadt, to bring trouble
> >>>to Mono)
> >>>
> >>>
> >>
> >>mono comes with the Suse distro. Novell could easily integrate mono.
> >>
> >>
> >>
> >>>Anyway, the .NET Runtim and many Things from Longhorn would be
> >>>rewritten from C/C++ to C#
> >>>and Managed Code. The .NET Runtime will be a integrated Component
> >>>inside the Operatingsystem
> >>>and any other Programms should based ont it.
> >>>
> >>>I dont know what is up with the Win32-API but it looks like, thadt
> >>>Microsoft will the Support cuttof after a Time.
> >>>
> >>>
> >>
> >>Basically Microsoft realizes it has a garbage OS and is trying to 
> make it
> >> as
> >>much like Linux as possible.
> >>
> >>
> >>
> >>
> >>>The Webbrowser Internet Explorer will also as Webcomponets fully
> >>>integrated with
> >>>Windows Longhorn.
> >>>
> >>>
> >>
> >>How much did Steve Ballmer pay you to write this email ?
> >>
> >>
> >>
> >>>ps:
> >>>I think MS will go on and make the Next Visual Studuio Version a 
> Mix of
> >>>WinFX and other
> >>>Longhorn Technologies.If this comes true, then it cannot be run on 
> Mono.
> >>>The Only way is, to
> >>>cover the complete WinFX API with all Sub API thadt are Close Source.
> >>>
> >>>Falk
> >>>
> >>>
> >>
> >>Is that Falk, or Fake ?
> >>
> >>
> >>
> >>>_______________________________________________
> >>>Mono-devel-list mailing list
> >>>Mono-devel-list at lists.ximian.com
> >>>http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>>
> >>>
> >>_______________________________________________
> >>Mono-devel-list mailing list
> >>Mono-devel-list at lists.ximian.com
> >>http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>
> >>-------------------------------------------------------
> >>_______________________________________________
> >>Mono-devel-list mailing list
> >>Mono-devel-list at lists.ximian.com
> >>http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>
> >>
> >>
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
>




More information about the Mono-devel-list mailing list