You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
This looks great for custom ui, interaction and simple games. It reminds me of PaintCode workflow, but cross platform. I would love to see an end-to-end tutorial / write-up on how to create a skiasharp asset and incorporate the generated code into a xamarin app with a visual property on the skiasharp object (like color, rotation or position) linked to a viewmodel property in the app changing in real-time. A little unclear on how the obiscript fits into this scenario... unless the obiscript is simply for design time visualization in the designer. Very promising and thanks for opening it up!
The text was updated successfully, but these errors were encountered:
migueldeicaza
changed the title
Looks very promising!
Wanted - Walkthrough on using Kimono with SkiaSharp
Mar 20, 2017
twheelmaker, Thanks for the very useful feedback. I'll see if I can't get a quick tutorial put together for you when I get a touch of free time. Right now, take a look at the TestConsumerxxx projects in the solution for output usage.
About ObiScript, eventually I want the scripted changes to flow into the generated code, this was beyond the scope of this release however. That said, if you export using the KimonoCore libraries and include KimonoCore in your consuming app(s), then the scripts still work.
Please let me know if you have any other questions and keep the great feedback coming.
KMullins-Xam, Thanks! I admittedly haven't dug in too deep yet... will check out the tests. I recommend looking at how PaintCode handles parameterized drawings (or don't... maybe I'm assuming too much in how I imagine this is supposed to be used). I think my questions around ObiScript will be answered by exploring the KimonoCore consumer tests.
I'm completely new to skiasharp though... do touch events get exposed at asset level or somehow through the container skiasharp view for interaction or is this more for low-level drawing only?
twheelmaker, SkiaSharp is strictly graphics only. It's up to the developer to add any user interaction. That said, some simple interactions like touch and drag might possibly be added as Kimono attributes that could be assigned to a Sketch and exported in code. Of course, that would be a feature request and something for a future release.
This looks great for custom ui, interaction and simple games. It reminds me of PaintCode workflow, but cross platform. I would love to see an end-to-end tutorial / write-up on how to create a skiasharp asset and incorporate the generated code into a xamarin app with a visual property on the skiasharp object (like color, rotation or position) linked to a viewmodel property in the app changing in real-time. A little unclear on how the obiscript fits into this scenario... unless the obiscript is simply for design time visualization in the designer. Very promising and thanks for opening it up!
The text was updated successfully, but these errors were encountered: