<div dir="ltr">Manfred,<br><br><div class="gmail_quote">On Thu, Oct 2, 2008 at 12:26 AM, Manfred Bergmann <span dir="ltr"><<a href="mailto:bergmannmd@web.de">bergmannmd@web.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Am 01.10.2008 um 21:17 schrieb Greg Hellings:<br>
<div class="Ih2E3d"><br>
> Manfred (and Chris),<br>
><br>
> On Wed, Oct 1, 2008 at 1:13 PM, Manfred Bergmann <<a href="mailto:bergmannmd@web.de">bergmannmd@web.de</a>><br>
> wrote:<br>
> Hi.<br>
><br>
> Good news for anyone wanting to start something native on the iPhone:<br>
> <a href="http://developer.apple.com/iphone/program/" target="_blank">http://developer.apple.com/iphone/program/</a><br>
><br>
> I already have the SWORD library building against the iPhone SDK in<br>
> XCode (the command-line building process simply doesn't work). I<br>
> can't get Eloquent to build for iPhone because of a few missing<br>
> Cocoa-based headers which the iPhone system doesn't have. I suppose<br>
> the next step is to go back to the drawing board and learn Objective-<br>
> C and the iPhone SDK's basic classes.<br>
<br>
</div>Yes, that may be.<br>
Which sources of Eloquent have you tried compiling? This project is<br>
rather old and you might want to use other backend sources.</blockquote><div><br>I'm trying to build the version out of SVN on googlecode. Is this the "latest" repo of it? As for other back end sources, I know of no other Obj-C back end sources for SWORD. If there are others, which are more up-to-date, I'll happily use them.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
I don't have an iPhone SDK installed but I would help porting the<br>
backend if needed.</blockquote><div><br>So far my errors are as follows:<br>SwordDictionary.mm can't find Cocoa/Cocoa.h or CocoLogger/CocoLogger.h.<br>SwordSearching.mm: missing headers - AppKit/NSApplication.h, Cocoa/Cocoa.h, Coco/CocoLogger.h, MBLOG/MBLOG_DEBUG/MBLOG_ERR macros missing, and class sword::VerseKey has no member named NewIndex on line 215<br>
SwordManager.mm - Cocoa/Cocoa.h and CocoLogger/CocoLogger.h and the MBLOG macros<br>SwordInstallSource.mm - same<br>SwordBook.mm - same<br>SwordCommentary.m - same<br>SwordInstallSourceController.mm - ditto<br>SwordModule.mm - ditto, plus "warning: 'SwordModule' may not respond to '-textForRef:'<br>
SwordBible.mm - same<br><br>So, it looks like, taking out CocoLogger/CocoLogger.h and finding what are the necessary includes for Cocoa/Cocoa.h instead, would alleviate almost all of the problems. The sample applications tend to include UIKit/UIKit.h in all of their files, and also in a .pch they include Foundation/Foundation.h. Just testing out a hypothesis... I merely commented out all of the includes that were raising errors (every inclusion of Cocoa/Cocoa.h, CocoLogger/CocoLogger.h, AppKit/NSApplication.h and all of the calls to MBLOG* macros), except for the errors about sword::VerseKey's member NewIndex, and the system builds fine, but for that one error. Perhaps it's not completely feature rich with all of the new Sword options, so that would be cause for future addressing, but I'm not close to ready to push those limits yet. ;)<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="Ih2E3d"><br>
> I have a general GUI layout in mind, so hopefully things will go<br>
> quickly once I get the hang of the RAD tools that XCode uses, etc.<br>
> They look like they should be rather simple, I just have never used<br>
> any type of RAD/GUI designing tools other than manual placement and<br>
> coding of interfaces.<br>
<br>
</div>Interface Builder is a really nice tool. Cocoa has the best<br>
implementation of MVC I have seen so far. Interface Builder really<br>
only creates the GUI and then you switch over to Xcode and do the<br>
Controller part.<br>
It is different compared to other language platforms but I like it.</blockquote><div><br>I detest all RAD GUI tools which I've tried so far. I can never find where to hook in my actual code to provide content, and Apple's attempt to simplify everything to the point of annoyance certainly does not help in that. I'm still just grasping at straws when it comes to the whole GUI/Controller dichotomy. I'd strongly prefer to do all the GUI creation directly in my own hand-writing, even if it means that I'll take twice as long as someone with RAD. In the end, I have code that I can work with and which I can complete long before I learn how to use a RAD tool. But, from the looks of things, Apple won't let you create interfaces without Interface Builder, so I suppose I'll have to buckle up and learn it. I just wish their developer documentation was more accessible to a non-OS X developer.<br>
<br>All-in-all, it looks like building on the iPhone shouldn't be a
problem, as long as we can clean up and keep up with the SWORD engine.
The only real hurdle now is whether or not yours truly can figure out
how Cocoa GUI programming is supposed to work. I work fine in the world of
the Java/wxWidgets/Qt style of C++ GUI interfaces. This doesn't seem
to resemble that in anyway. Maybe I'm just not looking hard enough -- any advice from an OS X programmer to a novice in the Mac/OS X programming world?<br><br>--Greg<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
<br>
<br>
Regards,<br>
<div><div></div><div class="Wj3C7c">Manfred<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>