Menu
▾
▴
jprojecttimer-developers — Information for developers of JProjectTimer
You can subscribe to this list here.
| 2002 |
Jan
(16) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Christian G. [M. Mitch] <mi...@mi...> - 2003-02-08 17:48:14
|
Hi there!
I've just finished a Debian package of JProjectTimer.
It is available here:
http://prdownloads.sourceforge.net/jprojecttimer/jprojecttimer_0.0.7-2_all.deb?download
http://www.h.shuttle.de/mitch/stuff/jprojecttimer_0.0.7-2_all.deb
If you'd like to have the Debian source package, get it from here:
http://jprojecttimer.sourceforge.net/archive/0.0.7/
If you like to stay up-to-date, add this line to your /etc/apt/sources.list:
deb http://www.h.shuttle.de/mitch/stuff ./
An ITP has already been filed:
http://bugs.debian.org/180269
Regards,
Christian
--
....Christian.Garbs.....................................http://www.cgarbs.de
Serena stopped kissing, then smiling, said,
"When you have cable, you're never innocent."
|
|
From: Christian G. [M. Mitch] <mi...@mi...> - 2003-01-04 20:12:15
|
I've just uploaded all available versions of JProjectTimer to the homepage at sourceforge because I need the space on my private webspace for something else :-( The newer releases are already stored with the released file on SF. I did this mainly for the old versions which have not been released on sourceforge (older than 0.0.4). As these are just 3 versions, I could integrate them into the released files if it is desired. As of now, I have created a subdirectory "archive": extern: http://jprojecttimer.sourceforge.net/archive/ local: /home/groups/j/jp/jprojecttimer/htdocs/archive This directory is rsync'ed from my local computer, so any changes to the directory or any subdirectory within it will be reverted on the next rsync run. Don't put any files there, they will be deleted sooner or later! We might want to add a link from the homepage to the archive, but we might as well link to the files download section on the sourceforge project page (as it is designed for the purpose of holding the files -- the project page has access to download mirrors and stuff, while the webpage does not). My local mirror at http://home.t-online.de/home/dietmar.garbs/download/JProjectTimer/ should not be used any more (it holds only one file now and might vanish altogether in the future). Regards, Christian --=20 =2E...Christian.Garbs.....................................http://www.cgarbs= =2Ede "", replied Anne, speechless. (The Long Road - Book Two of Undocumented Features) |
|
From: Christian G. [M. Mitch] <mi...@mi...> - 2002-11-23 12:12:16
|
Hi! What about switching to the newest library versions? We currently use JDOM 1.0 Beta 7 -- current version is Beta 8. http://www.jdom.org describes this release as "with many speed optimizations and functionality improvements!". I think we should just switch to the current version -- if it's ok, I'll just start and do it (should be just checking in the current .jar file). We also use Xerces 1.2.0. Xerces 1 is listed as a `hibernated' project[3] -- current version is 1.4.4 [1]. Xerces 2 is in active development -- version 2.2.1 is current [2]. I don't know to which version we should switch. On [2] it says: | Xerces2 is a nearly complete rewrite of the Xerces 1.x codebase in | order to make the code cleaner, more modular, and easier to | maintain. It includes a completely redesigned and rewritten XML | Schema validation engine. Applications using only the standard | interfaces such as JAXP, DOM, and SAX should not see any | differences. So perhaps we should just look which version is the smallest size and take that one -- I don't see other differences that would concern us. Again, I'd do the necessary changes to include the chosen library into the project. Regards, Christian [1] http://xml.apache.org/xerces-j/index.html [2] http://xml.apache.org/xerces2-j/index.html [3] http://xml.apache.org/ --=20 =2E...Christian.Garbs.....................................http://www.cgarbs= =2Ede lisp, v.: To call a spade a thpade. |
|
From: Christian G. [M. Mitch] <mi...@mi...> - 2002-11-17 14:12:20
|
Hi! What about tracking the road map and/or project status with JProjectTimer? We could put the .xml file and a screen shot of the current project status on the homepage. so long, Mitch -- ....Christian.Garbs.....................................http://www.cgarbs.de Jamie Zawinksi <jw...@ne...> wrote: > Fair enough, but I'll bet you could count the number of non-internet > Usenet feeds in existence today without even taking your socks off. I've got more UUCP feeds than that just between us and our customers. Unless you have really odd-looking hands. In which case I apologize for saying nasty things about the key bindings in Netscape. --- pe...@ta... (Peter da Silva) |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-02-19 22:12:17
|
On Sun, Feb 17, 2002 at 09:59:43PM +0900, Remi POUJEAUX wrote: > The new Java JDK (1.4) has just been released by SUN. Do we switch to it ? I can't get the JDK 1.4.0 to work under Linux (tested on SuSE 6.3 and Debian woody), it always throws this error: | Error occurred during initialization of VM | Could not reserve enough space for object heap I've had the same error with JDK 1.3.1 -- in fact, I'm still developing with JDK 1.2.2 :-) So would say we shouldn't switch to 1.4 yet -- at least not until 1.4 works for me. Are there some new things that we need in 1.3 or 1.4? Or could we stay at 1.2? This way more people could use JProjectTimer: - They would not have to install the newest JDK-Runtime - I don't seem to be the only one with problems under Linux Regards, Christian -- ....Christian.Garbs.....................................http://www.cgarbs.de Me transmitte sursum, calledoni! |
|
From: Remi P. <pou...@mb...> - 2002-02-17 13:00:00
|
The new Java JDK (1.4) has just been released by SUN. Do we switch to it ? Remi |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-02-08 21:48:20
|
Hi! I've just released v0.0.6 of JProjectTimer. It includes the latest changes: - Japanese and Spanish translation - XML file format - new Gantt diagram Thanks for your help! Christian -- ....Christian.Garbs.....................................http://www.cgarbs.de |
|
From: Remi P. <pou...@mb...> - 2002-02-03 15:40:18
|
I've committed Task.java and GanttDiagram.java. The improvement of the Gantt Diagram is not finished yet but you can already find: - links between tasks to represent predecessor relationship - null duration tasks represented as losanges - and some coloring Any comment or suggestion is welcome. Remi |
|
From: Barranger R. <bar...@Sc...> - 2002-01-27 19:45:50
|
Hey there,
Could someone please add the About Dialog to my task list (
tomacco_lover )
Thanks
Barranger
|
|
From: Tim O'B. <to...@di...> - 2002-01-26 00:43:32
|
Description: 1. I made JProjectTimer extend JFrame with the goal of making the JProjectTimer application 100% JFC Swing components. 2. I removed the Look and Feel section that was commented out. 3. Instead of hardcoding a reference to the sample data in /home/mitch, the user is allowed to specify command line arguments: -projectxml <filename> -projectfile <filename> 4. Added an iterative command line processing section. Eventually this should have more error checking, etc. And all of the log output should be I18N-ized. NOTE: If you try to load an existing project XML file with -projectxml, you will notice that the program will fail because there is no SAX parser available to the application. I'd recommend going with Xerces in the short term http://xml.apache.org, and just adding xerces.jar to the lib directory and modifying the patched build.xml and MANIFEST files to reflect the addition. Tim O'Brien to...@di... (847) 863-7045 |
|
From: Tim O'B. <to...@di...> - 2002-01-26 00:07:44
|
Sorry, I forgot to include the patch file. -----Original Message----- From: jpr...@li... [mailto:jpr...@li...]On Behalf Of Tim O'Brien Sent: Friday, January 25, 2002 6:03 PM To: jpr...@li... Subject: [Jprojecttimer-developers] [PATCH] build.xml - Execution of jar, removed copy of jars to classes dir Description: This patch overrides the patch I attached to an earlier message, and it contains the same changes I listed in that message: 1. Project name, version properties 2. Global directory locations 3. Classpath references And it adds the 2 following changes: 1. There is no need to copy the jdom.jar file to the classes directory. I removed that line from the compile target. 2. We execute the program by calling the executable jar. <java jar="..."/> Note: #2 will only work if the previous patch is applied to the MANIFEST file. Tim O'Brien to...@di... (847) 863-7045 _______________________________________________ Jprojecttimer-developers mailing list Jpr...@li... https://lists.sourceforge.net/lists/listinfo/jprojecttimer-developers |
|
From: Tim O'B. <to...@di...> - 2002-01-26 00:03:02
|
Description: This patch overrides the patch I attached to an earlier message, and it contains the same changes I listed in that message: 1. Project name, version properties 2. Global directory locations 3. Classpath references And it adds the 2 following changes: 1. There is no need to copy the jdom.jar file to the classes directory. I removed that line from the compile target. 2. We execute the program by calling the executable jar. <java jar="..."/> Note: #2 will only work if the previous patch is applied to the MANIFEST file. Tim O'Brien to...@di... (847) 863-7045 |
|
From: Tim O'B. <to...@di...> - 2002-01-25 23:59:21
|
Description: I included the "Class-Path:" section in the MANIFST to allow the executable jar to load classes from the jdom.jar file. This will allow you to execute the application with "java -jar JProjectTimer-0.0.6-pre1.jar", as long as the jdom.jar file is in the relative path "./lib/jdom.jar". |
|
From: Tim O'B. <to...@di...> - 2002-01-25 23:05:39
|
Mitch, Here you go, I refactored the build.xml a little bit form the original. You'll notice these changes: 1. Project name and project version are defined as properties. 2. Directories are defined in properties to be reused, this will make it easier to change the structure of the project if you decide to later. 3. The "run" target now depends on the "jar" target. Essential becuase the classpath includes a reference to the project JAR. 4. The compile, javadoc, and run targets all share a reference to a single "classpath" element, defined directly after the global properties. This means that anyone can check the project out of the repository and run it regardless of the environment's CLASSPATH. I attached the patch file. Tim O'Brien to...@di... -----Original Message----- From: jpr...@li... [mailto:jpr...@li...]On Behalf Of Christian Garbs [ Master Mitch ] Sent: Friday, January 25, 2002 3:49 PM To: jpr...@li... Subject: [Jprojecttimer-developers] RE: JDOM On Wed, Jan 23, 2002 at 04:54:12PM -0600, Tim O'Brien wrote: > Putting a JAR into a "lib" directory in a project that depends on > another library is a common practice. Check out the newsml-toolkit > project or any of the Jakarta project for examples. I've created a lib/ directory to include jdom.jar. > BTW, I made an Ant build.xml file for the jprojecttimer project. > Right now it relies on jdom.jar being in the classpath that runs > Ant, but if you included the JAR file then the Ant script could > incorporate it into the classpath when compiling and running the > jprojecttimer application. I tried to expand the build.xml so that lib/jdom.jar is included. The "compile" and "run" targets work fine. But I've got a problem: jdom.jar is included in jprojecttimer.jar, but when I cut down my CLASSPATH and run jprojecttimer.jar, the org.jdom.* classes are not found. The edited version of build.xml can be found in the CVS repository. so long, Mitch -- ....Christian.Garbs.....................................http://www.cgarbs.de Von Zeit zu Zeit muß man sündigen, damit man den Spaß an der Tugend nicht verliert. _______________________________________________ Jprojecttimer-developers mailing list Jpr...@li... https://lists.sourceforge.net/lists/listinfo/jprojecttimer-developers |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-01-25 22:00:16
|
On Wed, Jan 23, 2002 at 04:54:12PM -0600, Tim O'Brien wrote: > Putting a JAR into a "lib" directory in a project that depends on > another library is a common practice. Check out the newsml-toolkit > project or any of the Jakarta project for examples. I've created a lib/ directory to include jdom.jar. > BTW, I made an Ant build.xml file for the jprojecttimer project. > Right now it relies on jdom.jar being in the classpath that runs > Ant, but if you included the JAR file then the Ant script could > incorporate it into the classpath when compiling and running the > jprojecttimer application. I tried to expand the build.xml so that lib/jdom.jar is included. The "compile" and "run" targets work fine. But I've got a problem: jdom.jar is included in jprojecttimer.jar, but when I cut down my CLASSPATH and run jprojecttimer.jar, the org.jdom.* classes are not found. The edited version of build.xml can be found in the CVS repository. so long, Mitch -- ....Christian.Garbs.....................................http://www.cgarbs.de Von Zeit zu Zeit muß man sündigen, damit man den Spaß an der Tugend nicht verliert. |
|
From: Barranger R. <Bar...@Sc...> - 2002-01-25 18:56:12
|
hello there could anyone please expand on the feature request #507287 on the sourceforge project feature request page Thanks, Barranger |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-01-25 18:02:44
|
On Thu, Jan 24, 2002 at 01:19:01PM -0500, Barranger Ridler wrote: > If you select that you want a new task then close the insuing dialog > with the "x" in the upper right hand corner the task is still added to the > task list This bug has just been fixed. Regards, Christian -- ....Christian.Garbs.....................................http://www.cgarbs.de "Linux bereitet auf's Leben vor. Aber worauf bereitet Windows vor?" "Auf die allfälligen Enttäuschungen im Leben." [Dieter Brügmann zu Daniel Reutter in dag°] |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-01-25 18:00:16
|
On Wed, Jan 23, 2002 at 07:43:11PM -0500, Barranger Ridler wrote: > Hello there, > > I was just wondering about what features are needed within > jprojecttimer before it will be considered version 1.0? Hi! There is no Roadmap yet, but I think we should come up with one. When these tasks are finished... 45739 Finish Project class. 45789 Make a better Gantt diagram 45753 Catch IOExceptions 45756 Add tooltips 45755 Add toolbar 45737 Add about box. 45748 TaskEdit cancel button ...the release could be considered "0.2.0". The tasks that are not visible to the user (JavaDoc, code cleanups etc.) should be finished, too, but they are "internal affairs". I think they should not be included in the official release schedule. So the Roadmap is defined from an end-user's point of view while the developer's view is the Task list on the project page (with priorities adapted to reflect the Roadmap's needs). Comments, anyone? Christian -- ....Christian.Garbs.....................................http://www.cgarbs.de Keyboard not found. Press F1 to continue. |
|
From: Barranger R. <Bar...@Sc...> - 2002-01-24 18:32:49
|
Hello there, If you select that you want a new task then close the insuing dialog with the "x" in the upper right hand corner the task is still added to the task list Thanks, Barranger |
|
From: Barranger R. <bar...@Sc...> - 2002-01-24 00:45:15
|
Hello there,
I was just wondering about what features are needed within
jprojecttimer before it will be considered version 1.0?
Thanks,
Barranger
|
|
From: Tim O'B. <to...@di...> - 2002-01-23 22:56:18
|
I attached a build.xml file and the LICENSE.txt file from JDOM. Tim |
|
From: Tim O'B. <to...@di...> - 2002-01-23 22:54:27
|
Putting a JAR into a "lib" directory in a project that depends on another library is a common practice. Check out the newsml-toolkit project or any of the Jakarta project for examples. You can definitely incorporate JDOM into your project. I attached the JDOM License.txt file. You'll just need to do the following: 1. Reproduce this: "Copyright (C) 2000-2002 Brett McLaughlin & Jason Hunter. All rights reserved." In your license as a reference to the JDOM. 2. Put the JDOM jar in ./lib 3. Add the JDOM jar without keyword substitution. Otherwise, you'll end up with corrupted binary file. "cvs add -kb" BTW, I made an Ant build.xml file for the jprojecttimer project. Right now it relies on jdom.jar being in the classpath that runs Ant, but if you included the JAR file then the Ant script could incorporate it into the classpath when compiling and running the jprojecttimer application. The JDOM developers also ask that you acknowledge them in your project documentation. Tim O'Brien to...@di... (847) 863-7045 |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-01-22 22:15:16
|
narf. first post, wrong language. I'll try again: Now that we use the JDOM classes - how do we supply them to the end user? AFAIK there is no binary distribution of the JDOM classes at http://www.jdom.org. We want to distribute a *complete* JProjectTimer .jar that runs out of the box. Needing to download external packages is bad, having to compile these packages on your own is even worse. Can we just compile JDOM for ourselves and add the JDOM .class files to our jar? Perhaps even to CVS? Does this make sense? Does the JDOM license allow this? so long, Mitch -- ....Christian.Garbs.....................................http://www.cgarbs.de |
|
From: Christian G. [ M. M. ] <mi...@mi...> - 2002-01-21 22:15:17
|
Mahlzeit! Wie bauen wir die JDOM-Klassen am besten in unsere .jars ein? Mitliefern? Ist das erlaubt? Sonst muss sich der User erst noch das JDOM ziehen -- die haben AFAIK derzeit keine Binary-Distribution. Dann müsste jeder potentielle Nutzer das SDK installiert haben?! so long, Mitch -- ....Christian.Garbs.....................................http://www.cgarbs.de :wq!^W SYS64738 |
