Hi again,
somewhat off-topic, but I think we should remove the red/orange
coloring of the letters "Jab" in JabRef on the front page. I think
this made more sense in an earlier design of the home page.
--
Morten
-
This SF.n
On 11/09/2007, Kolja Brix <[EMAIL PROTECTED]> wrote:
> Dear Jabref developers,
>
> > Perhaps we should do as Christopher suggests, and add prominent
> > "Download stable version" and "Download beta version" links on the top
> > of the main page.
>
> a few moments ago, I added two download buttons t
Dear Jabref developers,
> Perhaps we should do as Christopher suggests, and add prominent
> "Download stable version" and "Download beta version" links on the top
> of the main page.
a few moments ago, I added two download buttons to the main webpage. I hope
you like the design.
--
Bye,
Kolj
2007/9/11, Morten Omholt Alver <[EMAIL PROTECTED]>:
> > > Our biggest problem is perhaps that users download 2.3 beta without
> > > realizing that it is a beta version.
> > Exactly. Maybe the first button on the SourceForge.net download page should
> > be
> > a link to the files for JabRef 2.2 adv
On 10/09/2007, Christopher Oezbek <[EMAIL PROTECTED]> wrote:
> > We should include this check already in the 2.3
> > version, since it requires Java 1.5.
>
> Sure! You only need the class JabRefMain from net.sf.jabref and the
> modified compile target in the build.xml.
> Running from the Jar should
On 11/09/2007, Kolja Brix <[EMAIL PROTECTED]> wrote:
> Dear Morten!
>
> > The current version of JabRef is 2.2, and it requires Java 1.4.2. The
> > current beta version requires version 1.5, but I would rather
> > recommend 1.6.
> Yes, ok. Why exactly do we need version 1.5 or higher in the beta ve
Hi Kolja, Hi Guys,
> Exactly. Maybe the first button on the SourceForge.net download page
> should be a link to the files for JabRef 2.2 advertised as 'latest
> stable version'
> followed by a link to the files for JabRef 2.3 beta 2 advertised as
> 'current beta version'. Can we do this?
My
Dear Morten!
> The current version of JabRef is 2.2, and it requires Java 1.4.2. The
> current beta version requires version 1.5, but I would rather
> recommend 1.6.
Yes, ok. Why exactly do we need version 1.5 or higher in the beta versions?
What is the advantage of JRE version 1.6 over 1.5? Is i
Dear Christopher!
> Okay, I just implemented a new main class (called JabRefMain), which
> checks for Java 1.5 and prints warnings if a wrong JRE is found. It still
> tries to start JabRef nevertheless, just in case afterwards. I also
> modified the build-file that this new Main file is compiled u
> We should include this check already in the 2.3
> version, since it requires Java 1.5.
Sure! You only need the class JabRefMain from net.sf.jabref and the
modified compile target in the build.xml.
Running from the Jar should then perform the checks before starting JabRef
itself.
Christopher
Christopher,
great work/initiative! We should include this check already in the 2.3
version, since it requires Java 1.5.
Morten
On 10/09/2007, Christopher Oezbek <[EMAIL PROTECTED]> wrote:
> Thanks Ambrogio!
>
> I fixed this problem and improved the warning message. Please give it
> another sp
Thanks Ambrogio!
I fixed this problem and improved the warning message. Please give it
another spin.
Can somebody also try with a different JRE from Classpath/GCJ, Kaffe or
Blackdown?
Thanks,
Christopher
@Egon: Have a look at
https://jabref.svn.sourceforge.net/svnroot/jabref/trunk/jabre
Okay, I just implemented a new main class (called JabRefMain), which
checks for Java 1.5 and prints warnings if a wrong JRE is found. It still
tries to start JabRef nevertheless, just in case afterwards. I also
modified the build-file that this new Main file is compiled using Java 1.4
and n
> in the last weeks it is often asked, which is the minimum requirement on the
> Java Runtime Environment to run the current version of JabRef. We recommend
> Sun JRE version 1.5, right?
The current version of JabRef is 2.2, and it requires Java 1.4.2. The
current beta version requires version 1.5
Hi Kolja,
On 9/9/07, Kolja Brix <[EMAIL PROTECTED]> wrote:
> Why is it not possible to check for the JRE version number in the very
> beginning of the program using System.getProperty("java.version"); and give a
> correct error message when the JRE is too old.
One problem is that a 1.4 JVM will n
15 matches
Mail list logo
