Timo Baur

Show:

What's happening?

  • GeoMaint

    faloondev committed patchset 8 of module geomaint to the GeoMaint CVS repository, changing 1 files.

    2007-08-02 13:05:09 UTC in GeoMaint

  • GeoMaint

    faloondev committed patchset 7 of module geomaint to the GeoMaint CVS repository, changing 4 files.

    2007-08-01 13:12:35 UTC in GeoMaint

  • GeoMaint

    faloondev committed patchset 6 of module geomaint to the GeoMaint CVS repository, changing 1 files.

    2007-05-31 15:14:19 UTC in GeoMaint

  • GeoMaint

    faloondev committed patchset 5 of module geomaint to the GeoMaint CVS repository, changing 2 files.

    2007-05-31 13:25:39 UTC in GeoMaint

  • change system requirements in documentation to GT 4.0.2

    the provider is working under 4.0.2 though, it may be necessary in 4.0.2 to change libexec/infoprovider/site-provider.pl to use the absolute path of site-provider.pl ------------------------------ java.io.IOException: libexec/infoprovider/site-provider.pl: not found > > You can try to fix the error by inserting the absolute path of the file > site-provider.pl in the file...

    2007-02-28 14:09:15 UTC in GeoMaint

  • check coordinate entries for correctness

    there should be a check for correct entries in the geocoordinates. For example, numbers like 07.31 are not interpreted correctly by GoogleMaps and require a workaround string that costs a lot of xslt-processing time while generating the javascript. So, the provider should check that coordinates are sent in the form [1-9][0-9]*.[1-9]* e.g. 7.31 instead of 07.31.

    2007-02-28 12:17:32 UTC in GeoMaint

  • deinstallation

    there should be an easy method to deinstall the provider.

    2007-02-28 09:18:16 UTC in GeoMaint

  • Comment: we should force entries in site.conf to UTF-8

    To see the problem from the webmds download this in Firefox: http://lxgrid02.lrz-muenchen.de:8080/webmds/webmds?info=indexinfo and then choose view source, change the character encoding to UTF-8 in the new window, to ensure that the browser automatic encoding is not used.

    2007-02-27 15:34:46 UTC in GeoMaint

  • Comment: we should force entries in site.conf to UTF-8

    The problem with this is that some (all should...) XML-parsers don't accept the document as correct and throws an exception.

    2007-02-27 15:32:42 UTC in GeoMaint

  • we should force entries in site.conf to UTF-8

    it seems like I'm receiving non-UTF-8 characters within the XML-file even though it says that the document is UTF-8 encoded. Regionales Rechenzentrum f�r Niedersachsen der Gottfried Wilhelm Leibniz Universit�t Hannover.

    2007-02-27 15:30:07 UTC in GeoMaint

About Me

  • 2002-06-13 (7 years ago)
  • 562283
  • faloondev (My Site)
  • Timo Baur

Send me a message