Re: [Mldonkey-users] generalized GUI protocol

[b8_bavard]

I think the main problem of the GUI protocol is its missing
documentation.  Indeed, there should be a document describing it, with
two parts: the basic interface API (with a basic GUI example), and the
complete API.

Anyway, MLdonkey also uses the giFT protocol, you just have to connect
any giFT GUI to the normal giFT GUI port on a computer running
MLdonkey, and you will see that it works, maybe not as well as with
giFT, but this work has begun...

- b8_trop_bavard

>  I've been tinkering w/ MLDonkey for the last few days trying to create 
>  simple GUI for average computer users.
>  
>  My initial thoughts are that way too much "computer science" thought 
>  has been put into the ways that MLDonkey converses w/ various front 
>  ends... And the developers should take a lesson from the guys at 
>  giFT...
>  
>  the giFT GUI interface is extremely simple - all text based in 
>  key(value) pairs w/ semi-colons and spaces used as delimiters.
>  
>  The only drawback in giFT is that the GUI must work on its clock. e.g. 
>  whenever it feels like dumping data, you have to respond rather than 
>  the MLDonkey way of only giving data when it's asked for...
>  
>  Anyway...
>  
>  I would propose creating a simplified communications protocol - all 
>  text, use a "CMD { key(value) key(value) key(value) subCMD { key(value) 
>  key(value) }} ; " structure (like giFT...) but that only provides data 
>  when asked for.
>  
>  Lose all the regex stuff, lose all the binary-enum command list stuff. 
>  For people who love web browsers go ahead and keep all that...
>  
>  This would simplify GUI creation immensely - and would probably make 
>  MLDonkey the most popular p2p daemon around...
>  
>  My $0.02
>  
>  Or is this being done already and I just haven't seen it?