Stimulus: Escribir JavaScript profesional

Hey @symfonyace ,

Yeah, good question, because it's probably not very clear from the video. Actually, Ryan just reloads the page after the sidebar is gone i.e. he clicks the button, the sidebar is animated and removed completely, then he reloads the page in the browser (presses a shortcut like Cmd + R on a Mac to reload the page) that loads a new HTML page again with the sidebar, and finally clicks the button again to remove the sidebar. And so on, just super simple and no magic ;)

Thank you for asking about Ryan! Unfortunately, Ryan passed away last year. You can read the related blog post about him here: https://symfonycasts.com/blog/remembering-ryan-weaver

Cheers!

Update: I found the "aside" element in homepage.html.twig and was able to continue the video.

Also, let me just add that not everybody is using PHPStorm. I am using VSCode and not all that functionality you show off is available here. I feel like this course should focus on purely Symfony and not utilize some features PHPStorm includes. I get it: it is the defacto IDE for PHP. Just know that some of us just learning Symfony did not pay for PHPStorm and are using freely available resources instead. And I had to heavily add extensions to VSCode to even follow this course from the beginning. Just letting my voice heard.

Hey Kay,

I'm happy to see you were able to find that youself, good job!

Thank you for your interest in SymfonyCasts tutorials! Yes, you're totally right, not all devs use PhpStorm for their own reasons, also it's just a matter of taste too. Though we would like to recommend it as the best IDE for PHP and Symfony projects. We're trying to avoid using specific PhpStorm features unless it helps to save some time in the video, and when users should be clear enough on how to do that manually. We constantly try to keep it in mind, and I believe you should not encounter such moments in the tutorials very often.

Anyway, thanks again for reminding that, we appreciate it. And I agree with you on this. If you ever have any problems following our tutorials - please, feel free to ask your questions in the comments section below the video and our support team will help you :)

Cheers!

Hi Victor.. I will admit of joining the discussion about the IDEs.. I just have an idea - I totally understand the point that you in SymfonyCasts are using PHPStorm (thanks God not vim :D) and totally no point in changing that, - but maybe SymfonyCasts authors from now on could check out VSCode as it is free (well.. better probably, VSCodium, the Free as in Freedom, not as in a free beer, and Open - the source code for "core" VSCode is theoretically open-sourced but the binary build is a bit different, quite hard to explain in short time, I will rather recommend to read about it online [ https://medium.com/gopypi/issues-with-vscode-license-you-should-worry-fdb784796b6d ] - unfortunately it seems that VSCode and it's open source forks are not 100%-compatible) and then in the upcoming series just shortly explain, how to perform some PHPStorm-specific code edit / generation actions in VSCodium?

Or, maybe a one-shot/some short series like "VScode/VSCodium for PHP Geeks"?

Also, it is worth checking out, probably some of SF subscribers/watchers are collage students, - as far as I know, there is a discount for students for Jetbrains family tools? Would be worth mentioning somewhere, maybe folks do not know this.

Regardless, SymfonyCasts is amazing, and you can even use Vim (well, honestly, Vim IS brilliant.. just maybe not for everyone/it HAS a big learning curve :D ) I will continue to watch it, as Ryan did a great job, let's simply say his unconventional talent as a tutor and a teacher made me interested in coming back to learn Symfony.. His death is such a loss for all programming community, I believe.. I just hope Kevin and other SF authors (Leanna's tutorials are also amazing) will try to tread in His footsteps..

Hey Jan-Makar,

Thank you for your interest in SymfonyCasts tutorials! ♥️

We have a lot of discussions internally about IDE, and we're constantly trying to improve our educational path in videos to make it as smooth as possible for our users. All you said definitely makes sense, and I agree on it. Many cool devs indeed use other IDEs (or even VIM that is still crazy for me :) ), that's just a matter of taste, devs may just get used to specific tools and use them for years, or just a price issue. In our tutorials, we're mostly focusing on writing code and use very little hotkeys and features so that the users who follow our courses on a different IDE may not be too confused. And even when we use some tricks like implementing methods etc - we make it clear so that people could just type them instead of using the auto-generation feature from IDE. But once again, it's usually very rarely when we do it.

Your "VScode/VSCodium for PHP Geeks" indeed sounds like a good course, we have a course about PhpStorm btw: https://symfonycasts.com/screencast/phpstorm - similar about VScode/VSCodium would be cool to have too. Though I can't say when it may happen, because all our team members indeed use PhpStorm for personal use also, and it's indeed one of the best IDE you can find for PHP, and with the Symfony plugin, I think it's probably the best one for Symfony.

We would like to stick to PhpStorm for our future tutorials as well, just to keep videos consistent. And changing it have little sense fairly speaking, first of all, because I think most of the devs still use PhpStorm if we changed it to VSCode, for example, VSCode guys would be happy, but PhpStorm guys will write to us the same :) So, considering facts I mentioned above, we're trying to very little features of the IDE during the code to do not overcomplicate and better focus on the topics we're learning in the course.

Btw, yes, PhpStorm has discounts for students, and I think it's pretty clear on the pricing page when you look for a license. Actually, they have many "Special Offers" for their licenses so I would recommend you to check them, maybe you fit for a category there. And even if nothing fits, a little-known fact but PhpStorm has EAP (early access program) that allows you to use the latest beta version of PhpStorm just literally free - you can check it here: https://www.jetbrains.com/phpstorm/nextversion/ . So I think it still should be pretty much accessible for all types of users.

