Flash for Linux, libmozembed progress
It would be nice to have flash.
Don’t expect a release worthy edition of a new Flash for Linux until 2007 from Adobe/Macromedia. A developer with Adobe/Macormedia blogged that they are working on it. I’m not very impressed. They said a new alpha would be released very soon but they started saying that over 1 year ago. (Yes I understand that Flash 8 introduced a homemade GC so it made it hard to port and why its been hard to move to x86_64, but yeeesh).
libmozembed progress
libmozembed is getting closer and closer. I’m finishing up on a bunch of tedious parts right now. It’s working, and I should have some rough screenshots soon when I remove a bunch of inline stuff and make it re-sizable and able to move from location to location. Right now it freezes right after the first page load because of some workarounds I was using to be able to see what I was doing before while building up the underlying scaffolding that makes everything work. Now its just the tedious task of removing everything like that and remove all those annoying printfs (poor mans debug, since most of the dump stacks I get via pinvoke on the unamanged side sort of stink). Should be commit ready very soon to start alpha testing the Mozilla control for System.Windows.Forms/Managed.Windows.Forms control (not the IE API compatible version yet). I’m guestamating next week before its ready for that.
Tags: Mono & .NET, Personal
June 1st, 2006 at 1:16 am
Wonderful work! BTW, how will we distinguish the moz version from the ie version?
June 1st, 2006 at 2:37 am
thats a good question… one way would be via reflection into the inside the component to check to see if one my internal types exist. Its great but that would work without breaking ABI. I might be able to provide something else (maybe invoke something and getting a predicted variable back (like on init, the title tag will be “about:mozilla” until it chages pages unlike IE, which defaults to “about:blank”).
June 1st, 2006 at 4:13 am
How about exposing a property that exposes the UserAgent? That was the purpose wasn’t it?
June 1st, 2006 at 4:59 am
part of the problem is that microsoft’s api doesn’t expose the useragent as something in the api.
June 1st, 2006 at 7:05 am
Not sure, but can\’t you access the html code and run javascript? If so you can easly check the browser and version creating a custom page and invoking a javascript inside it.
June 1st, 2006 at 11:32 am
true. i guess we can cross that bridge when we came to it.