On Thursday, June 16, 2011 10:00:45 PM Greg Hellings wrote:
As I understood it the FSF had (at least in the past) declared that
there was an incompatibility. But IIRC, the incompatibility was
actually that Apple is always violating the GPL with its distribution.
Since the GPL states that the
On Tue, Jun 21, 2011 at 10:39 AM, David (Mailing List Addy)
davidsli...@gmx.net wrote:
On Thursday, June 16, 2011 10:00:45 PM Greg Hellings wrote:
As I understood it the FSF had (at least in the past) declared that
there was an incompatibility. But IIRC, the incompatibility was
actually that
That is in line with my understanding also. However, if the copyright
holder does not bring the case against Apple, I am doubtful anyone
else would be able to legitimately bring suit. So just don't go
screaming to or at Apple about the GPL nature of the App and you can
probably slip in
On Tuesday, June 21, 2011 10:48:24 AM Greg Hellings wrote:
So just don't go
screaming to or at Apple about the GPL nature of the App and you can
probably slip in under the radar. It may not be technically compliant
on Apple's part, but we're the ones who get to make a fuss about it,
not
On Friday, June 17, 2011 01:12:30 PM Nic Carter wrote:
Curious.
A brief reading of the GPL licence that we use shows that it says nothing
about the source being able to be compiled to work on a platform. The fact
that the src is available freely seems to satisfy it, so the fact that you
On Tuesday, June 14, 2011 11:18:57 PM Mike Hart wrote:
ottom line, BREW is not an open system, and is not compatible with the
business model Sword and GoBible operate under (free, Free, FREE.)
From what I understand App Repos like the Apple App Store and the Android
Market are also not open
My understanding of GPL (other than my general dislike for it) is that it is
fine with iOS development as it stands. Originally you weren't allowed to
share ANY code you had written for iOS, as part of the insane NDA that you
needed to agree with in order to get the iOS APIs, but that has all
As I understood it the FSF had (at least in the past) declared that
there was an incompatibility. But IIRC, the incompatibility was
actually that Apple is always violating the GPL with its distribution.
Since the GPL states that the person doing the distribution is
required to make the code and
Curious.
A brief reading of the GPL licence that we use shows that it says nothing about
the source being able to be compiled to work on a platform. The fact that the
src is available freely seems to satisfy it, so the fact that you then need to
pay apple for the privilege to run it on your
Just to follow up on BREW. Unlike J2ME apps, Each Application published via
= BREW is for a single model of phone on a single wireless carrier only. To
publish a Bible app on a single model phone on all phone carriers in the US,
That would be about 20 publications. Each publication has a
Thanks Mike, for following this through. A shame, but can not be helped.
Peter
On 15/06/11 07:18, Mike Hart wrote:
Just to follow up on BREW. Unlike J2ME apps, Each Application published via
= BREW is for a single model of phone on a single wireless carrier only. To
publish a Bible app on a
I have just started a new wiki page, already with a rudimentary sub-section
for BREW.
http://crosswire.org/wiki/Ideas_for_new_projects
Please feel free to contribute content to it.
David
--
View this message in context:
Phones with Brew generally do not have Java ME, so Go Bible applications
cannot be installed.
However, there are already solutions to porting J2ME apps to BREW. Example:
http://blue-edge.bg/brew.html
Mike, please evaluate this one, and report your findings to CrossWire.
David
--
View this
I ofund this:
http://willperone.net/Code/brewcpp.php
Original-Nachricht
Datum: Wed, 20 Apr 2011 00:56:44 -0700 (PDT)
Von: David Haslam dfh...@googlemail.com
An: sword-devel@crosswire.org
Betreff: Re: [sword-devel] BREW Development?
Phones with Brew generally do not have
I guess a separate page would have been preferable, Chris.
e.g. one headed Ideas for further projects.
with subsections for
== Ideas for front-end applications ==
=== Platforms with no front-end application ===
=== Application frameworks with no front-end application ===
PS. As for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/04/2011 08:15, David Haslam wrote:
I guess a separate page would have been preferable, Chris.
To me, it doesn't matter if those non-projects are on the same page, or
a different page. What I find useful is that it is an acknowledgement of
the
I've recently switched cellphone carriers, and as a result of various factors,
I'm now using a dumb phone that does not support Java apps, but only BREW.
(Metro is giving away a dumb phone when you buy any phone, and my wife got the
nice one.)
While investigating what BREW means, I run into
Von: Mike Hart just_mik...@yahoo.com
I'm planning to work toward this end, and would rather be involved in an
existing project than duplicating effort.
I think this is the first time that I have heard of this and I am pretty linked
in to what is happening on GoBible.
So, if you start
Some long time ago, I posted something about BREW in the Current Projects
page in our wiki, though it was subsequently deleted by an over-zealous
Osk.
Check the history of the page.
http://crosswire.org/mediawiki/index.php?title=Current_Projectsaction=history
I admit, I don't see any value to all of the space wasted to say we
don't support this platform, we don't have any content on this topic
in the wiki yet, or here's some format that is irrelevant to Sword.
It just makes it more difficult to find relevant content that actually
has been written.
20 matches
Mail list logo
