advertisement

Article:
  An Open Source File Updater
Subject:   Re: Appreciated
Date:   2001-05-31 17:20:34
From:   simon450
Response to: Appreciated

The XML version will hopefully have a good update preparation tool (which works at the moment, but can't do things like copy and paste things because it relies on dialog boxes) which allows you to edit and create updates.


At the moment I am trying to avoid anything else which operates on the older configuration file. However, if you want to try to set up a server, I suggest you download update9.txt and use it as a template. The file format is not extremely difficult to understand, although that might just be my opinion because I have been working with it on a daily basis for a few months.


I don't know that much Perl, if that accounts for the problems with the CGI. I'm not even sure how to create an XML version of the update submission CGI.


BTW, the update submission tool does work on SourceForge. I use it to put the updates up. However, some strange characters (at least on the server side) end up in the directions sometimes.


Sometime soon I'm hoping to have time to read "Learning Perl" and at that point I'll try to improve the CGI.
Full Threads Oldest First

Showing messages 1 through 3 of 3.

  • CarbonLib 1.3.1 breaks XML OSAX
    2001-06-01 15:57:43  Corvus [Reply | View]

    I installed CarbonLib 1.3.1 from Apple's Software Update to OS 9.1, and now my machine crashes on startup. Removing the XML Tools.osax from the Scripting Additions folder fixes it. Take a look at this before implementing the XML format updater.
    • CarbonLib 1.3.1 breaks XML OSAX
      2003-05-12 12:12:27  anonymous2 [Reply | View]

    • Re: CarbonLib 1.3.1 breaks XML OSAX
      2001-06-03 01:05:01  simon450 [Reply | View]

      Hmm... I believe that I'm using CarbonLib 1.3.1 just fine, but it may be an item I haven't upgraded for test purposes (I wouldn't be able to test IntelliDate if I had a completely up-to-date system, would I?). I can't check right now because I'm half way around the globe from my machine in China.

      I think that the problem may lie in the version of the XML OSAX you are using. Try using the one which doesn't have the .osax extension. I don't think that that one's carbonized in the first place.

      Updates for the IntelliDate files may be a little slow while I'm here.