6 ms·
Wait, what? What do they need it for?
by KptMarchewa 5y ago
Wait, what? What do they need it for?
- Andrew_nenakhov 5y agoTo a boy with a hammer everything looks like a nail, I guess.
- planb 5y agoInteractive Tutorials? https://developer.apple.com/documentation/docc/building-an-interactive-tutorial https://developer.apple.com/documentation/docc/building-an-i... I found that via web search, but I couldn't find a demo anywhere online...
- pornel 5y agoThe tutorials are written manually in a SwiftUI-like script. It's a totally different thing from the docs auto-generator.
- planb 5y agoThanks for clarifying, but are you sure? On the very page I mentioned, there's a link at the bottom: "Distributing Documentation to External Developers" and on that page it says: "Share your documentation directly with Xcode users or host it on a web server." Sounds to me like you build that documentation using the SwiftUI-like DSL, but it is distributed in the DocC package.
- deleted 5y ago[deleted]
- coldtea 5y agoSearch? Interaction? Collapsable sections? It's 2021.
- Klonoar 5y agoNone of these require a framework.
- coldtea 5y agoWe don't use frameworks because they're required, we use them because they make dev lives easier and provide some common ready-made structure and functionality. Strictly speaking, nothing ever requires a framework: after all, any framework is just code - and you could always write vanilla code to achieve the same functionality (up to re-implementing the whole code of the framework yourself from scratch).
- Klonoar 5y agoThis comment does nothing except state the obvious. ;P The parent I'm responding to listed very simple examples that in no way necessitate a framework; of course frameworks can be useful for larger scaffolding and the like. Where exactly do you think you're commenting...?
- Zababa 5y agoRust has all of them with vanilla JS. The code is clear and easy to understand, and could be reused by other people easily. Here's an example: https://doc.rust-lang.org/std/vec/struct.Vec.html https://doc.rust-lang.org/std/vec/struct.Vec.html
- ironmagma 5y agoThere is no way anyone in their right mind would call main.js[1] easy to understand. It's basically complete chaos. Guillaume is making a good effort to clean up this inherited code slowly, but the interactions are still kind of broken and will be until this code is rewritten in a sane pattern such as MVU. FWIW, I have been working towards this for the past year. [1] https://github.com/rust-lang/rust/blob/master/src/librustdoc/html/static/main.js https://github.com/rust-lang/rust/blob/master/src/librustdoc...
- easrng 5y agoLooks easy to understand to me, it would be better if it was set up as modules instead of a single file full of IIFEs but it looks pretty good as is.
- Zababa 5y agoYou're right, as a whole it's not trivial. I remember reading the search part and found it not particularly hard, but I missed the big picture. Thank you for your work!
- coldtea 5y ago>Rust has all of them with vanilla JS. Which is neither here, nor there. Since JS is required for those features (in the absense of a dynamic server backend), who cares whether it's bundled Vue.js or some hand-rolled vanilla JS? I'm sure some care. I'm not sure many care, and I'm even less sure that they have any valid reason to care besides a knee-jerk "bloat" reaction.
- akiselev 5y agoThere is a quantitative difference between a folder with some HTML + other assets and a project that requires a specific v8 runtime wrapper and its own build pipeline to generate the aforementioned artifacts. My grandmother knows how to (and does) use the former. The latter guarantees I'll always have a job.
- est31 5y agocollapsible sections are possible using css only, or using the details tag (not even css needed). As for search, you don't need a framework for that.