https://scarlet.deltasoft.com/api.php?action=feedcontributions&feedformat=atom&user=SteveB 2026-08-20T11:15:23Z User contributions MediaWiki 1.46.0 https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=523 2010-08-26T13:23:24Z

<p>SteveB: </p> <hr /> <div>Welcome to ScarletDME.org. [[ScarletDME]] is a OpenSource [[multivalue|MultiValue]] database, a community fork of [[OpenQM]] originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[ScarletDME]] and contribute to [[OpenQM]]. While there are no longer regular official releases from [[Ladybridge]] we aim to support and develop for Scarlet to help our commercial sister, While providing a Free and open platform for Multi value development. <br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL if you wish to encourage and allow incorporation into proprietary products. Contributors to [[ScarletDME]] are welcome to submit changes back to Ladybridge as well, for inclusion in Commercial QM. See [[Commercial submissions]] for details. We encourage submission to Ladybridge, the founder of this MultiValue database. We do recognise their processes are not as easy as traditional GPL projects. So we simply offer an easier forum for development with less stringent controls on contribution and participation.<br /> <br /> The server is a kvm virtual machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> '''This server is DOWN/SLOW around 04:00GMT nightly for 15mins while backing up.'''<br /> <br /> ==For Users==<br /> *[[Downloads]]: Source tarball and package builds for key platforms<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> *[[QMBASIC Enhancements]] - QMBASIC features that are custom or were not part of the original GPL release.<br /> *[http://www.scarletdme.org/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[[Documentation]] - Documented differences from the Commercial Documentation (Check here first, then below)<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *General support email group: [http://groups.google.co.uk/group/scarletdme Register] then mailto:scarletdme@googlegroups.com <br /> *IRC Chat: irc://irc.efnet.org/openqm or java client http://www.scarletdme.org/chat/<br /> <br /> ====Supporting Projects====<br /> Various external projects that provide tools for or API's into OpenQM<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> *[[PHP_Native_API|PHP Native API module]]<br /> *[[C++ Wrapper]]<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> <br /> ==For Developers==<br /> For those that want to contribute to OpenQM GPL project.<br /> *Subversion repository: https://scarletdme.org/svn/qmvdb/ - [[HOWTO]] <br /> *Development email group: [http://www.scarletdme.org/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@dev.scarletdme.org<br /> *[[Development snapshots]] - How to obtain, build, and upgrade using the snapshots.<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> *[[Installers]] - Installing scripts/programs or package systems<br /> *[[Commercial submissions]] - Sending stuff to Ladybridge<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of Scarlet, then send it to the [http://groups.google.co.uk/group/scarletdme general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of Scarlet (eg. php5 module) then send it to the [http://www.scarletdme.org/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === External Resources ===<br /> * [[Installations]] - Places where GPL OpenQM is in use (I'm attempting to create a new section for this) - http://capersqm.dnsalias.net/<br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module (C Wrapper) <br /> * [http://sourceforge.net/projects/jd3 JD3] is a socket based server for D3 ported to QM <br /> * [http://www.billabong-services.co.uk/jd3/jd3php.html David Patterson's guide to using PHP with JD3] David's original page has disappeared (unable to contact), so here's the google cache<br /> * [http://www.billabong-services.co.uk/jd3/jd3java.html David Patterson's guide to using Java with JD3] google cache again<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Talk:Branding_tasks&diff=425 2009-05-15T07:10:49Z

<p>SteveB: </p> <hr /> <div>Change the @QMSYS at-var (note: change in F-type VOC entries, too). Change to '@SYS'? <br /> <br /> :[[User:Diccon|Diccon]] @SYS sounds fine to me, either that or @SYSDIR<br /> ::[[User:Diccon|Diccon]] 01:35, 15 May 2009 (UTC) This one is going to be a bastard, 56 matches by grep, in both text source files, and impressivly it found references in Binary files like the VOC too (Yeay Grep). <br /> <br /> <br /> Change '/usr/qmsys' to something more appropriate.<br /> <br /> :[[User:Diccon|Diccon]] Suggestions? /usr/scarlet /usr/scarletsys, easy and very subjective, as it depends on the config file. Only applicable to installers and packages.<br /> <br /> <br /> Change '/etc/qmconfig' to something more appropriate. [[User:Diccon|Diccon]] I got this one<br /> <br /> :[[User:Diccon|Diccon]] Suggests /etc/scarlet.conf, more in line with traditional Linux conf names<br /> <br /> ::[[User:Diccon|Diccon]] 01:18, 15 May 2009 (UTC) Also needs QMCONF environment variable renaming, going for SCARLET_CONF for now.<br /> <br /> Change the various program names from 'qm*' (except QMClient?).<br /> <br /> :[[User:Diccon|Diccon]]Trickey one this, to what? i suggest short names. &quot;scarlet&quot;, &quot;scrlt&quot;, &quot;sdme&quot;??<br /> <br /> [[User:SteveB|SteveB]] 07:10, 15 May 2009 (UTC) sq for sqarlet? ugly but functional</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Commercial_submissions&diff=408 2009-04-29T16:56:32Z

<p>SteveB: New page: In summary you need to print and fax or mail an agreement to Ladybridge before emailing submissions to support@openqm.com Full details at: http://www.openqm.com/cgi/lbscgi.exe?X=vve55uaw4...</p> <hr /> <div>In summary you need to print and fax or mail an agreement to Ladybridge before emailing submissions to support@openqm.com<br /> <br /> Full details at: http://www.openqm.com/cgi/lbscgi.exe?X=vve55uaw42&amp;t0=h&amp;t1=devinfo</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=407 2009-04-29T16:50:17Z

<p>SteveB: /* For Developers */</p> <hr /> <div>gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> '''This server is DOWN/SLOW around 04:00GMT nightly for 15mins while backing up.'''<br /> <br /> ==For Users==<br /> *[[Downloads]]: Source tarball and package builds for key platforms<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> *[[QMBASIC Enhancements]] - QMBASIC features that are custom or were not part of the original GPL release.<br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *IRC Chat: irc://irc.efnet.org/openqm or java client http://gpl.openqm.com/chat/<br /> ====Supporting Projects====<br /> Various external projects that provide tools for or API's into OpenQM<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> *[[PHP_Native_API|PHP Native API module]]<br /> *[[C++ Wrapper]]<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> <br /> ==For Developers==<br /> For those that want to contribute to OpenQM GPL project.<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *[[Development snapshots]] - How to obtain, build, and upgrade using the snapshots.<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> *[[Installers]] - Installing scripts/programs or package systems<br /> *[[Commercial submissions]] - Sending stuff to Ladybridge<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === External Resources ===<br /> * [[Installations]] - Places where GPL OpenQM is in use (I'm attempting to create a new section for this) - http://capersqm.dnsalias.net/<br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module (C Wrapper) <br /> <br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=368 2009-04-14T07:20:12Z

<p>SteveB: /* For Users */</p> <hr /> <div>gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> '''This server is DOWN/SLOW around 04:00GMT nightly for 15mins while backing up.'''<br /> <br /> ==For Users==<br /> *[[Downloads]]: Source tarball and package builds for key platforms<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> *[[QMBASIC Enhancements]] - QMBASIC features that are custom or were not part of the original GPL release.<br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *IRC Chat: irc://irc.efnet.org/openqm or java client http://gpl.openqm.com/chat/<br /> ====Supporting Projects====<br /> Various external projects that provide tools for or API's into OpenQM<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> *[[PHP_Native_API|PHP Native API module]]<br /> *[[C++ Wrapper]]<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> <br /> ==For Developers==<br /> For those that want to contribute to OpenQM GPL project.<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *[[Development snapshots]] - How to obtain, build, and upgrade using the snapshots.<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> *[[Installers]] - Installing scripts/programs or package systems<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === External Resources ===<br /> * [[Installations]] - Places where GPL OpenQM is in use (I'm attempting to create a new section for this) - http://capersqm.dnsalias.net/<br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module (C Wrapper) <br /> <br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Subversion_Repository:_HOWTO&diff=330 2009-04-05T20:46:52Z

<p>SteveB: /* Acquiring rights to commit */</p> <hr /> <div>== Introduction ==<br /> <br /> === Terminology ===<br /> <br /> #Checkout - downloads a copy for the first time<br /> #'''Update''' - downloads your copy with any changes in the repository<br /> #'''Commit''' - uploads any changes you made in your copy to the repository<br /> #Import - upload - can be replaced by a combination of update/commit<br /> <br /> repo - repository<br /> <br /> depo - your copy<br /> <br /> === Acquiring rights to commit ===<br /> <br /> To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com or you can choose your own password by sending the output of the following command to an admin ([[Admin_Team]] and look for subversion)<br /> <br /> htpasswd -n yourdesiredusername<br /> <br /> then any gpl.openqm.com server admin (with root or sudo access) can grant user yourdesiredusername access with the following command. It will ask for the password which is hashed password after the : in the output of the above/previous htpasswd command.<br /> <br /> htpasswd /etc/subversion/passwd yourdesiredusername<br /> <br /> Then commit with something like the following. username is usually cached and only required the first time.<br /> <br /> svn --username yourdesiredusername commit<br /> <br /> == Command Line User Interface ==<br /> <br /> Assumes you have already installed Subversion.<br /> <br /> Looks complicated but boils down to issuing two commands. One to checkout the project or to update your already checked project. Two to commit your changes.<br /> <br /> === Walkthrough ===<br /> <br /> Make a working directory if you don’t have one<br /> <br /> mkdir qmvdb<br /> <br /> OR, if you already checked out a copy of the repo, just change into your working directory<br /> <br /> cd qmvdb<br /> <br /> If you just made the working directory then use svn checkout to get a copy of the project (all branches, tags and trunk of project openqm in this example)<br /> <br /> svn checkout https://gpl.openqm.com/svn/qmvdb/openqm<br /> <br /> OR, if you already checked out a copy of the repo, then best to ensure you are working on the latest version to avoid later work resolving any conflicts with other people's edits.<br /> <br /> svn update<br /> <br /> Find the file you want to work on (dh_ak.c in this example)<br /> <br /> find . -name dh_ak.c<br /> <br /> See the list of alternatives in different branches<br /> <br /> ./openqm/tags/release-2.6.6/gplsrc/dh_ak.c<br /> ./openqm/branches/workdevbranch1/gplsrc/dh_ak.c<br /> ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Decide to edit version of the file in the trunk directly. Only put tested changes in the trunk because people expect it to be stable at all times.<br /> <br /> vi ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Example edit:<br /> <br /> if (big_dict_rec)<br /> {<br /> /*SB patch from AC from MP/Sep08*/<br /> /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> if (header.file_version &lt; 2)<br /> {<br /> ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> }<br /> else<br /> {<br /> ak_header.itype_ptr = 2;<br /> }<br /> } <br /> <br /> Optionally check that nobody else has, since you last got the file, edited and committed the same section that you edited - and reconcile any conflicts interactively if necessary.<br /> <br /> svn update<br /> <br /> Optionally ask subversion to show you a diff of all changes you made in the whole tree<br /> <br /> svn diff<br /> <br /> &lt;pre&gt;<br /> Index: openqm/trunk/gplsrc/dh_ak.c<br /> ===================================================================<br /> --- openqm/trunk/gplsrc/dh_ak.c (revision 10)<br /> +++ openqm/trunk/gplsrc/dh_ak.c (working copy)<br /> @@ -1892,7 +1892,16 @@<br /> big_dict_rec = (dict_rec_len &gt; AK_CODE_BYTES);<br /> if (big_dict_rec)<br /> {<br /> - ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;<br /> + /*SB patch from AC from MP/Sep08*/<br /> + /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> + if (header.file_version &lt; 2)<br /> + {<br /> + ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> + }<br /> + else<br /> + {<br /> + ak_header.itype_ptr = 2;<br /> + }<br /> }<br /> else /* Short enough to store in AK header */<br /> {<br /> &lt;/pre&gt;<br /> <br /> Commit your changes WITH A CONCISE COMMENT ABOUT ITS PURPOSE so people can get a good idea by looking at the log. This is so important that if you don't include a log message, Subversion will ask you for one. It is suggested that you do ''not'' include a message on the command line, so you can use the editor of your choice to write the message. The key advantage to this (other than being able to write multiline comments more easily) is that it shows you *exactly* which files it's going to commit (along with why, if you can read the codes). If you've forgotten something, or are commiting something you didn't mean to, you can just quit the editor and Subversion will ask you if you want to quit. It helps to avoid unnecessary commits and embarrassing log comments. To commit using this method, use<br /> <br /> svn --username yourname commit trunk/gplsrc/dh_ak.c<br /> <br /> or, to write your message on the command line,<br /> <br /> svn --username yourname commit -m &quot;Bug fix for indexing on complex fields in non-VERSION 1 files from MP in Sep08 via AC&quot;<br /> <br /> If you made an edit to a file and then backed out the change, you can easily revert back to the svn version of the file using &quot;revert&quot;:<br /> svn revert gplsrc/op_sh.c<br /> <br /> This would replace your copy of op_sh.c with the one from the source repository.<br /> <br /> Note that in order for svn to open your editor, you need to have the SVN_EDITOR environment variable set. You can do this by entering the following command at the shell prompt. Alternately, you can add the command to your .bashrc file so you don't need to remember to re-enter the command each time you log in.<br /> export SVN_EDITOR=&lt;your editor of choice&gt;<br /> <br /> == Graphic User Interface - Windows Tortoise ==<br /> <br /> === Walkthrough ===<br /> <br /> http://tortoisesvn.tigris.org/<br /> <br /> This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.<br /> <br /> The interesting bits of source code management automatically jump out at you later when two people work on the same SECTION of the same file at the same time ie between checkout/update and commit.<br /> <br /> *You commit a file which has also committed by someone else AFTER you checked it out<br /> *You update your depo from repo and someone has committed changes to a file that you have already locally changed.<br /> <br /> In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.<br /> <br /> === Other tools===<br /> <br /> Visual Studio - http://ankhsvn.open.collab.net/<br /> <br /> Eclipse - http://subclipse.tigris.org/<br /> <br /> Netbeans supports it natively now too. &lt;Diccon&gt; Bean a life saver. (Can we have a few hints, Diccon?)<br /> <br /> === Installation === <br /> <br /> http://tortoisesvn.net/downloads<br /> <br /> Might need a reboot<br /> <br /> === Checking Out ===<br /> <br /> Right click on your desktop and choose SVN CHECKOUT<br /> <br /> Fill in the details<br /> <br /> URL? https://gpl.openqm.com/svn/qmvdb<br /> <br /> Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT<br /> <br /> Click OK<br /> <br /> Do you want to create the directory? Yes<br /> <br /> Do you want to accept the unsigned certificate? Yes<br /> <br /> Wait while it downloads the whole repository<br /> <br /> Finished: OK<br /> <br /> After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo<br /> <br /> Subversion puts a hidden folder called .svn in any folder it is managing<br /> <br /> === Committing ===<br /> <br /> #Open the folder TESTIT<br /> #Create a file called testing.txt anywhere in the folder structure<br /> #Close the folder and notice that it has a big red ! on it showing that something is commitable<br /> #Right click on the TESTIT folder (or indeed any subfolder)<br /> #Choose SVN Commit<br /> #It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All<br /> #It helps to add a message explaining why you are committing<br /> #Click OK<br /> #Enter your committers username and password<br /> #Screen showing upload progress<br /> #Click OK when finished and note that the red ! has changed back into a green tick<br /> <br /> <br /> == Committing Binary Files like VOC/ERRMSG ==<br /> <br /> To subversion, VOC/ERRMSG (and other files? which?) are deemed to be &quot;binary&quot; rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.<br /> <br /> The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.<br /> <br /> The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.<br /> <br /> If you do not do follow one of the procedures below then when you finally come to UPDATE or COMMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files. Depending on how much work you have dont this could be mildly irritating or extremely inconvenient.<br /> <br /> PRACTICAL SOLUTION FOR NOW<br /> <br /> Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.<br /> <br /> #Get a lock on the file (or more likely folder) that you want to edit<br /> #SVN UPDATE<br /> #Edit the file<br /> #SVN COMMIT '''or''' release the lock on the file<br /> <br /> By default, a commit releases the lock. If you want to commit but keep the lock, use '--no-unlock' on the command line, or check the checkbox 'keep locks' in TortoiseSVN.<br /> There might be a combined LOCK&amp;UPDATE command but I don't know it.<br /> <br /> Command line<br /> <br /> svn lock files -m &quot;Reason for locking these files&quot;<br /> <br /> Tortoise<br /> <br /> [[image:svnlock.jpg]]<br /> <br /> [[image:svnrelease.jpg]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Subversion_Repository:_HOWTO&diff=329 2009-04-05T20:44:48Z

<p>SteveB: /* Walkthrough */</p> <hr /> <div>== Introduction ==<br /> <br /> === Terminology ===<br /> <br /> #Checkout - downloads a copy for the first time<br /> #'''Update''' - downloads your copy with any changes in the repository<br /> #'''Commit''' - uploads any changes you made in your copy to the repository<br /> #Import - upload - can be replaced by a combination of update/commit<br /> <br /> repo - repository<br /> <br /> depo - your copy<br /> <br /> === Acquiring rights to commit ===<br /> <br /> To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com or you can choose your own password by sending the output of the following command to an admin ([[Admin_Team]] and look for subversion)<br /> <br /> htpasswd -n yourdesiredusername<br /> <br /> then any gpl.openqm.com server admin (with root or sudo access) can grant user yourdesiredusername access with the following command. It will ask for the password which is hashed password after the : in the output of the above/previous htpasswd command.<br /> <br /> htpasswd /etc/subversion/passwd yourdesiredusername<br /> <br /> == Command Line User Interface ==<br /> <br /> Assumes you have already installed Subversion.<br /> <br /> Looks complicated but boils down to issuing two commands. One to checkout the project or to update your already checked project. Two to commit your changes.<br /> <br /> === Walkthrough ===<br /> <br /> Make a working directory if you don’t have one<br /> <br /> mkdir qmvdb<br /> <br /> OR, if you already checked out a copy of the repo, just change into your working directory<br /> <br /> cd qmvdb<br /> <br /> If you just made the working directory then use svn checkout to get a copy of the project (all branches, tags and trunk of project openqm in this example)<br /> <br /> svn checkout https://gpl.openqm.com/svn/qmvdb/openqm<br /> <br /> OR, if you already checked out a copy of the repo, then best to ensure you are working on the latest version to avoid later work resolving any conflicts with other people's edits.<br /> <br /> svn update<br /> <br /> Find the file you want to work on (dh_ak.c in this example)<br /> <br /> find . -name dh_ak.c<br /> <br /> See the list of alternatives in different branches<br /> <br /> ./openqm/tags/release-2.6.6/gplsrc/dh_ak.c<br /> ./openqm/branches/workdevbranch1/gplsrc/dh_ak.c<br /> ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Decide to edit version of the file in the trunk directly. Only put tested changes in the trunk because people expect it to be stable at all times.<br /> <br /> vi ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Example edit:<br /> <br /> if (big_dict_rec)<br /> {<br /> /*SB patch from AC from MP/Sep08*/<br /> /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> if (header.file_version &lt; 2)<br /> {<br /> ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> }<br /> else<br /> {<br /> ak_header.itype_ptr = 2;<br /> }<br /> } <br /> <br /> Optionally check that nobody else has, since you last got the file, edited and committed the same section that you edited - and reconcile any conflicts interactively if necessary.<br /> <br /> svn update<br /> <br /> Optionally ask subversion to show you a diff of all changes you made in the whole tree<br /> <br /> svn diff<br /> <br /> &lt;pre&gt;<br /> Index: openqm/trunk/gplsrc/dh_ak.c<br /> ===================================================================<br /> --- openqm/trunk/gplsrc/dh_ak.c (revision 10)<br /> +++ openqm/trunk/gplsrc/dh_ak.c (working copy)<br /> @@ -1892,7 +1892,16 @@<br /> big_dict_rec = (dict_rec_len &gt; AK_CODE_BYTES);<br /> if (big_dict_rec)<br /> {<br /> - ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;<br /> + /*SB patch from AC from MP/Sep08*/<br /> + /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> + if (header.file_version &lt; 2)<br /> + {<br /> + ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> + }<br /> + else<br /> + {<br /> + ak_header.itype_ptr = 2;<br /> + }<br /> }<br /> else /* Short enough to store in AK header */<br /> {<br /> &lt;/pre&gt;<br /> <br /> Commit your changes WITH A CONCISE COMMENT ABOUT ITS PURPOSE so people can get a good idea by looking at the log. This is so important that if you don't include a log message, Subversion will ask you for one. It is suggested that you do ''not'' include a message on the command line, so you can use the editor of your choice to write the message. The key advantage to this (other than being able to write multiline comments more easily) is that it shows you *exactly* which files it's going to commit (along with why, if you can read the codes). If you've forgotten something, or are commiting something you didn't mean to, you can just quit the editor and Subversion will ask you if you want to quit. It helps to avoid unnecessary commits and embarrassing log comments. To commit using this method, use<br /> <br /> svn --username yourname commit trunk/gplsrc/dh_ak.c<br /> <br /> or, to write your message on the command line,<br /> <br /> svn --username yourname commit -m &quot;Bug fix for indexing on complex fields in non-VERSION 1 files from MP in Sep08 via AC&quot;<br /> <br /> If you made an edit to a file and then backed out the change, you can easily revert back to the svn version of the file using &quot;revert&quot;:<br /> svn revert gplsrc/op_sh.c<br /> <br /> This would replace your copy of op_sh.c with the one from the source repository.<br /> <br /> Note that in order for svn to open your editor, you need to have the SVN_EDITOR environment variable set. You can do this by entering the following command at the shell prompt. Alternately, you can add the command to your .bashrc file so you don't need to remember to re-enter the command each time you log in.<br /> export SVN_EDITOR=&lt;your editor of choice&gt;<br /> <br /> == Graphic User Interface - Windows Tortoise ==<br /> <br /> === Walkthrough ===<br /> <br /> http://tortoisesvn.tigris.org/<br /> <br /> This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.<br /> <br /> The interesting bits of source code management automatically jump out at you later when two people work on the same SECTION of the same file at the same time ie between checkout/update and commit.<br /> <br /> *You commit a file which has also committed by someone else AFTER you checked it out<br /> *You update your depo from repo and someone has committed changes to a file that you have already locally changed.<br /> <br /> In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.<br /> <br /> === Other tools===<br /> <br /> Visual Studio - http://ankhsvn.open.collab.net/<br /> <br /> Eclipse - http://subclipse.tigris.org/<br /> <br /> Netbeans supports it natively now too. &lt;Diccon&gt; Bean a life saver. (Can we have a few hints, Diccon?)<br /> <br /> === Installation === <br /> <br /> http://tortoisesvn.net/downloads<br /> <br /> Might need a reboot<br /> <br /> === Checking Out ===<br /> <br /> Right click on your desktop and choose SVN CHECKOUT<br /> <br /> Fill in the details<br /> <br /> URL? https://gpl.openqm.com/svn/qmvdb<br /> <br /> Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT<br /> <br /> Click OK<br /> <br /> Do you want to create the directory? Yes<br /> <br /> Do you want to accept the unsigned certificate? Yes<br /> <br /> Wait while it downloads the whole repository<br /> <br /> Finished: OK<br /> <br /> After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo<br /> <br /> Subversion puts a hidden folder called .svn in any folder it is managing<br /> <br /> === Committing ===<br /> <br /> #Open the folder TESTIT<br /> #Create a file called testing.txt anywhere in the folder structure<br /> #Close the folder and notice that it has a big red ! on it showing that something is commitable<br /> #Right click on the TESTIT folder (or indeed any subfolder)<br /> #Choose SVN Commit<br /> #It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All<br /> #It helps to add a message explaining why you are committing<br /> #Click OK<br /> #Enter your committers username and password<br /> #Screen showing upload progress<br /> #Click OK when finished and note that the red ! has changed back into a green tick<br /> <br /> <br /> == Committing Binary Files like VOC/ERRMSG ==<br /> <br /> To subversion, VOC/ERRMSG (and other files? which?) are deemed to be &quot;binary&quot; rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.<br /> <br /> The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.<br /> <br /> The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.<br /> <br /> If you do not do follow one of the procedures below then when you finally come to UPDATE or COMMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files. Depending on how much work you have dont this could be mildly irritating or extremely inconvenient.<br /> <br /> PRACTICAL SOLUTION FOR NOW<br /> <br /> Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.<br /> <br /> #Get a lock on the file (or more likely folder) that you want to edit<br /> #SVN UPDATE<br /> #Edit the file<br /> #SVN COMMIT '''or''' release the lock on the file<br /> <br /> By default, a commit releases the lock. If you want to commit but keep the lock, use '--no-unlock' on the command line, or check the checkbox 'keep locks' in TortoiseSVN.<br /> There might be a combined LOCK&amp;UPDATE command but I don't know it.<br /> <br /> Command line<br /> <br /> svn lock files -m &quot;Reason for locking these files&quot;<br /> <br /> Tortoise<br /> <br /> [[image:svnlock.jpg]]<br /> <br /> [[image:svnrelease.jpg]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Subversion_Repository:_HOWTO&diff=321 2009-04-04T09:07:19Z

<p>SteveB: /* Acquiring rights to commit */</p> <hr /> <div>== Introduction ==<br /> <br /> === Terminology ===<br /> <br /> #Checkout - downloads a copy for the first time<br /> #'''Update''' - downloads your copy with any changes in the repository<br /> #'''Commit''' - uploads any changes you made in your copy to the repository<br /> #Import - upload - can be replaced by a combination of update/commit<br /> <br /> repo - repository<br /> <br /> depo - your copy<br /> <br /> === Acquiring rights to commit ===<br /> <br /> To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com or you can choose your own password by sending the output of the following command to an admin ([[Admin_Team]] and look for subversion)<br /> <br /> htpasswd -n yourdesiredusername<br /> <br /> then any gpl.openqm.com server admin (with root or sudo access) can grant user yourdesiredusername access with the following command. It will ask for the password which is hashed password after the : in the output of the above/previous htpasswd command.<br /> <br /> htpasswd /etc/subversion/passwd yourdesiredusername<br /> <br /> == Command Line User Interface ==<br /> <br /> Assumes you have already installed Subversion.<br /> <br /> Looks complicated but boils down to issuing two commands. One to checkout the project or to update your already checked project. Two to commit your changes.<br /> <br /> === Walkthrough ===<br /> <br /> Make a working directory if you don’t have one<br /> <br /> mkdir qmvdb<br /> <br /> OR, if you already checked out a copy of the repo, just change into your working directory<br /> <br /> cd qmvdb<br /> <br /> If you just made the working directory then use svn checkout to get a copy of the project (all branches, tags and trunk of project openqm in this example)<br /> <br /> svn checkout https://gpl.openqm.com/svn/qmvdb/openqm<br /> <br /> OR, if you already checked out a copy of the repo, then best to ensure you are working on the latest version to avoid later work resolving any conflicts with other people's edits.<br /> <br /> svn update<br /> <br /> Find the file you want to work on (dh_ak.c in this example)<br /> <br /> find . -name dh_ak.c<br /> <br /> See the list of alternatives in different branches<br /> <br /> ./openqm/tags/release-2.6.6/gplsrc/dh_ak.c<br /> ./openqm/branches/workdevbranch1/gplsrc/dh_ak.c<br /> ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Decide to edit version of the file in the trunk directly. Only put tested changes in the trunk because people expect it to be stable at all times.<br /> <br /> vi ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Example edit:<br /> <br /> if (big_dict_rec)<br /> {<br /> /*SB patch from AC from MP/Sep08*/<br /> /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> if (header.file_version &lt; 2)<br /> {<br /> ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> }<br /> else<br /> {<br /> ak_header.itype_ptr = 2;<br /> }<br /> } <br /> <br /> Optionally check that nobody else has, since you last got the file, edited and committed the same section that you edited - and reconcile any conflicts interactively if necessary.<br /> <br /> svn update<br /> <br /> Optionally ask subversion to show you a diff of all changes you made in the whole tree<br /> <br /> svn diff<br /> <br /> &lt;pre&gt;<br /> Index: openqm/trunk/gplsrc/dh_ak.c<br /> ===================================================================<br /> --- openqm/trunk/gplsrc/dh_ak.c (revision 10)<br /> +++ openqm/trunk/gplsrc/dh_ak.c (working copy)<br /> @@ -1892,7 +1892,16 @@<br /> big_dict_rec = (dict_rec_len &gt; AK_CODE_BYTES);<br /> if (big_dict_rec)<br /> {<br /> - ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;<br /> + /*SB patch from AC from MP/Sep08*/<br /> + /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> + if (header.file_version &lt; 2)<br /> + {<br /> + ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> + }<br /> + else<br /> + {<br /> + ak_header.itype_ptr = 2;<br /> + }<br /> }<br /> else /* Short enough to store in AK header */<br /> {<br /> &lt;/pre&gt;<br /> <br /> Commit your changes WITH A CONCISE COMMENT ABOUT ITS PURPOSE so people can get a good idea by looking at the log. This is so important that if you don't include a log message, Subversion will ask you for one. It is suggested that you do ''not'' include a message on the command line, so you can use the editor of your choice to write the message. The key advantage to this (other than being able to write multiline comments more easily) is that it shows you *exactly* which files it's going to commit (along with why, if you can read the codes). If you've forgotten something, or are commiting something you didn't mean to, you can just quit the editor and Subversion will ask you if you want to quit. It helps to avoid unnecessary commits and embarrassing log comments. To commit using this method, use<br /> svn commit trunk/gplsrc/dh_ak.c<br /> or, to write your message on the command line,<br /> svn commit -m &quot;Bug fix for indexing on complex fields in non-VERSION 1 files from MP in Sep08 via AC&quot;<br /> <br /> If you made an edit to a file and then backed out the change, you can easily revert back to the svn version of the file using &quot;revert&quot;:<br /> svn revert gplsrc/op_sh.c<br /> <br /> This would replace your copy of op_sh.c with the one from the source repository.<br /> <br /> Note that in order for svn to open your editor, you need to have the SVN_EDITOR environment variable set. You can do this by entering the following command at the shell prompt. Alternately, you can add the command to your .bashrc file so you don't need to remember to re-enter the command each time you log in.<br /> export SVN_EDITOR=&lt;your editor of choice&gt;<br /> <br /> == Graphic User Interface - Windows Tortoise ==<br /> <br /> === Walkthrough ===<br /> <br /> http://tortoisesvn.tigris.org/<br /> <br /> This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.<br /> <br /> The interesting bits of source code management automatically jump out at you later when two people work on the same SECTION of the same file at the same time ie between checkout/update and commit.<br /> <br /> *You commit a file which has also committed by someone else AFTER you checked it out<br /> *You update your depo from repo and someone has committed changes to a file that you have already locally changed.<br /> <br /> In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.<br /> <br /> === Other tools===<br /> <br /> Visual Studio - http://ankhsvn.open.collab.net/<br /> <br /> Eclipse - http://subclipse.tigris.org/<br /> <br /> Netbeans supports it natively now too. &lt;Diccon&gt; Bean a life saver. (Can we have a few hints, Diccon?)<br /> <br /> === Installation === <br /> <br /> http://tortoisesvn.net/downloads<br /> <br /> Might need a reboot<br /> <br /> === Checking Out ===<br /> <br /> Right click on your desktop and choose SVN CHECKOUT<br /> <br /> Fill in the details<br /> <br /> URL? https://gpl.openqm.com/svn/qmvdb<br /> <br /> Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT<br /> <br /> Click OK<br /> <br /> Do you want to create the directory? Yes<br /> <br /> Do you want to accept the unsigned certificate? Yes<br /> <br /> Wait while it downloads the whole repository<br /> <br /> Finished: OK<br /> <br /> After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo<br /> <br /> Subversion puts a hidden folder called .svn in any folder it is managing<br /> <br /> === Committing ===<br /> <br /> #Open the folder TESTIT<br /> #Create a file called testing.txt anywhere in the folder structure<br /> #Close the folder and notice that it has a big red ! on it showing that something is commitable<br /> #Right click on the TESTIT folder (or indeed any subfolder)<br /> #Choose SVN Commit<br /> #It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All<br /> #It helps to add a message explaining why you are committing<br /> #Click OK<br /> #Enter your committers username and password<br /> #Screen showing upload progress<br /> #Click OK when finished and note that the red ! has changed back into a green tick<br /> <br /> <br /> == Committing Binary Files like VOC/ERRMSG ==<br /> <br /> To subversion, VOC/ERRMSG (and other files? which?) are deemed to be &quot;binary&quot; rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.<br /> <br /> The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.<br /> <br /> The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.<br /> <br /> If you do not do follow one of the procedures below then when you finally come to UPDATE or COMMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files. Depending on how much work you have dont this could be mildly irritating or extremely inconvenient.<br /> <br /> PRACTICAL SOLUTION FOR NOW<br /> <br /> Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.<br /> <br /> #Get a lock on the file (or more likely folder) that you want to edit<br /> #SVN UPDATE<br /> #Edit the file<br /> #SVN COMMIT '''or''' release the lock on the file<br /> <br /> By default, a commit releases the lock. If you want to commit but keep the lock, use '--no-unlock' on the command line, or check the checkbox 'keep locks' in TortoiseSVN.<br /> There might be a combined LOCK&amp;UPDATE command but I don't know it.<br /> <br /> Command line<br /> <br /> svn lock files -m &quot;Reason for locking these files&quot;<br /> <br /> Tortoise<br /> <br /> [[image:svnlock.jpg]]<br /> <br /> [[image:svnrelease.jpg]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Wish_list&diff=320 2009-03-30T13:25:00Z

<p>SteveB: Add Voting Columns</p> <hr /> <div>Things we need or want.<br /> <br /> If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.<br /> <br /> To keep in touch with this slowly evolving agenda register, making sure your preferences[http://gpl.openqm.com/wiki/Special:Preferences] include &quot;E-mail me when a page on my watchlist is changed&quot;, and that you are logged in, and click the &quot;watch&quot; tab at the top of this page.<br /> <br /> ==Development==<br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Wished<br /> ! Diccon<br /> ! Karaken12<br /> ! Ashley<br /> ! DanW<br /> ! SteveB<br /> ! Geneb<br /> ! 7<br /> ! 8<br /> ! 9<br /> ! 0<br /> ! 1<br /> ! 2<br /> ! 3<br /> ! 4<br /> ! 5<br /> ! 6<br /> ! 7<br /> ! 8<br /> ! 9<br /> ! 0<br /> |-<br /> |Accumulate Existing bugfixes into subversion - '''IMPORTANT'''; Can anyone with existing bug fixes please email [[Admin Team]] or commit them into our subversion trunk [[HOWTO]]. (1 Done Thanks Ashley)<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Lastest version DEB package<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |QM API list compression<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |XML Database layer<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |XQuery Engine<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Interface to Maverick running inside a JVM in a web-browser so as to implement client-side form processing in multivalue BASIC.<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Specific flavoured compatibility modes (eg D3 mode, Sequoia mode)<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Code porting program, similar to jBase's PORT.BAS (ideal for Perl regexp?)<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |QM BASIC Subversion client wrapper - Simple way to get Pickies onboard. - '''TAKEN''' - [[User:Karaken12|Karaken12]] I've already done this, although it does need some cleaning up.<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |QM Virtual File System (VFS) for some SQL database(s)<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Pref to set SCROLL option as default ON for all access statements<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |&quot;FOR EACH&quot; BASIC syntax (Like perl and other languages)<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Utility to use dictionary names for handling a record instead of direct AM addressing (possibly using OO QM) -[[User:Diccon|Diccon]]<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |Enhancment to the Cygwin Windows port to address poor IPC performance.<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> ! 1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 0<br /> |-<br /> |}<br /> <br /> Notes:<br /> #Digits mean nothing and are just to make it easier to edit the weird wiki table format.<br /> #If you have a column, please change your digit to indicate any preferences eg + ++ ++ - -- ---. You can use empty columns and add your name in the column heading or add more columns.<br /> <br /> ==Sysadmin==<br /> *Sort /var/www or Apache so we dont have to multi sym link to get dirs visible. - '''TAKEN''' - [[User:DanW|DanW]] I'll sort this, I think a simple landing page with links to the various bits of the system will simplify our directory structure somewhat.<br /> &lt;strike&gt;*ftp access? (not sure if we need this) '''TAKEN''' - [[User:DanW|DanW]] - I can set up SFTP access, somewhat more secure than FTP&lt;/strike&gt; See [[SFTP]]<br /> *SVN compatibility/capability with hashed files<br /> &lt;strike&gt;*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.&lt;/strike&gt; - [http://gpl.openqm.com/bugzilla Bugzilla up]<br /> <br /> ==Bugfixes==<br /> [[List of fixed bugs in the commercial version of OpenQM (Current as of 2.8-10)]]<br /> <br /> ==General Bright Ideas==<br /> * point SORTWORK to a RAMFS mount, would provide very fast sort handling. (Ashley notes: Altering the SORTMEM parameter does the same)<br /> * A bit blue-sky, but something I've wanted to work on for ages: full Unicode support.<br /> * Construct a &quot;High performance&quot; benchmark and tuning section<br /> *Define a &quot;core&quot; of standardised multivalue capabilities that is implemented in all systems, so porting between systems requires zero modifications.</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Subversion_Repository:_HOWTO&diff=290 2009-03-16T17:19:47Z

<p>SteveB: /* Acquiring rights to commit */</p> <hr /> <div>== Introduction ==<br /> <br /> === Terminology ===<br /> <br /> #Checkout - downloads a copy for the first time<br /> #'''Update''' - downloads your copy with any changes in the repository<br /> #'''Commit''' - uploads any changes you made in your copy to the repository<br /> #Import - upload - can be replaced by a combination of update/commit<br /> <br /> repo - repository<br /> <br /> depo - your copy<br /> <br /> === Acquiring rights to commit ===<br /> <br /> To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com or you can choose your own password by sending the output of the following command to an admin ([[Admin_Team]] and look for subversion)<br /> <br /> htpasswd -n yourdesiredusername<br /> <br /> then any admin (with root or sudo access) can grant user xxxxxxxxx access with the following command. It will ask for the password which is hashed password after the : in the output of the above/previous htpasswd command.<br /> <br /> htpasswd /etc/subversion/passwd xxxxxxxxx<br /> <br /> == Command Line User Interface ==<br /> <br /> Assumes you have already installed Subversion.<br /> <br /> Looks complicated but boils down to issuing two commands. One to checkout the project or to update your already checked project. Two to commit your changes.<br /> <br /> === Walkthrough ===<br /> <br /> Make a working directory if you don’t have one<br /> <br /> mkdir qmvdb<br /> <br /> OR, if you already checked out a copy of the repo, just change into your working directory<br /> <br /> cd qmvdb<br /> <br /> If you just made the working directory then use svn checkout to get a copy of the project (all branches, tags and trunk of project openqm in this example)<br /> <br /> svn checkout https://gpl.openqm.com/svn/qmvdb/openqm<br /> <br /> OR, if you already checked out a copy of the repo, then best to ensure you are working on the latest version to avoid later work resolving any conflicts with other people's edits.<br /> <br /> svn update<br /> <br /> Find the file you want to work on (dh_ak.c in this example)<br /> <br /> find . -name dh_ak.c<br /> <br /> See the list of alternatives in different branches<br /> <br /> ./openqm/tags/release-2.6.6/gplsrc/dh_ak.c<br /> ./openqm/branches/workdevbranch1/gplsrc/dh_ak.c<br /> ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Decide to edit version of the file in the trunk directly. Only put tested changes in the trunk because people expect it to be stable at all times.<br /> <br /> vi ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Example edit:<br /> <br /> if (big_dict_rec)<br /> {<br /> /*SB patch from AC from MP/Sep08*/<br /> /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> if (header.file_version &lt; 2)<br /> {<br /> ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> }<br /> else<br /> {<br /> ak_header.itype_ptr = 2;<br /> }<br /> } <br /> <br /> Optionally check that nobody else has, since you last got the file, edited and committed the same section that you edited - and reconcile any conflicts interactively if necessary.<br /> <br /> svn update<br /> <br /> Optionally ask subversion to show you a diff of all changes you made in the whole tree<br /> <br /> svn diff<br /> <br /> &lt;pre&gt;<br /> Index: openqm/trunk/gplsrc/dh_ak.c<br /> ===================================================================<br /> --- openqm/trunk/gplsrc/dh_ak.c (revision 10)<br /> +++ openqm/trunk/gplsrc/dh_ak.c (working copy)<br /> @@ -1892,7 +1892,16 @@<br /> big_dict_rec = (dict_rec_len &gt; AK_CODE_BYTES);<br /> if (big_dict_rec)<br /> {<br /> - ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;<br /> + /*SB patch from AC from MP/Sep08*/<br /> + /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> + if (header.file_version &lt; 2)<br /> + {<br /> + ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> + }<br /> + else<br /> + {<br /> + ak_header.itype_ptr = 2;<br /> + }<br /> }<br /> else /* Short enough to store in AK header */<br /> {<br /> &lt;/pre&gt;<br /> <br /> Commit your changes WITH A CONCISE COMMENT ABOUT ITS PURPOSE so people can get a good idea by looking at the log.<br /> <br /> svn commit -m &quot;Bug fix for indexing on complex fields in non-VERSION 1 files from MP in Sep08 via AC&quot;<br /> <br /> == Graphic User Interface - Windows Tortoise ==<br /> <br /> === Walkthrough ===<br /> <br /> http://tortoisesvn.tigris.org/<br /> <br /> This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.<br /> <br /> The interesting bits of source code management automatically jump out at you later when two people work on the same SECTION of the same file at the same time ie between checkout/update and commit.<br /> <br /> *You commit a file which has also committed by someone else AFTER you checked it out<br /> *You update your depo from repo and someone has committed changes to a file that you have already locally changed.<br /> <br /> In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.<br /> <br /> === Other tools===<br /> <br /> Visual Studio - http://ankhsvn.open.collab.net/<br /> <br /> Eclipse - http://subclipse.tigris.org/<br /> <br /> Netbeans supports it natively now too. &lt;Diccon&gt; Bean a life saver. (Can we have a few hints, Diccon?)<br /> <br /> === Installation === <br /> <br /> http://tortoisesvn.net/downloads<br /> <br /> Might need a reboot<br /> <br /> === Checking Out ===<br /> <br /> Right click on your desktop and choose SVN CHECKOUT<br /> <br /> Fill in the details<br /> <br /> URL? https://gpl.openqm.com/svn/qmvdb<br /> <br /> Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT<br /> <br /> Click OK<br /> <br /> Do you want to create the directory? Yes<br /> <br /> Do you want to accept the unsigned certificate? Yes<br /> <br /> Wait while it downloads the whole repository<br /> <br /> Finished: OK<br /> <br /> After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo<br /> <br /> Subversion puts a hidden folder called .svn in any folder it is managing<br /> <br /> === Committing ===<br /> <br /> #Open the folder TESTIT<br /> #Create a file called testing.txt anywhere in the folder structure<br /> #Close the folder and notice that it has a big red ! on it showing that something is commitable<br /> #Right click on the TESTIT folder (or indeed any subfolder)<br /> #Choose SVN Commit<br /> #It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All<br /> #It helps to add a message explaining why you are committing<br /> #Click OK<br /> #Enter your committers username and password<br /> #Screen showing upload progress<br /> #Click OK when finished and note that the red ! has changed back into a green tick<br /> <br /> <br /> == Committing Binary Files like VOC/ERRMSG ==<br /> <br /> To subversion, VOC/ERRMSG (and other files? which?) are deemed to be &quot;binary&quot; rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.<br /> <br /> The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.<br /> <br /> The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.<br /> <br /> If you do not do follow one of the procedures below then when you finally come to UPDATE or COMMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files. Depending on how much work you have dont this could be mildly irritating or extremely inconvenient.<br /> <br /> PRACTICAL SOLUTION FOR NOW<br /> <br /> Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.<br /> <br /> #Get a lock on the file (or more likely folder) that you want to edit<br /> #SVN UPDATE<br /> #Edit the file<br /> #SVN COMMIT '''or''' release the lock on the file<br /> <br /> By default, a commit releases the lock. If you want to commit but keep the lock, use '--no-unlock' on the command line, or check the checkbox 'keep locks' in TortoiseSVN.<br /> There might be a combined LOCK&amp;UPDATE command but I don't know it.<br /> <br /> Command line<br /> <br /> svn lock files -m &quot;Reason for locking these files&quot;<br /> <br /> Tortoise<br /> <br /> [[image:svnlock.jpg]]<br /> <br /> [[image:svnrelease.jpg]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Subversion_Repository:_HOWTO&diff=287 2009-03-11T18:01:34Z

<p>SteveB: /* Acquiring rights to commit */</p> <hr /> <div>== Introduction ==<br /> <br /> === Terminology ===<br /> <br /> #Checkout - downloads a copy for the first time<br /> #'''Update''' - downloads your copy with any changes in the repository<br /> #'''Commit''' - uploads any changes you made in your copy to the repository<br /> #Import - upload - can be replaced by a combination of update/commit<br /> <br /> repo - repository<br /> <br /> depo - your copy<br /> <br /> === Acquiring rights to commit ===<br /> <br /> To commit you must have a username and password which is given by an admin with root perms on gpl.openqm.com or you can choose your own password by sending the output of the following command to an admin ([[Admin_Team]] and look for subversion)<br /> <br /> htpasswd -n yourdesiredusername<br /> <br /> root command where xxxxxxx is the username<br /> <br /> htpasswd /etc/subversion/passwd xxxxxxxxx<br /> <br /> == Command Line User Interface ==<br /> <br /> Assumes you have already installed Subversion.<br /> <br /> Looks complicated but boils down to issuing two commands. One to checkout the project or to update your already checked project. Two to commit your changes.<br /> <br /> === Walkthrough ===<br /> <br /> Make a working directory if you don’t have one<br /> <br /> mkdir qmvdb<br /> <br /> OR, if you already checked out a copy of the repo, just change into your working directory<br /> <br /> cd qmvdb<br /> <br /> If you just made the working directory then use svn checkout to get a copy of the project (all branches, tags and trunk of project openqm in this example)<br /> <br /> svn checkout https://gpl.openqm.com/svn/qmvdb/openqm<br /> <br /> OR, if you already checked out a copy of the repo, then best to ensure you are working on the latest version to avoid later work resolving any conflicts with other people's edits.<br /> <br /> svn update<br /> <br /> Find the file you want to work on (dh_ak.c in this example)<br /> <br /> find . -name dh_ak.c<br /> <br /> See the list of alternatives in different branches<br /> <br /> ./openqm/tags/release-2.6.6/gplsrc/dh_ak.c<br /> ./openqm/branches/workdevbranch1/gplsrc/dh_ak.c<br /> ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Decide to edit version of the file in the trunk directly. Only put tested changes in the trunk because people expect it to be stable at all times.<br /> <br /> vi ./openqm/trunk/gplsrc/dh_ak.c<br /> <br /> Example edit:<br /> <br /> if (big_dict_rec)<br /> {<br /> /*SB patch from AC from MP/Sep08*/<br /> /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> if (header.file_version &lt; 2)<br /> {<br /> ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> }<br /> else<br /> {<br /> ak_header.itype_ptr = 2;<br /> }<br /> } <br /> <br /> Optionally check that nobody else has, since you last got the file, edited and committed the same section that you edited - and reconcile any conflicts interactively if necessary.<br /> <br /> svn update<br /> <br /> Optionally ask subversion to show you a diff of all changes you made in the whole tree<br /> <br /> svn diff<br /> <br /> &lt;pre&gt;<br /> Index: openqm/trunk/gplsrc/dh_ak.c<br /> ===================================================================<br /> --- openqm/trunk/gplsrc/dh_ak.c (revision 10)<br /> +++ openqm/trunk/gplsrc/dh_ak.c (working copy)<br /> @@ -1892,7 +1892,16 @@<br /> big_dict_rec = (dict_rec_len &gt; AK_CODE_BYTES);<br /> if (big_dict_rec)<br /> {<br /> - ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;<br /> + /*SB patch from AC from MP/Sep08*/<br /> + /*ak_header.itype_ptr = ak_header_size + DH_AK_NODE_SIZE;*/<br /> + if (header.file_version &lt; 2)<br /> + {<br /> + ak_header.itype_ptr = DH_AK_NODE_SIZE + ak_header_size;<br /> + }<br /> + else<br /> + {<br /> + ak_header.itype_ptr = 2;<br /> + }<br /> }<br /> else /* Short enough to store in AK header */<br /> {<br /> &lt;/pre&gt;<br /> <br /> Commit your changes WITH A CONCISE COMMENT ABOUT ITS PURPOSE so people can get a good idea by looking at the log.<br /> <br /> svn commit -m &quot;Bug fix for indexing on complex fields in non-VERSION 1 files from MP in Sep08 via AC&quot;<br /> <br /> == Graphic User Interface - Windows Tortoise ==<br /> <br /> === Walkthrough ===<br /> <br /> http://tortoisesvn.tigris.org/<br /> <br /> This is a minimal but totally functional how to checkout from, and commit to, gpl.openqm in Windows using the Tortoise Windows Explorer shell extension. Think of Tortoise as a folder sync tool which pops up reconciliation screens where conflicts occur between people's edits.<br /> <br /> The interesting bits of source code management automatically jump out at you later when two people work on the same SECTION of the same file at the same time ie between checkout/update and commit.<br /> <br /> *You commit a file which has also committed by someone else AFTER you checked it out<br /> *You update your depo from repo and someone has committed changes to a file that you have already locally changed.<br /> <br /> In these cases you get presented with opportunity to compare and reconcile the two edits in a neat side by side window.<br /> <br /> === Other tools===<br /> <br /> Visual Studio - http://ankhsvn.open.collab.net/<br /> <br /> Eclipse - http://subclipse.tigris.org/<br /> <br /> Netbeans supports it natively now too. &lt;Diccon&gt; Bean a life saver. (Can we have a few hints, Diccon?)<br /> <br /> === Installation === <br /> <br /> http://tortoisesvn.net/downloads<br /> <br /> Might need a reboot<br /> <br /> === Checking Out ===<br /> <br /> Right click on your desktop and choose SVN CHECKOUT<br /> <br /> Fill in the details<br /> <br /> URL? https://gpl.openqm.com/svn/qmvdb<br /> <br /> Checkout Folder? D:\Documents and settings\steve\Desktop\TESTIT<br /> <br /> Click OK<br /> <br /> Do you want to create the directory? Yes<br /> <br /> Do you want to accept the unsigned certificate? Yes<br /> <br /> Wait while it downloads the whole repository<br /> <br /> Finished: OK<br /> <br /> After you click on the folder or refresh desktop with F5, the new folder TESTIT should have a big green tick over it indicating all synced with the repo<br /> <br /> Subversion puts a hidden folder called .svn in any folder it is managing<br /> <br /> === Committing ===<br /> <br /> #Open the folder TESTIT<br /> #Create a file called testing.txt anywhere in the folder structure<br /> #Close the folder and notice that it has a big red ! on it showing that something is commitable<br /> #Right click on the TESTIT folder (or indeed any subfolder)<br /> #Choose SVN Commit<br /> #It shows a long list of files that it thinks could be committed - in your case just the testing.txt file - you have to check all files that you want uploaded or check Select All<br /> #It helps to add a message explaining why you are committing<br /> #Click OK<br /> #Enter your committers username and password<br /> #Screen showing upload progress<br /> #Click OK when finished and note that the red ! has changed back into a green tick<br /> <br /> <br /> == Committing Binary Files like VOC/ERRMSG ==<br /> <br /> To subversion, VOC/ERRMSG (and other files? which?) are deemed to be &quot;binary&quot; rather like image files. Unlike ordinary source/text files, parallel edits on binary files from two people cannot (or rather should not) be merged. Conflicts, due to simultaneous edits outside of the repository, can only be resolved by picking one or the other person's file.<br /> <br /> The tempting solution is to make these into directory files but this doesnt work - probably because a) the default file type isnt directory and b) performance.<br /> <br /> The proper solution would be that these files are represented as ordinary directory files in the source code repository and that the required binary files are built thereof during the QM build process. Since only QM can build these files, the build process will first have to build QM and then use QM to build these files.<br /> <br /> If you do not do follow one of the procedures below then when you finally come to UPDATE or COMMIT and someone else has also worked on the file in the meantime then you will be presented with the unpleasant choice of either losing your changes or trashing someone elses - on the all or nothing principle for binary files. Depending on how much work you have dont this could be mildly irritating or extremely inconvenient.<br /> <br /> PRACTICAL SOLUTION FOR NOW<br /> <br /> Do SVN UPDATE just before editing these files and do SVN COMMIT immediately afterwards.<br /> <br /> #Get a lock on the file (or more likely folder) that you want to edit<br /> #SVN UPDATE<br /> #Edit the file<br /> #SVN COMMIT '''or''' release the lock on the file<br /> <br /> By default, a commit releases the lock. If you want to commit but keep the lock, use '--no-unlock' on the command line, or check the checkbox 'keep locks' in TortoiseSVN.<br /> There might be a combined LOCK&amp;UPDATE command but I don't know it.<br /> <br /> Command line<br /> <br /> svn lock files -m &quot;Reason for locking these files&quot;<br /> <br /> Tortoise<br /> <br /> [[image:svnlock.jpg]]<br /> <br /> [[image:svnrelease.jpg]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Talk:Main_Page&diff=260 2009-02-12T13:10:05Z

<p>SteveB: </p> <hr /> <div>Whacked QM API on here because there is no home or structure yet, will correct it when we next all talk - [[User:Diccon|Diccon]]<br /> <br /> I think we should split ithis up a bit, now we have content.<br /> <br /> We need a &quot;User&quot; section, with guides, Docs, utilityies, API's and packages.<br /> This needs to have a prominent Downloads bit with the packages. I also need to figure out and make the .deb package, can be harder that the .rpm one :)<br /> <br /> And a &quot;Developer&quot; section, with dev mailing list, contacts, potential products/features, bugzilla (half both really), svn, svn guides.<br /> <br /> Were a bit cluttered at the moment, wills care newbies off :)<br /> <br /> Any thoughts, scream now, before I change anything.<br /> <br /> [[User:SteveB|SteveB]] 13:10, 12 February 2009 (UTC) Yes it could do with a haircut or at least a shave.</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=258 2009-02-11T13:08:54Z

<p>SteveB: /* Welcome! */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> This server is DOWN/SLOW around 04:00GMT nightly for 15mins while backing up.<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=257 2009-02-11T12:53:52Z

<p>SteveB: /* Welcome! */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.&lt;BR&gt;<br /> *** The server is DOWN/SLOW around 04:00GMT nightly for 30mins while backing up.<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Dynamic_linking&diff=256 2009-02-06T10:51:29Z

<p>SteveB: </p> <hr /> <div>The CCALL interface is an OpenQM opcode that allows direct access to dynamically linked C libraries. What this means to us is that you can call C functions from within QM-Basic.<br /> <br /> '''Warning!''' Like all low level programming, this is an inherently dangerous activity. It is easy to crash QM processes using this interface, which can lead to data corruption. If your functionality can be implemented as a separate ansyncronous process, consider using the socket libraries, which provide a safer interface.<br /> <br /> == ccall.zip ==<br /> <br /> This is a VERY comprehensive set of examples by Doug Dumitu related to calling functions in glibc.<br /> <br /> If the links dont work then search in http://groups.google.co.uk/group/OpenQM for &quot;ccall.zip&quot; or &quot;Creating a VFS interface to D3&quot; or 'The CCALL layer is a low-level &quot;stack&quot; processors.' and look for Dougs post on the 3 Sep 2007. The ccall.zip file is attached at the end.<br /> <br /> File: [http://groups.google.co.uk/group/OpenQM/attach/b8a1dfce36f27f4c/ccall.zip?part=2 ccall.zip]<br /> <br /> Intro: [http://groups.google.com/group/OpenQM/browse_thread/thread/32e385ff877d7a69/34dccbc201e6f3ea?lnk=gst&amp;q=ccall.zip# Creating a VFS interface to D3] Look for Dougs post in this discussion.<br /> <br /> &quot;The CCALL layer is a low-level &quot;stack&quot; processor. It allows you to build the native C calling stack and then &quot;call&quot; a function. It assumes that you are very careful and understand calling conventions.&quot;</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=254 2009-01-30T14:10:23Z

<p>SteveB: /* Welcome! */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him. *** The server is DOWN/SLOW around 04:00GMT nightly for 30mins while backing up.<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=250 2009-01-18T09:49:08Z

<p>SteveB: /* Resources */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module<br /> *Steve Bush's [[Cygwin Port]] - Is it worth considering a MinGW port? - Would have to replace some posix bits which MinGW doesnt have.<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Administration&diff=249 2009-01-18T09:34:08Z

<p>SteveB: </p> <hr /> <div>Mailing List Manager http://gpl.openqm.com/mailman/admin/openqm-dev<br /> <br /> Tech orientated web based admin https://gpl.openqm.com:14920/<br /> <br /> Secure Shell ssh://gpl.openqm.com:19580<br /> <br /> Secure FTP sftp://gpl.openqm.com:19580<br /> <br /> Google Analytics https://www.google.com/analytics/home/<br /> <br /> [[Backup/Restore procedure]]<br /> <br /> [[Admin Team]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Administration&diff=248 2009-01-18T09:33:37Z

<p>SteveB: </p> <hr /> <div>Mailing List Manager http://gpl.openqm.com/mailman/admin/openqm-dev<br /> <br /> Tech orientated web based admin https://gpl.openqm.com:14920/<br /> <br /> Secure Shell ssh://gpl.openqm.com:19580<br /> <br /> Secure FTP sftp://gpl.openqm.com:19580<br /> <br /> Google Analytics https://www.google.com/analytics/home/<br /> <br /> [[Backup/Restore procedure]]<br /> <br /> [[Admin Team]]<br /> <br /> test speed</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Administration&diff=237 2009-01-07T10:19:03Z

<p>SteveB: </p> <hr /> <div>Mailing List Manager http://gpl.openqm.com/mailman/admin/openqm-dev<br /> <br /> Tech orientated web based admin https://gpl.openqm.com:14920/<br /> <br /> Secure Shell ssh://gpl.openqm.com:19580<br /> <br /> Secure FTP sftp://gpl.openqm.com:19580<br /> <br /> Google Analytics https://www.google.com/analytics/home/<br /> <br /> [[Backup/Restore procedure]]<br /> <br /> [[Admin Team]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Cygwin_Port&diff=236 2009-01-07T10:07:26Z

<p>SteveB: </p> <hr /> <div>Discussion [http://groups.google.com/group/OpenQMCygwin Google Group] Slow speed/possible poor Cygwin IPC implementation.<br /> <br /> [http://gpl.openqm.com/downloads/openqmcygwin.zip openqmcygwin.zip]<br /> <br /> Note that the qm runtime built here only requires a smallish cygwin1.dll (not the full cygwin install) to provide some posix functionality that is not provided by mingw/msvc.<br /> <br /> &lt;pre&gt;<br /> <br /> July 2006<br /> <br /> Here it is. The file is a bit big since I put some screen caps of the<br /> generic cygwin install process to try and get people up to speed quickly.<br /> <br /> http://www.neosys.com/software/openqmcygwin.zip<br /> <br /> I couldn't make a proper install script yet.<br /> <br /> Also I can only get telnet (to qm) working by running xinetd service from a<br /> cygwin command line and not as a proper installed service. I'm pretty<br /> certain that it is a permissions issue. Perhaps someone can explain how to<br /> get the usual inetd daemon running instead of xinetd. The command is<br /> &quot;/usr/sbin/xinetd -d&quot;.<br /> <br /> Cheers,<br /> Steve<br /> <br /> INSTALL CHECKLIST<br /> <br /> - install cygwin default (for all users not &quot;just me&quot;)<br /> add the following:<br /> - development - GCC compiler<br /> - net - xinetd<br /> - admin - cygrunsrv<br /> - editors - vim<br /> <br /> - unpack openqm distro file to be /usr/qmsys (c:\cygwin\usr\qmsys)<br /> <br /> in cygwin:<br /> cd /usr/qmsys<br /> ./buildgpl (should be no errors/warnings except maybe qmconv<br /> doesn't compile)<br /> <br /> create a file /etc/qmconfig containing: (caps required!)<br /> [QM]<br /> QMSYS=/usr/qmsys<br /> NUMUSERS=9<br /> <br /> To enable qmconsole<br /> -------------------<br /> in My Computer properties, Advanced, Environment Variables, Add SYSTEM Env<br /> Variable<br /> - CYGWIN system environment variable to include the word &quot;server&quot; space to<br /> sep other words<br /> then *CLOSE* and reopen all cygwin consoles!<br /> <br /> in cygwin<br /> cygserver-config to install as a service<br /> chmod 666 /var/log/cygserver.log<br /> net start cygserver<br /> or<br /> /usr/sbin/cygserver -d<br /> and read the screen to see that cygserver is running<br /> (nb service permissions may be less than console permissions)<br /> <br /> then<br /> cd /usr/qmsys<br /> bin/qm -start (if you get Bad System Command then close and restart all<br /> cygwin consoles and restart cygserver service)<br /> (it should reply QM has been started<br /> bin/qm (should open a console for you with no login required)<br /> <br /> To enable telnet and client<br /> ---------------------------<br /> cd /usr/qmsys<br /> bin/qm -start (if you haven't already done so)<br /> <br /> - copy sample file from this folder (qmclient and qmsrvr) service def files<br /> to /etc/xinetd.d folder<br /> - change to a valid administrator user name embedded in the above files<br /> - dos2unix /etc/xinetd.d/*<br /> <br /> - /etc/services to have lines for qmclient tcp 4242 and qmsrvr tcp 4243<br /> qmsrvr 4242/tcp #OpenQM Telnet Server<br /> qmclient 4243/tcp #OpenQM Client Access<br /> <br /> - start xinetd.d as follows<br /> cd /usr/sbin<br /> ./xinetd -d<br /> and read screen log to ensure qmclient and qmsrvr services are loaded<br /> control+c to stop<br /> the following to add as a service<br /> cygrunsrv -I xinetd -p /usr/sbin/xinetd<br /> <br /> look in win application event log if fail to start<br /> /var/log/service log records connections<br /> maybe need to chmod 666 /var/log/servicelog<br /> <br /> telnet localhost 4242<br /> <br /> login with any valid win32 user name and password<br /> for account put qmsys<br /> <br /> DONE! <br /> &lt;/pre&gt;</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Dynamic_linking&diff=228 2008-12-19T01:06:32Z

<p>SteveB: /* ccall.zip */</p> <hr /> <div>== ccall.zip ==<br /> <br /> This is a VERY comprehensive set of examples by Doug Dumitu related to calling functions in glibc.<br /> <br /> If the links dont work then search in http://groups.google.co.uk/group/OpenQM for &quot;ccall.zip&quot; or &quot;Creating a VFS interface to D3&quot; or 'The CCALL layer is a low-level &quot;stack&quot; processors.' and look for Dougs post on the 3 Sep 2007. The ccall.zip file is attached at the end.<br /> <br /> File: [http://groups.google.co.uk/group/OpenQM/attach/b8a1dfce36f27f4c/ccall.zip?part=2 ccall.zip]<br /> <br /> Intro: [http://groups.google.com/group/OpenQM/browse_thread/thread/32e385ff877d7a69/34dccbc201e6f3ea?lnk=gst&amp;q=ccall.zip# Creating a VFS interface to D3] Look for Dougs post in this discussion.<br /> <br /> &quot;The CCALL layer is a low-level &quot;stack&quot; processor. It allows you to build the native C calling stack and then &quot;call&quot; a function. It assumes that you are very careful and understand calling conventions.&quot;</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Dynamic_linking&diff=227 2008-12-19T01:05:00Z

<p>SteveB: New page: == ccall.zip == This is a VERY comprehensive set of examples by Doug Dumitu related to calling functions in glibc. If the links dont work then search in http://groups.google.co.uk/group/...</p> <hr /> <div>== ccall.zip ==<br /> <br /> This is a VERY comprehensive set of examples by Doug Dumitu related to calling functions in glibc.<br /> <br /> If the links dont work then search in http://groups.google.co.uk/group/OpenQM for &quot;ccall.zip&quot; or &quot;Creating a VFS interface to D3&quot; or 'The CCALL layer is a low-level &quot;stack&quot; processors.' and look for Dougs post on the 3 Sep 2007. The ccall.zip file is attached at the end.<br /> <br /> [http://groups.google.co.uk/group/OpenQM/attach/b8a1dfce36f27f4c/ccall.zip?part=2 ccall.zip] Look for Dougs post in this discussion.<br /> <br /> [http://groups.google.com/group/OpenQM/browse_thread/thread/32e385ff877d7a69/34dccbc201e6f3ea?lnk=gst&amp;q=ccall.zip# Creating a VFS interface to D3]<br /> <br /> &quot;The CCALL layer is a low-level &quot;stack&quot; processors. It allows you to build the native C calling stack and then &quot;call&quot; a function. It assumes that you are very careful and understand calling conventions.&quot;</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=226 2008-12-19T00:44:25Z

<p>SteveB: /* Resources */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *[[Dynamic linking]] - Calling objects written in other languages.<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module<br /> *Steve Bush's [[Cygwin Port]]<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Wish_list&diff=222 2008-12-11T08:10:07Z

<p>SteveB: move done items to bottom</p> <hr /> <div>Things we need or want.<br /> <br /> If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.<br /> <br /> To keep in touch with this slowly evolving agenda register, making sure your preferences[http://gpl.openqm.com/wiki/Special:Preferences] include &quot;E-mail me when a page on my watchlist is changed&quot;, and that you are logged in, and click the &quot;watch&quot; tab at the top of this page.<br /> <br /> ==Development==<br /> *Accumulate Existing bugfixes into subversion - '''IMPORTANT'''; Can anyone with existing bug fixes please email [[Admin Team]] or commit them into our subversion trunk [[HOWTO]]. (1 Done Thanks Ashley)<br /> *Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)<br /> *Lastest version DEB package<br /> *QM API list compression<br /> *XML Database layer<br /> *XQuery Engine<br /> *Specific flavoured compatibility modes (eg D3 mode, Sequoia mode)<br /> *Code porting program, similar to jBase's PORT.BAS (ideal for Perl regexp?)<br /> *QM BASIC Subversion client wrapper - Simple way to get Pickies onboard. - '''TAKEN''' - [[User:Karaken12|Karaken12]] I've already done this, although it does need some cleaning up.<br /> *QM Virtual File System (VFS) for some SQL database(s)<br /> *Pref to set SCROLL option as default ON for all access statements<br /> *&lt;strike&gt;Svn Linux howto&lt;/strike&gt; [http://gpl.openqm.com/wiki/HOWTO#Command_Line_User_Interface Done]<br /> *&lt;strike&gt;Logo&lt;/strike&gt; See [[Logo]]<br /> *&lt;strike&gt;Add Google Analytics&lt;/strike&gt; [http://www.google.com/analytics/ Done]<br /> *&lt;strike&gt;Keywords&lt;/strike&gt; Done [[Keywords]]<br /> <br /> ==Sysadmin==<br /> *Sort /var/www or Apache so we dont have to multi sym link to get dirs visible. - '''TAKEN''' - [[User:DanW|DanW]] I'll sort this, I think a simple landing page with links to the various bits of the system will simplify our directory structure somewhat.<br /> &lt;strike&gt;*ftp access? (not sure if we need this) '''TAKEN''' - [[User:DanW|DanW]] - I can set up SFTP access, somewhat more secure than FTP&lt;/strike&gt; See [[SFTP]]<br /> *SVN compatibility/capability with hashed files<br /> &lt;strike&gt;*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.&lt;/strike&gt; - [http://gpl.openqm.com/bugzilla Bugzilla up]<br /> <br /> ==Bugfixes==<br /> ==General Bright Ideas==<br /> * point SORTWORK to a RAMFS mount, would provide very fast sort handling.</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=219 2008-12-10T13:19:23Z

<p>SteveB: /* Problems with current strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 02:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == &lt;font color=red&gt;Problems with current strategy&lt;/font&gt; ==<br /> <br /> #Only [[User:SteveB|SteveB]] has overview and responsibility. This is a single point of failure.<br /> #Only one physical backup copy - overwritten daily - so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification that the backup copy is usable - so the backup procedure could fail silently eg if there is anything wrong with the script logic<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Ladybridge&diff=218 2008-12-10T13:06:37Z

<p>SteveB: New page: [http://www.ladybridge.org http://www.ladybridge.org]</p> <hr /> <div>[http://www.ladybridge.org http://www.ladybridge.org]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Multivalue&diff=217 2008-12-10T13:04:07Z

<p>SteveB: New page: Wikpedia article about the original multivalue operating system and its derivatives. [[http://en.wikipedia.org/wiki/Pick_operating_system http://en.wikipedia.org/wiki/Pick_operating_system...</p> <hr /> <div>Wikpedia article about the original multivalue operating system and its derivatives.<br /> [[http://en.wikipedia.org/wiki/Pick_operating_system http://en.wikipedia.org/wiki/Pick_operating_system]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=216 2008-12-10T11:37:47Z

<p>SteveB: /* Backup */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 02:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only [[User:SteveB|SteveB]] has overview and responsibility. This is a single point of failure.<br /> #Only one physical backup copy - overwritten daily - so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification that the backup copy is usable - so the backup procedure could fail silently eg if there is anything wrong with the script logic<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=215 2008-12-10T11:37:26Z

<p>SteveB: /* Current Strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 04:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only [[User:SteveB|SteveB]] has overview and responsibility. This is a single point of failure.<br /> #Only one physical backup copy - overwritten daily - so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification that the backup copy is usable - so the backup procedure could fail silently eg if there is anything wrong with the script logic<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=214 2008-12-10T11:36:25Z

<p>SteveB: /* Problems with current strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only [[User:SteveB|SteveB]] has overview and responsibility. This is a single point of failure.<br /> #Only one physical backup copy - overwritten daily - so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification that the backup copy is usable - so the backup procedure could fail silently eg if there is anything wrong with the script logic<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=213 2008-12-10T11:32:29Z

<p>SteveB: /* Problems with current strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only [[User:SteveB|SteveB]] has overview and responsibility. This is a single point of failure.<br /> #Only one physical backup copy - overwritten daily - so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification that the backup copy is usable so the backup procedure could fail silently eg if there is anything wrong with the script logic<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=211 2008-12-10T11:25:35Z

<p>SteveB: /* Problems with current strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure<br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=210 2008-12-10T11:11:21Z

<p>SteveB: /* Backup */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd while the VM is running.<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=209 2008-12-10T11:09:53Z

<p>SteveB: /* Restore to another host */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd. It is supposed to minimise the<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Similar to restoration to the original location plus:<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=208 2008-12-10T11:08:49Z

<p>SteveB: /* Restore to original host */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd. It is supposed to minimise the<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> Restart the VM after removing the snapshot<br /> <br /> === Restore to another host ===<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=207 2008-12-10T11:04:35Z

<p>SteveB: /* Problems with current strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd. It is supposed to minimise the<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> === Restore to another host ===<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure<br /> #VMSnapshot/Rsync is not totally proven method but results in minimal downtime whereas VMSuspend/Rsync will result in maybe 30 mins downtime</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=206 2008-12-10T10:51:06Z

<p>SteveB: /* Current Strategy */</p> <hr /> <div>== Current Strategy ==<br /> <br /> === Backup ===<br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> The VMWare virtual machine is snapshotted and then its file system is rsync'd. It is supposed to minimise the<br /> <br /> ===Restore to original host===<br /> <br /> Copy the rsync copy back to its original location<br /> <br /> === Restore to another host ===<br /> <br /> Needs VMWare Server 2.0 installed<br /> <br /> gpl.openqm.com DNS to point to new server.<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=205 2008-12-10T10:41:07Z

<p>SteveB: </p> <hr /> <div>== Current Strategy ==<br /> <br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable so the procedure could fail silently eg if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview and responsible which is a single point of failure</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Backup/Restore_procedure&diff=203 2008-12-10T10:38:42Z

<p>SteveB: New page: == Current Strategy == Currently running a backup script at 06:00 UTC == Problems with current strategy == #Only one physical backup copy overwritten daily so no possibility to go b...</p> <hr /> <div>== Current Strategy ==<br /> <br /> Currently running a [[backup script]] at 06:00 UTC<br /> <br /> == Problems with current strategy ==<br /> <br /> #Only one physical backup copy overwritten daily so no possibility to go back more than one day if a corrupt system is backed up<br /> #No regular verification if the backup copy is usable<br /> #Backup procedure could fail silently if there is anything wrong in the scripts<br /> #Only [[User:SteveB|SteveB]] has overview responsible means a single point of failure</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=202 2008-12-10T10:35:35Z

<p>SteveB: /* Welcome! */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of [[OpenQM]], by providing an environment where anyone can acquire, study and contribute to the [[OpenQM]] [[multivalue]] database.<br /> <br /> This project is focussed purely upon the GPL implementation of [[OpenQM]], originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of [[OpenQM]]. Naturally, contributors to [[OpenQM]] are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> Submissions to this project must be under the GPL version 2, with the option to use a later version if the licensee wishes. Or they can be licensed under the LGPL. There may be links on this site to non-conforming software, but that does not include them in this project.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth backup mirror, please contact him.<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the [http://groups.google.co.uk/group/openqm-opensource general email support group].<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the [http://gpl.openqm.com/mailman/listinfo/openqm-dev development email group].<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> * [http://billabong-services.co.uk/anji Billabong Services' Anji] - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. <br /> * [http://www.rushflat.co.nz/downloads.shtml Brian Speir's Installation instructions and other downloads ]<br /> * [http://www.tridentinfosys.com/ Kevin Powick's Trident Delphi wrapper]<br /> * [http://openqm.blackflute.com/ Tom Delombard's old QM page.] Includes details of the tape utilities and the PHP4 module<br /> *Steve Bush's [[Cygwin Port]]<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Administration&diff=201 2008-12-10T10:26:49Z

<p>SteveB: </p> <hr /> <div>http://gpl.openqm.com/mailman/admin/openqm-dev<br /> <br /> https://gpl.openqm.com:14920/<br /> <br /> ssh://gpl.openqm.com:19580<br /> <br /> https://www.google.com/analytics/home/<br /> <br /> [[Backup/Restore procedure]]<br /> <br /> [[Admin Team]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Guides_%26_HOWTOs&diff=191 2008-12-07T21:52:40Z

<p>SteveB: /* Development */</p> <hr /> <div>==Installation==<br /> <br /> === Fedora ===<br /> *[http://www.geneb.org/qm/fedora_notes.txt http://www.geneb.org/qm/fedora_notes.txt] - Guide to installing and configuring QM from source on Fedora (useful scripts and configs)<br /> <br /> === Ubuntu ===<br /> <br /> *[http://www.rushflat.co.nz/files/UbuntuInstall.pdf http://www.rushflat.co.nz/files/UbuntuInstall.pdf] Installing the GPL Version of OpenQM on Ubuntu (aimed at Linux newbies)<br /> <br /> ==Development==<br /> <br /> *[[Recompiling QM]] - How to recompile QM's system C code and BASIC code<br /> *[[HOWTO|SVN Howto]] - How to use Subversion to check out code and commit it back (Windows and Linux)</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=179 2008-12-07T08:10:48Z

<p>SteveB: /* Resources */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of OpenQM, by providing an environment where anyone can acquire, study and contribute to the OpenQM multivalue database.<br /> <br /> This project is focussed purely upon the GPL implementation of OpenQM, originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of OpenQM. Naturally, contributors to OpenQM are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is kindly hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth mirror, please contact [[User:SteveB|SteveB]].<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the general email support group.<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the development email group.<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> *[[Guides &amp; HOWTOs]] - Index of useful guides and HOWTO's on this Wiki<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *Billabong Services' Anji - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. [http://billabong-services.co.uk/anji]<br /> *Brian Speir's Installation instructions and other downloads [http://www.rushflat.co.nz/downloads.shtml]<br /> *Kevin Powick's Trident Delphi wrapper [http://www.tridentinfosys.com/]<br /> *Tom Delombard's old QM page. Includes details of the tape utilities and the PHP4 module [http://openqm.blackflute.com/]<br /> *Steve Bush's [[Cygwin Port]]<br /> *[[C++ Wrapper]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=C%2B%2B_Port&diff=178 2008-12-07T08:10:25Z

<p>SteveB: C++ Port moved to C++ Wrapper: Port will be read as a move of the main body of code into another language/environment, which this isnt.</p> <hr /> <div>#REDIRECT [[C++ Wrapper]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=C%2B%2B_Wrapper&diff=177 2008-12-07T08:10:25Z

<p>SteveB: C++ Port moved to C++ Wrapper: Port will be read as a move of the main body of code into another language/environment, which this isnt.</p> <hr /> <div>This is a class for interfacing with the qmclilib library. It should make it easier to interface when using C++, as it converts C++ strings into C strings and calls the appropriate function in qmclilib.<br /> <br /> [http://gpl.openqm.com/wiki/images/b/b9/Libqm%2B%2B.h libqm++.h]<br /> [http://gpl.openqm.com/wiki/images/2/27/Libqm%2B%2B.cpp libqm++.cpp]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Talk:Cygwin_Port&diff=157 2008-12-06T00:19:11Z

<p>SteveB: </p> <hr /> <div>[[User:Diccon|Diccon]]: Nice one Steve, how viable do you find the cygwin port?<br /> <br /> [[User:SteveB|SteveB]] 00:19, 6 December 2008 (UTC) Sorry didnt have watch emails on. Cygwin port is probably not viable as it is. 100 times slower on a simple file write test I think. See the discussion link. I didnt look at resolving.</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Administration&diff=149 2008-12-05T12:27:12Z

<p>SteveB: </p> <hr /> <div>http://gpl.openqm.com/mailman/admin/openqm-dev<br /> <br /> https://gpl.openqm.com:14920/<br /> <br /> ssh://gpl.openqm.com:19580<br /> <br /> https://www.google.com/analytics/home/<br /> <br /> [[Admin Team]]</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Wish_list&diff=148 2008-12-05T11:57:09Z

<p>SteveB: /* Development */</p> <hr /> <div>Things we need or want.<br /> <br /> If you can do this for the project pop your name by it to claim the job, and contact the Dev mailing list.<br /> <br /> To keep in touch with this slowly evolving agenda register, making sure your preferences[http://gpl.openqm.com/wiki/Special:Preferences] include &quot;E-mail me when a page on my watchlist is changed&quot;, and that you are logged in, and click the &quot;watch&quot; tab at the top of this page.<br /> <br /> ==Development==<br /> *Accumulate Existing bugfixes into subversion - '''IMPORTANT'''; Can anyone with existing bug fixes please email [[Admin Team]] or commit them into our subversion trunk [[HOWTO]]. (1 Done Thanks Ashley)<br /> *Makefile - '''TAKEN''' - [[User:Diccon|Diccon]] (Thanks to Andruk Tatum for the Original on Google group, only minor tweaks to get working on our source)<br /> *Lastest version DEB package<br /> *QM API list compression<br /> *&lt;strike&gt;Svn Linux howto&lt;/strike&gt; [http://gpl.openqm.com/wiki/HOWTO#Command_Line_User_Interface Done]<br /> *[[Logo]]<br /> *XML Database layer<br /> *XQuery Engine<br /> *Specific flavoured compatibility modes (eg D3 mode, Sequoia mode)<br /> *Code porting program, similar to jBase's PORT.BAS (ideal for Perl regexp?)<br /> *QM BASIC Subversion client wrapper - Simple way to get Pickies onboard. - '''TAKEN''' - [[User:Karaken12|Karaken12]] I've already done this, although it does need some cleaning up.<br /> *&lt;strike&gt;Add Google Analytics&lt;/strike&gt; [http://www.google.com/analytics/ Done]<br /> *&lt;strike&gt;Keywords&lt;/strike&gt; Done [[Keywords]]<br /> *QM Virtual File System (VFS) for some SQL database(s)<br /> <br /> ==Sysadmin==<br /> *Sort /var/www or Apache so we dont have to multi sym link to get dirs visible. - '''TAKEN''' - [[User:DanW|DanW]] I'll sort this, I think a simple landing page with links to the various bits of the system will simplify our directory structure somewhat.<br /> *ftp access? (not sure if we need this) '''TAKEN''' - [[User:DanW|DanW]] - I can set up SFTP access, somewhat more secure than FTP<br /> *SVN compatibility/capability with hashed files<br /> &lt;strike&gt;*A proper Bug Tracker. This page will do for now, but it would be much better to have a real tool.&lt;/strike&gt; - [http://gpl.openqm.com/bugzilla Bugzilla up]<br /> <br /> ==Bugfixes==<br /> *ERRMSG to hold more than one error</div>

SteveB https://scarlet.deltasoft.com/index.php?title=Main_Page&diff=147 2008-12-05T11:48:37Z

<p>SteveB: /* Welcome! */</p> <hr /> <div>==Welcome!==<br /> gpl.openqm.com is dedicated to the development of a community distribution of OpenQM, by providing an environment where anyone can acquire, study and contribute to the OpenQM multivalue database.<br /> <br /> This project is focussed purely upon the GPL implementation of OpenQM, originally developed by [[Ladybridge]]. This project was founded on the 28th November 2008 to independently develop future versions of OpenQM. Naturally, contributors to OpenQM are welcome to submit any changes that they may make back to Ladybridge for inclusion in Commercial QM.<br /> <br /> The subdomain that points to this website is granted by [[Ladybridge]], however the server hosting this project, and it's content is neither their responsibility, or under their control. The server is a VMWare Server 2 Virtual Machine located in a high-bandwidth datacentre in Amsterdam, Netherlands. It is kindly hosted by [[User:SteveB|SteveB]] who maintains a daily backup to a secondary datacentre in Amsterdam. If you can provide a stable high bandwidth mirror, please contact [[User:SteveB|SteveB]].<br /> <br /> == How do I use this site? ==<br /> <br /> If you have a question on USAGE of the community version of OpenQM, then send it to the general email support group.<br /> <br /> If you want to discuss DEVELOPMENT of the community version of OpenQM (eg. php5 module) then send it to the development email group.<br /> <br /> While the email lists are best for getting attention, permanent changes in this wiki will have a longer term impact so feel free to add or change ANYTHING in this wiki.<br /> <br /> === Services ===<br /> <br /> *General support email group: [http://groups.google.co.uk/group/openqm-opensource Register] then mailto:openqm-opensource@googlegroups.com<br /> *Development email group: [http://gpl.openqm.com/mailman/listinfo/openqm-dev Register] then mailto:openqm-dev@gpl.openqm.com<br /> *IRC Chat: irc://irc.efnet.org/openqm<br /> *Wiki: http://gpl.openqm.com/wiki/ (This page)<br /> *Subversion repository: https://gpl.openqm.com/svn/qmvdb/ - [[HOWTO]] <br /> *[http://gpl.openqm.com/bugzilla Bugzilla] reporting and tracking bugs:<br /> *[http://www.openqm.org/docs/ Documentation] (Commercial Version)<br /> *[[Downloads]]: automated daily build for key platforms is top priority<br /> *[[Wish list]] - Things that you want &amp; that we need contributors/devs for (lots of small things)<br /> <br /> === Resources ===<br /> *[[QM Client API]] - Documentation and Available API's for the QM remote protocol.<br /> *Billabong Services' Anji - an open web based file browser and reporter. Eventually to become a RAD system. Pre-alpha grade of code. [http://billabong-services.co.uk/anji]<br /> *Brian Speir's Installation instructions and other downloads [http://www.rushflat.co.nz/downloads.shtml]<br /> *Kevin Powick's Trident Delphi wrapper [http://www.tridentinfosys.com/]<br /> *Tom Delombard's old QM page. Includes details of the tape utilities and the PHP4 module [http://openqm.blackflute.com/]<br /> *Steve Bush's [[Cygwin Port]]<br /> <br /> <br /> --[[Administration]]</div>

SteveB