Skip to content
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

Terminology: Section or Page? #52

Open
nikolas opened this issue Mar 5, 2015 · 2 comments
Open

Terminology: Section or Page? #52

nikolas opened this issue Mar 5, 2015 · 2 comments

Comments

@nikolas
Copy link
Member

nikolas commented Mar 5, 2015

What is the reasoning for using the class name 'Section' for nodes in the pagetree? I think it would make more sense to call them Pages.

@thraxil
Copy link
Contributor

thraxil commented Mar 6, 2015

Yeah, it's an old debate. I feel like "page" is such an overused and vague term that I kind of wanted to get away from it. I also thought it seemed weird since there is a recursive relationship between them. "Section" is pretty vague and overused as well but at least it made more sense for a section to contain other sections rather than pages containing pages. So, ultimately, I'm not crazy about it either but "section" just seemed like the least bad term to use.

@nikolas
Copy link
Member Author

nikolas commented Mar 10, 2015

I see. Maybe just something like "Node" would be the most straightforward? It's not a big deal I was just curious. When I first looked at the pagetree code, it wasn't immediately obvious that a "Section" is the primary construct we're dealing with.. it sounds like it's referring to a group of things.

If we did want to change Section to something else, I wonder if it would be possible to maintain backwards-compatibility by having a class "alias" or something.

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

2 participants