2007/2/25, Seb Ruiz <<a href="mailto:me@sebruiz.net">me@sebruiz.net</a>>:<div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I suggested the possiblity of using QGraphicsView for the context
<br>browser around 6 months ago, when I was working with it heavily on my<br>thesis project. I began to implement a standalone prototype, but that<br>has lagged behind.</blockquote><div><br>Which is probably how the concept started brewing in our minds. I'm not claiming I have original ideas.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'd still be very interested in giving this a shot. When trunk is a<br>little more stable and usable I'll give it a proper attempt.
</blockquote><div><br>This makes me even more confident about the Context View idea.<br><br>After Maximilian wrote this mail we put something on a piece of paper that kind of makes sense:<br></div><ul><li>Data is supplied by scripts (think lyrics-scripts in stable), sources are web-services, external tools,... . Scrips are written in a Kross supported language, we prefer Ruby for the default scripts (minimize dependencies). Data could also come from the database, obviously not using a script.
<br></li><li>Widgets (C++) for QGraphicsView to represent data. These are fast and memory efficient, and might be hardware accelerated (OpenGL). Possibilities are endless.<br></li><li>Themes (CSS) determine colors, place, behaviour, ... of the widgets in the QGraphicsView.
</li></ul>This needs some research to see if we can combine the 3 technologies to create one kick ass eye candy monster.<br><br>Have fun picking holes :) and goodnight.<br><br>Stecchino<br></div>