wxwidgets for mobile platform
Gour
I've decided to use wx(haskell) as the lib for developing desktop
application (the other alternative was gtk(2hs) ).
The desktop application could possible have its 'lite' companion
running on some MDI/smart-phone and I wonder if there is some mobile
platform for which one can use wxwidgets?
I know that Maemo will use Qt in next version, but I'm not sure if
there is port for Mer project?
What about Moblin?
Sincerely,
Gour
--
Gour | Hlapicina, Croatia | GPG key: F96FF5F6
----------------------------------------------------------------
Vadim Zeitlin
G> The desktop application could possible have its 'lite' companion
G> running on some MDI/smart-phone and I wonder if there is some mobile
G> platform for which one can use wxwidgets?
wxWinCE is by far the best bet. It still has its share of not implemented
features but it does work and you can use it to create useful programs (I
did back in 2006 or so).
The next platform we could support would be indeed Maemo, it used to work
more or less on my N700 and there is/are patch(es) in Trac adding support
for later Maemo version which nobody had the time to test/integrate so far
unfortunately.
And then there is a (pre-Web) Palm port but I don't know how usable (or
still relevant) is it.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/
Stefan Csomor
> G> The desktop application could possible have its 'lite' companion
> G> running on some MDI/smart-phone and I wonder if there is some mobile
> G> platform for which one can use wxwidgets?
>
> wxWinCE is by far the best bet. It still has its share of not implemented
> features but it does work and you can use it to create useful programs (I
> did back in 2006 or so).
>
> The next platform we could support would be indeed Maemo, it used to work
> more or less on my N700 and there is/are patch(es) in Trac adding support
> for later Maemo version which nobody had the time to test/integrate so far
> unfortunately.
>
> And then there is a (pre-Web) Palm port but I don't know how usable (or
> still relevant) is it.
wx is also used in some iPhone apps, but they are using native Interface
builder UI (or wxGLCanvas) for the front-end and wxiphone for the backend
Best,
Stefan
Gour
>>>>>> "Vadim" == Vadim Zeitlin <va...@wxwidgets.org> wrote:
Vadim> wxWinCE is by far the best bet. It still has its share of not
Vadim> implemented features but it does work and you can use it to
Vadim> create useful programs (I did back in 2006 or so).
I'd like to avoid that platform, nor I plan to buy device running it.
Vadim> The next platform we could support would be indeed Maemo, it
Vadim> used to work more or less on my N700 and there is/are patch(es)
Vadim> in Trac adding support for later Maemo version which nobody had
Vadim> the time to test/integrate so far unfortunately.
Hmm, that's interesting...My main concern is Maemo (stuff like N900)
vs Moblin.
Considering Maemo 6 will be Qt-based, does it mean that Maemo support
will be for the Mer project ot Maemo based on 'community support' ?
Vadim Zeitlin
G> Vadim> The next platform we could support would be indeed Maemo, it
G> Vadim> used to work more or less on my N700 and there is/are patch(es)
G> Vadim> in Trac adding support for later Maemo version which nobody had
G> Vadim> the time to test/integrate so far unfortunately.
G>
G> Hmm, that's interesting...
In fact I was wrong, the patch (http://trac.wxwidgets.org/ticket/9058)
adding support for Hildon 2 was applied to the trunk a couple of months
ago.
G> My main concern is Maemo (stuff like N900)
I don't really know much about Maemo 5 differences with the previous
versions. I originally played with wxGTK under Maemo 2 (OS2006) on my N770
and I reflashed it later to use Maemo 3 (OS2007[HE]) but never looked at it
since then.
G> vs Moblin.
And I don't know anything at all about developing for Moblin. I'd like to
see wx port to it though, this should be a fun project...
Gour
>>>>>> "Vadim" == Vadim Zeitlin <va...@wxwidgets.org> wrote:
Vadim> In fact I was wrong, the patch
Vadim> (http://trac.wxwidgets.org/ticket/9058) adding support for
Vadim> Hildon 2 was applied to the trunk a couple of months ago.
Heh, it took quite some time to be applied.
Vadim> I don't really know much about Maemo 5 differences with the
Vadim> previous versions. I originally played with wxGTK under Maemo 2
Vadim> (OS2006) on my N770 and I reflashed it later to use Maemo 3
Vadim> (OS2007[HE]) but never looked at it since then.
Afaik, Maemo won't have long lifetime since Nokia is pushing Qt for
Maemo 6 next year...
Vadim> And I don't know anything at all about developing for Moblin.
Vadim> I'd like to see wx port to it though, this should be a fun
Vadim> project...
...and that's why it might be better to have wx port for Moblin which
is getting its own toolkit called mx (replacing old nbtk) based on
Clutter.
However, in the meantime I still have lot of things to learn to learn
wx(haskell) - for now I'm reading free wxwidgets (C++) book (from the
Haskell perspective) in orde to become familiar how the library is
working.
Gour
>>>>>> "Vadim" == Vadim Zeitlin <va...@wxwidgets.org> wrote:
Vadim> And I don't know anything at all about developing for Moblin.
Vadim> I'd like to see wx port to it though, this should be a fun
Vadim> project...
I've just returned from my trip and saw announcement about merging of
Maemo & Moblin projects as MeeGoo project (http://meego.com/).
Now, I really wonder if it means that seeing wxWidgets port is more
probable than before?
Mike Musterd
On Thu, 28 Jan 2010 21:54:01 +0100
>>>>>> "Vadim" == Vadim Zeitlin <va...@wxwidgets.org> wrote:
Vadim> And I don't know anything at all about developing for Moblin.
Vadim> I'd like to see wx port to it though, this should be a fun
Vadim> project...
I've just returned from my trip and saw announcement about merging of
Maemo & Moblin projects as MeeGoo project (http://meego.com/).
Now, I really wonder if it means that seeing wxWidgets port is more
probable than before?
Gour
>>>>>> "Mike" == Mike Musterd <mike.m...@gmail.com> wrote:
Mike> Don't know. Meego (and symbian^4) will all be Qt-based. KDE
Mike> already is. Since the license relaxation of Qt, a wxQt backend
Mike> would be perfectly possible, and it could sit next to the wxGTK
Mike> backend. It would also enable wx development on Nokia devices and
Mike> Qtopia-enabled devices.
Yes, and considering the devices supposed to use Moblin...quite nice.
Mike> On the other hand, Qt is quite portable in itself, so adding the
Mike> wx layer over it seems quite redundant.
Mike> Has there ever been an effort for "wxQt"?
The last which I've found is the following thread "wxQt - The missing
port" on dev list (check
http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/110519)
It would be pitty to leave mobile devices just in hand of Qt.
Julian Smart
> On Fri, 26 Feb 2010 09:14:31 +0100
>
>
> Mike> already is. Since the license relaxation of Qt, a wxQt backend
> Mike> would be perfectly possible, and it could sit next to the wxGTK
> Mike> backend. It would also enable wx development on Nokia devices and
> Mike> Qtopia-enabled devices.
>
> Yes, and considering the devices supposed to use Moblin...quite nice.
>
> Mike> On the other hand, Qt is quite portable in itself, so adding the
> Mike> wx layer over it seems quite redundant.
> Mike> Has there ever been an effort for "wxQt"?
>
> The last which I've found is the following thread "wxQt - The missing
> port" on dev list (check
> http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/110519)
>
>
> It would be pitty to leave mobile devices just in hand of Qt.
>
Is it worth spending more time on wxGTK on MeeGo or are we going to have
the rug pulled from under us at some point? I suppose GTK+ is going to
be a second class citizen on this platform, sooner or later.
Mobile platforms are fragmenting at such a rate that it's hard to know
what to target and how, especially with WinMobile 7 being
Silverlight-only. At least we could let Qt do the heavy lifting with a
wxQt port, if wxQt doesn't end up too bloated. Since Qt will be built
into MeeGo devices perhaps it'll be no worse targetting Qt than GTK+ in
terms of space requirements.
We could propose a start at wxQt for a GSoC project. Although we try to
shy away from over-ambitious GSoC projects, I think it could be worth
the risk if we can gather some funding and enthusiasts for taking it
further. We could think of it as a big insurance policy...
Regards,
Julian
Gour
>>>>>> "Julian" == Julian Smart <jul...@anthemion.co.uk> wrote:
Julian> True. I wonder how seriously we can take the inclusion of GTK+
Julian> in MeeGo? Is it worth spending more time on wxGTK on MeeGo or
Julian> are we going to have the rug pulled from under us at some
Julian> point? I suppose GTK+ is going to be a second class citizen on
Julian> this platform, sooner or later.
I believe that it could even happen sooner than later.
Maemo 6 was already announced as Qt, with GTK+ as only 'community
supported'.
Julian> Mobile platforms are fragmenting at such a rate that it's hard
Julian> to know what to target and how, especially with WinMobile 7
Julian> being Silverlight-only.
That's true, although Intel+Nokia gives some weight to MeeGo.
Julian> We could propose a start at wxQt for a GSoC project. Although
Julian> we try to shy away from over-ambitious GSoC projects, I think
Julian> it could be worth the risk if we can gather some funding and
Julian> enthusiasts for taking it further. We could think of it as a
Julian> big insurance policy...
I wholeheartedly agree with the above and can just pray that some
knowledgeable devs become interested to launch wxQt.
With all respect to Qt, I still feel much more secure to depend on
open-source toolkit for ALL my development.
Alec Ross
<jul...@anthemion.co.uk> writes
Hmm ... IANAL, but I have just looked at the licences involved for Qt,
and the sample price quoted for a single developer, single os,
commercial licence, and blanched; and wondered what the situation might
be for someone using a wxQt for commercial development.
Alec
--
Alec Ross
Milan Babuskov
> Hmm ... IANAL, but I have just looked at the licences involved for Qt,
Qt is dual-licensed. You can use LGPL and pay nothing as long as you
adhere to LGPL rules.
--
Milan Babuskov
==================================
The easiest way to import XML, CSV
and textual files into Firebird:
http://www.guacosoft.com/xmlwizard
==================================
Alec Ross
<mil...@panonnet.net> writes
>Alec Ross wrote:
>> Hmm ... IANAL, but I have just looked at the licences involved for
>>Qt,
>
>Qt is dual-licensed. You can use LGPL and pay nothing as long as you
>adhere to LGPL rules.
>
Yes, but http://news.bbc.co.uk/1/hi/entertainment/8536899.stm
also states:
"
Qt Commercial Developer License
The Qt Commercial Developer License is the correct license to use for
the development of proprietary and/or commercial software with Qt where
you do not want to share any source code.
You must purchase a Qt Commercial Developer License from us or from one
of our authorized resellers before you start developing commercial
software. The Qt Commercial Developer License does not allow the
incorporation of code developed with the Qt GNU LGPL v. 2.1 or GNU GPL
v. 3.0 license versions into a commercial product.
"
Alec
(Intending to drop out of this thread now)
--
Alec Ross
Julian Smart
> In message <4B87F2C4...@panonnet.net>, Milan Babuskov
> <mil...@panonnet.net> writes
>> Alec Ross wrote:
>>> Hmm ... IANAL, but I have just looked at the licences involved for Qt,
>>
>> Qt is dual-licensed. You can use LGPL and pay nothing as long as you
>> adhere to LGPL rules.
>>
>
> Yes, but http://news.bbc.co.uk/1/hi/entertainment/8536899.stm
> also states:
>
> "
> Qt Commercial Developer License
>
> The Qt Commercial Developer License is the correct license to use for
> the development of proprietary and/or commercial software with Qt
> where you do not want to share any source code.
>
> You must purchase a Qt Commercial Developer License from us or from
> one of our authorized resellers before you start developing commercial
> software. The Qt Commercial Developer License does not allow the
> incorporation of code developed with the Qt GNU LGPL v. 2.1 or GNU GPL
> v. 3.0 license versions into a commercial product.
> "
and
http://qt.nokia.com/products/licensing
The table says: Can create proprietary applications? LGPL: Yes, in
accordance with the LGPL v. 2.1 terms.
So assuming the app dynamically links with the Qt libraries it looks
like commercial apps are in the clear.
Regards,
Julian
>
> Alec
> (Intending to drop out of this thread now)
--
Julian Smart, Anthemion Software Ltd.
28/5 Gillespie Crescent, Edinburgh, Midlothian, EH10 4HU
www.anthemion.co.uk | +44 (0)131 229 5306
Tools for writers: www.writerscafe.co.uk
wxWidgets RAD: www.dialogblocks.com
Blog: www.juliansmart.com
Alec Ross
Yep, sorry. It should have been your second one below.
>I assume this isn't up to date, since it appears to be contradicted by e.g.:
>
>http://arstechnica.com/open-source/news/2009/01/nokia-qt-lgpl-switch-hug
>e-win-for-cross-platform-development.ars
>
>and
>
>http://qt.nokia.com/products/licensing
>
>The table says: Can create proprietary applications? LGPL: Yes, in
>accordance with the LGPL v. 2.1 terms.
>
>So assuming the app dynamically links with the Qt libraries it looks
>like commercial apps are in the clear.
>
Well, this did seem like a contradiction to me too; but as I said, IANL.
Alec
--
Alec Ross