SketchAssetConverter migrate web server to executable CLI about parabeac_core HOT 3 CLOSED

Thanks for reply @x64Eddie :) I understand your thought. The limitation is "SAC requires an OSX". SAC is using a web server has no problem at this time. I focus on generating code better. When need to change the webserver to CLI, I dive in this issue

from parabeac_core.

Yeah, you have a point of running SketchAssetConverter(SAC) as CLI locally, good call👍🏼 . It was left as a web server due to time constraints.
However, not sure if you agree or disagree with running SAC as a web server in the cloud but ill share my opinion on why it should, we can then discuss the pros and cons!🤘 When Parabeac does run in the cloud, SAC would run as a web server, we don't want to couple Parabeac Core to SAC. There are two reasons for this. First, SAC requires an OSX environment to run. This is the case because it makes use of the Sketchtool. If SAC was coupled to Parabeac Core, it would inherently force Parabeac Core to run in an OSX environment as well. The final reason is that SAC is going to be doing more than just converting SketchVectors to Image, a set of responsibilities than don't align with Parabeac Core's responsibilities. 🤔

from parabeac_core.

Closing this issue out since Windows cannot run Sketch Tool.

from parabeac_core.