<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Barry,<br>
I wanted to you to know that I do appreciate the feedback, as you are
coming at it from a different approach and I never thought to be
clicking all around the screen while waiting. I do agree this needs to
be addressed. I just didn't want to appear to be attacking you when
replying to your comments and I hope you don't take it that way, I just
wanted to be firm on my opinion about this issue. <br>
--<br>
In Christ,<br>
David<br>
<br>
David Trotz wrote:
<blockquote cite="mid:E1J3Dn6-0006pz-9i@crosswire.org" type="cite">
<pre wrap="">Barry,
Let's remember I said 'experimental' for a reason. The current build as it stands is alpha level software, its not even at a beta level. As I stated earlier there are some kinks that need some smoothing out. I am confident that as I move forward I can address these issues, one by one. This is an initial implementation, not the end result the point of this current version is to prove one point, and only one point, will this speed up initial rendering times. Answer in my opinion Yes. Now I plan to work out the kinks. I feel strongly that long waits are unacceptable for a program that only displays text, and I am further encouraged in this opinion because other bible software on this platform and even Palm do not lag nearly as much (if at all) as ours does.
I like DM Smith's timestamping idea and will look into that. I am not so hot on the busy cursor unless its absolutely essential, and I can see times when is such as when searching but for dispaying text, I would rather not. Lord willing we can do this, its going to take several iterations but I feel this is priority #1 for this reason, *it's slow* adding new features will make it slower and harder to optimize later on down the line. Let's get this right now.
--
In Christ,
David
-----Original Message-----
From: Barry Drake <a class="moz-txt-link-rfc2396E" href="mailto:b.drake@ntlworld.com"><b.drake@ntlworld.com></a>
Sent: Friday, December 14, 2007 8:18 AM
To: SWORD Developers' Collaboration Forum <a class="moz-txt-link-rfc2396E" href="mailto:sword-devel@crosswire.org"><sword-devel@crosswire.org></a>
Subject: Re: [sword-devel] SwordReader - Experimental Double Buffering added.]
Hi there ..........
DM Smith wrote:
</pre>
<blockquote type="cite">
<pre wrap="">In another app, we put up a busy cursor and blocked input at the start
of every event and restored the cursor and user input at it's end.
</pre>
</blockquote>
<pre wrap=""><!---->Thanks for that - sounds good to me. I think I'd prefer that approach
to any other, as it lets the user know to wait! And it is a long wait
.... Do you think that's the answer, David?
God bless,
Barry
-- From Barry Drake (The Revd) minister of the Netherfield United Reformed church, Nottingham see <a class="moz-txt-link-freetext" href="http://www.jesusinnetherfield.org.uk">http://www.jesusinnetherfield.org.uk</a> for our church homepages).
Replies - <a class="moz-txt-link-abbreviated" href="mailto:b.drake@ntlworld.com">b.drake@ntlworld.com</a>
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
</body>
</html>