Add the instawow Mac GUI to the list #17
Conversation
layday
force-pushed
the
add-instawow-gui
branch
from
f6f4e49
to
6fbe3ca
Compare
|
@torkus just in case you missed these. |
|
hi, yes, I've seen the activity, I'm planning on dealing with it all this weekend. regarding two entries for instawow, it's not going to happen. I'm happy to add 'GUI*' (with an os-specific caveat, if that's what this is). |
|
How would one be able to tell that there is both a CLI and a GUI? I'm also not sure why a caveat on the GUI is required - that's not there for all the other GUIs? |
Not through the list. In this case, a GUI is better than a TUI, which is better than a CLI. If you have a GUI, I won't mention the fact you also have a TUI or CLI. Of course, if you'd prefer to stick with CLI and not mention you have a GUI I can accommodate that as well.
I hadn't properly looked at your change yet, I was under the impression the GUI was only available on certain operating systems. |
That does pose a problem because the CLI is available for all 3 OSes and the GUI is only available for macOS. This is one reason why I split it up - the other being that filtering wouldn't work with a UI value of 'GUI/CLI' without changes to the code - not because I want to lend more visibility to instawow. I'm not sure if a GUI is necessarily better than a CLI either - the instawow CLI is definitely more capable and more robust than the GUI. I would say that CLIs and GUIs cater to difference audiences (or different moods) and I wouldn't want to toss either one out. But it is your list so I leave it to you to decide. |
|
I've added instawow as |
|
Alright, thanks for getting this in. |
|
Well, it looks like it's filtered out both when you filter by CLI and when you filter by GUI, so uh. The asterisk gives the impression that the GUI is deficient as compared to the other GUIs on the list; and the footnote does not mention that it's there because OS support differs between the CLI and GUI. Maybe we should just revert this and instawow can live out the rest of its inanimate life as a CLI. |
This is correct behaviour, the list isn't capturing multiple user interfaces, just the best one. When you select "GUI" you are saying "just GUIs, no exceptions".
it is, it comes with burdened with caveats. In this case, the GUI only works on some operating systems.
I'll revert it for you. |
|
done, it should refresh in a minute or two |
If instawow did not have a CLI it would not have an asterisk. The caveat only begins to makes sense if you have prior knowledge of the fact that instawow has a CLI and that is why the UI and OS values are inconsistent with each other. Otherwise it is nonsensical.
Thank you :) |
|
An alternative would be to keep the GUI un-caveated and mark Windows and Linux with an asterisk since the GUI can be built on those two OSs - it's just not something I've pursued. But I think we've probably spent enough time on this one. |
|
This frustrates me a little, though I shouldn't let it frustrate me, because the majority of my traffic comes from this list. (Perhaps I should just stop looking at traffic statistics.) But I still don't fully understand why the GUI itself was caveated rather than the OSs. |
All caveats are described at the bottom of the list. The OS caveat reads:
I don't think that requires further explanation. The GUI was caveated because "it has a GUI, but it doesn't work everywhere". Your options are:
I'm not trying to be mean or punish you or instawow here, I think your work is great, but this list I maintain is deliberately uncomplicated and in the small spaces where confusion may arise I try to offer a simple explanation.
This list has [zero presence on Google](https://www.google.com/search?hl=en&q=wow addon managers), so traffic is probably more like: reddit -> list -> instawow I deleted my reddit account so I won't be there to market strongbox or the list any more. I'm looking at doing some basic SEO and Google-optimisation of the page to see if I can improve it's rankings. If you have some ideas I'd love to hear them. |
I'm probably not making myself clear. What I don't understand was why the GUI column was caveated. What I'm asking is why it was presented like this: Instead of like this: Or like this: What is special about this GUI that it requires the UI column to be caveated? |
|
does your GUI work on Linux, Mac and Windows? |
|
It works on Mac natively. It does not work on Linux unless it's compiled from source. There is no support for Windows (unless one would be willing to go in the source code and change some paths). |
|
so ... what is difficult to understand here? You have a GUI but it doesn't work everywhere. You have seamless installation across all platforms except the GUI is busted in 2/3 of them. I'm not going to contort the list and it's definitions to fit instawow. |
|
Well, I'm not asking you to do that. I thought you only wanted to capture the GUI in the list, in which case you would ignore platform support for the CLI. That is what confused me. |
|
Imagine this scenario: random user arrives at the list and sees an addon manager for windows that purports to have all these features including a GUI (which is normal in their world, anything else is strange). They click it, and arrive at a Github page rather than a regular website, but whatever, they're curious and haven't committed yet. They finally figure out how to download the bastard (releases? and then which release do I need? is it 386 or x64? source code? tar gzip or zip?), get it open and double click the executable, click through the windows alert about allowing the program to make changes to their system ... and are presented with a CLI? CLI's are cool, I guess, a little retro, but retro is back again. But I thought it had a GUI? It says right there in the list it has a GUI. Did the list lie to me? No, it was 'technically correct', it says the UI isn't supported across all platforms. Eh. What does this next manager do? And while we're vacillating about a fucking asterisk, https://github.com/casperstorm/ajour is eating our lunch ;) 20 new stars since I looked on Friday. He might finally achieve 'perfect addon manager' status... |
That's why I asked why platform support (e.g. Windows) wasn't caveated or set to 'no' instead of the UI ;P But yes, I see your point.
It really seems to have taken off on Reddit - I wonder what the secret formula is. Maybe I'm just not very likeable! |
GUIs in the Rust world are a bit of a novelty as well. There are a few efforts around at the moment but nothing that provides a native look and feel, so I'm guessing he might have some stars coming from Rust people rather than WoW people, just like I have some interest coming from Clojure people. |
|
Well, it's taken me the better part of the week but the GUI now works on Linux (not statically built, so it's only really guaranteed to work on Debian and Ubuntu, although it should also work on Arch) and Windows (in portable format) out of the box. |
|
congratulations - would you like me to test it for you as well? I'll update the list this weekend. |
Thanks. If you could, I’d be grateful. |
|
That's a really nice gui, well done. |
|
list is updated, congrats on hitting 'perfect' status 🥇 |
|
Thanks and thanks for trying it out - appreciate it! |
I added it as a separate entry because compatibility
is different and I don't think filtering would work if the
UI field was 'CLI/GUI'.