Hey Fuser Crew,
Been venturing with Fuse’s DataToResource system. Fantastic, but ever since the deprecation of <Style>, Resources can no longer be ux:Included and thus it cannot be seperated / resolved from the element who’s looking for the resource’s children and parents.
Would love to see a way of seperating the Resources into own ux file again.
For Reference, please refer to https://www.fusetools.com/examples/swipe-gesture-reveal and head over to the Resources.ux file and replace the deprecated <Style> tags.
Cheers,
Elizabeth
Hi! You can use a panel, like in this example: https://www.fusetools.com/examples/signup-concept
Or the separate container that Kristian provided here
Hope this helps. 
Hi Remi!
Thanks for the reply back.
Hmm … then the above issue seems to only be related to the <FileImageSource> resources.
Because I have tried to use <Panel> in replace of <Style> and the resources does not get resolved. 
This could be a minimal test case for the crew:
For Reference, please refer to https://www.fusetools.com/examples/swipe-gesture-reveal and head over to the Resources.ux file and replace the deprecated <Style> tags.
You are right the other types of resources work though.
Cheers,
Elizabeth
Hi Elizabeth!
You are right that putting resources defined with ux:Key in their own files is not possible after the removal of Style. I posted the code for an uno-component that lets you do this, here: https://www.fusetools.com/community/forums/howto_discussions/resources_in_their_own_file_replacement_for_style?page=1&highlight=fbcb3632-2cc5-452a-9a93-66997c44316a#post-fbcb3632-2cc5-452a-9a93-66997c44316a
I’ll see if it a good enough solution to go into fuselibs in an upcoming release. This case should somehow be properly covered eventually.
I hope this helps in the meantime
Hi Kristian!
Thanks. That’ll work great until a solution gets implementated into fuselibs.
Cheers,
Elizabeth
