browserlaunch2-development Mailing List for BrowserLauncher2

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I'm happy to report that the problem was with the path, not the
application.  The file simply didn't exist.  Carry on and thanks for the
great product!

rk

Trying out BrowserLaunch2 for my own (open-source) application.  This
project definitely fills a needed gap!

Running under MacOS, I find that the com.apple.mrj.MRJFileUtils.openURL()
method does nothing but write a message to my console.  To wit:

007-05-26 06:17:44.008 java[2505] LSOpenFromURLSpec() returned -43 for
application (null) path <...>

Known problem?  I would guess that it's the "application (null)" part that's
the cause of the problem.  I get the same result whether I set my default
browser to Opera or Firefox.  I gather that LSOpenFromURLSpec is a native
library function.  The docs seem to indicate that you can specify the
desired application explicitly, but I can't see that this is surfaced in the
Java API.

Thanks for your efforts and any help you can offer.

Rodney
rk

Hi,

I've added logging code to the unix/linux and windows code. Someone else 
needs to add logging to the Mac code. The logging works very well in 
conjunction with the test application.

I think I've also fixed the problem with windows XP. We were leaving out 
the "" argument. Apparently Windows interprets the first argument in 
quotes as the title for the command prompt window.

I think we're ready for another release.

Jeff

Hi,

Is anyone still there?

I've updated the test app to display logging information in the debug 
window. That should help with testing. I hope. You can also configure 
the debugging level from the interface. All the code is checked in.

Does anyone have any ideas on the bug that was logged? I don't have 
access to a Windows XP 2002, SP2 machine.

"Using RC1, get a command window with URL as title

When I attempt to open a URL using the RC1 release on
Windows XP 2002, SP2 with IE as default browser or with
FireFox as default browser I get a command window
(prompt) with a title of the url e.g., "sf.net" instead
of a browser window."

I guess we should add some logging to our browser launcher code. Any 
ideas on the best strategy for that?

Any ideas on when to do a new release?

I'm thinking after we add the logging code would be a good time for an 
rc2 release.

Later,
Jeff

Hi,

Did anyone see the new bug report logged on SourceForge? I just noticed 
it this morning.

    [ 1160468 ] Using RC1, get a command window with URL as title

Using RC1, get a command window with URL as title

When I attempt to open a URL using the RC1 release on
Windows XP 2002, SP2 with IE as default browser or with
FireFox as default browser I get a command window
(prompt) with a title of the url e.g., "sf.net" instead
of a browser window.

Code is as follows:

String urlString = "www.sf.net";
BrowserLauncherErrorHandler errorHandler = new
BrowserLauncherDefaultErrorHandler();
BrowserLauncherRunner runner = new
BrowserLauncherRunner(Util.getBrowserLauncher(),
urlString, errorHandler);
Thread launcherThread = new Thread(runner);
launcherThread.start();

I confirmed that this behavior is not consistent with
BrowserLauncher1.4b1:

try {

BrowserLauncher.openURL("http://www.redfin.com");
} catch (Exception e) {
throw new RuntimeException(e);
}

Opens the browser just fine (both FireFox and Explorer).
=================================================
Would the lack of a protocal make a difference?

I wish he would try this in the test application.

Later.
Jeff

Some minor news on logging: I upgraded the code to use WrapLog 1.1, 
which mostly means that logging messages include level, timestamp and 
thread.

Regards, Thomas.

On 22-Feb-2005, at 22:25, Thomas Aglassinger wrote:

> On 22-Feb-2005, at 14:01, Jeff Chapman wrote:
>
>> It appears the stats for sourceforge are broken. They seem to have 
>> been stuck on January 15 for weeks.
>
> Yeah, check the site status at <http://sourceforge.net/docs/A04/>, it 
> says:
>
> (  2005-01-27 10:29:20 - Statistics )   Project statistics data for 
> 2005 that is omitted will not be processed until launch of the new 
> statistics system. [...]

It seems that stats are about to come back, here's a quote from the 
current newsletter:

"The new SF.net stats system is also being rolled-out in March.
This new system provides live stats (as opposed to batched) for
downloads, page views, bandwidth, and many other services.
All stats have been enhanced, and you will be able to see
online graphs for many of the metrics, including a break down
per package per project.  It's impressive stuff, and I know
you'll find it very useful."

Thomas.

Hi,

