[sword-devel] Katana / Maemo / N900
On Thu, 2010-06-10 at 12:14 -0500, Nathan Anderson wrote: Then a group of us decided we wanted to write a QT based version and so Katana was started. It has most of the features in Rapier; but it is a lot faster and more finger friendly. ;-) I tried it out, and indeed, Katana is more finger friendly than Rapier, and Katana seems to better follow guidelines for the gui on Maemo. When opening the KJV, for example, Katana properly shows the text. It nicely fills the whole screen. WLC is the same. Aleppo too. But when opening the Ndebele Bible, a Bible produced by Bibledit from USFM files, it only displays the chapter numbers and the verse numbers. Producing this Bible was done through osis2mod. It displays fine in Xiphos. Are there any hints about how to produce a Sword module from USFM files that display properly in Katana? Perhaps there are certain settings in the .conf file that need to be set to specific values? Any help is appreciated! Teus Benschop ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Sword2Net: DumpBibleModuleContent()
Wolfgang,
On 06/12/2010 09:43 AM, Wolfgang Schultz wrote:
for (FFSwordBible-getKey(); !FFSwordBible-getKey()-Error();
FFSwordBible-getKey()-increment(1)) { }
I haven't looked at the context, so you might be ok, but be sure to
position the module to the top at loop initialization. The current
initialization clause doesn't do anything.
I use:
for ((*FFSwordBible) = TOP; !FFSwordBible-Error(); (*FFSwordBible)++) { }
You also might want to turn heading on before the loop so you get those
as well:
((VerseKey *)FFSwordBible-getKey())-Headings(true);
Hope this is useful.
Troy
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Katana / Maemo / N900
Teus, osis2mod is conservative with file permissions. Be sure the files have proper permissions before you deploy. I only mention this because I often forget to grant read access to files before deploying a module for testing and the result is only chapter/verse numbers. Troy On 06/12/2010 10:33 AM, Teus Benschop wrote: On Thu, 2010-06-10 at 12:14 -0500, Nathan Anderson wrote: Then a group of us decided we wanted to write a QT based version and so Katana was started. It has most of the features in Rapier; but it is a lot faster and more finger friendly. ;-) I tried it out, and indeed, Katana is more finger friendly than Rapier, and Katana seems to better follow guidelines for the gui on Maemo. When opening the KJV, for example, Katana properly shows the text. It nicely fills the whole screen. WLC is the same. Aleppo too. But when opening the Ndebele Bible, a Bible produced by Bibledit from USFM files, it only displays the chapter numbers and the verse numbers. Producing this Bible was done through osis2mod. It displays fine in Xiphos. Are there any hints about how to produce a Sword module from USFM files that display properly in Katana? Perhaps there are certain settings in the .conf file that need to be set to specific values? Any help is appreciated! Teus Benschop ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] HTTP install manager code
Hi all, Just wanted to report here that I've discovered a flaw in the code I submitted a while ago for having an HTTP repository. The problem is in the code to parse a directory, and the issue is that different web servers dish up their ftp folders in different ways. I coded that based on the CrossWire repos, so that the code works great for both the CrossWire and the CrossWire Beta (and the CrossWire experimental!) repos, but I have just started working on adding custom repos to PocketSword and when you add the HTTP version of the Xiphos repo, there is a crash. I'm not sure if anyone else is actually using that code atm, but if you are, please be aware of that! I'm hoping to patch it so that it fails nicely, and then I may either try to fix it or change the code so it tries to download the zip file instead (which is what Bible Desktop does, I believe?). :) FYI, the issue is how the html is dished out. On the Xiphos server, it pushes out the formatting in pre tags, whereas the CrossWire server does it using proper html formatting. Shouldn't be too hard to fix, but I've now realised that we can't really guarantee how the directory contents will be displayed by the server, so perhaps it's not a battle we should be striving to win? In some (brief) testing, I believe that accessing the CrossWire repos via HTTP is quicker than via FTP, so I am going to prefer HTTP over FTP in cases where it works. :) Thanks, ybic nic... :) Nic Carter PocketSword Developer - an iPhone Bible Study app www: http://crosswire.org/pocketsword iTunes: http://itunes.apple.com/app/Pocketsword/id341046078 Twitter: http://twitter.com/pocketsword ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Android SWORD
I have posted a new build of Bishop and libsword.so built with r4 of the NDK with debug support, so you can attach to it with ndk-gdb if necessary. I had better luck with this build connecting and downloading Bibles from remote repositories. http://crosswire.org/~scribe/bishop2.apk 06/09/2010 08:01 AM, SonWon wrote: I would be glad to provide input for the user interface. On Wed, Jun 9, 2010 at 8:28 AM, mjdenham mjden...@gmail.com mailto:mjden...@gmail.com wrote: Hi Troy, I just thought I would mention that I have also been playing around with Android. I have spent the last few weeks creating a prototype bible viewer application for Android, but I just noticed Troy's messages in this forum. I took a slightly different technical approach to you and I don't know which is better and I also came at this project with the aim of creating a mobile bible viewer I could tweak and improve rather than specifically to write an Android front end for Sword. By way of information I thought I would outline my approach and what led me to start. I have used Pocket e-Sword for many years but development has now ceased on Pocket e-Sword and it is already looking a bit old, as is WinMob that it runs on, so I started thinking what to use in the future. Although I loved using Pocket e-sword there were one or two things that I would have loved to change if I had access to the source but the source was closed. Most pocket bible apps seem to be closed source and many charge money or depend on being on-line so I began to think about writing my own. I have been writing Java code for a living since the 90's. I looked at Java ME which unfortunately is not supported by recent, popular, trend-setting phones like iPhone and Android and started going that route but there doesn't seem to be much http://stackoverflow.com/questions/1414288/j2me-vs-android-vs-iphone-vs-symbian-vs-windows-ce buzz around Java ME at the moment. I briefly thought of iPhone but refuse to learn Objective-C, buy a Mac, and bend over backwards to get the app into App Store. Then I realised that Google have built Android primarily for Java Applications and Gartner predict that by 2012 Android will outsell the iPhone so I downloaded the Android SDK and am impresed by the application framework Google have put into Android. Incidentally I went to a fascinating talk on Android by Reto Meier yesterday evening. As Android hosts Java apps so well it seemed a good idea to use java front to back so I downloaded the jSword and sword-Common projects back-end to serve the OSIS documents and started creating a Java front-end for jsword on Android so I have now been doing that for the last couple of weeks off and on. I included the jsword and common jars in my Android app and simplified the xslt template I found in bible-desktop and now have a basic bible viewer app. Troy, I am interested to see that you use jni to access a C back-end. Is that right? Does this give better performance or is there another reason. In the front end I am currently using a TextView but briefly used a WebView which has better html support. I may have to switch back to WebView. I tried to copy the PocketSword verse selection screen but failed so I am just using 3 combos for now. I haven't used Crosswire code before and it took me a while to get used to OSIS and jsword but the code looks great and I am now familiar enough with jsword to find my way around the necessary parts. Here is a screen print of the current state: http://sword-dev.350566.n4.nabble.com/file/n2248754/android-bible1.jpg For now I am still happily trying to improve on the prototype but I could switch and contribute to a central project with others. My only aim is to create a good open source bible I can tweak and that others may find useful too. Best regards Martin -- View this message in context: http://sword-dev.350566.n4.nabble.com/Android-SWORD-tp360475p2248754.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org mailto:sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Android SWORD
Martin, Great news on your success of getting JSword to build on Android. I'm sure the JSword mailing list would be interested to hear about your success! I'm not sure about the speed. I will add a primitive search box to my test app and let you know how long a complete search of the KJV (a heavily marked up Bible) takes on my G1. Troy. On 06/09/2010 05:28 AM, mjdenham wrote: Hi Troy, I just thought I would mention that I have also been playing around with Android. I have spent the last few weeks creating a prototype bible viewer application for Android, but I just noticed Troy's messages in this forum. I took a slightly different technical approach to you and I don't know which is better and I also came at this project with the aim of creating a mobile bible viewer I could tweak and improve rather than specifically to write an Android front end for Sword. By way of information I thought I would outline my approach and what led me to start. I have used Pocket e-Sword for many years but development has now ceased on Pocket e-Sword and it is already looking a bit old, as is WinMob that it runs on, so I started thinking what to use in the future. Although I loved using Pocket e-sword there were one or two things that I would have loved to change if I had access to the source but the source was closed. Most pocket bible apps seem to be closed source and many charge money or depend on being on-line so I began to think about writing my own. I have been writing Java code for a living since the 90's. I looked at Java ME which unfortunately is not supported by recent, popular, trend-setting phones like iPhone and Android and started going that route but there doesn't seem to be much http://stackoverflow.com/questions/1414288/j2me-vs-android-vs-iphone-vs-symbian-vs-windows-ce buzz around Java ME at the moment. I briefly thought of iPhone but refuse to learn Objective-C, buy a Mac, and bend over backwards to get the app into App Store. Then I realised that Google have built Android primarily for Java Applications and Gartner predict that by 2012 Android will outsell the iPhone so I downloaded the Android SDK and am impresed by the application framework Google have put into Android. Incidentally I went to a fascinating talk on Android by Reto Meier yesterday evening. As Android hosts Java apps so well it seemed a good idea to use java front to back so I downloaded the jSword and sword-Common projects back-end to serve the OSIS documents and started creating a Java front-end for jsword on Android so I have now been doing that for the last couple of weeks off and on. I included the jsword and common jars in my Android app and simplified the xslt template I found in bible-desktop and now have a basic bible viewer app. Troy, I am interested to see that you use jni to access a C back-end. Is that right? Does this give better performance or is there another reason. In the front end I am currently using a TextView but briefly used a WebView which has better html support. I may have to switch back to WebView. I tried to copy the PocketSword verse selection screen but failed so I am just using 3 combos for now. I haven't used Crosswire code before and it took me a while to get used to OSIS and jsword but the code looks great and I am now familiar enough with jsword to find my way around the necessary parts. Here is a screen print of the current state: http://sword-dev.350566.n4.nabble.com/file/n2248754/android-bible1.jpg For now I am still happily trying to improve on the prototype but I could switch and contribute to a central project with others. My only aim is to create a good open source bible I can tweak and that others may find useful too. Best regards Martin ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
