[sword-devel] List Archives Search?

2008-01-15 Thread Keith Watson
I just subscribed to the list. Do the mail list archives have a search feature? I have looked and cannot find one. I would like to search before I start asking questions. Thanks, Keith Watson ___ sword-devel mailing list: sword-devel@crosswire.org ht

[sword-devel] Module Submission

2008-01-15 Thread RLRANDALLX
Hi Guys! I have sent three Daily Devotional module upgrades (DBD, Daily and SME) to the below email but I have no idea where they are in the pipeline. Could we have a list on the website or the Wiki that would list when mods were submitted, approved, rejected, tested, by whom etc. That wou

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread jonathon
Eeli wrote: > > create resources --- piracy. I'm not sure how to prevent it. [One > That is a real issue but even some commercial Bible applications have > resource sharing if I have understood correctly. I've seen most, if not all of the currently available commercial bible Study Programs a

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Eeli Kaikkonen
On Wed, 16 Jan 2008, jonathon wrote: > There is one major issue with tools that make it easy for users to > create resources --- piracy. I'm not sure how to prevent it. [One > thing that would help, would be if copyright owners were more serious > about cracking down on pirated material of thei

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Eeli Kaikkonen
On Tue, 15 Jan 2008, Karl Kleinpaste wrote: > I am thinking through these sorts of problems because I am again > considering how to integrate the idea of users authoring their own > modules, and how they could get them published in some sense, where > friends/students/the world could get at them.

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread jonathon
Karl wrote: > I believe that as long as it's difficult for Joe Random to produce and > distribute a Sword module (cf. Peter, who succeeds because he is bull-headed > enough to keep pushing), that kind of community critical mass will not come > into being. +1 I look at the number and type of

Re: [sword-devel] SwordReader Module Manager

2008-01-15 Thread David Trotz
Barry, Things have settled down around here. I am ready to try out your module manager. I am using MS Visual Studio 2005 and you are running 2008. I didn't feel up to installing another IDE since I have eVC 3 and 4 and MS VS 2005 on my computer already. I was wondering if you could send me the

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Karl Kleinpaste
I think Peter's suggestions are very good, for the most part. The lack of an "alpha" area where authors can make more or less immediate updates when problems are addressed is a serious sore point. It's why I put up a public repository of my own in the first place, where a half dozen of the 30 modu

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Troy A. Griffitts
Karl, If you'd like to contribute code to make mvnforums, linux, and our new community site all use a common passwd repository, I'd welcome it. I actually tried to port htpasswd code to java so the community site would share our svn passwd repo. My code produces what looks like an htpasswd h

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Karl Kleinpaste
"Troy A. Griffitts" <[EMAIL PROTECTED]> writes: > You can already sign up for your login id, but not much else is > testable yet. So I've got a login on Crosswire itself. And a forums login. And a JIRA login. And now this one. Perhaps some things should be managed in common. _

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Troy A. Griffitts
A quick note in regard to this thread. As Chris has mentioned, we have wanted to do this for quite some time. Work has been done toward developing a facility for people to maintain module sets. Wycliffe and others have expressed a desire to maintain their own repositories of texts and we hav

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread peter
DM Smith wrote: > On Jan 15, 2008, at 5:33 AM, Chris Little wrote: > >> peter wrote: >>> One of the things which are recurrent on the mailing list is the >>> difficulty + slowness of getting a module through the door - i.e. >>> both >>> to put it into beta and to get it from beta eventually tran

Re: [sword-devel] OLPC interest still?

2008-01-15 Thread Pierre Amadio
Hi there. I will for sure have a close look at any project involving a sword application on the olpc. I still though have no idea at all what sort of feature would take advantage of the olpc "mesh" thingy. I did try the SDK in 2007, but i must admit i got lost quite fast and was not even able to

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread DM Smith
On Jan 15, 2008, at 5:33 AM, Chris Little wrote: > peter wrote: >> One of the things which are recurrent on the mailing list is the >> difficulty + slowness of getting a module through the door - i.e. >> both >> to put it into beta and to get it from beta eventually transferred >> into >> rel

Re: [sword-devel] question on possible update to ChiUns

2008-01-15 Thread DM Smith
Chris, We have a couple of active developers at jsword-devel who are native Chinese speakers and could possibly help. I'm cross posting this to there. DM On Jan 15, 2008, at 1:36 AM, Chris Little wrote: > I suspect we could come up with a way to merge the existing featureful > ChiUns with a c

Re: [sword-devel] modules upload etc - suggestion

2008-01-15 Thread Chris Little
peter wrote: > One of the things which are recurrent on the mailing list is the > difficulty + slowness of getting a module through the door - i.e. both > to put it into beta and to get it from beta eventually transferred into > release. I don't know what you mean by 'alpha' since we have no such

[sword-devel] modules upload etc - suggestion

2008-01-15 Thread peter
One of the things which are recurrent on the mailing list is the difficulty + slowness of getting a module through the door - i.e. both to put it into beta and to get it from beta eventually transferred into release. There is also no fast way of doing corrections on released module - at least for