FileZilla 3 development diary

[boco]

Before: <removed, problem fixed>

After: <removed, problem fixed>

[botg]

Fixed. Oh, and always use .png for screenshots. .jpg makes screenshots look like taken on a touchscreen. Filthy and dirty.

[redleg]

Every time settings are accessed (whether clicking ok or even if canceled) all tabs other than the first will go full length side to side (left to right) for directory and file panes.

Fixed.

By the way, for bug reports there's http://trac.filezilla-project.org/

sorry bout that, I finally registered there yesterday and made the sticky 990 bug- was looking for confirmation on this client one before creating another report. btw, thanks for the quick fix. Is a new download in place off the old one or do I need to grab a nightly?

Code: Select all

[edit- add] disregard, I see the note in trac to grab the nightly

[botg]

Nightly, tomorrow.

[boco]

Nightly seems to have fixed my problem.

[botg]

Busyness as usual. The upcoming version of FileZilla will feature mostly internal changes and small improvements and of course the usual collection of bugfixes.

Of the highlights to come:

• Arrows indicating sort direction in file lists on non-MSW systems
• Refresh item in context menu of file lists
• Added context menu to tab bar

Especially the last change provoked me to refactor large parts of the code that handles the appearance and functionality of the main window and the tabs. The sheer complexity of the code is the biggest obstacle. The main window has to react to all sorts of events coming from all other parts of FileZilla. Much of the functionality has already been moved into other, more specialized places, but the myriad interdependencies are making it difficult.

[botg]

3.3.1-rc1 is out with the above mentioned improvements as well as the usual collection of bugfixes.

Behind the scenes I made some improvements to the nightlybuild system. The plan is to eventually create builds for each and every SVN commit so that changes can be tested in a more timely manner.

Up until now, the build scripts created a huge compressed tarball with all the sources and uploaded them to the systems actually compiling said sources. Needless to say, if this would be done for every single commit instead of once every night, a lot of network bandwidth will be consumed. A possible way to solve this would have been to simply check out the sources from the source repositories on each build node. However this won't work for several reasons. For once, the SVN servers of both wxWidgets as well as SF.net (which hosts the FZ repository) are somewhat slow and have been quite unreliable in the past. More importantly, lots of files in the source distribution of FileZilla are generated, they are not stored in the repository, for example the configure script, or the many Makefile.in files. Depending on which system those files are generated, the used versions of the GNU autotools and several other factors, these files may differ. So no two build nodes would actually compile the exact same source which would make debugging any potential issues a nightmare. To solve this dilemma, I'm now distributing the sources through rsync, which has the benefit that only those files are transferred that have actually changed. To be precise only those parts of the files that have changed. Copying around local working copies during the build process is now also done using local rsync to further speed up things.

In addition to cutting down bandwidth requirements, these changes also reduced build times by around five minutes, time that was previously spent on copying, (un)tarring and (de)compressing the sources.

[boco]

The tab context menu's "Create new tab" has no effect for me. Windows version 3.3.1rc1 .

[boco]

The greeting message from FileZilla now appears every time instead of one time only. From a quick look it seems there is no configuration entry written to filezilla.xml.

Intended because of release candidate? Or did a bad one slip in?

[botg]

Must be your system, nothing has changed in that part of the code.

[boco]

Edit: Scratch that - forgot to remove a kiosk mode 2 I had from a test. Doh!

Could you add a visual indication if you're running read-only? For example in the titlebar: FileZilla (read only).

[Weedy]

PRET is not part of any FTP standard.

Hello,
it's making me sad to read that all the time.
Can you please talk to the people running http://filezilla.de and tell them to correct their text?

They wrote "bei gleichzeitiger Unterstützung möglichst vieler nützlicher Features entwickelt."
which means "while supporting as many useful features as neccessary".

This part is absolutely wrong, since you didn't - as read in a topic in this forum - implement it, although it's easy to do and a useful feature.

I love FileZilla (although the Qeue is kinda weird), but I can't see a useful reason to not implement an easy implementable feature.
Breaking the standard? I don't want to marry it, just use it. I don't care what it does as long as it works.

Sounds ignorant? Open your eyes! Internet Explorer is the most used browser, just because it's easy to use it instead of installing an other browser.
I hope you're aware of your target group. Is it the ftp-cmd-linux-geek-hacker-dude that cares about every and each fart and watches out that it's (oh my god beware) nothing like any Microsoft product or people using FileZilla because work has to be done and they need an easy, usable application theirfor?

I think the idea of keeping a standard is great if else it would have alot of different implementations of the same feature. But in this case there is only one possible implementation and it's already the most popular one, because (afaik) there's no alternative.

Also even if it "breaks the standard", it does it in a good way, doesn't it? Since when are distributed systems bad?

[botg]

PRET isn't useful, it's useless. Just don't bother making the storages of independent machines available under a single hostname, that's just bollox.

[Weedy]

PRET isn't useful, it's useless. Just don't bother making the storages of independent machines available under a single hostname, that's just bollox.

I don't see a way to retrieve files directly from a slave in passive mode without breaking the holy standard. Could you explain this hostname stuff further? If neccessary, we could move it to a new thread, too.

[botg]

A common complaint has been that it was too hard to change the speed limits on-the-fly. This is going to change.

In the next version, the speed limits will be easily accessible through the menu and also through the statusbar:

speedlimit.png (7.19 KiB) Viewed 15812 times

If all limits are disabled, the icon turns grey.


The plan is to further add this to the toolbar in a future version, but it'll require some more work as I want to make the toolbar configurable. It's already getting too long.

Obvious rant: Thanks to Microsoft and its shady business practices we're plagued by netbooks with terribly low screen resolution so that they are allowed to run Windows. Any higher res and Microsoft doesn't sell the vendors any licenses...