-
Notifications
You must be signed in to change notification settings - Fork 0
Parts
Every website is build out of Parts. It is important to slice the website into parts, not only to minimize redundancy, but also it is the way how the asynchronous optimization works.
All available parts can be found in R::Parts::[PartName]
if you #include "../engine/Resources.h"
There are different types of parts, and they have different behaviors.
The class StaticPart :public Part
is the most basic part. It just contains HTML code and when you use it, it just gives you its HTML. But you can put other, more complex parts inside this HTML.
You will never write your own StaticPart. Instead, they will get generated by the ProjectBuilder.
Not implemented yet
The class DataPart :public Part
does only hold dynamic data. It can't be cached by the client. Try to keep the DataParts as small as possible, to optimize loading times.
DataParts are not generated by the ProjectBuilder