Consolidate Container and Loader about lu HOT 5 CLOSED

"If it is a URL the content should be a-synced in and then an Iframe should be created " -- if we're AJAXing the content in from the URL, why do we need an iFrame?

from lu.

The use cases for Loader were:

Loading content or in a tip (Mini profile)
Loading content in an accordion panel
Loading content in a tab.
Loading content in a dialog.

The above should say "If it is a URL from the same domain the content should be a-synced in otherwise, an Iframe should be created..."

I was probably hopped up on pain killer at the time of writing the above ...

In truth, we should probably give the option to force the content into an iframe even if the url originated from the same domain.

Container will be useful for other controls to extend or use. IMO because the events on other controls vary container should not inherently respond to any events. Rather, Controls like Dialog should respond to a close event ant call a close method on container. Likewise Accordion could respond to an expand event, get the content height of the containers content and then expand the container.

from lu.

It sounds to me like Loader should inherit from Container -- is that what you're thinking? And Tip could inherit from Loader as well.

I don't recall why we originally had Container create an internal instance of Loader, instead of going the inheritance route...?

I agree on the iframe option, too.

from lu.

Container & Loader are mostly done. Examples in Primer (also for Tip). Still need to create unit tests w/Kiro's help....

from lu.

Nice!

from lu.