If you then restart Alfresco, the Alfresco Explorer client will use this PreviewURIService instance to resolve Web Project preview servers. In this case, it will redirect preview requests to the URI defined by studioURI.
In this way, users can work on Surf objects via AVM CIFS, FTP or what have you and then instantly preview their Surf site against Web Studio.
Web Studio will still offer in-context overlays and all that fun stuff, however, the primary benefit it offers is that it will automatically switch sites and render back whichever site was requested - all directly from WCM in Alfresco Explorer.
Note: This is a very basic implementation of this service. It will be changed in the future to allow for things like dynamic switching of preview servers based on Web Project type. That said, it is useful to try out for purposes of exploring the capability.
Inside Web Studio, you will find a file called web-studio-config.xml which defines configuration properties for the Web Studio application. These settings can be customized to suite your needs.
That said, it is not recommended that you make changes to this file. Rather, we recommend that you introduce a new file called web-studio-config-custom.xml and drop it into your /shared/classes/alfresco/web-extension folder.
By switching to development mode, Web Studio will not use its prearranged, minimized JS file and will instead load all of the original JS files by hand. This makes things a good bit slower but also allows you the ability to tweak and play with the source files.
To switch into development mode, you can simply provide the following block inside of the WebFramework condition block.
We would like to make Web Studio as extensible as possible. If you have any feedback on new or improved hook points or on ways by which the product could be improved, please drop us a note on the forums!