"http:// ()" sensing block.

cs293450

(http://[snap.berkeley.edu])

reports the code of a url of a website.

Last edited by cs293450 (March 20, 2016 19:49:50)

Ravenpaw-Warrior

75% No support and 25% Support. Duplicate too, and could lead to an innopropiate site.

JonathanSchaffer

no support: would glitch/lag.

(https://[scratch.mit.edu/]::sensing)

would report a ton of gooble-goppity-gop.

Last edited by JonathanSchaffer (March 20, 2016 17:49:44)

stickfiregames

What does it do? If it actually does report the URL of the website like you said, it would be useless since it literally just reports whatever you type into it.

Sheep_maker

So

(http://[www.wwwdotcom.com/]::sensing)

would report

http://www.wwwdotcom.com/

How would this be used?
Unless it returns the HTML of the page

DownsGameClub

Does that have any use? Please explain how this would be useful.

BookOwl

I'm pretty sure that

(http://[example.com] :: sensing)

would act like it does in Snap!, namely it would return the source of that page. For example, if "example.com" was put in the box, it would report

<!doctype html>
<html>
<head>
    <title>Example Domain</title>
    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
        
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 50px;
        background-color: #fff;
        border-radius: 1em;
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        body {
            background-color: #fff;
        }
        div {
            width: auto;
            margin: 0 auto;
            border-radius: 0;
            padding: 1em;
        }
    }
    </style>    
</head>
<body>
<div>
    <h1>Example Domain</h1>
    <p>This domain is established to be used for illustrative examples in documents. You may use this
    domain in examples without prior coordination or asking for permission.</p>
    <p><a href="http://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>

Semi-support, while it would be incredibly useful and open up a whole new category of projects (live weather reporting, anyone?), it could also be able to be used to show inappropriate content. But since projects that do that could be reported, put me at 90% support.

Last edited by BookOwl (March 20, 2016 19:44:48)

happyland440

BookOwl wrote:

I'm pretty sure that

(http://[example.com] :: sensing)

would act like it does in Snap!, namely it would return the source of that page. For example, if "example.com" was put in the box, it would report

<!doctype html>
<html>
<head>
    <title>Example Domain</title>
    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
        
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 50px;
        background-color: #fff;
        border-radius: 1em;
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        body {
            background-color: #fff;
        }
        div {
            width: auto;
            margin: 0 auto;
            border-radius: 0;
            padding: 1em;
        }
    }
    </style>    
</head>
<body>
<div>
    <h1>Example Domain</h1>
    <p>This domain is established to be used for illustrative examples in documents. You may use this
    domain in examples without prior coordination or asking for permission.</p>
    <p><a href="http://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>

Semi-support, while it would be incredibly useful and open up a whole new category of projects (live weather reporting, anyone?), it could also be able to be used to show inappropriate content. But since projects that do that could be reported, put me at 90% support.

Yes, if it's used for the purpose above. Again, people can hide inappropriate content not viewable on the website like:

//Inappropriate content

Just report that.

Also, this would take up a TON of data and would look weird as a variable.

Last edited by happyland440 (March 20, 2016 20:58:27)

1004587

BookOwl wrote:

I'm pretty sure that

(http://[example.com] :: sensing)

would act like it does in Snap!, namely it would return the source of that page. For example, if "example.com" was put in the box, it would report

<!doctype html>
<html>
<head>
    <title>Example Domain</title>
    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
        
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 50px;
        background-color: #fff;
        border-radius: 1em;
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        body {
            background-color: #fff;
        }
        div {
            width: auto;
            margin: 0 auto;
            border-radius: 0;
            padding: 1em;
        }
    }
    </style>    
</head>
<body>
<div>
    <h1>Example Domain</h1>
    <p>This domain is established to be used for illustrative examples in documents. You may use this
    domain in examples without prior coordination or asking for permission.</p>
    <p><a href="http://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>

Semi-support, while it would be incredibly useful and open up a whole new category of projects (live weather reporting, anyone?), it could also be able to be used to show inappropriate content. But since projects that do that could be reported, put me at 90% support.

^^^
Except I support fully. Like BookOwl said, this could be used to make revolutionary projects like his example.

DaSpudLord

Oh yeah, this would open up a TOTALLY new range of projects. I fully support. However, how would returns translate into the reporter? And what would the project do while it is waiting for the page to load? Perhaps this would be better-

load http://[] to [list v] and wait::list

Support for that.

Last edited by DaSpudLord (March 21, 2016 00:17:21)

alexphan

Ravenpaw-Warrior wrote:
75% No support and 25% Support. Duplicate too, and could lead to an innopropiate site.

Well, the OP is asking to display the actual html code for the website.
I support for

line () of http://[] :: list reporter

Ninkancho

I don't know. HTML transclusion seems a tad too complex for Scratch, wouldn't you say?

Scratcher1002

Ninkancho wrote:
I don't know. HTML transclusion seems a tad too complex for Scratch, wouldn't you say?

HTML is the most basic you can get.. (Never tried Python.) I 90% support as per BookOwl:

BookOwl wrote:

I'm pretty sure that

(http://[example.com] :: sensing)

would act like it does in Snap!, namely it would return the source of that page. For example, if "example.com" was put in the box, it would report

<!doctype html>
<html>
<head>
    <title>Example Domain</title>
    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
        
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 50px;
        background-color: #fff;
        border-radius: 1em;
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        body {
            background-color: #fff;
        }
        div {
            width: auto;
            margin: 0 auto;
            border-radius: 0;
            padding: 1em;
        }
    }
    </style>    
</head>
<body>
<div>
    <h1>Example Domain</h1>
    <p>This domain is established to be used for illustrative examples in documents. You may use this
    domain in examples without prior coordination or asking for permission.</p>
    <p><a href="http://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>

Semi-support, while it would be incredibly useful and open up a whole new category of projects (live weather reporting, anyone?), it could also be able to be used to show inappropriate content. But since projects that do that could be reported, put me at 90% support.

Mrcomputer1

Support

helloandgoodbye9

BookOwl wrote:

I'm pretty sure that

(http://[example.com] :: sensing)

would act like it does in Snap!, namely it would return the source of that page. For example, if "example.com" was put in the box, it would report

<!doctype html>
<html>
<head>
    <title>Example Domain</title>
    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
        
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 50px;
        background-color: #fff;
        border-radius: 1em;
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        body {
            background-color: #fff;
        }
        div {
            width: auto;
            margin: 0 auto;
            border-radius: 0;
            padding: 1em;
        }
    }
    </style>    
</head>
<body>
<div>
    <h1>Example Domain</h1>
    <p>This domain is established to be used for illustrative examples in documents. You may use this
    domain in examples without prior coordination or asking for permission.</p>
    <p><a href="http://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>

Semi-support, while it would be incredibly useful and open up a whole new category of projects (live weather reporting, anyone?), it could also be able to be used to show inappropriate content. But since projects that do that could be reported, put me at 90% support.

Hard to say it better myself. Also, it means you have to learn html. Crazy idea - Ill support if it implants Elemental.

BookOwl

If these blocks were added, this block would be even more useful.

Gaza101

Support! Perhaps there could also be some blacklisted terms for URLs too in order to prevent misuse.

Ninkancho

Scratcher1002 wrote:
Ninkancho wrote:
I don't know. HTML transclusion seems a tad too complex for Scratch, wouldn't you say?
HTML is the most basic you can get.. (Never tried Python.)

Yes, but it's still an entire markup language, and most of its syntax isn't exactly obvious or kid-friendly. Most kids probably don't even know anything about HTML. And Scratch isn't the place to learn new languages, other than Scratchblocks itself.

moss-shadow

cs293450 wrote:
(http://[snap.berkeley.edu])
reports the code of a url of a website.

Just wondering, why would this script be useful?

BookOwl

moss-shadow wrote:
cs293450 wrote:
(http://[snap.berkeley.edu])
reports the code of a url of a website.
Just wondering, why would this script be useful?

Did you see my post?

Discuss Scratch