Hi!
Could you specify a time when Qt4Pas 2.2 is going to be released? I currently plan some improvements in the Debian and Ubuntu packaging of Qt4Pas and if there is a new release very soon, I would delay those changes until 2.2 is released.
Thanks!
Matthias Klumpp

Matthias Klumpp wrote

Could you specify a time when Qt4Pas 2.2 is going to be released? I currently plan some improvements in the Debian and Ubuntu packaging of Qt4Pas and if there is a new release very soon, I would delay those changes until 2.2 is released.

I am very close. I only need to clean up the maemo generator part, but that will probably not result in different code.

Can Zeljko confirm he does not need anything soon anymore.

Splitting the dll into different dlls is too much work, I have not started it yet so it will not be for the next release.

Should we also create a deb package for maemo ?

That's cool! I'll wait with the new packaging until the release is out. I don't think it's necessary to create a deb package for Maemo: Maemo syncs with Debian, so it will be present there in some days. Or is there a different DLL created for Maemo/MeeGo? The I'll have to create two packages.
By the way: We built libqt4pas for all available architectures on Debian... So it will work with every architecture FPC works with. (Also ARM on MeeGo powerpc like stuff)

http://packages.debian.org/squeeze/libqt4pas5

Matthias Klumpp wrote

different DLL created for Maemo/MeeGo? The I'll have to create two packages.

yes, I cannot merge the maemo code with the rest of the platforms because the maemo qt is a different source tar.

Then I have some questions:
1) Will Lazarus support the Maemo version as a new widgetset type?
2) Will the name of the Maemo version and the normal Qt version be different, so that both libs can be installed parallel?
3) Does the Maemo version work with MeeGo too?
4) Will the Mameo and normal version be published in one upstream source tarball?
There's a MeeGo working group in Debian, FPC apps for this platform would be very interesting. But if I can create a package for MeeGo depends on the questions above, important is if Lazarus will support it and if both libs can be installed at the same time.
Thanks!

Then I have some questions:

1) Will Lazarus support the Maemo version as a new widgetset type?

Maemo Qt is just another style, touch friendly, of Qt, a new widget type is overkill. Given the small screen real estate, not being able to use the form editor is not really that bad. You can use the form editor and run the app with the plastik style, it will be pixel perfect, only not very touch screen finger friendly

2) Will the name of the Maemo version and the normal Qt version be different, so that both libs can be installed parallel?

No, for the moment I could not even install Qt Maemo on a normal desktop and vice versa is useless. I hope that with the next Qt version, the Maemo source is just nicely integrated in one Qt everywhere source tarball.

3) Does the Maemo version work with MeeGo too?

I do not have a MeeGo device nor is a usable Phone MeeGo released yet. The current MeeGo is probably Qt 4.6.2, so then answer is yes, but MeeGo is rpm and not deb.
I haven't tried MeeGo yet, so I am not 100% sure. Nokia will not create a MeeGo for N900, but the community is looking into that, if a usable (phone/gps/wifi/...) MeeGo gets released, I might try to install it on my N900 and create a MeeGo Free Pascal Qt binding.

4) Will the Mameo and normal version be published in one upstream source tarball?

See above,

There's a MeeGo working group in Debian, FPC apps for this platform would be very interesting. But if I can create a package for MeeGo depends on the questions above, important is if Lazarus will support it and if both libs can be installed at the same time.

again, Qt Maemo did not install on a regular desktop linux, embedded OpenGL-ES was needed. Installing regular Qt on Maemo does not work either.

Thanks!

Den Jean wrote

[...] > There's a MeeGo working group in Debian, FPC apps for this platform

would

> be very interesting. But if I can create a package for MeeGo depends on > the > questions above, important is if Lazarus will support it and if both

libs

> can be installed at the same time. again, Qt Maemo did not install on a regular desktop linux, embedded OpenGL-ES was needed. Installing regular Qt on Maemo does not work

either.
Then I'll package the "normal" Qt4Pas. If the Maemo version requires OpenGL-ES and stuff, it's a challenge for the Debian Mobile Team. MeeGo will feature Qt 4.7, I think.
Thanks again!

P.S: If you plan to split up the library into a set of others (lib libqt4pas-core, libqt4pas-webkit etc.), please notify me and I'll do the same with the Debian packages.

afaik, there's no any feature needed except that people are asking about OpenGL .... second thing is that I want to keep 2.1 until we release new stable version of lazarus.
So, basicaly 2.2 can be released but will not be available with lazarus until stable release is out (it should be during this summer just after fpc-2.4.2 is out).

zeljko

fpc-2.4.2

is out).

Currently, LibQt4Pas 2.1 is not compatible with the Lazarus version in Debian (0.9.28.2). The Qt4 packages available in Debian are just placeholders for the upcoming Qt bindings.
So, if Lazarus 0.9.30 will use LibQt4Pas 2.2, I'll publish the new version in Debian. If NOT, then a new version of the lib would be useless for users, so I would keep 2.1.
Will Lazarus 0.9.30 support v.2.2?

Matthias Klumpp wrote

Currently, LibQt4Pas 2.1 is not compatible with the Lazarus version in Debian (0.9.28.2). The Qt4 packages available in Debian are just

I know that, it still uses libqt4intf.

placeholders for the upcoming Qt bindings. So, if Lazarus 0.9.30 will use LibQt4Pas 2.2, I'll publish the new version in Debian. If NOT, then a new version of the lib would be useless for users, so I would keep 2.1.

What's wrong with 2.1 ? 0.9.29 uses it ..

Will Lazarus 0.9.30 support v.2.2?

I'm not sure, I've already mentioned that we are planning to release 0.9.30 this summer, so we need to fix a lot of bugs in gtk2 , win32, carbon and some in qt.
What's new in 2.2 anyway ? If you guys says that we badly need 2.2, ok I'll commit 2.2 :), but if that isn't needed so badly, I'll prefer to commit it after release of 0.9.30.

zeljko