Greg,
I have therefore added a suitable news item to
http://www.crosswire.org/wiki/Frontends:SWORDReader#News
http://www.crosswire.org/wiki/Frontends:SWORDReader#News .
Feel free to adjust this if anything is not to your liking. I omitted the
details about DNS cache, etc.
David
--
View this
Hi Greg,
You were thinking of me in this respect, I think ? (Bisaya-Inunhan NT).
Please chat with Peter (RefDoc).
He is experimenting with AbiWord as a bridge from MS Word docs to flat XML.
See http://www.crosswire.org/wiki/File_Formats#ABW
http://www.crosswire.org/wiki/File_Formats#ABW
Da
On Wed, Dec 23, 2009 at 10:43 AM, SonWon wrote:
> I'll be moving from WM to Android next year when my contract expires om my
> current phone.
>
> I see WM dieing. Microsoft has not properly maintained the platform and
> they have hidden calls in their DLLs which programmers are not allowed to
> u
I'll be moving from WM to Android next year when my contract expires om my
current phone.
I see WM dieing. Microsoft has not properly maintained the platform and
they have hidden calls in their DLLs which programmers are not allowed to
use, unless you are a MS programmer. Really upset me when I
jonathon wrote:
Do I understand this correctly:
* There will be ongoing support for Sword Reader;
* The only ongoing development will be bug fixes;
That is how I see the situation unless someone else climbs aboard. Your
observation about other software and Windows Mobile does suggest that
the
On Tue, Dec 22, 2009 at 12:02, Barry Drake wrote:
> suspect that there is no longer any need to maintain the present release
> beyond offering support, which I can do!
Do I understand this correctly:
* There will be ongoing support for Sword Reader;
* The only ongoing development will be bug fi
Hi David ...
David Haslam wrote:
A search through the archives finds (2009-05-23) that David Trotz decided to
stop work on SwordReader development.
David did correspond with me before he left, as I was a co-developer on
the project. That is why I posted the comment. I am not active on
Barry,
A search through the archives finds (2009-05-23) that David Trotz decided to
stop work on SwordReader development.
This decision was one he made before he took up his position with OliveTree
Bible Software.
This is why, on the main wiki page, we moved the SwordReader link to under
the hea
If nobody volunteers to pick up from where David Trotz has reached, the
http://www.crosswire.org/wiki/Main_Page wiki main page should be updated to
move the SwordReader link to the section entitled, No longer actively being
developed.
Some edits to the http://crosswire.org/ CrossWire website
Hi there ...
SonWon wrote:
We are discussing the module installer for SwordReader.
Windows Mobile only supports Microsoft ActiveSinc which is Windows only.
I have already developed a working Module installer which is in SVN.
It works perfectly (using a copy of Sword Module Manager which
I'm a Linux user, so I prefer cab files and such. If you created a Windows-only
installer that installed from a Sword installation or online repositories, that
would be great for Windows users (and you should do it, in my opinion). I would
suggest that adding the option of installing zipped modu
SonWon wrote:
Please give David and I your opinion.
We are discussing the module installer for SwordReader.
Should it be windows based only?
Leaves the MAC and Linux users out in the cold.
Don't PocketPCs still "require" Windows for ActiveSync purposes? Are
there any precedents for content
I think Peter von Kaehne would be the person to ask. He it is who revamped
the CrossWire website recently.
-- David
David Trotz wrote:
>
> I am not sure who is in charge of this... but can someone snag the
> screenshot off of swordreader.org and put it in place of the one on
> crosswire.org?
As soon as I get back in town on tuesday night I will add links to
this on the website.
-David
(Sent from my mobile phone)
On 7/20/08, David Trotz <[EMAIL PROTECTED]> wrote:
> Guys,
> I have added a bug tracker to the swordreader.org website
> http://www.swordreader.org/mantis
> If you are testin
Combine the colors and gray. Have both vary, thus viewable by both groups,
happily :).
- Original Message
From: SonWon <[EMAIL PROTECTED]>
To: SWORD Developers' Collaboration Forum
Sent: Friday, July 18, 2008 1:38:49 PM
Subject: Re: [sword-devel] SwordReader Feature List
Yes I agree a tabbed display with the ability to join two tabs together
in a split screen mode, this can be later on though.
David Trotz wrote:
> Go for it, and consider using a tabbed display if possible, I foresee
> quite a few options to support on such a small screen. :-)
> In Christ,
> Davi
Go for it, and consider using a tabbed display if possible, I foresee
quite a few options to support on such a small screen. :-)
In Christ,
David Trotz
Albert L. Sites, Sr. wrote:
> Has anyone started on a configuration screen? If not, I can start on one.
>
> Al
>
>
>
jonathon wrote:
> On Sat, Jul 19, 2008 at 7:06 AM, Albert L. Sites, Sr. wrote:
>
>
>> Are there people with no vision that use Windows Mobile?
>>
>
> I thought the PDA that my housemate uses ran Windows Mobile, but I've
> just been informed that it uses Windows CE.
>
>
>> Any cell phone
On Sat, Jul 19, 2008 at 7:06 AM, Albert L. Sites, Sr. wrote:
> Are there people with no vision that use Windows Mobile?
I thought the PDA that my housemate uses ran Windows Mobile, but I've
just been informed that it uses Windows CE.
> Any cell phones they use are simple ones.
How "simple' the
I think then we will need to give the user control over the screen colors.
Trevor Jenkins wrote:
> On Sat, 19 Jul 2008, Albert L. Sites, Sr. <[EMAIL PROTECTED]> wrote:
>
>
>> In my opinion, we should simply change the color between OT and NT for now.
>> A blind person using something to direct
On Sat, 19 Jul 2008, Albert L. Sites, Sr. <[EMAIL PROTECTED]> wrote:
> In my opinion, we should simply change the color between OT and NT for now.
> A blind person using something to direct them to the book is going to be in
> the same position as the color blind person. They will need to know whe
Developers' Collaboration Forum
Subject: Re: [sword-devel] SwordReader Feature List
On Fri, Jul 18, 2008 at 3:45 PM, Eeli Kaikkonen wrote:
>> > Don't use colours colour blind people will be unable to distinguish
between :).
> Using colors is OK as long you don't use
On Fri, Jul 18, 2008 at 3:45 PM, Eeli Kaikkonen wrote:
>> > Don't use colours colour blind people will be unable to distinguish
>> > between :).
> Using colors is OK as long you don't use red/green combination.
The more significant issue is with people who have no vision. Screen
readers don't
On Fri, 18 Jul 2008, SonWon wrote:
> How about different levels of gray?
>
> Jonathan Morgan wrote:
> > Don't use colours colour blind people will be unable to distinguish between
> > :).
Using colors is OK as long you don't use red/green combination. There
are very few people who can't see colo
How about different levels of gray?
Jonathan Morgan wrote:
> On 7/18/08, Daniel Blake <[EMAIL PROTECTED]> wrote:
>
>> >>>3. Division between Old and New Testament in Book selection
>> screen,
>> >>>
>> >>>
>> >> It used to have that, but space on the screen meant it became a probl
On 7/18/08, Daniel Blake <[EMAIL PROTECTED]> wrote:
>
> >>>3. Division between Old and New Testament in Book selection
> screen,
> >>>
> >>>
> >> It used to have that, but space on the screen meant it became a problem.
> >> I don't really see a problem with the present layout, and
Great idea!
Daniel Blake wrote:
3. Division between Old and New Testament in Book selection screen,
>>> It used to have that, but space on the screen meant it became a problem.
>>> I don't really see a problem with the present layout, and everybo
>>>3. Division between Old and New Testament in Book selection screen,
>>>
>>>
>> It used to have that, but space on the screen meant it became a problem.
>> I don't really see a problem with the present layout, and everybody
>> knows where the division occurs, don't they?
Barry Drake wrote:
> Hi there
>
> SonWon wrote:
>
>>1. Switch to different Bible versions
>>
>
> It already does that. And David is already considering a two pane view
> so that two modules can be seen in parallel.
>
Scratched from the list.
>>2. Usable Sea
I went back to sword revision 2176, swordreader revision 150 and now it
compiles with EVC3. I think we should build SwordReader from the stable
libraries, sword 1.5.11 release.
Barry Drake wrote:
> Hi Troy .
>
> I'm just trying to get back into SwordReader again after quite a few
> mon
Hi there
SonWon wrote:
>1. Switch to different Bible versions
It already does that. And David is already considering a two pane view
so that two modules can be seen in parallel.
>
>2. Usable Search
This is in hand, but will probably not be available until the new so
2008 5:25 PM
> To: SWORD Developers' Collaboration Forum
> Subject: Re: [sword-devel] SwordReader - Next Chapter
>
> Albert L. Sites, Sr. wrote:
>
>> I have a Motorola Q9m and I have both a scroll wheel and navigation
>>
> buttons.
>
>> The scroll wheel
with
how small the font is. When I run SwordReader in an emulator, the font looks
bigger.
Al
-Original Message-
From: SonWon [mailto:[EMAIL PROTECTED]
Sent: Monday, July 14, 2008 5:25 PM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] SwordReader - Next Chapter
Alb
ginal Message-
> From: SonWon [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 13, 2008 8:24 AM
> To: SWORD Developers' Collaboration Forum
> Subject: Re: [sword-devel] SwordReader - Next Chapter
>
> I thought SmartPhones had a virtual mouse? Can you flick scroll with a
>
avior depending on how we address
hyperlinks.
Al
-Original Message-
From: SonWon [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 13, 2008 8:24 AM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] SwordReader - Next Chapter
I thought SmartPhones had a virtual mouse? Can
I thought SmartPhones had a virtual mouse? Can you flick scroll with a
virtual mouse? We can always add functions into the navigate menu. I
think we will need to build functions into the menus for anything we can
do with a stylus.
Daniel Blake wrote:
> I like Troy's idea for using flick scro
I think this is a good idea.
Troy A. Griffitts wrote:
> How about just flick scroll to the next chapter? A flick scroll would
> stop, as it currently does, at the bounds of a chapter, but if at the
> bounds, then another flick scroll in that same direction would take you
> to the adjoining cha
I like Troy's idea for using flick scroll also. I'm not sure what to do
for SmartPhones though..
Barry Drake wrote:
> Hi Troy .
>
> Troy A. Griffitts wrote:
>
>> How about just flick scroll to the next chapter? A flick scroll would
>> stop, as it currently does, at the bounds of a c
Hi Troy .
Troy A. Griffitts wrote:
> How about just flick scroll to the next chapter? A flick scroll would
> stop, as it currently does, at the bounds of a chapter, but if at the
> bounds, then another flick scroll in that same direction would take you
> to the adjoining chapter.
Hey
How about just flick scroll to the next chapter? A flick scroll would
stop, as it currently does, at the bounds of a chapter, but if at the
bounds, then another flick scroll in that same direction would take you
to the adjoining chapter.
___
sword-de
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
Troy,
> Yeah, somewhere before:
>
> s += (TCHAR *)m_modCurText->RenderText();
>
> add the line:
>
> m_modCurText->processEntryAttributes(false);
>
I tried this as well. When you mentioned it in #sword yesterday, the
first thing I did when I got home was try this. When it didn't improve
my resul
Yeah, somewhere before:
s += (TCHAR *)m_modCurText->RenderText();
add the line:
m_modCurText->processEntryAttributes(false);
Your call to:
SWBuf preverseHeading = m_modCurText->getEntryAttributes()...;
is off anyway, as entryAttributes aren't populated until RenderText is
called. So this pr
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
Hello all,
Even though I have a newer Windows device, I would like to see
SwordReader continue to support the older Windows Mobile devices. There
has been quite a bit of development for the Windows Mobile platform
lately and it would be to bad to see that slow down or stop completely
because
John,
> The abandonment of eVC 3.0 will, correct me if I am misunderstanding, render
> the SwordReader "broken" for the platform (Windows CE 3.0) for the SH-3
> processor. I would most diligently consider a platform of development that
> will continue support for these units, and keep this tool
T 3.0 forums
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2723319&SiteID=1)
which are asking M$ to restore the download link for the packages you
mentioned.
R,
John Gammon
- Original Message -
From: "Daniel Blake" <[EMAIL PROTECTED]>
To: &qu
mon
- Original Message -
From: "Daniel Blake" <[EMAIL PROTECTED]>
To: "SWORD Developers' Collaboration Forum"
Sent: Wednesday, July 02, 2008 10:39 PM
Subject: Re: [sword-devel] SwordReader - eVC 3.0 discontinued
>I just looked at the EULA and the only thing
I just looked at the EULA and the only thing I found was the standard
right to "Software Transfer" clause.
e.Software Transfer. You may permanently transfer all of your rights
under this EULA, provided you retain no copies, you transfer all of the
SOFTWARE PRODUCT (including all component
Barry,
> It is the appropriate thing to do. Why not consider at the same time,
> shedding the resource (rc temlate) altogether. this was only included
> to make a different menu set available to the same source files. The
> reason I suggest this is that if anyone wants to make a SmartPhone
>
Hi David .
David Trotz wrote:
> Feel free to chime in if there are any concerns or suggestions.
No concerns at all. And since I'm the only person other than yourself
that's put anything much into this project in recent years, I'm the only
one that might have taken offence. And I'm jus
Hi David .
David Trotz wrote:
> I would like to propose that it is time to shed the gui project and
> rename the simplegui project to SwordReader.
It is the appropriate thing to do. Why not consider at the same time,
shedding the resource (rc temlate) altogether. this was only includ
I found the leaks and they were in SwordReader's search code. There was
a call to VerseKey::clone which returns a pointer to a SWKey, which was
then being implicitly cast back into a VerseKey object, and the
anonymous object was lost in the transaction. This also cleared the
stdstr leak as well
Hi David .
David Trotz wrote:
> I have spent the weekend restructuring some of the SwordReader code.
Fantastic work. I've been watching your recent commits to svn. I
haven't updated and re-built as yet, but the changes look as though it's
going to be great. It's wonderful to see that
Awesome David! Looking forward to developing in 2005 and still
compiling release packages with eVC3 to support older devices! This is
the best of both worlds! Thank you!
-Troy.
David Trotz wrote:
> I am happy to report, I have successfully ported SwordReader to Visual
> Studio 200
1 - 100 of 193 matches
Mail list logo
