Actually, can I even compile swc files from flex using framework components like httpRequest and then load them as RSL ?
Seems like I can make my custom component include it in a library project, export it as swc and include that swc as RSL in my actual Flex project.
But I'm still not sure which approach is better, using RSL for this case or just a module? Does it make any difference ?
Also another question that rises in my mind is that if using RSL which class should I extend from, when this component will have no visual representation but should be able to do httpRequests and load modules/applications?
Message was edited by: FM_Flame
1 person found this helpful
I didn't understand the question. I would recommend packaging components as
SWCs. Otherwise, the user has to understand modules or sub-apps.
Thanks, that kinda pointed me in building the component as swc since it basicly serves the same purpose as if it was a module but you can choose to merge it in code or load it as RSL. Also you don't have to write code to load it as if it was a module.
In my case the structure of the website you build would kinda require the knowledge of modules and loading sub apps if you want to use all the system features so I guess I could have done it with module too, but seems like the swc approach is more convenient.
P.S. I extended group.