Hi Matt.
You'd actually handle this at the firefox level, but in a non-obvious
manner as the seems mozilla gave up on the -maximize option a long time ago.
Are you using a shared profile or letting it create one on the fly?
Either way, what you need make the change to whatever localstore.rdf you
are using. "chrome://browser/content/browser.xul#main-window" is what
controls the size and placement of the main browser window.
So change it to whatever your biggest possible screen is, it will only
start as large as the actual x canvas running, so you can cover all
possibilities by setting it to a high resolution.
<RDF:Description
RDF:about="chrome://browser/content/browser.xul#main-window"
width="5000"
height="3000"
screenX="0"
screenY="0"
sizemode="maximized" />
If you are letting it create a profile on the on the fly, you'd add this
section to <Firefox install directory>/defaults/profile/localstore.rdf
(somewhere in between the initial open and close RDF tags)
If using a existing profile (like one in the prototypes directory), just
edit the existing localstore.rdf in ~.mozilla/firefox/*.default to
reflect the above.
On 7/26/11 10:53 AM, Matthew Arensberg Wieben wrote:
Off the top of your head, do you know if you can get metacity to maximize
firefox after it's launched? I've been using fvwm2 to do what you describe
below, but no matter how much I hack the fvwm2 config file, firefox doesn't
seem to respond well to that WM's way of doing things. I *think* I was able to
get some apps to auto-maximize in fvwm2 but it's been months since I last tried
it.
Thanks,
Matt
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Craig Bender
Sent: Tuesday, July 26, 2011 8:07 AM
To: SunRay-Users mailing list
Subject: [SunRay-Users] Kiosk App Tip
Ever publish a kiosk app like firefox or a terminal for troubleshooting?
Hate that you don't have windowing manager due to pop-unders or modal
mozilla messages?
Did you know you can just start metacity and not have to resort to using
something like the locked down JDS app?
Just start metacity before what ever your kiosk app calls and then kill
it after.
Once you do the above, you might find cases where a minimized app seems
to have disappeared. It hasn't but on some clients (like iPad) it's a
bit tricky to do an alt-tab. Best to just remove the minimize button
all together from the running instance of metacity.
Example of both tips together:
#!/bin/sh
# Get rid of the minimize button on the windowing manager
/usr/bin/gconftool-2 \
--type string \
--set /apps/metacity/general/button_layout menu:maximize,close
# Start a window manager so firefox doesn't get stuck with modal windows
under the browser
/usr/bin/metacity&
# Start Firefox
/opt/firefox/firefox
# Cleanup the window manager so Kiosk exits after firefox closes
pkill -9 $USER metacity
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
