Question: how should we introduce [scratchblocks] to new users?

blob8108

We've now implemented the [scratchblocks] tag on the forums, similar to the one from the 1.4 site.

The full guide to the syntax is on the wiki, but we need a nice way of introducing new users to the system and showing them how to use it.

On the old site, we had a short explanation and an example below the “new post” textbox.

There might not quite be room for that, as that's where the post preview goes on the new site. Lightnin suggested maybe we could add a button to the post edit toolbar (the one above the post textbox), next to the picture/link icons.

Lightnin emphasised making it clear, simple, and easy to understand.

Any suggestions?

Progress so far

Thanks to some suggestions, I'm thinking of an expandable window similar to the smilies dropdown in the post bar.

Some computer keyboards don't have keys for brackets (like < >, [ ], or ( )), so the dropdown should have buttons for those:

blocks:           [scratchblocks]
number/reporter:  ( )
boolean:          < > 
text:             [ ]
dropdown:         [ v]

Clicking on the brackets would insert the brackets into the textbox and place the cursor between them.
g through a menu. But maybe you're right.

Check out the live mockup!

Last edited by blob8108 (Sept. 2, 2013 19:54:19)

curiouscrab

Test:

move (10) steps

I say it gets added in the toolbar that has the stuff in it like click on the picture to insert a picture and the chain link for a link. Where you make replies, that toolbar. Also, a forum about it would be cool. Could you make a forum? Also, a testing ground is here.

ProdigyZeta7

Add a disclaimer that says

Please use the [scratchblocks] responsibly.

dracae

When gf clicked
wait until <(scratchblock bbc code released?) = (1)>
set [sad v] to (1)

Last edited by dracae (Aug. 30, 2013 22:45:57)

jh1234l

When gf clicked
forever
if ((scratchblocks released?) = (1))
Clear rules
Clear info
Add [No spamming with scratch blocks] to rules
Add [Scratch blocks are under the same rules as regular words] to rules
Add [Put scripts between (scratchblocks) and (/scratchblocks) with square brackets.] to info
Add [Booleans = <booleans>, reporters = (reporters)] to info
end
end

Last edited by jh1234l (Aug. 30, 2013 23:04:28)

DotDash

Edit: ^-^

Hmmmmm…

TEST:

when gf clicked
forever
 if <[hi] = [true]>
 say [hi!]
 end
end[/sratchblocks]

Last edited by DotDash (Aug. 30, 2013 23:33:01)

curiouscrab

dracae wrote:

When gf clicked
wait until <(scratchblock bbc code released?) = (1)>
set [sad v] to (1)

jh1234l wrote:

When gf clicked
forever
if ((scratchblocks released?) = (1))
Clear rules
Clear info
Add [No spamming with scratch blocks] to rules
Add [Scratch blocks are under the same rules as regular words] to rules
Add [Put scripts between (scratchblocks) and (/scratchblocks) with square brackets.] to info
Add [Booleans = <booleans>, reporters = (reporters)] to info
end
end

DotDash wrote:
Edit: ^-^

Hmmmmm…

TEST:
when gf clicked
forever
 if <[hi] = [true]>
 say [hi!]
 end
end

Stop spamming with scratchblocks!

stop all

Edit:Please remember to close your scratchblocks tags and spell it correctly so quoting is possible!

Last edited by curiouscrab (Aug. 30, 2013 23:35:58)

ProdigyZeta7

ProdigyZeta7 wrote:
Add a disclaimer that says
Please use the [scratchblocks] responsibly.

DotDash

curiouscrab wrote:

dracae wrote:

When gf clicked
wait until <(scratchblock bbc code released?) = (1)>
set [sad v] to (1)

jh1234l wrote:

When gf clicked
forever
if ((scratchblocks released?) = (1))
Clear rules
Clear info
Add [No spamming with scratch blocks] to rules
Add [Scratch blocks are under the same rules as regular words] to rules
Add [Put scripts between (scratchblocks) and (/scratchblocks) with square brackets.] to info
Add [Booleans = <booleans>, reporters = (reporters)] to info
end
end

DotDash wrote:
Edit: ^-^

Hmmmmm…

TEST:
when gf clicked
forever
 if <[hi] = [true]>
 say [hi!]
 end
end

Stop spamming with scratchblocks!

stop all

Edit:Please remember to close your scratchblocks tags and spell it correctly so quoting is possible!

Lol i was just making sure it worked.

curiouscrab

