Re: Packt is looking for someone to author a Learning D
On Sun, 2015-02-15 at 04:38 +, Craig Dillabaugh via Digitalmars-d-announce wrote: […] Well, if you do the document with Latex on git (or some similar version control), you get most of the same stuff. Latex has a comment tool where you can do margin comments if you wish, and of course you can also do comments in the 'code' if you want - they don't show up in the document at all. Heck, I am sure there is a package for everything in Latex if you look hard enough. (Xe|Lua)LaTeX or AsciiDoc Git or Mercurial or Bazaar Publishers have, however, seemed to have decided that sub-editors must work on the original source document files directly. If this is an integral part of the publisher workflow and the sub-editors cannot deal with DVCS or the markup languages, then the publishers refuse to use those tools. Still as long as some half-way decent authors are prepared to use Word and abdicate their responsibility for the content once initially created, the publishers win. A MS-word document with 'track changes' on, edited by multiple people, is the greatest eyesore known to humanity. I still don't understand why anyone who had a choice between Latex and MS-Word would pick MS-Word for anything longer than 25 pages... And who has the current master version, which file is the master, etc., etc. Just my personal opinion as one who recently finished a 200 page thesis in Latex, and is now working for a company where we do all our internal documents in Word. Latex certainly has its ugly warts, but it is so nice for lengthy document1. Luxury. I typed my thesis (including the maths equations) using a broken portable manual typewriter. ;-) -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Re: Calypso: Direct and full interfacing to C++
Alirighty, Calypso builds and runs on both Linux and Win64 with that last change from today in my fork. Now when I say 'runs' on Linux, I mean it runs properly and fully (compiling and running all examples from Feb 8th)...but when I say 'runs' on Win64, I should say 'runs as far as it can' because there is an internal LLVM assert with getVTableContext Microsoft VTableContext not yet supported UGH! :( Well...that is a stopper on Win64, period. I imagine this will be addressed fairly quickly because LLVM is moving extremely fast on Win64...at least I hope that will be the case!! So that leaves us with Calypso up to the last commit on February 8th, LDC from yesterday (Feb 14th) and with LLVM-3.7/Clang using the revision hashes above. I will make sure all this builds and works on OS X now...wish me luck :) I will also try to pull in the latest Calypso commits from the last couple days, and merge it with LDC so that we are all up to date and synced with LDC from yesterday. Unfortunately we are stuck with bleeding edge on all this stuff, (even when LLVM-3.6 stable comes out next week) because most of the Win64 code in LLVM and LDC has been added in just the last few weeks. Anyways, hopefully you can just spend time on the internal Calypso stuff this way Elie, and not waste time poking around with the Win64 build right now. Thanks, Kelly
Re: Packt is looking for someone to author a Learning D
On Sat, 2015-02-14 at 10:21 -0800, Andrei Alexandrescu via Digitalmars-d-announce wrote: […] Many publishers may allow you to provide camera-ready copies. Sadly not. The big publishers (well the three I have had dealing with in the last 5 years) feel they have this need to keep all their design and typesetting staff employed and so enforce the authors write with Word and then we do all the page design, typesetting, etc., etc., author do not need to worry themselves over the presentation of their content, we do that. The words arrogant and condescending spring to mind. Also the one sub-editor in the UK who was prepared to work with LaTeX source retired. All the others will only work with Word. Which of course ruins the workflow with anyone using LibreOffice. Which I don't except for presentation slides. Any suggestion of DocBook/XML as authored source is generally met with derision, especially given there is AsciiDoc. You'd be surprised to hear the tooling at the Pragmatic Programmer is all XML based and quite inflexible. Our negotiations broke down over that, in spite of their really beefy financial offering. Hence my comment about AsciiDoc. O'Reilly and Pragmatic Programmers seemed to have Git and DocBook/XML sorted, but then totally forgot about author usability. AsciiDoc fixes that by being a reasonable markup language that feeds into the DocBook/XML toolchain. So if I am not allowed to use XeLaTeX for authoring, my only option is AsciiDoc. If that is not acceptable, I don't write books. I have to admit, doing a Go or D book, is kind of appealing. Technically I am supposed to be doing Python for Rookies, 2e but it isn't happening for reasons I would rather not let the NSA know about. Go? Urgh. As they say: Come for the concurrency, leave for everything else :o). I think you severely mis-quote John Graham-Cummins there. But I suspect by design. Go is gaining massive traction. I need income. Go is where the income is. And anyway, I like Go. OK So I also like Groovy, Kotlin, Ceylon, and D. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Re: Packt is looking for someone to author a Learning D
On Sat, 2015-02-14 at 18:15 +, Vladimir Panteleev via Digitalmars-d-announce wrote: On Saturday, 14 February 2015 at 17:04:24 UTC, Russel Winder wrote: Obviously XeLaTeX is the correct medium, but AsciiDoc is acceptable as a second best. During the editing of the Russian translation of TDPL, I've worked in MS Word as well. Probably its main advantage is its collaboration tools: you can see who added or deleted which parts, and toggle between visible edits and final text easily. You can also add comments to a text range; by passing the document along, this made possible even short conversations. What would be the equivalent of such collaboration in a non-MS-Word- based workflow? Git, Mercurial, Bazaar, … -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Re: Calypso: Direct and full interfacing to C++
On Sunday, 15 February 2015 at 11:48:50 UTC, Kelly wrote: Alirighty, Calypso builds and runs on both Linux and Win64 with that last change from today in my fork. Now when I say 'runs' on Linux, I mean it runs properly and fully (compiling and running all examples from Feb 8th)...but when I say 'runs' on Win64, I should say 'runs as far as it can' because there is an internal LLVM assert with getVTableContext Microsoft VTableContext not yet supported UGH! :( It's from Calypso actually, the assert is in gen/dcxxclasses.cpp and is only triggered by D classes inheriting from C++ classes with a vtable. If the rest works as usual on Linux you got the most important covered. I'll check your merge as soon as I'm done fixing a linking error with the std::string example the latest additions introduced, then I'll add the Microsoft VTableContext support so we could get those first working binaries for Windows users :) However LLVM and Clang 3.6 aren't even released yet (next week), IMHO it would be wiser to stick with 3.6 and get LDC/Calypso working with 3.6 until 3.7 is more stable. Did you mean that even LDC can't be built by MSVC with LLVM 3.6 atm?
Re: Calypso: Direct and full interfacing to C++
On Sunday, 15 February 2015 at 14:03:22 UTC, Elie Morisse wrote: It's from Calypso actually, the assert is in gen/dcxxclasses.cpp and is only triggered by D classes inheriting from C++ classes with a vtable. Ah, sorry I see it now...there is the assert and then a backtrace that indicates that an llvm file had the assert, but the actual error does print from within dxxclasses.cpp before the assert code backtrace. If the rest works as usual on Linux you got the most important covered. I'll check your merge as soon as I'm done fixing a linking error with the std::string example the latest additions introduced, then I'll add the Microsoft VTableContext support so we could get those first working binaries for Windows users :) Ok, cool. Hopefully that is the only difficulty left. However LLVM and Clang 3.6 aren't even released yet (next week), IMHO it would be wiser to stick with 3.6 and get LDC/Calypso working with 3.6 until 3.7 is more stable. Did you mean that even LDC can't be built by MSVC with LLVM 3.6 atm? Actually, I am not totally sure whether the current LDC will build with 3.6 on Win64. I didn't want to try it until 3.6 is finalized because building takes forever on Windoze!!! Probably 10 times slower than Linux/OSX...and my Win7 machine is a dual quad-core i7 with 12GB RAM!! A much better machine than my Linux machines. Anyways, once 3.6 final comes out we'll have to see if it works, I guess. Thanks, Kelly
Re: Packt is looking for someone to author a Learning D
On Sunday, 15 February 2015 at 11:36:22 UTC, Russel Winder wrote: On Sun, 2015-02-15 at 04:38 +, Craig Dillabaugh via Digitalmars-d-announce wrote: […] Well, if you do the document with Latex on git (or some similar version control), you get most of the same stuff. Latex has a comment tool where you can do margin comments if you wish, and of course you can also do comments in the 'code' if you want - they don't show up in the document at all. Heck, I am sure there is a package for everything in Latex if you look hard enough. (Xe|Lua)LaTeX or AsciiDoc Git or Mercurial or Bazaar Publishers have, however, seemed to have decided that sub-editors must work on the original source document files directly. If this is an integral part of the publisher workflow and the sub-editors cannot deal with DVCS or the markup languages, then the publishers refuse to use those tools. Still as long as some half-way decent authors are prepared to use Word and abdicate their responsibility for the content once initially created, the publishers win. A MS-word document with 'track changes' on, edited by multiple people, is the greatest eyesore known to humanity. I still don't understand why anyone who had a choice between Latex and MS-Word would pick MS-Word for anything longer than 25 pages... And who has the current master version, which file is the master, etc., etc. Just my personal opinion as one who recently finished a 200 page thesis in Latex, and is now working for a company where we do all our internal documents in Word. Latex certainly has its ugly warts, but it is so nice for lengthy document1. Luxury. I typed my thesis (including the maths equations) using a broken portable manual typewriter. ;-) And you tell new students these days, and they won't believe you :o) One other nice thing about LateX is that since you prepare your content in a text editor, it lets you focus on your content and not be distracted by fiddling with formatting as you go! In theory you should do the same in MS-Word, but its sometimes hard to focus with all the pretty buttons :o) Of course, TeX is also a programming language, so for developer types it does present its own distraction. Luckly TeX coding is so obtuse it is never a serious temptation.
Re: Packt is looking for someone to author a Learning D
On Sun, 2015-02-15 at 15:37 +, Craig Dillabaugh via Digitalmars-d-announce wrote: On Sunday, 15 February 2015 at 11:36:22 UTC, Russel Winder wrote: […] Luxury. I typed my thesis (including the maths equations) using a broken portable manual typewriter. ;-) And you tell new students these days, and they won't believe you :o) There is one wonderful upside to this story, the examiners appreciated the complexity associated with changing anything, that they took considerable effort to find the minimum changes necessary that could be done with Snopake and a pen. […] Of course, TeX is also a programming language, so for developer types it does present its own distraction. Luckly TeX coding is so obtuse it is never a serious temptation. Uuuurrr… like m4, once you get into it it isn't so bad. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Re: DDocs.org: auto-generated documentation for all DUB projects (WIP)
On Thursday, 12 February 2015 at 15:27:14 UTC, Andrej Mitrovic wrote: On 2/10/15, Kiith-Sa via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: DDocs.org (http://ddocs.org) It would be nice to be able to jump to the project's hosted repository in the docs page (maybe generate a github icon with a link somewhere?) E.g. I'm here: http://ddocs.org/bloom/latest/dawg/bloom.html But want to get the link to the github repository. I'd have to go to the homepage and search for the package. Good idea, added the feature.
Re: Tkd - Cross platform GUI toolkit based on Tcl/Tk
On Saturday, 7 February 2015 at 02:00:32 UTC, Jack wrote: I've been using this for learning experience and tried to use .jpg for the Image Object in vain. Are there plans to include jpg support here? Or is there a workaround for that? or can I use other image libraries to embed it to a Label Object or Button Object? Tcl/Tk only currently supports *.ppm, *.pgm, *.png and *.gif. PPM/PGM formats were deemed to obscure to support in Tkd.
Re: Packt is looking for someone to author a Learning D
On 15 February 2015 at 17:56, Russel Winder via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On Sun, 2015-02-15 at 15:37 +, Craig Dillabaugh via Digitalmars-d-announce wrote: On Sunday, 15 February 2015 at 11:36:22 UTC, Russel Winder wrote: […] Luxury. I typed my thesis (including the maths equations) using a broken portable manual typewriter. ;-) And you tell new students these days, and they won't believe you :o) There is one wonderful upside to this story, the examiners appreciated the complexity associated with changing anything, that they took considerable effort to find the minimum changes necessary that could be done with Snopake and a pen. […] Of course, TeX is also a programming language, so for developer types it does present its own distraction. Luckly TeX coding is so obtuse it is never a serious temptation. Uuuurrr… like m4, once you get into it it isn't so bad. Hmm, yeah. Depends on the application use of m4 though. I've been at a company who used m4 to generate all their DNS zone files. In which you'd get high marks for having a way to add/remove records that was relatively low maintenance cost, but low marks for complexity of adding features/debugging bugs in the wiry maze of macros. :) Iain.
This Week in D - Issue 5
After my sick day last week, this rounds up two weeks of discussion. http://arsdnet.net/this-week-in-d/feb-15.html If someone else wants to post to reddit this time, I'd appreciate it.
Re: This Week in D - Issue 5
On Monday, 16 February 2015 at 03:43:48 UTC, Adam D. Ruppe wrote: On Monday, 16 February 2015 at 03:05:56 UTC, Brian Schott wrote: Typo: DCD was spelled as CD. oops fixed thx Aamodule was written for Walter's Sargon extension library. Should be A module?
Re: This Week in D - Issue 5
On Monday, 16 February 2015 at 03:05:56 UTC, Brian Schott wrote: Typo: DCD was spelled as CD. oops fixed thx
Re: This Week in D - Issue 5
On 2/15/15 11:12 PM, Andrei Alexandrescu wrote: On 2/15/15 6:32 PM, Adam D. Ruppe wrote: After my sick day last week, this rounds up two weeks of discussion. http://arsdnet.net/this-week-in-d/feb-15.html If someone else wants to post to reddit this time, I'd appreciate it. Nicely done. Thanks! -- Andrei Oh, could you please add that DConf has a call for submissions and an early bird discount through Feb 28? (We really need your talk proposals folks. No proposals means no conference.) Andrei
Re: This Week in D - Issue 5
On 2/15/15 6:32 PM, Adam D. Ruppe wrote: After my sick day last week, this rounds up two weeks of discussion. http://arsdnet.net/this-week-in-d/feb-15.html If someone else wants to post to reddit this time, I'd appreciate it. Nicely done. Thanks! -- Andrei
