omplicated because most digikam-related
> repos don't have tags for releases (or betas):
>
> $ cd libkgeomap/
> $ git tag
>
> ... and no tags anywhere. This makes hard to tell at which point in time
> (save looking through the commit history) commits appeared relative to the
ses (or betas):
$ cd libkgeomap/
$ git tag
... and no tags anywhere. This makes hard to tell at which point in time
(save looking through the commit history) commits appeared relative to the
last release (or beta).
It would make the packagers' job a little easier (and also, it would help
wrt
SC repository).
>
> In short: maintainers should simply stop bundling libraries together
> with digikam, and just make sure digikam (and kipi-plugins as well)
> builds and work fine at least with the latest stable series of them.
>
> Back to the topic of this thread: I'd mildl
able series of them.
Back to the topic of this thread: I'd mildly oppose to move libkgeomap
to kdegraphics, since:
a) its API and ABI get broken from time to time (even too often), with
no actual bump of SONAME
b) digikam people rarely care about non-master branches of those
libraries, fi
On Friday 30 January 2015 01:38:57 Kevin Kofler wrote:
> > libkgeomap (just like all the other libraries used by digikam) has been
> > built as standalone on build.kde.org for years, and digikam (and now
> > kphotoalbum as well) are able to use it fine as "separate" lib
Pino Toscano wrote:
> Why does libkgeomap need to move "somewhere" just to be used by some
> other extragear application? Just do independent releases of it, and
> stop bundling it in digikam, so
> a) it's easier to package it in distros
> b) can be really seen as
ut. I have no idea
what's happening "behind the scenes". I only saw that neither libkface, nor
libkgeomap had a dedicated release, which is not desirable for what I
implemented. And Gilles (who is apparently responsible in some way for both
libs) asked me to ask here for a move of th
El Dimecres, 28 de gener de 2015, a les 14:57:18, Tobias Leupold va escriure:
> > Why does libkgeomap need to move "somewhere" just to be used by some
> > other extragear application? Just do independent releases of it, and
> > stop bundling it in digikam
>
> If
lease
> some extra library from time to time (*) should not be an huge overload.
Well ... I'm not developing neither libkface, nor libkgeomap; we're just using
both libs here at KPhotoAlbum (and would thus like to see distributions
delivering single libs, so that KPA won't have t
On Wednesday 28 January 2015 14:57:18 Tobias Leupold wrote:
> > Why does libkgeomap need to move "somewhere" just to be used by some
> > other extragear application? Just do independent releases of it, and
> > stop bundling it in digikam
>
> If I remember c
> Why does libkgeomap need to move "somewhere" just to be used by some
> other extragear application? Just do independent releases of it, and
> stop bundling it in digikam
If I remember correctly, this is the problem. The Digikam team can't or do not
want to do single
time and now, we have a Digikam-
> independent libkface release to be found in unstable/applications (which can
> be used by distributors to create Digikam-independent libkface packages).
> Thanks again for the move :-)
>
> Recently, we started to use another library from Digikam in
time and now, we have a Digikam-
> independent libkface release to be found in unstable/applications (which can
> be used by distributors to create Digikam-independent libkface packages).
> Thanks again for the move :-)
>
> Recently, we started to use another library from Digikam in
Tobias Leupold va
> > >
> > > escriure:
> > >> Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid:
> > >> > H, i understand you're the only user at the moment, but how is
> > >> >
> > >> >
> > >&
On Sun, Jan 4, 2015 at 8:21 PM, Michael G. Hansen wrote:
>
> We also had a Google Summer of Code student work on the library, and the
> project was not rejected by Google.
I would actually be surprised if it was. GSoC is run by the Google Open
Source Office
and this program particularly is done
Hi,
Happy New Year to all in this room.
Thanks Micheal for all details about libkgeomap history, especially
GoogleMaps rules.
Just few words about libkgeomap KF5 port :
- Library is fully ported as QT5/KF5 and sound work fine.
- Alin Marin Elen currently work on
KGeoMap::HTMLWidget class to
On 03.01.2015 15:09, Tobias Leupold wrote:
IMHO, the real question is, shouldn't that pointless wrapper be deprecated
in favor of just using Marble directly?
Can marble be used in an identical way as libkgeomap, as a QWidget only
displaying a map with not only coordinates but also
On Samstag, 3. Januar 2015 15:09:58 CEST, Tobias Leupold wrote:
IMHO, the real question is, shouldn't that pointless wrapper be deprecated
in favor of just using Marble directly?
Can marble be used in an identical way as libkgeomap
Afaiu and would expect, libkgeomap wraps m
> IMHO, the real question is, shouldn't that pointless wrapper be deprecated
> in favor of just using Marble directly?
Can marble be used in an identical way as libkgeomap, as a QWidget only
displaying a map with not only coordinates but also photo thumbnails (grouping
the coordinat
Albert Astals Cid wrote:
> H, i understand you're the only user at the moment, but how is
>
> ****
> libkgeomap is a wrapper between marble for local map, OpenStreetMap,
> and GoogleMaps, to display geolocated items place over a world map.
>
> A widget is p
about the KDE internals and where to put
some libraries, but ;-) What about kde-edu? This is where marble lives I
think? Essentially, libkgeomap has nothing to do with graphics or photo
management (although it's not used for anything else at the moment and as far
as I know). It simply sh
criure:
>> >> Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid:
>> >> > H, i understand you're the only user at the moment, but how is
>> >> >
>> >> >
>> >> > libkgeomap is a wrapper betwee
7:48 schrieb Albert Astals Cid:
> >> > H, i understand you're the only user at the moment, but how is
> >> >
> >> >
> >> > libkgeomap is a wrapper between marble for local map, OpenStreetMap,
> >> > and GoogleMaps, to display geoloc
at the moment, but how is
>> >
>> >
>> > libkgeomap is a wrapper between marble for local map, OpenStreetMap,
>> > and GoogleMaps, to display geolocated items place over a world map.
>> >
>> > A widget is provided, and collection of tools to process :
>&
El Diumenge, 21 de desembre de 2014, a les 19:39:27, Tobias Leupold va
escriure:
> Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid:
> > H, i understand you're the only user at the moment, but how is
> >
> >
> > libkgeomap is a wrap
Am Sonntag 21 Dezember 2014, 19:27:48 schrieb Albert Astals Cid:
> H, i understand you're the only user at the moment, but how is
>
> ****
> libkgeomap is a wrapper between marble for local map, OpenStreetMap,
> and GoogleMaps, to display geolocated items place over
ou're the only user at the moment, but how is
****
libkgeomap is a wrapper between marble for local map, OpenStreetMap,
and GoogleMaps, to display geolocated items place over a world map.
A widget is provided, and collection of tools to process :
- Reverse Geocoding,
- Tracks managemen
be found in
>> >> unstable/applications
>> >> (which can be used by distributors to create Digikam-independent libkface
>> >> packages). Thanks again for the move :-)
>> >>
>> >> Recently, we started to use another library from Digikam in KPhotoAlbum,
&
ibkface release to be found in
> >> unstable/applications
> >> (which can be used by distributors to create Digikam-independent libkface
> >> packages). Thanks again for the move :-)
> >>
> >> Recently, we started to use another library from Digikam in KPh
ges). Thanks again for the move :-)
>>
>> Recently, we started to use another library from Digikam in KPhotoAlbum,
>> libkgeomap. Would it be possible (of course after some review etc.) to do
>> the same with this library, for the same reasons? Probably,
>> kdegraphics/libs
eantime and now, we have a
> Digikam- independent libkface release to be found in unstable/applications
> (which can be used by distributors to create Digikam-independent libkface
> packages). Thanks again for the move :-)
>
> Recently, we started to use another library from Digika
2014-12-15 22:01 GMT+01:00 Albert Astals Cid :
> El Dilluns, 15 de desembre de 2014, a les 21:57:05, Gilles Caulier va
> escriure:
>> libkgeomap is a wrapper between marble for local map, OpenStreetMap,
>> and GoogleMaps, to display geolocated items place over a world map.
2014-12-15 22:01 GMT+01:00 Albert Astals Cid :
> El Dilluns, 15 de desembre de 2014, a les 21:57:05, Gilles Caulier va
> escriure:
>> libkgeomap is a wrapper between marble for local map, OpenStreetMap,
>> and GoogleMaps, to display geolocated items place over a world map.
El Dilluns, 15 de desembre de 2014, a les 21:57:05, Gilles Caulier va
escriure:
> libkgeomap is a wrapper between marble for local map, OpenStreetMap,
> and GoogleMaps, to display geolocated items place over a world map.
>
> A widget is provided, and collection of tool
libkgeomap is a wrapper between marble for local map, OpenStreetMap,
and GoogleMaps, to display geolocated items place over a world map.
A widget is provided, and collection of tools to process :
- Reverse Geocoding,
- Tracks management,
- Selection over map to process searches.
It used in
eantime and now, we have a
> Digikam- independent libkface release to be found in unstable/applications
> (which can be used by distributors to create Digikam-independent libkface
> packages). Thanks again for the move :-)
>
> Recently, we started to use another library from Digika
I would just to indicate that libkgeomap is already ported to KF5, as
libkipi, libkexiv2, libkface, and libkdcraw. see this wiki page for
details :
https://techbase.kde.org/Projects/Digikam/CodingSprint2014#KF5.2FQt5_Port_Status
Gilles Caulier
2014-12-14 18:57 GMT+01:00 Tobias Leupold :
>
(which can
be used by distributors to create Digikam-independent libkface packages).
Thanks again for the move :-)
Recently, we started to use another library from Digikam in KPhotoAlbum,
libkgeomap. Would it be possible (of course after some review etc.) to do the
same with this library, for the
Hi all,
As has been requested by a repository administrator, the repository
"libkmap" on git.kde.org has been renamed to "libkgeomap". Those
people with clones of this repository will need to adjust them in
order to continue using them as follows:
git remote set-url origin kd
39 matches
Mail list logo
