Just some idea:
If someone would want to load the static assets (js + css) from a different/external location this is what would make this possible easily (in a CDN push scenario - NOT needed for CDN pull):
change assets/ to wporg-assets/ (wp_deploy should support that, right?!)
move css/ and js/ to (now empty) assets/ folder
provide a filter + function to change the "assets urls" (in the main file)
<?php
public function get_url() {
return esc_url( apply_filters( 'black_studio_tinymce_url', plugins_url( '/', __FILE__ ) ) );
} // End get_url()
public function get_assets_url() {
return esc_url( apply_filters( 'black_studio_tinymce_assets_url', $this->get_url() . 'assets/' ) );
} // End get_assets_url()
use these functions to generate the urls for enqueuing the files like:
The idea is good, but I think that in a CDN push scenario, it would be better to use a WP level filter instead of a plugin level filter. In particular script_loader_src and style_loader_src should do the trick.
Just some idea: If someone would want to load the static assets (js + css) from a different/external location this is what would make this possible easily (in a CDN push scenario - NOT needed for CDN pull):
assets/
towporg-assets/
(wp_deploy should support that, right?!)css/
andjs/
to (now empty)assets/
folder