Yes. Because that is the way the swf console works. It's a stand-
alone app. It is pretty useless to have the console break if your LFC
is broken (or changes its API).
When you are testing the console, are you testing the 'frozen' console
that is checked in, or are you just trying to run the console as an
app? It may be that the frozen console is not compatible with the
current LFC, and perhaps someone updated the app but didn't know they
had to rebuild the frozen version?
On 2008-02-11, at 20:29 EST, Henry Minsky wrote:
But the embedDHTML script looks like it still loads the DHTML LFC
separately I guess. What's weird is that the console app runs OK in
DHTML in the main app iframe, but doesn't seem to load in the console
div area.
Hmm, that seems like a bug, we should have the console
keep it's own frozen copy of the LFC (if it's in its own iframe, it is
isolated from the main app's LFC, right?)
On Mon, Feb 11, 2008 at 6:53 PM, P T Withington <[EMAIL PROTECTED]> wrote:
I thought the console was compiled as a solo app and checked in to
insulate it from any lossage in the LFC?
Are you recompiling the console app by hand?
(Max really should have created a build.xml that had a target for
doing this. I actually don't know the recipe, but I think you just
call lzc and move the output to the right spot.)
On 2008-02-11, at 18:46 EST, Henry Minsky wrote:
I can compile and run the dev console app by itself, but the
LzDHTMLEmbed script that is embedding it in its position at the
bottom
of the screen
seems to be failing to load the DHTML LFC.
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
