Also, it will be potentially much slower. ) would need to be implemented by Enscape developers, which will take away developer time from core Enscape features. Every feature (for example batch management, test libraries. If the custom assets are exclusively hosted on the cloud, that will not be possible and we will be limited to the feature set provided by Enscape. have multiple variations of the library, write small applications to automate tasks (that we'd be happy to share with the community here), etc. That will allow us to go in and tweak files ourselves.
With that, I mean a non-cloud based solution so that we can host our assets locally. Yes I would appreciate that as well But more importantly, I would appreciate an open implementation for custom assets.
0 kommentar(er)
