[sword-devel] iPhone NDA dropped

[Greg Hellings]

Manfred,

On Thu, Oct 2, 2008 at 12:26 AM, Manfred Bergmann <bergmannmd at web.de> wrote:

>
> Am 01.10.2008 um 21:17 schrieb Greg Hellings:
>
> > Manfred (and Chris),
> >
> > On Wed, Oct 1, 2008 at 1:13 PM, Manfred Bergmann <bergmannmd at web.de>
> > wrote:
> > Hi.
> >
> > Good news for anyone wanting to start something native on the iPhone:
> > http://developer.apple.com/iphone/program/
> >
> > I already have the SWORD library building against the iPhone SDK in
> > XCode (the command-line building process simply doesn't work).  I
> > can't get Eloquent to build for iPhone because of a few missing
> > Cocoa-based headers which the iPhone system doesn't have.  I suppose
> > the next step is to go back to the drawing board and learn Objective-
> > C and the iPhone SDK's basic classes.
>
> Yes, that may be.
> Which sources of Eloquent have you tried compiling? This project is
> rather old and you might want to use other backend sources.


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.


>
>
> I don't have an iPhone SDK installed but I would help porting the
> backend if needed.


So far my errors are as follows:
SwordDictionary.mm can't find Cocoa/Cocoa.h or CocoLogger/CocoLogger.h.
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
SwordManager.mm - Cocoa/Cocoa.h and CocoLogger/CocoLogger.h and the MBLOG
macros
SwordInstallSource.mm - same
SwordBook.mm - same
SwordCommentary.m - same
SwordInstallSourceController.mm - ditto
SwordModule.mm - ditto, plus "warning: 'SwordModule' may not respond to
'-textForRef:'
SwordBible.mm - same

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. ;)


>
>
> > I have a general GUI layout in mind, so hopefully things will go
> > quickly once I get the hang of the RAD tools that XCode uses, etc.
> > They look like they should be rather simple, I just have never used
> > any type of RAD/GUI designing tools other than manual placement and
> > coding of interfaces.
>
> Interface Builder is a really nice tool. Cocoa has the best
> implementation of MVC I have seen so far. Interface Builder really
> only creates the GUI and then you switch over to Xcode and do the
> Controller part.
> It is different compared to other language platforms but I like it.


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.

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?

--Greg


>
>
>
>
> Regards,
> Manfred
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20081002/cd2d7fa8/attachment.html