Change which Program opens Images linked via url

Is it possible to change which program opens images linked to Tellico entries
via a url?

When I click the url, it opens the jpg file with KView. Can I make it open,
e.g with Fspot by clicking on the url?

Changing "Properties - Open with" makes no difference.

Thanks

Jay
--

-- 
View this message in context: http://www.nabble.com/Change-which-Program-opens-Images-linked-via-url-tf4742546.html#a13561797
Sent from the Tellico mailing list archive at Nabble.com.

Re: Change which Program opens Images linked via url

On Saturday 03 November 2007, jaywalker14 wrote:
> Is it possible to change which program opens images linked to Tellico
> entries via a url?

It should follow whatever the file association is for that particular image 
type. Keep in mind that gif, jpeg, and png are all separate file types...

> Changing "Properties - Open with" makes no difference.

I'm not sure exactly what that does. KDE can be funky sometimes with so many 
preferences. In KControl, go to File Associations and find gif (or jpeg or 
whatever) The first application in that list should be the one that opens.

Robbt

Re: Change which Program opens Images linked via url

Fixed it, thanks, Robbie.

File associations lists "jpg" and 'jpeg". All my image files had the "jpg"
extension, so I had been changing the association for that. Now I discover
that the associated program only changes when you change the associations
for "jpeg".

Thanks for your help.

Jay

Robby Stephenson wrote:
> 
> On Saturday 03 November 2007, jaywalker14 wrote:
>> Is it possible to change which program opens images linked to Tellico
>> entries via a url?
> 
> It should follow whatever the file association is for that particular
> image 
> type. Keep in mind that gif, jpeg, and png are all separate file types...
> 
>> Changing "Properties - Open with" makes no difference.
> 
> I'm not sure exactly what that does. KDE can be funky sometimes with so
> many 
> preferences. In KControl, go to File Associations and find gif (or jpeg or 
> whatever) The first application in that list should be the one that opens.
> 
> Robbt

Barcode recognition patch

Hello list,

I finally spent some time recoding my barcode recognition solution in c++.
You can find the current patch (to svn-version 1.3.x of tellico):

http://tellico.dyndns.org/tellico/tellico-barcode-20071104.patch

It certainly needs fine tuning (especially settings for brightness, ...), but on my system it compiles
cleanly and works fine.

br,
Sebastian
--

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

Re: Barcode recognition patch

On Sunday 04 November 2007, Sebastian Held wrote:
> I finally spent some time recoding my barcode recognition solution in
> c++. You can find the current patch (to svn-version 1.3.x of tellico):
>
> http://tellico.dyndns.org/tellico/tellico-barcode-20071104.patch
>
> It certainly needs fine tuning (especially settings for brightness, ...),
> but on my system it compiles cleanly and works fine.

Cool, thanks! I don't actually have a webcam, though. I'm guessing this 
doesn't need any compile-time options?

Robby

Re: Barcode recognition patch

Am Montag, 5. November 2007 schrieb Robby Stephenson:
> On Sunday 04 November 2007, Sebastian Held wrote:
> > I finally spent some time recoding my barcode recognition solution in
> > c++. You can find the current patch (to svn-version 1.3.x of tellico):
> >
> > http://tellico.dyndns.org/tellico/tellico-barcode-20071104.patch
> >
> > It certainly needs fine tuning (especially settings for brightness, ...),
> > but on my system it compiles cleanly and works fine.
>
> Cool, thanks! I don't actually have a webcam, though. I'm guessing this
> doesn't need any compile-time options?
>
> Robby
> _______________________________________________
> tellico-users mailing list
> tellico-users@...
> http://forge.novell.com/mailman/listinfo/tellico-users

no compile time options (apart from enabling debug output ;) ).
It includes some header files - that may need additional checks in autoconf; 
but I don't know how to do that.

The code should not alter tellico's behaviour, when no webcam is present.

br,
Sebastian

_______________________________________________

Re: Barcode recognition patch

On Sunday 04 November 2007, Sebastian Held wrote:
> no compile time options (apart from enabling debug output ;) ).
> It includes some header files - that may need additional checks in
> autoconf; but I don't know how to do that.

Cool, I'll check that.

> The code should not alter tellico's behaviour, when no webcam is present.

Could I convince you to write a paragraph or two describing how it works, 
from a user's point of view, so I can stick that in the documentation? From 
what I can tell, the webcam image shows up in a label that pops up? And it 
beeps when it has an image? Is there any error reporting? That kind of 
stuff..

I'm going to look into getting a webcam myself here. Off to research linux 
support...

Robby

Re: Barcode recognition patch

Am Mittwoch, 7. November 2007 schrieb Robby Stephenson:
> Could I convince you to write a paragraph or two describing how it works,
>from a user's point of view, so I can stick that in the documentation?

I will do that, but it will take one or two weeks. I'm busy right now.

br,
Sebastian

_______________________________________________
tellico-users mailing list
tellico-users@...
http://forge.novell.com/mailman/listinfo/tellico-users

Re: Barcode recognition patch

On Monday 12 November 2007, Sebastian Held wrote:
> Am Mittwoch, 7. November 2007 schrieb Robby Stephenson:
> > Could I convince you to write a paragraph or two describing how it
> > works, from a user's point of view, so I can stick that in the
> > documentation?
>
> I will do that, but it will take one or two weeks. I'm busy right now.

Cool, thanks!

Robby

patch: discogs.com API fetcher

Helping a friend digitizing his entire vinyl-collection I'm happy to
tell that we made a fetcher for the recently appeared Discogs.com API.
The attached patch is a preliminary version, it's based on the
yahoofetcher.cpp and full of bugs and ugly hacks.

What bugs me specifically is that the blocking
FileHandler::readXMLFile()-call in the DiscogsFetcher::getTracks()
method won't work, so I had to set off an async request via KIO::Job
each time a search result is clicked. The problem is, when a search
result is clicked it is immediately displayed and only then the
request to retrieve more detail and the track list is started , so the
missing information is not displayed unless the particular search
result is clicked a second time.

Any ideas how this could be solved?

The diff is made against the tellico-1.3.x branch as of today. I plan
to fix the remaining bugs and adding a configuration dialog for
setting the API key.
The API key in the patch is hard-coded and the one we're using here
currently. You can use it for testing, but please don't abuse it!

Roman