Tagging sample sections.

master
Thomas Hintz 4 years ago
parent 08d5fdfbee
commit 5808343b61

@ -19,7 +19,7 @@
#+options: toc:nil tags:nil #+options: toc:nil tags:nil
* Preface :frontmatter: * Preface :frontmatter: :sample:
:PROPERTIES: :PROPERTIES:
:EXPORT_FILE_NAME: manuscript/preface.markua :EXPORT_FILE_NAME: manuscript/preface.markua
:END: :END:
@ -52,10 +52,9 @@ you better understand how it works, and even more critically, it will
allow you to play with it and test how the algorithms work with your allow you to play with it and test how the algorithms work with your
own examples. own examples.
Even if you don't write out the code yourself and,instead, read through this Even if you don't write out the code yourself and, instead, read
book more like a novel, I believe the through this book more like a novel, I believe the fundamentals will
fundamentals will still stick with you and provide value in your still stick with you and provide value in your React programs-to-come.
React programs-to-come.
I'm very excited to take you on this journey with me and, so, now it's time I'm very excited to take you on this journey with me and, so, now it's time
to learn what lies at the very foundation of React. to learn what lies at the very foundation of React.
@ -346,7 +345,7 @@ of ~elements~ (surprise).
That's it. Now we have everything we need to actually begin the That's it. Now we have everything we need to actually begin the
process of rendering our tree to the DOM! process of rendering our tree to the DOM!
* Render: Putting Elements on the Screen * Render: Putting Elements on the Screen :sample:
:PROPERTIES: :PROPERTIES:
:EXPORT_FILE_NAME: manuscript/render.markua :EXPORT_FILE_NAME: manuscript/render.markua
:END: :END:
@ -742,7 +741,7 @@ process works as a whole. At this point, bottlenecks are much more
likely to occur from the underlying algorithms and not from the Fibers likely to occur from the underlying algorithms and not from the Fibers
specific details. specific details.
* Putting it all together * Putting it all together :sample:
:PROPERTIES: :PROPERTIES:
:EXPORT_FILE_NAME: manuscript/putting-it-all-together.markua :EXPORT_FILE_NAME: manuscript/putting-it-all-together.markua
:END: :END:

@ -1,4 +1,3 @@
frontmatter.txt
preface.markua preface.markua
acknowledgments.markua acknowledgments.markua
mainmatter.txt mainmatter.txt

@ -1,4 +1,5 @@
# Preface {sample: "true"}
# Preface :frontmatter:
Welcome to *Foundations of High-Performance React Applications* where we build our own simplified version of React. Well use our React to gain an understanding of the real React and how to build high-performance applications with it. Welcome to *Foundations of High-Performance React Applications* where we build our own simplified version of React. Well use our React to gain an understanding of the real React and how to build high-performance applications with it.

@ -1,3 +1,4 @@
{sample: "true"}
# Putting it all together # Putting it all together
Now that we've explored how React renders your components, it's time to finally create some components and use them! Now that we've explored how React renders your components, it's time to finally create some components and use them!

@ -1,3 +1,4 @@
{sample: "true"}
# Render: Putting Elements on the Screen # Render: Putting Elements on the Screen
There are now only two major puzzles remaining in our quest for our own React. The next piece is `render`. How do we go from our JSM tree of nodes to actually displaying something on screen? We do this by exploring the `render` method. There are now only two major puzzles remaining in our quest for our own React. The next piece is `render`. How do we go from our JSM tree of nodes to actually displaying something on screen? We do this by exploring the `render` method.

Loading…
Cancel
Save