Alternatives
in [Visual Basic]
|
From: Tom Shelton on 15 Jan 2009 20:36 On 2009-01-15, Schmidt <sss(a)online.de> wrote: > > "Ulrich Korndoerfer" <ulrich_wants_nospam(a)prosource.de> schrieb im > Newsbeitrag news:%23kMNzyydJHA.3792(a)TK2MSFTNGP02.phx.gbl... > >> Did you write a VB binding wrapper for Cairo? > Yep - "over Christmas" to present myself a nice gift... ;-) > Interesting choice... Mono uses Cairo in it's System.Windows.Forms implementation. Should be good. -- Tom Shelton
From: Karl E. Peterson on 15 Jan 2009 21:34 Bill McCarthy wrote: > Note MSFT dropped in 2000, and has remained pretty much flat since. > Absolutely no correlation to the NASDAQ or DOW etc. The correlation is to Ballmer's ascendency, which corresponded to the first previews of VB.NET at PDC... http://vb.mvps.org/images/ballmerceo.gif Ballmer has to go! -- ..NET: It's About Trust! http://vfred.mvps.org
From: Karl E. Peterson on 15 Jan 2009 21:40 Ken Halter wrote: > want to go today" question, seems to be "To the nearest PC with Linux > installed". Several PC manufacturers are offering Linux as a choice these > days. I've been *totally* avoiding the Windows Tax myself, lately! http://www.dell.com/business/desktops?~ck=mn#subcats=&navla=80770~0~1791343&navidc=Operating%20System&navValc=FreeDOS%20and%20Linux&a=80770~0~1791343 -- ..NET: It's About Trust! http://vfred.mvps.org
From: Ulrich Korndoerfer on 15 Jan 2009 22:33 Hi, Tom Shelton schrieb: >>> Did you write a VB binding wrapper for Cairo? >> Yep - "over Christmas" to present myself a nice gift... ;-) >> > > Interesting choice... Mono uses Cairo in it's System.Windows.Forms > implementation. Should be good. It is a natural choice. Cairo is good and has some reputation (Olaf knows that of course). It is as powerful or even more powerful than GDI or GDI+, but more easy to wrap in VB. This is partially due to the fact that MS does not want to help VB programmers and so even a measely MS typelib for GDI+ is missing, not to mention a COM-wrapper. But of course DotNET wrappers are available from MS. The long term plan is to write a platform independent complete widget set (in VB) from scratch to replace the intrinsic VB widgets. So a powerful drawing engine is necessary. As a starter Olaf used GDI with the plan to replace it later by Cairo (because Cairo is platform independent). He realized that writing the drawing engine for the widgets by using GDI is more cumbersome than using Cairo in the first place, even when he has to write a wrapper for Cairo first. Cairo has been developed for being easily bound to other languages than the language it is written in (pure C). And it is easier to write widgets from scratch than writing VB wrappers for native Windows widgets. Perhaps not all functionality of the windows widgets will be implemented, but the most relevant functionality parts of them, those parts users use often. -- Ulrich Korndoerfer VB tips, helpers, solutions -> http://www.proSource.de/Downloads/
From: Schmidt on 17 Jan 2009 09:07
"Tom Shelton" <tom_shelton(a)comcastXXXXXXX.net> schrieb im Newsbeitrag news:%23kGLXr3dJHA.1184(a)TK2MSFTNGP05.phx.gbl... > Interesting choice... Mono uses Cairo in it's System. > Windows.Forms implementation. Not only there - the Mono-project is using Cairo under the hood of their System.Drawing namespace and their GDI+ implementation (and also in Moonlight). Cairo is also the rendering-engine of the platform- independent GTK+ widget-set - indirectly also the *native* widget-engine of Mono (GTK#). And those who are using Firefox 3, already have their "daily dose of Cairo-experience" (so to say). Strg+Mousewheel - that's the: "must-be-Cairo-powered"- Aha! effect... ;-) Olaf |