Daniel Blake wrote:
> David Trotz wrote:
>
>> That would be easy enough to do. I currently have it stop just beyond
>> the end of the last line in a chapter, so that you cannot scroll and
>> scroll beyond that point only to get confused when trying to scroll back.
>>
>> Anyone else have an op
Thank you for the quick change.
David Trotz wrote:
>> I would have the feedback occur on stylus down and the next selection
>> screen on stylus up. Then if I tapped the wrong choice I could slide
>> the stylus over to the correct choice and then release to obtain the
>> correct choice.
>>
>
David Trotz wrote:
> That would be easy enough to do. I currently have it stop just beyond
> the end of the last line in a chapter, so that you cannot scroll and
> scroll beyond that point only to get confused when trying to scroll back.
>
> Anyone else have an opinion about this? Scroll till the
I would have the feedback occur on stylus down and the next selection
screen on stylus up. Then if I tapped the wrong choice I could slide
the stylus over to the correct choice and then release to obtain the
correct choice.
Done, and in the current SVN. Thanks for the suggestion.
--
David
David Trotz wrote:
> SonWon wrote:
>
>> Agreed. Also I recommend defaulting to the less complex menu for all new
>> users.
>>
>>
> I think we are all pretty much in agreement on this now.
>
>> I noticed today that I can flick scroll past the last verse. I think
>> flick scroll sho
SonWon wrote:
> Agreed. Also I recommend defaulting to the less complex menu for all new
> users.
>
I think we are all pretty much in agreement on this now.
> I noticed today that I can flick scroll past the last verse. I think
> flick scroll should stop at the last verse so the last verse is
SwordReader to the 1.0.0 level.
>
> Al
>
>
>
> *From:* David Trotz [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, July 10, 2008 9:45 PM
> *To:* SWORD Developers' Collaboration Forum
> *Subject:* Re: [sword-devel] SwordReader PocketPC and Smart
orked out and get SwordReader to the 1.0.0 level.
Al
_
From: David Trotz [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2008 9:45 PM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] SwordReader PocketPC and SmartPhone CAB files.
SonWon wrote:
B
Sorry if I stepped on any toes, was not my plan just expressing my thoughts.
No you didn't step on any toes. :-)
So this is what I propose (actually you already made a mention of
this): Let's make the two menu system default out of the box, which
will be our official menu where every singl
David Trotz wrote:
> SonWon wrote:
>> Barry Drake wrote:
>>
>>> Hi David .
>>>
>>> David Trotz wrote:
>>>
>>>
Certainly lets discuss this further. I would like to hear others opinions
as well; including Albert Sites and Barry Drake.
If we diverge to two separate
SonWon wrote:
Barry Drake wrote:
Hi David .
David Trotz wrote:
Certainly lets discuss this further. I would like to hear others opinions as
well; including Albert Sites and Barry Drake.
If we diverge to two separate menus we need to implement some way to keep them
in sync,
Barry Drake wrote:
> Hi David .
>
> David Trotz wrote:
>
>> Certainly lets discuss this further. I would like to hear others opinions as
>> well; including Albert Sites and Barry Drake.
>> If we diverge to two separate menus we need to implement some way to keep
>> them in sync, so tha
SonWon wrote:
> Barry Drake wrote:
>
>> snip...
>> Big big wish we must implement a dual parallel text screen so two
>> versions or a version and a commentary can be viewed at one time. That
>> was the original intention (using the extra menuitem that was present in
>> the old 'gui' as
Barry Drake wrote:
> snip...
> Big big wish we must implement a dual parallel text screen so two
> versions or a version and a commentary can be viewed at one time. That
> was the original intention (using the extra menuitem that was present in
> the old 'gui' as distinct from 'simplegu
Hi David ..
David Trotz wrote:
> It is my intention to have the ability to view two texts side by side. So
> don't worry its coming, I just really want to focus on stablization and
> optimization once I get all the original functionality back in place, which
> includes the hyperlinks.
Trotz
-Original Message-
From: Barry Drake <[EMAIL PROTECTED]>
Sent: Thursday, July 10, 2008 1:45 AM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] SwordReader PocketPC and SmartPhone CAB files.
Hi David .
David Trotz wrote:
> Certainly lets discuss this fu
Hi David .
David Trotz wrote:
> Certainly lets discuss this further. I would like to hear others opinions as
> well; including Albert Sites and Barry Drake.
> If we diverge to two separate menus we need to implement some way to keep
> them in sync, so that when a smartphone developer add
lity over appearance, within reason of course. :)
I'll shut up now, until others have a word.
> -
> In Christ,
> David Trotz
>
>
> -Original Message-
> From: SonWon <[EMAIL PROTECTED]>
> Sent: Wednesday, July 09, 2008 3:52 PM
> To: SWORD Developers
<[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2008 3:52 PM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] SwordReader PocketPC and SmartPhone CAB files.
David Trotz wrote:
> snip...
>> The gui looks real clean. I would prefer the navigate features to be
David Trotz wrote:
> snip...
>> The gui looks real clean. I would prefer the navigate features to be
>> single tap access instead of having to tap into a menu. Is there a
>> reason behind the current menu system, like M$ usability guidelines?
>>
>>
> The menu was driven by the Smartphon
On Jul 8, 2008, at 9:46 AM, Ben Morgan wrote:
> There are two things to note here:
> a) the ESV is a compressed module (uses the zText driver).
> The zText driver is quite a bit slower than the rawtext one (around
> 20-30x slower!)
> Here are the times taken to getRawEntry for a compressed and
That was for the whole of the ESV.
Machine specs were something like:
1.67GHz processor with 490MB RAM under WinXP.
Its a few years old.
This was done from python.
God Bless,
Ben
---
The Lord is not slow to f
On Jul 7, 2008, at 11:58 PM, Daniel Owens wrote:
Here is the wiki page:
http://www.crosswire.org/wiki/index.php/Frontends:SWORDReader
It's pretty bare right now. I would be happy to add more than just a
wish list such as features, screenshots, etc., but I thought that
might be a place to
Thank you!
Daniel Owens wrote:
> Here is the wiki page:
> http://www.crosswire.org/wiki/index.php/Frontends:SWORDReader
>
> It's pretty bare right now. I would be happy to add more than just a
> wish list such as features, screenshots, etc., but I thought that
> might be a place to list support
Ben,
For reference what verses did you use for this example, and what were
the machine specs?
David
Ben Morgan wrote:
> Hi,
>
> There are two things to note here:
> a) the ESV is a compressed module (uses the zText driver).
> The zText driver is quite a bit slower than the rawtext one (around
> 20
Hi,
There are two things to note here:
a) the ESV is a compressed module (uses the zText driver).
The zText driver is quite a bit slower than the rawtext one (around 20-30x
slower!)
Here are the times taken to getRawEntry for a compressed and uncompressed
ESV:
uncompressed: 1.89 seconds (this is a
ssage -
From: Daniel Owens
To: SWORD Developers' Collaboration Forum
Sent: Monday, July 07, 2008 11:58 PM
Subject: Re: [sword-devel] SwordReader PocketPC and SmartPhone CAB files.
Here is the wiki page:
http://www.crosswire.org/wiki/index.php/Frontends:SWORDReader
It's pr
Great, thanks. I will look forward to seeing how things develop.
Daniel
David Trotz wrote:
Daniel Owens wrote:
David,
I tested the cab file on my HP iPAQ hx2410, and it integrates nicely
with WM5. I particularly like the flick and spin (not sure what to
call it) navigation of
Daniel Owens wrote:
> David,
>
> I tested the cab file on my HP iPAQ hx2410, and it integrates nicely
> with WM5. I particularly like the flick and spin (not sure what to
> call it) navigation of the page. My friend with his smartphone skinned
> as an iPhone will be excited to see that. I didn't
John
Thanks for this. The code to handle this exists in the source code now,
and worked in 0.80 but is broken at the moment.
--
David
SonWon wrote:
> David,
>
> Not sure if this is useful since it is pure Win32.
>
> Try this out, call in WinMain():
>
> globals:
> TCHAR g_szClassName[11] = TEXT("
Here is the wiki page:
http://www.crosswire.org/wiki/index.php/Frontends:SWORDReader
It's pretty bare right now. I would be happy to add more than just a
wish list such as features, screenshots, etc., but I thought that might
be a place to list supported features and features desired by users.
John,
> Thank you very much for the CAB. I can see many changes now from the
> last time I looked at the SwordReader. Great job on the HTML window,
> single taps work! :) Can it tell a verse number from Strong's numbers
> or other numbers?
>
It can tell a hyperlink (strongs or otherwise)
All great ideas.
Daniel Owens wrote:
> David,
>
> I tested the cab file on my HP iPAQ hx2410, and it integrates nicely
> with WM5. I particularly like the flick and spin (not sure what to
> call it) navigation of the page. My friend with his smartphone skinned
> as an iPhone will be excited to
David,
Not sure if this is useful since it is pure Win32.
Try this out, call in WinMain():
globals:
TCHAR g_szClassName[11] = TEXT("App name here");// Main window class
name
TCHAR g_szTitle[11] = TEXT("Window name here");// Main window name
/
David,
I tested the cab file on my HP iPAQ hx2410, and it integrates nicely
with WM5. I particularly like the flick and spin (not sure what to call
it) navigation of the page. My friend with his smartphone skinned as an
iPhone will be excited to see that. I didn't notice any problems that
Barr
David,
Thank you very much for the CAB. I can see many changes now from the
last time I looked at the SwordReader. Great job on the HTML window,
single taps work! :) Can it tell a verse number from Strong's numbers
or other numbers?
The gui looks real clean. I would prefer the navigate fe
> Another thing to sort out. If I exit SwordReader using the exit
> menuitem, it's OK. If I exit using the close button, as you know,
> Windows Mobile leaves the program running in the background. When I try
> to re-start SwordReader, another instance opens, and won't run properly
> because
David Trotz wrote:
> Troy,
>
>> You of all people should know this... :) SWORD stores all the tags
>> inline in the text. When you start turning things OFF is when all the
>> filters have to do work to remove things. If everything is left on,
>> then the text is just handed back as it wa
Hi Troy
This message reached my e-mail client showing the date 08/07/2008
just seems a bit wierd!
God bless,
Barry.
Troy A. Griffitts wrote:
> Just a note regarding the comment that the SWORD engine take > 6 seconds
> to render psalm119...
>
> If this is the case there is a
Hi David ...
David Trotz wrote:
> I have assembled a couple of CAB files for the Windows Mobile platform
Another thing to sort out. If I exit SwordReader using the exit
menuitem, it's OK. If I exit using the close button, as you know,
Windows Mobile leaves the program running in the back
On Jul 7, 2008, at 1:41 PM, David Trotz wrote:
> Troy,
>>
>> You of all people should know this... :) SWORD stores all the tags
>> inline in the text. When you start turning things OFF is when all
>> the
>> filters have to do work to remove things. If everything is left on,
>> then the text
Hi David ...
David Trotz wrote:
> I have assembled a couple of CAB files for the Windows Mobile platform
More testing: The links to footnotes, strongs refs. etc. no longer
produce popups. They did in the last version I built. I haven't looked
at the code yet; I assume this is work in pro
Troy,
>
> You of all people should know this... :) SWORD stores all the tags
> inline in the text. When you start turning things OFF is when all the
> filters have to do work to remove things. If everything is left on,
> then the text is just handed back as it was stored. I'm still not
> co
David,
You of all people should know this... :) SWORD stores all the tags
inline in the text. When you start turning things OFF is when all the
filters have to do work to remove things. If everything is left on,
then the text is just handed back as it was stored. I'm still not
convinced. :
Troy,
> Just a note regarding the comment that the SWORD engine take > 6 seconds
> to render psalm119...
>
> If this is the case there is a bug somewhere.
>
Perhaps there is a bug, because...
> It usually takes < 6 seconds to render an entire Bible to a file on a
> low end PC, which I'm guessi
Just a note regarding the comment that the SWORD engine take > 6 seconds
to render psalm119...
If this is the case there is a bug somewhere.
It usually takes < 6 seconds to render an entire Bible to a file on a
low end PC, which I'm guessing is about the same power as todays handhelds.
My gues
Hi David .
David Trotz wrote:
> I have assembled a couple of CAB files for the Windows Mobile platform
Thanks for this. Works just fine on my pocket pc (Vodaphone v1640).
I've not done all the tests yet, but no problems on most normal
operations. The tests have reminded me that searc
Guys,
I have assembled a couple of CAB files for the Windows Mobile platform
for both the PocketPC and SmartPhone.
These are alpha builds so if you are not feeling risky, then please do
not download them, I cannot guarantee that these builds won't melt your
device.
Grab them at:
Pocket PC:
http
48 matches
Mail list logo