[FEATURE REQUEST] List all the keyboard shortcuts

[trebmuh]

I've just hit a frustration when trying to improve the translation.

There are a bunch of shortcuts which are "hardcoded" (ie: non-modifiable, such as on some menu's items) and some of those can conflict with the accelerators which are defined in regards to the & strings in the language translation files, which mean that they are/can_be differents for each languages.

It's currently a bit hard to find out which one will be conflicting with another one without trying those live. Then (as a translator who would like to improve consistency around keyboard shortcuts), it basically means that one have to compile (~30mins on my core2duo 4G RAM dev computer), try it, see there is a conflict, modify the translation file, recompile (another 30 mins), and again...

You get the (horribly frustrating) picture.

Would that be possible to have a display of the mapped shortcuts somewhere on the menu? (just under the "manual" item in the info menu would make sense I guess)

Note that I'm not asking for something user-customizable (for now at least), but only a display which would help translators a lot (and users too I bet).

Best thing would be to have 3 columns:

• one for the action description
• one for the "hardcoded" shortcuts
• one for the "coming from the translation" shortcuts
• bonus: one for the place(s) where the item is found (menu, window, ...)

[jeremyz]

Hey,
first thing, if you are on linux, install ccache,
then use ./build.sh mm
compilation will then be .. instant ( after the first run )
second, I will try to come with a quick dirty shell script to help you,
third, if you're not on linux, yeah, something is needed ;)

[heit0r]

I was wondering if there could be something like this since i had to adapt some codes like this on the translator.

I'm running manjaro linux on a i3 4gb of ram notebook.

I think i know to run a script and some commands in terminal, but i don't know how to download the sourcecode, never done this. There is any manual about this?
Thanks!

[heit0r]

*on the translation i made.

[elpescado]

one have to compile (~30mins on my core2duo 4G RAM dev computer), try it, see there is a conflict, modify the translation file, recompile (another 30 mins), and again...

How are you building Hydrogen? Rebuild shouldn't take that long, it should recompile only files changed since last build.

Anyway, full build shouldn't take half an hour. My ancient MacBook (also Core 2 Duo, albeit with 8 GB of RAM and SSD drive) manages to build Hydrogen in 8 minutes.

[trebmuh]

How are you building Hydrogen? Rebuild shouldn't take that long, it should recompile only files changed since last build.

I'm usually rebuilding a deb package for other users as well which obviously takes a bit more that what a compile is doing. I might rethink my translation workflow that being said.

@Heitor : please look at the wiki, there are a lot of information about building Hydrogen. After that, feel free to open a new thread if you're missing something to get it build.

[heit0r]

Sure, i'm going to do this! I'll probably answer here ASAP

[trebmuh]

@jeremyz toc toc, any news about this potential script?

[elpescado]

Here's how I work with Hydrogen.

# Clone repository
git clone git@github.com:hydrogen-music/hydrogen.git
cd hydrogen

# Create build directory and 
mkdir build
cd build
cmake ..
make -j 2

It takes less than 10 minutes.After that I have complete build. I make some changes, run make again, and it builds only those bits that were changed:

make -j 2

Actually, I use ninja instead of make:

mkdir build
cd build
cmake .. -GNinja
ninja

[trebmuh]

Thanks. I now that I can do that this way. Still, a file or/and a summary display like I've asked originally would be a big time saver if someone would be able to provide it. If not, I'll keep working with a bunch of rebuilds.

[jeremyz]

Hi,
I don't have much time these days ... install ack on your system (a colorful version of grep).
then run these
ack '&' src/ --ignore-file=match:about_dialog.ui
ack QKeySequence src/gui/src/PlaylistEditor/PlaylistDialog.cpp src/gui/src/MainForm.cpp
you'll have a nice enough overview (I hope) of the shortcuts.