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.) 

I've been annoyed with this in the past. These days, I let websites choose serif, sans serif, or monospace; but only I choose which fonts those map to. If your website asks for Helvetica or Arial, it's getting Cronos. If it asks for Times, it gets Chaparral. And so forth.

In Firefox, under the Content tab of the preferences window, look at the Fonts & Colors group and press Advanced. There is a checkbox that controls whether websites' preferences for fonts will be honored.

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
> 

Thanks to everyone on the team for your hard work!

Lars Ivar Igesund wrote:
> Chad J wrote:
> 
>> 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).
> 

Darn.  Well alright.

>> 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.
> 

OK, that's pretty much what I meant.  I hope we eventually get more than return type though: non-templated function args, class ancestors, etc. would be nice as well.

Christian Kamm wrote:

> Lars Kyllingstad Wrote:
>> Are there plans to release a Tango-LDC bundle any time soon?
> 
> Yes. There will be a new release of LDC that comes bundled with Tango 0.99.8.

Can you please give us a deadline for it (if there is of course) ? :)

-- 
Vincenzo Ampolo
http://goshawknest.wordpress.com/