Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add "Keyboard Shortcuts" and "About Themix" items into the primary menu #186

Closed
nana-4 opened this issue Dec 23, 2018 · 23 comments
Closed
Labels

Comments

@nana-4
Copy link
Member

nana-4 commented Dec 23, 2018

No description provided.

actionless added a commit that referenced this issue Dec 27, 2018
@actionless
Copy link
Member

added "Keyboard Shortcuts"

@actionless
Copy link
Member

could you please provide a mockup for the "About Themix" window?

@nana-4
Copy link
Member Author

nana-4 commented Jan 6, 2019

How about simply imitating Nautilus, etc.? Most modern GNOME/GTK apps have this pattern.

image
image

@actionless
Copy link
Member

i was more wondering about typography for all the plugins, their versions and authors

@nana-4
Copy link
Member Author

nana-4 commented Jan 8, 2019

OK. In the GNOME's latest mockup of about-dialogs, there is the "Legal" tab. Maybe we can imitate that.

How about renaming "Legal" to "Plugins" and adding version info next to the name of each plugin?

@actionless
Copy link
Member

yes, that's looking similar to what i had on my mind 👍

@actionless
Copy link
Member

btw good idea with the buttons

also speaking of translations, mb later i can setup integration with transifex so users could easier edit .po files

@actionless
Copy link
Member

what about adding third menu item "Tutorial" and show it on the first run?

@nana-4
Copy link
Member Author

nana-4 commented Jan 16, 2019

third menu item "Tutorial"

I think such information should be in "Help" of the primary menu, as per the GNOME's Initiative.

show it on the first run

It would be fine, but I don't know what kind of design/info it should be.

@actionless
Copy link
Member

yeah, Help sounds like a more general name than Tutorial

but I don't know what kind of design/info it should be.

i myself don't know what could be not clear in the app so it require some help, but i guess to make just few buttons:

  • how to create and export theme
  • how to import and export base16
  • how to create themes from images
    etc

and when clicking on each, it either opens wiki/md from the repo, in a way like this doc https://gist.github.com/actionless/f9ad9e5ab9eac414dac8a3392beb3ad5

or just shows some help message inline

idk

@nana-4
Copy link
Member Author

nana-4 commented Jan 17, 2019

+1 for using wiki.

For reference, gnome-builder has "Help" as a link to the web document.
Just like Builder, in Oomox, I think it would be nice to have "Help" as a link to the top page of wiki.

Also, IMHO, if Oomox has a user-friendly UI even for beginners (like this), I feel there is no need to show a helper dialog even on the first run.

@actionless
Copy link
Member

actionless commented Jan 17, 2019

i don't like idea of straightly opening web page -- i think it could alienate from reading the help in a way "oh instead of doing real help they just put a link to 100 pages of wiki, so i'll just close it instead of reading', so i thought what displaying links to some particular help topics could be useful right in the help window

or, mb, more precise names for such window could be "Getting started…"

@nana-4
Copy link
Member Author

nana-4 commented Jan 18, 2019

"oh instead of doing real help they just put a link to 100 pages of wiki, so i'll just close it instead of reading'

Even though I pointed to Builder as an example, but in Themix, I think having only several sub-pages on top page of wiki is enough.

Anyway I share my idea of a startup/help dialog something like this:

                    Welcome to Themix                                <-- title

  Are you new to Themix? Online documentation is available!

  [ How to create and export theme ]                                 <-- link button
  [ How to import and export base16 ]                                <-- link button
  [ How to create themes from images ]                               <-- link button

  [x] Don't show show this dialog at startup.                        <-- checkbox

----------------------------------------------------------
                            OK                                       <-- button

@actionless
Copy link
Member

yes, exactly as i see it

@actionless
Copy link
Member

hi, @nana-4, have you got any luck with the mascot? i thought it would be cool to use it for "About" window

@nana-4
Copy link
Member Author

nana-4 commented Sep 26, 2020

Sorry, I'm not an illustrator, so I don't have an ability to create a nice looking mascot. I can only create a terrible looking mascot :P I’m afraid having a bad looking mascot can give users a bad impression...

Besides, I'm still not a fan of the idea of having a mascot, to be honest -- the concept of "mascot for application" reminds me of ancient applications... I think having a simple character/mascot in the app icon, like Firefox and Xfce, is not too bad, but I don't have a good idea to make it look decent at the moment.

i thought it would be cool to use it for "About" window

Most GTK apps show their own icon in the About dialog. Shouldn't we follow that for now?

@actionless
Copy link
Member

but we'll loose the possibility to be in SuperTuxCart at some point!

@nana-4
Copy link
Member Author

nana-4 commented Sep 27, 2020

lol. Then the mascot needs a body as well as a head ;)

By the way, how about such a "colorful robot" instead of an "alien"?

image

The robot implies it's recolorable, transformable and replicable...

@actionless
Copy link
Member

actionless commented Sep 27, 2020

that actually nice, would be very hard for you now to pretend not having a drawing ability :)

what about trying suiseiseki-like colors for the eyes? or that might look as a reference to 3d-glasses? :(

re: body

in worst case we could just mount a head on top of a square-wheel bicycle

@actionless
Copy link
Member

actionless commented Sep 27, 2020

i've actually right now realized what this concept of robot could be very organically variated for different contexts:

for example:
by adding star-like glasses it could be used as a headline for Pop Art theme section
by adding a red hat on robot's head - as a headline for Gnome section
by pixelating and changing rainbow into CGA - as a headline image for Retro section

and etc

@nana-4
Copy link
Member Author

nana-4 commented Sep 28, 2020

that actually nice, would be very hard for you now to pretend not having a drawing ability :)

I found it quite difficult for me to draw the alien. But a robot is much easier to draw even with my poor skills :)

what about trying suiseiseki-like colors for the eyes?

IMO, having different colored eyes on colorful skin could be information overload (or it would look like a "broken" robot).

About adding different variations of robot to each section: If this were a game app, I'd have no objection. But I'm not sure if it works well with this app -- isn't it too pop as a utility tool?

@actionless
Copy link
Member

those were just usage examples of variability, but generally it could any other example of variable logo usages -- like matching it to release codename, or using on a website sections, etc. doesn't mean what any of those gonna happen but just nice to be able to have that variability potential there :)

@actionless
Copy link
Member

finally implemented both Hotkeys and About windows

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants