Websites made out of scratch? Html embeded

iamunknown2

But you wouldn't need blocks, would you? All you would need if it were to be a non-OO language, you would only need 1 block. I would prefer it to be something like Markdown:

# This is a header!
## This is a subheader!

This is a sample paragraph.

* These are bullet pointss!
* Look how easy it is?

1. These are ordered lists!
2. Look how easy they are as well?

```javascript
alert("This will produce a codeblock, syntax-highlighted in JS.");
```
<!--You can also insert HTML into Markdown if you want!-->

This would produce

This is a header!

This is a subheader!

This is a sample paragraph.
These are bullet points!
Look how easy it is?
These are ordered lists!
Look how easy they are as well?
alert("This will produce a codeblock, syntax-highlighted in JS.");

Look at the source for the above quote recreated with BBCode. Which one's easier?

Last edited by iamunknown2 (July 3, 2015 09:33:33)

| My website | Using Geany | A Christian | Running Ubuntu MATE 14.04 with Flash 18.0 (release 0) | Search this with quotation marks on Google to view my posts: “ellipsepostpianolizard” (some posts may not show up) |

Moving on from Scratch? Learn Python/a scripting language (e.g Perl, JavaScript), then move on to a C derivative

bobbybee

iamunknown2 wrote:
But you wouldn't need blocks, would you? All you would need if it were to be a non-OO language, you would only need 1 block. I would prefer it to be something like Markdown:
-snip-
Look at the source for the above quote recreated with BBCode. Which one's easier?

Heh, markdown's easier. No one's arguing that :p

Granted, MD is less featureful than pure HTML, considering I don't count the ability to embed HTML as part of MD. Maybe that's better suited for Scratch blocks though

“Ooo, can I call you Señorita Bee?” ~Chibi-Matoran

NickyNouse

at risk of feeding a necropost
This thread inspired me to spend my afternoon modding Snap! into a webdev tool, and I'm excited by my progress. Nothing does anything yet, but I've removed the motion, looks, sounds, and pen categories and added blocks to 3 new categories: elements (blue), style (purple), and DOM (green). I also added a new reporter shape for elements and figured out how to make a hat-c-cap block:

I'm thinking the stage will become a webview and the green flag will act as a reload button, not sure what to do about the sprites panel tho. My original plan was to change the scripts/costumes/sounds tabs into Elements/Styles/Scripts, but I dunno how to do that yet.

QuillzToxic

NickyNouse wrote:
at risk of feeding a necropost
This thread inspired me to spend my afternoon modding Snap! into a webdev tool, and I'm excited by my progress. Nothing does anything yet, but I've removed the motion, looks, sounds, and pen categories and added blocks to 3 new categories: elements (blue), style (purple), and DOM (green). I also added a new reporter shape for elements and figured out how to make a hat-c-cap block:

I'm thinking the stage will become a webview and the green flag will act as a reload button, not sure what to do about the sprites panel tho. My original plan was to change the scripts/costumes/sounds tabs into Elements/Styles/Scripts, but I dunno how to do that yet.

Sweet, I'd have to show my it teacher xD

Firedrake969

NickyNouse wrote:
at risk of feeding a necropost
This thread inspired me to spend my afternoon modding Snap! into a webdev tool, and I'm excited by my progress. Nothing does anything yet, but I've removed the motion, looks, sounds, and pen categories and added blocks to 3 new categories: elements (blue), style (purple), and DOM (green). I also added a new reporter shape for elements and figured out how to make a hat-c-cap block:

I'm thinking the stage will become a webview and the green flag will act as a reload button, not sure what to do about the sprites panel tho. My original plan was to change the scripts/costumes/sounds tabs into Elements/Styles/Scripts, but I dunno how to do that yet.

I like it!

Would you let people use JS somehow?

One issue I can see is order of script/style (not that style order should matter?) loading, but if you're that advanced, go ahead and use regular HTML.

Last edited by Firedrake969 (July 4, 2015 17:05:09)

'17 rickoid

bf97b44a7fbd33db070f6ade2b7dc549

NickyNouse

Firedrake969 wrote:
NickyNouse wrote:
at risk of feeding a necropost
This thread inspired me to spend my afternoon modding Snap! into a webdev tool, and I'm excited by my progress. Nothing does anything yet, but I've removed the motion, looks, sounds, and pen categories and added blocks to 3 new categories: elements (blue), style (purple), and DOM (green). I also added a new reporter shape for elements and figured out how to make a hat-c-cap block:

I'm thinking the stage will become a webview and the green flag will act as a reload button, not sure what to do about the sprites panel tho. My original plan was to change the scripts/costumes/sounds tabs into Elements/Styles/Scripts, but I dunno how to do that yet.
I like it!

