> Of course, this leaves the problem of how to look and feel like a > native application on any given platform, among other issues. Using an > FFI to interface with a higher level toolkit like wxWidgets or TK is > undoubtedly the best way to go in the short term, but I think the > "best" long term solution is "Lisp all the way" - more work up front, > but the power of Lisp Graphics all the way down in the end.
You might want to follow the lead of SWT. The lower level directly maps to the host (ie whether Win/gdi, OSX/carbon or Linux/GTX) while the higher level homogenise all those interfaces into a single Display (and derived) and Shell (and derived) classes. They do use the native underlying OS widget set, yet shield you, the app programmer, from the differences. And yet, for an end-user there is almost no way to tell that the resulting app is not 100% native. The core "OS access level" is about 4 C files per platform, and the rest is 109% Java. There's no reason why we couldn't have a similar situation in CL. -- JFB _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
