Showing posts with label publishing. Show all posts
Showing posts with label publishing. Show all posts

Wednesday, March 11, 2009

"Interference" seems like an appropriate name

I got a request from a marketer that I link to his product from this blog:From him:
Inference is a Microsoft Office add-in that has a point-and-click interface for adding MATLAB code, .m files, and structured data to Word and Excel documents. If you use Microsoft Office, Inference is an alternative to EX Builder and Notebook for generating reports, reproducible research, and Office applications. And regardless of whether you use Office, Inference has an integrated development environment (Inference Studio) with an intelligent editor that features breakpoints and edit-and-continue.
I have no idea why you would possibly need such a thing. I view software like this as predatory—it preys on people who think they're helpless. They end up overlooking existing easy solutions (like using the debugging features of MATLAB's own editor) and get distracted from finding truly good solutions.

Perhaps I'm being a little too harsh. Interference's own website gives a better description of its features:
Inference for MATLAB allows you to:
  • Execute MATLAB code directly inside of Microsoft Word to create formatted reports that contain explanatory text and graphical/code output.
  • Execute MATLAB code directly inside of Microsoft Excel to create dynamic spreadsheets that leverage existing Excel functionality.
  • Store all of your MATLAB code, data, and M-Files inside a single Microsoft Word and Excel document.
If you have use for such a thing... Give it a whirl, but don't come to me for help.

(by the way, my LaTeX build environment does the equivalent of "Interference for MATLAB" for LaTeX users. Among other things, if you \includegraphics{image_name} and the build environment finds an image_name.m file, it will automatically generate an image_name.eps (or image_name.pdf) whenever the MATLAB script gets updated)

Sunday, July 22, 2007

Copyright Explained

"Copyright Explained: I May Copy It, Right?" from Smashing Magazine
With blogging comes great responsibilty. You define the content of your weblog and you carry the full responsibility for every word you’ve published online. More than that, you are responsible for comments in your posts. To make sure you fulfill your legal obligations, it’s important to know, what you, as blogger, may or should do; and you have to know, how to achieve this. After all, the ignorance of the law does not make one exempt from compliance thereof.

This article explains copyright and how it applies to electronic material. Sure, it's focussed at bloggers, but anyone who is starting a career that involves publishing might be interested in this.

Monday, May 28, 2007

powerdot clock fix

UPDATE: Soon after the posting of this, Hendri posted this patch (by Heiko Oberdiek) which is nothing but a more compact refactoring of the code below.

As of May 2007, the clock feature of the powerdot presentation class for LaTeX has not been working. I think that I have a good patch. I have sent this patch to Hendri Adriaens, powerdot's author of record, who has added verification of it to his todo list.

First, update to the latest versions of hyperref, oberdiek, and xcolor. These packages have been updated very recently, and so you must not take for granted that you have the latest versions.

Next, if you have the
[2005/12/06 v1.3 powerdot presentation class (HA,CE)]
version of powerdot, you can simply replace your powerdot.cls file with this one, which is linked here for easy viewing.

Alternatively (this may work with newer versions of powerdot too), patch your version of powerdot with this patch which is shown below.
--- powerdot.orig/powerdot.cls 2007-05-28 00:38:50.000000000 -0400
+++ powerdot/powerdot.cls 2007-05-28 10:24:52.000000000 -0400
@@ -65,7 +65,7 @@
\AtBeginDocument{%
\@Form[]%
\ifnum\pd@orient=\z@
- \def\pd@clockrot{] /R 90\@gobble}%
+ \def\pd@clockrot{90}%
\else
\let\pd@clockrot\@empty
\fi
@@ -579,7 +579,8 @@
\edef\pd@tempa{\expandafter\pd@tempa\pd@tempb\@nil}%
\ifx\pd@@clockpos\@empty\else
\rput[\pd@@clockhook](\pd@@clockpos){%
- \TextField[name=pdclock.time,bordercolor=\pd@clockrot,%
+ \TextField[name=pdclock.time,%
+ bordercolor=,rotation=\pd@clockrot,%
backgroundcolor={},align=\pd@@clockalign,color=\pd@tempa,%
charsize=\pd@@clockcharsize,width=\pd@@clockwidth,%
height=\pd@@clockheight]{}%
If you use this patch method, invoking
patch -p1 < powerdot-clockfix.patch
in the directory that holds powerdot.cls should be sufficient, assuming that the patch file is also in that directory.