I hope that helps! And thank you for your understanding! :)

Cheers!

OMG! I just realized that for some reason, I jumped ahead to chapter 18 instead of doing chapter 15! Idk how that happened, I'm so sorry. I was just following along the track and it landed me on Chapter 18, and I didn't check!

You ARE creating that partial twig file in Chapter 15 that I was kinda missing in this video. Urgh!!! Again, I'm so sorry.

Hey Kay,

Oh, no problem! That may happen if you open that Ch18 in a new tab and play the video, then the system could return you back to that chapter when you ocntinue the course. Or it was just an accidental click that may happen too. Anyway, I'm glad to hear you're back on the right path ;)

If you ever have any questions following our tutorials - please, just ask!

Cheers!

Much appreciated. Thanks!

Hey Himanshu,

If you're talking about web sockets - we have a few screencasts about Mercure Symfony component, kind of like web sockets but cooler :) You can check them here: https://symfonycasts.com/search?q=mercure&sort=most relevant&types[]=video - you can leverage our advanced search on SymfonyCasts to find more content related to a specific stack. Unfortunately, no content about express@4.

I hope it helps!

Cheers!

Hey Rom,

I don't see we use that on this tutorial, or am I missing something? If so, please, could you link me to the correct chapter? Also, could you tell me what exactly deprecation message do you see about that preload option? Or do you mean it's gone from the recipe now? If so, IIRC that should be enabled by default now, you can check the source HTML code to see it includes preload. If not, you can always enable it manually in the importmap youself.

Cheers!

Hey @John-S

Thank you for your feedback and I agree with you, all of this can be too much. By the way, we have a dedicated tutorial for Stimulus and Symfony UX https://symfonycasts.com/screencast/stimulus

Cheers!

Hey @pasquale_pellicani ,

It depends on your needs, the project, and your knowledge. We do recommend Stimulus/Turbo as it's a straightforward tool with a nice Symfony integration. This is just ideal if you have a server-side project and want to give it a feeling of single-page application. It's ideal if you're OK with rendering templates server-side and let Stimulus handle it for you. In short, you just need to understand Stimulus, it's basic idea and how it works. For this - we do recommend you to watch this Stimulus course :)

But if Stilulus isn't enough for your needs, i.e. if you need more complex UI, if you want to render UI client-side without sending AJAX requests to the server and get already rendered template response that Stimulus just insert into the page for you - then take a look at more serious UI frameworks like VueJS, or React/Angular for example. They all are kinda good, and if you already know something well - probably better to use that as you will spend more time on developing instead of learning and fixing some edge cases when you start with a completely new technology for you.

So that's my personal opinion on it. In. short, if Stimulus and Turbo is enough for you - great, definitely go with it. If not - look at something more serious and focused on client-side rendering like Vue/React/Angular.

I hope that helps!

Cheers!

thanks you always come for the precious answers @Victor , so what do I do? Am I waiting for a reactJs + Symfony video course? ;)

Hey @pasquale_pellicani ,

Haha, we're mostly leaning towards VueJS instead of ReactJS, and we do have some screencasts about it here:

• https://symfonycasts.com/screencast/vue
• https://symfonycasts.com/screencast/vue2

We will definitely want to record more Vue-related content but I don't know when it might be released, we're busy with other good topics lately.

About ReactJS, we worked with it before, and even have a course: https://symfonycasts.com/screencast/reactjs - but then we re-wrote that part of the system with Stimulus instead. and it works great in our specific case :)

Cheers!

So, why would one choose Vue or React or stimulus? What do you think the choice is based on?
Is this the most recent guide on the stimulus/turbo topic? Or are there more recent ones?
thanks

Hey @pasquale_pellicani ,

That https://symfonycasts.com/screencast/last-stack course is the latest indeed, but it includes more topics besides Stimulus & Turbo. If you're looking for a Stimulus and Turbo course in more details, I would recommend you to watch this topic-specific courses:

• https://symfonycasts.com/screencast/stimulus
• https://symfonycasts.com/screencast/turbo

Vue or React or stimulus?

Well, first of all, Stimulus is not the same as Vue/React, so technically the difference is the same I mentioned above. If you're looking for client-side UI rendering - take a look at Vue/React. If you're OK with rendering UI server-side - Stimulus might be enough for you, it will help you dynamically inject. already server-side rendered templates into the page via AJAX requests.

So if simplify that to "Vue or React"? Well, simply, a matter of taste mostly. Something gets more hipster with a new release, etc. Sometimes people start working with something and so are already familiar with the technology and it makes sense to continue working with it while it's doing the job for you. On the more technical level and limitations - you probably first should get familiar with both technologies so that you could make some conclusions yourself.

I hope that helps!

Cheers!

Hey Mahmut,

Are you following this course on your private project you did you download the course code and started from the start/ directory? It feels like you're on a private project. Please, download the course code and look at the base.html.twig - that contains some blocks, e.g.:

        {% block stylesheets %}
            // ...
        {% endblock %}
        
        {% block javascripts %}
            // ...
        {% endblock %}

That are required for Stimulus to work, as they integrate Stimulus code into your project.

Cheers!

thank you.I noticed it and after adding block javascript, it worked.

Hey Mahmut,

Great, thanks for confirming javascript block helped!

Cheers!