![]() containing fragments of HTML rather than semantic descriptors, or deep integration with Win32 peculiarities). The secondary limiting factor is that our code often is too tightly bound to a particular GUI model (e.g. to allow some parts of a program to run on the client, and other parts on the server. Today, the main limiting factor seems to be that most languages don't have effective support for partitioning or code distribution - i.e. if you can 'serve' a web page, why not also 'serve' a wx form? A sort of parametric cross-compilation to different client models need not be very difficult if you have a good abstraction for API (and client parameters and extensions). I wouldn't be surprised to see such idioms in other apps - i.e. I think I could get a lot more bang for each line of code if I focus on app servers rather than direct use of keyboard/video/mouse/sound - and that, with a little careful design and abstraction, I could still effectively support the 'local canvas' (wx, local audio, OpenGL). (And there are probably more I don't know or don't recall.)Īnd I'm currently thinking about how to support it from Haskell - albeit, mostly in context of my Sirea project. Haxe, Curl, Ur/Web, and GWT are close on the languages side. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |