Packages

  • package root
    Definition Classes
    root
  • package ostrat

    This is the root package for the Openstrat project.

    This is the root package for the Openstrat project. The top of this package contains, 32 bit Int based Colours, the Multiple type class, a show and persistence library using RCON (Name may change), Rich Compact Object Notation, array based compound value collections of same length elements, an Either based errors framework and general utilities.

    Definition Classes
    root
  • package gOne

    This is the package for an extremely simple simultaneous turn game.

    This is the package for an extremely simple simultaneous turn game.

    Definition Classes
    ostrat
  • GOneGui
  • OneScen
  • OneScen1
  • OneScen2
  • OneScenStart
  • Player
  • PlayerA
  • PlayerB
  • PlayerC
  • PlayerD
  • RPlayer
  • package gTwo
    Definition Classes
    ostrat
  • package geom

    The package name has been chosen to avoid clashing with "geometry" that may be use in other libraries This package contains Basic geometry.

    The package name has been chosen to avoid clashing with "geometry" that may be use in other libraries This package contains Basic geometry. A number of implementation Value classes of the Int and Double product classes defined in ostrat. 2d graphical objects for generalised use. They are of particular use for the generic canvas based classes defined in pCanv but can be used in any display framework and for printing.

    Definition Classes
    ostrat
  • package p1783

    This p1783 package is the beginnings of a grand strategy development game starting in 1783.

    This p1783 package is the beginnings of a grand strategy development game starting in 1783.

    Definition Classes
    ostrat
  • package p305

    This is the beginnings of a grand strategy game starting in BC305 covering Europe, North Africa and West Asia.

    This is the beginnings of a grand strategy game starting in BC305 covering Europe, North Africa and West Asia.

    Definition Classes
    ostrat
  • package pCanv

    The package attempts to encapsulate the various abstract canvas traits while the actual objects that populate a canvas go in package geom.

    The package attempts to encapsulate the various abstract canvas traits while the actual objects that populate a canvas go in package geom.

    Definition Classes
    ostrat
  • package pCard

    This is ancient code.

    This is ancient code. Not use how much is worth salvaging

    Definition Classes
    ostrat
  • package pChess

    This is a package for Chess and Draughts (also known as Checkers).

    This is a package for Chess and Draughts (also known as Checkers). It has been included in the main Strat library, as useful to have code. Because they are finished games, with established rules and iconography. As opposed to applications like GOne, GTwo etc, which are super simple games merely created for the teaching of the use use of the ostrat libraries. And also as opposed to the games in the Dev module which are intended to be developed into interesting games which may at some point have their own individual repositories.

    Definition Classes
    ostrat
  • package pCiv

    A civilisation development game.

    A civilisation development game.

    Definition Classes
    ostrat
  • package pCloseOrder
    Definition Classes
    ostrat
  • package pDev
    Definition Classes
    ostrat
  • package pDraughts
    Definition Classes
    ostrat
  • package pDung
    Definition Classes
    ostrat
  • package pEarth

    This package and module is for Earth maps.

    This package and module is for Earth maps. In particular the tiling of the whole world in Hex grids, defining the changes over the course of history. This will be a data orientated module. It will also include terrain types to model terrain, both real and imagined for local maps and higher scales right up to 0.5 metres per tile However it won't generally include the data for these. The data for the real world will be organised according to a number of levels, which are likely to change over increasingly shorter historical time frames.

    1 Base elevation, relative to 1950 sea level, and relief. 2 Climate. 2 Sea level, shore lines, lake shore lines and river courses. 3 Land-use, both natural and human.

    Definition Classes
    ostrat
  • package pFlags
    Definition Classes
    ostrat
  • package pGrid

    This package works with hexagonal and Square tile grids.

    This package works with hexagonal and Square tile grids. The tile objects themselves will not in the general case the contain grid coordinates, although it may be necessary to include this data for complex Tile values interacting with their wider environment. Its fundamental components are the grid data itself. This is just a linear array of tile data. Compile-time typed grid data. So for example a chess board can be represented by a 64 element Arr, its context determines that it is to be interpreted as an 8 by 8 square grid. Grid descriptions that describe the grid representation in the Array and GridFunctions which implement Cood to T. The grid and grid-gui hierarchies currently contain a mix of new and old systems.

    The package name pGrid was chosen to allow you to use the name "grid" in your code.

    Definition Classes
    ostrat
  • package pHtmlFac
    Definition Classes
    ostrat
  • package pParse

    This is the RSON package.

    This is the RSON package. Readable Succinct Object Notation. It could be just as accurately be described as Readable Succinct Data Notation, but that wouldn't scan as well and indicate it as a better replacement for JSON. RSON uses the standard semicolon separated statements combined with multilevel bracket hierarchy syntax familiar from C, C++, Java and JavaScript. Its main innovations over JSON and XML are allowing statements to be partitioned into comma delineated clauses, the empty statement, the empty clause and type inference. It uses a context free operator precedence hierarchy, with the exception of allowing the 4 ( - + ~ !) operator to be used as prefix operators. Beyond this it generally follows Scala syntax where this doesn't conflict with the preceding rules. Unlike Scala statements must finish with a semicolon unless it is the last statement of a file or a bracket block. Allowing statements to end with a newline introduces horrendous ambiguities unless one is willing to go completely down the significant whitespace route and I'm not sure if that could work even work for such a general purpose basic syntax.

    The above allows it to combine a high level of human readability, succinctness, non-programmer / non-expert write-ability, programmer flexibility and composability and fast-parsing. The initial motivating use case was strategy games, which require huge amounts of modable date files. XML and JSON, the current defaults are simply not fit for purpose. RSON aims to break down the walls between game player, game modder, professional game artist, professional game scripter, professional imperative programming wizards in languages such as C / C++ and Rust and professional functional programming wizards in languages such as Scala, Haskell and Idris.

    Definition Classes
    ostrat
  • package pReactor
    Definition Classes
    ostrat
  • package pSJs
    Definition Classes
    ostrat
  • package pSpace
    Definition Classes
    ostrat
  • package pStrat

    Package for miscellaneous game utilities and data.

    Package for miscellaneous game utilities and data.

    Definition Classes
    ostrat
  • package pWW2

    This pSimp is the beginnings of a WWII grand strategy game.

    This pSimp is the beginnings of a WWII grand strategy game.

    Definition Classes
    ostrat
  • package pWeb

    This package for the manipulation of Html, XML CSS and Javascript.

    This package for the manipulation of Html, XML CSS and Javascript. Some of the functionality could be replaced by Scalatags. As it currently stands the code and design quality of this package is not up to standard, but due to many other higher priorities, I have not been able to take the next step, which is to 1 improve and document it, rewrite it from scratch or 3 replace it with a Scala-tags dependency or some other library.

    Definition Classes
    ostrat
  • package pXml

    I'm just trying out a new package, not sure whether will use pWeb.

    I'm just trying out a new package, not sure whether will use pWeb.

    Definition Classes
    ostrat
  • package pZug
    Definition Classes
    ostrat
  • package strat
    Definition Classes
    ostrat

package gOne

This is the package for an extremely simple simultaneous turn game.

Linear Supertypes
AnyRef, Any
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. gOne
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. Protected

Type Members

  1. case class GOneGui(canv: CanvasPlatform, scenStart: OneScen) extends CmdBarGui with Product with Serializable

    Graphical user interface for GOne example game.

  2. trait OneScen extends AnyRef
  3. trait OneScenStart extends OneScen
  4. case class Player(char: Char, colour: Colour) extends Product with Serializable
  5. case class RPlayer(value: Player, rd: Roord) extends TileMem[Player] with Product with Serializable

    A Player has a very simple token with a letter and colour for recognition."

Value Members

  1. def dummyMethod: String

    This is just a dummy method as empty package objects can cause problems.

  2. object OneScen
  3. object OneScen1 extends OneScenStart
  4. object OneScen2 extends OneScenStart
  5. object Player extends Serializable
  6. object PlayerA extends Player
  7. object PlayerB extends Player
  8. object PlayerC extends Player
  9. object PlayerD extends Player

Inherited from AnyRef

Inherited from Any

Ungrouped