Skip to content

Read Next page on Tour of Scala #875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
KipTwitchell opened this issue Sep 2, 2017 · 4 comments
Closed

Read Next page on Tour of Scala #875

KipTwitchell opened this issue Sep 2, 2017 · 4 comments

Comments

@KipTwitchell
Copy link

The comment at the bottom of the screen telling the user to select the next page would be more clear if there was a button close to it, or at least refer to the table of contents. It wasn't clear the two were connected.

http://docs.scala-lang.org/tour/tour-of-scala.html

@adonig
Copy link

adonig commented Sep 15, 2017

Yep, +1. Came here to report exactly the same issue. Would be nice to have a link like:

Please continue to the next page to read more.

@som-snytt
Copy link
Contributor

A bad link on that first page:

Furthermore, Scala’s notion of pattern matching naturally extends to the processing of XML data with the help of right-ignoring sequence patterns, by way of general extension via extractor objects.

"sequence patterns" is a link to using Regex in a pattern match, but I think it used to be about ancient regex syntax in match expressions; it looks like the tour doesn't mention unapplySeq, which is probably just as well.

I find that whole paragraph confusing. Maybe there's a feature that makes Scala an easy sell for web services?

But whoever adds a link at the bottom could at least remove the offending link described.

SethTisue added a commit that referenced this issue Oct 15, 2017
#875 - Clarify how to get to next page on Tour of Scala page
@rillig
Copy link

rillig commented Dec 9, 2017

The "link to the next page" should be on every page, not only the first. As an interested reader, I want to cover all topics, one after another. For this, scrolling to the top after each page is unnecessary and error-prone, especially since the current topic is not highlighted in the contents.

@SethTisue
Copy link
Member

fixed by #961

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants