PRT.UnivDevelop History

Show minor edits - Show changes to output - Cancel

July 19, 2013, at 11:55 AM by 82.139.115.35 -
Changed line 3 from:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed. The URL will contain "VMS" if the page is old:
to:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed. The page will have the "VMS" logo at the top if the page is old:
July 19, 2013, at 11:54 AM by 82.139.115.35 -
Changed line 3 from:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed:
to:
Development related to PRT covers many different kinds of projects, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed. The URL will contain "VMS" if the page is old:
July 19, 2013, at 11:54 AM by 82.139.115.35 -
Changed lines 1-3 from:
!!Welcome to the VMS Development Area

Development related to VMS covers many different kinds of projects, from writing benchmarks
, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project. A project consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:
to:
!!Welcome to the Development Area for PRT Universal

Development related to PRT covers many different kinds of projects
, from writing benchmarks and applications, to creating languages on top of PRT, to modifying PRT itself. To satisfy the needs of developers of each different kind of project, an individual project has been organized as a collection of sub-repositories. A top-level repository has a list of all the sub-repositories, and cloning the top will clone all the sub-repos, and update each to a particular version. Notes on a variety of aspects of PRT related development can be found in the pages linked below -- note, however, that this site is in flux, and many of these pages are old, dating back to the original version of proto-runtime, which was called VMS, so some of the information may differ from how PRT-Univ is developed:
December 06, 2012, at 01:20 PM by 24.130.186.152 -
Added line 10:
* [[VMS.DevelopLearnCode | Learning the code base]]
September 10, 2012, at 05:16 AM by 24.130.186.152 -
Changed line 10 from:
* [[VMS.DevelopPatterns | Patterns to use while developing VMS projects]]
to:
* [[VMS.DevelopPatterns | Patterns for directory structure, naming, and so on, to use while developing VMS projects]]
September 10, 2012, at 05:14 AM by 24.130.186.152 -
Added lines 3-8:
Development related to VMS covers many different kinds of projects, from writing benchmarks, to creating languages, to extending VMS. To keep things manageable and straight forward for the various developers, each aspect of development has been given its own project, which consists of a top-level repository and a number of sub-repositories. Notes on a variety of aspects of VMS related development can be found in the pages linked below:

!!!Individual Projects
* [[VMS.DevelopProjectNotes|A list of pages with notes about the projects, one for each project]]
* [[VMS.DevelopGetProject | Generic instructions on getting a project and configuring it]]
Deleted line 13:
* [[VMS.DevelopGetProject | Getting a project and configuring it]]
Deleted line 20:
* [[VMS.DevelopProjectNotes|Notes about individual projects]]
September 04, 2012, at 12:07 PM by 24.130.186.152 -
Added line 16:
* [[VMS.DevelopProjectNotes|Notes about individual projects]]
September 04, 2012, at 11:57 AM by 24.130.186.152 -
Changed line 11 from:
* [[http://hg.opensourceresearchinstitute.org/cgi-bin/hgwebdir.cgi/VMS/2__runs_and_data/|The repository for run results, configuration files, and input files]]
to:
* [[VMS.DevelopRunsAndDataRepo|The repository for run results, configuration files, and input files]]
September 04, 2012, at 11:56 AM by 24.130.186.152 -
Changed lines 11-12 from:
to:
* [[http://hg.opensourceresearchinstitute.org/cgi-bin/hgwebdir.cgi/VMS/2__runs_and_data/|The repository for run results, configuration files, and input files]]
Changed line 22 from:
* [[VMS.IntellMICArch | MIC architecture]]
to:
* [[VMS.IntellMICArch | MIC architecture]]
September 04, 2012, at 11:30 AM by 24.130.186.152 -
Added line 14:
* [[VMS.DevelopVisualTool| Using the performance visualizer]]
August 03, 2012, at 05:37 AM by 24.130.186.152 -
Added lines 14-16:

!!!Research Ideas
* [[VMS.DevelopSchedulers|Scheduler Research]]
July 17, 2012, at 01:09 AM by 24.130.186.152 -
Added line 8:
* [[VMS.DevelopGetProject | Getting a project and configuring it]]
Deleted line 10:
* [[VMS.DevelopGetProject | Getting a project and configuring it]]
July 05, 2012, at 07:27 AM by 24.130.186.152 -
Added line 5:
* [[VMS.DevelopDebug| Tips on debugging Applications, languages, and VMS itself]]
July 02, 2012, at 12:43 AM by 24.130.186.152 -
Added line 9:
* [[VMS.DevelopGetProject | Getting a project and configuring it]]
June 30, 2012, at 06:05 AM by 24.130.186.152 -
Deleted lines 5-7:
!!! Implementation Details
* [[VMS.DevelopPerformanceCounters| Using performance counters]]
Added lines 9-11:

!!! Implementation Details
* [[VMS.DevelopPerformanceCounters| Using performance counters]]
June 30, 2012, at 04:25 AM by 24.130.186.152 -
Deleted line 3:
* [[VMS.DevelopPractices | Development Practices]]
June 30, 2012, at 04:15 AM by 24.130.186.152 -
Added line 5:
* [[VMS.DevelopPatterns | Patterns to use while developing VMS projects]]
June 30, 2012, at 04:13 AM by 24.130.186.152 -
Added lines 1-9:
!!Welcome to the VMS Development Area

!!!Development Practices
* [[VMS.DevelopPractices | Development Practices]]

!!! Implementation Details
* [[VMS.DevelopPerformanceCounters| Using performance counters]]

!!!Repositories
Added lines 12-13:

!!!Intelligence Gathering
Changed line 15 from:
* [[VMS.IntellMICArch | MIC architecture]]
to:
* [[VMS.IntellMICArch | MIC architecture]]
June 30, 2012, at 04:04 AM by 24.130.186.152 -
Changed lines 3-4 from:
* [[VMS.IntellSCC | SCC architecture]]
to:
* [[VMS.IntellSCC | SCC architecture]]
* [[VMS.IntellMICArch | MIC
architecture]]
June 30, 2012, at 04:02 AM by 24.130.186.152 -
Deleted line 0:
Changed lines 2-3 from:
* [[VMS.DevelopCreateRepository | creating a repository]]
to:
* [[VMS.DevelopCreateRepository | creating a repository]]
* [[VMS.IntellSCC | SCC architecture
]]
June 23, 2012, at 03:08 AM by 24.130.186.152 -
Changed lines 1-3 from:
* [[VMS.Develop_CreateRepository | creating a repository]]
to:
* [[VMS.DevelopRepositoryStructure | Repository Structure and Usage]]
* [[VMS.DevelopCreateRepository
| creating a repository]]
June 23, 2012, at 02:12 AM by 24.130.186.152 -
Changed line 1 from:
* [[VMS.Develop.CreateRepository | creating a repository]]
to:
* [[VMS.Develop_CreateRepository | creating a repository]]
June 23, 2012, at 02:12 AM by 24.130.186.152 -
Changed lines 1-2 from:
* [[VMS.Develop/CreateRepository | creating a repository]]
to:
* [[VMS.Develop.CreateRepository | creating a repository]]
June 23, 2012, at 02:12 AM by 24.130.186.152 -
Changed lines 2-3 from:
* [[VMS/Develop/CreateRepository | creating a repository]]
to:
* [[VMS.Develop/CreateRepository | creating a repository]]
June 23, 2012, at 02:11 AM by 24.130.186.152 -
Added lines 1-3:


* [[VMS/Develop/CreateRepository | creating a repository]]