nocui: a template for porting new toolkits

Signed-off-by: Jeff Carr <[email protected]>

1 files changed, 29 insertions, 0 deletions

diff --git a/toolkit/gocui/structs.go b/toolkit/gocui/structs.go
index e9f89af..b2a8b20 100644
--- a/toolkit/gocui/structs.go
+++ b/toolkit/gocui/structs.go
@@ -85,11 +85,40 @@ type config struct {
 	writeMutex sync.Mutex
 }
 
+// deprecate these
 var (
 	initialMouseX, initialMouseY, xOffset, yOffset int
 	globalMouseDown, msgMouseDown, movingMsg bool
 )
 
+// this is the standard binary tree structure for toolkits
+type node struct {
+	parent	*node
+	children []*node
+
+	WidgetId	int	// widget ID
+	WidgetType	toolkit.WidgetType
+	ParentId	int	// parent ID
+
+	Name   string
+	Text   string
+
+	// This is how the values are passed back and forth
+	// values from things like checkboxes & dropdown's
+	B	bool
+	I	int
+	S	string
+
+	A	any // switch to this or deprecate this? pros/cons?
+
+	// This is used for things like a slider(0,100)
+	X      int
+	Y      int
+
+	// the internal plugin toolkit structure
+	tk *cuiWidget
+}
+
 // the gocui way
 // the logical size of the widget
 // corner starts at in the upper left corner