Impending removal of OSX export functionality

Dave Carpeneto

Hi all - We are looking to remove OSX export functionality from CSIDE, since we cannot see where these exports may in fact be imported. 

Prior to doing this however we'd like feedback from the end users. Hence: this forum post. 

Please do let us know if this is functionality you still depend on in any way by replying to this post.

David Henshaw

Hi Dave - don't think we've ever used OSX export format.

I will use your post as a opportunity to voice some desires though....

1) When doing a build, it would be handy to have the build automatically copy the supporting files (HTML, help, adminhelp, ojlib, weblingo, support assets etc) to the module directory.

2) Even better than above, the ability to build a the full module inclusive all ospaces and files/directories form a command line. I see on roadmap there's mention of "obuild" which I'm holding hope will address this.....it can't come soon enough.

3) Extending 3 above - the ability for a completely command line or other automated build process that can be incorporated/used in a CI/CD context, inclusive of building the OSpaces and SmartView bundles. Right now as far as I can see, one has to compile and assemble the module by hand, remembering to build the SmartView components and manually copy into the final module. Argh.

I heard on the grapevine that a new project manager for CSIDE was potentially coming on to the team........curious to know if that's occurred?