Storage and View -> imageViewer

[C167]

Are talking here about binary .rcc file or a .cpp file generated by rcc? Anyway, you can ask Qt to compress the resource file --- it should reduce the size of SVG files.

hm... i looked at the cpp, sry, the binary that comes out is much smaller.

Not QVariant, but SQLite. It supports only text, so Qt will have to encode the data somehow. Try adding the same files to the database and compare the size of .rcc file and the database.

So, is there a documentation about that? AFAIR, base64 would make the files 1.33 times larger

Yes, only Qt knows how to read .rcc files. Another solution is to use some 3rd party library for storing those files or you can keep them as regular files.

no, i mean the data in the database... but that would be no big deal to write a simple program that reads one file and outputs the original jpg.

[jacek]

So, is there a documentation about that?

I don't think so. I've just made a simple test program and it seems that Qt cheats when it comes to QPixmaps stored as QVariants. You will have to convert images to strings yourself.

[Thomas]

Perhaps I am missing something here, but why shall the application contain the images but not load them dynamically?

At program start up I would rather browse through the image directory/directories, load them and store them into SQLite as BLOBs. BLOBs will be stored "as is" so neither a conversion is necessary nor will this result in an inflated data size.

Pros:
- All images will be automatically be stored in the DB after start up.
- If the CD image changes with respect to new images, no recompilation is necessary.
- A default DB could be created and put on the CD, containing already stored images which are common to all future versions.

Cons:
- Depending on the amount of images to be stored on start up, the time until the application is "ready" could increase significantly.

[C167]

[QUOTE=Thomas;59052]Perhaps I am missing something here, but why shall the application contain the images but not load them dynamically?[QUOTE]Oh, maybe i was a bit unclear: the program+database gets copied to the cd, and the program should show the images, either from db directly or with the help of the db, from files. the discussion about containing them was about rcc's, which i use to store the button icons etc.

At program start up I would rather browse through the image directory/directories, load them and store them into SQLite as BLOBs. BLOBs will be stored "as is" so neither a conversion is necessary nor will this result in an inflated data size.
Pros:
- All images will be automatically be stored in the DB after start up.
- If the CD image changes with respect to new images, no recompilation is necessary.
- A default DB could be created and put on the CD, containing already stored images which are common to all future versions.

Cons:
- Depending on the amount of images to be stored on start up, the time until the application is "ready" could increase significantly.

yea, I was unclear
we create a CD, that contains:

• the cdlauncher
• a pictureDB
• some programms
• pictures, that should be displayed

so, thats similar to digikam: we store information about the pics in the db right now.
ATM, the DB contains some tables containing author-, album- and picture-information. The application loads the db and if you select an image, it gets pulled from the contruct pics/{albumname}/{filename}
Scanning through the images at startup is problematically, because they are on the cd, which is quite slow. it would mean that we would have to browse through nearly 500MBs of images, so the program would need up to several minutes to start. impossible!
But writing a simple two-liner, that uses the db (which already stores everything neccessary, except the pic) to collect every image and writes it into the db, that would be a good method, as we have to run it once, put everything together in an iso and mount it in the windows-vm.
Thanks so far, i'll write a little test-prg to test how we have to deal with images in DBs
C167

[C167]

okay, i wrote a little testapp that stores an image (or every file you give it) into a BLOB-field. the db-file grows to the size of the given image, so it should be in it, although the chars i get if i do a select to qDebug() are only 8, all unprintable. So, here's my app:

int main( int argc, char *argv[] )
{
	QCoreApplication app( argc, argv );
	QSqlDatabase db = QSqlDatabase::addDatabase( "QSQLITE" );
	db.setDatabaseName( "/home/stefan/source/qt4/cdlauncher/pictures.db" );
	if ( !db.open() )
	{
		qDebug() << "Opening failed";
		return 1;
	}
	qDebug() << "Opening successfull, using database " << db.databaseName();
	qDebug() << "filling an image into the DB...";
	QFile file( "/home/stefan/pic/space/191853main_image_feature_929_full.jpg" );
	QByteArray fileData;
	if ( file.exists() )
	{
		if ( file.open( QIODevice::ReadOnly ) )
		{
			fileData = file.readAll();
			file.close();
		}
	}
	else
	{
		qDebug() << "File " << file.fileName() << " could not be located";
	}
	QSqlQuery query("UPDATE pictures SET data=? WHERE rowid=1;");
	query.addBindValue(fileData);
	query.exec();
	qDebug() << query.lastError();
	return 0;
}

int main( int argc, char *argv[] )
{
	QCoreApplication app( argc, argv );
	QSqlDatabase db = QSqlDatabase::addDatabase( "QSQLITE" );
	db.setDatabaseName( "/home/stefan/source/qt4/cdlauncher/pictures.db" );
	if ( !db.open() )
	{
		qDebug() << "Opening failed";
		return 1;
	}
	qDebug() << "Opening successfull, using database " << db.databaseName();
	qDebug() << "filling an image into the DB...";
	QFile file( "/home/stefan/pic/space/191853main_image_feature_929_full.jpg" );
	QByteArray fileData;
	if ( file.exists() )
	{
		if ( file.open( QIODevice::ReadOnly ) )
		{
			fileData = file.readAll();
			file.close();
		}
	}
	else
	{
		qDebug() << "File " << file.fileName() << " could not be located";
	}
	QSqlQuery query("UPDATE pictures SET data=? WHERE rowid=1;");
	query.addBindValue(fileData);
	query.exec();
	qDebug() << query.lastError();
	return 0;
}

