
I find that very interesting ... doing the thing right or doing the right thing... old debate... IM(NS)HO, the second bigger risk is to get sidetracked, the first being that to have nothing... And if you consider that the Haskell Communitity is full of researcher, that risk cannot be discarded lightheartedly.. if you can achieve that the (few available) people / ressource can deliver a decent GUI, in 6-9-12 month time, that would probably a major achievement for the Haskell community, ... Haskell would then have a much bigger potential audience... which would in turn provide more ressource, which can then focus on nativeness... if that's still an issue... (Btw, Java, for instance, achieve "nativeness" on none of the platforms...) In other words, if you can provide me a treecontrol, a grid and D&D, even partially native, I would feel much cooler than just a "native" hollow hello world ... well, if on top you can get rid of a dependency on a external lib, that's perfect, but that's more of an "infrastructure" thingy ... especially if that lib is OSS... Luc (Just a basic green belt user..)
Wolfgang Jeltsch
wrote, On Wednesday, 2003-09-10, 12:47, CEST, Axel Simon wrote:
[...]
A quick poll at the Haskell workshop revealed that 1/3 of the people thought that the CGA approach is worthwhile, 2/3 thought that the cross-platform approach is adequate. Hence the CGA idea as it stands right now will not be pursued.
I have to say that I'm very disappointed by this decision. I was very enthused that there was such a strong focus on "nativeness" in the past because, in my opinion, this "nativeness" is very important. I fear that the wxWindows approach won't give us applications that conform to the platform-specific conventions very well. Therefore, I'm interested in developments like HToolkit where there's a strong emphasis on styleguide conformance.
Better a viable GUI binding with some reasonable level of nativeness now than chasing after the ideal binding for two years and be left with nothing.
What makes you think that the few people in the Haskell community who are interested in building GUI infrastructure can do a better job at a cross-platform API than the masses of GUI developers for whom this is their daily bread?
I think we are better off by piggy-backing on a major cross-platform effort driven by a large developer community than by wasting our time on trying to solve problems that the experts couldn't crack so far.
Cheers, Manuel _______________________________________________ GUI mailing list GUI@haskell.org http://www.haskell.org/mailman/listinfo/gui
participants (1)
-
list@taesch.com