It would be really useful to have the option to be able to install components of FastForward without large sections of the product not working.
We would like to be able to install a ‘clean’ version on our production machine and then pick and chose which components of FastForward would be useful to move over, however, after a lot of trying we have discovered that you loose a lot of the sailable features of Rhythmyx if you don’t install it with FastForward.
I would suggest that if the product is reliant on FastForward to such an extent it is worth packaging it up to allow admins to install the components from it that they wish, rather than the whole lot.
I agree with Georgina’s observations. To look at it another way, actually, it would help me if Percussion treated Fast Forward components as an integral part of Rhythmyx, and then gave instructions on how to modify or disable those components. It would make the relationship between FF and Rx less nebulous to boldly state that these components are necessary to avoid a steeper learning curve and extra development, but that developers are welcome to make changes to their installation if they want. Sometimes I feel like I moved into a house before the carpenters were finished.
The upcoming “barracuda” release should go a long way to addressing this one. Stay tuned.