DotDash wrote:
curiouscrab wrote:
dracae wrote:
When gf clicked
wait until <(scratchblock bbc code released?) = (1)>
set [sad v] to (1)
jh1234l wrote:
When gf clicked
forever
if ((scratchblocks released?) = (1))
Clear rules
Clear info
Add [No spamming with scratch blocks] to rules
Add [Scratch blocks are under the same rules as regular words] to rules
Add [Put scripts between (scratchblocks) and (/scratchblocks) with square brackets.] to info
Add [Booleans = <booleans>, reporters = (reporters)] to info
end
end 
DotDash wrote:
Edit: ^-^

Hmmmmm…

TEST:
when gf clicked
forever
 if <[hi] = [true]>
 say [hi!]
 end
end
Stop spamming with scratchblocks!
stop all
Edit:Please remember to close your scratchblocks tags and spell it correctly so quoting is possible!
Lol i was just making sure it worked.

Ok, but the other 2 were spamming. Also, you spelled scratchblocks wrong when closing the code.

Last edited by curiouscrab (Aug. 30, 2013 23:37:34)

DotDash

oh…….lol

dracae

When gf clicked
wait until <([mood v] of [curiouscrab v]) = [Angry]>
say [Sorry, I was just testing it out]

Last edited by dracae (Aug. 31, 2013 00:05:23)

DotDash

dracae wrote:

When gf clicked
wait until <([mood v] of [curiouscrab v]) = [Angry]>
say [Sorry, I was just testing it out]

lol

EH7meow

blob8108 wrote:
On the old site, we had a short explanation and an example below the “new post” textbox. (If someone could find me a screenshot, that'd be much appreciated.) .

Here it is and here is a cool way they did it before that. Those links are to the wiki.

blob8108

EH7meow wrote:
Here it is

Thank you!

dracae

When I receive [scratchblocks are out v]
say [I am sad]
set [explanation v] to (People will obnoxiously use this in normal conversation)
set [mood v] to (Hypocritical)

[/scratchblocks]

(Lol you can't close off scratchblocks)

Last edited by dracae (Aug. 31, 2013 12:02:11)

ProdigyZeta7

dracae wrote:

When I receive [scratchblocks are out v]
say [I am sad]
set [explanation v] to (People will obnoxiously use this in normal conversation)
set [mood v] to (Hypocritical)

[/scratchblocks]

(Lol you can't close off scratchblocks)
[/quote]

broadcast to user [dracae v] message [Reply v] potato (9001)
say [You're making it worse by contributing to the obnoxious use of scratchblocks] for (5) secs
say [Oh, oops, I'm using them too. :P] for (3) secs
stop [this silly script v]

Last edited by ProdigyZeta7 (Aug. 31, 2013 16:34:23)

Failord

Want to hear what I think? Expandable/collapsable window explaining them. Sort of like what 1.4 had, but maybe moved to a more convenient place and more thoroughly explained.

Some people's computer keyboards don't have keys for <, >, [, ], ^, etc. Maybe the bar under “message” with the emotes and boldface and stuff could include those.

when [forums use v] > (0)
if < (scratchblocks in normal conversation) > (9000) >
say [It'll die down eventually.] for (2) secs
wait (1) secs
say [...Eventually.] for (1) secs
end

Last edited by Failord (Aug. 31, 2013 18:03:02)

scratchisthebest

How about embedding the project-to-scratchblocks thing in the toolbar somewhere?

You know how the Smilies thing drops down? Maybe there could be a dropdown like that, but with the 10 block categories instead. Each of those would have a submenu inside with the individual blocks.

blob8108

scratchisthebest wrote:
You know how the Smilies thing drops down? Maybe there could be a dropdown like that

Failord wrote:
Expandable/collapsable window explaining them.

Yeah, I'm starting to think that's how we should do it. Particularly as

Some people's computer keyboards don't have keys for <, >, [, ], ^, etc.

So, the dropdown could have buttons like:

blocks:           [scratchblocks]
number/reporter:  ( )
boolean:          < > 
text:             [ ]
dropdown:         [ v]

…which would insert the brackets and place the cursor between them.

scratchisthebest wrote:
a dropdown like that but with the 10 block categories instead. Each of those would have a submenu inside with the individual blocks.

I'm not sure about having all the blocks listed: typing them in seems much quicker than going through a menu. But maybe you're right.

Thanks, guys!

So, who wants to do me a mockup?

Last edited by blob8108 (Aug. 31, 2013 19:44:31)

Discuss Scratch