Do you by chance have your widget UI drawn through OWF.ready? That wouldn’t be executed outside of OWF – you’d want to make a decision to execute based on Ozone.util.isRunningInOWF – if false, then run the same code you’d otherwise have executed through OWF.ready.
Beyond that, I’d make use of Firebug (good to see it or Chrome developer tools being used) to see what things get loaded and what network calls get made in the OWF environment versus the non-OWF to see where the issue is.
Tina Coleman
NEXTCENTURYCORPORATION
7075 Samuel Morse Drive, Suite 250
| Columbia, MD 21046
m 443.545.3100
|
f 443.285.0799
|www.nextcentury.com