(days since MM( ) / DD( ) / YYYY ( )::sensing)
(days between MM( ) / DD( ) / YYYY ( ) and MM( ) / DD( ) / YYYY ( )::sensing)

why in the world would you use mm/dd/yyyy?

TheExample_2020 wrote:

(#61)
why in the world would you use mm/dd/yyyy?

The OP is probably American.
But anyway, it should probably be DD/MM/YYYY since only 34% of Scratchers are American.

These blocks are so messy. A vast majority of the blocks in scratch have 0, 1, or 2 parameters. There are a couple with 3 but none with 4 or more, much less 6. It's also very unnecessary to have one with 3 parameters too. The only blocks with 3 parameters on scratch are ones that are completely essential blocks that would not function without it (the insert and replace list blocks). That block would function just as well with 1 or no parameters. Also, these blocks don't allow for anything that the current block doesn't, nor does it make anything easier. It just looks ugly and confusing for no reason.

Also, the latter 3 blocks are useless and unnecessary. Blocks that just function as constants are already pretty unneeded given how easy they are to workaround, but at least blocks like a pi block would have actually uses. Those blocks are useful for literally nothing. Why would you need to use any of those three dates in any scenario? How would it even output a date. Overall, these blocks are not very good.

Those blocks can't be applicable in the offline editor.

there was a dupe a few days ago so BUMP

-LekkerGames- wrote:

Ah, the most useless block on Scratch.

(days since 2000)

Nope. No. Absolutely not.

The days since 2000 block is the most precise timing method in Scratch, so it's extremely useful. And, what you've suggested can be easily worked around with some addition.

RubiksRocker wrote:

Those blocks can't be applicable in the offline editor.

Yes, all of them can, due to the way the offline editor works.

when it actually gets replaced
the existing projects with

(days since 2000)

block will be converted to

(days since MM (1) / DD / (01) YYYY / (2000) ::sensing)

problem solved

(days since MM (1) / DD / (01) YYYY / (2000) ::sensing)

i feel like this block looks messy.
should be

(days since [mm] / [dd] / [yyyy] ::sensing)

on the block pallete, by default it would say mm dd yy in the inputs and you can change the input.

starlightsparker wrote:

(#69)
should be

(days since [mm] / [dd] / [yyyy] ::sensing)

on the block pallete, by default it would say mm dd yy in the inputs and you can change the input.

does that mean it would be text entry and not number entry? would i be able to do this??

(days since [january] / [first] / [nineteen seventy] :: sensing)

breakfast_for_dinner wrote:

starlightsparker wrote:

(#69)
should be

(days since [mm] / [dd] / [yyyy] ::sensing)

on the block pallete, by default it would say mm dd yy in the inputs and you can change the input.

does that mean it would be text entry and not number entry? would i be able to do this??

(days since [january] / [first] / [nineteen seventy] :: sensing)

I never implied it’s text entry. Number entry.

starlightsparker wrote:

(#71)
I never implied it’s text entry. Number entry.

but you said

starlightsparker wrote:

by default it would say mm dd yy in the inputs

breakfast_for_dinner wrote:

starlightsparker wrote:

(#71)
I never implied it’s text entry. Number entry.

but you said

starlightsparker wrote:

by default it would say mm dd yy in the inputs

I’m so silly I just realized there can’t be text in number inputs but that’s text so err
Well idk
I said that to avoid confusion on the date format but..
Well I guess they could make it so that you can type in words?

starlightsparker wrote:

(#73)
I’m so silly

welcome to sillyland, how was the fall?

starlightsparker wrote:

(#73)
Well I guess they could make it so that you can type in words?

why? dates are numbers. and how would this work in other languages?

starlightsparker wrote:

breakfast_for_dinner wrote:

starlightsparker wrote:

(#69)
should be

(days since [mm] / [dd] / [yyyy] ::sensing)

on the block pallete, by default it would say mm dd yy in the inputs and you can change the input.

does that mean it would be text entry and not number entry? would i be able to do this??

(days since [january] / [first] / [nineteen seventy] :: sensing)

I never implied it’s text entry. Number entry.

Or the ST could just use an HTML <input type=“date”> element, or create a date picker. If they did that, it would likely look like

(days since (1/1/2000 v) :: sensing)

Where the date picker appears when that box is clicked/tapped, and it accepts variable inputs.

BigNate469 wrote:

starlightsparker wrote:

breakfast_for_dinner wrote:

starlightsparker wrote:

(#69)
should be

(days since [mm] / [dd] / [yyyy] ::sensing)

on the block pallete, by default it would say mm dd yy in the inputs and you can change the input.

does that mean it would be text entry and not number entry? would i be able to do this??

(days since [january] / [first] / [nineteen seventy] :: sensing)

I never implied it’s text entry. Number entry.

Or the ST could just use an HTML <input type=“date”> element, or create a date picker. If they did that, it would likely look like

(days since (1/1/2000 v) :: sensing)

Where the date picker appears when that box is clicked/tapped, and it accepts variable inputs.

But people might be confused on the date format though

starlightsparker wrote:

But people might be confused on the date format though

It wouldn't just be text, it would only show text. The actual date picking would use an interface designed for it, likely resembling a calendar. Alternatively, it could use HTML's built-in date input element: https://bignate469.github.io/random-stuff/date-input/

Bumping because of a duplicate.