User:Crond/sandbox - Revision history

Crond: /* OpenGL driver bugs */ someone elses problem

2011-07-10T15:22:48Z

‎OpenGL driver bugs: someone elses problem

2011-07-10T15:20:11Z

rm more user data; update

2011-07-10T15:13:03Z

‎Known issues: rm user data

2011-06-18T22:03:22Z

‎OpenGL bugs: specificity

2011-06-18T21:49:17Z

‎Application from scratch: placeholder

2011-06-18T21:37:32Z

‎Examples: to be done

2011-06-18T21:18:46Z

‎Persistence

2011-06-18T21:18:35Z

‎Persistence: hmm

2011-06-18T21:17:46Z

‎Subscriptions

2011-06-18T20:54:27Z

‎Examples

@@ Line 138: / Line 138: @@
 </source>
-Additional complications may arise via this chipset.
+Additional complications may arise via this chipset, which are outside the scope of [Py]CEGUI to deal with.
 == Examples ==

@@ Line 14: / Line 14: @@
 == Implementation ==
 PyCEGUI uses [http://freshmeat.net/projects/pyplusplus Py++] and [http://www.boost.org/doc/libs/1_46_1/libs/python/doc/ Boost.Python] - this allows rapid development of the bindings and easy maintenance. It may be a bit slower than [http://www.swig.org/ SWIG], and certainly slower than hand written bindings; but, since neither of those will happen, be content with what is provided. The slowness is very unlikely to be noticeable at all unless you do synthetic tests.
 == Subscriptions ==
@@ Line 37: / Line 26: @@
 <source lang="python">
 wnd.subscribeEvent(PyCEGUI.Window.EventMouseEnters, PythonModule.freeFunction)
 </source>
 == Known issues ==
 === Reference counting ===
-'''Note: Fixed; pending release'''<br />
+'''Note: Fixed; pending release (0.8+)'''<br />
 C++, like C, gives the programmer a pretty free hand in allocating memory, passing it around, and possibly forgetting that it ever exists; while certainly not the recommended way of doing things, it is possible. Python, however, is a different creature altogether - by default, it has a garbage collection system which is implemented via reference counting (the specifics of this are not important, and left as an exercise to the reader if they are that interested). Basically, what this means, is that when an object is no longer needed, it is deleted.

@@ Line 40: / Line 40: @@
 == Known issues ==
 === Reference counting ===
-'''Note: Fixed; pending'''<br />
+'''Note: Fixed; pending release'''<br />
 C++, like C, gives the programmer a pretty free hand in allocating memory, passing it around, and possibly forgetting that it ever exists; while certainly not the recommended way of doing things, it is possible. Python, however, is a different creature altogether - by default, it has a garbage collection system which is implemented via reference counting (the specifics of this are not important, and left as an exercise to the reader if they are that interested). Basically, what this means, is that when an object is no longer needed, it is deleted.

@@ Line 117: / Line 117: @@
 morgul has integrated CEGUI with Panda via [http://www.panda3d.org/forums/viewtopic.php?t=10814 these bindings].
-== OpenGL bugs ==
+== OpenGL driver bugs ==
 If an Intel 915GM, 910GML, or similar chipset is used, it might be necessary to create/destroy a window before the display mode is initialized via OpenGL. The following illustrates:

@@ Line 152: / Line 152: @@
 === Application from scratch ===
-* n
+* See [[User:Crond/sandbox/application1|here]].
-* n+1
-* ...

@@ Line 151: / Line 151: @@
 * A further demonstration of event subscriptions can be found [[User:Crond/sandbox/openglEventExample2|here]].
-=== todo: Multi-class example ===
+=== Application from scratch ===
-See [[PyCEGUI/Example|here]].
+* n

@@ Line 41: / Line 41: @@
 == Known issues ==
 === Persistence ===
-'''Todo: Is this true? And if it's not, why did I think it was?'''
+'''Todo: Is this true? And if it's not, why did I think it was?'''<br />
 For the folks who are exploring both CEGUI and PyCEGUI, consider that attributes and methods defined in Python do not persist when passed back into C++; that is to say, if an attribute is defined on some arbitrary PyCEGUI object, and that object is passed (indirectly) into C++, there should be no expectation that the aforementioned attribute will exist.

@@ Line 147: / Line 147: @@
 === Subscriptions ===
-* A demonstration of subscribing to events in the context of a single class can be found [[User:Crond/sandbox/openglEventExample|here]].
+* A basic demonstration of subscribing to events can be found [[User:Crond/sandbox/openglEventExample|here]].
 === todo: Multi-class example ===
 See [[PyCEGUI/Example|here]].