Lucene indexing and search is pretty much the same. AFAICT, it works for Bibles
and commentaries. It would be fairly easy to extend it for other types of
modules. Essentially, in the Lucene index it creates one Document per key (aka
reference) and stores the key in that document for retrieval.
right I just saw allot of info flying by about qt and guessed.
So what features are being added to the backend
All my experience these days is with python but since I use pyqt i'm fairly
familiar with qt. Just not the c++ version.
All these years I for some reason jsut could not get a simple ide
Hi Brook,
The SWORD in focus for a new release is the "back-end", not "The SWORD
Project for Windows".
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/SWORD-1-7-0RC2-tp4652963p4653033.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
__
Sorry to tack onto this thread but I was kind of curious what all does the
new sword bring?
I mean I'm looking at user side functionality.
Also I notice allot from the mailing list about clucene and in the past I
know it was kind of I had to use bibletime or xiphos to search non bible
modules. Ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think we are relatively safe to assume that these are at least of
type long (or unsigned long) and at least 32 bits wide. I doubt Sword
will be ported to 16- or 8-bit architectures.
God bless!
Jaak
On 12.08.2013 12:44, Troy A. Griffitts wrote:
> So
Sorry, one more for gcc:
http://gcc.gnu.org/onlinedocs/cpp/If.html#If
On 08/12/2013 11:42 AM, Troy A. Griffitts wrote:
On 08/12/2013 10:46 AM, Jaak Ristioja wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2013 10:34, Troy A. Griffitts wrote:
OK, I've put together a scheme which
On 08/12/2013 10:46 AM, Jaak Ristioja wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2013 10:34, Troy A. Griffitts wrote:
OK, I've put together a scheme which moves the new version macros
into our swversion.h file. The new scheme goes out to 4 segments
as we support in the SWVer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2013 10:34, Troy A. Griffitts wrote:
> OK, I've put together a scheme which moves the new version macros
> into our swversion.h file. The new scheme goes out to 4 segments
> as we support in the SWVersion class. Here are the defines.
> Pleas
OK, I've put together a scheme which moves the new version macros into
our swversion.h file. The new scheme goes out to 4 segments as we
support in the SWVersion class. Here are the defines. Please add your
comments and ask question, but I hope these will be self-explanitory.
My only concer
Afaik cmake has a way to get this information from pkgconfig (not on windows
though).
--- Ursprüngl. Mitteilung ---
Von: Jaak Ristioja
Gesend.: 07.08.2013, 00:53
An: sword-devel@crosswire.org
Betreff: Re: [sword-devel] SWORD 1.7.0RC2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Aug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Aug 6, 2013 at 11:12 AM, Troy A. Griffitts wrote:
> My only mention of this is to show that we're not simply speaking
> of obtaining version information when discussion whether or not to
> use pkg-config.
Just to be clear, I'm not against pr
On Tue, Aug 6, 2013 at 11:12 AM, Troy A. Griffitts wrote:
> Yes, quick lookup and paste for an example, but the problem is the same
> regardless of my mention of vtable: The classes are different between the
> compiled objects and this is not a safe situation.
>
> My only mention of this is to s
Yes, quick lookup and paste for an example, but the problem is the same
regardless of my mention of vtable: The classes are different between
the compiled objects and this is not a safe situation.
My only mention of this is to show that we're not simply speaking of
obtaining version informati
On Tue, Aug 6, 2013 at 8:05 AM, Troy A. Griffitts wrote:
> For example, consider the following code:
>
> class Q_CORE_EXPORT QString
> {
> public:
> ...
> #ifndef QT_NO_REGEXP
> int indexOf(const QRegExp &, int from = 0) const;
> int lastIndexOf(const QRegExp &, int from = -1) const;
>
For example, consider the following code:
class Q_CORE_EXPORT QString
{
public:
...
#ifndef QT_NO_REGEXP
int indexOf(const QRegExp &, int from = 0) const;
int lastIndexOf(const QRegExp &, int from = -1) const;
inline QBool contains(const QRegExp &rx) const { return
QBool(indexOf(rx)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.08.2013 14:54, Troy A. Griffitts wrote:
> Remember, just because you compile and link doesn't mean you've
> successfully build your app against the exact state of the headers
> when the library was compiled and this can be dangerous.
Can you pl
Well, a few issues with this.
Currently, I don't believe best practice is to install config.h because it
defines so many general things like VERSION and PACKAGE_NAME. Image including
two of these from different packages.
I was going to add the new version define to swversion.h, but considered i
On Tue, Aug 6, 2013 at 6:29 AM, Troy A. Griffitts wrote:
> Windows frontends do not use a common packaging system to share a SWORD
> devel installation.
>
Correct, but accessing this information at build time might still be
useful. Could config.h.in be updated to include this information in
addit
Windows frontends do not use a common packaging system to share a SWORD devel
installation.
Greg Hellings wrote:
>Relying on pkgconfig is not an entirely viable solution as it is not
>feasible to use on all target platforms - most notably Windows.
>
>--Greg
>
>
>On Mon, Aug 5, 2013 at 9:07 PM, T
Relying on pkgconfig is not an entirely viable solution as it is not
feasible to use on all target platforms - most notably Windows.
--Greg
On Mon, Aug 5, 2013 at 9:07 PM, Troy A. Griffitts wrote:
> Jaak,
>
> I've include -DSWORD_NUMVERSION as a pkg-config cflag directive. I hope
> this is good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure this helps us, because we're using CMake, not qmake.
Blessings!
Jaak
On 06.08.2013 05:07, Troy A. Griffitts wrote:
> Jaak,
>
> I've include -DSWORD_NUMVERSION as a pkg-config cflag directive. I
> hope this is good enough for you. You c
Jaak,
I've include -DSWORD_NUMVERSION as a pkg-config cflag directive. I hope
this is good enough for you. You can get this defined for you by
including this in your .pro file.
CONFIG += link_pkgconfig
PKGCONFIG += sword
On 08/05/2013 10:12 PM, Jaak Ristioja wrote:
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Its not simple to port to Sword 1.7.0_rc2, because the Sword test
magic in BibleTime #includes , which is not available in
1.7. Hence compilation of that file fails. There's no way to do stuff
like:
#include
#if SWORD_VERSION >= 0x010690
#inclu
Well, It's been quiet since the release of RC2. Does this mean things
are working as expected? Could I get a few positives from frontends if
you've tried the bundle? Thank you.
Troy
On 08/03/2013 12:01 PM, Troy A. Griffitts wrote:
Thanks for all the testing and reports against RC1. Thing
No need to answer.
Chris already compiled them and posted his message at almost exactly the
same time as mine.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/SWORD-1-7-0RC2-tp4652963p4652966.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
__
Do the SWORD utilities for Windows need to be recompiled for RC2 ?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/SWORD-1-7-0RC2-tp4652963p4652965.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
swo
The win32 utilities based on SWORD 1.7.0RC2 (r2947) are at the usual
location:
http://crosswire.org/ftpmirror/pub/sword/utils/win32/
I hope that the LXX and Orthodox versification systems are now in their
final states (but am open to corrections).
--Chris
___
Thanks for all the testing and reports against RC1. Things have quieted
down, so hopefully we have all the remaining items polished off. RC2 is
available for your weekend pleasure.
http://crosswire.org/sword/alpha/alpha/sword-1.7.0RC2.tar.gz
___
sw
28 matches
Mail list logo
