instead of immediately backgrounding, have the client background after initial messages.
Similar for later "controlling" wuala instances, don't exit or background until the command completes (or fails) or all output has been sent (in case of logins if that is handled as a non-terminating command)
Linux version should notice that the arguments are commands and ALWAYS try to connect to previous instance. If no such instance exists it should give an error such as "Wuala is not currently running."
The current behavior is to try to start another instance. This causes problems if you are using nogui and nomount and basepath to start wuala, If wuala isn't running it tries to start and fails.
i had the idea to implement a detailed view into the filefolder structure because often filenames are cut or you cannot see how big or small a file is
can you maybe implement a detailed view into one of the next versions ?
It would be great to habe a tab in Wuala that lists the files downloaded from anywhere (meaning the world tab) so it isn't necessary to look the files up by hisself.
Hallo,
Ich weiß, dass das schon einmal angesprochen wurde. Dennoch möchte ich die Entwickler noch einmal darauf aufmerksam machen, dass ich mir eine Trennung von GUI und Core wünsche. Wie der Core auf dem Server gestartet wird, wäre mir garnicht einmal so wichtig (Daemon oder Screen), momentan mache ich das mit Screen. Mir fehlt nur einfach eine Option in Wuala, die es einem ermöglicht, sich zu einem auf einem anderen System laufenden Core zu verbinden.
Hoffentlich wird das in einer der nächsten Version eingebaut!
Viele Grüße
I need a button and visual feedback to verify that all the uploads are done.
I often work in a laptop and when I am finished, I copy the current work to Wuala and shut down the computer. When I go to the another computer next morning, I get a message that the file is not uploaded.
I even once got a crash during the upload and the file was not uploaded in any of my computers!
So I want some transaction kind of thinking here. When I copy a file to wuala, I wont it certainly be in the local cache when the operation is finished. I want to be able to delete the file at this point and be sure that Wuala takes the responsibility of the file - even thought it is still in the local cache.
In the transaction two I want to be sure that the file is available from other computers. I want a visual feedback when this has happened and I want to be 100% sure that it has actually happened. Even if a lightning hits to my computer at the same second.
And I certainly don't want that the system updates the metadata before the actual data. If the upload fails, I want to find the current version. Currently I get a message that the file is not uploaded and the old version is not available.
I don't think that Wuala makes a good job with these transactions currently. At least I have LOST some important data already.
Summary: If I put SVN (Subversion) repository to Wuala directory file:///W:/me/SVN it does not work. I get some "forbidden operation"-type messages. I guess, some unsupported locking scheme is needed.
I have a limited group of people developing code.
Currently I have to set up a complex subproject to the central SVN version management repository server. Everything has to be agreed with the repository responsible. It would be much easer that the group could have their SVN repository as a directory in a Wula group directory. Additional benefit is to be able to access the repository from everywhere in the Internet. Relatively securely.
A SVN repository in a shared network disk should work. It is especially mentioned that FSFS (native file) type repository works reliably at shared network disks (but Berkely DB does not).
Hey, I think it would be really great if you could daemonize Wuala - I mean you would be able to run wuala as a daemon from the console on a *nix system to share disk space on a server system with no GUI desktop.
I already told you guys that support for symbolic links would be a great idea too.
I by the way also think that this web-only thing in the upcoming version is great! But above I have two more ideas to make Wuala even greater ;)
Hi People,
I am running multiple PCs at home each with at least 2 HDDs. 1 of the HDDs is meant as a backup for 'more important' files or simply to add more storage. Now my problem is that Wuala can only use space on one partition. This means that I cannot share all the space that I don't need simply because I cannot divide it.
I would love to see an option which allows me to share Folders on different partitions and set a seperate sharing-limit on each of them.
I hope that this is possible and feasible for you to integrate since it would help me a lot!
Every so often, people ask where the downloads are. They remain at their original location and you need to navigate there. The downloads window helps you find them. Also, you can add the file to your favorites so that you find them again.
However, it doesn't solve the problem of accessing the files via the network drive, especially if it is a file from the world area (where is it??). There's no central place for downloads yet. What about the following idea?
- We introduce a new special folder "Downloads" under your files. A central place for all downloads.
- You can open it in Wuala or via the network drive W:/USERNAME/Downloads
- Only explicit downloads appear there. Files that you open directly (double click, e.g. in the world are) won't.
- You can keep the files forever, or delete them to free up HD space, as you like
- The download window remains, to show progress, speed and such. If you clear the list there, it does what it says, not more, meaning that the list is empty but the files remain in your downloads folder.
The concept is very similar to a browser download (downloads window, file on desktop). Also, you can execute files directly in the browser (open) or download them explicitly, also similar. Favorites would be a bit obsolete - we could introduce a 5-star rating later.
I have serveral computers on my network that run wuala. So If I Ctrl-D something on one client and I moved to a different computer while it was downloading and would like to have the file on this other computer I don't want it to be downloaded from the internet again but rather from the other computer where the file is already present, at a substantially higher speed. This is for a scenario where several clients run under the same user, not sure if it makes a difference if the clients run under different users...
Generally speaking, wuala clients on the same network coulb build a micro-network and serve requests internally, if a piece is not found, resort to downloading from the big network on the internet.
The nicest thing about wuala for me, apart from file availability and encryption, is the network drive option for Windows computers. This is because it is transparent to the user and requires no additional steps to work with files, you simply manipulate the files as if they were on a local drive. In a business environment this would be great because the user needs no additional training to use the program.
What I would like to see is a version of the client for mobile business users with the following features:
-Disable 'world' access so that business documents cannot be shared with the outside world
-Enhanced sharing permissions and access control
-Better Windows x64 network drive integration and Linux FUSE support
-Sync to local 'master copy' of files, on company intranet server.
I think businesses would gladly pay for such a version because of small infrastructure & training costs.
Ich würde gerne meine Dateien mit Gruppen teilen, das geht zwar, nur haben die Gruppen auch Unterverzeichnisse. Wuala kann zwar meine Dateien an eine Gruppe schicken aber dort nicht in Unterordner. Das geht zwar wenn ich direkt un den Unterordner der Gruppe gehe und die Sachen dort hochlade, dann landen die Sachen bei mir selbst aber nur im Group Postings Verzeichniss. Wäre doch super wenn man das irgendwie ändern könnte, also das wenn ich Dateien oder Verzeichnisse an eine Gruppe Weiterposte, dass dann auch die Unterverzeichnisse angezeigt werden.
clearing the local cache should be done asynchronously, I think... I accidently hit that button and now the gui's been blocked for several minutes already...
In the bottom of the main Wuala window there could be a couple more informations that users always like:
- Data used in local disk (traded space) - along with the used space;
- Uploaded total and downloaded total in a stats icon/button or on mouseOver the current upload/download speed.
it would be nice if there was a feature to be able to protect elements in the wuala store so that applications which work with the filesystem integration (driveletters, pathnames etc...) couldnt accidentally change modify or delete your stuff in there.
it would then for example only be possible to alter the contents of a folder or to delete stuff from within the wuala gui, but not on via driveletters/pathnames.
in a similar way there are usb-storage sticks, flash-chips or harddrives that have a physical little switch where you can set a read-only mode and thus protect your data for example from virusses, install programms accidental deletion and so on.
As the amount of data requested can make a long list in a few moments there should be a new tab next to the actions icon.
Instead of showing popup windows for a "Save as" action, it could simply add a download to a queue.
By drag'n'dropping queue items to the same "level" as an existing queue item, it sould download both at same time.
I can provide a schema to exemplify my idea...
havent found anything useful yet to my idea so i just post it.
how about letting wuala "observe" one directory for any new files (f.ex. images) and then upload them automatic. in googles picasa there is such a function which observes the directory and whenever a new image hits the directory it gets indexed. same function for wuala would be awesome! (making backups would be much much easier...)
if there is already such a function.. i havent seen it (maybe too blind..)