GNUe Traffic #99 For 10 Nov 2003

                             By Arturas Kriukovas

Table Of Contents

  * Standard Format
  * Text Format
  * XML Source
  * Introduction
  * Threads Covered

    1. 4 Nov 2003  Unicode (UTF-8) printing
    2. 4 Nov 2003  GNUe on Debian
    3. 5 Nov 2003  GTrigger splits
    4. 7 Nov 2003  TriggerError renamed to LangIfError

Introduction

This covers the three main mailing lists for the GNU Enterprise (http://
www.gnuenterprise.org) project, plus the #gnuenterprise IRC channel.

1. Unicode (UTF-8) printing

4 Nov 2003 Archive Link: "[IRC] 04 Nov 2003"

People: Chan Min Wai, Jan Ischebeck

Chan Min Wai (dcmwai) asked how to "print the UTF-8 grd and the utf-8 db" (
"printing on an html files or PDF files" ). He was talking "about the
month2.grd which all unicode is UTF-8 when using grcvs to get and html /pdf"
"the output isn't utf-8" . Jan Ischebeck (siesel) solved the problem by
correcting pdf.py for pdfs and setting "textEncoding=utf-8 in gnue.conf
[common] section" .

2. GNUe on Debian

4 Nov 2003 Archive Link: "[IRC] 04 Nov 2003"

People: Reinhard M?ller, Jeff Bailey

Reinhard M?ller (reinhard) announced that "common, forms, designer, and reports
have made it into sarge, appserver and navigator have entered sid" . Thanks to
Jeff Bailey!!!

3. GTrigger splits

5 Nov 2003 Archive Link: "[IRC] 05 Nov 2003"

People: Jan Ischebeck, James Thompson, James Thompson

Jan Ischebeck (siesel) announced he was "beginning to split the GTrigger code
into language specific and trigger specific parts" to achieve "two goals: 1.
make it easy to reuse from appserver 2. add new trigger languages" . He of
course has faced some problems - a naming issue: what about putting "the
language specific stuff in subdirectorys of gnue/common/logic/connector like
gnue/common/logic/connector/python/" . The "connector" was chosen as "language
connector". James Thompson (jamest) noticed that "connector makes me think of
networking for some reason, same could be said for logic/interface" . Jan
"thought of adding a "remote connector" which calls the trigger on the
application server" . Nothing application specific should go in there. James
liked the split idea.

Another problem - namespace issue - "the namespace stuff is very python
specific" . "So we'd end up with a generic trigger system that manages
triggers" .

On mailing list Jan announced available support for ECMAscript triggers,
support for C# is planned.

4. TriggerError renamed to LangIfError

7 Nov 2003 Archive Link: "[IRC] 07 Nov 2003"

People: Jan Ischebeck

Jan Ischebeck (siesel) said he had stopped using TriggerError, "as it would be
"Trigger" specific" . He had named it to "LangIfError, like Language Interface
Error" . "if an error in a trigger /procedure occurs it raises an XXX Error,
which is catched by the Language Interface and replaced with a LangIfError.
Depending on the time the error occurs its an LangIfRuntime or an
LangIfCompileError which are both inheriting LangIfError, so you just have to
name it in an except statement" .

 

 

 

 

 

 

                                Sharon And Joy
                                        

Kernel Traffic is grateful to be developed on a computer donated by Professor
Greg Benson and Professor Allan Cruse in the Department of Computer Science at
the University of San Francisco. This is the same department that invented
FlashMob Computing. Kernel Traffic is hosted by the generous folks at
kernel.org. All pages on this site are copyright their original authors, and
distributed under the terms of the GNU General Public License version 2.0.

</html>