Manfred,
You are now the proud owner of the Jira entry for MacSword. You
should be able to administer any settings for it, but feel free to ask
me for help if you need it.
DM
Manfred Bergmann wrote:
> DM.
>
> Please change the owner to me.
> Then we will see in which way we will use it.
>
>
DM.
Please change the owner to me.
Then we will see in which way we will use it.
Thx,
Manfred
Am 21.03.2008 um 14:32 schrieb DM Smith:
> Manfred,
>
> You can use the one at CrossWire.
> http://www.crosswire.org/bugs/secure/BrowseProject.jspa?id=10010
> It is not otherwise being used. I can c
That sounds quite nice actually.
But we don't have Trac.
So either we create a internal tracker in SF or use Jiira which is
also a very nice bug tracker system and I would prefer it over SF.
But switching between SF and Jiira... Not sure if practically.
Manfred
Am 21.03.2008 um 21:42 schrieb
That is one thing I like Trac for... not only does it track issues,
but it integrates with Subversion.
When you commit a changeset, you can say "closes #34" referencing a
ticket, and if set up properly, it will actually close the ticket.
Those #ticket and [changeset] bits of text link betwe
Manfred,
You can use the one at CrossWire.
http://www.crosswire.org/bugs/secure/BrowseProject.jspa?id=10010
It is not otherwise being used. I can change the project owner to you,
if you'd like.
DM
On Mar 21, 2008, at 9:04 AM, Manfred Bergmann wrote:
> Another question.
>
> I would like to cr
Another question.
I would like to create an internal tracker for tasks/issue on
development versions not for public use.
What do you think?
Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sw
On 20-Mar-08, at 10:13 AM, Manfred Bergmann wrote:
> I remember there were some locale problems. I think it is in the
> SwordManager initialization code.
> I didn't had the time and look deeply into it. But yes, there is also
> a problem for German localization. Some Umlauts in the Booknames are
>
Am 20.03.2008 um 17:57 schrieb Nathan Youngman:
>
> On 20-Mar-08, at 1:21 AM, Manfred Bergmann wrote:
>
>> The problems are probably due to many changes in the trunk lately.
>> But Hebrew??? That's strange.
>
> Strange indeed... my Mac's second language is Hebrew, but it should be
> using Englis
On 20-Mar-08, at 1:21 AM, Manfred Bergmann wrote:
> The problems are probably due to many changes in the trunk lately.
> But Hebrew??? That's strange.
Strange indeed... my Mac's second language is Hebrew, but it should be
using English, especially since Hebrew isn't my second language :-).
Am 20.03.2008 um 05:01 schrieb Nathan Youngman:
>
> On 19-Mar-08, at 2:32 PM, Manfred Bergmann wrote:
>
>> Eh, svn:external?
>
> svn:externals would be especially useful if you were working against
> the trunk of
> Sword, and/or wanted the option of committing changes back to Sword
> itself.
>
>
Thanks Troy,
The AspenSimulator1.2.sdk (iPhone) actually does have
SearchKit.framework, which is what MacSword is now using. That will be
more convenient for porting, as we can have a low-level OS X framework
that works identically for both.
- nathan
On 17-Mar-08, at 11:02 AM, Troy A. Gri
On 19-Mar-08, at 2:32 PM, Manfred Bergmann wrote:
> Eh, svn:external?
svn:externals let you reference other repositories,
when you check out one, you get the other
this is how you would do it
sword_mac_build> svn propedit svn:externals .
(not the dot for current directory)... and put in the f
Hi Nathan.
Am 19.03.2008 um 21:01 schrieb Nathan Youngman:
> On 19-Mar-08, at 12:34 AM, Manfred Bergmann wrote:
>
>> Done. trunk is now again the trunk. ;)
>
> Much, much cleaner. Now just to build sword and all that.
> I wonder if we couldn't use an svn:external to the Sword repository
> and se
Hi Manfred,
On 19-Mar-08, at 12:34 AM, Manfred Bergmann wrote:
> Done. trunk is now again the trunk. ;)
Much, much cleaner. Now just to build sword and all that.
I wonder if we couldn't use an svn:external to the Sword repository
and set it up
within Xcode so that it's Build & Go simple.
You
Hi Nathan.
Am 19.03.2008 um 02:09 schrieb Nathan Youngman:
> I suppose we could rename the trunk and then rename the branch to
> clear it up. Subversion is kinda so/so with renames, but generally it
> works okay if it's planned well.
Done. trunk is now again the trunk. ;)
> My account on sourc
Hey Manfred,
Always helps to be looking in the right place... :-)
I suppose we could rename the trunk and then rename the branch to
clear it up. Subversion is kinda so/so with renames, but generally it
works okay if it's planned well.
My account on sourceforge forwards to [EMAIL PROTECTED],
Am 17.03.2008 um 17:45 schrieb Nathan Youngman:
>
> Hi Manfred,
>
> Yay, SearchKit! Sounds like a little cleanup is needed in Subversion
> though :-)
You need to look at branches/MacSword-reorg
I did reorganize all source files in a branch some time ago and it
never made it into the trunk.
So
Just a side note, but SWORD includes a compiler option to use clucene
(c++ port of lucene). If you can get clucene compiled for the iphone
(it has compiled for me fairly straight-forward on most platforms), then
you can turn on sword support for this (usrinst.sh near the top) and
sword search
Hi Manfred,
Yay, SearchKit! Sounds like a little cleanup is needed in Subversion
though :-)
I'm not sure if SearchKit is on iPhone OS, I don't see why not, but
never know.
Regarding the networking bit:
"There may be occasions when you need to configure your application
target so that it
Guys. :)
Am 17.03.2008 um 17:06 schrieb Greg Hellings:
> Nathan,
>
> On Mon, Mar 17, 2008 at 10:46 AM, Nathan Youngman <[EMAIL PROTECTED]
> > wrote:
>>
>> Hi Sébastien,
>>
>> While the iPhone only has 128 MB of RAM for running programs, I think
>> the 4-16 GB of storage space should be fine for
Hi Nathan.
We don't use Lucene any longer (for quite a while now actually).
Instead Apple's SearchKit is used for indexing/searching.
Maybe there is time to create a Spotlight plugin in the future. But
more important things need to get done actually.
Do you know if SearchKit is available on iPho
Nathan,
On Mon, Mar 17, 2008 at 10:46 AM, Nathan Youngman <[EMAIL PROTECTED]> wrote:
>
> Hi Sébastien,
>
> While the iPhone only has 128 MB of RAM for running programs, I think
> the 4-16 GB of storage space should be fine for having multiple Bibles.
> Though for simplicity of the interface, i
Hi Manfred,
Nice to meet you. :-)
Your wrapper will go a long way towards supporting both Tiger and the
iPhone SDK, I'm sure. From peering at the source code, I noticed the
Java
version of Lucene being used, which won't port to the iPhone either.
Sword uses OSIS and other XML formats internall
Hi Sébastien,
While the iPhone only has 128 MB of RAM for running programs, I think
the 4-16 GB of storage space should be fine for having multiple Bibles.
Though for simplicity of the interface, it might even be a good idea
to scale back to a single text.
As far as other languages, it may m
Hi Nathan.
Good to hear from you.
Your name appears on many of the source files in MacSword. :)
Finally I pulled out all the Objective-C 2.0 stuff of the Sword
wrapper. This way it is more widely useable.
Also I put everything in a framework so there is only one codebase and
it can be used on
On Sun, Mar 16, 2008 at 07:14:09PM -0700, Nathan Youngman wrote:
> The iPhone SDK does sandbox you into a directory for your application,
> but you could use the networking layer to retrieve and install Sword
> modules. Perhaps another possibility would be to just preload it with
> a few... I
Hi,
Thought I'd chime in on the conversation between Manfred and Greg on
MacSword and the iPhone SDK.
Glad to see MacSword is alive and kicking. The Eloquent wrapper sounds
like a good step, though the iPhone SDK doesn't include garbage
collection (pretty much all the other Objective-C 2.0
Hi Greg.
Am 11.03.2008 um 21:42 schrieb Greg Hellings:
> Manfred,
>
> Thanks, that clears up quite a bit of how it works. More below...
>
> On Tue, Mar 11, 2008 at 3:19 PM, Manfred Bergmann
> <[EMAIL PROTECTED]> wrote:
>> Hi Greg.
>>
>>
>> Am 11.03.2008 um 20:52 schrieb Greg Hellings:
>>
>>
>
On Tue, Mar 11, 2008 at 4:29 PM, Manfred Bergmann <[EMAIL PROTECTED]> wrote:
> Because I was curious about Objective-C 2.0 which has a couple of
> enhancements (like properties and gargabe collector) and Eloquent is
> completely using it (module installer and Sword backend).
> If I backport the mod
Because I was curious about Objective-C 2.0 which has a couple of
enhancements (like properties and gargabe collector) and Eloquent is
completely using it (module installer and Sword backend).
If I backport the module installer and the refactored backend to
MacSword, it will need the Objectiv
I agree.
--
David
DM Smith wrote:
> I think this is a great plan.
>
> On Mar 11, 2008, at 5:46 PM, Manfred Bergmann wrote:
>
>
>> Hi DM.
>>
>> Mac Users should be used to that all of a sudden some software support
>> is just canceled.
>> Just kidding. :)
>> But still, I think they are used to s
Troy.
Thanks for your comments.
I will work on an official bundle right away. Which are the default
modules that should be included?
Of course it is necessary to support older systems.
We have support back to Mac OSX Jaguar (10.2) with MacSword 1.2.1.
This is fine. We will keep this and at the
I think this is a great plan.
On Mar 11, 2008, at 5:46 PM, Manfred Bergmann wrote:
> Hi DM.
>
> Mac Users should be used to that all of a sudden some software support
> is just canceled.
> Just kidding. :)
> But still, I think they are used to such things more than Windows or
> Linux or even Java
Hi DM.
Mac Users should be used to that all of a sudden some software support
is just canceled.
Just kidding. :)
But still, I think they are used to such things more than Windows or
Linux or even Java users.
Apple sometimes is very restrictive and makes hard cuts themselfes.
But you are right
DM,
On Tue, Mar 11, 2008 at 3:57 PM, DM Smith <[EMAIL PROTECTED]> wrote:
> Manfred Bergmann wrote:
> > it would be a Leopard only
> > application.
> > IIRC the majority of users that had questions about MacSword actually
> > were using Leopard.
> >
>
> We have thought about which OSes we sho
Manfred Bergmann wrote:
> it would be a Leopard only
> application.
> IIRC the majority of users that had questions about MacSword actually
> were using Leopard.
>
We have thought about which OSes we should support for BibleDesktop. The
conclusion was to support at least the current and th
Manfred,
Thanks, that clears up quite a bit of how it works. More below...
On Tue, Mar 11, 2008 at 3:19 PM, Manfred Bergmann <[EMAIL PROTECTED]> wrote:
> Hi Greg.
>
>
> Am 11.03.2008 um 20:52 schrieb Greg Hellings:
>
>
> > I've been starting to tackle the iPhone/iPod Touch question this past
>
On 11/03/2008, Manfred Bergmann <[EMAIL PROTECTED]> wrote:
> My thinking was that until something new is there I would branch
> MacSword and backport the backend and the module installer into
> MacSword. The UI would stay the same and it would be a Leopard only
> application.
> IIRC the major
Curious: Why Leopard only? I am currently running Tiger and won't be
upgrading for a while and I suspect many are in my shoes as well. Is
there some feature of Leopard you are targeting? I currently use
MacSword (when I am on my mac) and really enjoy it. :-)
--
David
Hi Greg.
Am 11.03.2008 um 20:52 schrieb Greg Hellings:
> I've been starting to tackle the iPhone/iPod Touch question this past
> week, and it doesn't look like it would be terribly difficult. The
> most complicated and tedious portion of the project is getting Sword
> to compile in XCode in a m
I've been starting to tackle the iPhone/iPod Touch question this past
week, and it doesn't look like it would be terribly difficult. The
most complicated and tedious portion of the project is getting Sword
to compile in XCode in a manner which would allow it to build for an
iPhone app. I am not c
I for one am STOKED about an iPhone/iPod Touch Sword app! :)
I'm okay with Leopard-only for the time being, particularly as some of
the main apps I'm using these days are Leopard-only...
Thanks!
Jon Brisbin
http://jbrisbin.com
On Mar 11, 2008, at 12:37 PM, Manfred Bergmann wrote:
> Hi.
>
>
Dear Manfred,
I think your ideas are exciting. My only thoughts (which you've likely
already considered) are that it would be nice to package an official
bundle of the beta at sourceforge. This would allow pre-Leopard users
to have something usable with our latest modules. It might be nice t
Hi.
Although MacSword is quite old and it would be more than time for
something new I found that it will still take a good amount of time
until something usable is there that can replace MacSword.
I'm the only one developing in this area ATM and was quite busy with
my daily work the last mon
44 matches
Mail list logo
