You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The input field is a little darker, which in my opinion, does not look very good.
In general it looks very empty, maybe add also some infos, like on nc app?
Maybe also remove "talk" in "nextcloud talk server" as it can lead to the impression that there is a special talk server instead of the regular nextcloud server (of course with talk app enabled) @jancborchardt
The text was updated successfully, but these errors were encountered:
a) I need to check what's up with the logo
b) title was already changed to "Nextcloud server address"
c) There will be a proceed button under this all
d) IHMO, the input box looks nice - it's TextField Box according to Material guidelines
Can confirm the weird logo. Looks like lossy SVG compression
The dark background of the input box is unnecessary, the white line already is enough.
The arrow is good as a confirm button. Either way we do it, it should be consistent across both apps please.
We can put the same notice we have in the Files app there too. @jospoortvliet maybe a filter on the providers page as to which provider has the Talk app enabled?
Also – it would be really nice if we would not have this issue at all and just Take server address & credentials from main Nextcloud app #14 ;)
As said, we designed the Files app view for a reason like that and I'm not fond of going through the same design discussion process again when we already know how to do it. ;)
The input field is a little darker, which in my opinion, does not look very good.
In general it looks very empty, maybe add also some infos, like on nc app?
Maybe also remove "talk" in "nextcloud talk server" as it can lead to the impression that there is a special talk server instead of the regular nextcloud server (of course with talk app enabled)
@jancborchardt
The text was updated successfully, but these errors were encountered: