You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(14) |
Mar
(107) |
Apr
(211) |
May
(93) |
Jun
(158) |
Jul
(159) |
Aug
(368) |
Sep
(188) |
Oct
(151) |
Nov
(115) |
Dec
(98) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(25) |
Feb
|
Mar
(33) |
Apr
(28) |
May
(116) |
Jun
(2) |
Jul
(117) |
Aug
(19) |
Sep
(9) |
Oct
(2) |
Nov
|
Dec
(4) |
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(9) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
(22) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(267) |
Sep
|
Oct
|
Nov
(6) |
Dec
(512) |
| 2008 |
Jan
(187) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <de...@us...> - 2003-08-26 09:51:20
|
Update of /cvsroot/babeldoc/www.babeldoc.com/html In directory sc8-pr-cvs1:/tmp/cvs-serv17307/html Modified Files: main.html sidebar.html Log Message: Adding SF logo and adding some missing tags Index: main.html =================================================================== RCS file: /cvsroot/babeldoc/www.babeldoc.com/html/main.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** main.html 9 Aug 2003 15:36:26 -0000 1.2 --- main.html 26 Aug 2003 09:51:13 -0000 1.3 *************** *** 34,41 **** <a href="http://jakarta.apache.org/velocity"><img src="images/powered-by-velocity.gif" alt="Powered By Velocity"></a> <a href="http://http.apache.org"><img src="images/apache_pb.gif" alt="Powered By Apache"></a> ! </td> </tr> </table> </BODY> - </HTML> - --- 34,42 ---- <a href="http://jakarta.apache.org/velocity"><img src="images/powered-by-velocity.gif" alt="Powered By Velocity"></a> <a href="http://http.apache.org"><img src="images/apache_pb.gif" alt="Powered By Apache"></a> ! ! <a onclick="top.location='http://sourceforge.net/projects/babeldoc';" ! href="http://sourceforge.net/projects/babeldoc"><img src="http://sourceforge.net/sflogo.php?group_id=56976&type=1" width="125" height="37" border="0" alt="Babeldoc development on SourceForge.net" /></a> ! </td> </tr> </table> </BODY> Index: sidebar.html =================================================================== RCS file: /cvsroot/babeldoc/www.babeldoc.com/html/sidebar.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** sidebar.html 13 Aug 2003 01:39:46 -0000 1.4 --- sidebar.html 26 Aug 2003 09:51:13 -0000 1.5 *************** *** 9,13 **** </HEAD> <BODY> ! <img src="images/pipelines.png" border="0"></td> </tr> <br/> <div class="dtree"> --- 9,19 ---- </HEAD> <BODY> ! <table> ! <tr><td> ! <img src="images/pipelines.png" border="0"> ! </td></tr> ! ! ! </table> <br/> <div class="dtree"> *************** *** 33,36 **** --- 39,43 ---- </script> </div> + </BODY> </HTML> |
|
From: <de...@us...> - 2003-08-26 08:21:41
|
Update of /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker
In directory sc8-pr-cvs1:/tmp/cvs-serv4584/modules/scanner/src/com/babeldoc/scanner/worker
Modified Files:
FtpScanner.java
Log Message:
Putting back initialization of ftpPassword property removed by Bruce (YEAH BRUCE, YOU DID IT!!!) that caused exceptions when trying to log in ftp server.
Index: FtpScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/FtpScanner.java,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** FtpScanner.java 17 Aug 2003 04:12:29 -0000 1.18
--- FtpScanner.java 26 Aug 2003 08:21:33 -0000 1.19
***************
*** 176,182 ****
*/
public void initialize() throws ScannerConfigurationException {
! // LogService.getInstance().logInfo("initialize");
ftpHost = this.getInfo().getStrValue(FTP_HOST);
ftpUsername = this.getInfo().getStrValue(FTP_USERNAME);
ftpFolder = this.getInfo().getStrValue(FTP_FOLDER);
ftpOutFolder = this.getInfo().getStrValue(FTP_OUT_FOLDER);
--- 176,183 ----
*/
public void initialize() throws ScannerConfigurationException {
!
ftpHost = this.getInfo().getStrValue(FTP_HOST);
ftpUsername = this.getInfo().getStrValue(FTP_USERNAME);
+ ftpPassword = this.getInfo().getStrValue(FTP_PASSWORD);
ftpFolder = this.getInfo().getStrValue(FTP_FOLDER);
ftpOutFolder = this.getInfo().getStrValue(FTP_OUT_FOLDER);
|
|
From: <de...@us...> - 2003-08-26 08:06:42
|
Update of /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker
In directory sc8-pr-cvs1:/tmp/cvs-serv2301/modules/scanner/src/com/babeldoc/scanner/worker
Modified Files:
MailboxScanner.java
Log Message:
Fixed bug that caused ClassCastException when processing messages
Index: MailboxScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/MailboxScanner.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** MailboxScanner.java 17 Aug 2003 04:12:29 -0000 1.22
--- MailboxScanner.java 26 Aug 2003 08:06:35 -0000 1.23
***************
*** 290,294 ****
processMultipart((Multipart) message.getContent(), message);
} else {
! processPart((Part) message.getContent(), message);
}
}
--- 290,294 ----
processMultipart((Multipart) message.getContent(), message);
} else {
! processPart((Part) message, message);
}
}
|
|
From: Dejan K. <dej...@nb...> - 2003-08-26 07:39:12
|
I guess you are right that DefaultErrorHandler is ignored. IMO, the
execution should look like this:
- in case of error try to get error handler:
-if there is error handler configured for this stage return it
-if no error handler configured for this stage try to return default
error handler
- error handler shoud try to handle this error
- if error handler returns true, continue with processing. Otherwise, if
error stage is configured for particular stage, it should be processed next.
I noticed that default error handler is hardcoded and configuration option
in service factory is ignored. Now the problem is how we can guarantee that
some error handler would be returned from getErrorHandler() method? Maybe we
should just throw an exception in case default error handler could not be
obtained. The problem is that this is not something that user would notice
when start babeldoc. It could take a lot of time untill first error occures.
This would mean that user woudn't be aware that configuration is wrong until
first error occued.
The other option that could be possible is that getErrorHandler would first
try to get error handler configured for that stage, then it should try to
obtain default error handler configured in service file, and in case that
fail it should return DefaultPipelineStageErrorHanlder class. This also
could be bad solution since user might think that it is all right, even if
he has not configured PipelineStageErrorHandler.default correctly.
Ken, do you have some ideas how to improve this code furhter? I don't like
it right now, it looks pretty complicated...
Dejan
----- Original Message -----
From: "Ken Geis" <kg...@sp...>
To: <bab...@li...>
Sent: Tuesday, August 26, 2003 3:34 AM
Subject: [Babeldoc-devel] Setting the error handler
> The docs say
>
> > If you want to have some other error handler you can do it by writing
> > your own error handler class. Your class should implement the
> > interface com.babeldoc.core.pipeline.IPipelineStageErrorHandler. You
> > will also need to provide your new error handler Java class to the
> > pipeline configuration.
>
> That last sentence needs to be expanded. It took looking at the code
> for me to figure it out.
>
> So looking at the PipelineStage code, I would need to set errorHandler
> on each pipeline stage in order to override the default error handler.
> I'd like to be able to change one setting and have it be the default
> error handler. Right now, there is an entry in the core
> service/query.properties
>
>
PipelineStageErrorHandler.default=com.babeldoc.core.pipeline.DefaultPipeline
StageErrorHandler
>
> It looks like this setting is ignored (see
PipelineStage.getErrorHandler().)
>
> Am I missing something? How do I do this? Is there some code that
> needs to get written? I'm glad to do it.
>
>
> Ken
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> at the same time. Free trial click
here:http://www.vmware.com/wl/offer/358/0
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
|
|
From: Ken G. <kg...@sp...> - 2003-08-26 01:35:06
|
The docs say > If you want to have some other error handler you can do it by writing > your own error handler class. Your class should implement the > interface com.babeldoc.core.pipeline.IPipelineStageErrorHandler. You > will also need to provide your new error handler Java class to the > pipeline configuration. That last sentence needs to be expanded. It took looking at the code for me to figure it out. So looking at the PipelineStage code, I would need to set errorHandler on each pipeline stage in order to override the default error handler. I'd like to be able to change one setting and have it be the default error handler. Right now, there is an entry in the core service/query.properties PipelineStageErrorHandler.default=com.babeldoc.core.pipeline.DefaultPipelineStageErrorHandler It looks like this setting is ignored (see PipelineStage.getErrorHandler().) Am I missing something? How do I do this? Is there some code that needs to get written? I'm glad to do it. Ken |
|
From: McDonald, B. <Bru...@ba...> - 2003-08-22 12:46:49
|
The configuration option code is finally getting to where we wanted it when we put it in about 9months ago! -----Original Message----- From: Dejan Krsmanovic [mailto:dej...@nb...] Sent: Friday, August 22, 2003 4:56 AM To: bab...@li... Subject: Re: [Babeldoc-devel] Re: Babeldoc: SmtpWriter It should be fixed now. I was suprised when I saw that in config option info it always had 'true' default value. Anyway, until latest Bruce's changes this wasn't important since no code had used that information. Now if you request value of some config option you WILL get default value if no value is provided. Earlier each stage was responisble for checking if value is present and dealing with default values. I like this new code, Bruce! Dejan ----- Original Message ----- From: "Dejan Krsmanovic" <dej...@ya...> To: <bab...@li...> Sent: Friday, August 22, 2003 8:40 AM Subject: [Babeldoc-devel] Re: Babeldoc: SmtpWriter > Yes, it was false by default. I will check the code > right now to see what's happening... > > Dejan > > --- Bruce McDonald <br...@mc...> wrote: > > Ken, > > > > I would imagine that its false by default. Dejan? > > > > regards, > > Bruce. > > > > On Thursday 21 August 2003 07:12 pm, Ken Geis wrote: > > > Hi Bruce, Dejan. > > > > > > In the SmtpWriterPipelineStage, the > > "attachDocument" option defaults to > > > true, but the i18n file comments that it is false > > by default. I think > > > it should be false, but someone needs to decide > > what the behavior should > > > be and then whether to change the code or the > > documentation. Also, > > > perhaps the comment on the option shouldn't say > > what the default is at > > > all; that information is already in the > > ConfigOption. > > > > > > It's funny that this comes up when we are playing > > with the 1.1 series. > > > That code hasn't changed recently, but I guess the > > ConfigOptions are now > > > being used! > > > > > > > > > Ken > > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines > at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Dejan K. <dej...@nb...> - 2003-08-22 08:57:53
|
It should be fixed now. I was suprised when I saw that in config option info it always had 'true' default value. Anyway, until latest Bruce's changes this wasn't important since no code had used that information. Now if you request value of some config option you WILL get default value if no value is provided. Earlier each stage was responisble for checking if value is present and dealing with default values. I like this new code, Bruce! Dejan ----- Original Message ----- From: "Dejan Krsmanovic" <dej...@ya...> To: <bab...@li...> Sent: Friday, August 22, 2003 8:40 AM Subject: [Babeldoc-devel] Re: Babeldoc: SmtpWriter > Yes, it was false by default. I will check the code > right now to see what's happening... > > Dejan > > --- Bruce McDonald <br...@mc...> wrote: > > Ken, > > > > I would imagine that its false by default. Dejan? > > > > regards, > > Bruce. > > > > On Thursday 21 August 2003 07:12 pm, Ken Geis wrote: > > > Hi Bruce, Dejan. > > > > > > In the SmtpWriterPipelineStage, the > > "attachDocument" option defaults to > > > true, but the i18n file comments that it is false > > by default. I think > > > it should be false, but someone needs to decide > > what the behavior should > > > be and then whether to change the code or the > > documentation. Also, > > > perhaps the comment on the option shouldn't say > > what the default is at > > > all; that information is already in the > > ConfigOption. > > > > > > It's funny that this comes up when we are playing > > with the 1.1 series. > > > That code hasn't changed recently, but I guess the > > ConfigOptions are now > > > being used! > > > > > > > > > Ken > > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines > at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: <de...@us...> - 2003-08-22 08:11:43
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/pipeline/stage
In directory sc8-pr-cvs1:/tmp/cvs-serv16313/modules/core/src/com/babeldoc/core/pipeline/stage
Modified Files:
SmtpWriterPipelineStage.java
Log Message:
Fixed bug with attachment config option.
Document is NOT attached by default.
Index: SmtpWriterPipelineStage.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/pipeline/stage/SmtpWriterPipelineStage.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** SmtpWriterPipelineStage.java 12 Aug 2003 23:44:44 -0000 1.10
--- SmtpWriterPipelineStage.java 22 Aug 2003 08:11:40 -0000 1.11
***************
*** 145,149 ****
IConfigOptionType.STRING, null, false, I18n.get("100146")));
options.add(new ConfigOption(ATTACH_DOC, IConfigOptionType.BOOLEAN,
! "true", false, I18n.get("100147")));
options.add(new ConfigOption(DOC_FILE_NAME, IConfigOptionType.STRING,
"babeldoc-document", false, I18n.get("100148")));
--- 145,149 ----
IConfigOptionType.STRING, null, false, I18n.get("100146")));
options.add(new ConfigOption(ATTACH_DOC, IConfigOptionType.BOOLEAN,
! "false", false, I18n.get("100147")));
options.add(new ConfigOption(DOC_FILE_NAME, IConfigOptionType.STRING,
"babeldoc-document", false, I18n.get("100148")));
|
|
From: Dejan K. <dej...@ya...> - 2003-08-22 06:40:13
|
Yes, it was false by default. I will check the code right now to see what's happening... Dejan --- Bruce McDonald <br...@mc...> wrote: > Ken, > > I would imagine that its false by default. Dejan? > > regards, > Bruce. > > On Thursday 21 August 2003 07:12 pm, Ken Geis wrote: > > Hi Bruce, Dejan. > > > > In the SmtpWriterPipelineStage, the > "attachDocument" option defaults to > > true, but the i18n file comments that it is false > by default. I think > > it should be false, but someone needs to decide > what the behavior should > > be and then whether to change the code or the > documentation. Also, > > perhaps the comment on the option shouldn't say > what the default is at > > all; that information is already in the > ConfigOption. > > > > It's funny that this comes up when we are playing > with the 1.1 series. > > That code hasn't changed recently, but I guess the > ConfigOptions are now > > being used! > > > > > > Ken __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
|
From: Bruce M. <br...@mc...> - 2003-08-20 03:37:36
|
Looking good!! |
|
From: <dgl...@us...> - 2003-08-19 05:11:41
|
Update of /cvsroot/babeldoc/babeldoc/modules/gui/src/com/babeldoc/gui/journal/browser
In directory sc8-pr-cvs1:/tmp/cvs-serv22667/modules/gui/src/com/babeldoc/gui/journal/browser
Modified Files:
JournalBrowserFrame.java JournalTree.java
Log Message:
Added menu, set color for steps that have statusUpdate="fail", or any journalUpdate operation
Index: JournalBrowserFrame.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/gui/src/com/babeldoc/gui/journal/browser/JournalBrowserFrame.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** JournalBrowserFrame.java 11 Jun 2003 23:35:38 -0000 1.2
--- JournalBrowserFrame.java 19 Aug 2003 05:11:38 -0000 1.3
***************
*** 66,71 ****
--- 66,74 ----
package com.babeldoc.gui.journal.browser;
+ import com.babeldoc.core.config.ConfigService;
import com.babeldoc.core.journal.query.QueryTicket;
+ import java.awt.event.ActionEvent;
+ import java.awt.event.ActionListener;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
***************
*** 75,85 ****
import javax.swing.event.TreeModelListener;
import javax.swing.tree.DefaultMutableTreeNode;
import javax.swing.tree.TreeNode;
import javax.swing.tree.TreePath;
import javax.swing.tree.TreeSelectionModel;
/**
! * This is the main window to the the PipelineBuilder.
*/
public class JournalBrowserFrame extends JFrame {
--- 78,90 ----
import javax.swing.event.TreeModelListener;
import javax.swing.tree.DefaultMutableTreeNode;
+ import javax.swing.tree.DefaultTreeCellRenderer;
import javax.swing.tree.TreeNode;
import javax.swing.tree.TreePath;
import javax.swing.tree.TreeSelectionModel;
+ import org.apache.batik.apps.svgbrowser.Application;
/**
! * This is the main window to the the JournalBrowser
*/
public class JournalBrowserFrame extends JFrame {
***************
*** 87,90 ****
--- 92,101 ----
private JournalTree tree;
+ private String version = ConfigService.getString("env/build", "babeldoc_version");
+ private String TITLE_MESSAGE = "JournalBrowser v" + version;
+ private String ABOUT_MESSAGE = TITLE_MESSAGE + "\n\n" +
+ "(C)opyright 2000-2003 The Apache Software Foundation\n" +
+ "All rights reserved";
+ private String COMING_SOON_MESSAGE = "This feature will soon be implemented.\nPlease be patient!";
/**
* Construct the main UI.
***************
*** 115,119 ****
--- 126,233 ----
});
+ // build the menu options
+ this.setJMenuBar(buildMenu());
+
+ // finish setting up the frame
+ this.setTitle(TITLE_MESSAGE);
this.getContentPane().add(new JScrollPane(tree));
+ }
+
+ /**
+ * Builds the menu for the JournalBrowser
+ * @return JMenuBar the menu for the JournalBrowser
+ */
+ protected JMenuBar buildMenu() {
+ // Menu
+ JMenuBar jMenuBar = new JMenuBar();
+
+ // ====== File menu items ======
+ JMenu jMenuFile = new JMenu("File");
+ jMenuFile.setMnemonic('F');
+ jMenuBar.add(jMenuFile);
+
+ // File | Exit
+ JMenuItem jMenuFileExit = new JMenuItem("Exit");
+ jMenuFileExit.setMnemonic('x');
+ jMenuFileExit.addActionListener(new ActionListener() {
+ public void actionPerformed(ActionEvent e) {
+ System.exit(0);
+ }
+ });
+ jMenuFile.add(jMenuFileExit);
+
+ // ====== Edit menu items ======
+ JMenu jMenuEdit = new JMenu("Edit");
+ jMenuEdit.setMnemonic('E');
+ jMenuBar.add(jMenuEdit);
+
+ // Edit | Replay
+ JMenuItem jMenuEditReplay = new JMenuItem("Replay");
+ jMenuEditReplay.setMnemonic('R');
+ jMenuEditReplay.addActionListener(new ActionListener() {
+ public void actionPerformed(ActionEvent e) {
+ JOptionPane.showMessageDialog(
+ null,
+ COMING_SOON_MESSAGE,
+ "Coming Soon!",
+ JOptionPane.PLAIN_MESSAGE);
+ }
+ });
+ jMenuEdit.add(jMenuEditReplay);
+
+ // ====== View menu items ======
+ JMenu jMenuView = new JMenu("View");
+ jMenuView.setMnemonic('V');
+ jMenuBar.add(jMenuView);
+
+ // View | Color
+ JMenuItem jMenuViewColor = new JMenuItem("Color");
+ jMenuViewColor.setMnemonic('C');
+ jMenuViewColor.setSelected(true); // default to on
+ jMenuViewColor.addActionListener(new ActionListener() {
+ public void actionPerformed(ActionEvent e) {
+ JOptionPane.showMessageDialog(
+ null,
+ COMING_SOON_MESSAGE,
+ "Coming Soon to JournalBrowser",
+ JOptionPane.PLAIN_MESSAGE);
+ }
+ });
+ jMenuView.add(jMenuViewColor);
+
+ // View | Records
+ JMenuItem jMenuViewRecords = new JMenuItem("Records");
+ jMenuViewRecords.setMnemonic('R');
+ jMenuViewRecords.addActionListener(new ActionListener() {
+ public void actionPerformed(ActionEvent e) {
+ JOptionPane.showMessageDialog(
+ null,
+ COMING_SOON_MESSAGE,
+ "Coming Soon to JournalBrowser",
+ JOptionPane.PLAIN_MESSAGE);
+ }
+ });
+ jMenuView.add(jMenuViewRecords);
+
+ // ====== Help menu items ======
+ JMenu jMenuHelp = new JMenu("Help");
+ jMenuHelp.setMnemonic('H');
+ jMenuBar.add(jMenuHelp);
+
+ // Help | About
+ JMenuItem jMenuHelpAbout = new JMenuItem("About");
+ jMenuHelpAbout.setMnemonic('A');
+ jMenuHelpAbout.addActionListener(new ActionListener() {
+ public void actionPerformed(ActionEvent e) {
+ JOptionPane.showMessageDialog(
+ null,
+ ABOUT_MESSAGE,
+ "About JournalBrowser",
+ JOptionPane.PLAIN_MESSAGE);
+ }
+ });
+ jMenuHelp.add(jMenuHelpAbout);
+
+ return jMenuBar;
}
Index: JournalTree.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/gui/src/com/babeldoc/gui/journal/browser/JournalTree.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** JournalTree.java 11 Jun 2003 23:35:38 -0000 1.2
--- JournalTree.java 19 Aug 2003 05:11:38 -0000 1.3
***************
*** 68,74 ****
--- 68,80 ----
import com.babeldoc.core.journal.query.QueryTicket;
+ import java.awt.Color;
+ import java.awt.Dimension;
+ import java.awt.Font;
+
import javax.swing.*;
+ import javax.swing.plaf.ColorUIResource;
import javax.swing.tree.DefaultMutableTreeNode;
import javax.swing.tree.DefaultTreeModel;
+ import javax.swing.tree.TreeCellRenderer;
***************
*** 95,102 ****
this.populateTree();
super.setModel(this.journalTreeModel);
}
/**
! */
private void populateTree() {
QueryTicket[] qts = this.browserModel.getTickets(0, 100);
--- 101,112 ----
this.populateTree();
super.setModel(this.journalTreeModel);
+
+ // set the custom renderer so that we can control the colors
+ this.setCellRenderer(new JournalBrowserCellRenderer());
}
/**
! * Populate the tree (duh!)
! */
private void populateTree() {
QueryTicket[] qts = this.browserModel.getTickets(0, 100);
***************
*** 125,128 ****
--- 135,253 ----
}
}
+
+ /**
+ * Cell renderer to show error steps in red
+ */
+ class JournalBrowserCellRenderer extends JPanel implements TreeCellRenderer {
+ protected JLabel icon;
+ protected JTextArea text;
+ protected Color defaultColor;
+ protected Color defaultBackgroundColor;
+ protected Font defaultFont;
+ protected Font boldFont;
+
+ private final Color FAIL_COLOR=Color.WHITE;
+ private final Color FAIL_BCOLOR=Color.RED;
+ private final Color MSG_COLOR=Color.WHITE;
+ private final Color MSG_BCOLOR=Color.BLUE;
+ private final int STRUT_WIDTH=4;
+
+ /**
+ * Constructor
+ */
+ public JournalBrowserCellRenderer() {
+ setLayout(new BoxLayout(this, BoxLayout.X_AXIS));
+ icon = new JLabel() {
+ public void setBackground(java.awt.Color color) {
+ if (color instanceof ColorUIResource) {
+ color = null;
+ }
+ super.setBackground(color);
+ }
+ };
+ add(icon);
+ add(Box.createHorizontalStrut(STRUT_WIDTH));
+ add(text = new JTextArea());
+ defaultColor = text.getForeground();
+ defaultBackgroundColor = text.getBackground();
+ defaultFont = text.getFont();
+
+ // create a bold font to use for emphasis
+ boldFont = new Font(defaultFont.getName(), Font.BOLD, defaultFont.getSize());
+ }
+
+ /**
+ * Override getPreferredSize to make room for modified display string
+ * @return java.awt.Dimension
+ */
+ public java.awt.Dimension getPreferredSize() {
+ Dimension iconD = icon.getPreferredSize();
+ Dimension textD = text.getPreferredSize();
+ return new Dimension(iconD.width + textD.width + STRUT_WIDTH, textD.height);
+ }
+
+ /**
+ * Return the TreeCellRenderComponent, modified for background color
+ * @return java.awt.Component
+ */
+ public java.awt.Component getTreeCellRendererComponent(javax.swing.JTree tree,
+ Object value, boolean selected, boolean expanded, boolean leaf, int row,
+ boolean hasFocus) {
+ // setup initial state
+ setEnabled(tree.isEnabled());
+
+ if (leaf) {
+ icon.setIcon(UIManager.getIcon("Tree.leafIcon"));
+ }
+ else if (expanded) {
+ icon.setIcon(UIManager.getIcon("Tree.openIcon"));
+ }
+ else {
+ icon.setIcon(UIManager.getIcon("Tree.closedIcon"));
+ }
+ text.setText(value.toString());
+ text.setForeground(defaultColor);
+ text.setBackground(defaultBackgroundColor);
+ text.setFont(defaultFont);
+
+ // do a bit of sanity checking here
+ if (value instanceof DefaultMutableTreeNode) {
+
+ DefaultMutableTreeNode node = (DefaultMutableTreeNode)value;
+ if (node.getUserObject() instanceof JournalTreeTicketStep) {
+ // Use the following color scheme:
+ // failure = red background, white text
+ // message = green background, white text
+ QueryTicket ticket = (QueryTicket)((JournalTreeTicketStep)node.getUserObject()).getQTicket();
+ if (leaf) {
+ if (ticket.getOperation().equals("updateStatus") && ticket.getOther().equals("fail")) {
+ text.setForeground(FAIL_COLOR);
+ text.setBackground(FAIL_BCOLOR);
+ text.setFont(boldFont);
+ }
+ else if (ticket.getOperation().equals("updateJournal")) {
+ text.setForeground(MSG_COLOR);
+ text.setBackground(MSG_BCOLOR);
+ text.setFont(boldFont);
+ }
+ }
+ }
+ }
+
+ return this;
+ }
+
+ /**
+ * Set the background color. This override will ensure that the parent (tree)
+ * container matches the node background color
+ * @param color java.awt.Color
+ */
+ public void setBackground(Color color) {
+ if (color instanceof ColorUIResource) {
+ color = null;
+ }
+ super.setBackground(color);
+ }
+ }
}
***************
*** 218,222 ****
return "Step: " + getQTicket().getStep() + ", stage: " +
getQTicket().getStage() + ", date: " + getQTicket().getDate() +
! ", operation: " + getQTicket().getOperation();
}
}
--- 343,348 ----
return "Step: " + getQTicket().getStep() + ", stage: " +
getQTicket().getStage() + ", date: " + getQTicket().getDate() +
! ", operation: " + getQTicket().getOperation() +
! ", other: " + getQTicket().getOther();
}
}
|
|
From: Bruce M. <br...@mc...> - 2003-08-18 22:35:55
|
Good, We can use those classes as a starting point. Maybe move them into a package just under code (or somewhere out of the pipeline.stage). Transformation api for XSL. It too needs to have a resolver but is one is called URIResolver but the idea is the same. It wants to resolve URIs into Sources. On Monday 18 August 2003 05:44 pm, Leech, Jonathan wrote: > I think you're right. I wrote those classes in a hurry and they're > definitely not feature-rich. > One thing to add to the list is the ability to specify the location of the > directory for the disk cache. > What is TRax? > > -Jonathan > > > -----Original Message----- > From: McDonald, Bruce [mailto:Bru...@ba...] > Sent: Monday, August 18, 2003 3:28 PM > To: bab...@li... > Subject: [Babeldoc-devel] EntityResolvers and Babeldoc > > > All, > > I have been looking through the tree and I have been looking at the two > entity resolvers in the core/.../pipeline/stage source directory. There is > a entity resolver for in-memory caching and one for caching on the > filesystem. These are chained - the Memory resolver uses the Disk Cache. > Now here are my thoughts: > > 1. We should make these bits of code more pervasive - not just limited to > the DomifyPipelineStage (which is quite fragmented at the moment). > 2. There is an opportunity for code reuse between these two classes. The > resolveEntity method shows significant similarities. > 3. Can we expand this to also implement URIResolver which is what TRaX > uses? This means that we might need to standardize how the cache documents > are named in the directory (it currently uses a hashcode of the System ID). > Maybe we can "sanitize" the SystemID and the URI references (for example, > all /:; becomes ~) names so that we can store the files with a name that is > kinda like their original name. > 4. We need to make it so that entities can be stored in the configuration > directories so that long term DTDs, Schemas can be cached in the > configuration dirs. > > What are your thoughts here? Anyone have any experience with this? > > regards, > Bruce. > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Leech, J. <jl...@vi...> - 2003-08-18 21:46:17
|
I think you're right. I wrote those classes in a hurry and they're definitely not feature-rich. One thing to add to the list is the ability to specify the location of the directory for the disk cache. What is TRax? -Jonathan -----Original Message----- From: McDonald, Bruce [mailto:Bru...@ba...] Sent: Monday, August 18, 2003 3:28 PM To: bab...@li... Subject: [Babeldoc-devel] EntityResolvers and Babeldoc All, I have been looking through the tree and I have been looking at the two entity resolvers in the core/.../pipeline/stage source directory. There is a entity resolver for in-memory caching and one for caching on the filesystem. These are chained - the Memory resolver uses the Disk Cache. Now here are my thoughts: 1. We should make these bits of code more pervasive - not just limited to the DomifyPipelineStage (which is quite fragmented at the moment). 2. There is an opportunity for code reuse between these two classes. The resolveEntity method shows significant similarities. 3. Can we expand this to also implement URIResolver which is what TRaX uses? This means that we might need to standardize how the cache documents are named in the directory (it currently uses a hashcode of the System ID). Maybe we can "sanitize" the SystemID and the URI references (for example, all /:; becomes ~) names so that we can store the files with a name that is kinda like their original name. 4. We need to make it so that entities can be stored in the configuration directories so that long term DTDs, Schemas can be cached in the configuration dirs. What are your thoughts here? Anyone have any experience with this? regards, Bruce. ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: McDonald, B. <Bru...@ba...> - 2003-08-18 21:29:18
|
All, I have been looking through the tree and I have been looking at the two entity resolvers in the core/.../pipeline/stage source directory. There is a entity resolver for in-memory caching and one for caching on the filesystem. These are chained - the Memory resolver uses the Disk Cache. Now here are my thoughts: 1. We should make these bits of code more pervasive - not just limited to the DomifyPipelineStage (which is quite fragmented at the moment). 2. There is an opportunity for code reuse between these two classes. The resolveEntity method shows significant similarities. 3. Can we expand this to also implement URIResolver which is what TRaX uses? This means that we might need to standardize how the cache documents are named in the directory (it currently uses a hashcode of the System ID). Maybe we can "sanitize" the SystemID and the URI references (for example, all /:; becomes ~) names so that we can store the files with a name that is kinda like their original name. 4. We need to make it so that entities can be stored in the configuration directories so that long term DTDs, Schemas can be cached in the configuration dirs. What are your thoughts here? Anyone have any experience with this? regards, Bruce. |
|
From: <dgl...@us...> - 2003-08-18 19:21:10
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal/query
In directory sc8-pr-cvs1:/tmp/cvs-serv29528/modules/core/src/com/babeldoc/core/journal/query
Modified Files:
QueryTicket.java
Log Message:
Spelling correction
Index: QueryTicket.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal/query/QueryTicket.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** QueryTicket.java 27 Jun 2003 02:19:58 -0000 1.4
--- QueryTicket.java 18 Aug 2003 19:21:07 -0000 1.5
***************
*** 205,209 ****
.append("operation", operation)
.append("stage", stage)
! .append("addional", additional)
.append("other", other).append("step", step)
.toString();
--- 205,209 ----
.append("operation", operation)
.append("stage", stage)
! .append("additional", additional)
.append("other", other).append("step", step)
.toString();
|
|
From: <dgl...@us...> - 2003-08-18 19:18:44
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/pipeline/stage
In directory sc8-pr-cvs1:/tmp/cvs-serv28966/modules/core/src/com/babeldoc/core/pipeline/stage
Modified Files:
JournalUpdatePipelineStage.java
Log Message:
Moved logMessage into IJournal interface
Index: JournalUpdatePipelineStage.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/pipeline/stage/JournalUpdatePipelineStage.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** JournalUpdatePipelineStage.java 18 Aug 2003 00:23:21 -0000 1.3
--- JournalUpdatePipelineStage.java 18 Aug 2003 19:18:41 -0000 1.4
***************
*** 134,138 ****
// add a journal entry for the message
try {
! ((SimpleJournal)getJournal()).logMessage(getTicket(), getPipelineName() + "." + getName(),
message);
}
--- 134,138 ----
// add a journal entry for the message
try {
! getJournal().logMessage(getTicket(), getPipelineName() + "." + getName(),
message);
}
|
|
From: <dgl...@us...> - 2003-08-18 19:18:32
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal
In directory sc8-pr-cvs1:/tmp/cvs-serv28937/modules/core/src/com/babeldoc/core/journal
Modified Files:
IJournal.java Journal.java
Log Message:
Moved logMessage into IJournal interface
Index: IJournal.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal/IJournal.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** IJournal.java 12 Aug 2003 23:44:43 -0000 1.6
--- IJournal.java 18 Aug 2003 19:18:29 -0000 1.7
***************
*** 157,160 ****
--- 157,168 ----
/**
+ * Log a message into the log file
+ * @param stage the stage to log
+ * @param String The message to log
+ */
+ public void logMessage(IJournalTicket ticket, String stage, String message)
+ throws JournalException;
+
+ /**
* Replay this ticket from the step
*
Index: Journal.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal/Journal.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** Journal.java 27 Jun 2003 02:19:57 -0000 1.6
--- Journal.java 18 Aug 2003 19:18:29 -0000 1.7
***************
*** 157,160 ****
--- 157,170 ----
/**
+ * Log a message into the log file
+ * @param stage the stage to log
+ * @param String The message to log
+ */
+ public void logMessage(IJournalTicket ticket, String stage, String message)
+ throws JournalException {
+ log(ticket, JournalOperation.updateJournal, message, stage, null);
+ }
+
+ /**
* Log string to the log file. This MUST be overriden.
*
|
|
From: <dgl...@us...> - 2003-08-18 19:18:10
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal/simple
In directory sc8-pr-cvs1:/tmp/cvs-serv28829/modules/core/src/com/babeldoc/core/journal/simple
Modified Files:
SimpleJournal.java
Log Message:
Moved logMessage into IJournal interface
Index: SimpleJournal.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/journal/simple/SimpleJournal.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** SimpleJournal.java 17 Aug 2003 22:34:46 -0000 1.8
--- SimpleJournal.java 18 Aug 2003 19:18:07 -0000 1.9
***************
*** 448,461 ****
/**
- * Log a message into the log file
- * @param stage the stage to log
- * @param String The message to log
- */
- public void logMessage(IJournalTicket ticket, String stage, String message)
- throws JournalException {
- log(ticket, JournalOperation.updateJournal, message, stage, null);
- }
-
- /**
* Log string to the log file
*
--- 448,451 ----
|
|
From: McDonald, B. <Bru...@ba...> - 2003-08-18 14:20:26
|
I cant remember right off hand but you are fine! Check in away (!?) -----Original Message----- From: David Glick [mailto:dg...@co...] Sent: Monday, August 18, 2003 9:34 AM To: Bruce McDonald; bab...@li... Subject: Re: [Babeldoc-devel] JournalUpdatePipelineStage... What is the timeframe for the 1.2 release? I have some changes I'm working on right now for the journalbrowser that I was planning to check in tonight or tomorrow, but I don't want to impact the 1.2 release. On Monday 18 August 2003 6:06 am, Bruce McDonald wrote: > Yes I did, > > Heres what I think we can do to get this to work: > > Add a reference in the description to an example you have manually entered > after the pipelinestages get included. I am very leary about redoing the > documentation / configinfo stuff at this stage before 1.2 goes live. > > regards, > Bruce > > On Monday 18 August 2003 08:09 am, David Glick wrote: > > Excellent suggestion! I'll try to get this fixed today. > > > > On a totally unrelated note, have you had a chance to review my post > > regarding the documentation? I'd like to get some updates in, but I'm > > not sure which direction to proceed. > > > > > > Thanks, > > > > David > > > > On Sunday 17 August 2003 10:56 pm, Bruce McDonald wrote: > > > David, > > > > > > In the mentioned class you cast the journal to SimpleJournal - why dont > > > you just expand the interface to accomodate what you need - it could > > > fail with SqlJournal. > > > > > > regards, > > > Bruce. > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > > > Data Reports, E-commerce, Portals, and Forums are available now. > > > Download today and enter to win an XBOX or Visual Studio .NET. > > > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_0 > > >1/ 01 _______________________________________________ > > > Babeldoc-devel mailing list > > > Bab...@li... > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Bruce M. <br...@mc...> - 2003-08-18 14:19:21
|
Yes I did, Heres what I think we can do to get this to work: Add a reference in the description to an example you have manually entered after the pipelinestages get included. I am very leary about redoing the documentation / configinfo stuff at this stage before 1.2 goes live. regards, Bruce On Monday 18 August 2003 08:09 am, David Glick wrote: > Excellent suggestion! I'll try to get this fixed today. > > On a totally unrelated note, have you had a chance to review my post > regarding the documentation? I'd like to get some updates in, but I'm not > sure which direction to proceed. > > > Thanks, > > David > > On Sunday 17 August 2003 10:56 pm, Bruce McDonald wrote: > > David, > > > > In the mentioned class you cast the journal to SimpleJournal - why dont > > you just expand the interface to accomodate what you need - it could fail > > with SqlJournal. > > > > regards, > > Bruce. > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > > Data Reports, E-commerce, Portals, and Forums are available now. > > Download today and enter to win an XBOX or Visual Studio .NET. > > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/ > >01 _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Dejan K. <dej...@ya...> - 2003-08-18 13:59:50
|
I guess you can create separate CVS branch. And if you finish it soon then you can merge it with 1.1 codebase. If not leave it for 1.3. Dejan --- David Glick <dg...@co...> wrote: > What is the timeframe for the 1.2 release? I have > some changes I'm working on > right now for the journalbrowser that I was planning > to check in tonight or > tomorrow, but I don't want to impact the 1.2 > release. > > > On Monday 18 August 2003 6:06 am, Bruce McDonald > wrote: > > Yes I did, > > > > Heres what I think we can do to get this to work: > > > > Add a reference in the description to an example > you have manually entered > > after the pipelinestages get included. I am very > leary about redoing the > > documentation / configinfo stuff at this stage > before 1.2 goes live. > > > > regards, > > Bruce > > > > On Monday 18 August 2003 08:09 am, David Glick > wrote: > > > Excellent suggestion! I'll try to get this > fixed today. > > > > > > On a totally unrelated note, have you had a > chance to review my post > > > regarding the documentation? I'd like to get > some updates in, but I'm > > > not sure which direction to proceed. > > > > > > > > > Thanks, > > > > > > David > > > > > > On Sunday 17 August 2003 10:56 pm, Bruce > McDonald wrote: > > > > David, > > > > > > > > In the mentioned class you cast the journal to > SimpleJournal - why dont > > > > you just expand the interface to accomodate > what you need - it could > > > > fail with SqlJournal. > > > > > > > > regards, > > > > Bruce. > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > > > > Data Reports, E-commerce, Portals, and Forums > are available now. > > > > Download today and enter to win an XBOX or > Visual Studio .NET. > > > > > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_0 > > > >1/ 01 > _______________________________________________ > > > > Babeldoc-devel mailing list > > > > Bab...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > -- > David Glick > Transmit Consulting, Inc > 619-475-4052 > dg...@tr... > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are > available now. > Download today and enter to win an XBOX or Visual > Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
|
From: David G. <dg...@co...> - 2003-08-18 13:47:56
|
What is the timeframe for the 1.2 release? I have some changes I'm working on right now for the journalbrowser that I was planning to check in tonight or tomorrow, but I don't want to impact the 1.2 release. On Monday 18 August 2003 6:06 am, Bruce McDonald wrote: > Yes I did, > > Heres what I think we can do to get this to work: > > Add a reference in the description to an example you have manually entered > after the pipelinestages get included. I am very leary about redoing the > documentation / configinfo stuff at this stage before 1.2 goes live. > > regards, > Bruce > > On Monday 18 August 2003 08:09 am, David Glick wrote: > > Excellent suggestion! I'll try to get this fixed today. > > > > On a totally unrelated note, have you had a chance to review my post > > regarding the documentation? I'd like to get some updates in, but I'm > > not sure which direction to proceed. > > > > > > Thanks, > > > > David > > > > On Sunday 17 August 2003 10:56 pm, Bruce McDonald wrote: > > > David, > > > > > > In the mentioned class you cast the journal to SimpleJournal - why dont > > > you just expand the interface to accomodate what you need - it could > > > fail with SqlJournal. > > > > > > regards, > > > Bruce. > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > > > Data Reports, E-commerce, Portals, and Forums are available now. > > > Download today and enter to win an XBOX or Visual Studio .NET. > > > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_0 > > >1/ 01 _______________________________________________ > > > Babeldoc-devel mailing list > > > Bab...@li... > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |
|
From: David G. <dg...@co...> - 2003-08-18 12:02:48
|
Excellent suggestion! I'll try to get this fixed today. On a totally unrelated note, have you had a chance to review my post regarding the documentation? I'd like to get some updates in, but I'm not sure which direction to proceed. Thanks, David On Sunday 17 August 2003 10:56 pm, Bruce McDonald wrote: > David, > > In the mentioned class you cast the journal to SimpleJournal - why dont you > just expand the interface to accomodate what you need - it could fail with > SqlJournal. > > regards, > Bruce. > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |
|
From: Bruce M. <br...@mc...> - 2003-08-18 05:56:09
|
David, In the mentioned class you cast the journal to SimpleJournal - why dont you just expand the interface to accomodate what you need - it could fail with SqlJournal. regards, Bruce. |
|
From: <dgl...@us...> - 2003-08-18 00:28:14
|
Update of /cvsroot/babeldoc/babeldoc/modules/core/config/i18n In directory sc8-pr-cvs1:/tmp/cvs-serv16859/modules/core/config/i18n Modified Files: messages.properties Log Message: Protect journal integrity by converting harmful characters into html equivalents Index: messages.properties =================================================================== RCS file: /cvsroot/babeldoc/babeldoc/modules/core/config/i18n/messages.properties,v retrieving revision 1.22 retrieving revision 1.23 diff -C2 -d -r1.22 -r1.23 *** messages.properties 17 Aug 2003 22:34:47 -0000 1.22 --- messages.properties 18 Aug 2003 00:23:21 -0000 1.23 *************** *** 388,392 **** core.pipeline.stage.externalapplication.opt.pipein=Pipe the response into the document in the attribute ExternalApplicationResponse ! core.pipeline.stage.journalupdate.description=This pipeline stage writes a message into the journal. This message will be displayed when viewed with the journal tool. core.pipeline.stage.journalupdate.opt.message=The message to write to the Journal core.pipeline.stage.journalupdate.error.message=No journal message --- 388,392 ---- core.pipeline.stage.externalapplication.opt.pipein=Pipe the response into the document in the attribute ExternalApplicationResponse ! core.pipeline.stage.journalupdate.description=This pipeline stage writes a message into the journal that can be viewed with the journal tool (babeldoc journal). Please note that journal entries should be one line long and contain no quotes, commas, or newlines. If these characters are detected, they will be translated into their HTML equivalents to prevent 'bad things' from happening to the journal tool. However, the output from the journal tool will most likely not be what you are expecting. core.pipeline.stage.journalupdate.opt.message=The message to write to the Journal core.pipeline.stage.journalupdate.error.message=No journal message |