Steven Schveighoffer schrieb:
> Because you haven't submitted a ticket for it yet ;)
> 
> http://www.dsource.org/projects/tango/newticket
> 
Good idea.

I also have a problem with non-ASCII characters.
But I couldn't find out the cause yet :(


[sendCommand] Sending command 'CWD Dreckschlüpper
'
[readResponse] Expected Response 250
[readResponse] Actual Response 550
[sendCommand] Sending command 'QUIT
'
[readResponse] Expected Response 221
[readResponse] Actual Response 221
tango.net.ftp.FtpClient.FtpException: 420 Goodbye.
. "Dreckschlüpper" : no such file or directory.

Lars Ivar Igesund wrote:
> Dear D community 
> 
> A new version of Tango is now available for download. The release is named after Sean Kelly for his past work on the Tango runtime and now druntime. The release have several new features, and fairly major changes to tie the IO even closer together. To make the transition easier, the previous incarnation is still available for this release.
>  This has been a much delayed release compared to the earlier Tango releases, but time has been spent fairly well, covering 301 closed tickets and more than 600 commits. 
> 
>  * Final refinement of the IO  * JSON parser/builder  * FTP adapter for the VFS by Lester L. Martin II  * Serial port support by Robin Kreis  * Inter-thread communication by Steven Schveighoffer  * /dev/null support by Fawzi Mohamed  * Random framework by same Fawzi  * BigInt by Don Clugston  * Updated for DMD 1.041, including Mac support  * Support for LDC  * OpenSolaris support by BlueZeniX  * New API docs courtesy of Aziz and Moritz  * More containers such as HashFile  For a complete list of changes please see the changelog. We welcome all feedback and testing. 
> 
> We're in the process of updating to new API docs as mentioned above, now generated by dil. You can see the docs for 0.99.8 at http://www.dsource.org/projects/tango/docs/0.99.8 or later download them from via the download pages.
> 
> We are always looking for new participants, so feel free to contact us via the page linked below. In particular, we are looking for someone to help drive the online presence via our Trac pages. 
> 
> The Tango homepage can be found at http://www.dsource.org/projects/tango 
> 
> Downloads: http://www.dsource.org/projects/tango/wiki/Download 
> 
> See http://www.dsource.org/projects/tango/wiki/TopicInstallTango for more detailed installation instructions for your system. 
> 
> Contact information at http://www.dsource.org/projects/tango/wiki/Contact  ------
> 
> Signed, 
> 
> The Tango Team
> 

That's great.

A few thoughts on the new documentation:

The new dil generated documentation is a little hard to read. There is no space after the documentation of an item and the text item. I also liked the old font better than the new. Now when the documentation for object.di is actually generated we could perhaps get some documentations for it.

Other from that I really like the new documentation.

Jacob Carlborg wrote:

> Lars Ivar Igesund wrote:
>> Dear D community
>> 
>> A new version of Tango is now available for download. The release is
>> named after Sean Kelly for his past work on the Tango runtime and now
>> druntime. The release have several new features, and fairly major changes
>> to tie the IO even closer together. To make the transition easier, the
>> previous incarnation is still available for this release.
>> 
>> This has been a much delayed release compared to the earlier Tango
>> releases, but time has been spent fairly well, covering 301 closed
>> tickets and more than 600 commits.
>> 
>>  * Final refinement of the IO
>>  * JSON parser/builder
>>  * FTP adapter for the VFS by Lester L. Martin II
>>  * Serial port support by Robin Kreis
>>  * Inter-thread communication by Steven Schveighoffer
>>  * /dev/null support by Fawzi Mohamed
>>  * Random framework by same Fawzi
>>  * BigInt by Don Clugston
>>  * Updated for DMD 1.041, including Mac support
>>  * Support for LDC
>>  * OpenSolaris support by BlueZeniX
>>  * New API docs courtesy of Aziz and Moritz
>>  * More containers such as HashFile
>> 
>> For a complete list of changes please see the changelog. We welcome all
>> feedback and testing.
>> 
>> We're in the process of updating to new API docs as mentioned above, now generated by dil. You can see the docs for 0.99.8 at http://www.dsource.org/projects/tango/docs/0.99.8 or later download them from via the download pages.
>> 
>> We are always looking for new participants, so feel free to contact us via the page linked below. In particular, we are looking for someone to help drive the online presence via our Trac pages.
>> 
>> The Tango homepage can be found at http://www.dsource.org/projects/tango
>> 
>> Downloads: http://www.dsource.org/projects/tango/wiki/Download
>> 
>> See http://www.dsource.org/projects/tango/wiki/TopicInstallTango for more detailed installation instructions for your system.
>> 
>> Contact information at http://www.dsource.org/projects/tango/wiki/Contact
>> 
>> ------
>> 
>> Signed,
>> 
>> The Tango Team
>> 
> 
> That's great.
> 
> A few thoughts on the new documentation:
> 
> The new dil generated documentation is a little hard to read. There is no space after the documentation of an item and the text item. I also liked the old font better than the new. Now when the documentation for object.di is actually generated we could perhaps get some documentations for it.

