dimanche 9 janvier 2005
21:06, Par alexandre jenny :: Coding, Dev

Développer des applications web en XUL

http://xulfr.org

Tient, voila une technologie mature, intéressante et totalement inutilisée ... Pourquoi ? Parce Microsoft ne l'utilise pas (sauf peut-etre dans un ersatz sous longhorn le XAML)

2 commentaires :: un trackback

lundi 3 janvier 2005
16:52, Par alexandre jenny :: Coding, Dev

.NET Connector for MySql

Enfin, j'attendais cela depuis longtemps, un wrapper natif officiel .NET pour MySql. Cool :-) http://dev.mysql.com/downloads/connector/net/1.0.html

2 commentaires :: 2 trackbacks

dimanche 2 janvier 2005
20:35, Par alexandre jenny :: Coding, Dev

Quelques découvertes

2 commentaires :: un trackback

18:55, Par alexandre jenny :: Coding, Dev

Multiplatform Coding

  • Qt Commercial
  • GTK+/GTK.mm has been ported, but Windows port is not really efficient and sntax maybe somewhat confusing to Qt developers. There's not real signal/slot mechanism, you'll have to use libsigc++ for this.
  • WxWidgets is portable, has a correct OO paradigm, is easy to learn and maintain. Its only drawback could be its peculiar syntax in some ways. For its main advantages, it has a native look and feel for all platforms.
  • Fox Toolkit is very nice, has a somewhat Qt like architecture, and is easy to learn, read and maintain. Drawbacks: whatever pltform you'll use it, it has the Windows look and feel. Technically, it does not like STL and somewhat limited when it comes to databases. In this way, real portability may be hairy.
  • FLTK is very light and produces nice apps. No real database support, no signal/slot mechanism, you're back in the callback world.
  • P::Classes is the most Qt like framework, with a signal/slot mechanism. But it has no graphics widgets. SQL model is nice.
Threading or not!

This is no more a problem, as all toolkits from 1 support threading.

Need database access or not!

Qt and P::Classes have a nice database handling. For others, you're stuck in external libraries or other abstraction layers wich might complexify maintenance.

I18n support or not!

All toolkits have some form of I18n., being good or bad upon target platform.

Memory footprint!

This is the most challenging option between kits. FLTK is the winner with the smallest one, when not bloated by extension libraries. P::Classes is great for non graphics apps, with an under 100K footprint. GTK+ needs a huge list of external libraries when developing useful programs and is a memory hog. Others fit in a medium range, Fox being close to Qt in memory use.

Execution speed!

All can be ranged from excellent to bad according to programming practise with the kit tricks.

Development and port charge!

Depends on programmer skills, amplitude of rewriting and kit syntax. GTK+ is the most difficult to master with its thousands of calls, not always clearly documented. FLTK and its Fluid designer is the winner.

Articles : http://freshmeat.net/articles/view/928/

67 commentaires :: 523 trackbacks