Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Data Structure</strong><br/> You should definitely use a quadtree (or another hierarchical data structure) to store your canvas and its nodes should contain <strong>much</strong> smaller blocks than 512x512 pixels. Maybe not as small as 1x1 pixels, because then the hierarchical overhead would kill you - you'll find a good balance through testing.</p> <p><strong>Drawing</strong><br/> Let your users only draw on one (the highest) resolution. Imagine a infinitely large uniform grid (two dimensional array). Since you know the position of the mouse and the amount which your users have scrolled from the origin, you can derive absolute coordinates. Traverse the quadtree into that region (eventually adding new nodes) and insert the blocks (for example 32x32) as the user draws them into the quadtree. I would buffer what the user draws in a 2D array (for example as big as his screen resolution) and use a separate thread to traverse/alter the quadtree and copy the data from the buffer to circumvent any delays.</p> <p><strong>Rendering</strong><br/> Traversing the quadtree and copying all tiles to one texture and send it to the GPU? No! You see, sending over one texture which is as big as the screen resolution is not the problem (bandwidth wise). But traversing the quadtree and assembling the final image is (at least if you want many fps). The answer is to store the quadtree in system memory and stream it from the GPU. Means: Asynchronously another thread does the traversal and copies currently viewed data to the GPU in chunks as fast as it can. If your user doesn't view the canvas in full resolution you don't have to traverse the tree to leaf level, which gives you automatic level of detail (LOD).</p> <p><strong>Some random thoughts regarding the proposed strategy</strong><br/></p> <ul> <li>The quadtree approach is great because it is very memory efficient.</li> <li>The streaming idea can be extended to the HDD...<a href="http://www.youtube.com/watch?v=s-DqZ8jAmv0" rel="nofollow">SeaDragon</a></li> <li>A sophisticated implementation would require something like CUDA.</li> <li>If your GPU doesn't offer the necessary performance/programmability, just implement the traversal on the CPU - a little longer delay until the image is fully displayed but should be acceptable. Don't forget to program asynchronously using multiple threads so that the screen doesn't freeze while waiting on the CPU. You can play with different effects: Showing the whole image at once, blurry at first and slowly increasing detail (breadth first search (BFS)) or render it tile by tile (depth first search (DFS)) - maybe mixed with some cool effects.</li> <li>Software implementation should be pretty easy, when only allowing viewing of the canvas at full resolution. If one can zoom out in steps that's a minor change to the traversal. If one can zoom seamlessly, that'll require linear interpolation between neighboring quadtree nodes' tiles - not trivial anymore, but doable.</li> <li>Layers: The quadtree should give you low enough memory consumption allowing you to simply store one quadtree per layer. But when you've many layers you'll need some optimizations to stay in realtime: You can't assemble 200 textures per frame and send them to the GPU. <strong>Maybe</strong> (not totally sure whether that's the best solution) for each layer deleting all nodes of quadtrees beneath that layer whose tile's pixels are completely covered by the layer above. That would need to be done at runtime while drawing and a depth-buffer is required. If you offer an eraser tool, you can't delete nodes but have to mark them as "invisible" so that they can be omitted during traversal.</li> </ul> <p>..off the top of my head. If you have further questions, let me know!</p>
    singulars
    1. This table or related slice is empty.
    1. POI'm looking for any optimizations I can make in a graphics editing program
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDave O.
    1. USDave O.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POI'm looking for any optimizations I can make in a graphics editing program
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThe Quadtree seems like a really cool datastructure for 2d graphics. I think I'll be using it in my next project!
      singulars
      1. PO
      1. USCam
    2. CO@Cam :-) If your colored pixels are distributed very sparse/unevenly it is more memory efficient than a 2D array. If every pixel is covered, it at least offers automatic LOD (good when dealing with huge images). But if the resolution you deal with is ~< 4kx4k pixels simply use 2D arrays.
      singulars
      1. PO
      1. USDave O.
    3. CONothing short of an impressive response, I must say. I never even considered a quadtree, which would fit in extremely well. Would you happen to have any idea of how photoshop and other such fancy programs handle it?
      singulars
      1. PO
      1. USAddi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload