Comments (15)
Can you please elaborate on what you expect the OpenSCAD team to do here? We have no control over how the Wikibooks search works, so I don't see any possible action on our side other than fully moving away from Wikibooks (which has been discussed but would be quite some effort).
from openscad.
There is a search input field top right above the logo https://en.wikibooks.org/wiki/OpenSCAD_User_Manual
also https://openscad.org/cheatsheet/ will help you find things
from openscad.
from openscad.
from openscad.
I think the brackets confused the search. Putting just minkowski
in the "search this book" box works for me.
from openscad.
It will find the section on the printed version
https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Print_version#The_OpenSCAD_Language_Reference
It also finds the links to https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Transformations#minkowski ,
But the content of https://en.wikibooks.org/wiki/OpenSCAD_User_Manual itself is not searched.
So all information is found - but not every mention of the link.
from openscad.
from openscad.
I don't think I would call it "OK", but rather, it seems to me out of scope to even try to address search results. Integrated wiki search bars have been relatively poor quality in their search results since the dawn of wikipedia, and functionally we use wikibooks more as a convenient shared-editing host of our manual and tutorial content. For making content language findable, our prepared solution which I think is prominently linked in our documentation and tutorials, is the cheatsheet: https://openscad.org/cheatsheet/ This beats search bars by leaps and bounds, I think. Now if we did an inadequate job of making the cheatsheet clearly findable for new people, or in making its specific use or value clear, that I would consider worth doing a tweak if there is someplace more appropriate or useful to link to it, or a different way to describe it while doing so.
from openscad.
The problem with @JamesC1's second search is that it searches for "language reference", a phrase that appears in only a few places. (But the search doesn't find the top-level page, which seems pretty wrong.) The various "reference" pages don't have the word "reference" on them.
The biggest problem is, I think, that the "language reference" section looks sort of book-like. A few ideas for reducing the opportunity for confusion:
- We could change the name of the "OpenSCAD User Manual" section to something else that clarifies that it's a section of the larger manual. "Tutorial" comes to mind, but really only applies to a few of its subsections - and there's also the separate "OpenSCAD Tutorial" wikibook. "Overview" also comes to mind, but again a lot of its content is detail, not overview.
- Remove the "User Manual" section header, and maybe demote "Language Reference" to being a chapter.
- Remove "The OpenSCAD" from the titles of those top-level sections, which might make it less likely that a reader will think of them as books.
I thought about moving the language reference to a separate wikibook, but that would make the search picture worse.
from openscad.
from openscad.
The problem with splitting into two books is that then you couldn't hit both books with one search, except by doing a Wikibooks-wide search and trying to narrow it enough with keywords.
I think the better approach is to have one book - maybe even pulling in the currently-separate Tutorial book - and structuring it so that it's clear that that's how it's been done.
from openscad.
from openscad.
There's no law that says that the "user manual" can't have a reference section, so that particular aspect doesn't concern me. We'd have to change the text inside to avoid drawing that distinction. But since we don't publish anything other than a user manual, we could just drop the word "user".
I don't know Wikibooks well enough to know whether we can add hierarchy. But we can certainly put the word "reference" in appropriate titles.
from openscad.
Essentially there is one book with 2 major sections. To me it seems like the discussion is focusing on the wrong things.
Goto main book page: https://en.wikibooks.org/wiki/OpenSCAD_User_Manual
Use the appropriate search:
Select Search this book
and find a reasonable list of hits in the OpenSCAD Book only:
Notably that finds exactly the minkowski
entry on the Transformations
page mentioned in the original post as first hit.
The only action I can see here is to make that search field a bit more obvious and (if that works) adding external pointers directly to this. Maybe even have an additional "search" page with an explanation of the search behavior if someone feels like writing that.
from openscad.
The manual, titled "OpenSCAD User Manual", has two distinct sections, titled "The OpenSCAD User Manual" and "The OpenSCAD Language Reference". I think his concern is that he was trying to find reference information, and all of the search results say "OpenSCAD User Manual" - the first section - and none of them say "OpenSCAD Language Reference".
That first link does lead to the reference section, but it isn't instantly obvious that it does, and one might reasonably think that it leads to the first section instead. (And to confuse the issue further, the last link, which also could be construed to lead to the first section, leads to a single-page "printable" version of the second section.)
The problem is that "OpenSCAD User Manual" refers to both the book as a whole, and to the first section of that book.
from openscad.
Related Issues (20)
- Chore: renovate python scripts to py>=3.8
- Display colors when rendering using F6 HOT 3
- Customizer: Support vectors with more than 4 elements HOT 1
- Nightly Build Crashes During Render of Complicated Object HOT 15
- Does not see user color schemes (Mac OS 13.6.4) HOT 2
- Intersection not working, creating union instead HOT 5
- preview does not show diffrence() correctly HOT 1
- roof_ss.cc sans me HOT 1
- `$variable` assignment no longer seems to work. HOT 13
- really weird issue that might involve floats HOT 1
- Linear_extrude with 3d vector as height yields inapropriate result HOT 3
- let color() work in rendering mode too and allow to export colored STL files. HOT 1
- Save and restore GUI window state more reliably
- Splat 2D/3D functions HOT 7
- Document vector swizzling HOT 1
- Setting to do full Renders in place of Preview on AutoReload HOT 4
- path_extrudes() not loved by Manifold (or even CGAL, maybe...) HOT 10
- Add / change Metadata for 3mf export HOT 9
- Sadly, we can't add .scad files to the issues in the openSCAD repository HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openscad.