Notes from day 3
* Morning discussion:
- An interesting widget to have might be a readonly multi-paragraph label that can embed children in the text and reflow
- Another interesting widget to have might be a simple multiline entry without markup
- Discussion about text view
- how do we get to css for text ?
- enforce tree structure for markup, or put tree structured css node underneath tags
- add css names to tags
- translate css properties to pango attributes
- use cases for text view: builder and gedit
- how do we get to css for text ?
- Docs
- hot-doc is getting pitched
- advantages:
- can generate from gir
- can generate multi-language docs
- can do live editing
- disadvantages
- can't do some of the other developer docs we currently have that are mallard based
- obstacles:
- needs new infrastructure for getting docs on the website
- needs a gradual transition path from where we are now
- portal issues:
- We decided to make the g_app_info_launch portal implementation a little more synch to help xdg-open
- We also decided to write very simple C versions of xdg-open and xdg-email for use in the runtime
- Build system question
- Merging the meson support is fine
- We don't want to maintain 2 build systems in the long term, but a limited coexistence is fine
- Simon says distros will be ok with git-archive generated tarballs. No tarballs would be rougher