From clmf8 at yahoo.com Thu Nov 6 12:26:21 2003 From: clmf8 at yahoo.com (Sam Feltus) Date: Mon Aug 2 21:28:36 2004 Subject: [Classiccity-pm] Flash_Djinni.pm Message-ID: <20031106182621.97704.qmail@web12505.mail.yahoo.com> Here is a rough draft for Flash_Djinni.pm. http://henryjamesfeltus.com/expensive_gypsy/Flash_Djinni.htm Right now it 1. Compiles a FLA file to a SWF movie file... Flash_Djinni::compile_swf 2. Displays a JPG, woohoo, got a video signal... Flash_Djinni::display_jpg 3. Creates an MP3 soundtrack, woohoo, audio too... Flash_Djinni::generate_soundtrack Next step is too automate XML interface and add some useful Audio Video Widgets Sam the Gardener Any comments, corrections or suggestions would be GREATLY appreciated. --------------------------------- Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.pm.org/pipermail/classiccity-pm/attachments/20031106/e16ad963/attachment.htm From darrell at golliher.net Fri Nov 7 14:27:34 2003 From: darrell at golliher.net (Darrell Golliher) Date: Mon Aug 2 21:28:36 2004 Subject: [Classiccity-pm] Re: Classiccity-pm Digest, Vol 4, Issue 6 In-Reply-To: <20031031150121.68620.qmail@web12506.mail.yahoo.com> References: <200310301800.h9UI0gW15651@mail.pm.org> <20031031150121.68620.qmail@web12506.mail.yahoo.com> Message-ID: <20031107202734.GA16130@golliher.net> On Fri, Oct 31, 2003 at 07:01:21AM -0800, Sam Feltus wrote: > 3. Darrell, my web host has all sorts of Perl stuff but not Mason, what was the name of the Web Hosting company that supported Mason??? > > Sam the Gardener Sorry I've been slow to respond. linode.com is who I use. They don't "support Mason", but they do give you complete root access to a virual server where you can setup Mason for yourself. That even better in my book. -Darrell From darrell at golliher.net Fri Nov 7 14:31:43 2003 From: darrell at golliher.net (Darrell Golliher) Date: Mon Aug 2 21:28:36 2004 Subject: [Classiccity-pm] perl, procmail and early closed pipes.. Message-ID: <20031107203143.GB16130@golliher.net> Hi Gang, I have this procmail recipie: # # If the previous rule caused the X-Spam-Status header to be yes, then the # message must have scored a 10 or higher so we rewrite the subject # to indicate a high SA score. # :0fw * ^X-Spam-Status: Yes | perl -ne '$search = quotemeta("*****SPAM*****"); s/$search/*****UBERSPAM*****/o;print;' and occasionally I get errors like so.. procmail: Error while writing to " perl -ne '$search = quotemeta("*****SPAM*****"); s/$search/*****UBERSPAM*****/o;print;'" The procmail manpage mentions the i condition: i Ignore any write errors on this recipe (i.e., usually due to an early closed pipe). Which makes me thing the problem with with the little bit of perl. Does anybody see why perl would be closing the pipe early in this case? I'd like to find the problem with the perl code and fix it rather than use the i condition (if at all possible). -Darrell From pkeck at uga.edu Sun Nov 16 00:55:29 2003 From: pkeck at uga.edu (Paul Keck) Date: Mon Aug 2 21:28:36 2004 Subject: [Classiccity-pm] basic idiot question In-Reply-To: <5.2.1.1.0.20031030210228.02598520@email.uga.edu> References: <5.2.1.1.0.20031025203519.00b91590@email.uga.edu> <5.2.1.1.0.20031025142502.01fe5170@email.uga.edu> <5.2.1.1.0.20031024204825.02123ea8@email.uga.edu> <5.2.1.1.0.20031024131930.01aeaeb8@pop.charter.net> <5.2.1.1.0.20031024204825.02123ea8@email.uga.edu> <5.2.1.1.0.20031025142502.01fe5170@email.uga.edu> <5.2.1.1.0.20031025203519.00b91590@email.uga.edu> <5.2.1.1.0.20031030210228.02598520@email.uga.edu> Message-ID: <20031116065529.GE25984@uga.edu> On Thu, Oct 30, 2003 at 11:05:01PM -0700, Jeff Scarbrough wrote: > The final program is listed at > http://www.fishplate.org/perl/data_prep.txt if you want to see how I made > it work. I'd be interested in any critiques you folks can provide, as this > is not just a job, but also a learning experience...I'm curious to see if > there is a better solution. It's been longer than I intended, but I do have a few comments. ========== 1. You might find it easier to pass in the filename arguments on the command line rather than prompting for them, a la: ./data_prep.pl file1 file2 You access these arguments through the @ARGV array, which is populated for you automagically. So then you could say $fileroot_1 = shift @ARGV; #shifts one element off @ARGV and sticks it in there open(INFILE, "$fileroot_1" . ".prn"); @array_1 = ; close INFILE; and then do it again for the next file. In fact, I'd probably force them to type the whole name of each file instead of tacking on .prn for them. When you write this to handle abitrary numbers of files, and you have a directory with just these files in it, they could type ./data_prep.pl * or, if there's other junk mixed in with the .prn files, ./data_prep.pl *.prn ========== 2. You have this line in there for each array processing loop: $_ =~ s/\\n//; # Strip carraiage return from line You could substitute chomp $_; or just chomp; #by default it chomps $_ Which will take off trailing newlines, if they are there. "chop" takes off the last char of the line, whether it's a newline or not. chomp is smarter. In fact, it's so smart you could, before your loop, do this: chomp @array_1; and it will do what you want- take off newlines from all the elements of @array_1, if they exist. =========== 3. I'm not sure of everything you're doing with the $doyday stuff, but you might get some benefit out of the Julian Day module from cpan.org: http://search.cpan.org/~muir/Time-modules-2003.0211/lib/Time/JulianDay.pm ========== 4. What kind of program is taking the output of this one? If it's one you're writing, it might be better to have a somewhat different output format, rather than having " , , , , , , , , , , , , , , " in there a bunch of times. The stuff I posted last time with the more complicated data structure and the Data::Dumper module comes to mind- if you can free yourself from the constriction of having all the data from a day on one line in a file, yet still tell which day it all came from, you could perhaps make it simpler. Or at least it makes it easier to handle multiple files without a bunch of hard-coded variables like @array_1 and @array_2. -- Paul Keck pkeck@uga.edu http://www.arches.uga.edu/~pkeck University of Georgia http://www.uga.edu/ucns/telecom EITS Network Engineering mailto:pkeck@ediacara.org --Opinions mine.-- Go fighting anomalocaridids!!!