AppLogic GUI & Firefox on Mac OS X

[tmart]

I've had problems ( :confused: ) both AppLogic 2.1.1 and 2.3.9b using Firefox (v2.* and v3.*) on Mac OS X. I'm wondering if it's just my machine(s) and how I have Firefox configured.

Safari seems to be altogether unsupported.

I've seen the following problems:

1) about 75% of the time, the GUI only partially loads objects. It's like some cache of objects needed by the AppLogic GUI get recycled before their time. For example, when I double-click on an instance in the GUI to view properties, sometimes not all tabs show up; other times, the tabs show up with no content; other times some field labels show up but the fields are not editable. If I am very patient and try 3,4 or 5 times, eventually the property panel (for example) will fully load. This issue creates a real barrier to using the AppLogic GUI on a Mac.

2) during operations that are not instantaneous, it appears that Firefox times-out and I must repeatedly click "Continue executing script" instead of "Cancel." This happens during branching, volume creation, move back to catalog, etc. -- I looked to see if there was a way to increase timeout, but I didn't see any. This is only a nuisance, but it would be nice to find a way to fix it.

[PeterNic]

Safari seems to be altogether unsupported.

Safari is not yet supported. As it is adding more and more Ajax-related features, I expect we'll be able to add support for it.


I've seen the following problems:

1) about 75% of the time, the GUI only partially loads objects. It's like some cache of objects needed by the AppLogic GUI get recycled before their time. For example, when I double-click on an instance in the GUI to view properties, sometimes not all tabs show up; other times, the tabs show up with no content; other times some field labels show up but the fields are not editable. If I am very patient and try 3,4 or 5 times, eventually the property panel (for example) will fully load. This issue creates a real barrier to using the AppLogic GUI on a Mac.

That shouldn't be happening; I have seen similar behavior on really bad connections (e.g., overloaded wireless during conferences) and usually you also get a message box indicating a connection error. Have you looked at connection loss stats and latency from your machine to the grid?

If that's not the issue, I'll ask to set up some time with our engineers to look at the behavior over webex with you.


2) during operations that are not instantaneous, it appears that Firefox times-out and I must repeatedly click "Continue executing script" instead of "Cancel." This happens during branching, volume creation, move back to catalog, etc. -- I looked to see if there was a way to increase timeout, but I didn't see any. This is only a nuisance, but it would be nice to find a way to fix it.

The last time we looked, there was no way to remove this box -- anything that takes longer than the FF-mandated "script execution time" brought that message up. In the upcoming 2.4 beta release, we have changed the way all long operations work, added progress bar and a cancel button. I believe this change also removes the FF warning message; I'll check with the team during QA.

Best regards,
-- Peter