Alo Sarv
lead developer

Donate via
MoneyBookers

Latest Builds

version 0.3
tar.gz tar.bz2
Boost 1.33.1 Headers
MLDonkey Downloads Import Module Development
Payment completed
Development in progress.
Developer's Diary
irc.hydranode.com/#hydranode

Monday, December 19, 2005

Small changes

A new command has been added to shell, links <num>, which displays plugin-specific links to downloads (e.g. ed2k:// links, location to .torrent file and such). Original idea and feature request by chemical.

Some settings locations have been changed / renamed as well. MailNotify was using "MailNotify" section (capital letters), but the current standard is all lower-cased, so that was changed to conform with the standard. HNShell module wasn't following the standard location for it's settings either, it's settings were stored at top-level, and with long-and-ugly names. Now HNShell settings are stored in [hnsh] section, and have been renamed somewhat to be easier to change / remember.

Shell Command Reference is now somewhat more complete, with few added commands and some rephrasing of descriptions here and there. Also, there's a new page - Configuring Hydranode - in the devcenter, which lists all config.ini settings along with descriptions.

I also dropped the second UDP port used in ed2k module - at hardcoded TCP + 3 port - which was used for server queries. Now both client and server queries are handled by the same UDP port (4673 by default), and it's no longer needed to forward two UDP ports from router / firewall.

New builds for Windows and Linux have been uploaded.

Madcat, ZzZz



Comments:
Thanks for the updated Command Reference, sure helps a lot. Maybe you should put a link onto the Documentation page of the main page (http://hydranode.com/docs/index.php). That would help people new to the project to find it, too.
Btw, the lsmod command is mentioned twice on the doc page in "Statistics-related" and "Modules management".

Greets,
Majin Sniper
 
Btw, the lsmod command is mentioned twice on the doc page in "Statistics-related" and "Modules management".

Yes, because it's both statistics related AND modules management related :)

Madcat.
 
[IMHO]
Trying giving a robust base and structure to this software is good choice but I (IMHO) think that by pushing developing of GUI's interface protocol (and giving specs to sancho's developers) 'll provide a wider user base to your software.
My opinion/suggestion (Perhaps I'm wrong) is to slow down developing of core's features/debuggin' and concentrate on interface issues for a while. It' s quite a marketing choice.
[/IMHO]

Ps: I like looking at your developer's diary and hydranode advancement, goodluck ! Fabtar
 
"My opinion/suggestion is to slow down developing of core's features/debuggin' and concentrate on interface issues for a while."

User interface will be the next step after BT-plugin is finished.

Hydranode Roadmap:
" Core/GUI Communication: On hold until BitTorrent is finished"
 
Then we all dream to see BT done! :)

can i call u "santa claus madcat"? :)

i guess we both people here are ager to receive this new toy O:)

Good night...
if i wasn't again in a 15 hours of code by myself i would love to help u ;)
 
"My opinion/suggestion (Perhaps I'm wrong) is to slow down developing of core's features/debuggin' and concentrate on interface issues for a while. It' s quite a marketing choice."

I'm against things, because HN will be another cool app but that it will end running like MLDonkey and wrongly unmaintained code.

I prefer putting the low wor k first the best possible and later giving it to the users that don't have idea of techie stuff. This will give very strong low level stuff to the project, that is very important to developers. It's better wait than doing things too early and wrong.

My think about the project: better supporting a lot of non-GUI stuff interesting to very different types of users (casual p2p user, hardcore p2p user...) and then give the best GUI of the P2P world ever.

Start donations to Madcat ;)
 
Post a Comment



<< Home

This page is powered by Blogger. Isn't yours?