The CSS and DDoc macro's are in SVN, I think most of what you mention can be fixed via that so feel free to suggest patches. A note on fonts; I think none are currently specified meaning that what you see are the browswer defaults.

> Other from that I really like the new documentation.

Me too :)

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource, #d.tango & #D: larsivi
Dancing the Tango

"Lars Ivar Igesund" <larsivar@igesund.net> wrote in message news:gqkpm7$2cip$1@digitalmars.com...
>
> The CSS and DDoc macro's are in SVN, I think most of what you mention can
> be
> fixed via that so feel free to suggest patches. A note on fonts; I think
> none are currently specified meaning that what you see are the browswer
> defaults.
>

The only font I have a problem with is the one used for the function signature. It looks like some sort of typewriter font and definitely isn't my browser's default. (Although I suppose it might be my default monospace font and just looks weird when scaled up and bolded...In fact, glancing at the HTML/CSS right now, I think that is the case.)

On 28.03.2009 17:57, Nick Sabalausky wrote:
> "Lars Ivar Igesund"<larsivar@igesund.net>  wrote in message
> news:gqkpm7$2cip$1@digitalmars.com...
>>
>>  The CSS and DDoc macro's are in SVN, I think most of what you mention can
>>  be
>>  fixed via that so feel free to suggest patches. A note on fonts; I think
>>  none are currently specified meaning that what you see are the browswer
>>  defaults.
>>
>
> The only font I have a problem with is the one used for the function
> signature. It looks like some sort of typewriter font and definitely isn't
> my browser's default. (Although I suppose it might be my default monospace
> font and just looks weird when scaled up and bolded...In fact, glancing at
> the HTML/CSS right now, I think that is the case.)
>
>

The test docs on the dil site look ok in my browser:

http://dil.googlecode.com/svn/doc/Tango_0.99.7/tango.text.xml.Document.html

Except for the font in the list box on the left side, which is a bit slow to read.

I'm on Windows using Firefox.

Lars Ivar Igesund wrote:

> Dear D community
> 
> ------
> 
> Signed,
> 
> The Tango Team

Thank you.

Trass3r schrieb:
> Steven Schveighoffer schrieb:
>> Because you haven't submitted a ticket for it yet ;)
>>
>> http://www.dsource.org/projects/tango/newticket
>>
> Good idea.
> 
> I also have a problem with non-ASCII characters.
> But I couldn't find out the cause yet :(
> 
> 
> [sendCommand] Sending command 'CWD Dreckschlüpper
> '
> [readResponse] Expected Response 250
> [readResponse] Actual Response 550
> [sendCommand] Sending command 'QUIT
> '
> [readResponse] Expected Response 221
> [readResponse] Actual Response 221
> tango.net.ftp.FtpClient.FtpException: 420 Goodbye.
> . "Dreckschlüpper" : no such file or directory.

Seems like the server sends the name encoded with utf-8.
But the tango code treats it as ANSI.

Lars Ivar Igesund wrote:
> Dear D community
> 
> ------
> 
> Signed,
> 
> The Tango Team
> 
(Also Jacob commented on the docs.)

I'll give some critique on the new dil-generated docs as well.

I'm looking at these two links: http://www.dsource.org/projects/tango/docs/0.99.8/ http://dil.googlecode.com/svn/doc/Tango_0.99.7/tango.text.xml.Document.html

I'm assuming the latter are an older version of dil/kandil?.

