Shared assets dilemna

1

I’m trying to analyze the pros/cons of different ways of handling shared assets and am hoping for feedback on the best option or perhaps an option I haven’t yet thought of…

  1. create gui fla with assets set to export for sharing
    import the needed assets into the destination flas

    PROS
    single gui where assets can be managed

CONS
need to update/republish destination flas every time a shared asset is updated

  1. create an swc and link to it in the destinations

PROS
do not need to update destinations
single gui where assets can be managed

CONS
must load entire gui instead of just the needed gui items

Is there any way to get the best of both worlds here? It would be very cumbersome to republish all the dependent flas every time a gui asset is updated, but I don’t want to load the entire gui every time an asset is used from it…

Any help appreciated! Thanks.

Jenny