-
Notifications
You must be signed in to change notification settings - Fork 299
x/mobile driver #45
Comments
I'm up for it :) |
I would prefer gotk3/gtkmm over gxgui. Layout and treeview are mature in gtkmm and map well over X-Window. Gotk3 also helps to reduce the time relearning another api that already works on win64, Linux and osx. |
I was just going to open an issue about this and more... Now I'm not sure if I should post here or new issue. |
+1 |
I'm working on this now (alongside with adding WebGL backend to x/mobile/gl, as discussed in #49). |
Okay, I've got a working version of the driver that uses I ran into two more The other has to do with with
gxui currently tries to support multiple src types like For now, I did a quick hack to get it to run: func CreateIndexBuffer(ty PrimitiveType, data16 []uint16) *IndexBuffer {
// HACK: I know only `USHORT` PrimitiveType is being used atm,
// so this was the quickest thing to get it to compile and run. Assumes LittleEndian.
data := make([]byte, len(data16)*2)
for i, v := range data16 {
data[2*i+0] = byte(v >> 0)
data[2*i+1] = byte(v >> 8)
}
... But we need to think of the right long term solution. There's more than one option, each with tradeoffs (performance vs. generality of code and ability to run on platforms with different endianness, etc.). |
I just need to clean up a little and rebase on top of latest But before I can do that, I need to know the following:
The advantage of replacing current driver is that it will receive most thorough testing as everyone will be using it (and the samples don't need to be duplicated, one for each driver). The disadvantage is that I expect I am guessing it's better to go for 2 separate drivers for now, so that will be my upcoming PR. But feel free to comment on that. |
It's not clear that GXUI will ever be ideal for mobile devices, but it's worth an experiment.
The text was updated successfully, but these errors were encountered: