On Wed, Feb 5, 2014 at 8:25 AM, aboobacker sidheeque mk <aboobackervyd
@gmail.com> wrote:

> What about a qt app , so that we can maintain same code base for
> android ,iphone and blackberry
>

We already have a "native" (Java based) app for Android, and I guess that
it could be easily adapted for Blackberry 10. From my point of view this
approach makes more sense for these platforms (I can think of performance
as the first reason, for instance). So only iOS (and Windows Phone) would
be missing, and I think that going for a native app for them would make
more sense. It's just my opinion, anyway.



> Ps: qt for ios still development stage
>

That makes it even worse!




>
> On 2/5/14, Per Tunedal <[email protected]> wrote:
> > Hi,
> > what about going a bit commercial? Many companies use a dual licence
> > model: GPL + proprietary (e.g. the small Swedish company that made MySQL
> > started that way).
> >
> > Would it do any harm if the project offered an iOS port for $10? And
> > used the income for the development of Apertium?
> > Unfortunately, that would not fit into GSOC though. We would have to
> > finance it some other way. GOTEO? http://goteo.org/ Or some other crowd
> > funding?
> >
> > Most Ipad/Iphone users are the opposite of hackers: they are happy with
> > the limitations of the system. An Apertium-app for Ipad must be
> > accessible in the App Store to reach the audience.
> >
> > Yours,
> > Per Tunedal
> >
> > On Wed, Feb 5, 2014, at 0:08, Jimmy O'Regan wrote:
> > --snip--
> >>
> >> First of all, the basic problem with an iOS port is that it would not
> >> be distributable through the App Store (its terms are
> >> GPL-incompatible). This is the reason why an iOS port was not pursued
> >> in the past, and nothing has changed: see
> >>
> http://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement
> >>
> > --snip--
> >> --
> >> <Sefam> Are any of the mentors around?
> >> <jimregan> yes, they're the ones trolling you
> >>
> >>
> ------------------------------------------------------------------------------
> >> Managing the Performance of Cloud-Based Applications
> >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> >> Read the Whitepaper.
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> >> _______________________________________________
> >> Apertium-stuff mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> >
> >
> ------------------------------------------------------------------------------
> > Managing the Performance of Cloud-Based Applications
> > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> > Read the Whitepaper.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Apertium-stuff mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> >
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> Apertium-stuff mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to