yellowled wrote:There will be a transcript in English, don't worry.
Not sure what to transcribe here. Let's see what we discussed …
– I gave a short introduction to what we changed since getting feedback in a closed alpha test.
– We discussed the open UI/UX issues that I had. That included exchanging some icons used, keeping the colors used (at least for the time being) and switching to an off-canvas nav on small screens instead of the mobile dropdown.
– Discussion: what needs to be done before this can be “shipped” as a beta – optimization of backend CSS/JS, testing in IE and mobile browsers, no-js fallback etc.
– Discussion about the default plugin selection, but without actually discussing which plugin could be removed or added (this seems a better discussion for the forums).
– I still want to adapt the backend sections created by additional plugins. Garvin will provide an example as to how to use a version detection to emit different markup for 1.7.x and older/2.0 backends.
– We don't want to set a precise timeframe for the beta phase. End of march might be realistic depending on the open issues and required testing. Adapting plugins will not be part of the beta phase. “Beta” means people can test 2.0 in a non-productive environment.
– Timbalu had a list of smaller issues, potential issues and concerns. I can't really list all of them since some of them are out of my area of expertise, but I think we were able to find solutions or ways to solve them.
(This is about the time Garvin had to leave. I'm not sure if what we discussed after that is still relevant. I'll list the important stuff anyway.)
– We might want to make the new core dashboard extendable so that other plugins(?) can add functionality to the core dashboard. (Doesn't have to be implemented for beta.)
– Already added to 2.0 by Timbalu: a new function (in the Maintenance section) to purge templates_c.
– Some minor UI/UX issues which I have (kind of) fixed already, i.e. zebra striping, the info buttons.
– Lengthy debate about details/summary (used for categories) in Chrome vs Firefox. For everyone involved: it is
actually a bug in Firefox
– mind the reported date of the bug …
– We also revisited the discussion as to why the Karma plugin does not emit anything in the backend (which we also discussed in the first leg of the dev talk). No solution though, since nobody really uses it.
… and then we called it a day.