@holograph sorry again, I'll review the PR on the next few days
So as promised, I merged #158 (thanks @holograph!) and also published earlier today a blog post in which I share some thoughts regarding muCommander: http://ahadas.github.io/about-mucommander. Would love to get your feedback on this!
Hi guys, I just found out about muCommander and I really like it so far. Maybe I'm stupid or something but how do I get to the user documentation? Using Help > Online documentation in the application takes me to Home · mucommander/mucommander Wiki · GitHub. The bullet there that says "Documentation, to learn more about the way muCommander works." on that page doesn't have any link (the other bullets do). I can't find any in the github wiki side bar either, nor on the homepage :/
Hi Oscal, welcome :)
Unfortunately, that part never existed. You can find the original link at:
http://web.archive.org/web/20140814211713/http://trac.mucommander.com/wiki/Documentation
May I ask what were you trying to find in the documentation?
Unfortunately, that part never existed. You can find the original link at:
http://web.archive.org/web/20140814211713/http://trac.mucommander.com/wiki/Documentation
May I ask what were you trying to find in the documentation?
Hi @ahadas :) Thanks for your reply, that explains I couldn't find it ;) Mostly what I wanted to check was if there's a recommended way to backup my custom keyboard shortcuts + bookmarks as I've modified them quite a lot by now. I've also managed to restore the factory defaults once so I had to start over.
@ocyj , well, I'm afraid the only way is to back them up manually: browse to the folder that hold the customization files (it depends on the operating system you're using, see: https://github.com/mucommander/mucommander/wiki/Preference-Files) and copy action_keymap.xml and bookmarks.xml elsewhere.
Guys, I'm glad to announce that version 0.9.3 has been released! It is a relatively small release that includes few important fixes and some very nice contributions from the community. As a token of appreciation, @holograph and @thomasuebel were added to the list of contributors. Thanks guys and keep up the good work!
@ahadas hey mate, I was hoping .. could you please shed some light onto the release process ? The readme shadowJar seems to be commented out. What is the way to get the full jarfile to run with the runner script? (trying to run it this way for debugging purposes in other enviroment). cheers
@kousalik hi and welcome! :) not all the packaging options have been adjusted to OSGi yet. We will no longer the application as a single jar but as an OSGi application, like Eclipse, that is composed of a running script, the apache-felix framework (or any other framework that we prefer) and a folder of bundles. You can take the RPM packaging as a reference, I started to adjust it
If you like to fix the packaging for the specific distribution you work with and need an assistance, please let me know
cool, I figured that out at the end ... reseting to the last release commit should do for me at the moment. what about some prioritization? tasks to track progress or at least give some context around the work ppl could do? I guess not really necessary if you're the only active developer. Anyway I thought I could get my head around the source a little by looking at some of the issues. Anyway, I'll try to have a look at some of the issues working in the 9.3.4 branch.
If I'm successfull I'll fix it in both streams
@kousalik , yeah - so I think we're talking about two different things here. (1) progress tracking - we used Trac in the past and then tried Jira but that seems to be overkill at the moment, as you wrote; and (2) pool of features that newcomers could take something from - I started to write something in https://github.com/mucommander/mucommander/wiki/Roadmap. That being said, I think that our main focus should now be stabilizing the master branch (fixing stuff that got broken by the switch to OSGi, including packaging) and addressing some of the more important issues, in order to release 0.9.4
Then I think we can publish the artifacts needed to implement new plugins, which will make it easier for people to introduce new functionality, like a PDF viewer
But it was hard to keep them sync and we kind of mads duplicate efforts in few areas
I am trying to build+debug ... without success
I get
2: Task failed with an exception.
Where:
Build file 'D:\arn\downloadTools\hadoop\hdfs-explorers\mucommander\apache-bzip2\build.gradle' line: 16What went wrong:
A problem occurred evaluating project ':apache-bzip2'.Could not get unknown property 'revision' for task ':apache-bzip2:jar' of type org.gradle.api.tasks.bundling.Jar.
Any idea ??
hi @/all , there is an ongoing discussion about switching to Discord (https://github.com/mucommander/mucommander.github.io/pull/3#issuecomment-782229116) and as this group has not been active for a while, I'm wondering whether it has something to do with the tooling itself (gitter) and if so, whether Discord would be better. I'll appreciate your feedback on this!
if it managed to support OneDrive, Box and GDrive, even with third party plugins, I´d be all set.
@fcassia_twitter , google-drive was added in 0.9.6 . I was about to write you that I'm working on adding dropbox but I see that 'box' is a different thing :) it's now easier than ever to add new services like that - how about filing an issue on github for 'box' (we already have one for onedrive) and see if someone will pick it up?
Hi Arik, many thanks for your work, my donation will be soon :) I almost managed to reconfigure muC to mimic win TC with all keybindings (even Alt+F5 +F7 etc) trying to replace TC to unified work on linux and macosx and have only few quirks. One is SCALING, when linux ubuntu gnome is at 125% fractional, then muC is TINY - appearance fonts to 24pt helped, but rest of UI tends to be tiny still - is somewhere possible to direct java to scale it with -Dsun.java2d.uiScale.enabled=true or so? Another thing which is weird is nonpersistence of remote connections (I tried FTP, SFTP along with gdrive too, which is fastest, but nothing was persisted - always needed to enter password and each service has then only one instance?) but again, thanks a lot, it elps me to live in lin/mac :)
@apws thanks for the feedback :) iirc tuning scaling by default was addressed by a later version of Java - but the one I previously upgraded to (11) was buggy so it was reverted back to Java 8. need to give it another shot. persistency - yeah, we generally store the credentials but it's different with those cloud storages (google drive and in the next release also dropbox) that require authentication through the browser - their credentials are stored differently (in the .credentials folder)
and good to hear you plan to contribute key bindings! I had some thoughts about it in the past, like that it would be nice to configure them differently per-OS. do you intend to change the default bindings or to make more intrusive changes to the implementation?
hi, I summarized my approach here - its from the point of view of windows user, ya
mucommander/mucommander#437
mucommander/mucommander#437
one thing I dont know how to achieve yet is making separate virtual volumes (mimic win drives) on unix-like; its probably some symlinks mounted under /Volumes (on mac) ... in windows I use such few root "drives": H: ~/ O: ~/OneDrive W: ~/OneDrive/Documents P: ~/OneDrive/Pictures V: ~/Versioning X: ~/Downloads (easy by VisualSubst app)
in relation to code contribution, I am only few weeks back in java after 20 years (from C#), but commited to stay to death, probably )) ... peeking into muCommander source caused me some kind of fever though ... I know its organized and well done, but too much well done for my current abilities to help :))
and yeah, the separation to modules with OSGi definitely complicated the repo but on the other hand, should make it easier for us to provide an API for plugins
let me know if I can assist with questions or things that block you from contributing
ale nice thing would be to ensure only one instance - both things switchable in settings, sure