I think it is more a problem of the lz.embed (JavaScript Code). I don't think it has something to do with solo or not in general.
However my status of the HTML component is that: - It is not possible to catch clicks in the iFrame / HTML-component - It is not possible to catch changes of the iFrame / HTML-component - It is forbidden by browser's cross-site-scripting policy to read or set the URL of the iFrame Besides that it seemed to me that Firefox + Windows has some glitches with the z-Layer overlay of HTML content over an Flash Applet. However this might be solved already. But the first 3 points are still valid. The only thing that you _could_ do with it is that the moderator enters an URL and everybody else can by synced. However as soon as the moderator clicks into the HTML site => no even will be broadcasted. Also I don't know any possibility to prevent that the users just browse somewhere else in that mini browser window. Sebastian 2012/3/19 Pete Oakloan <[email protected]> > Hi Alexei, > > it boils down to me trying to use the openlaszlo <html> tag in a <view>, > replacing the whiteboard. > however, testing this tag in a minimal environment (3-line lzx file > actually) i found out there are problems in SOLO mode. > it works flawlessly in proxied, though. > > one possibility would be to try and compile a single component to - say - > dhtml. but as far as i can tell it's not possible > to give different runtime-targets to different parts of OM. > > any ideas? > > error log is not sufficient i'm afraid. my test.lzx works proxied with > ?lzr=swf8, however stays blank when compiled to swf8 via cli > and then tested in browser. > > i think it's some kind of deep openlaszlo problem. unfortunately, the > community over there seems kind of... inactive. > the <html> tag in SOLO mode has been an issue since 2007 (or openlaszlo > 4.0.5 - we are 4.9.0 now). > > kind regards, > pete > > Am 19. März 2012 14:46 schrieb Alexei Fedotov <[email protected]>: > > > Hi Pete, > > that was possible. > > > > Now Openmeetings does not contain the whole OpenLaszlo distribution > > requied for running in proxied mode, > > but the better clue should be the corresponding error log. > > > > Why would you need this? > > > > -- > > With best regards / с наилучшими пожеланиями, > > Alexei Fedotov / Алексей Федотов, > > http://dataved.ru/ > > +7 916 562 8095 > > > > > > > > On Mon, Mar 19, 2012 at 5:43 PM, Pete Oakloan > > <[email protected]> wrote: > > > Hi everyone, > > > > > > what are the chances of getting OM to run in proxied mode? > > > > > > I am trying with the source-code revision that is currently packaged on > > the > > > demo-server and did the following: > > > > > > - deploy openlaszlo on red5 > > > - add /*.lzx handle & servlet to openmeetings web.xml > > > - changed build.xml so that OM *.lzx files are copied to red5 om > webapps > > dir > > > > > > however - it doesn't work as in no clue why. where to start? is it > viable > > > anyhow? > > > > > > kind regards, > > > pete > > > -- Sebastian Wagner http://www.openmeetings.de http://incubator.apache.org/openmeetings/ http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
