ConwayLife.com

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

I don't really request for that to be necessarily added at the moment, the current function seems adequate for me, I was just noting the cause of the phenomenon drc described.

Build 231 is now live on the Forums and LifeWiki

Please note: you will need to refresh your browser to use the new build

Enhancements since the last released build:

• 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

Fixes since the last released build:

• 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

Comments, feedback, suggestions and bug reports welcome!

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

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

Read the first post in this thread for starters. Hit 'H' for help in LifeViewer to see a list of all the supported commands. For examples of syntax in specific cases, follow Chris's handy "test" links for the build in which the feature appeared.

No, LifeViewer script commands are not a programming language, just a control mechanism and a way to set up animation sequences.

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

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

I thought about that briefly before answering... but it's really not the scripting commands that are Turing-complete, it's the set of possible patterns that LifeViewer can simulate. And for the most part, LifeViewer can do those simulations equally well with or without the scripting commands.

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...

Bringing this back up because there's currently no feature to read pattern comments (unless I somehow missed it in the help menu), although it seems that key "I' has been used already. I think N might be suitable, but I'm not sure.

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

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.

You can also use them as a window title:

Or as a waypoint message:

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.

I wasn't aware of this feature! I guess I didn't look too far into the changelog to notice that. Looks good.

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?

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?

Thanks for reporting! This has been fixed and will be in the next released build. Test case is here.

I already posted this somewhere else, but I'm reposting it because I think it deserves attention. My apologies if this issue is already known:

gameoflifeboy, in the LtL thread wrote:[U]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:[U]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.

Noted. It's on the backlog for LifeViewer. Thanks for reporting!

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

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

With Bounded Grids (and LifeHistory patterns too) LifeViewer uses the initial bounding box as the minimum size for AutoFit. I may make this an option in a future build.

Build 233 is now live on the Forums and LifeWiki

Please note: you will need to refresh your browser to use the new build

LifeViewer can now be used to display static images with the [[ NOGUI ]] script command. You can save the image by right clicking on it and "Save image as..." (depending on your browser). You can copy the pattern's source RLE the clipboard by mousing over the image and clicking on it when "Copy" appears.

Images can be as small as 64x64 pixels:

You can disable the copy functionality by using the [[ NOCOPY ]] script command:


Enhancements since the last released build:

• 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

Fixes since the last released build:

• 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

Comments, feedback, suggestions and bug reports welcome!

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

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:

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.

Correct, LtL is not yet complete in LifeViewer.

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

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

Same as Golly.

rowett wrote:

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

Same as Golly.

So you are the creator of LifeViewer?

gameoflifemaniac wrote:Same as Golly.

So you are the creator of LifeViewer?[/quote]
Yes if you cant tell already.

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?

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?

You can switch between the first two (hotkey '/'). LifeViewer does not support a true hexagonal grid.