Hey Ryan! Could you tell me which library do you use for syntax highlighting in this tutorial, if it is not a commercial secret of course? :) I like feature to expand whole script if I need, it's a very cool! Does it your custom solution or you use some third-party library for it?
Ah, glad you like it! The expanding code-block is something internal - the projects are built with a tool that manages a "diff" for each step (https://github.com/knpunive... and those are used to fuel the code blocks later. No more "out of date" code blocks :). Keep watch - when that's ready, parts of it will get released to help make collaboration on the code blocks possible.
But the syntax highlighting itself is totally open source :). Behind the scenes. Highlight.js is used to transform the code blocks into markup. On the frontend, the "Tomorrow Night" theme from highlight.js is used (it's one of the selections on the demo): https://highlightjs.org/sta....
Hope that helps :). Eventually I hope the "expanding" can be available to use on other sites (e.g. blogs) because it's nice to be able to see the whole context!
Hello, I know that this tutorial is quite old but I just like to point out that I guess that there has been some changes to monolog since then...
I believe that currently monolog wont spit the stuff out to stderr if there is no handler attached so the script wont actually "roar" at all :( So I guess you have to attach a StreamHandler('php://stderr') right from the start.
I wonder how the Symfony container thingy has changed from version 2 until now - heading on to the next chapter ;)
Ah, thanks for the note about that - I’m sure that’s true!
> I wonder how the Symfony container thingy has changed from version 2 until now - heading on to the next chapter ;)
The answer is... a LOT has changed. But also... not a lot. If you look at many of the files we open in this tutorial, they now look much different. The container also now has autowiring, autoconfigure, auto registration, service locators and private services by default. On the other hand, all the philosophies that we go through remain exactly the same: the idea of the ContainerBuilder, service definitions, compiler passes and the dumping of the container to a cached PHP file are all still totally relevant.
We do have it on our list to update this tutorial some time - it’s a great topic, and plenty has changed.
Cheers!
Please, log in to vote for this comment
|
Share Comment
"Houston: no signs of life" Start the conversation!
7 Comments
Hey Ryan!
Could you tell me which library do you use for syntax highlighting in this tutorial, if it is not a commercial secret of course? :)
I like feature to expand whole script if I need, it's a very cool! Does it your custom solution or you use some third-party library for it?
Wow, looks like you wrote this before becoming the part of the team. :)
Hey Serge,
Haha, you're right! It was about 3 years ago, wow... Nice catch btw! ;)
Cheers!
Ah, glad you like it! The expanding code-block is something internal - the projects are built with a tool that manages a "diff" for each step (https://github.com/knpunive... and those are used to fuel the code blocks later. No more "out of date" code blocks :). Keep watch - when that's ready, parts of it will get released to help make collaboration on the code blocks possible.
But the syntax highlighting itself is totally open source :). Behind the scenes. Highlight.js is used to transform the code blocks into markup. On the frontend, the "Tomorrow Night" theme from highlight.js is used (it's one of the selections on the demo): https://highlightjs.org/sta....
Hope that helps :). Eventually I hope the "expanding" can be available to use on other sites (e.g. blogs) because it's nice to be able to see the whole context!
Yes, it helps, thanks! I suspect that highlight.js is used by `hljs` class wrapped each code-block, but expanding code-blocks are awesome! :)
Hello,
I know that this tutorial is quite old but I just like to point out that I guess that there has been some changes to monolog since then...
I believe that currently monolog wont spit the stuff out to stderr if there is no handler attached so the script wont actually "roar" at all :(
So I guess you have to attach a
StreamHandler('php://stderr')right from the start.I wonder how the Symfony container thingy has changed from version 2 until now - heading on to the next chapter ;)
Hey @El KuKu!
Ah, thanks for the note about that - I’m sure that’s true!
> I wonder how the Symfony container thingy has changed from version 2 until now - heading on to the next chapter ;)
The answer is... a LOT has changed. But also... not a lot. If you look at many of the files we open in this tutorial, they now look much different. The container also now has autowiring, autoconfigure, auto registration, service locators and private services by default. On the other hand, all the philosophies that we go through remain exactly the same: the idea of the ContainerBuilder, service definitions, compiler passes and the dumping of the container to a cached PHP file are all still totally relevant.
We do have it on our list to update this tutorial some time - it’s a great topic, and plenty has changed.
Cheers!
"Houston: no signs of life"
Start the conversation!