Would you let people use JS somehow?

One issue I can see is order of script/style (not that style order should matter?) loading, but if you're that advanced, go ahead and use regular HTML.

All the blocks that aren't style or elements will be converted to js. I think what I'll do is limit you to one style block and one body block, otherwise there's some kind of a runtime error. The style will load before scripts.

Firedrake969

window.onload?
Element selectors?

(but if they want that they probably should use HTML, like I've already said

)

'17 rickoid

bf97b44a7fbd33db070f6ade2b7dc549

NickyNouse

Firedrake969 wrote:
window.onload?
Element selectors?

(but if they want that they probably should use HTML, like I've already said )

I'm thinking something like

when (elements with class [button] ::motion) [clicked v] :: hat control

liam48D

NickyNouse wrote:
Firedrake969 wrote:
window.onload?
Element selectors?

(but if they want that they probably should use HTML, like I've already said )
I'm thinking something like
when (elements with class [button] ::motion) [clicked v] :: hat control

But then you get..

when (elements with class [button] :: motion) [clicked v] :: hat control
div :: motion cstart
  text [Lol how is this processed?] :: motion
end

202e-202e-202e-202e-202e UNI-CODE~~~~~

NickyNouse

liam48D wrote:

-snip-
But then you get..

when (elements with class [button] :: motion) [clicked v] :: hat control
div :: motion cstart
  text [Lol how is this processed?] :: motion
end

something along the lines of:

when (elements with class [button] :: motion) [clicked v] :: hat control
set (element with ID [foo] :: motion) content to (join ([value v] attribute of (this ::motion) ::motion)[ selected]) :: pen

…the DOM category is for JS manipulation, and all the operator/control blocks can be used to help with that

Last edited by NickyNouse (July 4, 2015 22:46:58)

Firedrake969

But what would happen if you did the former?

'17 rickoid

bf97b44a7fbd33db070f6ade2b7dc549

NickyNouse

Firedrake969 wrote:
But what would happen if you did the former?

I'm working on a way to keep elements, style, and JS separate

liam48D

NickyNouse wrote:
Firedrake969 wrote:
But what would happen if you did the former?
I'm working on a way to keep elements, style, and JS separate

So if you combined HTML with JavaScript would your computer explode?

202e-202e-202e-202e-202e UNI-CODE~~~~~

CatsUnited

liam48D wrote:
NickyNouse wrote:
Firedrake969 wrote:
But what would happen if you did the former?
I'm working on a way to keep elements, style, and JS separate
So if you combined HTML with JavaScript would your computer explode?

<html>
    <script>
        console.log("Hello");
    </script>
</html>

It did not explode.
Anyway, why separate it?

bottom text

NickyNouse

CatsUnited wrote:
liam48D wrote:
NickyNouse wrote:
Firedrake969 wrote:
But what would happen if you did the former?
I'm working on a way to keep elements, style, and JS separate
So if you combined HTML with JavaScript would your computer explode?
<html>
    <script>
        console.log("Hello");
    </script>
</html>
It did not explode.
Anyway, why separate it?

To keep everything straightforward I guess. That's why the largest element tag is body instead of html, because I don't trust the user to know what they're doing or make good decisions

liam48D

<html>
    <script>
        <p>Lolwut</p>
        <b class="demo">Would this cause problems though</b>
    </script>
</html>

202e-202e-202e-202e-202e UNI-CODE~~~~~

Firedrake969

liam48D wrote:

<html>
    <script type='text/jsx'>
        var LolWut = React.createClass({
            render: function()  {
                return (
                    <p>Lolwut</p>
                    <b class="demo">Would this cause problems though</b>
                );
            }
        });
    </script>
</html>

Fixed, but you'd still need the JSX compiler and React.

Last edited by Firedrake969 (July 5, 2015 16:10:17)

'17 rickoid

bf97b44a7fbd33db070f6ade2b7dc549

Greenninjaxx25

Never thought of that but i guess since u could embed, i could embed to makea web!!!!!!!!!
So this way i could embed why online scratch game to a website
Thx people!!!

tuyger

Personally I use things like Angular and Polymer to do more things in plain HTML. Just using elements and attributes for as much as possible.

For example, hello “your name here”:

<input type=“text” ng-model=“yourName” />
<p>Hello, {{ yourName }}!</p>

<p>Here's google maps:</p>
<google-map latitude=“37.77493” longitude=“-122.41942”></google-map>

To keep it simple-ish

masterex1000

This would be so much fun to do. i think that i will actually try this!!!

Generation 379: the first time you see this copy and paste it on top of your sig in the scratch forums and increase generation by 1. Social experiment.

Discuss Scratch