Changes between Version 7 and Version 8 of wxGUIDevelopment/Refactoring/wxGUIAPIproposal

Timestamp:

03/29/13 08:44:33 (12 years ago)

Author:

wenzeslaus

Comment:

markup improvements and rashadkm's rendering notes moved to wxGUIDevelopment/MapRendering

wxGUIDevelopment/Refactoring/wxGUIAPIproposal

@@ -50 +50 @@
 }}}
 
-'''Proposing More classes'''
+== Proposing More classes ==
+
+=== non-GUI classes ===
+
 {{{
 #!python
@@ -61 +64 @@
 
   self.ltype = None
-  self.lname  = None
+  self.lname = None
   self.style = None
 
@@ -127 +130 @@
       """TBD"""
 
+}}}
+
+=== GUI classes ===
+
+{{{
+#!python
 
 class LayerManagerFrame(wx.Frame, layerManager):
@@ -163 +172 @@
 }}}
 
-'''Simple usage of the above Pseudo code'''
+=== Simple usage of the above Pseudo code ===
 
 {{{
@@ -179 +188 @@
 ''PyDispatcher added by vaclav should be used for Event mechanism in the New GUI''
 
-'''New Rendering Model'''[[BR]]
-[[BR]]
-With the help of GRASS Python modules, It easy to pull chunks from raster data as Numpy array. A new rendering model (in-memory) can be added to wxGUI [[BR]] which can directly display a numpy array as wx.Image. This will obivously increase the performance of rendering layers because the overhead of [[BR]]reading and writing data to file (PNG adds a compression during packing and unpacking) can be saved. Also the extent based rendering [[BR]]will allow to read portion of raster image than whole dataset. Also a tile based technique can be added to this which improves the rendering [[BR]]performance further.
-[[BR]]
-Basically this will do what d.rast or generally speaking d.* modules do. I agree adding other modules such as d.legend etc is a massive work. But compared[[BR]] to dealing with large dataset I think its worth it.[[BR]]. 
-[[BR]][[BR]]
-''This is just a breif of what I have. I can provide further details if anyone is interested''
 
 '''''TBD: To Be Decided'''''