Re: More Dconf 2015 videos
There have been a few responses agreeing with me. Chucks talk was awesome but the current edit doesn't do it justice. Is there any way this can be fed back to UVU/Chuck etc.? Did so. -- Andrei Cheers! A.
Re: More Dconf 2015 videos
On Friday, 26 June 2015 at 19:03:11 UTC, Andy Smith wrote: I don't want to sound negative but the editing of Chuck's talk could be a lot better IMHO. Round about 30:00 he describes a code example which isn't shown in the video!. He's making multiple references to lines/code etc. that were visible to the attendees at the conference but aren't visible on the video. Having seen it in person, Chuck's talk was a *great* advocacy of D. But seeing it second time round on youtube I'm not feeling it the same way :-( I appreciate the work that UVU have put in to making the talks available so I *really* don't mean to sound unappreciative or disrespectful, but I think in this case it might make sense to go back and revisit this particular talk. Specifically when Chuck is talking about a specific code sample / line of code, it needs to be put into the video. Otherwise context is completely lost and viewers will be left confused + bewildered. Regards, Andy. There have been a few responses agreeing with me. Chucks talk was awesome but the current edit doesn't do it justice. Is there any way this can be fed back to UVU/Chuck etc.? Cheers, A
Re: More Dconf 2015 videos
On 6/27/15 6:37 AM, Andy Smith wrote: On Friday, 26 June 2015 at 19:03:11 UTC, Andy Smith wrote: I don't want to sound negative but the editing of Chuck's talk could be a lot better IMHO. Round about 30:00 he describes a code example which isn't shown in the video!. He's making multiple references to lines/code etc. that were visible to the attendees at the conference but aren't visible on the video. Having seen it in person, Chuck's talk was a *great* advocacy of D. But seeing it second time round on youtube I'm not feeling it the same way :-( I appreciate the work that UVU have put in to making the talks available so I *really* don't mean to sound unappreciative or disrespectful, but I think in this case it might make sense to go back and revisit this particular talk. Specifically when Chuck is talking about a specific code sample / line of code, it needs to be put into the video. Otherwise context is completely lost and viewers will be left confused + bewildered. Regards, Andy. There have been a few responses agreeing with me. Chucks talk was awesome but the current edit doesn't do it justice. Is there any way this can be fed back to UVU/Chuck etc.? Did so. -- Andrei
Re: More Dconf 2015 videos
On Saturday, 27 June 2015 at 13:59:11 UTC, Andrei Alexandrescu wrote: On 6/27/15 6:37 AM, Andy Smith wrote: There have been a few responses agreeing with me. Chucks talk was awesome but the current edit doesn't do it justice. Is there any way this can be fed back to UVU/Chuck etc.? Did so. -- Andrei While we are sending them feedback could they include the talk titles in the YouTube titles to make them easier to find. The editing overall has been great. I've been pleasantly surprised. I was kind of expecting a fixed camera thrown up by an undergrad for some extra credit. It's really great that the change in venue hasn't resulted in a drop in video quality.
gen-package-version v1.0.0
Update to gen-package-version:
https://github.com/Abscissa/gen-package-version
Automatically generate a D module with version and timestamp information
(detected from git or Mercurial/hg) every time your program or library
is built. You can also generate a DDOC macro file (using the --ddoc=dir
switch.) In-between builds will automatically have their own
VCS-generated version number, including the VCS commit hash.
Now, by default, gen-package-version will NOT re-generate the output
files if the only difference is the build timestamp. So it won't trigger
unnecessary rebuilds of your project.
Usage is easy. Pop this in your dub.json:
--
dependencies: {
gen-package-version: ~1.0.0
},
preGenerateCommands:
[dub run gen-package-version -- your.package.name --root=$PACKAGE_DIR
--src=path/to/src]
--
And then import:
--
import your.package.name.packageVersion;
writeln(My Cool Program , packageVersion);
writeln(Built on , packageTimestamp);
--
Full changelog:
https://github.com/Abscissa/gen-package-version/blob/master/CHANGELOG.md
New in this version:
- Change: The generated 'packageTimestamp' is changed from ISOExt format
to human readable. The ISOExt formatted version is now called
'packageTimestampISO'.
- Change: Value for '--module=' is no longer allowed to contain periods.
- Enhancement: Basic ability to be used as a library. See the README for
details.
- Enhancement: Add '-r|--root' to support projects in any directory, not
just the current directory.
- Enhancement: Minor improvements to '--verbose' and '--trace' outputs.
- Fixed: Don't update the version file (and thus trigger a project
rebuild) if the version file doesn't need updated. Bypass this check
with the new '--force' flag.
- Fixed: Don't rebuild gen-package-version if not needed.
- Fixed: Failure on Windows when target project is on a different drive
letter from current working directory.
Re: safeArg v0.9.6
Another small update: safeArg v0.9.6 https://github.com/Abscissa/safeArg/blob/master/CHANGELOG.md One change: - Enhancement: Add --verbose|-v to echo the generated command to stdout before running.
Scriptlike v0.9.0
New update to Scriptlike: A library to aid in writing script-like programs in D. Home: https://github.com/Abscissa/scriptlike API Reference: http://semitwist.com/scriptlike Dub: http://code.dlang.org/packages/scriptlike Full changelog: http://semitwist.com/scriptlike/changelog.html --- In this version: - Change: Split scriptlike.file and scriptlike.path into the following: - scriptlike.core - scriptlike.file.extras - scriptlike.file.wrappers - scriptlike.path.extras - scriptlike.path.wrappers Utilizes package.d to retain ability to import scriptlike.file and scriptlike.path. - Change: Convert changelog from markdown to ddox so links are more readable. - Enhancement: Add (opt-in) command echoing to most functions in scriptlike.file. - Enhancement: Add yap and yapFunc as improved versions of to-be-deprecated echoCommand. - Fixed: Make escapeShellArg const-correct. - Fixed: Make Path.toRawString and Ext.toRawString both be pure @safe nothrow.
Scriptlike v0.9.1
On 06/28/2015 12:36 AM, Nick Sabalausky wrote: New update to Scriptlike: A library to aid in writing script-like programs in D. Home: https://github.com/Abscissa/scriptlike Scriptlike v0.9.1: - Fixed: Fails to compile unless the makedocs script has been run.
