Skip to content

chore: Pick program name (and change window title once it's been decided) #31

New issue

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

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

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gselzer
Copy link
Contributor

@gselzer gselzer commented Feb 5, 2025

@tlambert03 I'm assuming it wasn't deliberate to name the window "Mike" 😆

Lots of options here, including:

  • PyMMCore GUI (matching the repo)
  • mmgui (matching the entry point)
  • MicroManagerGUI

I actually kinda like the first one - opinions welcome (cc @tlambert03 @fdrgsp @marktsuchida)

@gselzer gselzer requested a review from tlambert03 February 5, 2025 16:29
@gselzer gselzer changed the title Change window title fix: Change window title Feb 5, 2025
Copy link

codecov bot commented Feb 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.48%. Comparing base (764f97c) to head (5bbb3a7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #31   +/-   ##
=======================================
  Coverage   84.48%   84.48%           
=======================================
  Files          17       17           
  Lines         980      980           
=======================================
  Hits          828      828           
  Misses        152      152           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fdrgsp
Copy link
Contributor

fdrgsp commented Feb 5, 2025

We can have a default name but maybe it can be nice to let the user decide how to name their microscope 😁

@tlambert03
Copy link
Member

tlambert03 commented Feb 5, 2025

it wasn't deliberate to name the window "Mike"

it was :) but just a joke (kinda 😄 ). I don't really want to want to name the actual program "something Gui". nothing in Program Files or Applications feels the need to clarify that it's a graphical user interface. It's assumed. So, we need some sort of name for this application beyond just the descriptor that this is "the" gui project that we're all working on.

I hate naming... but have been discussing it recently and the name that seems to keep winning so far is micro-pylot or some variant of that. Here's a long list of names, most junk

top contenders:

  • micro-pylot
  • mui
  • pymm

standard type names:

  • micro-pylot / MicroPylot / µPylot
  • pymm / pym / mmpy
  • pymmgui / pymmcore-gui / mmgui
  • magni-py
  • pysight
  • snapPy
  • microscoPy
  • pyfocal
  • Micros
  • Scope pilot
  • Scopy

friendly/playful names that have vague or not-so-vague references:

  • Fred
  • Mike
  • Otto
  • Mats
  • Nico

@tlambert03 tlambert03 changed the title fix: Change window title chore: Pick program name (and change window title once it's been decided) Feb 5, 2025
@gselzer
Copy link
Contributor Author

gselzer commented Feb 5, 2025

it was :) but just a joke.

You know, I really wouldn't mind "Mike" if there wasn't the name clash with https://github.com/jimporter/mike

the name that seems to keep winning so far is micro-pylot or some variant of that.

Yeah, that's not too bad. "pylot" really hurts my brain, but there's no objective reason it's bad - I probably just have to get used to it. I dislike names that you can't type on a/my keyboard, so my preference would be to avoid µ in the name.

  • pymm / pym / mmpy

This might even be a good thing, but when I see these I think
ant-man

As an aside, a short option could be "mui" - captures both "mu" (micro) and "ui" - although I find pronouncing it "mewy" awkward, and I know you're not a fan of (g)ui in names...

@tlambert03
Copy link
Member

You know, I really wouldn't mind "Mike" if there wasn't the name clash with https://github.com/jimporter/mike

I know, honestly it's not bad :)

for this particular thing, I'm not as concerned with pypi clashes. we will probably publish to pypi under some name, but given that this is much more application than library, we are more likely to guide people to the bundled versions: https://nightly.link/pymmcore-plus/pymmcore-gui/workflows/bundle/main

"pylot" really hurts my brain

I think i know what you mean actually.

mui

I do like that! adding it to the list

@gselzer
Copy link
Contributor Author

gselzer commented Feb 5, 2025

mui

I do like that! adding it to the list

Notably, mui and micro-pylot are not taken on pypi, but pymm/pym/Pylot are

@tlambert03
Copy link
Member

A downside of mui is that”material ui” sort of dominates that acronym. Would be hard to google

@marktsuchida
Copy link

Back in MM 1.4, the MMStudio window title was the config file name:
https://micro-manager.org/Micro-Manager_User's_Guide#the-micro-manager-main-window
(In case you want ideas for ways to defer the name pick while having something to put in the window title. I'd probably prefer the basename rather than the full path, though.)

I agree with not having the word GUI in the name, but don't have any other good ideas. "Micro-Manager 3"? (Likely premature for some time, of course.)

@tlambert03
Copy link
Member

Micro-Manager 3

😂 also feels a bit presumptuous

window title was the config file name:

good point, we can indeed distinguish between the window title and the program name. but of course, for various application reasons (native program awareness) we also need to pick a program name

@tlambert03
Copy link
Member

Micropylot is out because https://www.nature.com/articles/nmeth.1558

Other thoughts for recursive acronyms (cause everyone loves those)

GAMMa - GAMMa augments micro-manager
Timm - Timm is [more] micro manager
SPAM - spam pythonically augments mm

Other random short names

Luma

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

Successfully merging this pull request may close these issues.

4 participants