Re: [sword-devel] [Wiki Frontend comparison] Proximity searches

2009-03-01 Thread Ben Morgan
On 01/03/2009, Peter von Kaehne ref...@gmx.net wrote: It appears that all clucene/lucene capable frontends can do proximity searches. BpBible exposes this via its GUI, others rely on the clucene/lucene syntax. Q: Is there anything particular about bpbible's proximity searches or do I simply

Re: [sword-devel] frontend comparison

2009-03-01 Thread Ben Morgan
On 01/03/2009, Peter von Kaehne ref...@gmx.net wrote: Chris Little wrote: Karl Kleinpaste wrote: Manfred Bergmann bergman...@web.de writes: What is meant by Ancillary texts and Verse Lists? Many modules, both Bibles and commentaries, have additional introductory material at the

[sword-devel] Passage lists as user editable modules (was Re: Wiki front end comparison - a intermediate summary)

2009-03-01 Thread Jonathan Morgan
On Sun, Mar 1, 2009 at 1:39 PM, Peter von Kaehne ref...@gmx.net wrote: I have worked now several hours on the wiki comparison page. ... d) Bookmarks/tags/lists - all these appear essentially similar as a concept, but with some drastic differences in terms of access, usability and sub

Re: [sword-devel] frontend comparison

2009-03-01 Thread Peter von Kaehne
Ben Morgan wrote: I don't think book level introductions are usually particularly important - definitely not a serious bug. I think this is a decision for the module maker and not for the tool maker. As long as the sword engine supports a feature, module makers will make use of it - if they

Re: [sword-devel] Wiki front end comparison - a intermediate summary

2009-03-01 Thread Brian Fernandes
Peter, Truly a great effort and a good list of features for frontend authors to refer to and improve. I want to edit the FireBible rows a bit, but would like to make a few clarifications first; I will wait for your response before editing the tables or you can go ahead and edit it yourself.

Re: [sword-devel] Wiki front end comparison - a intermediate summary

2009-03-01 Thread Jonathan Morgan
On Sun, Mar 1, 2009 at 10:39 PM, Brian Fernandes infernalprot...@gmail.com wrote: Peter, Truly a great effort and a good list of features for frontend authors to refer to and improve. I want to edit the FireBible rows a bit, but would like to make a few clarifications first; I will wait for

Re: [sword-devel] Wiki front end comparison

2009-03-01 Thread Barry Drake
Hi there . I've only just had chance to take a proper look at the Wiki page. It seems good as far as it goes, but I'm very concerned about the things it doesn't compare. I know I keep going on about BibleCS and NET, but that is an important issue to me. Load NET and look at Gen 1:26.

Re: [sword-devel] [Wiki Frontend comparison] Proximity searches

2009-03-01 Thread DM Smith
On Mar 1, 2009, at 3:33 AM, Ben Morgan wrote: On 01/03/2009, Peter von Kaehne ref...@gmx.net wrote: It appears that all clucene/lucene capable frontends can do proximity searches. BpBible exposes this via its GUI, others rely on the clucene/lucene syntax. Q: Is there anything particular

Re: [sword-devel] Wiki front end comparison - a intermediate summary

2009-03-01 Thread DM Smith
Peter, (and others) A couple of thoughts regarding this wiki. First, I think it is going very well. Kudos to all that have helped. I can see a lot of effort has gone into this! I think it would be good to have an explanation of the column headings under each table. Many of the headings are

Re: [sword-devel] frontend comparison

2009-03-01 Thread Dan Blake
Eeli mentioned using graphics for some of the items to conserve space. Here are very small graphics for supported operating systems. I'm not sure if they will work good enough, but here they are. Sorry about attaching them to the message but I didn't have a place to host them right now.

Re: [sword-devel] frontend comparison

2009-03-01 Thread Brian J. Dumont
Ben Morgan wrote: I don't think book level introductions are usually particularly important - definitely not a serious bug. Chapter level ones may be important. They are usually suplementary material which isn't all that important. If the user gets it, fine. If they don't, they are unlikely

Re: [sword-devel] Wiki front end comparison

2009-03-01 Thread Peter von Kaehne
Barry Drake wrote: Hi there . I've only just had chance to take a proper look at the Wiki page. It seems good as far as it goes, but I'm very concerned about the things it doesn't compare. why are you concerned? Fix it please. The bulk of the table was produced by myself last night in

Re: [sword-devel] Wiki front end comparison - a intermediate summary

2009-03-01 Thread Peter von Kaehne
DM Smith wrote: Peter, (and others) A couple of thoughts regarding this wiki. First, I think it is going very well. Kudos to all that have helped. I can see a lot of effort has gone into this! Thanks I think it would be good to have an explanation of the column headings under each

Re: [sword-devel] frontend comparison

2009-03-01 Thread Peter von Kaehne
Dan Blake wrote: Eeli mentioned using graphics for some of the items to conserve space. Here are very small graphics for supported operating systems. Thanks Dan! You know what I really would like to have is a minimalistic graphic for yes/no/partial or some such. Peter

Re: [sword-devel] Wiki front end comparison - a intermediate summary

2009-03-01 Thread Peter von Kaehne
Thanks Brian, Brian Fernandes wrote: Peter, Truly a great effort and a good list of features for frontend authors to refer to and improve. It started as a way for users to compare, but I think ultimatrely it will be much more useful to developers etc. I want to edit the FireBible rows

Re: [sword-devel] frontend comparison

2009-03-01 Thread Daniel Owens
Ben, I think the module developer should decide on this. As a module developer I found it frustrating that only two front-ends, both of them compiled only for Linux at the time, supported book level introductions. When one front-end doesn't support a well-discussed feature it is hard to know

Re: [sword-devel] frontend comparison

2009-03-01 Thread Daniel Owens
Ben, I think the module developer should decide on this. As a module developer I found it frustrating that only two front-ends, both of them compiled only for Linux at the time, supported book level introductions. When one front-end doesn't support a well-discussed feature it is hard to know