On 22 April 2010 23:28, Bob Jolliffe bobjolli...@gmail.com wrote:
On 22 April 2010 19:35, Jason Pickering jason.p.picker...@gmail.com
wrote:
I think it should probably be a blueprint and I think it is a good idea.
It is certainly a problem on many machines I have encounterd in the
I somewhat agree with Bob, but I also see good reasons why packaging a
browser is a good idea. There seems to be pretty wide variation
between different browsers, and while it is a good idea to support
many different ones, it is also a lot of work. If we could focus on
being sure that all the
Something like this perhaps modified a bit to launch which every
browser would be included as part of the install
private void LaunchBrowser (String msBrowser,String msURL) throws IOException
{
if(msBrowser.equalsIgnoreCase(iexplore)){
Runtime.getRuntime().exec(C:/Program Files/Internet
On 23 April 2010 09:04, Bob Jolliffe bobjolli...@gmail.com wrote:
On 23 April 2010 08:54, Jason Pickering jason.p.picker...@gmail.com wrote:
I somewhat agree with Bob, but I also see good reasons why packaging a
browser is a good idea. There seems to be pretty wide variation
between different
Including the browser as part of the install is trivial. Making it
launch, without making it the default browser, is the issue really we
are discussing and that will require modification to the DHIS2 tray
app.
I have currently three different installers in trunk. 1) Windows
bare-bones installer
I was more thing of the unzip and run package.
If there is a folder DHIS2Live/firefox-portable/ I thought we could simply
run DHIS in this specific browser with a command on the form:
portable-firefox/firefox.exe http://localhost:8080/dhis;
Ola
--
On 23 April 2010 10:48, Jason Pickering
I've got an even simpler suggestion. Why not get the tray app to
simply try and exec firefox first (in the hope that it is installed
and in the path). If that fails it can try chrome and if that fails
open with default browser.
From the packaging perspective (and I think packaging is a slightly
Jolliffebobjolli...@gmail.com
Cc: DHIS 2 developersdhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] Site Specific Browser included with DHIS2 Live?
Yeah, the problem is, how do you know where Chrome/FireFox/etc is?
Sounds like we need to read the registry, which sounds even more
complicated.
My
-
From: Jason Pickering jason.p.picker...@gmail.com
Date: Fri, 23 Apr 2010 11:37:53
To: Bob Jolliffebobjolli...@gmail.com
Cc: DHIS 2 developersdhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] Site Specific Browser included with DHIS2 Live?
Yeah, the problem is, how do you know where
...@gmail.com
Date: Fri, 23 Apr 2010 11:37:53
To: Bob Jolliffebobjolli...@gmail.com
Cc: DHIS 2 developersdhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] Site Specific Browser included with DHIS2 Live?
Yeah, the problem is, how do you know where Chrome/FireFox/etc is?
Sounds like we
On Fri, Apr 23, 2010 at 1:30 PM, Knut Staring knu...@gmail.com wrote:
On Fri, Apr 23, 2010 at 12:39 PM, Saptarshi Purkayastha
sun...@gmail.com wrote:
I believe making it cross-browser is better than packaging a browser. Didn't
EU tell MS that browser bundling by a majority player is wrong. ;)
from my BlackBerry®
-Original Message-
From: Jason Pickering jason.p.picker...@gmail.com
Date: Fri, 23 Apr 2010 11:37:53
To: Bob Jolliffebobjolli...@gmail.com
Cc: DHIS 2 developersdhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] Site Specific Browser included with DHIS2 Live
On Fri, Apr 23, 2010 at 2:59 PM, Bob Jolliffe bobjolli...@gmail.com wrote:
wot's an SSB?
Site Specific Browser:
Prism http://prism.mozillalabs.com/
Fluid http://fluidapp.com/
http://stackoverflow.com/questions/1842277/chrome-application-shortcuts-mozilla-prism-installer
These are both quite interesting projects, and really point to a
complete rewrite of the GUI, reductio absurdum, meaining a webapp that
looks like a Desktop app. Something to keep in mind for future
releases.
I am pretty much convinced however that packaging a modern browser
with the installer
On Fri, Apr 23, 2010 at 8:11 PM, Jason Pickering
jason.p.picker...@gmail.com wrote:
These are both quite interesting projects, and really point to a
complete rewrite of the GUI, reductio absurdum, meaining a webapp that
looks like a Desktop app. Something to keep in mind for future
releases.
Given that DHIS2 runs best in Chrome (especially the Mapping module),
and also ok in Firefox, it might be a good idea to make sure people
have access to one of these browsers.
One way to do that is to package things with Prism (Firefox) or Chrome
(or Fluid for Mac http://fluidapp.com/)
I think it should probably be a blueprint and I think it is a good idea.
It is certainly a problem on many machines I have encounterd in the
field. We need to install FireFox, Chrome, Opera or something, and
ideally make it the default browser. This seems to be a good idea to
me, but can seem a
On 22 April 2010 19:35, Jason Pickering jason.p.picker...@gmail.com wrote:
I think it should probably be a blueprint and I think it is a good idea.
It is certainly a problem on many machines I have encounterd in the
field. We need to install FireFox, Chrome, Opera or something, and
ideally
18 matches
Mail list logo
