From c81d13d3c2d4a89d9cac3ca54cca69650ec3a52d Mon Sep 17 00:00:00 2001
From: Tim Redfern <tim@eclectronics.org>
Date: Tue, 11 Mar 2014 13:15:31 +0000
Subject: sizing image library

---
 json-instagram/src/exampleApp.cpp | 28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

(limited to 'json-instagram/src/exampleApp.cpp')

diff --git a/json-instagram/src/exampleApp.cpp b/json-instagram/src/exampleApp.cpp
index deb4f35..c064261 100644
--- a/json-instagram/src/exampleApp.cpp
+++ b/json-instagram/src/exampleApp.cpp
@@ -16,6 +16,32 @@ do we worry about memory - I guess not
 
 identify the images
 
+image save- reload system (? even necessary ?)
+camera + button
+transitions
+
+should the loader own the images?
+should the whole image bank be locked while loading?
+alternatively each image could have a lock? - threadedImage
+
+or true mip map via drawsubsection?
+
+start with a max size say 64 - should be 16k inc mip maps
+
+graphics card has 2048MB
+9% in use by ubuntu
+117964 textures
+I wonder is this faster with shared memory..
+
+load app
+get list of images in defined folder
+load them and create mip maps
+store indexed by file stub
+
+when a new image comes in
+load and create mip maps
+save to 
+
 */
 
 long ofToLong(const string& intString) {
@@ -30,9 +56,7 @@ void exampleApp::setup()
 {
 	ofSetFrameRate(24);
 	loader.set_interval(5.00f);
-	cout  << "starting" << endl;
 	loader.start();
-	cout  << "started" << endl;
 }
 
 void exampleApp::update (){
-- 
cgit v1.2.3