Create new repository for the Rust Qt Bindings Generator. Ref T6922
Description
Description
Details
Details
- Committed
bcooksley Sep 5 2017, 8:03 AM - Parents
- R247:d1147a18db2b: Add new project rust_qt_binding_generator
- Branches
- Unknown
- Tags
- Tasks
- Restricted Maniphest Task
Comment Actions
The project has an icon in the repo: demo/rust_qt_binding_generator.svg. Can that be reference in the metadata here? I noticed all the icon fields that are not null are just a name. How does that work?
Comment Actions
This field to my knowledge isn't used anywhere.
The field was intended to refer to the XDG icon name for an application or library, but it never went anywhere.
Comment Actions
I noticed not all parts of the README.md are rendered. Embedded HTML and an image ![]().
Where can I find the documentation on allowed features for the README.md?
Comment Actions
Phabricator's documentation is located at https://secure.phabricator.com/book/phabricator/article/remarkup/
Comment Actions
I think that documentation is writing comments. Not sure it applies to rendered files from the repo.
The extension .md should trigger rendering as Markdown, I'd hope.
I hope to recreate as nice a rendering as the project page has on GitHub: https://github.com/KDE/rust-qt-binding-generator
Comment Actions
To my knowledge Phabricator uses only a single rendering engine, which is a customised version of Remarkup.
Please see https://secure.phabricator.com/T5698 for additional explanation on their rationale behind it.
To my knowledge you can't currently reference images in the same repository.
Comment Actions
Ok. so fundamentally different rendering.
So now README.md gets rendered in three different ways:
https://github.com/KDE/rust-qt-binding-generator
https://cgit.kde.org/rust-qt-binding-generator.git/about/
https://phabricator.kde.org/source/rust-qt-binding-generator/
I'll see how to deal with that.