Allow the WebIDL parser to accept files without a top-level interface, and have the exposed-interface generator skip those modules. With that in place, register support IDLs through libweb_js_bindings() as well, including generated CSS IDLs from the build directory, and remove the separate support-idl plumbing. This is enabled now that the IDL generator rules have been simplified so that every IDL file produces a corresponding header and cpp file. |
||
|---|---|---|
| .. | ||
| EditorConfiguration | ||
| HumanInterfaceGuidelines | ||
| Images | ||
| AddNewIDLFile.md | ||
| AdvancedBuildInstructions.md | ||
| BrowsingContextsAndNavigables.md | ||
| BuildInstructionsLadybird.md | ||
| BuildProfilingInstructions.md | ||
| CodingStyle.md | ||
| CSSGeneratedFiles.md | ||
| CSSProperties.md | ||
| DevTools.md | ||
| EventLoop.md | ||
| FAQ.md | ||
| GettingStartedContributing.md | ||
| GtkFrontend.md | ||
| LibWebFromLoadingToPainting.md | ||
| LibWebPatterns.md | ||
| Patterns.md | ||
| Porting.md | ||
| ProcessArchitecture.md | ||
| README.md | ||
| RequestServerWireLogging.md | ||
| SmartPointers.md | ||
| StringFormatting.md | ||
| Testing.md | ||
| Troubleshooting.md | ||
Ladybird Documentation
Ladybird development moves quickly, so some of these might be out of date. Please let us know if something here is wrong, or submit a PR with any additions or corrections! If you have any questions that are not answered here or in the FAQ, you are welcome to ask on Discord.
Building and Running
Configuring Editors
Development
- How to Contribute
- Coding Style
- Common Patterns
- Guidelines for Text in UI
- EventLoop
- Smart Pointers
- String Formatting