To copy to clipboard, switch view to plain text mode 

that works everything is hardcoded, i know, but its only a test to see how it works.
So, now i want to retrieve the data. the normal way to display an image is

imgLabel->setPixmap(QPixmap::fromImage(QImage("filename")));

imgLabel->setPixmap(QPixmap::fromImage(QImage("filename")));

To copy to clipboard, switch view to plain text mode 

After some testing, reading and coffee-ing, i found the following way:

int main( int argc, char *argv[] )
{
	Q_INIT_RESOURCE( application );
	QApplication app( argc, argv );
	QSqlDatabase db = QSqlDatabase::addDatabase( "QSQLITE" );
	db.setDatabaseName( "/home/stefan/source/qt4/cdlauncher/pictures.db" );
	if ( !db.open() )
	{
		qDebug() << "Opening failed";
		return 1;
	}
	QSqlQuery query( "SELECT data FROM pictures WHERE rowid=1;" );
	QSqlRecord record = query.record();
	query.next();
	qDebug() << query.lastError();
	QByteArray ba = query.value(0).toByteArray();
	QWidget *wid = new QWidget();
	QLabel *imgLabel = new QLabel( wid );
	QPixmap *pic = new QPixmap();
	pic->loadFromData( query.value( record.indexOf( "data" ) ).toByteArray() );
	imgLabel->setPixmap( *pic );
	wid->show();
	return app.exec();
}

int main( int argc, char *argv[] )
{
	Q_INIT_RESOURCE( application );
	QApplication app( argc, argv );
	QSqlDatabase db = QSqlDatabase::addDatabase( "QSQLITE" );
	db.setDatabaseName( "/home/stefan/source/qt4/cdlauncher/pictures.db" );
	if ( !db.open() )
	{
		qDebug() << "Opening failed";
		return 1;
	}
	QSqlQuery query( "SELECT data FROM pictures WHERE rowid=1;" );
	QSqlRecord record = query.record();
	query.next();
	qDebug() << query.lastError();
	QByteArray ba = query.value(0).toByteArray();
	QWidget *wid = new QWidget();
	QLabel *imgLabel = new QLabel( wid );
	QPixmap *pic = new QPixmap();
	pic->loadFromData( query.value( record.indexOf( "data" ) ).toByteArray() );
	imgLabel->setPixmap( *pic );
	wid->show();
	return app.exec();
}

To copy to clipboard, switch view to plain text mode 

it successfully reads out the image and displays it...
a SELECT-query seems not to like the QSqlQuery::exec () method. So i used a single next() for that...
So far, everything is fantastic, thank you very much Thomas and jacek

[Thomas]

One last issue.

Make sure you delete stuff which you created with new.

[jacek]

a SELECT-query seems not to like the QSqlQuery::exec () method.

If you pass a string to QSqlQuery constructor, it will execute it immediately. It should be:

QSqlQuery query;
query.prepare("UPDATE pictures SET data=? WHERE rowid=1;");
query.addBindValue(fileData);
query.exec();

QSqlQuery query;
query.prepare("UPDATE pictures SET data=? WHERE rowid=1;");
query.addBindValue(fileData);
query.exec();

To copy to clipboard, switch view to plain text mode 

And the select should be:

QSqlQuery query( "SELECT data FROM pictures WHERE rowid=1;" );
query.next(); // <- positions the query on the first row
QSqlRecord record = query.record();

QSqlQuery query( "SELECT data FROM pictures WHERE rowid=1;" );
query.next(); // <- positions the query on the first row
QSqlRecord record = query.record();

To copy to clipboard, switch view to plain text mode 

[C167]

If you pass a string to QSqlQuery constructor, it will execute it immediately. It should be:

QSqlQuery query;
query.prepare("UPDATE pictures SET data=? WHERE rowid=1;");
query.addBindValue(fileData);
query.exec();

QSqlQuery query;
query.prepare("UPDATE pictures SET data=? WHERE rowid=1;");
query.addBindValue(fileData);
query.exec();

To copy to clipboard, switch view to plain text mode 

And the select should be:

QSqlQuery query( "SELECT data FROM pictures WHERE rowid=1;" );
query.next(); // <- positions the query on the first row
QSqlRecord record = query.record();

QSqlQuery query( "SELECT data FROM pictures WHERE rowid=1;" );
query.next(); // <- positions the query on the first row
QSqlRecord record = query.record();

To copy to clipboard, switch view to plain text mode 

Okay, thank you

One last issue.
Make sure you delete stuff which you created with new.

I thought Qt is handling such things for all the classes that inherit QObject, at least their own stuff? Okay, thx I'll add everything to my destructors

[jacek]

I thought Qt is handling such things for all the classes that inherit QObject, at least their own stuff?

Yes, it does, but only for objects that have a parent.

[C167]

okay, thx