FileZilla 3 development diary
Moderator: Project members
Thanks for pointing that out, I was unaware of the fact that WinSCP uses code from FileZilla. A quick glance at the code reveals that they are using the old 2.x branch of FileZilla. I'm surprised they managed to separate the engine from the interface in the 2.x branch, it's not as modular as 3.x
So far I didn't get any code changes back (if there are even any), and frankly said I don't really care, the old code is a mess compared to FZ3.
Other than that, I've taken WinSCP's shell extension for the drag&drop support in FileZilla.
And that's all code sharing there has ever been to my knowledge. WinSCP has been written in Borland C++, FileZilla 2 uses the MFC and FileZilla 3 uses wxWidgets, three completely different frameworks which makes sharing code quite difficult.
So far I didn't get any code changes back (if there are even any), and frankly said I don't really care, the old code is a mess compared to FZ3.
Other than that, I've taken WinSCP's shell extension for the drag&drop support in FileZilla.
And that's all code sharing there has ever been to my knowledge. WinSCP has been written in Borland C++, FileZilla 2 uses the MFC and FileZilla 3 uses wxWidgets, three completely different frameworks which makes sharing code quite difficult.
I'm currently working on the context menu for the remote tree control. Most actions done by it would be recursive, like deleting a directory or adding a whole subtree to queue.
Right now, the code that handles recursive operations is part of CRemoteListView and not usable by other classes. Therefore I'm moving that code into a new class, CRecursiveOperation.
Right now, the code that handles recursive operations is part of CRemoteListView and not usable by other classes. Therefore I'm moving that code into a new class, CRecursiveOperation.
The context menu for the remote directory tree should be fully working now.
I've been trying to reduce the size of the generated executable. It's possible to shrink a little bit by tweaking the configure flags for wxWidgets, by disabling unneeded features (e.g. --disable-printarch disables printing support).
I've ran about a few problems where some parts of wxWidgets did not check if another features was disabled or missing include files, but I've fixed them quickly. Naturally I've submitted the patches.
In addition, I've been working on the FileZilla 3 installer. It's now possible to choose between "Install for all users" and "Install for current user".
I've been trying to reduce the size of the generated executable. It's possible to shrink a little bit by tweaking the configure flags for wxWidgets, by disabling unneeded features (e.g. --disable-printarch disables printing support).
I've ran about a few problems where some parts of wxWidgets did not check if another features was disabled or missing include files, but I've fixed them quickly. Naturally I've submitted the patches.
In addition, I've been working on the FileZilla 3 installer. It's now possible to choose between "Install for all users" and "Install for current user".
Roadmap for 3.0.1 and other future versions:
Add ability to customize timestamps and filesize formatting.
For the timestamp formatting I'm going to offer three options: Default, ISO 8601 and custom (using strftime format specifiers)
Implement remote file editing as far as technically possible. There are unique technical difficulties in implementing this, especially regarding programs which use a single instance to edit multiple files at the same time.
Add ability to customize timestamps and filesize formatting.
For the timestamp formatting I'm going to offer three options: Default, ISO 8601 and custom (using strftime format specifiers)
Implement remote file editing as far as technically possible. There are unique technical difficulties in implementing this, especially regarding programs which use a single instance to edit multiple files at the same time.
Now that v3 is official, is it possible to save the settings in a XML file in the the program's own folder?
Does it support ascii in SFTP?
And does it support Creating and/or Revealing linked files?
Also, does it still lack everything in Roadmap?
Thanks!
Does it support ascii in SFTP?
And does it support Creating and/or Revealing linked files?
Also, does it still lack everything in Roadmap?
Thanks!
Have a look at docs/fzdefaults.xml.examplelwc wrote:Now that v3 is official, is it possible to save the settings in a XML file in the the program's own folder?
No. OpenSSH doesn't, as such I have no reference implementation nor testing environment.Does it support ascii in SFTP?
No.And does it support Creating and/or Revealing linked files?
Yes, still lacking. Will be implemented in a future version.Also, does it still lack everything in Roadmap?
Interesting, I had no idea this feature is so important for so many users. Personally I've never used it. Even during 3.0.0-rc3 there were only very few comments regarding the lack of this feature. But now that 3.0.0 is out, tons of users are complaining.Hmm, I can't work with v3 until I could edit files remotely. That's 99% of what I do in Filezilla...
As far as I know it just emulates ascii transfers. It relies on the user to tell it the line ending format of the server and performs the necessary transformations itself. In that case the user could as well transform the files himself with some external program before upload or after download. Besides, all modern editors support different line ending styles.As for ascii in SFTP, do remember the open sourced WinSCP supports it (more details in the aforementioned link).