Gogs: Mobile specific UI

[lommes]

... to make them fit on mobile devices.

Same goes with class img-responsive for images like on startpage

[unknwon]

Thanks for your feedback, but we have no plan for supporting mobile devices until 0.5

[EtienneBruines]

Also affects non-mobile devices that have enabled zoom (i.e.: pages showing at 110% zoom at desktop).

For instance, the "copy" button at newly created repo-clone, is not shown on the same page.

[unknwon]

@EtienneBruines thanks your info!

[bastiao]

Also, in the Issues, "New issue" and "Milestones" are not available. Tested in iPhone.

[nanoant]

@Unknwon FYI I can help you with that, if you want. As long we stick with pure Semantic UI where possible, this shouldn't be hard. See #2066

[unknwon]

@nanoant thanks for the advice, but Gogs is very rich content app, so I think simple responsive design is not going to work.

However, we need a complete different design page for mobile devices, and for sure it is going to use SUI.

[nanoant]

@Unknwon Since we don't have sidebar (which is good), which makes single column main layout, it is just a matter of properly configuring various elements to collapse properly on mobile devices. Somehow the PR of mine #2068 is example that now file list and commit list is somehow readable on mobile device, because layout no longer breaks (eg. icons breaking of the names, etc).

But I am aware there are some other places, such as top menu, where we could collapse to icon only view, removing textual labels such as "Pull request" that will no longer fit, or make it alternatively stackable.

We don't need perfect Mobile UI, but usable one, and I think we can manage it having single HTML+CSS using Stackable UI device (screen) classes.

[unknwon]

@nanoant I think we should the simple design principle of GitHub, which means we do not have to show everything as desktop version does.

[tboerger]

I really like the idea to be more mobile friendly. This view doesnt need to be officially supported yet. A more or less usable state until we have a real mobile view should be already fine.

[linquize]

What framework can be used to support mobile view?

[unknwon]

@linquize I think SUI is good enough?

[linquize]

Is it? https://github.com/SUI-Components

[unknwon]

I think point of mobile friendly is use more space for less content, does not matter the UI components.

[khromov]

Responsive layout would be great! Just looking at the current CSS, there are a few smart tweaks we could do to make it work nicely on a mobile device.

[YamiOdymel]

gogs was made by Semantic-UI, it has the built-in mobile tools.

[tboerger]

gogs was made by Semantic-UI, it has the built-in mobile tools.

Only if it's done right ;)

[YamiOdymel]

I was about to ask if there's any chances to send a pull request about this.

Sorry but why isn't it allowed?

[AddoSolutions]

I have quite an extensive UI background, if my assistance is of any value. I have done a lot with Semantic UI as well

[bkcsoft]

@AddoSolutions I at least want it more mobile-friendly :smiley: ( though I'd prefer an app honestly :trollface: ). If you decide to work on it, try as hard as you can to only do it with CSS, as fscking around with styles inline/javascript is horrible at best :unamused:

@YamiOdymel The reason is that Gogs has some inline-styles, and javascript fscking up styles. So it's not an easy task. Also MobileUI is very low priority as (like I mentioned above) a Mobile App would be preferred (when the API stabilizes I'll have a look at forking ForkHub :smiley: )

[genofire]

It should not be so difficult just add

<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />

and add on the most element with class grid or menu the class stackable.
(So it look not good on mobile, but is more useable on mobildevices-> https://github.com/genofire/gogs/commit/14fcd38a7566b5f3ee483ad6ad04ae67605214ab)

[rugk]

Any news on this?
And, @Unknwon, you still have not said why you added the "don't send pull requests" label.

[unknwon]

No, at least not until 2018.

[rugk]

And what about this :expressionless::

And, @Unknwon, you still have not said why you added the "don't send pull requests" label.

[YamiOdymel]

Because the UI is still changing, it's not stable yet.
2016/8/7 上午12:46 於 "rugk" [email protected] 寫道：

And what about this:

And, @Unknwon https://github.com/Unknwon, you still have not said why
you added the "don't send pull requests" label.

😑

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gogits/gogs/issues/144#issuecomment-238032854, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG-FrkLgaWtNPyX0gSgK7AhpMObJ2HXeks5qdLpHgaJpZM4B2tXS
.

[rugk]

Okay.

[unknwon]

It means we won't accept your PR about this, you can make it but only in your fork. It's a warning. Don't ask irrelevant questions, go forum: https://discuss.gogs.io.

[evantbyrne]

The reasoning behind not accepting PRs on this doesn't make much sense to me. Typically mobile UI dev is done alongside the desktop UI dev, or even before because elements naturally stack vertically in HTML. I would recommend considering PRs on this. There are probably a lot of people in this community willing to improve the mobile layout, including myself. I don't think it would take much to get it usable on mobile.

[vavrecan]

Its November already. Opensource is about collaboration. I was wondering, making its responsive is just a matter of putting in stackable and few easy changes. I think if the admins will not accept pull requests and does not want other people to contribute to the project (which I believe there are many great programmers who would do great contributions), we can just make fork (like lede from openwrt) voila :+1:

[tboerger]

It have been labeled that no pull requests are getting accepted... :(

[lyuwen]

I saw this issue... I wanted to post a new one because it is 3 years old. @Unknwon

[unknwon]

@lyuwen issues are valid as long as it is open no matter how old it is :smiley:

[skylarmt]

No, at least not until 2018

~$ date
Tue Jan 16 00:28:45 MST 2018

[netlander]

Arrogant git @Unknwon

[agherzan]

Any news on this?

[unknwon]

Unfortunately, no... Looking forward to use VueJS but still learning it.

[ghost]

No, at least not until 2018

its 2019 and we are still waiting

[skylarmt]

If you want a mobile interface, consider switching to Gitea, a community-run fork of Gogs. It has a mobile interface and some other features Gogs doesn't, such as a dark theme and two-factor with hardware security keys.

[BaxAndrei]

Any news on this?

[skylarmt]

I've since switched to Gitea, a fork of Gogs but it has a responsive/mobile UI, dark themes, and at least one Android app.

[ElleshaHackett]

Please support this. I'm happy to help too. This should prevent some users from moving to Gitea as well. It's 2020. That's simply requirement nowadays. Even adaptive (not fully responsive) support or showing less functionality is a start.

[unknwon]

@ElleshaHackett Mobile specific UI is where I plan to use VueJS and GraphQL but my skills on the former is still rough 😅

PS: Making Gogs responsive does not make sense to me as a content rich application.

[Schlomon]

Any news on this?

[skylarmt]

Any news on this?

My company has switched over to Gitea, a fork of Gogs that has a lot more community involvement, which has led to improvements such as a responsive UI and two-factor authentication. There's also a third-party Gitea Android app in F-Droid called GitNex.

[Schlomon]

My company has switched over to Gitea, a fork of Gogs that has a lot more community involvement, which has led to improvements such as a responsive UI and two-factor authentication. There's also a third-party Gitea Android app in F-Droid called GitNex.

Yeah I more and more feel like gitea is the only real option here.

[Prochy20]

Support 🔝🔝