Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Toni Ruottu
    @cyberixae
    also, I feel it is solving a problem that does not exist
    and if that problem existed I think there would likely be some better solution
    but that solution would be different depending on the problem
    Tomi Jylhä-Ollila
    @kagu
    I kind of feel the same way, to be honest, now that I've written the code :-P
    (whoa, not the kind of emoticon I expected)
    I think I'll make the channel defaults global this weekend, as it affects the file format and should be an easy thing to change
    Tomi Jylhä-Ollila
    @kagu
    Hmm, we are running out of space in the topmost toolbar of the main window
    Toni Ruottu
    @cyberixae
    Can you post a screenshot of the current situation?
    Toni Ruottu
    @cyberixae
    Some possible solutions:
    1
    1 turn some text into icons
    2 split top menu into two rows
    3 hide some menu items behind a burger/hotdog button
    At first glance 2 seems like a good option
    We have plenty of vertical space available
    And maybe the menu items can be sensibly divided into two groups
    This kind of categorization might even improve the user experience
    Tomi Jylhä-Ollila
    @kagu
    I guess most of the text buttons are the kinds that are typically put into top menus
    The rest are more like typical toolbar buttons
    Toni Ruottu
    @cyberixae
    I don't think top menus are very popular these days
    Toni Ruottu
    @cyberixae
    Not sure why
    Maybe they are still popular among productivity applications
    Tomi Jylhä-Ollila
    @kagu
    I guess they are mostly used in desktop applications
    But I do feel that we should probably add another tool bar instead, so that we can avoid unnecessary pop-up menus
    Toni Ruottu
    @cyberixae
    We could try that
    We can always rethink it later if it doesn't work out
    Tomi Jylhä-Ollila
    @kagu
    I'm about to add credits to the About window
    Should I just list the names without specifying the kind of contribution or add some more detailed info?
    Hmm, I guess some broad description of the scope of contribution would be appropriate
    because I would also like to mention Sami
    Tomi Jylhä-Ollila
    @kagu
    Maybe I'll split the credits to main/additional or something
    Tomi Jylhä-Ollila
    @kagu
    Hmm, I may end up removing the lowpass filter events entirely
    The system I'm currently developing for controlling audio unit internals is flexible enough to support that, once I add an actual filter processor
    Tomi Jylhä-Ollila
    @kagu
    I'm going to start working on the instrument expressions & strings soon
    Not entirely sure what might be a good user interface for that purpose
    Basically, the user needs to be able to select a subset of processors for each expression/string pair inside the instrument
    Toni Ruottu
    @cyberixae
    Write a proposal of how to do this with a bad user experience
    It is then easier for outsiders to comment how it can be improved
    Tomi Jylhä-Ollila
    @kagu
    Actually, I think I should implement this for instrument hits first
    It is a simpler case and also higher priority
    Tomi Jylhä-Ollila
    @kagu
    We really need to use something else than "string" for these upcoming instrument parameters as that word is bound to cause confusion
    Tomi Jylhä-Ollila
    @kagu
    I'm not actually sure if we should have a separate term for that
    Maybe we should just talk about two expression parameters, since they both provide the same functionality
    The expression vs. string distinction is merely useful for communicating the intended use (e.g. slap vs. lowest string in a bass)
    @cyberixae, any thoughts or comments regarding this?
    Toni Ruottu
    @cyberixae
    Without digging further into the question it is unclear to me what the implications of this decision would be or even what the options are
    Toni Ruottu
    @cyberixae
    Perhaps Kunquat could use Travis to run tests on pull requests
    "Testing your open source project is 10000% free"