Thread: [Dev-C++] Some Longhorn programming info
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
|
From: Ioannis V. <no...@ho...> - 2002-10-27 07:18:48
|
As i have said a few days ago, Longhorn will provide only a managed API (.NET). Here is some more info from a non-programming newsletter: =20 =20 - New applications and activity centers based on Longhorn's Avalon API, which appears to be an XML-based successor to the Win32 API that current Windows applications use. An example of this new type of application is Display Properties, which presents a vastly different UI from today's simple dialog boxes. In the Longhorn alpha screenshots I've seen, Display Properties is a single-window, task-based application that's similar to XP's User Accounts application. Another example of this type of application is My Hardware, which features a collapsible and graphic view of your PC's hardware divided into categories such as Audio Devices and Input Devices. =20 =20 Ioannis * Ioannis Vranos * Programming pages: http://www.noicys.freeurl.com <http://www.noicys.freeurl.com/>=20 * Alternative URL: http://run.to/noicys =20 |
|
From: staale <st...@le...> - 2002-11-05 18:09:47
|
Will not this make Longhorn unavailable to Dev-C++ compiled programs? In other words if you want Longhorn users to use your programs you will have to use VC.NET or whatever they call it these days..:o) Best Regards Staale At 09:18 27.10.02 +0200, Ioannis Vranos wrote: >As i have said a few days ago, Longhorn will provide only a managed API >(.NET). Here is some more info from a non-programming newsletter: > > >- New applications and activity centers based on Longhorn's Avalon >API, which appears to be an XML-based successor to the Win32 API that >current Windows applications use. An example of this new type of >application is Display Properties, which presents a vastly different >UI from today's simple dialog boxes. In the Longhorn alpha screenshots >I've seen, Display Properties is a single-window, task-based >application that's similar to XP's User Accounts application. Another >example of this type of application is My Hardware, which features a >collapsible and graphic view of your PC's hardware divided into >categories such as Audio Devices and Input Devices. > > >Ioannis > >* Ioannis Vranos >* Programming pages: ><http://www.noicys.freeurl.com/>http://www.noicys.freeurl.com >* Alternative URL: <http://run.to/noicys>http://run.to/noicys > |
|
From: Per W. <pw...@ia...> - 2002-11-05 20:33:20
|
Unless Microsoft will invalidate ALL existing windows applications - that's the applications that makes us stay with Windows, instead of using Linux, OS-X etc - they obviously must continue to support the Win32 API, in the same way that current Win32 platworms kept the support for old Win16 applications. Since I'm such a M$ lover, my hope is of course that they are stupid enough to remove Win32 support and let Linux rule :-) /Per W On Tue, 5 Nov 2002, staale wrote: > Will not this make Longhorn unavailable to Dev-C++ compiled programs? > In other words if you want Longhorn users to use your programs you will > have to use VC.NET or whatever they call it these days..:o) > > Best Regards > Staale > > At 09:18 27.10.02 +0200, Ioannis Vranos wrote: > >As i have said a few days ago, Longhorn will provide only a managed API > >(.NET). Here is some more info from a non-programming newsletter: > > > > > >- New applications and activity centers based on Longhorn's Avalon > >API, which appears to be an XML-based successor to the Win32 API that > >current Windows applications use. An example of this new type of > >application is Display Properties, which presents a vastly different > >UI from today's simple dialog boxes. In the Longhorn alpha screenshots > >I've seen, Display Properties is a single-window, task-based > >application that's similar to XP's User Accounts application. Another > >example of this type of application is My Hardware, which features a > >collapsible and graphic view of your PC's hardware divided into > >categories such as Audio Devices and Input Devices. > > > > > >Ioannis > > > >* Ioannis Vranos > >* Programming pages: > ><http://www.noicys.freeurl.com/>http://www.noicys.freeurl.com > >* Alternative URL: <http://run.to/noicys>http://run.to/noicys > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > |
|
From: Ioannis V. <no...@ho...> - 2002-11-06 00:53:36
|
> -----Original Message----- > From: Per Westermark [mailto:pw...@ia...] > Sent: Tuesday, November 05, 2002 10:33 PM > To: staale > Cc: Ioannis Vranos; Dev-C++ Mailing List > Subject: Re: [Dev-C++] Some Longhorn programming info > > > Unless Microsoft will invalidate ALL existing windows applications - > that's the applications that makes us stay with Windows, > instead of using > Linux, OS-X etc - they obviously must continue to support the > Win32 API, > in the same way that current Win32 platworms kept the support for old > Win16 applications. > > Since I'm such a M$ lover, my hope is of course that they are stupid > enough to remove Win32 support and let Linux rule :-) Well till 2004+, all will have moved to .NET. I do not what will happen will legacy code, but probably it will be lost. But I DO NOT KNOW. I am telling what i have read so far (and few things are available regarding Longhorn so far). Ioannis Vranos * Programming pages: http://www.noicys.freeurl.com * Alternative URL: http://run.to/noicys |
|
From: Ioannis V. <no...@ho...> - 2002-11-06 00:46:02
|
> -----Original Message----- > From: staale [mailto:st...@le...] > Sent: Tuesday, November 05, 2002 7:56 PM > To: Ioannis Vranos; Dev-C++ Mailing List > Subject: Re: [Dev-C++] Some Longhorn programming info > > > Will not this make Longhorn unavailable to Dev-C++ compiled programs? > In other words if you want Longhorn users to use your > programs you will > have to use VC.NET or whatever they call it these days..:o) Longhorn is still far away. It will even have an entirely different file system the WinFS, based on the upcoming SQL Server release (i do not remember its codename, my brain is very tired these days :)). It will be a database file system, that is one will be able to issue queries on it. My guess regarding managed APIs only support of Longhorn, is that it probably is part of the Palladium project, in which BillG must know all of your habbits (because he loves and cares about you as a Father, that's why) and this can't be done in Win32 API stuff. Longhorn will also have an advanced video api for amazing graphics. Expect Longhorn at the earliest in 2004. Imagine what computers we will have then (it's a century in computer time). Ioannis Vranos * Programming pages: http://www.noicys.freeurl.com * Alternative URL: http://run.to/noicys |
|
From: Ioannis V. <no...@ho...> - 2002-11-06 13:35:10
|
> -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf > Of Ioannis Vranos > Sent: Wednesday, November 06, 2002 2:46 AM > To: 'Dev-C++ Mailing List' > Subject: RE: [Dev-C++] Some Longhorn programming info > > > > -----Original Message----- > > From: staale [mailto:st...@le...] > > Sent: Tuesday, November 05, 2002 7:56 PM > > To: Ioannis Vranos; Dev-C++ Mailing List > > Subject: Re: [Dev-C++] Some Longhorn programming info > > > > > > Will not this make Longhorn unavailable to Dev-C++ compiled > programs? > > In other words if you want Longhorn users to use your > > programs you will > > have to use VC.NET or whatever they call it these days..:o) > > > Longhorn is still far away. It will even have an entirely > different file > system the WinFS, based on the upcoming SQL Server release (i do not > remember its codename, my brain is very tired these days :)). Today is another day. WinFS is based on the upcoming SQL Server's technology code-named "Yukon". > It will be > a database file system, that is one will be able to issue > queries on it. > My guess regarding managed APIs only support of Longhorn, is that it > probably is part of the Palladium project, in which BillG > must know all > of your habbits (because he loves and cares about you as a Father, > that's why) and this can't be done in Win32 API stuff. Longhorn will > also have an advanced video api for amazing graphics. > > > Expect Longhorn at the earliest in 2004. Imagine what > computers we will > have then (it's a century in computer time). Ioannis Vranos * Programming pages: http://www.noicys.freeurl.com * Alternative URL: http://run.to/noicys |
|
From: Ioannis V. <no...@ho...> - 2002-11-06 00:51:06
|
> -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of staale > Sent: Tuesday, November 05, 2002 7:56 PM > To: Ioannis Vranos; Dev-C++ Mailing List > Subject: Re: [Dev-C++] Some Longhorn programming info > > > Will not this make Longhorn unavailable to Dev-C++ compiled programs? > In other words if you want Longhorn users to use your > programs you will > have to use VC.NET or whatever they call it these days..:o) Yes the compiler must support .NET. Dev-C++'s MINGW will probably do so till then (but .NET is a different API). :) Ioannis Vranos * Programming pages: http://www.noicys.freeurl.com * Alternative URL: http://run.to/noicys |