Hi
On Nov 23, 2016 23:17, "Jens Georg" wrote:
>>
>> That's also my feeling from a quick glance at the conflicts.
>> True, the UI integration must be rewritten but it looks +/-
copy-paste-and-adapt from your changes.
>
>
> Done locally. Do you want a pull request?
Absolutely!
Hi
> Done locally. Do you want a pull request?
Thanks a lot.
I would be interested in testing it out, can you push your branch
somewhere (shotwell git has already many branches, so one could
add that one).
Norbert
--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
On 2016년 11월 23일 09:42, Jens Georg wrote:
There's a plan, but there is still no clue which tile provider to use
for that.
I know someone at mapbox. I could ask if they are willing to support
this project.
___
shotwell-list mailing list
Hi
On Nov 23, 2016 22:57, "Jens Georg" wrote:
>
> On Wed, 2016-11-23 at 14:58 +0100, Andreas Brauchli wrote:
> > Hey
> > On Nov 23, 2016 2:19 PM, "Jens Georg" wrote:
> > >
> > >
> > >>> There's a plan, but there is still no clue which tile provider to
> > use
Hey
On Nov 23, 2016 2:19 PM, "Jens Georg" wrote:
>
>
>>> There's a plan, but there is still no clue which tile provider to use
for
>>> that.
>>
>>
>> Ok, that are good news.
>>
>>> What's the issue with rebasing it against master?
>>
>>
>> Well, lots of conflicts that are not
There's a plan, but there is still no clue which tile provider to use
for
that.
Ok, that are good news.
What's the issue with rebasing it against master?
Well, lots of conflicts that are not trivial... the most persistent one
is in src/library/LibraryWIndow.vala, but there are big diffs
what is the current status of the map widget? I have tried to rebase
your
latest set of patches onto current master, without much success.
Is there any plan to include the map widget into the master branch?
There's a plan, but there is still no clue which tile provider to use
for that.