APL Wiki|
Size: 1052
Comment:
|
Size: 2570
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| acre is a fully-featured, source code management system for Dyalog APL. | == Overview == |
| Line 5: | Line 5: |
| acre manages the development of a project of size from a single individual to an international team of developers. | Do you want... |
| Line 7: | Line 7: |
| * It stores code that exists prior to its being put under acre's care into a code-file initially. * Additions and changes made in the Dyalog Editor are saved automatically to component files - one file per workspace item - and can be undone one-at-a-time and individually. No saving of a workspace is necessary.<<BR>><<BR>> Saved changes can be saved back to the code-file so that they can be delivered to a user or used modularly by another maintained system without losing the ability to reverse them. * The Project can be uploaded to a server to be downloaded and maintained co- operatively by a development team. Conflicts caused by two or more developers' changing the same item are handled and resolved safely. Users can see and download changes made by other developers without disturbing their own work. |
* 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 [[http://www.dyalog.com/dyalog_14/index.html |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 [[https://www.carlislegroup.com/ | 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/ProjectPage | acre project page ]] || || Link to the [[FlipDB/ProjectPage | FlipDB project page ]]|| -- KaiJaeger <<DateTime(2014-06-05T20:48:23Z)>> ---- 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