I was a bit annoyed by the API/Modules modality in the latter docs. It'd be nice if the "Modules" list became collapsible and put the API elements as children of each module.  It seems the newer(?) version of the docs is collapsible, but has yet to eliminate the modality.  The newer version is tolerable though since it doesn't just hijack the frame when I click on a module.  It made me have to navigate back to the "Modules" mode every time I wanted to go to a different module.  So yeah, forced modality here is a bad thing.  I'd prefer to just get rid of the modality entirely and merge it all into one collapsible index.

Also, it seems dil has yet to make types found in the documentation act as hyperlinks to their definitions or at least module of definition. This one is big for me.  I'm hoping it's been planned.

Other than that I like the new docs, and I like how progress is being made on more intelligent generated docs.  That I can at least click on things and see how they are defined in code is rather useful, especially given all the trickery D can play with its type system.  Good job!

- Chad

"torhu" <no@spam.invalid> wrote in message news:gqllhn$pfm$1@digitalmars.com...
> On 28.03.2009 17:57, Nick Sabalausky wrote:
>> "Lars Ivar Igesund"<larsivar@igesund.net>  wrote in message news:gqkpm7$2cip$1@digitalmars.com...
>>>
>>>  The CSS and DDoc macro's are in SVN, I think most of what you mention
>>> can
>>>  be
>>>  fixed via that so feel free to suggest patches. A note on fonts; I
>>> think
>>>  none are currently specified meaning that what you see are the browswer
>>>  defaults.
>>>
>>
>> The only font I have a problem with is the one used for the function
>> signature. It looks like some sort of typewriter font and definitely
>> isn't
>> my browser's default. (Although I suppose it might be my default
>> monospace
>> font and just looks weird when scaled up and bolded...In fact, glancing
>> at
>> the HTML/CSS right now, I think that is the case.)
>>
>>
>
> The test docs on the dil site look ok in my browser:
>
> http://dil.googlecode.com/svn/doc/Tango_0.99.7/tango.text.xml.Document.html
>
> Except for the font in the list box on the left side, which is a bit slow to read.
>
> I'm on Windows using Firefox.

Also Windows/Firefox here (FF2 - yes, deliberately not FF3...don't get me started...), and I agree with your opinion on that link you provided. But with the additional issue that the nav box on the left doesn't show up when I have JS turned off...that's not a good thing.

Chad J wrote:

> Lars Ivar Igesund wrote:
>> Dear D community
>> 
>> ------
>> 
>> Signed,
>> 
>> The Tango Team
>> 
> (Also Jacob commented on the docs.)
> 
> I'll give some critique on the new dil-generated docs as well.
> 
> I'm looking at these two links: http://www.dsource.org/projects/tango/docs/0.99.8/
> 
http://dil.googlecode.com/svn/doc/Tango_0.99.7/tango.text.xml.Document.html
> 
> I'm assuming the latter are an older version of dil/kandil?.

I think so yes (at least a few patches difference).

> I was a bit annoyed by the API/Modules modality in the latter docs. It'd be nice if the "Modules" list became collapsible and put the API elements as children of each module.  It seems the newer(?) version of the docs is collapsible, but has yet to eliminate the modality.  The newer version is tolerable though since it doesn't just hijack the frame when I click on a module.  It made me have to navigate back to the "Modules" mode every time I wanted to go to a different module.  So yeah, forced modality here is a bad thing.  I'd prefer to just get rid of the modality entirely and merge it all into one collapsible index.

Not sure it is feasible to put _all_ public Tango symbols in the same tree, JS performance seems to very quickly become a potential issue. In that case the modality is a very acceptable workaround IMO. Feel free to work with Aziz on it though. Or create ticket(s).

> Also, it seems dil has yet to make types found in the documentation act as hyperlinks to their definitions or at least module of definition. This one is big for me.  I'm hoping it's been planned.

Not sure what you mean here -if you mean that a return type should link to the docs of that type, then yes, that is something that we very much want but that requires more semantic processing than dil currently has.

> Other than that I like the new docs, and I like how progress is being made on more intelligent generated docs.  That I can at least click on things and see how they are defined in code is rather useful, especially given all the trickery D can play with its type system.  Good job!
> 
> - Chad

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource, #d.tango & #D: larsivi
Dancing the Tango