Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranî)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
Now that you know what is remix, let's quickly talk about how it works that you can add files and what
are these files that are already there.
So in the previous versions of Remix, there were no workspaces and this is kind of a new thing and
not so new anymore.
It's already there for a year or around.
But before there were no workspaces.
So what a workspace is.
Workspaces are like folders since remix is not really opening any folder on your hard drive.
I mean, you can technically I think there is a daemon for that, but internally it's kind of meant
to work around these projects and they call these workspaces.
So when you just open remix of the theorems that work for the first time, then you have a default workspace
and you can add new workspaces like new folders over here, and then you can give them a name and you
can even choose a template if you want to use one of those open Zeppelin smart contracts or just the
blank one or the default template, which is this one.
I'm not going to create a new workspace now.
I'm just using the default workspace throughout our course because I think I don't need another workspace.
If you want to create one, if you want to play around with that, fine.
The more important thing is what do you do inside those workspaces?
And that is you can create new files.
And since this is not a normal idea, like a is code or so when you can just like right click, it will
open the context menu of your browser unless you click on a file.
Then you have to, I think, select the folder where you want to create a file and then you create a
new file in there and you can name this for example, my contract dot sole for solidity file and what
will happen, maybe will happen, maybe not is that it gets directly compiled.
And you see now this is really tailored for solidity development because there is an integrated compiler,
there is an integrated test chain and it is also already highlighting solidity code.
So if you write something like a contract, my contract, and then you make curly brackets open and
closed, you see it's already highlighting the right syntax and so on and so forth.
So everything is kind of tailored around of development, which is the nice thing about it.
What happens if the contract is compiled?
It lands in an artifacts folder.
More on that later.
Don't worry about it.
And in remix, since a few version, you also have the option to script stuff because the whole thing
is JavaScript.
So it also injects a JavaScript environment.
It's JavaScript in JavaScript.
How nice can it be?
They also give you sample scripts for deploying smart contract using web free chess or ether as if you
don't know what it is.
Don't worry about it.
We are talking about those libraries later and you can run unit tests, which I never used in remix
and we are maybe going to talk about it in the course.
But normally I do testing of remix inside the Code in Truffle Hard Hat or Foundry Remix also has a JavaScript
console over here on the bottom, so it's interactive.
You can do that free for the free library, the utils stored, I don't know, a free and then create
an Kazak hash of this string that I just entered and that would be the case cache if you don't know
what it is.
Also don't worry about it.
What is important is, you know, you have to file this over here.
You have an editor on the right side.
There is also the small one over here.
Everything is there and there are plugins in remix and those plugins I the whole thing is a is a plugin
architecture.
I think even the file explorer is a plugin, but then you have a compiler which we are talking about
next where you have different versions and so on and you have a deploy and run transaction plugin where
you can actually test your smart contracts and you have a ton of more plugins if you want to, you can
go through them.
Maybe we use the debugger later and I think that's it, what we are going to use in this course because
we are going to move everything off chain of remix.
If you if you go to the settings, then in the settings you have a number of things, but if you like
there is also different themes.
So you can change the Yeah look of remix to something to your liking.
I stay with the dark theme for now, which is a total contrast to the light theme which we did in the
previous course.
In the next lecture, we are going to create the little smart contract.
We are going to start it, stop it and see how we can interact with it from within.
Remix.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.