Search Results

Search found 3 results on 1 pages for 'zamza'.

Page 1/1 | 1 

• Route global shortcuts to pages opened in Firefox

  - by zamza

  I like listening to music online on sites like stereomood.com. There is a major problem, however. I can not control the player with my keyboard. And even with a mouse - when I want to play/pause I must activate firefox window, select the tab where music plays and hit play/pause button manually - this is a pain, especially when you play a fullscreen game that can not minimize itself. Thus said, global keyboard shortcuts would be a perfect solution. I understand that different online media players have different controls and each site must be configured individually (like, select button with id 'play' and press it), but I believe that can be done in principle. I also guess that such tricks are impossible without some third-party native app which captures shortcuts and routes them to Firefox window. So, any solutions? Maybe some AutoHotkey hacks or similar.

  Read the article

• A layout for maven project with a patched dependency

  - by zamza

  Suppose, I have an opensource project that depends on some library, that must be patched in order to fix some issues. How do I do that? My ideas are: Have that library sources set up as a module, keep them in my vcs. Pros: simple. Cons: some third party sources in my repo, might slow down build process, hard to find a patched place (though can be fixed in README) Have a module, like in 1, but keep patched source files only, compile them with orignal library jar in classpath and somehow replace *.class files in library jar on build. Pros: builds faster, easy to find patched places. Cons: hard to configure, that jar hackery is non-obvious (library jar in repository and in my project assembly would be different) Keep patched *.class files in main/resources, and replace on packaging like in 2). Pros: almost none. Cons: binaries in vcs, hard to recompile a patched class as patch compilation is not automated. One nice solution is to create a distinct project with patched library sources, and deploy it on local/enterprise repository with -patched qualifier. But that would not fit for an opensourced project that is meant to be easily buildable by anyone who checks out its sources. Or should I just say "and also, before you build my project, please check out that stuff and run mvn install".

  Read the article

• Customized generation/filtering resources with maven

  - by zamza

  I wonder what is the Maven way in my situation. My application has a bunch of configuration files, let's call them profiles. Each profile configuration file is a *.properties file, that contains keys/values and some comments on these keys/values semantics. The idea is to generate these *.properties to have unified comments in all of them. My plan is to create a template.properties file that contains something like #Comments for key1/value1 key1=${key1.value} #Comments for key2/value2 key2=${key2.value} and a bunch of files like #profile_data_1.properties key1.value=profile_1_key_1_value key2.value=profile_1_key_2_value #profile_data_2.properties key1.value=profile_2_key_1_value key2.value=profile_2_key_2_value Then bind to generate-resources phase to create a copy of template.properties per profile_data_*, and filter that copy with profile_data_*.properties as a filter. The easiest way is probably to create an ant build file and use antrun plugin. But that is not a Maven way, is it? Other option is to create a Maven plugin for that tiny task. Somehow, I don't like that idea (plugin deployment is not what I want very much).

  Read the article

1