Re: some whishlists

Hello,

On Jan/15/2008, Aurélien Gâteau wrote:
> Le Monday 14 January 2008 23:30:58 Carles Pina i Estany, vous avez écrit :
> > Hello,
> >
> > On Jan/14/2008, Aurélien Gâteau wrote:
> > > Le Monday 14 January 2008 10:43:27 Angelo Naselli, vous avez écrit :
> > > > > > -Automatically plays audio files from photo directory, using Fade
> > > > > > In and Fade Out (slowly increase and decrase the volume), maybe
> > > > > > allowing to repeat or setting up the slide duration to some value
> > > > > > to watch all photos during one song or two songs.
> > > >
> > > > Dosn't it need something like a db? I mean how can you relate one by
> > > > one photo(s) to audio(s) - or a group of course-?
> >
> > here I thought about gwenview configuration file (XML? :-) )
> 
> Gwenview configuration file is not XML, it's a simple INI-like format,
> just like other KDE applications.

What I had in my head: I was thinking to have a Gwenview
extra-configuration file in the same directory than images to setup the
music, repetions, transitions, etc.

My first step was to not have configuration file (automatic searching
and playing the audio files), second step was to use a configuration
file. Angelo said an XML file, I agree that this configuration file
could be a very simple XML file (so Gwenview could write it after setup
some parameters in a dialog) or could also be a INI-like configuration
file (this is what Gwenview is using for gwenviewrc, I know)

(I'm not fan of XML configuration files, but last week I had to take a
look to Ant/Nant -ops!- and I felt that is not so bad :-) )

(I think that we can talk about it in some weeks, when we/me/you start
to implement it)

> > Yes, XML file looks fine. Actually: I don't want to do things with DB's
> > and gwenview. One of the things that I expect from gwenview is to not
> > have DB dependencies, or internal files for everything, etc. so please,
> > no DB (other programs could do it...)
> 
> Actually if we were using a db engine, it would most probably be
> sqlite. Since sqlite is bundled with Qt, it would not introduce any
> new dependency.

Yes I understand. But I still prefer a text file (INI like file) or XML
file in the directory than a .db binary file :-)

> > XML file: great! then, as Angelo Naselli said we could configure which
> > "in directory" music files play, which order, how many time, which kind
> > of transitions, etc.
> >
> > First step for this is the transitions engine. Aurélien: how do you do
> > this? just loading two image files to QByteArray or some Qt structure
> > and play with pixels? I'm curious to know. And also, any expected date
> > for first public testing? :-)
> 
> Hum... better let Qt do the work :-). If you combine QPainter and QGLWidget 
> you can produce hardware-accelerated alpha blending for example. It's quite 
> easy. Just paint the current pixmap, then paint the next pixmap over it, more 
> and more opaque.

Good! I have limited knowledges of Qt API, I didn't know about
QGLWidget. I hope that we can do some other transition effects :-)

> The thing is: it would be much easier to implement if we use a
> specialized view for fullscreen. Right now the fullscreen view is the
> same as the windowed image view: it can zoom and pan, it can even crop
> images. Would all of you consider it a major feature loss to have a
> zoom-to-fit only fullscreen view?

I don't crop images in full screen mode, but zoom and pan in full screen
mode is an important feature. I would consider it a major feature loss
(zoom and pan, not crop). But I would consider a major feature to have
transitions in full screen mode :-)

-- 
Carles Pina i Estany		GPG id: 0x8CBDAE64
	http://pinux.info	Manresa - Barcelona

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/