FileZilla 3 development diary

Moderator: Project members

Message
Author
User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#721 Post by botg » 2007-11-30 18:10

Won't happen. Nightlies are nightlies and can contain potentially dangerous code.

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#722 Post by botg » 2007-12-02 18:51

Some progress report:

- Comparing directories works fine
- Listings will be aligned side-by-side (depending on used layout)
- Scrolling is synchronized between local and remote listing

Currently I'm refactoring the code a bit, I'm trying to get rid of the high amount of code duplication between local and remote file listing

lwc
550 File not found
Posts: 32
Joined: 2005-09-03 18:14

Re: FileZilla 3 development diary

#723 Post by lwc » 2007-12-05 11:58

Please stop v3 from loading my floppy drive on each load. It drives me nuts...

Some notes about editing:

* The remote editing is impossible to work with because it keeps asking me if I want to keep/delete the local temp file.

* Please add v2's local "view/edit" and "open" commands.
Last edited by lwc on 2008-01-14 13:35, edited 1 time in total.

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#724 Post by botg » 2007-12-05 12:49

Ask Microsoft to fix it, it's a problem with Windows.

lwc
550 File not found
Posts: 32
Joined: 2005-09-03 18:14

Re: FileZilla 3 development diary

#725 Post by lwc » 2007-12-06 00:22

Are you talking about the first issue? How come it doesn't happen in v2?

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#726 Post by botg » 2007-12-06 01:01

No idea, it shouldn't even happen with FZ 3. All that FileZilla does is to enumerate all drives and to get the labels of all drives. For some stupid reason Windows doesn't remember the labels of floppy drives and checks all the time...

lwc
550 File not found
Posts: 32
Joined: 2005-09-03 18:14

Re: FileZilla 3 development diary

#727 Post by lwc » 2007-12-06 10:42

What about my notes? Will you give them some thought?

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#728 Post by botg » 2007-12-06 11:12

When it's done.

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#729 Post by botg » 2007-12-06 16:45

While implementing the directory comparison code I've noticed again how similar local and remote file list are. Yet still they are very difference, sometimes quite obvious, sometimes more subtle.

So far I could factor out the following code into a common base class, which also gets used by the queue in some cases:
- Scroll event handling
- Prefix search navigation

So far that's rather generic list control code, hence I named the class wxListCtrlEx in lack of a better name.

I'll try if I can also factor out the sorting code somehow, as it's again rather similar between the local and remote file lists.

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#730 Post by botg » 2007-12-13 09:43

Ah, this day started so well. Could not possibly become any worse. :(

A nice mail in my inbox about a new security updates available for Debian Etch.

So I logged into filezilla-project.org (which is running Etch) and started the update procedure. One of the updates available was a kernel update. Installing it was simple and afterwards it wanted me to reboot. So I did. But the server did not come up again. Panic! :shock:
Even though Debian told me that I was about to install the same kernel version, I figured out it must have changed and that I forgot to tell the boot loader about the new kernel version.

So I went to the server administation interface of the hosting company, enabled the rescue system and initiated a hardware reset. 15 seconds later the rescue system was up and running. Lucky me ;) I then did the usual mount sequence (root partition, and proc, binding dev). And of course it's using the terrible lilo boot manager. Anyhow, one command and it was fixed again. One more reboot and the server was back up and running.

What's the problem with nearly all operating systems? They absolutely love to piss you off by overwriting your custom bootloader. But if you perform a simple update inside the system, they fail to detect and update the very same bootloader they have written themselves.

sonu1234
500 Command not understood
Posts: 1
Joined: 2007-12-18 09:17
First name: Sonu
Last name: Singh

Re: FileZilla 3 development diary

#731 Post by sonu1234 » 2007-12-18 09:22

can you plz describe here what all new features or bug fixes each newer versions haves this will give all the File Zilla user an idea that why should they update to the newer version....
Last edited by sonu1234 on 2007-12-20 05:59, edited 1 time in total.

eyebex
226 Transfer OK
Posts: 171
Joined: 2004-04-02 15:24

Re: FileZilla 3 development diary

#732 Post by eyebex » 2007-12-19 16:00

This is not the right place to post a changelog. The changelog can be obtained for each release from the project download page:

http://sourceforge.net/project/showfile ... p_id=21558

Simply click on the brown-ish "Notes" icon for a release. Alternatively, see:

http://www.filezilla-project.org/changelog.php

eddan
226 Transfer OK
Posts: 423
Joined: 2004-02-25 08:44
Location: Norway
Contact:

Re: FileZilla 3 development diary

#733 Post by eddan » 2007-12-21 00:15

In addition to the links eyebex gave, check out http://wiki.filezilla-project.org/FileZilla_FTP_Client which probably is the best changelog for the average user.
For help and support, check out the support page on the wiki.

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#734 Post by botg » 2007-12-21 19:53

A few days ago, Vadim Zeitlin, one of the wxWidgets lead developers, proposed to refactor large parts of the wxWidgets socket class. (See http://thread.gmane.org/gmane.comp.lib. ... vel/95761/ for the discussion).
The primary reason is that nobody is able to understand the socket code fully anymore. I have tried myself a few times in the past to investigate a few bugs. It was a rather painful experience. As such, adding new features to wxSocket, e.g. sockets for GUI-less programs, has become increasingly difficult.

Naturally I've been very interested in this discussion. Without a good socket class, FileZilla cannot function.

Amongst other things, we were discussing the semantics of the various socket events. While looking through the code, I've noticed a problem in the way wxWidgets did reuse socket message ids on Windows. (For use with WSAAsyncSelect).
There is a chance that a socket ID can be reused while there are still pending messages to be processed. As a result, a new socket can receive messages intended for a previously destroyed one. After discussing a possible solutions I came up with a patch for this problem as well as a test case: http://sourceforge.net/tracker/index.ph ... tid=309863

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla 3 development diary

#735 Post by botg » 2007-12-25 16:23

I've spent some time to improve FileZilla's support for right-to-left languages on wxGTK (e.g. Linux and the likes).

I've fixed the following problems:
  • Positioning of message log
  • Send/recv indicators
  • Queue tab navigation buttos
  • Queue tab display
To fix the last problem, I had to create another patch for wxWidgets, see http://sourceforge.net/tracker/index.ph ... tid=309863

Other than that I've fixed a problem with the keepalive timer under wxGTK leading to crashes. I've also changed the code so that errors while writing to a file are now critical since they almost always require user interaction to be resolved.

Post Reply