Re: Tellico 1.2.14 Released

On Saturday, Sep 22nd 2007 at 19:46 -0000, quoth Robby Stephenson:

=>Tellico 1.2.14 is available at 
=>http://www.periapsis.org/tellico/download/tellico-1.2.14.tar.gz
=>

Is it possible to add a contrib directory or something like that to the 
distribution? As a kickoff, I'd like to contribute the tellico.spec file I 
found a while back that works with Core 4/1.2.14 found at 

http://steveo.syslang.net/tellico.spec

Yes? No?

--

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: Tellico 1.2.14 Released

Dnia niedziela, 7 października 2007, Robby Stephenson napisał:
> On Friday 05 October 2007, Steven W. Orr wrote:
> > Is it possible to add a contrib directory or something like that to the
> > distribution? As a kickoff, I'd like to contribute the tellico.spec file
> > I found a while back that works with Core 4/1.2.14 found at
> >
> > http://steveo.syslang.net/tellico.spec
> >
> > Yes? No?
>
> No reason why not, really. That helps with the RPM building, I suppose?

Glad that you remind me of that. 1.2.14 already sent to PLD Linux builders 
with http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/tellico.spec ;)

--

-- 
Łukasz [DeeJay1] Jernaś

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

next version development

Hi everyone,

I've been trying to work on Tellico 2.0 a little bit in the last month or 
so, and I've made some progress. I'm still trying to learn efficient SQL, 
and using threads with a database is rather non-trivial. The current state 
is still pretty much unusable, but most of the DB code is there. 
Unfortunately, I haven't gotten the performance anywhere close to what it 
needs to be. Everything is very slow. 

All that to say, I have other itches to scratch. :) There are still some 
pending patches (Cyril's 'merge entries' code, and Steve Beattie's patch 
from last year for board games) that I'd like to get into a release 
version, and that probably warrants a 1.3 release series.

So what I think I'm going to do is to continue to work on the SQL backend, 
but I'll probably start moving towards getting a 1.3 release out, with some 
significant updates, new features, etc. That probably makes v2 sound like 
vaporware, but such is life. :)

I'm still not sure when I'll start the port to KDE4 yet, either.

There will be some string changes, too, in 1.3, so I'll give a heads-up to 
the translators when it's appropriate.

Thanks!
Robby

Re: next version development

Sun, 7 Oct 2007 09:35:27 -0700, Robby Stephenson <robby@...> :

> So what I think I'm going to do is to continue to work on the SQL
> backend, but I'll probably start moving towards getting a 1.3 release
> out, with some significant updates, new features, etc. That probably
> makes v2 sound like vaporware, but such is life. :)
I think a 1.3 branch is a good idea. SQL backend is a good thing but
I don't think it's worth freezing other new features.

I'd like to propose some enhancements on the audio metadata importer,
like the inclusion of bitrate [1]. I'm using the importer a lot, I can
come up with additional suggestions if there's a 1.3 branch.

                   Doruk

[1]
http://forge.novell.com/pipermail/tellico-users/2007-February/001199.html

Re: next version development

On Sunday 07 October 2007, Doruk Fisek wrote:
> I'd like to propose some enhancements on the audio metadata importer,
> like the inclusion of bitrate [1]. I'm using the importer a lot, I can
> come up with additional suggestions if there's a 1.3 branch.

Right, I had your message in my patch mailbox, too. I'll have to check, I 
can't remember if I applied it to the 1.3 branch or not.

Robby

Re: next version development

On Sunday 07 October 2007, Doruk Fisek wrote:
> I'd like to propose some enhancements on the audio metadata importer,
> like the inclusion of bitrate [1]. I'm using the importer a lot, I can
> come up with additional suggestions if there's a 1.3 branch.
>
> [1]
> http://forge.novell.com/pipermail/tellico-users/2007-February/001199.html

The assumption there is that all of the audio files for a given album have 
the same bitrate, right? I mean, Tellico treats an album as the atomic 
entity, rather than the track, so there's only one bitrate per album. Do 
you think that's reasonable?

Robby

Re: next version development

Mon, 8 Oct 2007 21:56:06 -0700, Robby Stephenson <robby@...> :

> The assumption there is that all of the audio files for a given album
> have the same bitrate, right? I mean, Tellico treats an album as the
> atomic entity, rather than the track, so there's only one bitrate per
> album. Do you think that's reasonable?
Most of the time. I think there could be two better alternatives :

- Take an average of all of the tracks as the album bitrate
- Add bitrate column for each track (not just album) next to
title/length. As "Total", an average could be calculated.

                   Doruk

--
FISEK INSTITUTE - http://www.fisek.org.tr

Images

Is it possible to have image files stored in different directories other than
the data directory?

Also, is it possible to have images linked without having to have them
copied to the data directory and given one of those long file names?

I would like to create a number of different collection files, each with a
lot of images attached. As I understand it at present, images are copied to
the data directory. This gets them rather mixed up and makes editing rather
confusing. Also, if I have to change the image file that is attached to the
collection file, it seems that the image file is duplicated, with the old
one staying in the data directory as well as the new one.

I know that I can use a link field to attach the image files via URL, but
this does not give me those neat little images on each entry's page.

This is a great program, but I wonder if I am mistaken in using it for
collections that require so many images to be attached.

Jay

--

-- 
View this message in context: http://www.nabble.com/Images-tf4598128.html#a13128191
Sent from the Tellico mailing list archive at Nabble.com.

Re: Images

Hello,

I would like that very much, too. This will make it easy to publish a
collection to an internet server via rsync (currently the zip changes
too much for rsync).
I would suggest placing the image dir side by side to the project file.
 - books.tc
 - books_images/

br,
Sebastian

jaywalker14 schrieb:
> Is it possible to have image files stored in different directories other than
> the data directory?
>
> Also, is it possible to have images linked without having to have them
> copied to the data directory and given one of those long file names?
>
> I would like to create a number of different collection files, each with a
> lot of images attached. As I understand it at present, images are copied to
> the data directory. This gets them rather mixed up and makes editing rather
> confusing. Also, if I have to change the image file that is attached to the
> collection file, it seems that the image file is duplicated, with the old
> one staying in the data directory as well as the new one.
>
> I know that I can use a link field to attach the image files via URL, but
> this does not give me those neat little images on each entry's page.
>
> This is a great program, but I wonder if I am mistaken in using it for

Re: Images

On Tuesday 09 October 2007, jaywalker14 wrote:
> Is it possible to have image files stored in different directories other
> than the data directory?

No, not at the moment.

> Also, is it possible to have images linked without having to have them
> copied to the data directory and given one of those long file names?

No, not at the moment.

> This is a great program, but I wonder if I am mistaken in using it for
> collections that require so many images to be attached.

Probably. Sounds like you want more of an image database kind of 
application, with support for some bit of metadata. It'd take some work to 
move Tellico in that direction, I think.

Robby