FileZilla 3 development diary
Moderator: Project members
Here's the funnayyyyy: I'm currently adding a disconnect button to the toolbar (well, the disconnect button IS the toolbar)
In order to get the disconnect button working, I've to to implement the engine->ui message passing and most of the command handling functions as well.
If everything goes well, tomorrow FZ3 can disconnect from servers.
The next step would be to write the login code. After that, it would be required to implement the local/remote file lists and in case of the remote file list, the list engine code including the path and the list parser.
In order to get the disconnect button working, I've to to implement the engine->ui message passing and most of the command handling functions as well.
If everything goes well, tomorrow FZ3 can disconnect from servers.
The next step would be to write the login code. After that, it would be required to implement the local/remote file lists and in case of the remote file list, the list engine code including the path and the list parser.
botg wrote:[...] called poEdit. Unfortunately the interface looks crappy, guess I'll have to submit a patch to this project as well
Now, is poEdit's GUI crappy or nice?botg wrote:For the translators, there is a program called poEdit (http://poEdit.sf.net) with a nice gui [...]

BTW: Will FZ3 allow multiple child-windows for local and server views and will it be able to connect to multiple servers and do FXP?
There was a small glitch in the GUI that BotG fixed, submitted and got accepted.eyebex wrote:Now, is poEdit's GUI crappy or nice?![]()
I think the answer to this is yes, yes and yes! I'm not 100% sure, but who is?eyebex wrote:BTW: Will FZ3 allow multiple child-windows for local and server views and will it be able to connect to multiple servers and do FXP?
The poEdit GUI looked crappy but no longer does.
Connections to multiple servers will be handled with a tabbed interface, similar to Mozilla's tabbed browsing (oh I just love that) and FXP will be implemented using Drag&Drop. (If possible)
Today I've added the code that parses the replies into lines, messages from the server now get displayed in the message log. The login code should be easy to implement now.
I've also fixed some small bugs in FileZilla 2.2.5, I guess it's time for a small maintance release.
Connections to multiple servers will be handled with a tabbed interface, similar to Mozilla's tabbed browsing (oh I just love that) and FXP will be implemented using Drag&Drop. (If possible)
Today I've added the code that parses the replies into lines, messages from the server now get displayed in the message log. The login code should be easy to implement now.
I've also fixed some small bugs in FileZilla 2.2.5, I guess it's time for a small maintance release.
Build scripts always keep one busy.
The script on the server which generates the downloadable configure script tar.bz2 package for the update-configure script did not work properly. This has been fixed.
Also, I've fixed some dependancy issues and I'm trying to get the resource file inclusion for MinGW builds to work to get a nice application icon.
Other than that, I've made some small fixes, nothing big today.
The script on the server which generates the downloadable configure script tar.bz2 package for the update-configure script did not work properly. This has been fixed.
Also, I've fixed some dependancy issues and I'm trying to get the resource file inclusion for MinGW builds to work to get a nice application icon.
Other than that, I've made some small fixes, nothing big today.
I hope that you is wrong ... 32,5% is more cool ...botg wrote:While the changelog generation for FZ3 did already work for some time, it did not yet display on the changelog page.
But now the changelog is live and there are already 47 individual commits. Using v2 as a base with 1.443 commits, version 3 would already be 3.25% complete
Even better, I may release an early prealpha version in a couple of days. 
Well, I've recently implemented asynchronous dns lookups, so that incases of invalid hostnames or unresponding dns servers the interface doesn't get blocked.
Also, I'm switching to wxTextCtrl for the message log, the html parser is to slow to display 1000 lines in a short amount of time.
Though the text controls aren't perfect yet, there's still one feature missing (different indentations for the first and the remaining lines in a paragraph), Time to write another patch for wxWidgets.

Well, I've recently implemented asynchronous dns lookups, so that incases of invalid hostnames or unresponding dns servers the interface doesn't get blocked.
Also, I'm switching to wxTextCtrl for the message log, the html parser is to slow to display 1000 lines in a short amount of time.
Though the text controls aren't perfect yet, there's still one feature missing (different indentations for the first and the remaining lines in a paragraph), Time to write another patch for wxWidgets.

After three hours of debugging, trying to find out why the rich edit control didn't use the tabstops I did set, I found out that it was a glitch in the windows rich edit control itself: If using hanging indentation, the indentation mark did count as tabstop. And since my tabstop was after the indentation, it didn't seem to work.
So much wasted time I could have spent with something else.
Anyhow, my wxWidgets patch is almost complete, only the documentation has to be updated.
So much wasted time I could have spent with something else.
Anyhow, my wxWidgets patch is almost complete, only the documentation has to be updated.