- 11 Apr, 2018 1 commit
-
-
Leon Arnott authored
This will be followed by a number of other str- macros in the coming days. Additionally, the (text:) macro now has another alias, (str:). This alias will now be the preferred name for this macro in the documentation, mainly due to the arrival of other string macros that begin with "str-", and additionally to avoid semantic conflict with the various "text-" changer macros like (text-style:).
-
- 15 Jan, 2018 1 commit
-
-
Leon Arnott authored
Also raised the Harlowe version number to its proper value.
-
- 07 Dec, 2017 1 commit
-
-
Leon Arnott authored
-
- 06 Dec, 2017 2 commits
-
-
Leon Arnott authored
This currently only lists those that have been (set:), and ignores those that are created inside (for:) loops. Also fixed some debug view messages that put variable names in quotes (such as $'bones'). Also added documentation notes about how variable names cannot begin with numerals. Closes #111.
-
Leon Arnott authored
Additionally: * Added a button to toggle the variables pane. * Changed the docs build script to not keep outputting an incorrect icon URL. Closes #89.
-
- 20 Nov, 2017 2 commits
-
-
Leon Arnott authored
The censor-bar style, which was used in all previous versions but not correctly documented, was bugged to always be black even if the text colour was not black. It can be replicated in stories by simply using a `(background-colour:)` macro (preferably set to a variable) in its place. Also re-fixed certain broken maths macros for probably the fourth time in Harlowe history. Also reverted the default line-height CSS for <h1> and other elements to "1em" instead of "1rem", due to it causing problems with line-wrapped headers. Closes #115. Closes #107. Closes #80.
-
Leon Arnott authored
Formerly, this would just fail utterly and cause a crash. Also added a missing miscdocs file. Closes #93.
-
- 02 Aug, 2017 1 commit
-
-
Leon Arnott authored
Fixed a bug where the alternative macro spellings (text-color:) and (color:) were displayed as erroneous in the editor.
-
- 26 Apr, 2017 1 commit
-
-
Leon Arnott authored
-
- 08 Mar, 2017 1 commit
-
-
Leon Arnott authored
This fix forcibly checks which CSS properties are being applied to the <tw-enchantment> by style changers, and adds matching "inherit" inline styles to the <tw-story> below. Yes, it's unfortunate that the <tw-story> has to be permuted for this… oh well. Also added CodeMirror mode CSS that keeps the line-break marker gutter at left:0, which, for reasons yet unknown, it sometimes isn't. Version changed to 2.0.1. Closes #85. Closes #83.
-
- 25 Jan, 2017 1 commit
-
-
Leon Arnott authored
This closes #77. Also: * Added manual text for (enchant:). * Link macros like (link-enchant:) will now error when given an empty string.
-
- 19 Jan, 2017 1 commit
-
-
Leon Arnott authored
* Added documentation for the (altered:) macro. * Fixed various macro doc mistakes or errors. * Altered the documentation generation script to add a "changes" section pulling two recent versions' changes directly from README.md. * Now, the new invalid operators like "x" and "are" are no longer syntax-highlighted orange when inside string literals.
-
- 17 Jan, 2017 1 commit
-
-
Leon Arnott authored
Having them in the Harlowe.js file was kind of a kludge, and this amends that. Also added documentation for (for:), and temp variables. Also added a line to the README about the <tw-story> element's location.
-
- 10 Dec, 2016 1 commit
-
-
Leon Arnott authored
Also added a `make format` Makefile task to round out the offered tasks. Closes #62.
-
- 03 Dec, 2016 1 commit
-
-
Leon Arnott authored
This fairly obvious combination, which directly maps to (but currently doesn't bootstrap) the default sidebar's undo button, is now provided.
-
- 01 Dec, 2016 1 commit
-
-
Leon Arnott authored
This, along with a forthcoming (redo:) macro (which, in order to be used correctly, would require a (future:) macro, I guess), would allow the current default sidebar to be bootstrapped (constructed anew) from Harlowe code. Also changed the CSS of <html> such that its font declaration is now on <tw-story>, and fixed the CSS of <tw-error>s to make them white-on-black alongside the rest. (I may revise the latter some more to make it work when black-on-white is being used.)
-
- 30 Nov, 2016 1 commit
-
-
Leon Arnott authored
I've wanted to do this for a long time. I feel like white-on-black is the superior default for Twine, and was so during Twine 1, for a few reasons - black suggests a greater degree of intimacy, away from the "public" space of the white-on-black web, and invites more personal writing. Instructions for changing it back using (enchant:) are in the update notes. (Yes, I'm aware (enchant:) still needs to be documented.)
-
- 21 Nov, 2016 1 commit
-
-
Leon Arnott authored
The addition of "each" lambdas was the final piece of this puzzle - expressing which temp variable to loop over in an unambiguous and readable syntactic way.
-
- 04 Nov, 2016 1 commit
-
-
Leon Arnott authored
Fixed a bug where setting custom values in a datamap returned by (passage:) would save the data in all subsequent identical (passage:) datamaps. This is for 2.0 only, since it's entirely likely some stories rely on these bugged semantics for storage. Also corrected a few documentation notes. Closes #60.
-
- 02 Nov, 2016 1 commit
-
-
Leon Arnott authored
This eliminates one instance of the non-character U+FFFE appearing in the output, which caused some servers to error. Also brought down d628d45dd90e's change from the 2.0.0 branch.
-
- 11 Sep, 2016 1 commit
-
-
Leon Arnott authored
Added the (hover-style:) changer macro, which allows passed style changers to only apply when hovering over the hook. I'm a little uncomfortable about its name (as compared to (text-style:)) and the specificity of only allowing style changers (which currently does not include (transition:)s) but I think it'll be fine, and could be safely expanded a little in future. Also fixed a bug where joining a changer, using "+" in markup, with a changer macro that produced an error, would suppress the error.
-
- 06 Sep, 2016 1 commit
-
-
Leon Arnott authored
Also fixed a bug where the wrong value would be given if passed the empty string as a search term (due to being passed to String#split()). Closes #8.
-
- 03 Sep, 2016 1 commit
-
-
Leon Arnott authored
Added "any" and "all" properties to sequentials, which are used for "all" and "any" comparison operations. These properties produce special, unstorable "determiner" values, which, when used as the object of "contains", "is in", or other comparison expressions, results in every element of the sequential being compared using the operation. This is, I feel, a better solution to simply adding "contains all" and "contains any" operators, in that it naturally expands to cover ">", ">=" and other non-set-related operations. Also fixes a bug (that didn't manifest until just now) where certain unstorable values could be stored if they were in storable data structures.
-
- 01 Sep, 2016 1 commit
-
-
Leon Arnott authored
This was important, I decided, to ensure consistency in changer concatenation between macros and passage markup. $changer + $changer2 now joins changers in both modes. Also added a "none" (text-style:) which, when added to other (text-style:) combined changers, removes their styles.
-
- 30 Aug, 2016 2 commits
-
-
Leon Arnott authored
Trying to use common incorrect operators will result in an error message telling you what the correct operator is. These incorrect operators current include =>, =<, gte, lte, gt, lt, eq, isnot, neq, are, x. (This, of course, means that JS variable names that equal these words are no longer passed through.)
-
Leon Arnott authored
Fixed a bug where datasets could contain (and compared) data structures by reference, in constructing, concatenating and subtracting. Also: * Fixed a bug where subtracting arrays was also subject to comparing data structures by reference. * Fixed a bug where subtracting non-subtractable values (such as booleans) wouldn't produce an error.
-
- 29 Aug, 2016 1 commit
-
-
Leon Arnott authored
I spent years feeling rueful about adding this, as I'd felt it directly competes with the (replace:) macros' idiom. Lately, though, I've seen the merit in it, as a way of keeping revealed text inside the flow of the prose it is revealed inside, when said text is vital to the readability of the passage. I currently feel like this doesn't provide much way of expressing structure and relationship between hidden hooks and visible ones - no semantic way to convey that they form a list with only a single one visible, for instance, or that one builds upon the last, as with <<becomes>> and <<gains>> in Twine 1. But, future macros providing semantically clearer means of showing hidden hooks ((show-next:), (reveal-next:) or somesuch) can always be added.
-
- 24 Aug, 2016 1 commit
-
-
Leon Arnott authored
Also added to the test case HTML page a "ErrorMessages" global which collects all Harlowe error messages produced as a result of tests, so that they can be checked. Also decided to stick with the uncapitalised "boolean" for the data type in documentation and errors.
-
- 20 Aug, 2016 2 commits
-
-
Leon Arnott authored
This involved adding some structural indirection to the ChangeDescriptor's newTargets property - instead of an array of HookSets or jQuerys, it's an array of {target, append} properties, tying the append method to the target.
-
Leon Arnott authored
This enables the "when stored, can work across passages" test for revision macros to finally pass. In practice, it means that the section used for HookSets' hook selection is determined by the consumer macro. As a result, Section.selectHook() is gone, and (somewhat frustratingly) HookSet.forEach() now takes a section as its first param, breaking symmetry with Array#forEach. While implementing this, HookSets' targets and newTargets were changed to no longer be stored as strings - only HookSet, jQuery collections and arrays thereof are used now. Also, as a necessity of these changes, HookSets no longer have a length, and can no longer be spread with "...". (But, neither of these had much point ever since they became unstorable).
-
- 18 Aug, 2016 1 commit
-
-
Leon Arnott authored
This allows the "can be composed" tests for these macros to be re-enabled. Also gave HookSets a TwineScript_is() method, allowing them to finally be compared by value using the "is" operator.
-
- 16 Aug, 2016 1 commit
-
-
Leon Arnott authored
Also fixed a bug where using (set:) to set a substring, when the given array of positions contained "length" (such as (set: $a's (a:1,"length")) to "foo")), wouldn't produce an error.
-
- 08 Aug, 2016 1 commit
-
-
Leon Arnott authored
This macro, designed primarily for use with lambdas, lets you iterate over a datamap and have access to its names and values easily, without needing to interleave (datanames:) and (datavalues:). Also: * Fixed a bug where lambdas couldn't iterate over values that consisted of datamaps, datasets, or any Harlowe-specific data. * Added some styling for "where", "via", "making" and "with" to the CodeMirror mode.
-
- 02 Aug, 2016 1 commit
-
-
Leon Arnott authored
Also specified that 1.2.3 requires jQuery 2.x.
-
- 01 Aug, 2016 1 commit
-
-
Leon Arnott authored
This includes a ] inside a hook, a } inside the collapsing markup, or any of the formatting markup's closing tokens immediately after an opening token. I still need to determine if the HTML comments markup should have this applied, too. Closes #55.
-
- 14 Jul, 2016 1 commit
-
-
Leon Arnott authored
* Also wrapped it in the mathFilter function to filter out NaNs. * Also fixed a small documentation mistake.
-
- 12 Jul, 2016 1 commit
-
-
Leon Arnott authored
This alters the way Colours are converted to CSS properties inside (text-colour:) and (background:) - now, they'll be converted to rgba() instead of hexadecimal notation. Also fixed a bug in the Array#includes polyfill.
-
- 09 Jul, 2016 1 commit
-
-
Leon Arnott authored
This should prevent (http:...) and (https:...) from being considered invalid macros. Closes #41.
-
- 07 Jul, 2016 2 commits
-
-
Leon Arnott authored
Also cleaned up the update notes a bit.
-
Leon Arnott authored
* The (rgb:) and (hsl:) macros behave like the CSS colour functions, accepting three numbers to produce a new colour value. I'd like to add (rgba:) and (hsla:) as well at some point. * Colour values now have r, g, b, h, s and l properties, which can be used to extract components for use in further (hsl:) or (rgb:) calls. The h, s and l properties implicitly convert the colour's internal RGB representation into HSL, but should be accurate.
-