proto-wayic/brec/proposed_project.task

    < pushd ~/work/_/proto-wayic/brec
    ( http://reluk.ca/project/proto-wayic/brec/
    ( http://reluk.ca/var/deploy/test/proto-wayic/brec/

    - summary - Waybrec, a way modelling language
        ( preparatory to `./README.html` -
        < changing?  sync'd → Apache config if served using proto-wayic.mod_autoindex; see e.g.:
            ( http://reluk.ca/project/proto-wayic/mod_autoindex/directory_document.conf § Working example
            ( http://reluk.ca/sys/computer/server/etc/apache2/7_domain/reluk.ca/public/5_in_project_proto.conf
        - a lightweight language for way modelling based on Breccia
        = clarify
            - by mention of purpose, § q.v.
    - purpose
        - dilemma
            a) I want it for outlining (way modelling)
                - at least to rough out a way part initially by quickly giving shape to it
            b) given my small resources
                - it would only be feasible as mere formal variant that cleanly maps to Wayscript
                - such that passing it through a translator would yield Wayscript for processors
                  such as proto-wayic.read
            - these are under tension and pose a kind of dilemma
                a) Waybrec would bring one's waycast (and way) more in hand
                    - more under one's control
                    - by enabling one to shape it more easily
                b) Waybrec would take one's waycast (and way) further out of hand
                    - by interposing itself between the waycaster/scribe and the native language
                      of way modelling
                    - hiding the true, effective form of the way model
            - so they pose a dilemma
                - damned if I do Waybrec, damned if I do not
        -? how settle this
            - or at least come to grips with it
            - it troubles me, and will likely trouble me again in future
            | *only* for initial way modelling
                - as I find myself doing ad hoc anyway
                - precisely then Wayscript is clumsy and *itself* gets in the way
                    ( necessarily clumsy because it is based on HTML
                = task
                    - having it ready for trial use ASAP
                    - aiming to keep the language ruthlessly simple
                        - in line with its purpose
                        - and my small resources
                    - designing it to fit seamlessly into waysource under its own namespace
                        - in line with its purpose
    * grouping by parameterization
        - the actual parameters of a Breccian function equate to a Wayscript group



                                     Copyright © 2018-2019 Michael Allan and contributors.  Licence MIT.