Differences between revisions 3 and 4
Revision 3 as of 2014-06-06 05:53:11
Size: 2267
Editor: KaiJaeger
Comment:
Revision 4 as of 2014-06-06 08:13:16
Size: 2570
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * Do you want to store the source code and associated files of Dyalog APL projects in a database (repository) running somewhere, typically the cloud, supporting multiple developers? Do you want...
Line 7: Line 7:
 * Want to store private copies of such a project independently from the main branch in the same repository as an insurance against, say, the loss of your laptop?  * to store the source code and associated files of Dyalog APL projects in a database (repository) running somewhere, typically the cloud, supporting multiple developers?
Line 9: Line 9:
 * Want to save all versions of APL objects and files of a project locally until it’s time either to back them up into your private part of the repository or merge them into the main branch?  * to store private copies of such a project independently from the main branch in the same repository as an insurance against, say, the loss of your laptop?
Line 11: Line 11:
 * Want to have reports about what you've changed, what was backed up, what’s causing a conflict, who has changed what and when in the main branch, which of your changes, if any, will cause a conflict on upload?  * to save all versions of APL objects and files of a project locally until it’s time either to back them up into your private part of the repository or merge them into the main branch?
Line 13: Line 13:
 * Want to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?  * to have reports about what you've changed, what was backed up, what’s causing a conflict, who has changed what and when in the main branch, which of your changes, if any, will cause a conflict on upload?
Line 15: Line 15:
 * Want to restore effortless any old version from the main repository?  * to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?
Line 17: Line 17:
 * Want to go back to any older version since you’ve checked out your copy?  * to restore effortless any old version from the main repository?
Line 19: Line 19:
 * Want an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?  * to go back to any older version since you’ve checked out your copy?
Line 21: Line 21:
 * Don’t want to save workspaces any more?  * an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?

 * to abandon the need of saving (possibly corrupted) workspaces?
Line 24: Line 26:

== Watch acre in action ==

PhilLast and KaiJaeger will show acre in action at the [[http://www.dyalog.com/dyalog_14/index.html |2014 Dyalog conference]] held from 2014-09-21 to 2014-09-25 in Eastbourne / South England.
Line 29: Line 35:
To take full advantage of its power you also need a [[FlipDB]] database server running somewhere. FlipDB is the flagship of Carlisle Group. Luckily they have agreed to offer a free version of FlipDB as well. This will be a stripped down version of FlipDB but it is still a fully fledged relational database system written in Dyalog. FlipDB will soon be available for download from here as well. To take full advantage of its power you also need a [[FlipDB]] database server running somewhere. FlipDB is the flagship of Carlisle Group. Luckily they have agreed to offer a free version of FlipDB as well. This will be a stripped down version of FlipDB but it is still a fully fledged relational database system written in Dyalog that supports all the functionality required by acre. FlipDB will soon be available for download from here as well.
Line 31: Line 37:
Link to the [[acre/ProjectPage | acre project page ]] || Link to the [[acre/ProjectPage | acre project page ]] ||
|| Link to the [[FlipDB/ProjectPage | FlipDB project page ]]||
Line 33: Line 40:
Link to the [[FlipDB/ProjectPage | FlipDB project page ]]
Line 35: Line 41:

----
CategoryAcre

The code management system acre

Overview

Do you want...

  • to store the source code and associated files of Dyalog APL projects in a database (repository) running somewhere, typically the cloud, supporting multiple developers?
  • to store private copies of such a project independently from the main branch in the same repository as an insurance against, say, the loss of your laptop?
  • to save all versions of APL objects and files of a project locally until it’s time either to back them up into your private part of the repository or merge them into the main branch?
  • to have reports about what you've changed, what was backed up, what’s causing a conflict, who has changed what and when in the main branch, which of your changes, if any, will cause a conflict on upload?
  • to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?
  • to restore effortless any old version from the main repository?
  • to go back to any older version since you’ve checked out your copy?
  • an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?
  • to abandon the need of saving (possibly corrupted) workspaces?

If so then acre is for you. But be warned: once you’ve started working with it you won’t want to go back. Ever.

Watch acre in action

PhilLast and KaiJaeger will show acre in action at the 2014 Dyalog conference held from 2014-09-21 to 2014-09-25 in Eastbourne / South England.

How to get it

acre is a simple and small namespace that contains all the code. It was written by PhilLast on behalf of Carlisle Group in order to support the international development team of FlipDB. It is free. Soon you will be able to download it from here.

To take full advantage of its power you also need a FlipDB database server running somewhere. FlipDB is the flagship of Carlisle Group. Luckily they have agreed to offer a free version of FlipDB as well. This will be a stripped down version of FlipDB but it is still a fully fledged relational database system written in Dyalog that supports all the functionality required by acre. FlipDB will soon be available for download from here as well.

Link to the acre project page

Link to the FlipDB project page

-- KaiJaeger 2014-06-05 20:48:23


CategoryAcre

acre (last edited 2018-03-18 19:03:45 by KaiJaeger)