I found a really nice video lecture on JavaScript. I’m a JavaScript journeyman myself so I decided to review it to learn something new. I have written about JavaScript in the past — the previous post on JavaScript was “Learning JavaScript through Video Lectures“.
If you work with version control systems like subversion (svn) I'm sure you can relate to the problem of having test files show up when you try to commit changes. It is actually pretty simple to tell subversion ignore directories or specific files.
You can do this by editing the svn property called svn:ignore as follows:
svn propedit svn:ignore ./some_path
When you run that command svn will open your text editor, and this is where you can define patterns or specific files to ignore. If you place a * in the property file, it will ignore all files in the directory you specified ./some_path
Codesign error: no certificate for identifier "iPhone Developer" was found in your keychain august
Btw, first thing is to show the "build transcript" -- it's the little icon to the right of the yellow exclamation point ("Show or hide existing warnings"). It shows exactly what xcode is running and what those apps are returning. I think xcode's error message parsing / display is buggy -- /usr/bin/codesign was reporting the full identity I was trying to use: "iPhone Developer: MyFirstName MyLastName", I don't know why xcode kept saying only "iPhone Developer". The xcode Code Signing Build properties ui is also buggy, lots of reports of having to restart, clear fields. Remember "Target" build settings override project settings.
Anyway, as mentioned in the message below, turning Off "CRL checking" (in Keychain Access > Preferences > Certificates) fixed the codesign "iPhone Developer" error. When I next clicked Build and Go in xcode, I was asked to login to my keychain (or something like that) and then the app was transferred to my iphone
http://lists.apple.com/archives/Apple-cdsa/2008/Jul/msg00010.html
Perian is a free, open source QuickTime component that adds native support for many popular video formats.
Perian enables QuickTime application support for additional media:
- File formats: AVI, DIVX, FLV, MKV, GVI, VP6, and VFW
- Video types: MS-MPEG4 v1 & v2, DivX, 3ivx, H.264, Sorenson H.263, FLV/Sorenson Spark, FSV1, VP6, H263i, VP3, HuffYUV, FFVHuff, MPEG1 & MPEG2 Video, Fraps, Snow, NuppelVideo, Techsmith Screen Capture, DosBox Capture
- Audio types: Windows Media Audio v1 & v2, Flash ADPCM, Xiph Vorbis (in Matroska), and MPEG Layer I & II Audio, True Audio, DTS Coherent Acoustics, Nellymoser ASAO
- AVI support for: AAC, AC3 Audio, H.264, MPEG4, and VBR MP3
- Subtitle support for SSA/ASS and SRT
While the Visual Studio build process is familiar for all .NET developers, not everyone realizes the build customization capabilities that can be accomplished with just a little work. You can easily put together tasks that occur before, after, and even during a build.
This article describes how a computer can play the classic video game Tetris by getting information about the board, determining good actions, and performing those actions.
This article includes software capable of playing Tetris in real time.
The software includes the best real-time Tetris-playing algorithm in the public domain.
AWK Tutorial, Learn AWK
The awk utility interprets a programming language that makes it possible to handle simple data-reformatting jobs easily with just a few lines of code.
SED Tutorial
* The sed utility is an "editor"
* It is also noninteractive. This means you have to insert commands to be executed on the data at the command line or in a script to be processed.
* sed accepts a series of commands and executes them on a file (or set of files).
* sed fittingly stands for stream editor.
* It can be used to change all occurrences of "SAD" to "SED" or "New York" to "Newport."
* The stream editor is ideally suited to performing repetitive edits that would take considerable time if done manually.
This tutorial should enable you to install ffmpeg and the auxiliary libraries that will give ffmpeg support for various codecs. It'll then go on to explain the basics of what a video file is, how it's created by ffmpeg and how a media player takes it apart again to display the picture and give you the sound. Next, you'll find out how to influence the way the data is produced. Finally, I'll deal with more advanced topics such as merging several sources and introducing time differentials.
ffmpeg is a versatile video tool used to encode and convert a multitude of video and audio formats. x264 is a library used to encode H264 video and creates excellent looking video usually superior to xvid and other popular codecs. x264 is used by Avidemux, GordianKnot, VLC Player, MEncoder, and Handbrake.
Although ffmpeg and x264 are available in the Ubuntu repositories, you may need to compile from source. For example, the ffmpeg-user mailing list requires that you use the latest ffmpeg svn before asking for help. Since ffmpeg and x264 are updated frequently, you may also like to have the bleeding-edge for encoding videos. Also, ffmpeg in the Ubuntu repository may not support all of the codecs and formats that you may need.
This tutorial was tested on a command-line install of Ubuntu Hardy Heron (8.04) on a Pentium 4 3.0 GHz with 2 GB RAM using ffmpeg and x264 source files retrieved on May 7, 08. It was also tested in a standard Hardy Heron installation in VirtualBox.
Pidgin (earlier Gaim) is a multiple protocol Instant Messenger client which can be used to chat using MSN, Yahoo, AIM and many other protocols. But most people do not know that you can use Pidgin to chat with Google Talk users.
Pidgin supports a protocol called XMPP (Extensible Messaging and Presence Protocol). XMPP is the core protocol of the Jabber protocol and GTalk is also based on the Jabber protocol. So it is quite easy to make Pidgin to work with GTalk.
rcconf is Debian runlevel configuration tool. Rcconf allows you to control which services are started when the system boots up or reboots. It displays a menu of all the services which could be started at boot. The ones that are configured to do so are marked and you can toggle individual services on and off. If rcconf is not installed use apt-get command:
# apt-get install rcconfOR$ sudo apt-get install rcconf Now run rcconf and just follow on screen instructions:
# rcconf
Optimize what you need to (and only what you need to), profile find out what that is (it may be slow, but profiling is your friend), and use the right tools (rewriting a bit of code with RubyInline is way better than rewriting the whole app in C).
The top two concerns are usually performance and scalability: "Ruby is slow" or "Interpreted languages are slow" seem to be the most common. Here are some excellent articles on the subject (the overall summary being: Rails provides a great advantage in getting your product to market, there are reasonable and inexpensive ways of addressing any performance bottlenecks, and scalability is not a problem):
the cost per request is plummeting, but the cost of programming is not. Thus, we have to find ways to trade efficiency in the runtime for efficiency in the “thought time” in order to make the development of applications cheaper. I believed we’ve long since entered an age where simplicity of development and maintenance is where the real value lies.
You should refer to ITU-T H.264 standard
From the document
Baseline profile: profile_id 66 = 0x42
Main profile: profile_id 77 = 0x4D
Extended profile: profile_id 88 = 0x58
