ConwayLife.com

fluffykitty wrote:I think what gmc_nxtman wants is a way to track all non-state-0 cells.

• added [[ NOGUI ]] to disable menus and hotkeys - test

  Code: Select all

  x = 9, y = 5, rule = B3/S23
$bo3b3o$b3o2bo$2bo!
[[ NOGUI THEME 6 GRID WIDTH 96 HEIGHT 96 ]]
  • when you mouse over a [[ NOGUI ]] Viewer an RLE link appears which when clicked will copy the pattern's RLE into the Clipboard on modern browsers
  • reduces [[ WIDTH ]] and [[ HEIGHT ]] minimum limit to 64
  • silently disables the following if specified:
    • [[ GRAPH ]], [[ SHOWGENSTATS ]], [[ SHOWINFOBAR ]], [[ SHOWTIMING ]], [[ THUMB ]] and [[ THUMBLAUNCH ]]
  • Viewers that have [[ NOGUI ]] specified with script errors will not enforce [[ NOGUI ]] so errors can be seen
• added [[ NORLE ]] which disables the "RLE" link when you mouse over a [[ NOGUI ]] Viewer
• hotkey control and "c" will copy pattern source to the clipboard (on modern browsers)
• added [[ COLOR ERROR R G B ]] to set colour for error messages (default is red)
• generation statistics tooltips for alive, births and deaths shows full value (rather than abbreviated)
• variable substitutions can now be used in waypoint messages
  • #B the LifeViewer build number
  • #N the pattern name (if defined)
  • #O the pattern originator (if defined)
  • #R the pattern rule name
  • #A the pattern alias name
  • #T the program title ("LifeViewer")
  • ## the # symbol

• Generations rules containing B0 are now reported as an error - test
• rule decoder was failing on totalistic rules with no slash and only one of B or S - test
• fixed an issue with Torus bounded grids with Y shift - test

fluffykitty wrote:How do I use Lifeviewer scripts and are they Turing Complete?

AforAmpere wrote:Wouldn't they technically be Turing Complete, as they can simulate Turing Complete rules like W110? Maybe I am confusing this with something else. I thought I saw that as a proof for the Turing Completeness of some programming language

gmc-alpha-v0.02a wrote:I also think you should implement ability to read pattern comments, associate lines #O #N etc. with discoverer, name, and associate hotkey "I" with this feature if implemented...

• help information now includes pattern name and originator if specified in the RLE using #N and #O

#N Acorn
#O Charles Corderman
#C A methuselah with lifespan 5206.
x = 7, y = 3, rule = B3/S23
bo5b$3bo3b$2o2b3o!

#C [[ TITLE "#N by #O" ]]
#N Acorn
#O Charles Corderman
#C A methuselah with lifespan 5206.
x = 7, y = 3, rule = B3/S23
bo5b$3bo3b$2o2b3o!

#C [[ "Name: #N\nOriginator: #O" ]]
#N Acorn
#O Charles Corderman
#C A methuselah with lifespan 5206.
x = 7, y = 3, rule = B3/S23
bo5b$3bo3b$2o2b3o!

rowett wrote:This was partially implemented in build 182 which was released to the forum on April 8th, 2016:

• help information now includes pattern name and originator if specified in the RLE using #N and #O

Code: Select all

#N Acorn
#O Charles Corderman
#C A methuselah with lifespan 5206.
x = 7, y = 3, rule = B3/S23
bo5b$3bo3b$2o2b3o!

If you click "SHOW IN VIEWER" above and then use hotkey "i" for information you'll see the Name and Originator in the "Pattern:" section of the Help Information.

drc wrote:The code box with 15c/15 above it uses a torus too big for LifeViewer to handle. Maybe a limit should be imposed so that a black box doesn't appear?

gameoflifeboy, in the LtL thread wrote:nless the extended RLE [of a bounded-grid pattern] gives the pattern's coordinates, LifeViewer places the pattern in the upper left of the torus but Golly places it in the middle. This isn't a problem for tori, but the same thing also happens on a bounded grid, which causes some patterns to run differently. Fortunately this can be avoided by explicitly specifying the coordinates [with #CXRLE].

gameoflifeboy wrote:nless the extended RLE [of a bounded-grid pattern] gives the pattern's coordinates, LifeViewer places the pattern in the upper left of the torus but Golly places it in the middle.

gameoflifeboy wrote:When using AutoFit on this pattern, a lightspeed spaceship in a cylinder, LifeViewer zooms out despite the bounding box of the spaceship not growing

• improved compatibility of copy pattern source
• renamed [[ NORLE ]] to [[ NOCOPY ]] and then link from "RLE" to "Copy"
• added [[ NOSOURCE ]] which hides the pattern source textbox
• help information now shows MAP rules on multiple lines

• the RLE reader could skip rule definition if previous line was just a # character
• bounded grids are now checked to make sure they fit - test
• canonical MAP rule is now correct

gameoflifemaniac wrote:LtL rules are not simulated correctly in LifeViewer. The patterns are just stationary.

muzik wrote:

gameoflifemaniac wrote:LtL rules are not simulated correctly in LifeViewer. The patterns are just stationary.

That's because LifeViewer currently doesn't attempt to simulate them at all right now.

On that note, I wonder how development on just that is getting on.

muzik wrote:What will the limits (for range) be, if any?

rowett wrote:

muzik wrote:What will the limits (for range) be, if any?

Same as Golly.

gameoflifemaniac wrote: Same as Golly.

muzik wrote:Is there/could there be a way to switch between displaying hexagonal rules on a regular square lattice (as in golly), a brick square lattice (like lifeviewer currently), and a true hexagonal grid?