On Thu, Aug 27, 2009 at 5:32 AM, brett.wooldridge < brett.wooldri...@gmail.com> wrote:
> While we're on the topic, what is the state of the truck with respect > to OOPHM and Safari? I'm running off the trunk from about a month ago > (and it's usable), but I've seen lots of OOPHM related changes go in > as of late. If I update to the head, will I be broken? Will my > existing Safari plugin function or do I need a new one (and is it the > current download from the wiki page)? > The download from the wiki page is still the old one until we get done with the changes (as rebuilding all of them is a lot of work), and it will continue to function with current trunk. However, the UI won't benefit from the changes made, as the old plugin does not send a session key or the top level URL used to identify particular sessions/modules. That means you will basically see every module instance in one browser (if you have multiple modules) as a separate session containing one module, and all those sessions will be grouped into a single tab. You can also build the plugin and test it yourself (shortly it will have the final plugin identifier so you can have both the old and the new one installed [make sure to only have one enabled at a time] so you can try it out without risk -- before then you will have to re-install from the wiki page if you want to switch back). To build from trunk, make sure you have plugin-sdks checked out parallel to where you have trunk checked out with svn co http://google-web-toolkit.googlecode.com/svn/plugin-sdks . in the same directory where your trunk is, then in plugins/xpcom just type make BROWSER=ff35 (or ff3, or ff2 depending on what browser you want to use) and install the resulting oophm-xpcom-ff*.xpi by browsing to the prebuilt directory. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
