croxit
croxit copied to clipboard
waneck
Desktop client
Hey Cauê!
I started a prototype for an application I'm working with with Croxit and everything's going well so far. I would like to develop a desktop version (mainly OSX for now, but cross-platform would be great afterwards). What's the status of the desktop client?
By the way, the guy from Quaxe made an experiment with embedding Webkit and it was quite successful I think. If you don't have time right now, could you update me on what is the best way to go now and perhaps share the code you already have? I could take it from there, hopefully.
Cheers man!
Marcelo
Sorry for taking some time to answer you! I'm working on it, and I'm working so it can be ready to test until January. But I can't really hand you out a date very easily.
As for the best way to deal with that, after examining the options it seems to me that using CEF3 ( https://code.google.com/p/chromiumembedded/ ) is the best way to go. I started coding all the native code bindings by hand - since croxit 2 will expose window creation for example - but that was a massive amount of boilerplate code and there are some annoying issues - like for example the fact that both Haxe and the native parts need to store a backward reference from haxe to native handle, and native handle to haxe. Anyway, I'm dealing with all that in an exciting way (I think), but I plan to show it off once it's ready :)
If you're interested, drop me a message and let's talk about what's there to do. And anyway I'll let you know once it's ready to be tested!
On Dec 5, 2014, at 2:44 PM, Cauê Waneck [email protected] wrote:
Sorry for taking some time to answer you! I'm working on it, and I'm working so it can be ready to test until January. But I can't really hand you out a date very easily.
No problem! As for the best way to deal with that, after examining the options it seems to me that using CEF3 ( https://code.google.com/p/chromiumembedded/ https://code.google.com/p/chromiumembedded/ ) is the best way to go. I started coding all the native code bindings by hand - since croxit 2 will expose window creation for example - but that was a massive amount of boilerplate code and there are some annoying issues - like for example the fact that both Haxe and the native parts need to store a backward reference from haxe to native handle, and native handle to haxe. Anyway, I'm dealing with all that in an exciting way (I think), but I plan to show it off once it's ready :)
I'm quite curious! Does it leverage macros somehow? If you're interested, drop me a message and let's talk about what's there to do. And anyway I'll let you know once it's ready to be tested!
I’m definitely interested. I have a medium-sized project coming and it consists of a web app and a mobile app. I already started prototyping with Haxe and Croxit, and I like what I see so far, but I’d definitely be interested to help you in any way I can. Let me know if you have a shared list tracking the progress/milestones somewhere. —
Reply to this email directly or view it on GitHub https://github.com/waneck/croxit/issues/2#issuecomment-65851560.