Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 53 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 13 hrs ago - more...
|
2009-10-16
, 20:17
|
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#122
|
Originally Posted by ARJWright
I just ported it -- I didn't make any "design" changes. I needed to make sure all the underlying libraries worked. :-D
Looks good. Buttons eh, but looks good. Congrats to you Nathan et al for running still with this.
I'd probably also jump in and say that doing a new(er) app in Qt would be better for the long range use of such an app. After that, making items platform specific becomes easier.
Small update; the issue I said about not being able to compile in Armel has been resolved (Way to go Nokia!) so, once I get upload rights I plan on trying to get everything up so those who have been blessed with a phone can at least use something.
Nathan.
|
|
2009-10-17
, 15:50
|
|
Posts: 111 |
Thanked: 31 times |
Joined on May 2007
|
#123
|
Hi there !
I sort of changed my mind about not going to buy a n900 (thanks to the developer discount ). So on the worst case (nothing happening related to a Sword based application for maemo 5), I will try to port the current Rapier application and push it to maemo5 repository.
Being lazy (it is supposed to be a vertue for a developer, is it not ?), i would be happy to see Nathan or anybody else pushing some more fresh and "opt"ized packages (clucene,swig,sword and the python bindings) to the repository before i try to do so.
I suggest that nothing is pushed to the devel repository before someone has a full working stack.
As Rapier currently fullfill my needs for a Bible reader, I will not add new features or rewrite something else down from scratch.
However, as soon as a Sword/C++/Qt based reader will be available, i will most probably use it (i' m lazy, but i do like proper applications after all) and try to fix some bugs i may hit.
To whoever start such a project, let us know the project garage's name, and please use the garage svn (or git) so everybody can play with the latest development branches.
I sort of changed my mind about not going to buy a n900 (thanks to the developer discount ). So on the worst case (nothing happening related to a Sword based application for maemo 5), I will try to port the current Rapier application and push it to maemo5 repository.
Being lazy (it is supposed to be a vertue for a developer, is it not ?), i would be happy to see Nathan or anybody else pushing some more fresh and "opt"ized packages (clucene,swig,sword and the python bindings) to the repository before i try to do so.
I suggest that nothing is pushed to the devel repository before someone has a full working stack.
As Rapier currently fullfill my needs for a Bible reader, I will not add new features or rewrite something else down from scratch.
However, as soon as a Sword/C++/Qt based reader will be available, i will most probably use it (i' m lazy, but i do like proper applications after all) and try to fix some bugs i may hit.
To whoever start such a project, let us know the project garage's name, and please use the garage svn (or git) so everybody can play with the latest development branches.
|
|
2009-10-18
, 00:40
|
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#124
|
Originally Posted by pamadio
Congrats on making the Dev program! The more developers the merrier. ;-)
Hi there !
I sort of changed my mind about not going to buy a n900 (thanks to the developer discount ). So on the worst case (nothing happening related to a Sword based application for maemo 5), I will try to port the current Rapier application and push it to maemo5 repository.
Being lazy (it is supposed to be a vertue for a developer, is it not ?), i would be happy to see Nathan or anybody else pushing some more fresh and "opt"ized packages (clucene,swig,sword and the python bindings) to the repository before i try to do so.
I'm stumped for the moment and might have to move back to clucene 0.9.21b rather than the clucene 0.9.23 I have installed. I've got a post into the Sword dev list on how -- and I haven't given up hope. ;-)
I suggest that nothing is pushed to the devel repository before someone has a full working stack.
To whoever start such a project, let us know the project garage's name, and please use the garage svn (or git) so everybody can play with the latest development branches.
- Katana maybe?
Nathan.
| The Following User Says Thank You to Nathan For This Useful Post: | ||
 |
|
2009-10-18
, 04:21
|
|
Posts: 861 |
Thanked: 734 times |
Joined on Jan 2008
@ Nomadic
|
#125
|
For a name, since this would be made on a Maemo tablet device, and with Qt, why not something simple like Qt-Bible or Verses.
... Katana? Uhmm, sharp, I like that too
... Katana? Uhmm, sharp, I like that too
|
|
2009-10-18
, 07:31
|
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#126
|
Ok, a small status update.
I have managed to rebuild the entire stack. It does appear that clucence .9.23 has incompatibilities. By reverting back to 0.9.21b I was able to recompile the entire stack of dependencies properly. (It appears my first version of rapier that the above screen shot came from was a version with OUT clucene, when I went back and checked the sword library it was not linked against it; so that is how I got it to compile the first time, and couldn't afterwords. LOL)
I have also fixed several bugs in the Rapier for Fremantle and everything appears to be now working properly on my sdk machine. (Search, Strongs, Modules, Switching) -- I'll have to let one you actually try it on a real device as I do not (nor do I have any idea if/when I may even get one as the retail price is outside of my current ability).
I'm going to start to push the entire stack to the repositories now that I can easily re-compile it fully. I need to check about optifing it and I hope to get this all up by sometime tomorrow or the next day to the extras-testing, for those with devices.
Nathan.
I have managed to rebuild the entire stack. It does appear that clucence .9.23 has incompatibilities. By reverting back to 0.9.21b I was able to recompile the entire stack of dependencies properly. (It appears my first version of rapier that the above screen shot came from was a version with OUT clucene, when I went back and checked the sword library it was not linked against it; so that is how I got it to compile the first time, and couldn't afterwords. LOL)
I have also fixed several bugs in the Rapier for Fremantle and everything appears to be now working properly on my sdk machine. (Search, Strongs, Modules, Switching) -- I'll have to let one you actually try it on a real device as I do not (nor do I have any idea if/when I may even get one as the retail price is outside of my current ability).
I'm going to start to push the entire stack to the repositories now that I can easily re-compile it fully. I need to check about optifing it and I hope to get this all up by sometime tomorrow or the next day to the extras-testing, for those with devices.
Nathan.
|
|
2009-10-18
, 09:15
|
|
Posts: 111 |
Thanked: 31 times |
Joined on May 2007
|
#127
|
Hi there !
Please send me by mail the patch you made to have Rapier working on Fremantle. I'll install a sdk, try it out, create a branch for diablo (just in case) and keep the trunk (where the patch will be applyed) to get a Fremantle version so a simple reader will be available while a new one is being developed.
I like katana as it reference both QT and Sword context.
Originally Posted by Nathan
I meant to push the needed library in the devel repository. According to your next post, you are planning to do that soon. Cool :-)
As in your svn; or somewhere else? I have a fully working rapier (I have one bug that I think I have the solution for today that I haven't applied yet to rapier -- but I can submit it to svn for you (and anyone else to have) so that you don't have to figure out what to fix in it.
Please send me by mail the patch you made to have Rapier working on Fremantle. I'll install a sdk, try it out, create a branch for diablo (just in case) and keep the trunk (where the patch will be applyed) to get a Fremantle version so a simple reader will be available while a new one is being developed.
Any suggestions to a name. I'm willing to start the garage project and add Hogwash to it so that we both have full access to it. But we need to choose a name. ;-D
- Katana maybe?
|
|
2009-10-18
, 10:49
|
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#128
|
Originally Posted by pamadio
I'll push the entire stack (except for Rapier) to the repositories.
Hi there !
I meant to push the needed library in the devel repository. According to your next post, you are planning to do that soon. Cool :-)
Please send me by mail the patch you made to have Rapier working on Fremantle. I'll install a sdk, try it out, create a branch for diablo (just in case) and keep the trunk (where the patch will be applyed) to get a Fremantle version so a simple reader will be available while a new one is being developed.
I also fixed a couple of "warnings" that were floating around in the app that wasn't affecting anything (besides the console output) -- I hate seeing warnings for no reason; so most those places now check for "None" before trying to work on the value.
Can you PM me with your email address and I'll email you the new rapier source file. And you can handle the pushing it to extras.
I like katana as it reference both QT and Sword context
Nathan.
|
|
2009-10-19
, 14:37
|
|
Posts: 13 |
Thanked: 0 times |
Joined on Aug 2009
@ SC; USA
|
#129
|
This may be looking too far ahead, but I am wondering if it would be worth it to partner with one of the older companies that make Bible software for other platforms. For instance, Laridian currently partners with BEIKS to offer their content to the BlackBerry platform. They also announced today that they are partnering with Bits of God Software to make their library available on the Palm Pre.
If a Qt-based Bible reader would have access to a library the size of what Laridian or Olive Tree have to offer, it would be really good. I am not sure how open source you could still keep it though if this path was chosen.
If a Qt-based Bible reader would have access to a library the size of what Laridian or Olive Tree have to offer, it would be really good. I am not sure how open source you could still keep it though if this path was chosen.
|
|
2009-10-19
, 14:44
|
|
Posts: 369 |
Thanked: 191 times |
Joined on Sep 2009
@ Virginia
|
#130
|
Originally Posted by Nathan
Wow. You're really rockin' along Nathan. Outstanding!
Sweet it appears that we have at least two for it. Hogwash you?
Nathan.
I'm a bit of a Nihon-o-phile, so "Katana" is cool with me.
 |
| Tags |
| bible, maemo 5, rapier, reference browser, religious apps, scripture reader, sword |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 18:34.
I'd probably also jump in and say that doing a new(er) app in Qt would be better for the long range use of such an app. After that, making items platform specific becomes easier.
antoinerjwright.com | Mobile Ministry Magazine