What’s problem you are encountering? I am trying to create a “Note”.
What have you tried that didn’t work? I found a few references in Brian’s documentation but the sequence of steps to create a note is not working. I’m not being systematic because I ran out of time on this about 2 hours ago, Notes I create in the project do not appear outside the project. Is this because I have to publish it?
Post a project example, link, or screenshot: Sorry, not going to waste my time on this. Login, share, publish is massively confusing and inconsistent with other platforms.
More to the point FINDING ANYTHING, even using CoPilot is a horrible time sink.
Hi, Ursula. I’m sorry you’re having trouble with this.
Project notes are part of the project. So if you can see a project, you can see its notes.
You can of course always see your own projects, including their notes.
Other people can see your projects if they’re published. If a project is shared but not published, then anyone with the project URL can see it in the editor – the view that looks like this:
Thank you! It boils down “share” and “publish” While I am not new to Snap! I use it sporadically, and hadn’t been in the environment for years maybe. (I use Turtlestitch more consistengly).
When I gave up searching for the explanation (2 hours of futzing vs. 20 minutes of constructive code work), I suspected it had to do with publishing but my login was also acting flakey (because Ididn’t agree to stay logged in) so I was out of time to try to debug this.
Food for thought: Snap! is an extremely ‘closed’ community that makes assumptions about use and doesn’t support multiple pathways to locating ‘how to do’ stuff in the enviroment. I clocked it: it took me 6 times as long to figure out something than to do something constructive. Not saying other platforms are any better, but its the reason Snap! is not my ‘go to” exploratory language. Far too much complexity is untransparent. I need help in navigating the environment. List processing for fun and provide I can do.
Hmm. Do you have the same complaint about Google Docs? They have even more varieties of sharing. They provide options such as “anyone,” “anyone with the URL,” “these people…” etc. in answer to “who can read this?” Maybe you’d be happier if we spelled out the options that way instead of calling them “share” and “publish.”
The way we do it is partly historical; for a long time we didn’t have the option to publish to the web site, so sharing by URL was the only mechanism for letting other people see your projects. When we built the community web site, we briefly considered changing the meaning of “share” to publishing on the site, but decided that we couldn’t unilaterally change the status of already existing projects. That’s why we have both “share” and “publish” options. That’s also why you have to share before you can publish, something we should probably change.
We should probably make heavier use of hovertext, so you could hover over the Share button and get a little speech balloon saying “allow anyone with the URL to read this project.” When we get …
P.S. I was going to say “the Reference Manual has an index, you know,” but to my extreme embarrassment it doesn’t have entries for the Share button and the Publish button. Mea culpa, mea maxima culpa!
> Notes” in order to see them.
…