Difference between revisions of "Talk:Cocoa for EiffelVision2"
| Line 2: | Line 2: | ||
could serve as inspiration for the backend. | could serve as inspiration for the backend. | ||
| + | |||
| + | The basic approach would be: | ||
| + | * to write a very simple Vision2 application only showing a window. | ||
| + | * then we will have to write all implementation classes for the Vision2 widgets that will use the cocoa or carbon widgets internally | ||
| + | * these will be empty at the beginning and then slowly filled | ||
| + | * then one would start from the Vision2 event loop and try to fill the first implementation class, the one for the window probably | ||
| + | * and from there one would go to the other widgets | ||
| + | |||
| + | This is a very interesting project as it unifies many different widget toolkits, you learn lots about the widget toolkit on OS X. But it is also tricky because the widget toolkit on top of which you are also has bugs that you have to work around. For example in carbon the Bevel button in OS X does not display correctly when it's height is set to be smaller than 20 pixels. So if you provide an interface to that button, you would have to work around that. | ||
Revision as of 21:59, 11 April 2006
Maybe we should not target Cocoa, but carbon, just like SWT:http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt/Eclipse%20SWT/carbon
could serve as inspiration for the backend.
The basic approach would be:
- to write a very simple Vision2 application only showing a window.
- then we will have to write all implementation classes for the Vision2 widgets that will use the cocoa or carbon widgets internally
- these will be empty at the beginning and then slowly filled
- then one would start from the Vision2 event loop and try to fill the first implementation class, the one for the window probably
- and from there one would go to the other widgets
This is a very interesting project as it unifies many different widget toolkits, you learn lots about the widget toolkit on OS X. But it is also tricky because the widget toolkit on top of which you are also has bugs that you have to work around. For example in carbon the Bevel button in OS X does not display correctly when it's height is set to be smaller than 20 pixels. So if you provide an interface to that button, you would have to work around that.