I added simple logging to BrowserLauncherTestApp, but you can use it in 
any class. Basic pattern:

   import net.sf.wraplog.Logger;

   class MyClass {
     private static Logger logger = Logger.getLogger(MyClass.class);
     ...
     void blah() {
       logger.error("cannot blah: " + actual + " must be " + expected");
     }
   }

The current implementation just logs debug/info messages to System.out, 
and warning/error messages to System.err. But this is easy to change or 
extend, see <http://wraplog.sourceforge.net/> for details.

Thomas.

On 22-Feb-2005, at 14:01, Jeff Chapman wrote:

> It appears the stats for sourceforge are broken. They seem to have 
> been stuck on January 15 for weeks.

Yeah, check the site status at <http://sourceforge.net/docs/A04/>, it 
says:

(  2005-01-27 10:29:20 - Statistics )   Project statistics data for 
2005 that is omitted will not be processed until launch of the new 
statistics system. This data has been collected, but has not been 
processed for display. To ensure accuracy and reduce performance impact 
to users, these dates will be omitted until the new statistics system 
is launched. There is not currently a date set for the rollout of the 
new stats system. Please keep an eye here for that date when we release 
it.

Thomas,

I'm going to add browserlauncher to the freshmeat.net site. That should 
generate some more traffic to the project.

Jeff

Thanks Thomas. I suppose we should add support for Opera and Galeon as 
well.

It appears the stats for sourceforge are broken. They seem to have been 
stuck on January 15 for weeks.

Later,
Jeff

Hi,

I just committed a minor change to add support for Konqueror, the 
default browser for KDE based Linux distributions. I tested it with 
Mandrake 10.1 using KDE 3.2.

BTW, until now BrowserLauncher did not do *anything* if none of the 
supported browsers was installed. This is fixed now, it'll throw a 
BrowserLaunchingInitializingException.

Kind regards, Thomas.

I'll do a news item and maybe a freshmeat notice tomorrow.

Later,
Jeff

On 2-Feb-2005, at 19:14, Jeff Chapman wrote:

> Please take a look at the following webpages 
> (http://browserlaunch2.sourceforge.net/webpages/index.shtml). They're 
> not live and I haven't checked them in yet. Let me know if we need to 
> make changes.

Nice work!

But you should add the SourceForge logo as required, see 
<http://sourceforge.net/docman/display_doc.php?docid=790&group_id=1>.

One minor change: I just renamed BrowserLauncher2-all.zip to .jar (in 
the build.xml). Dunno where I missed that. Please update docs.shtml 
accordingly.

> I think we can do a release tomorrow of version 1.0rc1. I think we 
> need to get something out there for people to use and test.

I agree with that. AFAICT BL2 basically works, so it's time for some 
feedback.

> Sound good?

Go ahead,

Thomas.

Hi all,

Please take a look at the following webpages 
(http://browserlaunch2.sourceforge.net/webpages/index.shtml). They're 
not live and I haven't checked them in yet. Let me know if we need to 
make changes.

I think we can do a release tomorrow of version 1.0rc1. I think we need 
to get something out there for people to use and test.

We can then add Thomas's logging code in a subsequent release.

Sound good?

Jeff

I've released a tiny logging package called WrapLog at 
<http://wraplog.sourceforge.net/>. We should be able to integrate this 
into BrowserLauncher2.

The basic idea is that the library uses a generic logger interface 
which the client application developer can easily overwrite by 
inserting his own Logger class in the classpath. WrapLog already comes 
with wrappers for Log4j and java.util.logging, but also includes a 
simple logger that writes to System.out without the need for any 
libraries.

I decided to put it under a BSD-style license because developers 
probably will like to customize the code for their project. (I didn't 
bother to come up with a nice and flexible design; this is supposed to 
be lean and mean, there are already powerful but bulky logging packages 
around.)

That way, we can add the 2 relevant classes from WrapLog to the 
BrowserLauncher2 CVS, and include them in the BrowserLauncher2.jar. So 
client application developers need to add only one JAR to their 
classpath. I intend to provide a logger that logs warnings and errors 
toSystem.out/err. If client application developers don't like that, 
they can download the WrapLog.jar and create their own logger.

Kind regards,

Thomas.

On 1-Feb-2005, at 17:47, Jeff Chapman wrote:

> I'm putting together the web pages for the project. I want to include 
> a page that gives specific information on which OS's we are 
> supporting. Hopefully users will provide us with info on which one's 
> work. Most likely they will only tell us when something doesn't work.
>
> What level of detail do you think is appropriate for this page and 
> what OS's have you tested on at this point?

I guess the level of detail should be as curse as possible. In case of 
Mac OS X, it probably comes down to "10.2 or higher" because AFAIR Mac 
OS X 10.1 only supports JDK 1.3.

I've tested with Mac OS X, to be more specific (the "copy" button 
rocks):

Java Version: 1.4.2_05
Java Vendor: Apple Computer, Inc.
OS Name: Mac OS X
OS Version: 10.3.7

Thomas.

Hi,

First off, thanks Thomas for all your work.

I've spruced-up the test application. It now has a text area that 
captures info on the Java version being used and some information on the 
OS. Stacktraces are also captured and displayed in the text area (try 
entering a url without a protocol). I've added a copy button to allow 
for pasting the debug info into an email. The UI strings for the test 
app are now stored in a resource bundle for easier modification.  We can 
also i18n it someday if desired. I also made a small change to build.xml 
to facilitate copying the property file to the classes dir.

I'm putting together the web pages for the project. I want to include a 
page that gives specific information on which OS's we are supporting. 
Hopefully users will provide us with info on which one's work. Most 
likely they will only tell us when something doesn't work.

What level of detail do you think is appropriate for this page and what 
OS's have you tested on at this point?

Should we include information on which browsers are supported? This will 
likely be different for each platform.

Thanks,
Jeff

On 29-Jan-2005, at 5:14, Jeff Chapman wrote:

> What version number should we give to the first release?

1.0rc1?

>  I think we should do a release next week unless there are any 
> objections. I'm working on the webpages for the site. I will have 
> those done early next week.

Sounds good to me.

BTW, I cleaned up code for the the BrowserLauncherTestApp. It's a lot 
shorter and probably easier to understand. In particular, i did:

- simplify the exception handling
- simplify the application exit (no more listening for window events)
- changed GUI layout from absolute dimension to whatever the 
LayoutManager likes

Thomas.

What version number should we give to the first release? I think we 
should do a release next week unless there are any objections. I'm 
working on the webpages for the site. I will have those done early next 
week.

Jeff

On 25-Jan-2005, at 4:29, Jeff Chapman wrote:

> Here's the targets and properties file that I was using for 
> deployment. [...]

Ok, I applied it. Use

   ant build

to compile all classes, and

   ant deploy

to create the following archives:

- BrowserLauncher2.jar
- BrowserLauncher2-all.jar (I didn't use your name because it's not 
just the test, but also the source and the API documentation)

Thanks to your manifests, you can just double-click 
BrowserLauncher2-all.jar to run the test application.

Thomas.

Thanks Thomas,

Here's the targets and properties file that I was using for deployment.

    <target name="deployApp" depends="buildApp">
         <jar destfile="${deploy.dir}/BrowserLauncher2.jar"
            index="true"
            update="overwrite"
            manifest="${app.manifest}" >
            <fileset dir="${build.dir}" 
includes="edu/stanford/ejalbert/**" />
            <fileset file="${gnu.copying}" />
            <fileset file="${readme}" />
        </jar>
         <jar destfile="${deploy.dir}/BrowserLauncher2Test.jar"
            index="true"
            update="overwrite"
            manifest="${app.manifest.test}" >
            <fileset dir="${build.dir}" 
includes="edu/stanford/ejalbert/**" />
            <fileset file="${gnu.copying}" />
            <fileset file="${readme}" />
        </jar>
    </target>

-----------------------------

# build properties for BrowserLauncher project

src.dir=/home/jeffery/browserlauncher_stuff/source

build.dir=/home/jeffery/java_dev/classes
class.path=${build.dir}
optimize=on

deploy.dir=/home/jeffery/browserlauncher_stuff/release

app.manifest=/home/jeffery/browserlauncher_stuff/deployment/manifest.mf
app.manifest.test=/home/jeffery/browserlauncher_stuff/deployment/manifest.test.mf

gnu.copying=/home/jeffery/java_dev/gnu_stuff/lgpl/COPYING.txt
readme=/home/jeffery/browserlauncher_stuff/deployment/README.txt

--------------------------------------------------------

Thomas Aglassinger wrote:

> The CVS now contains a build.xml for ant. Right now, running
>
>   ant
>
> eventually yields two archives:
>
> - BrowserLauncher2.jar: a small JAR file containing only the *.class 
> files. This is intended to be included in (distributed) client 
> applications that use BrowserLauncher2.
>
> - BrowserLauncher2-all.zip: a "big" Zip archive again containing the 
> class files. Additionally, it includes the source and Javadoc API 
> documentation. This is intended to be used by developers that want to 
> develop applications that use BrowseLauncher2. They occasionally will 
> want to take a look at the API or source.
>
> Open issues:
>
> - The archives do not yet include COPYING.txt and stuff.
>
> - The archives do not yet include the MANIFEST.mf.
>
> Once these are addressed, we could make these archives available for 
> download.
>
> Any thoughts?
>
> Thomas.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Browserlaunch2-development mailing list
> Bro...@li...
> https://lists.sourceforge.net/lists/listinfo/browserlaunch2-development
>

The CVS now contains a build.xml for ant. Right now, running

   ant

eventually yields two archives:

- BrowserLauncher2.jar: a small JAR file containing only the *.class 
files. This is intended to be included in (distributed) client 
applications that use BrowserLauncher2.

- BrowserLauncher2-all.zip: a "big" Zip archive again containing the 
class files. Additionally, it includes the source and Javadoc API 
documentation. This is intended to be used by developers that want to 
develop applications that use BrowseLauncher2. They occasionally will 
want to take a look at the API or source.

Open issues:

- The archives do not yet include COPYING.txt and stuff.

- The archives do not yet include the MANIFEST.mf.

Once these are addressed, we could make these archives available for 
download.

Any thoughts?

Thomas.

The CVS now contains a .project and .classpath for eclipse 3.0.

Have fun, Thomas.

2005	Jan (6)	Feb (11)	Mar (3)	Apr (1)	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2007	Jan	Feb	Mar	Apr	May (2)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

browserlaunch2-development Mailing List for BrowserLauncher2

browserlaunch2-development — List for developers.