From: Panayotis K. <pan...@pa...> - 2009-10-19 07:59:49
|
On 19 Οκτ 2009, at 8:25 π.μ., Arno Puder wrote: > > OK. I'm finally back online again… Welcome back :) > If I understand you correctly, you want to generate the ObjC file > from the Java wrappers? Yes, that was the idea. "Was", because now I am trying to improve the emulator. The current xmlvm Cocoa Touch support is extremely limited. Actually is supporting *only* what the Xokoban and iRemote applications need. ;-) Since I'd preferred a more complete environment, I'm heading towards this direction first. > I think the problem is more complicated and deserves more thinking. … I agree with your thoughts. My consideration was to at least have a nice wrapper where we can start from. It probably be able to understand empty selector implementations and implementations already be done, and don't change the latter. Doing everything completely automatic is interesting but it's not trivial (although we're here to discuss it). What I did at the end, as a temporal solution, is to make xmlvm create for me the ObjC wrapper of the library, as if it was code I'd like to use it (like android library). Then I manually edited the file and quickly added the implementation. To make sure that, in existing implementations I wouldn't overwrite anything useful, I created a batch script that compares the two .h files and displays only the differences. That is of course far away from the optimal, but at least it improved my speed with tools already existing. Now, about parsing the ObjC binary - I don't think this is the direction to go on. I find it safer to parse .h files from the SDK, since this is the actual "showcase" of the application. |