vox populi vox dei

Marketing Technology behind $35 billion in holiday 2011 ecommerce sales

2012-01-07T14:43:00.000-08:00

Great article about Web Analytics

http://www.darrenherman.com/2011/12/30/marketing-technology-behind-35-billion-in-holiday-2011-ecommerce-sales/

Create Bootable USB Windows 7

2011-12-13T14:14:00.001-08:00

bootable USB guide, here we assume that you are using either Vista or Windows 7 to create a bootable USB.

1. Insert your USB (4GB+ preferable) stick to the system and backup all the data from the USB as we are going to format the USB to make it as bootable.

2. Open elevated Command Prompt. To do this, type in CMD in Start menu search field and hit Ctrl + Shift + Enter. Alternatively, navigate to Start > All programs >Accessories > right click on Command Prompt and select run as administrator.

3. When the Command Prompt opens, enter the following command:

DISKPART and hit enter.

LIST DISK and hit enter.

Once you enter the LIST DISK command, it will show the disk number of your USB drive. In the below image my USB drive disk no is Disk 1.

4. In this step you need to enter all the below commands one by one and hit enter. As these commands are self explanatory, you can easily guess what these commands do.

SELECT DISK 1 (Replace DISK 1 with your disk number)

CLEAN

CREATE PARTITION PRIMARY

SELECT PARTITION 1

ACTIVE

FORMAT FS=NTFS

(Format process may take few seconds)
ASSIGN

EXIT

Don’t close the command prompt as we need to execute one more command at the next step. Just minimize it.

5. Insert your Windows DVD in the optical drive and note down the drive letter of the optical drive and USB media. Here I use “D” as my optical (DVD) drive letter and “G” as my USB drive letter.

6. Go back to command prompt and execute the following commands:

6.1. Change directory to the DVD’s boot directory where bootsect lives:
d:
cd d:\boot

6.2. Use bootsect to set the USB as a bootable NTFS drive prepared for a Vista/7 image. I’m assuming that your USB flash drive has been labeled disk G:\ by the computer:
bootsect /nt60 g:

(Where “G” is your USB drive letter)

7. Copy Windows DVD contents to USB.

You are done with your bootable USB. You can now use this bootable USB as bootable DVD on any computer that comes with USB boot feature (most of the current motherboards support this feature).

Note that this bootable USB guide will not work if you are trying to make a bootable USB on XP computer.

Illusion

2011-11-13T13:01:00.000-08:00

If your brain works normally

This is another example of an amazing illusion!!! The last sentence is so true.

If your eyes follow the movement of the rotating pink dot, the dots will remain only one color, pink.

However if you stare at the black '+ ' in the center, the moving dot turns to green.
Now, concentrate on the black ' + ' in the center of the picture. After a short period, all the pink dots will slowly disappear, and you will see only a single green dot rotating.

It's amazing how our brain works. There really is no green dot, and the pink ones really don't disappear. This should be proof enough, we don't always see what we think we see.

Eclipse & Tomcat - Create a Webapp - Hello World Tutorial

2011-11-04T14:26:00.000-07:00

Untitled Document

Directory Structure under: C:\xampp\tomcat\bin\webapps\mytomcat-eclipse-helloworld-scratch

List of Directories:

\WEB-INF

\WEB-INF\lib

\WEB-INF\src

\WEB-INF\src\java

\WEB-INF\src\myeclipse

\WEB-INF\classes

\pages

List of files:

\index.jsp

\pages

\pages\myhelloworld_bean.jsp

\pages\myhelloworld_jstl.jsp

\WEB-INF\web.xml

\WEB-INF\lib\jstl.jar - copy this file.

\WEB-INF\lib\standard.jar - copy this file.

\WEB-INF\src\myeclipse\MyHelloWorldBean.java

\WEB-INF\src\myeclipse\MyHelloWorldServlet.java

1 Download and Install Eclipse
Eclipse IDE for Java Developers

2 Download and Install XAMPP to its default location

XAMPP comes really handy with

Apache 2.2.21

MySQL 5.5.16

PHP 5.3.8

phpMyAdmin 3.4.5

FileZilla FTP Server 0.9.39

Tomcat 7.0.21 (with mod_proxy_ajp as connector)

3 Download Eclipse Tomcat Launcher plugin

At the time of this article tomcatPluginV33.zip

Extract the archive tomcatPluginV33.zip under C:\eclipse\plugins this should create a sub folder com.sysdeo.eclipse.tomcat_3.3.0

4 Set JAVA_HOME to C:\Program Files\Java

5 Set JRE_HOME to C:\Program Files\Java\jre6

6 Let's get started

To give you the big picture, in the steps below, you will use Eclipse to
create the following directory structure and files.

This examples Tomcat "webapps" directory is located at:

C:\xampp\tomcat\bin\webapps

7 Eclipse - Create a Java Project

8 Launch Eclipse

9 Tomcat Plugin

The Sysdeo Tomcat Plugin is our best friend. After you have installed it, you will notice these buttons and menues in your IDE.

The left button starts Tomcat, the middle button stops it, the right button restarts Tomcat. Right now, they won't work if you press them. To enable them, you first need to configure a few things. Go to the menu "Window-> Preferences" there, you will see this dialogue box.

Configure Tomcat Plugin

Windows-->Preferences-->Tomcat

Now you need to go to the menu item "Tomcat" and select your Tomcat version. At the time of writing that would be the 7.x version. Now we adjust the field "Tomcat Home" to point to the install directory that we selected before at install time. The Sysdeo plugin now knows where to look for the server.xml file and automatically assumes the standard path to look for the file. Eclipse is now able to manage this configuration file, i.e. add a new <context> for a new application

Browse for tomcat home and select tomcat version

Click on JVM settings and add JVM Parameters

-Xmx2000M

-Xms1000M

-XX:MaxPermSize=128m

Now we are ready to test start our Tomcat server. Click on the start button in the Tomcat menu and watch the console output. If Tomcat boots up without any stacktraces open your browser, and try to open the following address http://localhost:8080/ . If you see an image

that is similar, to the one below everything is working okay

10 File, New, Project, Java Project, Next

11 Project Name: mytomcat-eclipse-helloworld-scratch

12 UnCheck - Use default location.

13 Click "Browse" and navigate to the Tomcat webapps"
directory (ex: C:\xampp\tomcat\bin\webapps\webapps).

14 This is a little tricky so follow closely. We want to create a
new directory.
- Note: The "webapps" directory should be selected.
- Click "Make New Folder"
- In the browse window list, you should be able replace the words "New
  Folder" with: mytomcat-eclipse-helloworld-scratch
  
  Note: If you can't, in the browse window scroll to the "New
  Folder" and right click, choose "Rename" and change the folder name to
  mytomcat-eclipse-helloworld-scratch
- Click "OK".
- Check the value of "Location:" to make sure you have selected the
  correct folder.
  
  Location should now show: C:\Tomcat\Tomcat6.0\webapps\mytomcat-eclipse-helloworld-scratch
- Click "Next" to go to the "Java Settings" screen.

15 Source Folder
- Click "Create new source folder".
  
  Folder name: WEB-INF/src
  
  Click "Finish"
- Right click on "src" and choose "Remove from Build Path".
  Later you will delete the folder.
  
  (Note: We just created the src file in a directory that web users
  can't directly get to: WEB-INF/src)

16 Output Folder
- Change the "Default output folder" to: mytomcat-eclipse-helloworld-scratch/WEB-INF/classes
  
  (Note: Currently the default will be:
  mytomcat-eclipse-helloworld-scratch/bin)

17 Click "Finish"

18 In the "Package Explorer" right click on "src" and choose delete.

19 Eclipse - Build Path - add the Tomcat lib jars files.

Right click on the project.

Click "Build Path", "Configure Build Path", then
click the tab "Libraries"

Check to see if "JRE System Library"
is listed. If not complete the next steps in this bullet.

Click "Add Library", "JRE System Library",
"Next", "Finish".

Note: Under the tab "Order and Export" this lib file should be directly
under the WEB-INF/src directory.

You can't compile .java files without this library!!!

Click "Add External JARs"

Browse to the Tomcat common library directory.

Ex: C:\xampp\tomcat\lib

Select all of the JAR files (Ctrl-A), then click "Open".

Click "OK" to leave the "Java Build Path" screen.

20 Create the "WEB-INF\lib" Folder

Right click on "WEB-INF", "New", "Folder".

Folder name: lib

Click "Finish"

Library files - for this project we will be using 2 .jar files:
standard.jar & jstl.jar.

These 2 jar files need to reside in: webapps\mytomcat-eclipse-helloworld\WEB-INF\lib
- mytomcat-eclipse-helloworld-scratch-lib.zip - download and extract this
  zip file into the new "lib" directory you just created.
  
  Note: If you downloaded the files in this tutorial you will have this
  file in the directory:
  
  Pathname: tomcat\tutorial_tomcat_eclipse\webapps\mytomcat-eclipse-helloworld-scratch-lib.zip
  
  (Note: These lib files came from the Apache JSTL project called
  "standard".)
- If you don't place the files properly in the lib directory you will get
  compile errors etc...

21 Create the "WEB-INF\src\myeclipse" Package

Right click on "WEB-INF/src" (not
"WEB-INF"), "New", "Package".
Folder name: myeclipse

Click "Finish"

22 Create the "pages" Folder

Right click on "mytomcat-eclipse-helloworld-scratch",
"New", "Folder". Folder name: pages

Click "Finish"

23 Create the "WEB-INF\web.xml" file.

Right click on "WEB-INF" (not "WEB-INF/src"), "New", "File".
File name: web.xml

web.xml -
copy this content into the file. Right click on the filename, open
with, Text Editor. If you open with the XML editor you can't copy and
paste. After you copy-n-paste, then open with "XML Editor".

Notice the 2 tags: <servlet> & <servlet-mapping>. This is planning
for the .java servlet file we will create.

24 Create the "index.jsp" file

Right click on "mytomcat-eclipse-helloworld-scratch", "New", "File".
File name: index.jsp

index.jsp -
copy this content into the file. (Warning:
If the server & browser doesn't show this file as a Text file then do a
view source so you can copy-n-paste.)

Note:
- This JSP has just HTML tags.

25 Create the "MyHelloWorldBean.java" Java source file.

Right click on "myeclipse"
under the directory "WEB-INF/src", "New", "Class".

Name: MyHelloWorldBean

Click "Finish"

MyHelloWorldBean.java -
copy this content into the file. (Warning:
If the server & browser doesn't show this file as a Text file then do a view
source so you can copy-n-paste.)

26 Create the "MyHelloWorldServlet.java" Java source file.

Right click on "myeclipse"
under the directory "WEB-INF/src", "New", "Class".

Name: MyHelloWorldServlet

Click "Finish"

MyHelloWorldServlet.java -
copy this content into the file. (Warning:
If the server & browser doesn't show this file as a Text file then do a view
source so you can copy-n-paste.)

27 Create the "myhelloworld_jstl.jsp" JSP file.

Right click on "pages", "New", "File".

File Name: myhelloworld_jstl.jsp

Click "Finish"

myhelloworld_jstl.jsp -
copy this content into the file. (Warning:
If the server & browser doesn't show this file as a Text file then do a view
source so you can copy-n-paste.)

28 Create the "myhelloworld_bean.jsp" JSP file.

Right click on "pages", "New", "File".

File Name: myhelloworld_bean.jsp

Click "Finish"

myhelloworld_bean.jsp -
copy this content into the file. (Warning:
If the server & browser doesn't show this file as a Text file then do a view
source so you can copy-n-paste.)

29 Reload the webapp or Stop Tomcat.

30Test your Web App

31 Start Tomcat and/or Reload this WebApp

32 Go to:
http://localhost:8080/mytomcat-eclipse-helloworld-scratch/pages/myhelloworld_jstl.jsp

Hello World (JSTL Example)

JSTL Example (c:out): Hello World

33 Go to: http://localhost:8080/mytomcat-eclipse-helloworld-scratch/pages/myhelloworld_bean.jsp

Hello World (JSP & Java Bean Example)

Bean Example MyHelloWorld.getStrMyMessage(): Hello World

34 Go to: http://localhost:8080/mytomcat-eclipse-helloworld-scratch/MyHelloWorldServlet

Hello World (Servlet Example)

Hello World

35 Optional - Change Text - Hello World

Using Eclipse, modify the following files then Reload the web app
or Stop/Start Tomcat.

filename: index.jsp

For the title & h1 tags change the following:

from:

mytomcat-eclipse-helloworld

to:

mytomcat-eclipse-helloworld-scratch

filename: WEB-INF\src\myeclipse\MyHelloWorldBean.java

from:

setStrMyMessage("Hello World");

to:

setStrMyMessage("Hello World - Hi");

filename: WEB-INF/src/myeclipse/MyHelloWorldServlet.java

from:

<p>Hello World</p>

to:

<p>Hello World - Hi</p>

filename: pages/myhelloworld_jstl.jsp

from:

<c:out
value="Hello
World"/>

to:

<c:out
value="Hello World
- Hi"/>

Reload Web App or Stop/Start Tomcat Service
(because you changed a .java file!) - see steps
above!

Test your Web App again

Matlab relative path issue in prj and MWArray.dll nightmare on Windows 7 64 bit

2011-11-03T13:44:00.000-07:00

Whenever you want to create a deployment project, you obviously would like to add it to source control repository for others to use..... But you will face a major issue...
The main problem is that the .prj file which deploytool creates contains absolute paths which will not work on other computers!. This is really bad to see that this is still the case in MatLab R2011a.... Really! So I decided to use Visual Studio 2005 vcproj file to maintain my deployment project because Visual Studio 2005 project support relative path pretty damn well! Thank you Microsoft Visual Studio Team!. I decided to create a WIN32 utility using MFC to convert the relative path to absolute path using the vcproj file and generate a Matlab PRJ file. In my case I am targetting C# .Net Assembly. Here is the source code!

#define _CRT_SECURE_NO_DEPRECATE
#include "stdafx.h"
#include "vcproj2matlabprj.h"
#include
#include
#include
#include
#include
#include "xmlParser.h"
#include "win32utility.h"

CString RelativePathToAbsolutePath(LPCTSTR contentRelativePath,LPCTSTR rootPath, BOOL &bRelativePathToParentFolders);

void PrintFileName(XMLNode xNode,LPCTSTR pszRootFolder);

FILE *_pOutMakeFile = NULL;

#if !defined (WIN32)
#define _strdup strdup
#endif

#ifdef _DEBUG
#define new DEBUG_NEW
#endif

// The one and only application object

CWinApp theApp;

using namespace std;

int _tmain(int argc, TCHAR* argv[], TCHAR* envp[])
{
int nRetCode = 0;

// initialize MFC and print and error on failure
if (!AfxWinInit(::GetModuleHandle(NULL), NULL, ::GetCommandLine(), 0))
{
// TODO: change error code to suit your needs
_tprintf(_T("Fatal Error: MFC initialization failed\n"));
nRetCode = 1;
}
else
{
CString strRootFolder;
CString strVCProjShortFilename;
CString csPath;
CString csFilenameNoExt;
CString csExtension;
CString strVCProj;
CString strMathlabProj;
CString strMathLabRootPath;
CString strClassName;
CString strNamespace;

if ( argc < 4 )
{
printf("Usage: %s [MathLab 2011a RootPath EG: \"C:\\MATLAB\\R2011a\"]\n",argv[0]);
return 1;
}

XMLNode xMainNode=XMLNode::openFileHelper(argv[1],"VisualStudioProject");

strRootFolder = CString(argv[1]);
strMathlabProj = CString(argv[2]);
GetPathFromFileName(strRootFolder);

strVCProj = CString(argv[1]);
strVCProjShortFilename = CString(argv[1]);
strMathLabRootPath = CString(argv[3]);

GetFileNameComponents(strMathlabProj, // in
csPath, csFilenameNoExt, csExtension); // out

if ( xMainNode.isEmpty() )
{
printf("Not valid input file [%s]\n", argv[1]);
return 2;
}

XMLNode xNode;

xNode = xMainNode.getChildNode("Configurations");

// Try to open output file
_pOutMakeFile = fopen(argv[2],"w");
if ( _pOutMakeFile == NULL )
{
printf("Can not open output file [%s]\n", argv[2]);
return 3;
}

// Generate Header
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n",csFilenameNoExt.GetBuffer(0),csPath.GetBuffer(0),strMathlabProj.GetBuffer(0));
fprintf(_pOutMakeFile,"%s\n",strMathlabProj.GetBuffer(0));
fprintf(_pOutMakeFile,".NET Assembly\n");
fprintf(_pOutMakeFile,"%s\n",csFilenameNoExt.GetBuffer(0));
fprintf(_pOutMakeFile,"${PROJECT_ROOT}\\%s\\src\n",csFilenameNoExt.GetBuffer(0));
fprintf(_pOutMakeFile,"${PROJECT_ROOT}\\%s\\distrib\n",csFilenameNoExt.GetBuffer(0));
fprintf(_pOutMakeFile,"true\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"all\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"on\n");
fprintf(_pOutMakeFile,"on\n");
fprintf(_pOutMakeFile,"on\n");
fprintf(_pOutMakeFile,"on\n");
fprintf(_pOutMakeFile,"on\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"option.net.framework.default\n");
fprintf(_pOutMakeFile,"option.assembly.type.private\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
strNamespace = csFilenameNoExt;
strNamespace.MakeUpper();
fprintf(_pOutMakeFile,"%s\n",strNamespace.GetBuffer(0));
strClassName = csFilenameNoExt;
fprintf(_pOutMakeFile,"C%s\n",strClassName.GetBuffer(0));
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n",strClassName.GetBuffer(0));

// Print list of files
xNode = xMainNode.getChildNode("Files");
PrintFileName(xNode,strRootFolder);

fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"%sdistrib\\%sNative.dll\n",csFilenameNoExt.GetBuffer(0),csFilenameNoExt.GetBuffer(0),strRootFolder.GetBuffer(0),csFilenameNoExt.GetBuffer(0));
fprintf(_pOutMakeFile,"%sdistrib\\%s.dll\n",csFilenameNoExt.GetBuffer(0),csFilenameNoExt.GetBuffer(0),strRootFolder.GetBuffer(0),csFilenameNoExt.GetBuffer(0));
fprintf(_pOutMakeFile,"%sdistrib\\readme.txt\n",csFilenameNoExt.GetBuffer(0),strRootFolder.GetBuffer(0));
fprintf(_pOutMakeFile,"%sdistrib\\%s_overview.html\n",csFilenameNoExt.GetBuffer(0),csFilenameNoExt.GetBuffer(0),strRootFolder.GetBuffer(0),csFilenameNoExt.GetBuffer(0));
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"%s\n",strMathLabRootPath.GetBuffer(0));
fprintf(_pOutMakeFile,"\n");
//fprintf(_pOutMakeFile,"C:\\My Documents\\MATLAB\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\general\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\ops\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\lang\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\elmat\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\randfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\elfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\specfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\matfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\datafun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\polyfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\funfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\sparfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\scribe\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\graph2d\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\graph3d\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\specgraph\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\graphics\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\uitools\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\strfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\imagesci\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\iofun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\audiovideo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\timefun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\datatypes\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\verctrl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\codetools\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\helptools\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\winfun\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\winfun\\NET\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\demos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\timeseries\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\hds\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\guide\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\plottools\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\local\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\matlab\\datamanager\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\simulink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\instrument\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\coder\\matlabcoder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simulink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simulink\\slresolve\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\blocks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\components\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\fixedandfloat\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\fixedandfloat\\obsolete\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simdemos\\aerospace\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simdemos\\automotive\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simdemos\\industrial\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simdemos\\simfeatures\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simdemos\\simgeneral\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\dee\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\glue\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\glue\\studio\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\dastudio\\depviewer\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\stateflow\\stateflow\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simulink\\MPlayIO\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simulink\\dataobjectwizard\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\hdlshared\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\asap2\\asap2\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\asap2\\asap2\\user\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\common\\can\\blocks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\common\\tgtcommon\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\connectivity\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\pil\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\shared\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtw\\datadiff\\GUI\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtw\\datadiff\\GUI\\Icons\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtw\\datadiff\\API\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtw\\cgv\\API\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtw\\misra\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulinkcoder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\accel\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\blocks\\library\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\blocks\\obsolete\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\fixedandfloat\\fxpdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simulink\\modeladvisor\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\simulink\\modeladvisor\\fixpt\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\stateflow\\sfdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\stateflow\\coder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\adivdsp\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\adivdsp\\vdspdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\adivdsp\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\adivdsp\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\adivdsp\\vdspblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\adivdsp\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\aero\\aero\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\mapgeodesy\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\aero\\astdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\asynciolib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\AUTOSAR\\AUTOSAR\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\blackfin\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\blackfin\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\blackfin\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\blackfin\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\blackfin\\blackfindemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\c166\\c166\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\c166\\blocks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\c166\\c166demos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\foundation\\utils\\resource_config\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\can\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\can\\canblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\can\\canmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\can\\canmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\cgir_fe\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\coder\\codegendemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\coder\\emlcodermex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\coder_foundation\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\simtargets\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\coder\\coder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\comm\\comm\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\comm\\commutilities\\comminit\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\comm\\commutilities\\commmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\comm\\commutilities\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\comm\\commdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\comm\\commdeprecated\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\help\\toolbox\\comm\\examples\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\testconsole\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\comparisons\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\compiler\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\compiler\\compilerdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\control\\control\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\control\\ctrlguis\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\control\\ctrlobsolete\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\control\\ctrlutil\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\control\\ctrldemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\help\\toolbox\\control\\examples\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\controllib\\engine\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\controllib\\engine\\options\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\controllib\\engine\\optim\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\controllib\\general\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\controllib\\graphics\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\controllib\\requirements\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\curvefit\\curvefit\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\curvefit\\splines\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\curvefit\\cftoolgui\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\curvefit\\sftoolgui\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\curvefit\\curvefitdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\optimlib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\daq\\daq\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\daq\\daqguis\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\daq\\daqdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\daq\\daqblks\\daqblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\daq\\daqblks\\daqmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\daq\\daqblks\\daqmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\dastudio\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\des\\desblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\des\\desmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\des\\desmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\des\\desdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\distcomp\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\user\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\mpi\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\pctdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\parallel\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\parallel\\util\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\lang\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\cluster\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\distcomp\\gpu\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dotnetbuilder\\dotnetbuilder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dotnetbuilder\\dotnetbuilderdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dsp\\dsp\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dsp\\dsputilities\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dsp\\dsputilities\\dspinit\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dsp\\dsputilities\\dspmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dsp\\dspdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\filterdesignlib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\system\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\dspblks\\dspblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\dspblks\\dspmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\fixedpoint\\fixedpoint\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\help\\toolbox\\dsp\\examples\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\dsp\\filterdesign\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\eclipseide\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\eclipseide\\eclipseidedemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\eclipseide\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\eclipseide\\registry\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\eclipseide\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\edalink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\foundation\\hdllink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\modelsim\\modelsim\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\modelsim\\modelsimdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\incisive\\incisive\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\incisive\\incisivedemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\discovery\\discovery\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\discovery\\discoverydemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\tlmgenerator\\foundation\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\tlmgenerator\\foundation\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\tlmgenerator\\foundation\\tlmgeneratordemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\eda\\edagraph\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\eda\\fil\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\eda\\fil\\fildemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\eda\\fpgaautomation\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\eda\\hdlparser\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\ecoder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\ecoder\\ecoderdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpt\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpt\\mpt\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpt\\user_specific\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\embeddedcoder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\eml\\eml\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\exlink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\fixedpoint\\fidemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\fixedpoint\\fixedpointtool\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\spcuilib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\siglib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\fixpoint\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\fixpoint\\fpca\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\edalink\\extensions\\fpgaautomation\\fpgademos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ghsmulti\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ghsmulti\\multidemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ghsmulti\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ghsmulti\\multiblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ghsmulti\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ghsmulti\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\hdlcoder\\hdlcoder\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\hdlcoder\\hdlcoder\\hdlwa\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\hdlcoder\\hdlcoderdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\hdlfilter\\hdlfilter\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\hdlfilter\\hdlfiltdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\iarew\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\iarew\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\iarew\\iarewdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\iarew\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\iarew\\templates\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\hookpoints\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\tgtpref2\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\profiler\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\blks\\tlc_c\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\pjtgenerator\\blks\\utils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\autointerface\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\autointerface\\ideregisterplugins\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\util\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\errorhandler\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\lfsocket\\lfsocket\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\foundation\\xmakefile\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\idelinkdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\ident\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\nlident\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\idobsolete\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\idguis\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\idutils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\iddemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\iddemos\\examples\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\ident\\idhelp\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\images\\colorspaces\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\images\\images\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\images\\imdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\images\\imuitools\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\images\\iptformats\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\images\\iptutils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\imageslib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\imaq\\imaq\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\imaqlib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\imaq\\imaqdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\imaq\\imaqblks\\imaqblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\imaq\\imaqblks\\imaqmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\imaq\\imaqblks\\imaqmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\instrument\\instrument\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\instrument\\instrumentdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\instrument\\instrumentblks\\instrumentblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\instrument\\instrumentblks\\instrumentmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\instrument\\instrumentblks\\instrumentmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\sam\\m3i\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slvnv\\simcoverage\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\\common\\configuration\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\\mpc555demos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\\mpc555dk\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\\pil\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\\rt\\blockset\\mfiles\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\mpc555dk\\rt\\blockset\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\optim\\optim\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\optim\\optimdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\data_manager\\data_manager\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\equation_language\\equation_language\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\foundation\\foundation\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\gl\\core\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\gl\\sli\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\logging\\base\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\logging\\mli\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\network_engine\\ne_support\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\network_engine\\network_engine\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\ne_sli\\ne_sli\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\pmir\\pmir\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\pm_sli\\pm_sli\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\powersys\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\DR\\DR\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\drives\\drives\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\facts\\facts\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\DR\\DRdemo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\drives\\drivesdemo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\facts\\factsdemo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\powersys\\powerdemo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\compiler\\core\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\compiler\\sli\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\simscapedemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\engine\\core\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\engine\\mli\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\engine\\sli\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\foundation\\simscape\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape_language\\simscape_language\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\library\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simscape\\simscape\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\simulation\\base\\m\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\physmod\\unit_manager\\unit_manager\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slvnv\\reqmgt\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slvnv\\slvnv\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slvnv\\rmidemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rf\\rf\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rf\\rfdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rf\\rftool\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rfblks\\rfblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rfblks\\rfblksmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rfblks\\rfblksmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rfblks\\rfblksdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgen\\rptgen\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgen\\rptgenv1\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgen\\rptgendemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgenext\\rptgenext\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgenext\\rptgenextv1\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgenext\\rptgenextdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\rptgen\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\rtwin\\rtwin\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\rtwin\\rtwindemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtwdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\rtwdemos\\rsimdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simulink\\blocks\\sb2sl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\eml\\eml\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\sigbldr\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\slcontrollib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\signal\\signal\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\signal\\sigtools\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\signal\\sptoolgui\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\signal\\sigdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simrf\\simrf\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simrf\\simrfmasks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\simrf\\simrfdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\help\\toolbox\\simrf\\examples\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\sl3d\\sl3d\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\sl3d\\sl3ddemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slcontrol\\slcontrol\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slcontrol\\slctrlguis\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slcontrol\\slctrlutil\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slcontrol\\slctrldemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\slcontrol\\slctrlobsolete\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\sldv\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\slvnv\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgenext\\slxmlcomp\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\stats\\stats\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\stats\\statsdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\stats\\classreg\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\statslib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\symbolic\\symbolic\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\symbolic\\symbolicdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\targetdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\foundation\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\foundation\\utils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\foundation\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\foundation\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\foundation\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\\utils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic2000\\tic2000demos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\utils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\blks\\sysobj_mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic6000\\tic6000demos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\linux\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\linux\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\linux\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\linux\\src\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\vxworks\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\vxworks\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\vxworks\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\vxworks\\src\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\windows\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\windows\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\operatingsystem\\windows\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\intelhost\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\\ti\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\\ti\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\\ti\\utils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\\ti\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\\ti\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\shared\\ti\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\etargets\\etargets\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\etargets\\etargets\\demoutils\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\testmeaslib\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\tasking\\tasking\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\tasking\\taskingdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rtw\\targets\\tasking\\tasking\\taskingblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\testmeaslib\\general\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\testmeaslib\\graphics\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\shared\\testmeaslib\\simulink\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic5000\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic5000\\blks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic5000\\blks\\mex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic5000\\blks\\masks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\target\\extensions\\processor\\tic5000\\tic5000demos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\ccsblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\ccsdemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\ccsdemos\\util\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\ccslinkblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\ccslinkblks\\rtdxsimblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\lic\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\tfl\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\util\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\rtw\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\ticcs\\envChecker\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\vision\\vision\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\vision\\visionutilities\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\vision\\visionutilities\\visioninit\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\vision\\visionutilities\\visionmex\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\vision\\visiondemos\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\help\\toolbox\\vision\\examples\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\wavelet\\wavelet\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\wavelet\\wmultisig1d\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\wavelet\\wavedemo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\wavelet\\compression\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\wrworkbench\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\wrworkbench\\mdlinfo\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\wrworkbench\\registry\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\idelink\\extensions\\wrworkbench\\wrworkbenchblks\n");
fprintf(_pOutMakeFile,"${MATLAB_ROOT}\\toolbox\\rptgen\\xmlcomp\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"true\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"true\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"5.1\n");
fprintf(_pOutMakeFile,"true\n");
fprintf(_pOutMakeFile,"false\n");
fprintf(_pOutMakeFile,"win32\n");
fprintf(_pOutMakeFile,"true\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n");
fprintf(_pOutMakeFile,"\n\n");
}

return nRetCode;
}

void PrintFileName(XMLNode xParentNode, LPCTSTR pszRootFolder)
{
CString strRootFolder = pszRootFolder;

int n=xParentNode.nChildNode();
for( int i = 0; i < n; i ++ )
{
XMLNode xNode = xParentNode.getChildNode(i);
if ( !strcmp(xNode.getName(), "File" ) )
{
const char *pcFileName = xNode.getAttribute("RelativePath");
char *pcNewStr = _strdup(pcFileName );

// Find the file extension
char *ext = strrchr(pcNewStr, '.');
if ( NULL != ext && !strcmp(ext, ".m"))
{
CString strFullFilename;
BOOL bRelativePathToParentFolders;
CString strRelativePath = pcNewStr;

if (IsCurrentDirPath(&strRelativePath))
{
CString strSubPath;
// remove .\ and append path
int pos = strRelativePath.Find("\\");
int len = strRelativePath.GetLength();
if ( pos > 0 ) {
strSubPath = strRelativePath.Right(len-pos-1);
}
// append
strFullFilename = strRootFolder + strSubPath;
}
else
{
strFullFilename = RelativePathToAbsolutePath(strRelativePath,strRootFolder, bRelativePathToParentFolders);
}

fprintf(_pOutMakeFile,"%s\n", strFullFilename.GetBuffer(0) );
}

free( pcNewStr );
}
else
{
PrintFileName(xNode,strRootFolder);
}
}
}

CString RelativePathToAbsolutePath(LPCTSTR contentRelativePath,LPCTSTR rootPath, BOOL &bRelativePathToParentFolders)
{
CString strContentPath;
CString strFullPath;
CString tempPath = _T("");

strContentPath.Format(_T("%s"),contentRelativePath);
tempPath.Format(_T("%s"),contentRelativePath);

// First let's convert to the right kind of path seps:
strContentPath.Replace('/', PATH_SEPARATOR);
CString fullPath = rootPath;
int sepIndex = fullPath.ReverseFind(PATH_SEPARATOR);

// put those together, and we've got our full path
if (sepIndex >= 0)
{
BOOL gotPath = FALSE;
CString strAbsoluteFullPath;
bool bRelativeUp = false;

CString beginStr = strContentPath.Left(3);
bRelativeUp = ( beginStr.CompareNoCase(REL_PATH_STR_WIN) == 0 || beginStr.CompareNoCase(REL_PATH_STR_MAC) == 0 || beginStr.CompareNoCase(REL_PATH_STR_UNIX) == 0 );
bRelativePathToParentFolders = bRelativeUp;

strFullPath = fullPath.Left(sepIndex + 1);

if (!strContentPath.IsEmpty() && strFullPath != contentRelativePath && bRelativeUp) {
CString extension;
int period = strContentPath.ReverseFind('.');
if ( period >= 0 )
extension = strContentPath.Right(strContentPath.GetLength()-period-1);

if ( (extension.GetLength() == 3) || (extension.GetLength() == 1)) {
//strContentPath.Replace(_T("..\\"), _T(".\\"));
CreateFullPath(&strAbsoluteFullPath, strFullPath, strContentPath);
strFullPath = strAbsoluteFullPath;
strFullPath.Replace('/', PATH_SEPARATOR);

gotPath = FileExist(strFullPath);
if (gotPath)
return strFullPath;
else
return CString(_T(""));

}
else
return CString(_T(""));
}
else
{
int sepIndex = strContentPath.ReverseFind(PATH_SEPARATOR);
if (sepIndex >= 0) {
// We have a full path already
gotPath = FileExist(strContentPath);
if (gotPath)
return strContentPath;
}

// We have a relative path (subfolder)
CString extension = _T("");
int period = strContentPath.ReverseFind('.');
if ( period >= 0 )
extension = strContentPath.Right(strContentPath.GetLength()-period-1);

if (extension.GetLength() == 3) {
// single file name no sub folder
strFullPath = strFullPath + strContentPath;
gotPath = FileExist(strFullPath);
if (gotPath)
return strFullPath;
else
return CString(_T(""));
}
}
}
else
{
strFullPath = fullPath;
}

strFullPath += tempPath;

return strFullPath;
}

This will solve the following issue :)

http://stackoverflow.com/questions/1790417/matlab-deployment-add-files-to-source-control

Now let's look at a sample Matlab script which can be converted to an assembly.

Follow the following link

http://www.mathworks.com/matlabcentral/fileexchange/12987-integrating-matlab-with-c

There is a big problem when targeting .NET 4.0 for a client referencing a generated assembly targeting .NET 4.0 as far as I am concerned which should be fixed ASAP by Mathworks. This problem still remains with Matlab R2011a.
A C# client targeting .NET 4.0 will not run on Windows 7 64 bit. When the C# client will try to instantiate the class wrapper for the generated Matlab assembly using new, an exception will be thrown. Only 32 bit OS such as the old Windows XP will support both the .NET Framework 2.0 and 4.0. But not Windows 7 64 bit running as 32 bit. There is a dependency with .NET 2.0 for MWArray.dll at least I can't find the v4 version anywhere under C:\MATLAB\R2011a. Because .NET Framework 2.0 won't install on Windows 7 64 bit, I highly request the Mathworks folks to release MWArray.dll for .NET 4.0 and create a dependency with the 4.0 version when building the assembly. I always check target 4.0 but the dependency is still the 2.0. Maybe this is a fallback and I am missing the 4.0 version or maybe it is not supported.

Deployment Runtime

http://www.mathworks.com/help/toolbox/compiler/f12-999353.html

Thanks!

Google engineer Steve Yegge let the frustration fly in a post regarding the Mountain View's plucky social network

2011-11-03T00:16:00.000-07:00

http://www.minyanville.com/dailyfeed/2011/10/13/google-engineer-calls-google-a/

Really adobe

2011-11-01T23:35:00.001-07:00

One update every two months.... Give me break!!!!

Sept 13, 2011 10.1.1 Q Latest release. This a regular quarterly update with security enhancements, improvements to stability, and bug fixes.
Jun 14, 2011 10.1 Q This is a major update that provides security fixes, feature updates, and major enhancements such as Protected View for Acrobat.
Apr 21, 2011 10.0.3 OOC This patch fixes a vulnerability and provides an updated Flash player.
Mar 21, 2011 10.0.2 OOC This patch fixes a vulnerability and provides an updated Flash player.
Feb 8 2011 10.0.1 Q Numerous security fixes as well as improvements to Protected Mode, QTP support, Flash, and support for SCCM via newly released SCUP catalogs.

Convert Mathlab to C# assembly

2011-11-01T19:06:00.000-07:00

Step 1 Install Mathlab 2011

Step 2 Install Visual Studio 2010

Step 3 native compiler

make sure you runmex -setup to select your target C++ compiler

Step 4 To create an Assembly launch Mathlab 2011

Select New Deployment Project then select the target Type

Step 5 Finally build .NET Assembly

The sub folder will contain the Assembly DLL and Native DLL

Small, simple, cross-platform, free and fast C++ XML Parser

2011-11-01T14:05:00.000-07:00

Small, simple, cross-platform, free and fast C++ XML Parser

Business Intelligence
TIMi added value
This project started from his frustration that he could not find any simple, portable XML Parser to use inside all my projects (for example, inside the award-winning TIMi software suite created by the Business-Insight company). Let's look at the well-known Xerces C++ library: The complete Xerces project is 53 MB! (11 MB compressed in a zipfile). In 2003, He was developping many small tools. He was using XML as standard for all my input/ouput configuration and data files. The source code of his small tools was usually around 600KB. In these conditions, don't you think at 53MB to be able to read an XML file is a little bit "too much"? So he created his own XML parser. His XML parser "library" is composed of only 2 files: a .cpp file and a .h file. The total size is 104 KB

Here is how it works: The XML parser loads a full XML file in memory, it parses the file and it generates a tree structure representing the XML file. Of course, you can also parse XML data that you have already stored yourself into a memory buffer. Thereafter, you can easily "explore" the tree to get your data. You can also modify the tree using "add" and "delete" functions
and regenerate a formatted XML string from a subtree. Memory management is totally transparent through the use of smart pointers (in other words, you will never have to do any new, delete, malloc or free)("Smart pointers" are a primitive version of the garbage collector in Java).

To the best of his knowledge, there exists no other "non-validating C++ XML parser" that is as simple and as powerfull.

Well Tiny XML is pretty powerful too!

Here are the characteristics of the XMLparser library:

Non-validating XML parser written in standard C++ (DTD's or XSD's informations are ignored).

Cross-plateform: the library is currently used every day on Solaris, Linux (32bit and 64bit) and Windows to manipulate "small" PMML documents (10 MB).
The library has been tested and is working flawlessly using the following compilers: gcc (under linux, Mac OS X Tiger and under many unix flavours), Visual Studio 6.0, Visual Studio .NET (under Windows 9x,NT,2000,XP,Vista,CE,mobile), Intel C/C++ compiler, SUN CC compiler, C++ Borland Compiler. The library is also used under Apple OS, iPhone/iPad OS, Amiga OS, QNX and under the Netburner plateform. To the best of my knowledge, i think that all plateforms are now supported.
The parser builds a tree structure that you can "explore" easily (DOM-type parser).
The parser can be used to generate XML strings from subtrees (it's called rendering). You can also save subtrees directly to files (automatic "Byte Order Mark"-BOM support).
Modification or "from scratch creation" of large XML tree structures in memory using funtions like addChild, addAttribute, updateAttribute, deleteAttribute,...
It's SIMPLE: no need to learn how to use dozens of classes: there is only one simple class: the 'XMLNode' class (that represents one node of the XML tree).

Very efficient (Efficiency is required to be able to handle BIG files):
The string parser is very efficient: It does only one pass over the XML string to create the tree. It does the minimal amount of memory allocations. For example: it does NOT use slow STL::String class but plain, simple and fast C malloc 's. It also allocates large chunk of memory instead of many small chunks. Inside Visual C++, the "debug versions" of the memory allocation functions are very slow: Do not forget to compile in "release mode" to get maximum speed.
The "tree exploration" is very efficient because all operations on the 'XMLNode' class are handled through references: there are no memory copy, no memory allocation, never.

The XML string rendering is very efficient: It does one pass to compute the total memory size of the XML string and a second pass to actually create the string. There is thus only one memory allocation and no extra memory copy. Other libraries are slower because they are using the string concatenation operator that requires many memory (re-)allocations and memory copy.

In-memory parsing
Supports XML namespaces
Very small and totally stand-alone (not built on top of something else). Uses only standard library (and only for the 'fopen' and the 'fread' functions to load the XML file).

Easy to integrate into you own projects: it's only 2 files! The .h file does not contain any implementation code. Compilation is thus very fast.
Robust.
Optionnally, if you define the C++ prepocessor directives STRICT_PARSING and/or APPROXIMATE_PARSING, the library can be "forgiving" in case of errors inside the XML.

He has tried to respect the XML-specs given at: http://www.w3.org/TR/REC-xml/
Fully integrated error handling :
The string parser gives you the precise position and type of the error inside the XML string (if an error is detected).
The library allows you to "explore" a part of the tree that is missing. However data extracted from "missing subtrees" will be NULL. This way, it's really easy to code "error handling" procedures.

Thread-safe (however the global parameters "guessUnicodeChar" and"strictUTF8Parsing" must be unique because they are shared by all threads).
Full Native Supports for a wide range of character sets & encodings: ANSI (legacy) / UTF-8 / Shift-JIS / GB2312 / Big5 / GBK.
Under Windows, Linux, Linux 64 bits & Solaris, they have additionnaly: Unicode 16bit / Unicode 32bit widechar characters support that includes:
For the unicode version of the library: Automatic conversion to Unicode before parsing (if the input XML file is standard ansi 8bit characters).
For the ascii version of the library: Automatic conversion to legacy or UTF-8 before parsing (if the input XML file is unicode 16 or 32bit wide characters).

The XMLParser library is able to handle successfuly chinese, japanese, cyrilic and other extended characters thanks to an extended UTF-8 encoding support, Shift-JIS (japanese) and to GB2312/Big5/GBK encoding support (chinese) (see this UTF-8-demo that shows the characters available). If you are still experiencing character encoding problems, he suggest you to convert your XML files to UTF-8 using a tool like iconv (precompiled win32 binary).

Transparent memory management through the use of smart pointers.

Support for a wide range of clearTags that are containing unformatted text:
{![CDATA[ ... ]]}, {!-- ... --}, {PRE} ... {/PRE}, {!DOCTYPE ... }
Unformatted texts are not parsed by the library and can contain items that are usually 'forbidden' in XML (for example: html code)
Support for inclusion of pure binary data (images, sounds,...) into the XML document using the four provided ultrafast Base64 conversion functions.
The library is under the Aladdin Free Public License(AFPL).

A small tutorial
Let's assume that you want to parse the XML file "PMMLModel.xml" that contains:
( all < replace by { and all > replace by } )

{?xml version="1.0" encoding="ISO-8859-1"?>
{PMML version="3.0" xmlns="http://www.dmg.org/PMML-3-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema_instance"}
{Header copyright="Frank Vanden Berghen"}
Hello World!
{Application name="<Condor>" version="1.99beta" /}
{/Header}
{Extension name="keys"}
{Key name="urn"}{/Key}
{/Extension}
{DataDictionary}
{DataField name="persfam" optype="continuous" dataType="double"}
{Value value="9.900000e+001" property="missing" /}
{/DataField}
{DataField name="prov" optype="continuous" dataType="double" /}
{DataField name="urb" optype="continuous" dataType="double" /}
{DataField name="ses" optype="continuous" dataType="double" /}
{/DataDictionary}
{RegressionModel functionName="regression" modelType="linearRegression"} {RegressionTable intercept="0.00796037"}
{NumericPredictor name="persfam" coefficient="-0.00275951" /}
{NumericPredictor name="prov" coefficient="0.000319433" /}
{NumericPredictor name="ses" coefficient="-0.000454307" /}
{NONNumericPredictor name="testXmlExample" />
{/RegressionTable}
{/RegressionModel}
{/PMML}

Let's analyse line by line the following small example program:

#include // to get "printf" function
#include // to get "free" function
#include "xmlParser.h"

int main(int argc, char **argv)
{
// this open and parse the XML file:
XMLNode xMainNode=XMLNode::openFileHelper("PMMLModel.xml","PMML");
// this prints "":
XMLNode xNode=xMainNode.getChildNode("Header");
printf("Application Name is: '%s'\n", xNode.getChildNode("Application").getAttribute("name"));
// this prints "Hello world!":
printf("Text inside Header tag is :'%s'\n", xNode.getText());
// this gets the number of "NumericPredictor" tags: xNode=xMainNode.getChildNode("RegressionModel").getChildNode("RegressionTable");
int n=xNode.nChildNode("NumericPredictor");
// this prints the "coefficient" value for all the "NumericPredictor" tags:
for (int i=0; i printf("coeff %i=%f\n",i+1,atof(xNode.getChildNode("NumericPredictor",i).getAttribute("coefficient")));
// this prints a formatted ouput based on the content of the first "Extension" tag of the XML file:
char *t=xMainNode.getChildNode("Extension").createXMLString(true); printf("%s\n",t);
free(t);
return 0;
}

XML Parser using XmlReader from an XML string in C#

2011-10-20T14:36:00.001-07:00

System.Text.UTF8Encoding encoding = new System.Text.UTF8Encoding();
Byte[] pBytes = encoding.GetBytes(strXML);
MemoryStream pMem = new MemoryStream(pBytes, 0, pBytes.Length, true, true);
XmlReader reader = XmlReader.Create(pMem);
string s = Encoding.UTF8.GetString(pMem.GetBuffer(), 0, (int)pMem.Position);
XmlElement element;
XmlDocument xmlDoc = new XmlDocument();
pMem.Seek(0, SeekOrigin.Begin);

while (reader.Read())
{
XmlNode node = null;
switch (reader.NodeType)
{
case XmlNodeType.Element:
bool fEmptyElement = reader.IsEmptyElement;
element = xmlDoc.CreateElement(reader.Prefix, reader.LocalName, reader.NamespaceURI);
//element.IsEmpty = fEmptyElement;
//ReadAttributes(reader, element);
//if (!fEmptyElement) {
//parent.AppendChild(element);
//parent = element;
//continue;
//}
//node = element;
break;

case XmlNodeType.EndElement:
//if (parent.ParentNode == null)
//{
// syntax error in document.
// IXmlLineInfo li = (IXmlLineInfo)reader;
// throw new XmlException(string.Format(SR.UnexpectedToken,"", li.LineNumber, li.LinePosition), null, li.LineNumber, li.LinePosition);
// }
//parent = parent.ParentNode;
continue;

case XmlNodeType.EntityReference:
if (reader.CanResolveEntity)
{
reader.ResolveEntity();
}
continue;

case XmlNodeType.EndEntity:
continue;

case XmlNodeType.Attribute:
//node = LoadAttributeNode(parent);
break;

case XmlNodeType.Text:
node = xmlDoc.CreateTextNode(reader.Value);
break;

case XmlNodeType.SignificantWhitespace:
node = xmlDoc.CreateSignificantWhitespace(reader.Value);
break;

case XmlNodeType.Whitespace:
//if (preserveWhitespace) {
// node = xmlDoc.CreateWhitespace(reader.Value);
// break;
//}
//else {
//continue;
//}
continue;
case XmlNodeType.CDATA:
node = xmlDoc.CreateCDataSection(reader.Value);
break;

case XmlNodeType.XmlDeclaration:
break;

case XmlNodeType.ProcessingInstruction:
node = xmlDoc.CreateProcessingInstruction(reader.Name, reader.Value);
break;

case XmlNodeType.Comment:
node = xmlDoc.CreateComment(reader.Value);
break;

case XmlNodeType.DocumentType:
string pubid = r.GetAttribute("PUBLIC");
string sysid = r.GetAttribute("SYSTEM");
node = xmlDoc.CreateDocumentType(reader.Name, pubid, sysid, reader.Value);
break;

default:
//UnexpectedNodeType(reader.NodeType);
break;
}
}

will developers adopt adobe flash 11

2011-10-19T00:51:00.001-07:00

http://bits.blogs.nytimes.com/2011/09/21/will-developers-adopt-adobe-flash-11/

http://alternativaplatform.com/en/showcase/

SearchIndexer.exe really suck !!!

2011-10-17T15:38:00.000-07:00

Will slow down your computer bit time....
Will suck 1 GB of memory in less than 5 minutes....

Whoever wrote this at Microsoft should be fire!!!

Turn off indexing and speed up Windows XP
If you don't use Windows XP's built-in search often (like every day), disabling indexing can significantly speed up your PC.

By default Windows XP indexes files on your hard drive and stores them in memory to speed up its' built-in search. But if you rarely use Windows search, turn off indexing to free up memory and CPU horsepower for the files and applications you actually do use. A few simple how-to steps after the jump.

To turn off indexing:

Open up "My Computer."
Right-click on your hard drive (usually "C:") and choose "Properties."
Uncheck the box at the bottom that reads "Allow Indexing Service to..."
Click OK, and files will be removed from memory. This removal may take a few minutes to complete.
To disable the indexing service:

In the "Start" menu, choose "Run."
Type "services.msc" and press Enter.
Scroll-down to "Indexing Service" and double-click it.
If the service status is "Running", then stop it by pressing the "Stop" button.
To make sure this service doesn't run again, under "Startup Type:", choose "Disabled."
Windows search will still work if you perform these steps, but it will work more slowly than if indexing was enabled.

Brute force WTF (aka What The Fuck!)

And to avoid rebooting the machine kill the process searchindexer.exe point to C:\WINDOWS\system32 and rename searchindexer.exe to searchindexer.exe.old.
This time you should be good. If you don't rename searchindexer.exe process will be automatically restarted....

Farewell Dennis Ritchie

2011-10-13T18:33:00.001-07:00

int main( int argc, char **argv )
{
printf( "Goodbye, world. :(\n" );
}

L'eulogie par Bjarne Stroustrup:

"
Before C, there was far more hardware diversity than we see in the
industry today. Computers proudly sported not just deliciously
different and offbeat instruction sets, but varied wildly in almost
everything, right down to even things as fundamental as character bit
widths (8 bits per byte doesn’t suit you? how about 9? or 7? or how
about sometimes 6 and sometimes 12?) and memory addressing (don’t like
16-bit pointers? how about 18-bit pointers, and oh by the way those
aren’t pointers to bytes, they’re pointers to words?).

There was no such thing as a general-purpose program that was both
portable across a variety of hardware and also efficient enough to
compete with custom code written for just that hardware. Fortran did
okay for array-oriented number-crunching code, but nobody could do it
for general-purpose code such as what you’d use to build just about
anything down to, oh, say, an operating system.

So this young upstart whippersnapper comes along and decides to try to
specify a language that will let people write programs that are: (a)
high-level, with structures and functions; (b) portable to just about
any kind of hardware; and (c) efficient on that hardware so that
they’re competitive with handcrafted nonportable custom assembler code
on that hardware. A high-level, portable, efficient systems
programming language.

How silly. Everyone knew it couldn’t be done.

C is a poster child for why it’s essential to keep those people who
know a thing can’t be done from bothering the people who are doing it.
(And keep them out of the way while the same inventors, being anything
but lazy and always in search of new problems to conquer, go on to use
the world’s first portable and efficient programming language to build
the world’s first portable operating system, not knowing that was
impossible too.)

Thanks, Dennis.
"

https://plus.google.com/u/0/101960720994009339267/posts/33mmANQZDtY

The UNIX Time-Sharing System
http://www.alcatel-lucent.com/bstj/vol57-1978/articles/bstj57-6-1905.pdf

UNIX Time-Sharing System: A Retrospective
http://www.alcatel-lucent.com/bstj/vol57-1978/articles/bstj57-6-1947.pdf

UNIX Time-Sharing System: The C Programming Language
http://www.alcatel-lucent.com/bstj/vol57-1978/articles/bstj57-6-1991.pdf

http://geektionnerd.net/un-genie-est-mort/

Farewell Steve

2011-10-07T18:18:00.001-07:00

I remember when it all started, moving that turtle around on the screen in elementary school using Logo then came the Apple I.

I remember programming Basic on an Apple ][ playing, karateka, sorcelery choplifter and loderunner.

I remember playing chess master on the mac+ of my uncle.

I remember beeing impressed by the 16 millions color of the Next Cube and it's DSP processor and I remember looking at the Next computer in Reims and drooling on being able to compile anything on it.

I remember seeing Toy Story and some cool pixar CGI done with renderman.

I remember working on a car adapter for the iPod at Motorola when the stock rise begin

I remember the simplicity of the iPod Touch.

I remember trading an iPod touch against two Adobe products to listen to music in my car after quite some resistence.

I remember comparing Microsoft, Google, Apple and the NASDAQ chart on yahoo and Google finance web site and see how Apple reaches 400$ and became the largest company in US by passing Chevron.

I remember enjoying writing COCOA code for Adobe on a very slick Mac Book Pro 17 inch.

I remember seeing Steve so incredibly excited to give a “small token” of appreciation at the Apple all-hands by giving everyone an iPod shuffle.

I remember the war between Apple and Adobe around Flash and in the end I think you made the right decision and left an open window for engineer to replace FLash by HTML5.

I remember seeing the words pancreatic cancer on the internet.

I remember my first iPhone 4 and that I will have an iPad soon :)

I remember my optimism and the world optimisim of seeing Steve beating this thing like Phil Lesh, the bassist of the Grateful Dead who defeated prostate cancer. This is sad to see that the one-year relative survival rate for pancreatic cancer is 20%, and the five-year rate is 4%.

This week many folks stopped by the Apple campus to pay some respects and remember Steve.

The parking lot was packed. There was some security, a bench with some flowers, some candles, and an iPad with the photo of Steve on the display.

Silence, Sadness and Loss.

Steve touched our lives in so many personal, and emotional ways. Thanks you for being different and a genius leader!

You will be missed Steve!

http://www.cnn.com/2011/10/05/us/obit-steve-jobs/index.html

Microsoft jettisons Flash with 'plug-in free' Windows 8 Metro IE10

2011-09-15T11:25:00.000-07:00

http://www.appleinsider.com/articles/11/09/15/microsoft_to_jettison_adobe_flash_with_plug_in_free_browsing_in_windows_8_metro_ie10.html

Electric Commander PERL system call limition

2011-09-09T14:13:00.000-07:00

If you ever wanted to execute a UI process on Windows using an Electric Commander step written in perl you will realize that you can only execute binary using STD IO in case your agent is running as a service.
One reason is that Electric commander will pipe all STD IO to its internal logging mecanism associated to each JOB you are running for each STEP.

Complete reason has been posted here
https://electriccloud.zendesk.com/entries/64647-kbec-00037-running-steps-that-require-an-interactive-windows-desktop-on-the-agent-machine

The only workaround I found is to implement an IOCP WIN32 service that you can use to send message using SOCKET. At this point the IOCP WIN32 service can execute the native application including complex application which may require OLE AUTOMATION. EG Itunes :), Microsoft Excel, etc...

Will not work

my $exePath = 'C:/Program Files/Notepad++/Notepad++.exe';
print "Execute $exePath \n";
$exitCode = system($exePath );

The process is spawn. I can see it using the Task Manager under Process tab but the Process doesn't receive ACTIVATION.

Here is the script that I use!

use IO::Socket;
use ElectricCommander;
use Cwd;
use Time::Local;

use Win32::Process;
use Win32::TieRegistry;
use Win32::TieRegistry qw(:KEY_);

my $regKey;
my $UserShellFoldersKey;
my $valueString;
my $exitCode = -1;
my $process;

# if you need to request current user folder
$regKey = new Win32::TieRegistry "CUser",
{ Access=>KEY_READ(), Delimiter=>"/" };
$UserShellFoldersKey = $regKey->Open( "Software/Microsoft/Windows/CurrentVersion/Explorer/User Shell Folders" );

# Get value data:
$valueString= $UserShellFoldersKey->GetValue("Personal");

my $launchedByUser = '$[/myJob/launchedByUser]';
my $jobName = '$[/myJob/jobName]';

my $build_test_dir = 'C:\\ec_workspace\\'.$jobName.'\\';

my $msg = '';

#the caller
my $sock_call = new IO::Socket::INET (
PeerAddr => 'localhost',
PeerPort => '4000',
Proto => 'tcp',
);
if ($sock_call)
{
print $sock_call "LaunchNotepad++\n";
my $sock_addr = recv($sock_call,$msg,190,0);
print $msg;

close($sock_call);
}
else
{
print "ERROR Could not create client socket to IOCP Broadcom Automation Service!\n";
die "Could not create client socket to IOCP Broadcom Automation Service $!\n";
}

}

The IOCP server (WIN32 service) is very small and powerful because it is using asynchronous IO so it can handle a lot of simultaneous request comming from multiple Electric commander JOBS. In my case the IOCP server will take care of enumerating the target process before executing it because the target process was not single instance and in my case if two JOBS were running at the same time I wanted to make sure not to end up with two running instances. Off course you can limit this inside Electric Commander itself by preventing job concurrency but then the UI can be left open at the end of its execution. Maybe you want to Remote Desktop the machine the next day to look at results. During this time you want to prevent others automation to be executed. To perform synchronisation the script can wait on idle for the same time used by the automation process to complete. You know this only after monitoring the automation process. Once you know you'll have to tune your step.

Electric Commander is very powerful. I wish I could afford the license to use it to perform recuring video security monitoring and reporting on a server running at home because once you can send message using local socket between EC apache instance and your process, you are entitled to implement a million of creative ideas!

Automation server and bot rules the world! Aren't they ?

IOCP Server

int CALLBACK WinMain(HINSTANCE hInstance,HINSTANCE ,LPSTR ,int ){
....
init();
run();
}

static void init(void)
{
init_winsock();
create_io_completion_port();
create_listening_socket();
bind_listening_socket();
start_listening();
load_accept_ex();
start_accepting();
}

static void run(void)
{
DWORD length;
BOOL resultOk;
WSAOVERLAPPED* ovl_res;
SocketState* socketState;

for (;;)
{
resultOk = get_completion_status(&length, &socketState, &ovl_res);

switch (socketState->operation)
{
case OP_ACCEPT:
OutputDebugString(L"* operation ACCEPT completed\n");
accept_completed(resultOk, length, socketState, ovl_res);
break;

case OP_READ:
OutputDebugString(L"* operation READ completed\n");
read_completed(resultOk, length, socketState, ovl_res);
break;

case OP_WRITE:
OutputDebugString(L"* operation WRITE completed\n");
write_completed(resultOk, length, socketState, ovl_res);
break;

default:
OutputDebugString(L"* error, unknown operation!!!\n");
destroy_connection(socketState, ovl_res); // hope for the best!
break;
} // switch
} // for
}

static void read_completed(BOOL resultOk, DWORD length,
SocketState* socketState, WSAOVERLAPPED* ovl)
{

if (resultOk)
{
if (length > 0)
{
_TCHAR message[512];
_sntprintf(message,512,L"* read operation completed, %d bytes read\n", length);
OutputDebugString(message);

wchar_t *pwText = NULL;
pwText = new wchar_t[length];
if(!pwText)
{
delete []pwText;
}
memset(pwText,0,length*sizeof(wchar_t));
MultiByteToWideChar (CP_ACP, 0, socketState->buf, -1, pwText, length-1 );

_sntprintf(message,512,L"* buffer: %s\n", pwText);
OutputDebugString(message);

HINSTANCE hInstanceMobCat = NULL;
HWND hWndMobCat = NULL;
DWORD dwProcessIdMobcat = 0;

if (_tcsicmp(pwText,L"LaunchNotepad++")==0)
{
std::string szExecutable = "C:\\Program Files\\Notepad++\\Notepad++.exe";

bstrExecutable = utf8toUTF16(szExecutable);
// Can't call ShellExecuteEx on main thread since it runs a message loop!
// That would let windows messages sneak in before they are expected (Bug 2507120)
HANDLE const hShellExecThread = CreateThread(NULL, 0, callShellExecThreadProc, bstrExecutable, 0, NULL);
if (!hShellExecThread)
{
}
DWORD result = WaitForSingleObject( hShellExecThread, INFINITE );
if( result == WAIT_FAILED )
{
}
DWORD exitCode = 5;
BOOL success = ::GetExitCodeProcess( hShellExecThread, &exitCode );
if( !success ) exitCode = 5;
CloseHandle(hShellExecThread);
}

delete []pwText;

// starts another write back to caller
socketState->length = length;
start_writing(socketState, ovl);
}
else // length == 0
{
OutputDebugString(L"* connection closed by client\n");
destroy_connection(socketState, ovl);
}
}
else // !resultOk, assumes connection was reset
{ int err = GetLastError();

_TCHAR message[512];

_sntprintf(message,512,L"* error %d in recv, assuming connection was reset by client\n", err);

OutputDebugString(message);
destroy_connection(socketState, ovl);
}
}

GOOGLE buying MMI

2011-08-15T11:11:00.000-07:00

One of those acquisition to remember

http://www.businessinsider.com/live-google-and-motorola-explain-the-big-acquisition-2011-8

http://www.businessinsider.com/google-just-admitted-that-android-is-a-mess-2011-8

Android Monkey Script DispatchPress Bug

2011-08-03T16:38:00.000-07:00

When using Monkey Script I noticed that DispatchPress(KEYCODE_BACK)
is doing nothing which really suck. In many cases this is due to the fact that the Actibity doesn't consume the Key event.
The solution to this problem is to use a mix of monkey script and
adb shell input command in a sequence.

1 Using monkey script gave some great timing
control. Wait a certain amount of second for the activity and is a
blocking adb call.
2 Finally sending adb shell input keyevent 4 will end the running APK.

EG

adb shell monkey -p com.my.application -v -v -v -f /sdcard/monkey_script.txt 1
adb shell input keyevent 4

How to rotate or flip a video inside Adobe Premiere

2011-07-27T09:07:00.001-07:00

When recording video with iPhone or Android device it is possible to record an up side down video. In this case you'll probably need to rotate/flip the video using Adobe Premiere before exporting the video to H264 :)

To do so here is what you can do in Adobe Premiere CS3/CS4 and probably CS5

Hit [Window] > [Effect Controls] *To see the panel*

Click on the clip that you want to flip

Hit [Video effects] > [Motion] > [Rotation]

Type in 180 instead of 0.

Virtual Earth

2011-07-22T11:45:00.000-07:00

When I was integrating Virtual Earth 3D in a GPS location software
I noticed that the default InfoBox for a push pin added on the map has a fixed size. When looking at Microroft documentation they said that the style can be overriden by calling map.ClearInfoBoxStyles().

http://msdn.microsoft.com/en-us/library/bb412441.aspx#Y792

Well this is working for 2D map but for 3D the info box is blanked.

The Virtual Earth CSS is poorly documented but I found a way to override the style sheet without calling ClearInfoBoxStyles and then be able to view bigger infobox.
Include the following at the top of your hosting page

/* override VE css to resize infoboxes */

.ero .ero-body
{
width:550px!important;
overflow: auto;
}

.ero .firstChild
{
width:540px!important;
}

Android Monkey Script

2011-06-15T18:35:00.000-07:00

Monkey: The Monkey is a program that runs on your emulator or device and generates pseudo-random streams of user events such as clicks, touches, or gestures, as well as a number of system-level events. You can use the Monkey to stress-test applications that you are developing, in a random yet repeatable manner.

Monkey script is unfortunately poorly documented but it is pretty easy to write monkey script after looking at the Monkey Script Java source code itself. The Java Source code is the code in charge of parsing the monkey script and dispatching all monkey script event in a timely manner.

development/cmds/monkey/src/com/android/commands/monkey/MonkeySourceScript.java

/*
* Copyright (C) 2008 The Android Open Source Project
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

package com.android.commands.monkey;

import android.os.SystemClock;
import android.view.KeyEvent;

import java.io.BufferedReader;
import java.io.DataInputStream;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.LinkedList;
import java.util.StringTokenizer;

/**
* monkey event queue. It takes a script to produce events
*
* sample script format:
* type= raw events
* count= 10
* speed= 1.0
* start data >>
* captureDispatchPointer(5109520,5109520,0,230.75429,458.1814,0.20784314,
* 0.06666667,0,0.0,0.0,65539,0)
* captureDispatchKey(5113146,5113146,0,20,0,0,0,0)
* captureDispatchFlip(true)
* ...
*/
public class MonkeySourceScript implements MonkeyEventSource {
private int mEventCountInScript = 0; //total number of events in the file
private int mVerbose = 0;
private double mSpeed = 1.0;
private String mScriptFileName;
private MonkeyEventQueue mQ;

private static final String HEADER_TYPE = "type=";
private static final String HEADER_COUNT = "count=";
private static final String HEADER_SPEED = "speed=";

private long mLastRecordedDownTimeKey = 0;
private long mLastRecordedDownTimeMotion = 0;
private long mLastExportDownTimeKey = 0;
private long mLastExportDownTimeMotion = 0;
private long mLastExportEventTime = -1;
private long mLastRecordedEventTime = -1;

private static final boolean THIS_DEBUG = false;
// a parameter that compensates the difference of real elapsed time and
// time in theory
private static final long SLEEP_COMPENSATE_DIFF = 16;

// maximum number of events that we read at one time
private static final int MAX_ONE_TIME_READS = 100;

// number of additional events added to the script
// add HOME_KEY down and up events to make start UI consistent in each round
private static final int POLICY_ADDITIONAL_EVENT_COUNT = 2;

// event key word in the capture log
private static final String EVENT_KEYWORD_POINTER = "DispatchPointer";
private static final String EVENT_KEYWORD_TRACKBALL = "DispatchTrackball";
private static final String EVENT_KEYWORD_KEY = "DispatchKey";
private static final String EVENT_KEYWORD_FLIP = "DispatchFlip";

// a line at the end of the header
private static final String STARTING_DATA_LINE = "start data >>";
private boolean mFileOpened = false;

FileInputStream mFStream;
DataInputStream mInputStream;
BufferedReader mBufferReader;

public MonkeySourceScript(String filename, long throttle) {
mScriptFileName = filename;
mQ = new MonkeyEventQueue(throttle);
}

/**
*
* @return the number of total events that will be generated in a round
*/
public int getOneRoundEventCount() {
//plus one home key down and up event
return mEventCountInScript + POLICY_ADDITIONAL_EVENT_COUNT;
}

private void resetValue() {
mLastRecordedDownTimeKey = 0;
mLastRecordedDownTimeMotion = 0;
mLastExportDownTimeKey = 0;
mLastExportDownTimeMotion = 0;
mLastRecordedEventTime = -1;
mLastExportEventTime = -1;
}

private boolean readScriptHeader() {
mEventCountInScript = -1;
mFileOpened = false;
try {
if (THIS_DEBUG) {
System.out.println("reading script header");
}

mFStream = new FileInputStream(mScriptFileName);
mInputStream = new DataInputStream(mFStream);
mBufferReader = new BufferedReader(
new InputStreamReader(mInputStream));
String sLine;
while ((sLine = mBufferReader.readLine()) != null) {
sLine = sLine.trim();
if (sLine.indexOf(HEADER_TYPE) >= 0) {
// at this point, we only have one type of script
} else if (sLine.indexOf(HEADER_COUNT) >= 0) {
try {
mEventCountInScript = Integer.parseInt(sLine.substring(
HEADER_COUNT.length() + 1).trim());
} catch (NumberFormatException e) {
System.err.println(e);
}
} else if (sLine.indexOf(HEADER_SPEED) >= 0) {
try {
mSpeed = Double.parseDouble(sLine.substring(
HEADER_SPEED.length() + 1).trim());

} catch (NumberFormatException e) {
System.err.println(e);
}
} else if (sLine.indexOf(STARTING_DATA_LINE) >= 0) {
// header ends until we read the start data mark
mFileOpened = true;
if (THIS_DEBUG) {
System.out.println("read script header success");
}
return true;
}
}
} catch (FileNotFoundException e) {
System.err.println(e);
} catch (IOException e) {
System.err.println(e);
}

if (THIS_DEBUG) {
System.out.println("Error in reading script header");
}
return false;
}

private void processLine(String s) {
int index1 = s.indexOf('(');
int index2 = s.indexOf(')');

if (index1 < 0 || index2 < 0) {
return;
}

StringTokenizer st = new StringTokenizer(
s.substring(index1 + 1, index2), ",");

if (s.indexOf(EVENT_KEYWORD_KEY) >= 0) {
// key events
try {
long downTime = Long.parseLong(st.nextToken());
long eventTime = Long.parseLong(st.nextToken());
int action = Integer.parseInt(st.nextToken());
int code = Integer.parseInt(st.nextToken());
int repeat = Integer.parseInt(st.nextToken());
int metaState = Integer.parseInt(st.nextToken());
int device = Integer.parseInt(st.nextToken());
int scancode = Integer.parseInt(st.nextToken());

MonkeyKeyEvent e = new MonkeyKeyEvent(downTime, eventTime,
action, code, repeat, metaState, device, scancode);
mQ.addLast(e);

} catch (NumberFormatException e) {
// something wrong with this line in the script
}
} else if (s.indexOf(EVENT_KEYWORD_POINTER) >= 0 ||
s.indexOf(EVENT_KEYWORD_TRACKBALL) >= 0) {
// trackball/pointer event
try {
long downTime = Long.parseLong(st.nextToken());
long eventTime = Long.parseLong(st.nextToken());
int action = Integer.parseInt(st.nextToken());
float x = Float.parseFloat(st.nextToken());
float y = Float.parseFloat(st.nextToken());
float pressure = Float.parseFloat(st.nextToken());
float size = Float.parseFloat(st.nextToken());
int metaState = Integer.parseInt(st.nextToken());
float xPrecision = Float.parseFloat(st.nextToken());
float yPrecision = Float.parseFloat(st.nextToken());
int device = Integer.parseInt(st.nextToken());
int edgeFlags = Integer.parseInt(st.nextToken());

int type = MonkeyEvent.EVENT_TYPE_TRACKBALL;
if (s.indexOf("Pointer") > 0) {
type = MonkeyEvent.EVENT_TYPE_POINTER;
}
MonkeyMotionEvent e = new MonkeyMotionEvent(type, downTime, eventTime,
action, x, y, pressure, size, metaState, xPrecision, yPrecision,
device, edgeFlags);
mQ.addLast(e);
} catch (NumberFormatException e) {
// we ignore this event
}
} else if (s.indexOf(EVENT_KEYWORD_FLIP) >= 0) {
boolean keyboardOpen = Boolean.parseBoolean(st.nextToken());
MonkeyFlipEvent e = new MonkeyFlipEvent(keyboardOpen);
mQ.addLast(e);
}
}

private void closeFile() {
mFileOpened = false;
if (THIS_DEBUG) {
System.out.println("closing script file");
}

try {
mFStream.close();
mInputStream.close();
} catch (IOException e) {
System.out.println(e);
}
}

/**
* add home key press/release event to the queue
*/
private void addHomeKeyEvent() {
MonkeyKeyEvent e = new MonkeyKeyEvent(KeyEvent.ACTION_DOWN,
KeyEvent.KEYCODE_HOME);
mQ.addLast(e);
e = new MonkeyKeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_HOME);
mQ.addLast(e);
}

/**
* read next batch of events from the provided script file
* @return true if success
*/
private boolean readNextBatch() {
String sLine = null;
int readCount = 0;

if (THIS_DEBUG) {
System.out.println("readNextBatch(): reading next batch of events");
}

if (!mFileOpened) {
if (!readScriptHeader()) {
closeFile();
return false;
}
resetValue();

/*
* In order to allow the Monkey to replay captured events multiple times
* we need to define a default start UI, which is the home screen
* Otherwise, it won't be accurate since the captured events
* could end anywhere
*/
addHomeKeyEvent();
}

try {
while (readCount++ < MAX_ONE_TIME_READS &&
(sLine = mBufferReader.readLine()) != null) {
sLine = sLine.trim();
processLine(sLine);
}
} catch (IOException e) {
System.err.println(e);
return false;
}

if (sLine == null) {
// to the end of the file
if (THIS_DEBUG) {
System.out.println("readNextBatch(): to the end of file");
}
closeFile();
}
return true;
}

/**
* sleep for a period of given time, introducing latency among events
* @param time to sleep in millisecond
*/
private void needSleep(long time) {
if (time < 1) {
return;
}
try {
Thread.sleep(time);
} catch (InterruptedException e) {
}
}

/**
* check whether we can successfully read the header of the script file
*/
public boolean validate() {
boolean b = readNextBatch();
if (mVerbose > 0) {
System.out.println("Replaying " + mEventCountInScript +
" events with speed " + mSpeed);
}
return b;
}

public void setVerbose(int verbose) {
mVerbose = verbose;
}

/**
* adjust key downtime and eventtime according to both
* recorded values and current system time
* @param e KeyEvent
*/
private void adjustKeyEventTime(MonkeyKeyEvent e) {
if (e.getEventTime() < 0) {
return;
}
long thisDownTime = 0;
long thisEventTime = 0;
long expectedDelay = 0;

if (mLastRecordedEventTime <= 0) {
// first time event
thisDownTime = SystemClock.uptimeMillis();
thisEventTime = thisDownTime;
} else {
if (e.getDownTime() != mLastRecordedDownTimeKey) {
thisDownTime = e.getDownTime();
} else {
thisDownTime = mLastExportDownTimeKey;
}
expectedDelay = (long) ((e.getEventTime() -
mLastRecordedEventTime) * mSpeed);
thisEventTime = mLastExportEventTime + expectedDelay;
// add sleep to simulate everything in recording
needSleep(expectedDelay - SLEEP_COMPENSATE_DIFF);
}
mLastRecordedDownTimeKey = e.getDownTime();
mLastRecordedEventTime = e.getEventTime();
e.setDownTime(thisDownTime);
e.setEventTime(thisEventTime);
mLastExportDownTimeKey = thisDownTime;
mLastExportEventTime = thisEventTime;
}

/**
* adjust motion downtime and eventtime according to both
* recorded values and current system time
* @param e KeyEvent
*/
private void adjustMotionEventTime(MonkeyMotionEvent e) {
if (e.getEventTime() < 0) {
return;
}
long thisDownTime = 0;
long thisEventTime = 0;
long expectedDelay = 0;

if (mLastRecordedEventTime <= 0) {
// first time event
thisDownTime = SystemClock.uptimeMillis();
thisEventTime = thisDownTime;
} else {
if (e.getDownTime() != mLastRecordedDownTimeMotion) {
thisDownTime = e.getDownTime();
} else {
thisDownTime = mLastExportDownTimeMotion;
}
expectedDelay = (long) ((e.getEventTime() -
mLastRecordedEventTime) * mSpeed);
thisEventTime = mLastExportEventTime + expectedDelay;
// add sleep to simulate everything in recording
needSleep(expectedDelay - SLEEP_COMPENSATE_DIFF);
}

mLastRecordedDownTimeMotion = e.getDownTime();
mLastRecordedEventTime = e.getEventTime();
e.setDownTime(thisDownTime);
e.setEventTime(thisEventTime);
mLastExportDownTimeMotion = thisDownTime;
mLastExportEventTime = thisEventTime;
}

/**
* if the queue is empty, we generate events first
* @return the first event in the queue, if null, indicating the system crashes
*/
public MonkeyEvent getNextEvent() {
long recordedEventTime = -1;

if (mQ.isEmpty()) {
readNextBatch();
}
MonkeyEvent e = mQ.getFirst();
mQ.removeFirst();

if (e.getEventType() == MonkeyEvent.EVENT_TYPE_KEY) {
adjustKeyEventTime((MonkeyKeyEvent) e);
} else if (e.getEventType() == MonkeyEvent.EVENT_TYPE_POINTER ||
e.getEventType() == MonkeyEvent.EVENT_TYPE_TRACKBALL) {
adjustMotionEventTime((MonkeyMotionEvent) e);
}
return e;
}
}

To write monkey script the first thing you have to do is write a small JAVA application. You can use hello world sample application. You can build it using Eclipse Java IDE and Android Windows SDK. Inside your sample application open the main activity JAVA file and add some code to enumerate the activity of an APK of your choice assuming this application is not presently running. If the application you'd like to automate is running, then use getPackageInfo(), instead of getPackageArchiveInfo().

See code bellow. Run the "rever engineering" application in the debugger with the device attached to your PC/Laptop with USB cable so that you can step into the code.

import android.app.Activity;
import android.content.ComponentName;
import android.content.Context;
import android.content.pm.ActivityInfo;
import android.content.pm.ApplicationInfo;
import android.content.pm.PackageInfo;
import android.content.pm.PackageManager;
import android.util.Log;

public class ReverseEngineering extends Activity
{
static final String TAG = "ReverseEngineering:Log";

/** onStart() is called when the application is on the foreground.
* We shouldn't use onCreate() which is called only once in the phone's process life cycle.
* This function will override what is available in the parent Activity class. */
@Override
public void onStart()
{
// Keep on starting.
super.onStart();
setContentView(R.layout.main);

PackageManager pm = getPackageManager();

PackageInfo info = pm.getPackageArchiveInfo("/data/app/com.company.application-1.apk", PackageManager.GET_ACTIVITIES);
if(info != null){
ApplicationInfo appInfo = info.applicationInfo;
String appName = pm.getApplicationLabel(appInfo).toString();
String packageName = appInfo.packageName;
Log.d(TAG, " appName =" + appName);
Log.d(TAG, " packageName =" + packageName);
}

ActivityInfo[] list = pm.getPackageArchiveInfo("/data/app/com.company.application-1.apk", PackageManager.GET_ACTIVITIES).activities;
for(int i = 0;i< list.length; i++){
String strName = list[i].getClass().getName();
Log.d(TAG, " ActivityInfo =" + strName);
}

Once you know the name of the activity you can invoke, write a small script.
The following script named monkey_script.txt will execute a package and
its activity.

captureDispatchPointer is a tap down action followed by a tap up action at the coordinate x and y EG X 146 and Y 165 as if you were using the touch screen with your finger. To find out the coordinate for a particular screen on the device you need to capture the screen using ddms (android tool) and open the screen with your favorites image editor. Mine is PhotoShop CS5 or Gimp if you don't have that much $ to spend. Development on Android is free after all.

# KEYEVENT http://developer.android.com/reference/android/view/KeyEvent.html# Start of Script
type= user
count= 49
speed= 1.0
start data >>
LaunchActivity(com.company.application.Activity, com.company.application.Activity)
UserWait(2000)
# first screen
captureDispatchPointer(5109520,5109520,0,146,165,0,0,0,0,0,0,0);
captureDispatchPointer(5109521,5109521,1,146,165,0,0,0,0,0,0,0);
UserWait(5000)
# second screen
captureDispatchPointer(5109520,5109520,0,117,268,0,0,0,0,0,0,0);
captureDispatchPointer(5109521,5109521,1,117,268,0,0,0,0,0,0,0);
# second screen selection dialog autoclose on selection
UserWait(2000)
# now access an other screen
captureDispatchPointer(5109520,5109520,0,117,358,0,0,0,0,0,0,0);
captureDispatchPointer(5109521,5109521,1,117,358,0,0,0,0,0,0,0);
UserWait(2000)
# access a selection dialog with only a cancel button. Dialog will autoclose on tap down
captureDispatchPointer(5109520,5109520,0,117,177,0,0,0,0,0,0,0);
captureDispatchPointer(5109521,5109521,1,117,177,0,0,0,0,0,0,0);
UserWait(2000)

A more complex script with android keypad input

# KEYEVENT http://developer.android.com/reference/android/view/KeyEvent.html
# Start of Script
type= user
count= 49
speed= 1.0
start data >>
LaunchActivity(com.mpowerlabs.coin.android, com.mpowerlabs.coin.android.LoginActivity)
# 3120021258
DispatchPress(KEYCODE_3)
UserWait(200)
DispatchPress(KEYCODE_1)
UserWait(200)
DispatchPress(KEYCODE_3)
UserWait(200)
DispatchPress(KEYCODE_5)
UserWait(200)
DispatchPress(KEYCODE_0)
UserWait(200)
DispatchPress(KEYCODE_2)
UserWait(200)
DispatchPress(KEYCODE_1)
UserWait(200)
DispatchPress(KEYCODE_2)
UserWait(200)
DispatchPress(KEYCODE_5)
UserWait(200)
DispatchPress(KEYCODE_8)
UserWait(200)
# Pin 12345
DispatchPress(KEYCODE_DPAD_DOWN)
UserWait(250)
DispatchPress(KEYCODE_1)
UserWait(200)
DispatchPress(KEYCODE_2)
UserWait(200)
DispatchPress(KEYCODE_3)
UserWait(200)
DispatchPress(KEYCODE_4)
UserWait(200)
DispatchPress(KEYCODE_5)
UserWait(200)
# Down and enter
DispatchPress(KEYCODE_DPAD_DOWN)
UserWait(250)
DispatchPress(KEYCODE_ENTER)

To execute the script on the device you need to create a batch file.

1 to make sure the application is deploy on the device
2 push the script
3 execute the script

adb root
adb install com.company.application.apk
adb push monkey_script.txt /sdcard/monkey_script.txt
adb shell monkey -p com.company.application -v -v -v -f /sdcard/monkey_script.txt 1

Hope you'll find this tutorial usefull !

Android.mk

2011-06-14T17:37:00.001-07:00

Android.mk file syntax specification

Introduction:
-------------

This document describes the syntax of Android.mk build file
written to describe your C and C++ source files to the Android
NDK. To understand what follows, it is assumed that you have
read the docs/OVERVIEW.TXT file that explains their role and
usage.

Overview:
---------

An Android.mk file is written to describe your sources to the
build system. More specifically:

- The file is really a tiny GNU Makefile fragment that will be
parsed one or more times by the build system. As such, you
should try to minimize the variables you declare there and
do not assume that anything is not defined during parsing.

- The file syntax is designed to allow you to group your
sources into 'modules'. A module is one of the following:

- a static library
- a shared library

Only shared libraries will be installed/copied to your
application package. Static libraries can be used to generate
shared libraries though.

You can define one or more modules in each Android.mk file,
and you can use the same source file in several modules.

- The build system handles many details for you. For example, you
don't need to list header files or explicit dependencies between
generated files in your Android.mk. The NDK build system will
compute these automatically for you.

This also means that, when updating to newer releases of the NDK,
you should be able to benefit from new toolchain/platform support
without having to touch your Android.mk files.

Note that the syntax is *very* close to the one used in Android.mk files
distributed with the full open-source Android platform sources. While
the build system implementation that uses them is different, this is
an intentional design decision made to allow reuse of 'external' libraries'
source code easier for application developers.

Simple example:
---------------

Before describing the syntax in details, let's consider the simple
"hello JNI" example, i.e. the files under:

apps/hello-jni/project

Here, we can see:

- The 'src' directory containing the Java sources for the
sample Android project.

- The 'jni' directory containing the native source for
the sample, i.e. 'jni/hello-jni.c'

This source file implements a simple shared library that
implements a native method that returns a string to the
VM application.

- The 'jni/Android.mk' file that describes the shared library
to the NDK build system. Its content is:

---------- cut here ------------------
LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

LOCAL_MODULE := hello-jni
LOCAL_SRC_FILES := hello-jni.c

include $(BUILD_SHARED_LIBRARY)
---------- cut here ------------------

Now, let's explain these lines:

LOCAL_PATH := $(call my-dir)

An Android.mk file must begin with the definition of the LOCAL_PATH variable.
It is used to locate source files in the development tree. In this example,
the macro function 'my-dir', provided by the build system, is used to return
the path of the current directory (i.e. the directory containing the
Android.mk file itself).

include $(CLEAR_VARS)

The CLEAR_VARS variable is provided by the build system and points to a
special GNU Makefile that will clear many LOCAL_XXX variables for you
(e.g. LOCAL_MODULE, LOCAL_SRC_FILES, LOCAL_STATIC_LIBRARIES, etc...),
with the exception of LOCAL_PATH. This is needed because all build
control files are parsed in a single GNU Make execution context where
all variables are global.

LOCAL_MODULE := hello-jni

The LOCAL_MODULE variable must be defined to identify each module you
describe in your Android.mk. The name must be *unique* and not contain
any spaces. Note that the build system will automatically add proper
prefix and suffix to the corresponding generated file. In other words,
a shared library module named 'foo' will generate 'libfoo.so'.

IMPORTANT NOTE:
If you name your module 'libfoo', the build system will not
add another 'lib' prefix and will generate libfoo.so as well.
This is to support Android.mk files that originate from the
Android platform sources, would you need to use these.

LOCAL_SRC_FILES := hello-jni.c

The LOCAL_SRC_FILES variables must contain a list of C and/or C++ source
files that will be built and assembled into a module. Note that you should
not list header and included files here, because the build system will
compute dependencies automatically for you; just list the source files
that will be passed directly to a compiler, and you should be good.

Note that the default extension for C++ source files is '.cpp'. It is
however possible to specify a different one by defining the variable
LOCAL_DEFAULT_CPP_EXTENSION. Don't forget the initial dot (i.e. '.cxx'
will work, but not 'cxx').

include $(BUILD_SHARED_LIBRARY)

The BUILD_SHARED_LIBRARY is a variable provided by the build system that
points to a GNU Makefile script that is in charge of collecting all the
information you defined in LOCAL_XXX variables since the latest
'include $(CLEAR_VARS)' and determine what to build, and how to do it
exactly. There is also BUILD_STATIC_LIBRARY to generate a static library.

There are more complex examples under apps/, with commented
Android.mk files that you can look at.

Reference:
----------

This is the list of variables you should either rely on or define in
an Android.mk. You can define other variables for your own usage, but
the NDK build system reserves the following variable names:

- names that begin with LOCAL_ (e.g. LOCAL_MODULE)
- names that begin with PRIVATE_, NDK_ or APP_ (used internally)
- lower-case names (used internally, e.g. 'my-dir')

If you need to define your own convenience variables in an Android.mk
file, we recommend using the MY_ prefix, for a trivial example:

---------- cut here ------------------
MY_SOURCES := foo.c
ifneq ($(MY_CONFIG_BAR),)
MY_SOURCES += bar.c
endif

LOCAL_SRC_FILES += $(MY_SOURCES)
---------- cut here ------------------

So, here we go:

NDK-provided variables:
- - - - - - - - - - - -

These GNU Make variables are defined by the build system before
your Android.mk file is parsed. Note that under certain circumstances
the NDK might parse your Android.mk several times, each with different
definition for some of these variables.

CLEAR_VARS
Points to a build script that undefines nearly all LOCAL_XXX variables
listed in the "Module-description" section below. You must include
the script before starting a new module, e.g.:

include $(CLEAR_VARS)

BUILD_SHARED_LIBRARY
Points to a build script that collects all the information about the
module you provided in LOCAL_XXX variables and determines how to build
a target shared library from the sources you listed. Note that you
must have LOCAL_MODULE and LOCAL_SRC_FILES defined, at a minimum before
including this file. Example usage:

include $(BUILD_SHARED_LIBRARY)

note that this will generate a file named lib$(LOCAL_MODULE).so

BUILD_STATIC_LIBRARY
A variant of BUILD_SHARED_LIBRARY that is used to build a target static
library instead. Static libraries are not copied into your
project/packages but can be used to build shared libraries (see
LOCAL_STATIC_LIBRARIES and LOCAL_STATIC_WHOLE_LIBRARIES described below).
Example usage:

include $(BUILD_STATIC_LIBRARY)

Note that this will generate a file named lib$(LOCAL_MODULE).a

TARGET_ARCH
Name of the target CPU architecture as it is specified by the
full Android open-source build. This is 'arm' for any ARM-compatible
build, independent of the CPU architecture revision.

TARGET_PLATFORM
Name of the target Android platform when this Android.mk is parsed.
For now, only 'android-3' is supported, which corresponds to the
Android 1.5 platform.

TARGET_ARCH_ABI
Name of the target CPU+ABI when this Android.mk is parsed.
For now, only 'arm' is supported, which really means the following:

ARMv5TE or higher CPU, with 'softfloat' floating point support

Other target ABIs will be introduced in future releases of the NDK
and will have a different name. Note that all ARM-based ABIs will
have 'TARGET_ARCH' defined to 'arm', but may have different
'TARGET_ARCH_ABI'

TARGET_ABI
The concatenation of target platform and abi, it really is defined
as $(TARGET_PLATFORM)-$(TARGET_ARCH_ABI) and is useful when you want
to test against a specific target system image for a real device.

By default, this will be 'android-3-arm'

NDK-provided function macros:
- - - - - - - - - - - - - - -

The following are GNU Make 'function' macros, and must be evaluated
by using '$(call )'. They return textual information.

my-dir
Returns the path of the current Android.mk's directory, relative
to the top of the NDK build system. This is useful to define
LOCAL_PATH at the start of your Android.mk as with:

LOCAL_PATH := $(call my-dir)

all-subdir-makefiles
Returns a list of Android.mk located in all sub-directories of
the current 'my-dir' path. For example, consider the following
hierarchy:

sources/foo/Android.mk
sources/foo/lib1/Android.mk
sources/foo/lib2/Android.mk

If sources/foo/Android.mk contains the single line:

include $(call all-subdir-makefiles)

Then it will include automatically sources/foo/lib1/Android.mk and
sources/foo/lib2/Android.mk

This function can be used to provide deep-nested source directory
hierarchies to the build system. Note that by default, the NDK
will only look for files in sources/*/Android.mk

this-makefile
Returns the path of the current Makefile (i.e. where the function
is called).

parent-makefile
Returns the path of the parent Makefile in the inclusion tree,
i.e. the path of the Makefile that included the current one.

grand-parent-makefile
Guess what...

Module-description variables:
- - - - - - - - - - - - - - -

The following variables are used to describe your module to the build
system. You should define some of them between an 'include $(CLEAR_VARS)'
and an 'include $(BUILD_XXXXX)'. As written previously, $(CLEAR_VARS) is
a script that will undefine/clear all of these variables, unless explicitely
noted in their description.

LOCAL_PATH
This variable is used to give the path of the current file.
You MUST define it at the start of your Android.mk, which can
be done with:

LOCAL_PATH := $(call my-dir)

This variable is *not* cleared by $(CLEAR_VARS) so only one
definition per Android.mk is needed (in case you define several
modules in a single file).

LOCAL_MODULE
This is the name of your module. It must be unique among all
module names, and shall not contain any space. You MUST define
it before including any $(BUILD_XXXX) script.

The module name determines the name of generated files, e.g.
lib.so for a shared library module named . However
you should only refer to other modules with their 'normal'
name (e.g. ) in your NDK build files (either Android.mk
or Application.mk)

LOCAL_SRC_FILES
This is a list of source files that will be built for your module.
Only list the files that will be passed to a compiler, since the
build system automatically computes dependencies for you.

Note that source files names are all relative to LOCAL_PATH and
you can use path components, e.g.:

LOCAL_SRC_FILES := foo.c \
toto/bar.c

NOTE: Always use Unix-style forward slashes (/) in build files.
Windows-style back-slashes will not be handled properly.

LOCAL_CPP_EXTENSION
This is an optional variable that can be defined to indicate
the file extension of C++ source files. The default is '.cpp'
but you can change it. For example:

LOCAL_CPP_EXTENSION := .cxx

LOCAL_C_INCLUDES
An optional list of paths, relative to the NDK *root* directory,
which will be appended to the include search path when compiling
all sources (C, C++ and Assembly). For example:

LOCAL_C_INCLUDES := sources/foo

Or even:

LOCAL_C_INCLUDES := $(LOCAL_PATH)/../foo

These are placed before any corresponding inclusion flag in
LOCAL_CFLAGS / LOCAL_CPPFLAGS

LOCAL_CFLAGS
An optional set of compiler flags that will be passed when building
C *and* C++ source files.

This can be useful to specify additionnal macro definitions or
compile options.

IMPORTANT: Try not to change the optimization/debugging level in
your Android.mk, this can be handled automatically for
you by specifying the appropriate information in
your Application.mk, and will let the NDK generate
useful data files used during debugging.

NOTE: In android-ndk-1.5_r1, the corresponding flags only applied
to C source files, not C++ ones. This has been corrected to
match the full Android build system behaviour. (You can use
LOCAL_CPPFLAGS to specify flags for C++ sources only now).

LOCAL_CXXFLAGS
An alias for LOCAL_CPPFLAGS. Note that use of this flag is obsolete
as it may disappear in future releases of the NDK.

LOCAL_CPPFLAGS
An optional set of compiler flags that will be passed when building
C++ source files *only*. They will appear after the LOCAL_CFLAGS
on the compiler's command-line.

NOTE: In android-ndk-1.5_r1, the corresponding flags applied to
both C and C++ sources. This has been corrected to match the
full Android build system. (You can use LOCAL_CFLAGS to specify
flags for both C and C++ sources now).

LOCAL_STATIC_LIBRARIES
The list of static libraries modules (built with BUILD_STATIC_LIBRARY)
that should be linked to this module. This only makes sense in
shared library modules.

LOCAL_SHARED_LIBRARIES
The list of shared libraries *modules* this module depends on at runtime.
This is necessary at link time and to embed the corresponding information
in the generated file.

Note that this does not append the listed modules to the build graph,
i.e. you should still add them to your application's required modules
in your Application.mk

LOCAL_LDLIBS
The list of additional linker flags to be used when building your
module. This is useful to pass the name of specific system libraries
with the "-l" prefix. For example, the following will tell the linker
to generate a module that links to /system/lib/libz.so at load time:

LOCAL_LDLIBS := -lz

See docs/STABLE-APIS.TXT for the list of exposed system libraries you
can linked against with this NDK release.

LOCAL_ALLOW_UNDEFINED_SYMBOLS
By default, any undefined reference encountered when trying to build
a shared library will result in an "undefined symbol" error. This is a
great help to catch bugs in your source code.

However, if for some reason you need to disable this check, set this
variable to 'true'. Note that the corresponding shared library may fail
to load at runtime.

LOCAL_ARM_MODE
By default, ARM target binaries will be generated in 'thumb' mode, where
each instruction are 16-bit wide. You can define this variable to 'arm'
if you want to force the generation of the module's object files in
'arm' (32-bit instructions) mode. E.g.:

LOCAL_ARM_MODE := arm

Note that you can also instruct the build system to only build specific
sources in arm mode by appending an '.arm' suffix to its source file
name. For example, with:

LOCAL_SRC_FILES := foo.c bar.c.arm

Tells the build system to always compile 'bar.c' in arm mode, and to
build foo.c according to the value of LOCAL_ARM_MODE.

NOTE: Setting APP_OPTIM to 'debug' in your Application.mk will also force
the generation of ARM binaries as well. This is due to bugs in the
toolchain debugger that don't deal too well with thumb code.

Building Video Lan Player for Android Tablet

2011-06-13T20:14:00.000-07:00

http://wiki.videolan.org/AndroidCompile

PDF Processing with Perl to include in Electric Cloud

2011-06-03T15:37:00.000-07:00

I personally love Electric Commander from Electric cloud when it comes to run automated build. Electric Commander comes with a very good Procedure and Steps engine which can integrate on Multiple agent node and be able to execute perl script.
At the end of the build it is always recommanded to generate a nice report sometimes after running complex automation test.

PDF Packages

I like PDF::Reuse, but there are several other options for PDF creation and manipulation on the CPAN.

PDF::API2, by Alfred Reibenschuh, is actively maintained. It is the package of choice if creating new PDF documents from scratch.
PDF::API2::Simple, by Red Tree Systems, is a wrapper over the PDF::API2 module for users who find the PDF::API2 module to difficult to use.
Text::PDF, by Martin Hosken, can work on more than PDF file at the same time and has Truetype font support.
CAM::PDF, by Clotho Advanced Media, is like PDF::Reuse more focused on reading and manipulating existing PDF documents. However, it can work on multiple files at the same time. Use it if you need more features than PDF::Reuse actually provides.
Conclusions
PDF::Reuse is a well-written and well-documented package, which makes it easy to create, combine, and change existing PDF documents. The two sample applications show some of its capabilities. Two limitations should be mentioned however, PDF::Reuse can't reuse existing bookmarks, and after combining different PDF documents some of the inner document hyperlinks might stop working properly.

TIOBE Programming Community Index

2011-05-24T18:20:00.001-07:00

May Headline: C# and Objective-C remain the strongest climbers

http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html

Where is Action Script ??

http://www.tiobe.com/index.php/content/paperinfo/tpci/tpci_definition.htm

Apple/Google/Microsoft

2011-05-16T20:41:00.000-07:00

http://brooksreview.net/2011/05/ballmer/

URL Escape Codes

2011-05-16T14:49:00.000-07:00

When encoding a URL, a character may not be available on the keyboard. Other times, the character of a URL might not
be usable in contexts where it may conflict with a reserved character. In either case, the character can be encoded
with a % followed by its ASCII hexadecimal equivalent code.

Android Code Bar is Sweet

2011-04-08T14:31:00.001-07:00

Love it!

Hexacopter in Cameroon

2011-02-20T12:22:00.001-08:00

Simply excellent !

http://vimeo.com/18873955

Execute a Java application on Windows using a batch file with command line arguments

2011-01-13T12:08:00.000-08:00

It is tricky to write batch file aimed to execute a java application on windows if you want to process command line arguments coming from the Windows OS. Windows will report path with \ and add some " automatically when draging a file or a path on the batch file itself. While when reunning from the command line you can past a windows path using the clipboard.

On the other end we all know that java is much more happy with / inside file path.

So assuming %1 is the argument you will receive from the OS, you need to replace to / and then make sure you remove the quote since you are adding the " in the batch file.

REM Replace - Replace a substring using string substitution
echo %1
set str=%1
echo.%str%
set str=%str:\=/%
echo.%str%
REM Trim Quotes - Remove surrounding quotes via FOR command
for /f "useback tokens=*" %%a in ('%str%') do set str=%%~a

java com.mycompany.MYAPP --arg1 --arg2 --input-file="%str%" --output-file="%str%.out"

more tips at

http://www.dostips.com/

Free ebook: Programming Windows Phone 7, by Charles Petzold

2010-11-15T15:23:00.000-08:00

http://blogs.msdn.com/b/microsoft_press/archive/2010/10/28/free-ebook-programming-windows-phone-7-by-charles-petzold.aspx

This book is a gift from the Windows Phone 7 team at Microsoft to the programming community, and Charles Petzold has been a part of it. Within the pages that follow, Charles Petzold shows you the basics of writing applications for Windows Phone 7 using the C# programming language with the Silverlight and XNA 2D frameworks.

This book is divided into three parts. The first part discusses basic concepts of Windows Phone 7 programming using example programs that target both Silverlight and the XNA framework. It is likely that many Windows Phone 7 developers will choose either one platform or the other, but Charles Petzold think it’s important for all developers who have at least a little knowledge of the alternative to their chosen path.

The second part of this book focuses entirely on Silverlight, and the third part on XNA 2D. For your convenience, the chapters in each part build upon previous knowledge in a progressive tutorial narrative, and hence are intended to be read sequentially.

Facebook etc... Do you still want to trust privacy ????

2010-10-25T16:00:00.000-07:00

http://codebutler.com/firesheep

When logging into a website you usually start by submitting your username and password. The server then checks to see if an account matching this information exists and if so, replies back to you with a "cookie" which is used by your browser for all subsequent requests.
It's extremely common for websites to protect your password by encrypting the initial login, but surprisingly uncommon for websites to encrypt everything else. This leaves the cookie (and the user) vulnerable. HTTP session hijacking (sometimes called "sidejacking") is when an attacker gets a hold of a user's cookie, allowing them to do anything the user can do on a particular website. On an open wireless network, cookies are basically shouted through the air, making these attacks extremely easy.

This is a widely known problem that has been talked about to death, yet very popular websites continue to fail at protecting their users. The only effective fix for this problem is full end-to-end encryption, known on the web as HTTPS or SSL. Facebook is constantly rolling out new "privacy" features in an endless attempt to quell the screams of unhappy users, but what's the point when someone can just take over an account entirely? Twitter forced all third party developers to use OAuth then immediately released (and promoted) a new version of their insecure website. When it comes to user privacy, SSL is the elephant in the room.

WxWidget/GTK vs QT

2010-08-13T11:37:00.000-07:00

wxWidgets

wxWidgets can be downloaded at http://www.wxwidgets.org/
and current stable build is available at http://sourceforge.net/projects/wxwindows/files/2.8.11

wxWidgets not only works for C++, but also has bindings for python, perl, java, lua, eiffel, C# (.NET), basic, ruby and even javascript (see General Information for bindings).
It is one of the most complete GUI toolkits. There are many utility classes.
There is a lot of documentation (though a bit fragmented in places).
Free for personal and commercial use.
Whenever possible, wxWidgets uses the native platform SDK. This means that a program compiled on Windows will have the look and feel of a Windows program, and when compiled on a Linux machine, it will get the look and feel of a Linux program.
A positive side effect is that wxWidgets is thus more likely to look, behave and feel native - sometimes including native features for free (e.g. possibility to have spellchecking built-in in all text areas on OS X).
A negative side effect of this is that it is more likely that the behaviour is different between platforms; toolkits where widgets are lightweight lose some of the native aspect but also minimize platform-specific code (hence minimizing the risk of different behaviour from platform to platform and also minimizing the risk of platform-specific bugs). Concentrating on native looks also mean wx may not be best suited for applications that want a customized look instead of the system's theme.

Windows Build extract everything under

C:\wxWidgets-2.8.11

Go to C:\wxWidgets-2.8.11\build\msw

open wx.dsw with Visual Studio 2008. Visual Studio will then ask you if
you want to convert the Visual Studio 6 project to visual studio vcproj.
Select yes to all. By default wxWidgets will target win32 platform but
you can add x64 platform.

All lib will be generated under

C:\wxWidgets-2.8.11\lib\vc_lib

wxWidget works well with GTK+ because GTK is one of the choice to build wxWidget on Linux.

GTK+

http://www.gtk.org
GTK+, originally the Gimp toolkit, is a LGPL C-language GUI library for Unix systems.
It has been ported to Windows, VMS, and other systems (MacOS X currently possible through Apple's X11.app, native version in development) using the same API. However, primary development and focus is for Unix, with multi-platform development mostly as an afterthought.
GTK+ is the primary library used to construct user interfaces in GNOME.
Unlike wxWidgets, GTK+ supports C (and there is a C++ wrapper called GTKMM, http://www.gtkmm.org )
The API is quite well developed, and includes safe casting and other things; but C++ has these built in.
It's built on top of glib, a general-purpose library (similar in some ways to the C++ STL -- it provides a few data structures, functions to help memory management, etc).
It looks the same on all platforms, except Windows XP, where it tries (with some success) to get Windows' native look and feel with the Wimp theme, which uses UxTheme. However, it's still very much a Unix library.

Building GTK+ on Windows requires MinGW and MSys which might mot be an easy task
some

Stable release for GTK+ is available on:

GNU/Linux and Unix
Windows (32-bit) and 64-bit
OSX

For windows http://www.gtk.org/download-windows.html
there are all-in-one bundles of the GTK+ stack including 3rd-party dependencies, both of GTK+ 2.16 and 2.20. The bundles contain both binaries and a lot of developer files, many of which are relatively irrelevant. If you intend to redistribute the GTK+ run-time, you need to figure out which files you can leave out yourself.

Download 2.20 bundle from http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/
and extract everything under

C:\gtk\gtk+-bundle_2.20.0-20100406_win32

Using CMake

CMake is a great way to generate Visual Studio 2008 solution for wxWidgets/GTK UI.
CMake GUI will help you browse for all library include path and library.
Cmake will update the build folder and cache all missing entry inside
CMakeCache.txt

# This is the CMakeCache file.
# For build in directory: c:/Dev/Project/Source/build
# It was generated by CMake: C:/Program Files (x86)/CMake 2.8/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUI's for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

When clicking on generate a solution for your compiler EG Visual Studio 2008
will be generated. From there you can open the solution and step into wxWidget/GTK UI.
GTK offer the advantage to be stable in term of API which means that if you build a UI using GTK today it should work 5 years from now.

Project using GTK

GNOME Desktop
Openmoko
Maemo surf tablet
GIMP on Linux and Windows and Mac
VMWare workstation
Inkscape Graphics Editor
Gnumeric

and earlier
GTK+ on BeOS and GTK+ using DirectFB

On the other hand Trolltek team made quite some changes between QT 3 and QT 4 which require some work to translate old code to new code. See Moving from Qt 3 to Qt 4 http://doc.trolltech.com/4.3/porting4-overview.html
When starting a project from scratch QT 4 would be a good solution.

QT

Both Qt (http://www.qtsoftware.com/) and wxWidgets have many non-GUI-related classes, such as date/time, containers, networking and OpenGL functionality.
Qt4.5 is available on MS Windows, Mac, and GNU/Linux under the LGPL and under a commercial license. All ports of wxWidgets are distributed under a permissive modified (but explicitly OSI-approved) LGPL, which allows development and distribution of proprietary applications without license costs.
Qt doesn't have true native ports like wxWidgets does. What we mean by this is that even though Qt draws them quite realistically, Qt draws its own widgets on each platform. It's worth mentioning though that Qt comes with special styles for Mac OS X and MS Windows XP and Vista that use native APIs (Appeareance Manager on Mac OS X, UxTheme on Windows XP) for drawing standard widget primitives (e.g. scrollbars or buttons) exactly like any native application. Event handling, the resulting visual feedback and widget layout are always implemented by Qt.
An approach similar to Qt's is achieved with wxUniversal.
It should be noted that on KDE and Qt for Embedded Linux platforms, Qt is the native GUI library.
Qt is used by several large projects like KDE (on the other hand, wxWidgets is used by projects like the AOL Communicator)
Qt makes extremely liberal use of virtual functions (QWidget, the base class of all widgets in Qt had 51 at last count), giving it a more OO design than wxWidgets (which uses a more MFC-like approach using macros). What this means is fewer lines of code in general when using Qt, but faster execution speed when using wxWidgets (although the degree to which this occurs depends on whom you ask).
Qt is used by IBM and Borland Kylix (discontinued): this should yield more reliability. However, it is rumoured that wxWidgets will be used in the next version of C++BuilderX.
Qt has a full-featured embeddable GUI (Qt for Embedded Linux) based on GNU/Linux with framebuffer. This means that once you have Linux with /dev/fb you are ready to run examples with no additional pains. Qt for Embedded Linux has a small footprint compared with X11.
There are numerous IDEs for Qt, QtDesigner, QtCreator, QDevelop, Edyuk as well as integrations with popular IDEs such as Visual Studio, Eclipse and XCode (though there are also several IDEs for wxWidgets).
Qt offers reliable commercial support (but so does wx, see http://www.wxwidgets.org/support/support.htm)
There is nothing to stop somebody writing a Qt-based implementation of wxWidgets, though wxWidgets applications can already be made to appear Qt-ish using wxGTK and GTK-Qt (this doesn’t work too good, though).

Internet Explorer 8 Automation with Flash content using VBScript on Windows 7 64 bit

2010-08-05T11:40:00.001-07:00

First of all running automation of Internet Explorer with Flash Content on a 64 bit OS is not easy because by default the OS will launch 64 bit version of Internet Explorer instead of the 32 bit version.

InternetExplorer.Application.vbs

Set objIE = CreateObject( "InternetExplorer.Application" )
' specify the IE settings
objIE.Navigate "http://www.actimus.com"
objIE.ToolBar = true
objIE.Resizable = False
objIE.StatusBar = False
objIE.Width = 800
objIE.Height = 600
' Make the window visible
objIE.Visible = True
WScript.Sleep 2000
'objIE.Refresh
'objIE.Quit
'Set objIE = Nothing

Will lead to the following message

Flash Player on 64-bit operating systems

Products affected
You might be on this page because you can't view content with the Flash Player. This is likely because your computer is running a 64-bit Web browser on a 64-bit operating system and you are trying to install Flash Player. Flash Player does not run in most 64-bit browsers. If you attempt to download the Flash Player in a 64-bit browser that does not support Flash Player, you will see a message from Adobe and a link back to this page. To install Flash Player, use a 32-bit Web browser on your 64-bit operating system. All major browsers are available in 32-bit versions and the Internet Explorer 32-bit browser is the default browser on Windows 64-bit systems.

There are two InternetExplorer.Application objects on x64-bit systems, one for x32 bit, the other for x64. By default, the x64 bit version is launched when you call the object, because by default the x64 bit wscript.exe is used. But you can also launch the x32 bit version of the object by using the x32 bit version of wscript.exe and passing the vbs url to it as an argument:

--------------------------------------------------

Set WshShell = CreateObject("WScript.Shell")
WshShell.Run("%windir%\SysWOW64\wscript.exe " & Chr(34) & "C:\test\InternetExplorer.Application.vbs" & Chr(34))

--------------------------------------------

The same works for all other x32 bit ActiveX objects in case you have to use them.

If you are using CoCreateInstance() of CLSID_InternetExplorer (to obtain an out-of-proc instance of iexplore.exe), you can pass one of these new flags in the dwClsCtx field to control which kind of server (32-bit or 64-bit) you get:

CLSCTX_ACTIVATE_32_BIT_SERVER = 0x40000, // Pick 32 bit server over 64 bit server
CLSCTX_ACTIVATE_64_BIT_SERVER = 0x80000 // Pick 64 bit server over 32 bit server

INTERACTIVE VIDEO IN FLASH CS5 USING ACTIVIDEO

2010-08-04T20:00:00.001-07:00

Activideo is a software created by a small company Actimus which can help you generate all what you need to produce the raw data needed for an interactive video experience. For more information about Activideo visit http://shop.actimus.com/ and to see how it work visit http://shop.actimus.com/demo/howitworks/. Some video tutorials are now available to explain you how to use Activideo
http://shop.actimus.com/demo/tutorials/ and user who purchase the software have access to online documentation.

Activideo is a fast and easy way to turn your videos into interactive presentations thanks to the export of well known Adobe XMP Metadata container. Activideo adds interactive hot spots (also called overlay sequences) to your videos. It is a simple but powerful concept: user-created hyperlinks within the video at various intervals and for specific areas in the video the same way hypertext is used on the Internet. These hyperlinks and interactive hotspots are exported into Adobe XMP RDF XML file format. Activideo could also produce Adobe Flash Action script 3 file along with a FLA and HTML template to be able to build your custom SWF with Adobe Flash CS4 or Adobe Flash CS5 thanks to a Plugin SDK. Actimus is about to release a live component for Flash CS5 which will provide the ability to validate/test each invisible hotspot by playing the video inside the Activideo Player.

Input Formats:

Activideo supports many input video file formats mostly any file format supported by the Direct Show software stack. Today, it currently supports MPEG1, MPEG2*, MPEG2-TS* transport streams including HD (720, 1080), DivX*, Microsoft AVI, Microsoft WMV* and WMV-HD *, Blueray * m2ts file, MKV, FLV and should work with WEBM (VP8). Activideo never modifies the original source video neither encode a Video. This tasks is left to Adobe Media Encoder and Adobe Bridge CS4 bundled with Adobe Flash CS4 Pro

Overlays:

The outlining of the overlay sequences is very precise because Activideo supports polygons with up to 100 vertices within a sequence. It performs linear interpolation of each vertex to transition smoothly from one shape to another. While the video is playing into Activideo, the user can move the current polygon location with the mouse visually to match any portion of the video associated and covered by polygon (and polygon are not visible on top of the final encoded Video. This is a human intervention process but it can be automated if the user doesn't plan to move the object on screen thanks to a very functional Wizard well suited to create a unique sequence and for example turn a logo encoded in the video into an hyperlink. To ease the overlay authoring process, a static logo sequence can be generate using the Creation Wizard.

Demo version:
Yes : Export of XMP
No : Project saving.
Yes : Wizard to create an interactive sequence available.
21 days of evaluation.

Full version:
Yes : Export XMP
Yes : Access to self registered COM Export Plug-ins available through Export As Menu
NO activation required.

Nokia QT with Visual Studio 2008 and MFC to QT

2010-07-30T16:52:00.000-07:00

DOWNLOAD QT SOURCE CODE
As the option to download only the Qt source code is a bit obfuscated on the current Nokia website, please follow these directions:

Go to http://qt.nokia.com/downloads and click the Go LGPL button.
Since you want only source code, look at the Qt: Framework Only column on the right. Click e.g. Download Qt libraries 4.6.3 for Windows (VS 2008, 194 MB) — choose the VS2008 one.

This starts the download for pre-built Qt. But we don’t want that as we will be building Qt ourselves. A page will appear with . Cancel the Save As dialog in your browser to cancel the binaries download you had clicked on, then click on this link, e.g. http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.3.zip
Unzip the file into e.g. c:\qt\4.6.3-vc. Please use a path with no embedded spaces, as the Qt build tools have issues with them.
SET ENVIRONMENT VARIABLES
Open Computer Properties | Advanced system settings | Environment Variables:

Edit environment variable to add: QTDIR = c:\qt\4.6.3-vc
Edit the PATH environment variable to add: %QTDIR%\bin
Either close all command prompts and Visual Studio instances, or reboot... the computer so the new command-line takes effect.
BUILD VC++ VERSION OF QT
Open a Microsoft Visual Studio 2008 Command Prompt, which is a command console with environment variables set for the specified VS. This is easily accomplished using Start | All Programs | Microsoft Visual Studio 2005 (or 2008) | Visual Studio Tools | Visual Studio 2005 (or 2008) Command Prompt.
Cleanup any previous build:
c:\> cd c:\qt\4.6.3-vc
c:\qt\4.6.3-vc> nmake distclean

c:\qt\4.6.3-vc> rm -rf tmp* // <– recursively remove all tmp\ folders and files
I use GNU Tools or even better Cygwin. Cygwin is very useful because you can also build other open source unix source code library including complicated ffmpeg that you may want to link to your QT project. You can download the gnuwin32 package maintenance utility on the sourceforge.net project portal. Cygwin can be downloaded here

3. Run Configure to target platform vc2008:

c:\qt\4.6.3-vc> configure -platform win32-msvc2008

Run Configure with no parameters to see a help screen. Configure generates nmake compatible makefiles to build all the Qt DLL’s, tools, and demos.

4. Run nmake to build.

c:\qt\4.6.3-vc> nmake

It will take awhile, but this grinds through building the specified Qt DLL’s, tools, and demos with Visual Studio.

INSTALL VISUAL STUDIO ADD-IN
The Qt Visual Studio Add-in is indispensible for developing Qt apps in Visual Studio. The Add-in has replaced the previous Qt Visual Studio Integration, which was only available to Commercial customers. Now the Add-in is used by both LPGL and Commercial licensees, and the Integration has been deprecated. While the Add-in does not allow integrated .ui editing (it instead launches Qt Designer to edit .ui files), it is fully supported and maintained by Nokia, whereas the Integration hadn’t been modified since the 4.3/4.4 timeframe.

Because Visual Studio Express does not allow add-ins, using these free versions of Visual Studio is not recommended for Qt development. You need at least Visual Studio Standard (Pro, Team System, etc. of course will also work).

1. Download and install the Qt Visual Studio Add-in to install the Qt plug-in into Visual Studio (both 2005 and 2008 are supported by the add-in).

2. Start Visual Studio.

3. Select menu Qt | Configure Qt Versions. Add c:\qt\4.6.3-vc.

4. Now Qt is fully functional, and you can use VS2008 to build Qt apps.

QT IN VISUAL STUDIO
1. See Qt menu item. Launch Qt Designer (the Resource editor) and Qt Linguist (the localization tool).

2. Create new Qt projects. File | New project, select Qt4 project.

3. Read Qt Help. Available from Help menu (Qt help is merged in with Visual Studio Help and viewed in Document Explorer.) Or, manually launch

C:\Qt\4.6.3-vc\bin\assistant.exe

4. The Whole Tomato Visual Assist X plug-in is highly recommended to develop Qt within Visual Studio

=====================================

How to generate a vc proj from a .pro QT file

there are two ways to do it.

1. On the command line with "qmake -tp vcapp -r yourProfile.pro"

Ensure that the QMAKESPEC environment variable is set to the appropriate value.
If you use Visual Studio 2008, then win32-msvc2008 is the correct value.

To set your environment variables in Windows, please see http://en.wikipedia.org/wiki/Environment_variable
Note that you may have to re-open a command window before your settings are changed.
To check that your PATH is set correctly:
C:\> qmake -v
QMake version: 2.01a
Using Qt version 4.6.3 in C:\Qt\4.6.3\lib
To see if QMAKESPEC is set correctly:
C:\> echo %QMAKESPEC%
%QMAKESPEC% // not set
win32-msvc2008 // set

2. With the Qt Visual Studio integration via the menu "Qt->Open From
.pro File" and save your project to also save the visual studio solution .sln file

==================== MFC AND QT

This walkthrough covers the migration of an MFC based program, generated by Microsoft Visual Studio's MFC Application Wizard, to the Qt toolkit using the Windows Migration Framework.

http://doc.trolltech.com/solutions/qtwinmigrate/winmigrate-walkthrough.html

and Nokia as a very nice landing page for this

http://qt.nokia.com/products/appdev/add-on-products/catalog/4/Windows/qtwinmigrate/

Anti Hacker Rules

2010-07-26T16:18:00.000-07:00

Anti-Hacker Standard Practices

The task of protecting your software from hackers is not easy. Put simply, complete and total protection - is not possible. If the hacker has access to your complete program, they can eventually break any and all protections you put in their way. This is not opinion - it is a fact. This is simply because they control the hardware at the most "intimate" level on which your program is running. As you know, a program is simply a set of instructions. Since the hacker controls the hardware on which those instructions are executed, eventually they will find the instructions in your program where your protections lie and simply change them.

A simple analogy illustrates this point: You have a lock on the front-door to your home don't you? When you leave the house, do you lock it? Of course you do. Why? You lock it because you don't want people to steal your stuff. If the door was unlocked, they would walk in and rob you. But, ask yourself, if they really wanted to get in, could they? If they had a crowbar and a chain-saw of course they could, sometimes they could simply kick in the door. If you had a great deal of valuables, you might get an alarm-system or a stronger door, but again, if they really wanted to rob you - they could. Software that resists hackers is just like a home with a locked door. You must make a reasonable attempt to keep your software safe since that will "keep the honest people honest", but at the same time, do not delude yourself into a false sense of security.

Of course - all is not lost. We recommend that, in light of this knowledge and accepting the facts as they are, instead of playing "the game" of protection with the intent to "win" (to completely stop the hackers) - we play for an impasse. Since we know that a "win" is impossible, we play the "game" for the next best thing - a tie. What we mean by a "tie" is that you should engineer your protections in such a way that:

It is as difficult, tedious and time consuming as possible for a cracker to crack.
Is difficult to crack successfully or without breaking some key part of the program.
If cracked, can be quickly and easily changed so the crack no longer works with the current version of the software.

What can you, as a developer, do to make your implementation of you software licensing solution as secure as possible?
What can you, as a developer, do on an ongoing basis, in order to make your software as secure as possible?
Anti-hacker standard practices are just that - standard. They should not be limited solely to your implementation of the licensing System and the code around it. So, in fact, the two concerns above are one and the same. Below are several simple "tricks" you should consider, that when used together, will force crackers trying to defeat your system to invest incrementally more time in doing so. When used in conjunction with the licensing System, their job will be unpleasant to say the least. Please be sure you understand that the purpose of playing the "game" is an impasse.

Here are several standard things you should do in any software you wish to protect to slow down crackers:

1 - Never give any registration or protection testing function a self describing name. Never use a function name like "IsActivated". Crackers will quickly locate these names (in most high level languages) and simply remove or rewrite them.
2 - Avoid unnecessary error messages. If your program gives an error message after an unsuccessful activation attempt, the crackers will be able to quickly locate the error message and know that at some point in the call stack immediately before it - a protection or activation-test function call failed.
3 - Wait using a timer in a separate thread to provide error messages. When an error message is unavoidable, you may wish to set a timer in a separate thread that will fire several seconds or minutes later to warn the user and take action. This makes tracing back to the protection call that caused the timer to start up more difficult and will slow the cracker down.
4 - Encrypt any and all protection strings. When an error message in unavoidable, be sure to dynamically generate the message string itself. The best way to do this is to store it in encrypted form in the binary and decrypt only immediately before you need it. This makes searching for the string very difficult. Better yet - encrypt all your programs strings.
5 - Use random tests for activation. Test that the program is correctly activated at random time intervals; hours, days or even weeks after it was first installed and run. Possibly test only after certain key functions (unrelated to activation) are used. This will often be missed by crackers and again will slow them down or make their crack worthless.
6 - Don't start the activation test for several seconds (or even minutes) after the activation. you may wish to store any Activation Codes input by the user temporarily in memory and after a brief pause try to activate them. You may even wish to require the user to restart the program before you input the value. This makes it difficult to trace and will slow the cracker down.
7 - Use CRC checksums in your application and dlls. Have your EXEs check themselves, check other DLLs, or even have them check each other. Consider computing a checksum on just a small section of the file itself instead of the whole thing - this makes the crackers job more difficult.
8 - Use Anti-Debugging tricks. Be sure you have read the Anti-Debugging section for more information on how to slow down crackers by having your software resist debuggers.
9 - Use Anti-Disassembling tricks. Be sure you have read the Anti-Disassembling section for more information on how to slow down crackers by having your software resist disassembling.
10 - Use more activation checking routines than the minimum necessary. You should test in several places, and in places where the crackers might not expect it. Check at random time intervals too (see above). One routine requires a time investment from the cracker to remove, then more routines will require even more time to break.
11 - Use Honey Pots. A "Honey Pot" is a fake or decoy routine (or set of routines) you code into your program that seem to check activation, but in fact - does nothing. Have it write and read registry keys, manipulate files, jump all over in memory computing useless values and doing meaningless comparisons. Use your imagination here. Name honey pots to draw the crackers attention (like "CheckReg"). The point is to waste their time with a ruse.
12 - Wrap Activation testing routines in ridiculously long code. Consider using several long procedures which do a huge amount of unnecessary (but seemingly meaningful) processing. At some point during this useless processing, legitimately check the activation. Consider even checking it two or three times in different ways. This make the crackers job of tracing through this giant jumble of assembly looking for the "real" code a more frustrating experience. This will slow them down. Your testing routines can safely take 5 to 20 seconds to execute on a reasonably fast machine.
13 - If you use a demo version of your software with limited features, make sure you don't have "grayed out" buttons or menu options. A cracker can simply change the enabled property of these controls which will effectively make your features visible again. It is always preferable to dynamically create these controls only when they are available.
If you use a demo version of your software with limited features, consider not distributing the actual binary code to execute those functions. The simplest way to do this is to include the "paid version only code" inside a DLL which is called from your program when it is legitimately purchased. Then when a customer purchases your software, give them an Activation Code to release your software protections as well as the required DLL containing the code for the missing features.
14 - If your program has been cracked, release a new version. This is probably the most important principle which makes all the above tricks worth while. Once you have wasted the crackers time as much as possible, slowing them down with all these tricks (and others you may think up yourself), you must immediately make all their hard work go to waste - release a new version fast. Change a few things around, re-organize the code, update the version number, test - and re-release. The cracker will have to start all over again. Reaction time is important too. Expect to move quickly if a crack is released. Try and release a new version as rapidly as possible to maximize the frustration effect.

cyclic redundancy check

A CRC (cyclic redundancy check) is a numeric value computed from some source (file, string, digest, etc). Unlike encryption, a CRC value is always the same size regardless of the source size. A CRC is also commonly referred to as a hash or a checksum.

There are numerous sources on the internet for information on what a CRC is, so the algorithms wont be discussed in depth here. Regardless - it may be preferable from a security standpoint for you to develop your own CRC algorithm variation based on a well-known cryptographically secure one.

A CRC can be used to help slow down hackers by computing a CRC checksum of some file (on Windows your EXE or a DLL) and comparing the computed value with a stored value from a known and trusted source. If any of the instructions have been changed, the CRC checksum will not match.

This can be used by your software team in a couple ways to slow down the crackers:

Trojan Server Attack

A cracker may try to replace the DLL (in case of COM with a Trojan COM server with the exact same interface but whose functions always returns true values). You can use a CRC value to attempt to defeat this attack:
The basic premise is:

On Windows Operating Systems, read from the registry the location of the DLL based on the known GUID of the COM server you want to check.
If that file exists, calculate a CRC checksum on it. (Any CRC or hashing algorithm can be used - it doesn't matter).
Compare the checksum calculated against your known checksum which you have previously computed on a trusted copy of the COM server. Take action depending on the match.
Perform a CRC check on the dll every time your program starts but before you actually use the system. Check the return value of the CRC check on the dll against a value you store inside your program. If they are not the same - the dll has been swapped, damaged or altered. To make this even more secure have the value inside the program you check against be stored in three different places, and assemble it just before you use it. A C++ example follows where, at development time, you have already run your CRC function on a trusted copy of the dll file and you know it should return a value of 3070908778 :

char buffer1[25] = {'\0'};
char buffer2[25] = {'\0'};
const char * val1 = "778"; // declared in a different module somewhere
const int val2 = 3070; // declared in a different module somewhere
static int val3 = 908; // maybe read from the registry where your installer wrote it.

if (CRCCheck("mydll.dll") != atol(strcat(strcat( itoa(val2, buffer1, 10), itoa(val3, buffer2, 10)), val1)))
{
// DefeatAttempt! - shut down.
}

You can even implement or use you own version of itoa, atol and strcat

CRCChecks can be quite simple to implement. We suggest that you use your own CRC to ensure that it is original.

Binary Instruction Replacement Attack
A cracker may simply replace the protection calls in your program to do nothing - ignoring the COM server altogether. In fact - this is a very common attack used by most crackers. You can use a CRC value to attempt to defeat this attack:

All 32-bit executables have a CRC checksum field in their programs PE header. You can force your compiler to generate this checksum. Then, using the Win32 API MapFileAndCheckSumA() you can get both the computed checksum and the stored one. Then simply compare them. This of course only works if the cracker doesn't change the stored one, but can sometimes be effective. There are many more sophisticated approaches to using CRCs in your program to detect the integrity of both itself and external modules (dlls) but they are beyond the scope of this help file.

You may even wish to consider computing the checksum on just a small section of the file itself instead of the whole thing - this makes the crackers job more difficult. Don't just have EXEs and DLLs check themselves, have them check each other.

Anti-Debugging

Debuggers are tools just like your IDE that allow crackers to trace a programs execution as they are running - instruction by instruction.

There are numerous anti-debugging tricks that are documented in books and on-line, but all approach the problem from two specific angles:

They attempt to detect any debugger that is currently attached to the process or running in the background.

They attempt to detect specific debuggers (like SoftICE and others).

Protected software should use some sophisticated techniques to protect you from debuggers in both these ways, However, this is only effective when the Binary/DLL methods are actually called to perform some action. To be even more resistant you should consider implementing anti-debugging tricks of your own.

There are simply too many well-documented ways to detect specific debuggers (like SoftICE) available to discuss them here. Many of them are very complex to implement or are ineffective. Instead, we suggest you make at least a simple attempt to detect debuggers. The simplest way to do this is with the Win32 API function call "IsDebuggerPresent". Although this is relatively simple to replace by most crackers, and only works on Windows NT, 2000 and XP, placing it in various unexpected locations in your program can sometimes be quite effective at slowing them down.

Anti-Disassembling

Disassemblers are tools crackers use to translate application code back into assembler or even a higher level language. There are several disassemblers on the market of various quality. Some even write comments on the translated code, which makes it easier for the cracker to understand.

Since the purpose of disassembling is to understand the programs code, a good way to counter disassemblers is to make it more incomprehensible internally. The simplest way to defend against disassemblers is to insert numerous small bits of code in between the legitimate program code instructions that do nothing meaningful, but appear to, and are complex to understand.

A simple way to do this is to define a number of anti-disassembling macros and inline functions. Use your imagination to write these macros and functions. Do lots of pointer arithmetic and mathematical transformations. Conditionally and unconditionally jump all around in memory. Make sure your anti-disassembling routines are macros or inline functions so the anti-disassembling code gets pre-processed and duplicated everywhere it is placed (instead of a simple function call which can be found and replaced in a single location by a cracker).

Then, sprinkle these macros and functions liberally around areas of your programs you wish to protect from disassembling. Increase the density of the routines around sensitive areas. Naturally this will increase the footprint of your binary and can potentially impact performance so use this trick very wisely. You may wish to reserve its use for areas only around your protections and licensing code.

The more you can make the crackers job tedious, the more time he will have to invest in cracking your software - which is the ultimate goal - to slow them down as much as possible.

Reading

http://www.amazon.com/gp/search?index=books&linkCode=qs&keywords=1597494224
http://www.amazon.com/gp/search?index=books&linkCode=qs&keywords=0321294319
http://www.amazon.com/gp/search?index=books&linkCode=qs&keywords=0072262877
http://blogs.technet.com/b/markrussinovich/archive/2005/10/31/sony-rootkits-and-digital-rights-management-gone-too-far.aspx
http://www.amazon.com/IDA-Pro-Book-Unofficial-Disassembler/dp/1593271786/ref=pd_sim_b_7

Qualcomm Snapdragon vs OMA Texas Instrument

2010-07-26T14:30:00.000-07:00

The Qualcomm Snapdragon platform continues to generate robust industry attention to accompany its steadily expanding customer base. At the recent COMPUTEX 2010 show, Qualcomm unveiled the sampling of the third generation of its Snapdragon platform – namely its first dual-CPU Snapdragon chipsets consisting of the MSM8260, MSM8660 and QSD8672 products that feature enhanced dual cores that can run at up to 1.2GHz and 1.5GHz respectively, and are targeted at the high-end smartphone market area (the third generation Snapdragon platform is expected to support commercial products by the end of 2010). The new third-generation Snapdragon products complement its first-generation QSD8x50 1GHz core product and the second-generation MSM8x55 and QSD8x50A products with 1GHz enhanced core, including multimedia optimizations and 1.3GHz enhanced core respectively.

The Snapdragon platform can be viewed as competing within the mobile application processor market segment (also referred to as the mobile multimedia processor market segment). Today the application processor segment includes IC platforms that typically integrate the application processor core along with additional functions such as baseband modem andwireless connectivity functions onto a single system-on-a-chip (SoC); this includes the Qualcomm Snapdragon. The application processor market also consists of IC platforms that exclude integration of baseband modems (e.g., TI’s OMAP 4). The application processor platform segment addresses a wide range of mobile devices including smartphones, mobile Internet devices (MIDs), netbooks and portable media devices. By its nature, the mobile application processor market segment attracts a wide swath of competition from the top-tier mobile silicon players, including Samsung, Apple, Intel and TI. Due to Qualcomm’s historically solid competitive foundation, based heavily on its CDMA chipset royalties, and the burgeoning traction of the Snapdragon platform (in over 140 device designs), it presents a mounting competitive challenge and thus generates the key issue of how the competition can position against the overall Snapdragon platform.
Perspective Current Perspective
The Snapdragon platform has been commercially available since Q4 2008 through the QSD8650 and QSD8250 first generation product offerings. From its inception, Qualcomm positioned the Snapdragon platform as an innovative breakthrough offering since it uses the in-house custom developed Scorpion CPU as the core application processor based on the ARMv7-based Cortex-A8 core. This approach has enabled Qualcomm to engineer improvements over standard off-the-shelf ARMv7-based Cortex-A8 processors in areas such as power consumption (e.g., the first Scorpion processor required 150 mW less power consumption at 600 MHz than the non-customized ARM equivalent and so on) as well as optimizing the processor design for the low-power (LP) process. As a result, the Snapdragon platform has proven a stalwart in the smartphone application processor market, as evidenced by the Snapdragon platform’s incorporation in over 140 device designs that include mobile devices that range from HTC’s Droid Incredible and Nexus One smartphones to Huawei’s S7 tablet, to name a few.

For the first generation Snapdragon QSD82x0 products and the second generation Snapdragon MSM8x55 and QSD8x50A products, Qualcomm shares platform and product metrics in areas such as core processor clock speed/performance, flexible wireless connectivity functions, HD video/3D/display/camera support and O/S versatility. This gives rivals a wide range of product areas to seek selective differentiation against the Qualcomm Snapdragon platform, although Qualcomm is hardly unique in that regard.

The topic of core processor clock speed and performance, for example, represents a straightforward and intuitive product area for rivals to assert competitive differentiation. The Snapdragon platform’s first-generation QSD8x50 supports a 1GHz core processor while the second-generation MSM8x55 and QSD8x50A products support a 1GHz enhanced core, including multimedia optimizations and a 1.3GHz enhanced core respectively. In contrast, Intel asserts that its x86 processor-based Moorestown platform via the Atom Z6xx processor series can support up to 1.5GHz clock speed for smartphone devices and up to 1.9 GHz clock speed for tablet devices. Such metrics will still match the third generation Snapdragon QSD8672 product that is designed to run dual cores that operate at 1.5GHz (this product should appear in mobile devices at retail by the end of 2010). This complements Intel’s overall efforts to position its Moorestown platform as prime time ready for smartphone technology due to the improvements realized in areas such as power consumption advances in battery life spans (based on 1500 mAh batteries) in support of 1080p/720p video (e..g, up to four hours for 1080p video) and browsing applications as well as multi-fold improvements gained in Java script, Web page, graphics and video performance. This includes up to fourfold Java script performance improvement and at least a doubling of Web page download performance and graphic performance in relation to the Qualcomm Snapdragon platform as well as wielding the industry’s only across-the-board support of 1080 HP/MP/BP 30 fps and 720 HP/MP/BP 30 fps video capabilities. Intel’s overall R&D investment and marketing blitz on behalf of the Moorestown platform is certainly targeted at Snapdragon, as well as advancing Intel’s longstanding ambition to promote the x86 processor architecture as a viable alternative to the ARM processor architecture that dominates the mobile device silicon market today. Intel hopes to play a more prominent role within the overall mobile device silicon market beyond netbook silicon. There is a bit of irony here as Intel is looking to use the Intel Moorestown platform to attack the ARM-centric Snapdragon platform in Qualcomm’s backyard of smartphone and tablet silicon, while Qualcomm is developing the Snapdragon platform to help more directly challenge Intel’s prominence within the netbook silicon segment.

Apple, Samsung and TI are Qualcomm rivals that also use the customization of the ARMv7-based Cortex-A8 processor to achieve select advancements over the standard ARM offering. Samsung and Apple currently have a strange bedfellow arrangement that can influence how they position their respective platforms against the Snapdragon platform. Samsung collaborated with Intrinsity in developing and introducing its 45nm-based Hummingbird platform during 2009. In April 2010, it was revealed that Apple acquired Intrinsity in stealth mode to lock up the FastCore intellectual property (IP) that was instrumental in realizing the iPad A4 processor’s enhancements to standard issue ARM Cortex-8 core processor technology (e.g., achieving 1 Ghz clock speed on a 45nm process). Through the acquisition, Apple can promote that its A4 processor development efforts are dedicated exclusively to the support of Apple products such as the iPad and iPhone, and the company can avoid the dissipation of processor engineering resources that its rivals, such as Qualcomm, are obliged to perform through the open-ended support of multiple OEM products. Samsung should look to further elucidate its plans to license the Hummingbird technology to other mobile device vendors and what if any impact this has on its Apple relationship. The Apple acquisition of Intrinsity does not change the fact that Apple’s A4 technology remains based on Samsung’s 45nm SoC technology and Samsung continues to have access and wield the Hummingbird IP gained from its joint collaboration with Intrinsity prior to the Apple acquisition of Intrinsity.

Samsung continues to register significant product development and marketing advances with its Hummingbird SC5PC110 processor. The Hummingbird S5PC110 runs the Samsung Galaxy S smartphone, which Samsung asserts will launch in an astonishing 110 countries. One area the Samsung can assert clear product differentiation against Qualcomm is in the area of 3D graphics. The S5PC110 processor can scale up to support 90 million triangles per second. In contrast, the Qualcomm QSD8650 delivers only 22 million triangles per second while the pending QSD8672 will do up to 80 million triangles per second. Additionally, in the related area of 2D graphics rendering, Samsung’s S5PC110 product can support up to one billion pixels per second while Qualcomm’s QSD8650 supports only 133 million pixels per second and the upcoming QSD8672 product still comes up short against Samsung with an improved 500 million pixels per second.

TI’s OMAP 4 platform using the OMAP4440 processor is slated to support mobile device products that will hit retail in late 2010/early 2011. The OMAP processor series is already found in well-known mobile handset products such as the Nokia N-series, the Motorola DROID, and the Palm Pre. However, OMAP 4 dual core clock speeds are limited to just 1 GHz, and that’s for a product that is not yet in generally available mobile products. In this regard, OMAP 4 only ties the Qualcomm Snapdragon’s first generation 1 GHz product and trails both the second and third generation 1.2Ghz-1.5Ghz products. However, TI has already staked out a competitive position against Qualcomm in this area showing how apples-to-apples comparisons can prove dicey at times in the mobile silicon space. TI asserts that the OMAP 4 can deliver improved resolution display and still image metrics in relation to the Snapdragon platform, despite the core processor clock speed differentials. For example, the OMAP 4 can deliver 20-megapixel camera support while the QSD8x50 product can only handle 12-megapixel cameras. Moreover, TI advocates the OMAP 4 platform will prove more flexible in hardware support of future video codecs in relation to the Snapdragon platform. TI will also invoke that its OMAP4440 processor will use the ARM Cortex-9 architecture, which can yield performance improvements over ARM Cortex-A8 products (up to 30 percent according to ARM) and more flexible dual core power management arrangements.

Overall the most serious long-term competitive threats to the Qualcomm Snapdragon platform within the smartphone and tablet application processor market will prove to be the major mobile silicon players such as Samsung, Apple and TI, as well as Intel, who already possess competitive application processor platforms targeted specifically at smartphone, MID and tablet products. Mobile silicon rivals such as Marvell, Freescale, NVIDIA and ST-Ericsson all sport viable mobile application processor platforms but need to prove they can move the market needle more within the mobile application processor market segment to mount a serious challenge to Qualcomm in the evolving smartphone/tablet silicon market segment. Marvell and Freescale have achieved market distinction within the ereader niche, for example, but are not able to match the Snapdragon’s presence in over 140 device design wins. Samsung, Apple, Intel and TI all possess the product differentiators in areas such as core processor clock speed/performance, power consumption metrics, and HD video/3D/display/camera video performance and the global channels to challenge the Snapdragon’s early market prominence in this area into the foreseeable future.
Recommended Actions Vendor Actions
• Mobile application processor vendors that target emerging 4G/LTE silicon devices should consider getting out ahead of the market in explaining how their platforms optimally complement the region-sensitive E-UTRA LTE bands (TDD/FDD modes). In general, mobile application processor vendors should posit the 4G/LTE market represents a new level playing field in the market as Qualcomm’s dominance in the CDMA/3G silicon market will not directly translate into the same type of dominance within the 4G/LTE space.

• Mobile application processor vendors should note that they generally rely on third-party partners to supply fundamental mobile silicon components such as baseband modems and RF transceivers to complement their application processor platforms while Qualcomm uses integrated in-house baseband modem and RF transceiver components as part of the Snapdragon offering. This provides some latitude in asserting that they can select best-of-breed components in these areas and have more supply chain flexibility in relation to Qualcomm’s single vendor approach.

• Intel should continue to pointing out that the smartphone/tablet market is still in its developing stages, which gives Intel ample opportunity to capitalize on new market opportunities in this fast growing segment. This includes pointing out that the Atom Z6xx series is already in the advanced demo stage in smartphones with 3.8”+ displays and ~15mm thin tablets and the x86 platform supports rising mobile O/Ss such as Android and MeeGo.
User Actions
• Smartphone and tablet OEMs need to test and contrast the Intel Atom Processor Z6xx series (prior codename Lincroft SoC) against competing ARM-based mobile device SoCs, such as Qualcomm’s Snapdragon platform, due to factors such as its compact package (i.e., 13.8x13.8x1.1mm with 0.5mm pitch), support of 19 power islands with on-die clock and power gating, new ultra low-power states (i.e., SOi1, SOi3), and the leveraging of Intel’s Hi-K 45nm LP SoC process.

• Smartphone and tablet OEMs should investigate the new OS power management (OSPM) capability that accompanies the overall Moorestown platform. This includes support of integrated PMUs, software-based OS power management options, and fine-grain power management functions that create power islands for sub-systems (i.e., power is only allocated to the application running and not dispersed to idle applications, etc.) and factor in such capabilities in seeking apples-to-apples validation of Intel’s power conservation claims on behalf of the Atom Moorestown platform in relation to the Snapdragon platform

Android WebKIT JS/HTML framework : PhoneGap

2010-07-21T19:31:00.000-07:00

This guide will help you setup your first android project but not a basic one. One taking advantage of WebKIT Javascript framework.

The first thing to do is to download and install all the required dependencies.

Please contribute platform specific instructions where needed.

Installing dependencies

1. Java JDK
If you do not already have the java JDK installed on you'r system, install the Java SE Development Kit - JDK 6 from here:
http://java.sun.com/javase/downloads/index.jsp

If you're running Windows this is a standard installer file, just follow the on screen instructions for installation.

2. Eclipse
Install the Eclipse IDE for Java Developers from http://www.eclipse.org/downloads/. This a ZIP archive file, extract the folder “eclipse” for me I extracted eclipse
under C:\eclipse . Most other flavors of Eclipse (like Aptana or platform specific builds) will also work, provided that you install all the necessary Eclipse plug-ins.

3. Android SDK
Install the Android SDK Package from here:
http://developer.android.com/sdk/index.html

Extract the downloaded archive and place it somewhere you'll remember like C:\sdk\android-sdk-windows
and add the tools sub directory to your environment PATH. Additional information and instructions for adding the Android SDK to your PATH can be found at:
http://developer.android.com/sdk/installing.html

Be sure to do the following (WINDOWS):
Add android SDK to your Path
Add android sdk tools (\android-sdk-windows\tools) to your path. This is necessary
for ruby to find the command "android create project" later on.

4. ADT Plug-in for Eclipse
Install the ADT Plug-in for Eclipse as described here:
http://developer.android.com/sdk/eclipse-adt.html

5. Adding Android SDK components
Install at least the required Android SDK components using the Eclipse ADT plug-in, as described here:
http://developer.android.com/sdk/adding-components.html

You can also launch the ADT tool by running android in your terminal.

To verify your installation of Eclipse, Android SDK, ADT, and Java, you can build a sample “Hello World” application using the instructions located here:
http://developer.android.com/guide/tutorials/hello-world.html.

6. Apache ANT

Windows - download and unzip Apache ANT and add it to your PATH http://ant.apache.org/index.html.

7. Ruby

Windows - download and install Ruby from the official site http://www.ruby-lang.org/en/downloads/ or use the RubyInstaller (recommended) here http://rubyinstaller.org/

8. Installing PhoneGap
Now make sure you download the latest version of PhoneGap here:
http://github.com/phonegap/phonegap-android.

9. edit the droidgap ruby file

change target_id = 5 to target_id = 6 to target Android 2.0.1 if your phone is running 2.0.1

10. Build framework and sample application

C:\Dev\mydroid\phonegap-android>ruby ./droidgap c:/sdk/android-sdk-win
dows/ phonegap com.phonegap.droid.demo c:/Dev/mydroid/phonegap-android/example/ c:/dev/mydroid
/phonegap-android/phonegap/

11. Once the phonegap app has been generated launch eclipse

To load eclipse and be able to see the workspace location use the -showlocation parameter

c:\eclipse\eclipse -showlocation

12. Next is to import the generated project in eclipse, fix any compilation errors, include the phonegap jar in your project build path and finally edit AndroidManifest.xml otherway you are going to see few crashes when trying to access lower level java class

I replaced the < by { and > by }

{?xml version="1.0" encoding="utf-8"?}
{manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.tuniverse.droid"
android:versionCode="1"
android:versionName="1.0"}
{uses-permission android:name="android.permission.INTERNET" /}
{uses-permission android:name="android.permission.CAMERA" /}
{uses-permission android:name="android.permission.VIBRATE" /}
{uses-permission android:name="android.permission.ACCESS_GPS" /}
{uses-permission android:name="android.permission.ACCESS_ASSISTED_GPS" /}
{uses-permission android:name="android.permission.ACCESS_LOCATION" /}
{uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /}
{uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" /}
{uses-permission android:name="android.permission.READ_PHONE_STATE" /}
{uses-permission android:name="android.permission.RECEIVE_SMS" /}
{uses-permission android:name="android.permission.RECORD_AUDIO" /}
{uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" /}
{application android:icon="@drawable/icon" android:label="@string/app_name"}
{activity android:name=".WebActivity"
android:label="@string/app_name" android:configChanges="orientation|keyboardHidden"}
{intent-filter}
{action android:name="android.intent.action.MAIN" /}
{category android:name="android.intent.category.LAUNCHER" /}
{/intent-filter}
{/activity}
{/application}
{/manifest}

13. When your app will build with no error, you can run the application
in the debugger or in the emulator.

To view the android log (emulator) open a shell (usually the same one than the one
used to lauch eclipse and run

abt logcat

If you want a nicer logcat output you can use some very cool python script to output the android log in color !!! Install python first from here

As you can see, the colored adb logcat is a huge improvement.

To easily use the code, copy the files color_console.py, coloredlogcat.py and logcat.bat to your Android SDK/Tools path like c:\android-sdk-windows-1.5_r3\tools\logcat.bat. Now, instead of running "adb logcat" just run "logcat".

You can download the files here colored_logcat.zip (3 KB)
Thanks go to
Jeff Sharkey
André Burgaud

To install APK applications on your Android phone do the following:

Copy the APK file you want to install to your phone's memory card and insert
the card into your Android phone.
Go to Android Market and search for the Apps Installer application.
Open it and click on the Install button.
After it is installed, just open it. It will show you all the APK files stored directly in the root directory of your memory card.
Just click on the application you want to install and it will be installed.

Using the Android SDK and USB driver

There is one more method that can be used, you can install APK files into your phone using the Android SDK. Download the Android SDK.

First of all, install the Android SDK on your computer. You will also need
to install the Android USB drivers to connect the SDK to your phone via USB. You can get instruction on how to install it from here

To install applications from other sources, you also need go to Settings -> Application Settings and enable Unknown Sources. Also go to Settings -> SD Card and Phone Storage -> Disable Use for USB Storage. You can enable it again later.

Next, just open Command Prompt and type: adb install path/file.apk

where path is the full path to the APK file and file is the name of the APK application file. Your application is now installed. This is all you need to do, now just open the application on your phone and use it.

HTML VIDEO OPEN STANDARD GOOGLE MOVING TOWARDS VP8 (ON2)

2010-06-30T09:30:00.000-07:00

Concerns about patents and licensing have prevented some browsers from supporting H.264; this in turn has prevented the HTML5 spec from requiring support for a standard format. We believe the web needs an open video format option. One that not only helps address the licensing concerns, but is also optimized for the unique attributes of serving video on the web. To that end, we’re excited about the new WebM project. Google is open sourcing and contributing the VP8 codec to the WebM effort. Google, Mozilla, and Opera have all committed to support WebM, and we have already started making YouTube videos available in the WebM format. Adobe has also committed to support VP8, the video codec for WebM, in an upcoming Flash Player release.

Full article here:
http://apiblog.youtube.com/2010/06/flash-and-html5-tag.html

Tons of html 5 video sample are available at http://oggtv.com/ mostly ogg

You’ll probably already have read up on and experimented with the new HTML5 video element, which allows us to include video inside an HTML page without the need for plugins (if not, read our Introduction to HTML5 video before going any further.) You’ll probably also be aware that there is somewhat of a disagreement over codecs going on. Opera and Firefox currently support the Ogg Theora video codec, while Safari supports the H.264 codec. Google Chrome supports both, while Microsoft have announced support for H.264 in IE9. This is not ideal, as to implement a cross-browser video with HTML5 you would need to encode and reference multiple video formats. For example:

Enter WebM
Help is just around the corner — Google has released the VP8 video codec and WebM container format under royalty-free terms, with the aim of making a high quality, open video format available across different browsers and platforms. This was announced publicly at the 2010 Google I/O conference. Opera has created an experimental WebM-enabled build, which you can play with today.

Windows:
Windows standard installer
Windows classic installer

Mac:
Mac universal binary
Mac intel package

Linux:
Linux 32-bit
Linux 64-bit

It is clear that Adobe now needs to integrate webm support in Flash Player and FLash Media Server ASAP.

How:

by providing the user the ability to decide on various fallback

If your browser supports it, HTML5 video is used.
If HTML5 video is not supported, Adobe Flash is used.
Finally, if all else fails, a placeholder image is shown
This is all done without JavaScript and requires only two video encodes, one OGG file, and one MP4 file.

It’s compatible with HTML 4, HTML5 (valid markup), XHTML 1 and additionally also works when served as application/xhtml+xml

http://camendesign.com/code/video_for_everybody

Ensure your server is using the correct mime-types. Firefox will not play the OGG video if the mime-type is wrong. Place these lines in your .htaccess file to send the correct mime-types to browsers
AddType video/ogg .ogv
AddType video/mp4 .mp4
AddType video/webm .webm

Now I am wondering how Microsoft is going to handle ism file format and how non microsoft browser are going to respond. The fallback mecanism should work with IE9 and support ism file format.

RTMFP

2010-06-24T17:50:00.000-07:00

Tom Krcha (platform evangelist at Adobe) has a bunch of stuff on his website about RTMFP.
lately he's been focusing on some of the new advanced topics, like RTMFP Groups, but he has materials
covering the spectrum of P2P topics. I went to https://afcs.acrobat.com/ and sign up to test RTMFP with
Flash Builder 4.0. The video tutorial are fantastic and the COCOMO SDK is very complete and fully loaded
with MXML sample.

Few interesting articles:

http://www.flashrealtime.com/basics-of-p2p-in-flash/
http://www.flashrealtime.com/ .
http://www.ealeyes.com/ articles and tutorials on using RTMFP
http://www.adobe.com/devnet/flashmediaserver/articles/p2p_rtmfp_groups.html

When using the COCOMO sample avoid basic and simple authentication which hardcode
the login and password inside the MXML. Instead take advantage of authentication using
hash.

http://livedocs.adobe.com/labs/acrobatcom/com/adobe/rtc/authentication/AdobeHSAuthenticator.html

Quicktime 7 / Quicktime X

2010-06-24T00:48:00.000-07:00

QuickTime 7.x QuickTime 7 represents one of the largest architectural changes to the QuickTime lineage since its first version Initially released on April 29,2005 in conjunction with Mac OS X v10.4 (for version 10.3.9 and 10.4.x), QuickTime 7.0 featured the following:
• Improved MPEG-4 compliance
• H.264/MPEG-4 AVCcod ec
• Core Graphics (Quartz) for screen drawing, allowing for live resizing and playback on an OpenGL surface
• Core Audior eplacin g Sound Manager, supporting high resolution sound
• Support for using Core Image filters in Mac OS X v10.4 on live video, also known as Core Video
• Support for Quartz Composer (.qtz) animations
• Support for distinct decode order and display order
• The QTKit, aCocoa framework for QuickTime After a couple of preview Windows releases, Apple released 7.0.2 as the first stable release on September 7, 2005
for Windows 2000 and Windows XP. Version 7.0.4, released on January 10, 2006 was the first universal binary version. But it suffered numerous bugs, including a buffer overrun, which is more problematic to most users. Apple dropped support for Windows 2000 with the release of QuickTime 7.2 on July 11,2007. The last
version available for Windows 2000, 7.1.6, contains numerous security vulnerabilities. Apple has not
indicated that they will be providing any further security updates for older versions. QuickTime 7.2 is the first version for Windows Vista.

Apple dropped support for Flash content in QuickTime 7.3,
breaking content that relied on Flash for interactivity, or animation tracks and those feature were removed from Flash CS4 on Adobe's side.
Security concerns seem to be part of the decision. In QuickTime 7.3, a processor that supports SSE is required. QuickTime 7.4 does not require SSE. Unlike versions 7.2 and 7.3, QuickTime 7.4 refuses to be installed on Windows XP SP1 system (its setup program checks if Service Pack 2 is installed). QuickTime 7.5 was released on June 10,2008.

QuickTime X QuickTime X (pronounced Quicktime Ten) is the next version of QuickTime. It was announced at WWDCon June 9, 2008. It will ship with Mac OS X v10.6 in mid-2009. It will be built upon media technology first used in iPhone OS and will have support for modern codecs and more efficient media playback.
Creating software that uses QuickTime QuickTime consists of two major subsystems: the Movie Toolbox and the Image Compression Manager. The Movie Toolbox consists of a general API for handling time-based data, while the Image Compression Manager provides services for dealing with compressedr aster data as produced by video and photo codecs.
Developers can use the QuickTime software development kit (SDK ) to develop multimedia applications for Mac or Windows with the C programming language or with the Java programming language (see QuickTime for Java ), or, under Windows, using COM/ActiveX from a language supporting this. The COM/ActiveX option was introduced as part of QuickTime 7 for Windows and is intended for
programmers who want to build standalone Windows applications using high-level QuickTime movie playback and control with some import, export, and editing capabilities. This is considerably easier than mastering the original QuickTime C++ API.

QuickTime 7 for Windows introduces a completely redesigned COM/ActiveX control that is fully scriptable from Visual Basic, C#, JavaScript, C++ and other applications that can host COM objects. This means that its even easier for Windows programmers to build standalone Windows applications that use QuickTime without needing to master QuickTime’s C/C++ API. Fully scriptable using either JavaScript or VBScript, automating your QuickTime workflow just got a whole lot easier.

For example, if your Windows server can run a Visual Basic, C# or a JavaScript application that uses QuickTime, you have the ability to create custom QuickTime content dynamically for delivery via the Web. As long as your clients have QuickTime installed, your content will work with Windows and Mac clients, Internet Explorer and non-Internet Explorer browsers.

In order to access these capabilities all you need to do is download the QuickTime 7 for Windows Software Development Kit (SDK). The old link for quicktime now point to
http://developer.apple.com/technologies/mac/graphics-and-animation.html

QuickTime 7 for Mac introduced the QuickTime Kit (aka QTKit), a developer framework that is intended to replace previous APIs for Cocoa developers. This framework is for Mac only, and exists as Objective- C abstractions around a subset of the C interface. Mac OS X v10.5 extends QTKit to full 64-bit support.

QTKit is an Objective-C interface to QuickTime available on Tiger, and also available with QT7 on Panther. It supercedes the Cocoa classes NSMovieView and NSMovie with a larger set of classes which provide a comprehensive interface into QuickTime from Objective-C. In addition to basic playback and tweaking, QTKit allows full-blown editing and other such goodies.
http://developer.apple.com/legacy/mac/library/documentation/QuickTime/Conceptual/QTKitProgrammingGuide/Chapter01/Introduction.html

QTKit is also the name of an open-source wrapper around QuickTime that was made outside of Apple. For information on that wrapper, http://sourceforge.net/projects/qtkit/.

Microsoft IIS Smooth Streaming Format SDK 1.0 Beta 2

2010-06-22T13:10:00.000-07:00

On June 18 2010, Microsoft released Beta 2 of the Microsoft IIS Smooth Streaming Format SDK 1.0.

The IIS Smooth Streaming Format SDK provides application developers the capability to mux encoded video and audio elementary streams into Smooth Streaming fragmented-MP4 format that is compliant with the Smooth Streaming Format and Protected Interoperable File Format (PIFF) specifications. The IIS Smooth Streaming Format SDK includes a native C++ static library that can be linked into your applications to support the muxing of fragmented-MP4 into files or sent live via HTTP POST to a server running Internet Information Services (IIS) 7.0 and IIS Media Services 3.0 and IIS Media Services 4.0 Beta 1. The SDK is available for download here.

Documentation for the SDK can be found online here – IIS Smooth Streaming Format SDK MSDN documentation and the release notes are available here – IIS Smooth Streaming Format SDK Beta 2 Release Notes.

The primary purpose of the IIS Smooth Streaming Format SDK is to enable developers to create applications that can generate PIFF compliant Smooth Streaming formatted fragmented-MP4 files for use in video-on-demand and live streaming scenarios. In addition, the SDK can be used to encrypt content using standard AES encryption as required by the PIFF specification (this SDK only supports the PlayReady specific protection headers).

It is expected that the video and audio encoding functionality is done externally from the SDK. Encoding for VC-1 can be accomplished by using the Microsoft VC-1 Encoder SDK – Professional. If you wish to do H.264 encoding, you will need to acquire a 3rd party H.264 encoding SDK and AAC audio encoder. There are lots of encoding library choices available both free and commercial.

The components of the SDK include:

1. A static-linked packaging library ssfsdk.lib, along with appropriate header files, that delivers f-MP4 wrapping capability to an application for use with the following video and audio codec combinations:
* Closed GOP encoded VC-1 with Elementary Stream Sequence Headers and WMA Pro, or WMA audio
* H.264 (AVC1 closed-GOP streams only with IDR frames at the first sample of a GOP – must not be an Annex B stream. PPS and SPS NAL units are not supported in the stream)
* AAC-LC audio
2. Sample source code for a basic on-demand muxing application that uses DirectShow to source from files.
3. Link to online MSDN documentation.

Updates included in the Beta 2 release of the Smooth Streaming Format SDK are:

* H.264 PlayReady sub-sample encryption support.
* PIFF 1.1 spec compliance.
* Multi-language audio muxing.
* Text stream and TTML track muxing support.

This is in addition to the following supported features:

* Support for Protected Interoperable File Format (PIFF) 1.1 compliant fragmented-MP4 file output.
* Support for ISO Base Media (ISO/IEC 14496-12:2008) spec compliance.
* Support for muxing live and on-demand content.
* Support for appropriate header boxes and formatting required for live streaming using IIS Media Services.
* Support for AES-CTR encryption of VC-1 and H.264 encoded content for use with PlayReady licensing servers and Silverlight 4.0 or higher.
* Support for writing out a compliant Smooth Streaming Transport Protocol server manifest files.
* Support for writing out a compliant Smooth Streaming Transport Protocol client manifest files.

NOTE: Beta 2 includes a “Go-Live” license if you would like to use this SDK in production applications.

If you have questions on how to use this SDK in your applications, comments, or feedback on the SDK please send them to me directly or to smooth@microsoft.com.

Download the Smooth Streaming Format SDK Beta 2 here:

SSFSDK_64.msi

SSFSDK_32.msi

Resources

* Download the Protected Interoperable File Format specification
* Download the IIS Smooth Streaming Transport Protocol Specification
* Download the Smooth Streaming Client 1.0
* API documentation for Smooth Streaming Client
* More Information on Smooth Streaming
* More Information on Live Smooth Streaming
* Supporting documentation on getting started with Smooth Streaming
o Smooth Streaming for IIS 7.0 – Getting Started
o Live Smooth Streaming for IIS 7.0 – Getting Started
o Smooth Streaming Deployment Guide
o Building your first Smooth Streaming Player using SSME

Compile Live555 using VS2008

2010-06-14T19:53:00.000-07:00

Compile Live555 using VS2005
Live555 is a media library to support local and streaming play media files. Its source code is easy to understand and extensible so it's suitable for doing some quick experimentals or demos. It's a cross-platform solution which supports Windows and Linux. But the original source package cannot generate the correct make file for VS2005. We need do some modification listed step by step here.

1. Modify the line "TOOLS32 = ..." in win32config to point to the VS2005 installed directory in your host machine. For example, "TOOLS32 = C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC" is corresponding to my desktop's configuration. Note that I have Windows 7 64 Bit.

2. Modify the line "LINK_OPTS_0 = $(linkdebug) msvicrt.lib" in win32config to "LINK_OPTS_0 = $(linkdebug) msvcrt.lib", otherwise VS2008 will report msvicrt.lib cannot be found.

3. Run genWindowsMakefiles.cmd to generate *.mak for VS2005/VS2008

4. Modify liveMedia/RTSPOverHTTPServer.cpp to add the following code:
#include
#if defined(__WIN32__) || defined(_WIN32)
#define snprintf _snprintf
#endif

Not require with live.2010.06.11

5. Modify groupsock/Makefile.head. Change from "INCLUDES = -Iinclude -I../UsageEnvironment/include" to "INCLUDES = -Iinclude -I../UsageEnvironment/include -DNO_STRSTREAM".

6. Save the following commands into a bat file in the src directory.
call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC
\bin\vcvarsall.bat"
cd liveMedia
nmake /B -f liveMedia.mak
cd ../groupsock
nmake /B -f groupsock.mak
cd ../UsageEnvironment
nmake /B -f UsageEnvironment.mak
cd ../BasicUsageEnvironment
nmake /B -f BasicUsageEnvironment.mak
cd ../testProgs
nmake /B -f testProgs.mak
cd ../mediaServer
nmake /B -f mediaServer.mak

7. run the saved bat file. Done :)

Now it's turn to debug using VS2008, because we don't have a solution file for VS2008, so we need to find another method to debug run.
1. you need to modify win32config to enable debug mode. Just comment the line "NODEBUG=1".
2. File->Open->Project/Solution to load a exe file to be debugged.
3. Debug->Step Over, it will stop at the main function entry point.

HTTP SMOOTH STREAMING AND FRAGMENTED MPEG-4

2010-06-14T10:45:00.000-07:00

	Microsoft IIS Smooth Streaming	Adobe Flash Dynamic Streaming	Apple HTTP Adaptive Bitrate Streaming
Cost per Streaming Server	Free download¹ + $469 for OS²	$4500³ + OS cost⁴	Cost of Web server⁵ + segmenter OS⁶
On-demand & Live Streaming
Live Streaming DVR⁷		Pause & Seek
Streaming Protocol	HTTP	RTMP	HTTP
Scalability via HTTP Edge Caches
Stateless Server Connection⁸
Supported Platforms	Silverlight, Xbox 360, other Smooth Streaming-compatible players, and iPhone OS 3.0⁹	Flash Player 10, AIR	iPhone OS 3.0, devices running QuickTime X
DRM Support for Live, VOD	PlayReady	None¹⁰	None
DRM ASP & Encoder ISV Support
Interoperable DRM (DECE Approved)¹¹
Real-time Client and Server Logging	¹²
Programmable Client Side Switching Logic
Live In-Stream Ad Integration
Built-in Analytics Framework
Delivery to Mobile Devices
Native 64-bit Server Support
Media Container	MPEG 4 – Part 12 (Fragmented MP4)	MPEG 4 – Part 12 (MP4), FLV	MPEG-2 TS
Supported Video Codecs	Codec Agnostic (currently supports VC-1 Advanced Profile & H.264 Baseline, Main, and High)	H.264 Baseline, Main, and High; VP6	H.264 Baseline Level 3.0
Supported Audio Codecs	Codec Agnostic (currently supports WMA & AAC)	AAC, MP3	MP3, HE-AAC, AAC-LC
Maximum Bit Rate	No limit	No limit	1.6 Mbps
Default Fragment Length	2 seconds	n/a	10 seconds
End-To-End Latency	As low as 1.5 seconds (configurable)	6 seconds	30 seconds¹³
File Type on Server	Contiguous	Contiguous	Fragmented
Client Programming Platform	Microsoft .NET Framework	Adobe ActionScript	Objective-C

Footnotes...
1 IIS Smooth Streaming is part of the free IIS Media Services download for Windows Server 2008 and Windows Server 2008 R2 .
2 Runs on any edition of Windows Server® 2008 or Windows Server 2008 R2 including Windows® Web Server, which has a list price of $469.
3 Assumes use of Adobe Flash Media Interactive Server to support Pause, Seek, Authentication, and higher scalability
4 Requires Windows Server 2003 SP2, Windows Server 2008, Red Hat® Enterprise Linux® 4, or Red Hat Enterprise Linux 5.2.
5 Runs on any Web server. Also requires the Apple streaming segmenter – see next note.
6 The Apple stream segmenter is a utility that receives encoded MPEG2-TS and breaks it into 10 second “chunks” for delivery. This free download requires an Intel-based Mac, with a Mac Pro or an XServe having two Ethernet network interfaces recommended.
7 Full DVR features include Pause, Seek, Fast Forward (e.g., 2x, 5x playback speeds), Fast Rewind, Go To Live, Instant Replay, and Slow Motion.
8 A stateless (non-persistent) connection between server and client increases scalability and allows seamless failover or rollover between load-balanced servers.
9 Support for adaptive streaming to the Apple iPhone from IIS Media Services 4 was announced on October 18th, 2009.
10 Future support was announced Sept. 10, 2009. Proposed availability is H1 CY10 for delivery to a future version of Adobe® Flash® Player and Adobe AIR™.
11 Digital Entertainment Content Ecosystem (DECE, LLC) is a consortium of major Hollywood studios, consumer electronics manufacturers and retailers, network hardware vendors, systems integrators and Digital Rights Management (DRM) vendors chartered to develop a set of standards for the digital distribution of premium Hollywood content.
12 Real-time logging for Silverlight applications using the IIS Advanced Logging extension.
13 Encoded live streams are processed by the Apple stream segmenter. This intermediate step results in increased latency for live delivery.

http://www.iis.net/download/SmoothStreaming
http://www.iis.net/download/SmoothFormatSDK

It's an adaptive streaming technology combining IIS and Silverlight. The core file format is fragmented MPEG-4, where each "chunk" of video is transmitted as a moof fragment starting with a Closed GOP, via a single HTTP request. A chunk will typically be 2-4 seconds long. Audio can be either muxed into the same chunk, or be provided in a parallel series of chunks to enable multilangauge audio or what have you.

The file format used is straight-up ISO fragmented MPEG-4, using XML and SMIL manifests to indicate what bitrates in the file set and where the fragments in those file are. We're not trying to make up a new file format here; just take advantage of existing technologies in a novel way.

Lots of other details to be had, including this roundup of links:
http://on10.net/blogs/benwagg/Beta-Release-of-Smooth-Streaming/

More importantly, zambelli had a great post showing how Microsoft is using the file format:
http://alexzambelli.com/blog/2009/02/10/smooth-streaming-architecture/

And we now have some sample files up that I encoded, including the media files and manifest files:
http://on10.net/blogs/benwagg/Big-Buck-Bunny-Smooth-Streaming-sample-for-download/

(if you're curious how it was encoded)
http://on10.net/blogs/benwagg/Behind-the-Scenes-at-SmoothHDcom-Encoding-Big-Buck-Bunny/

The current samples are VC-1 and WMA 10 Pro, but we'll be supporting H.264 and AAC-LC payloads with the next version of Silverlight later in 2009.

So, if you start seeing these *.ismv files out there, just know that they're
Fragmented MPEG-4
With VC-1 or H.264 for video
WMA 10 Pro or AAC-LC for audio

For apple http streaming, a tool called mediastreamsegmenter will take an MPEG2 transport stream and split it into smaller size chunk. Mediastreamsegmenter documentation is available here

HTM5 Video Tag using QuickTime

2010-06-08T21:41:00.001-07:00

Very Interesting article about HTML 5 VIDEO TAG using SAFARI

http://www.streamingmedia.com/Articles/Editorial/Featured-Articles/Note-to-Apple-Safari-%26-QuickTime-are-Not-Web-Standards-67645.aspx

My First iPhone application

2010-06-03T09:22:00.000-07:00

Here's what I have in the (default) login keychain:
• A valid intermediate CA: "Apple Worldwide Developer Relations Cerfitication Authority"
• A valid cert named "iPhone Developer: FirstName LastName" issued by the aforementioned CA
• A RSA 2048-bit private and public key, each named "FirstName iPhone Dev Key"
The keychain application is available through Application/Utilities/Keychain.app.
Once your certificate has been deployed you should see under My Certificate something like iPhone Developer: FirstName LastName.
So far, so good. Meanwhile, on the Program Portal, you need to:
• Registered your iPod touch
• Add an App ID (com.mycompany.myapp). I usually create one for each app keeping the com.mycompany the same.
• Create a Development Provisioning Profile for the aforementioned App ID, device and certificate.

A Provisioning Profile is a collection of digital entities that uniquely ties developers and devices to an authorized iPhone Development Team and enables a device to be used for testing. A Development Provisioning Profile must be installed on each device on which you wish to run your application code. Each Development Provisioning Profile will contain a set of iPhone Development Certificates, Unique Device Identifiers and an App ID.

Devices specified within the provisioning profile can be used for testing only by those individuals whose iPhone Development Certificates are included in the profile. A single device can contain multiple provisioning profiles.

Click here to access the Developer Portal and then
click on iPhone Provisioning Portal on the top right corner.
In the ‘Provisioning’ section of the Portal, click on iPhone Provisioning Portal. Team Admins should click 'Add' on the Development tab. Enter a name for the provisioning profile.
Specify which devices will be associated with the provisioning profile. You must specify a device in order for that device to utilize the provisioning profile. If a device's UDID is not included in the provisioning profile the profile and your application cannot be installed on that device.
Specify which iPhone Development Certificates will be associated with the provisioning profile. You must specify an iPhone Development Certificate in order for the application code signed with that same certificate to run on the device.
Specify a single App ID for the Development Provisioning Profile. Each Development Provisioning Profile can specify only ONE App ID, therefore, if you have applications requiring different Keychain access, you will need to create a separate Development Provisioning Profile for each of those applications. If you are installing a suite of applications with the same required Keychain access or have a set of applications not requiring access to the Keychain, use an App ID containing the wild-card asterisk character to build all of your applications.
Click ‘Submit’ to generate your Development Provisioning Profile.

NOTE: On the Portal, the Certificate only shows as "FirstName LastName" and not "iPhone Developer: FirstName LastName".

Installing a Development Provisioning Profile
All Team Agents, Admins and Members can download a Development Provisioning Profile from the ‘Provisioning’ section of the Portal after it has been created. Only those developers whose Apple device IDs and iPhone Development Certificates are included in the provisioning profile will be able to install and test their application on their device.

In the ‘Provisioning’ section of the Provisioning Portal, click the download button next to the desired provisioning profile.
Drag the downloaded file onto the Xcode application icon in the dock or into the ‘Organizer’ window within Xcode. This will automatically copy the .mobileprovision file to the proper directory. Alternatively, you can drag the .mobileprovision file onto the iTunes icon in the dock or copy the file to ‘~/Library/MobileDevice/Provisioning Profiles’. If the directory does not exist you will need to create it. Click on the ‘+’ button in the Provisioning section of the Organizer window to install your .mobileprovision file.
I recommend to create the Library/MobileDevice/Provisioning Profiles else after each download you will end up with all provisioning profile under you Download Folder.

Now, on to the home stretch! In Xcode 2.2.1, you must have:
• REMOVED my build directory (before launching Xcode with said project - OPTIONAL) or just perform a full project clean using XCode for the project in question .
• Docked/synced your iPod touch
• Dragged-and-dropped your downloaded provisioning profile into the appropriate spot in the Organizer. It's not grayed out, and the profile is also in your Library in the expected location.
• Chosen "iPhone Device 2.2.1" as the active SDK.
• Under Targets, select your app, then picked Get Info.
• Under the Build tab, verified Base SDK is set to "iPhone Device 2.2.1". For Code Signing Identity, Any iPhone OS Device, there is a value of "iPhone Developer" - fine.
• Under the Properties tab (right click on Targets then select Get Info, change the Identifier to match my App ID com.mycompany.myappid. Be careful not to add any extra leading space by mistakes (EG copy past from the web) Xcode is too stupid to remove spaces.... lame...

RTMP PLAYER SERVER AND SWF2VIDEO

2010-05-13T13:19:00.000-07:00

The most famous client RTMP is the Adobe Flash Player that can do streaming video and audio from RTMP servers.

Adobe Open Source Media Framework
http://opensource.adobe.com/wiki/display/osmf/Open+Source+Media+Framework

Moyea Web Player version 2. 0 with RTMP Stream Plugin supports playback of live video streaming and SMIL presentations and streaming video from RTMP servers.
http://www.moyeasoft.com/web-player/web-player-kits.html

JW Player
http://www.longtailvideo.com/

Flowplayer RTMP as well.
http://flowplayer.org/

Sublime Video Player
http://jilion.com/

RTMP server software

The only full RTMP server application is Adobe Flash Media Server, Onlinelib VCS Video Communication Server (including iPhone Support), Wowza media server and WebORB Integration Server (free of charge and available. NET, Java and ColdFusion), both commercial and closed source implementations. There is a reverse engineered open source project called Red5, which aims to produce a feature-complete written in Java. Finally my current favorite is C++ RTMP Server http://www.rtmpd.com/

SWF2Video

Moyea SWF to Video Converter V3.2
http://www.moyeasoft.com/news/update_081027.html

Software for 2D-3D conversion - Avatar follower

2010-04-28T13:19:00.000-07:00

StereoTracer is designed for creating 3D image out of one 2D image by means of «depth-map». The depth-map (disparity image or Z-image) serves to convert a two-dimensional image into a three-dimensional one. In the depth-map the gray color gradation shows each pixel's distance from the viewer. The lighter area in the depth-map correspond to the areas nearer to the viewer, the darker ones correspond to more distant areas.

A «depth-map» can be created from source one 2D image or stereopair automatically in StereoTracer. "How to" is available here.

StereoTracer generates a number of images which all have a slightly different viewing angle. This process models shooting of a scene from different points across the horizontal line. Resultant series of images is used for creating 3D (stereo) image by method of anaglyph encoding or making multi-view 3D lenticular picture in Triaxes 3DMasterKit or other lenticular generating application. Also a series of frames can be exported into a movie clip (AVI or animated GIF) and used for presentation purposes.

http://triaxes.com/

Sublime HTML5 HD Video Player

2010-04-26T17:36:00.000-07:00

All tests run on the following hardware:

Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 8
L2 Cache: 12 MB
Memory: 8 GB
Bus Speed: 1.6 GHz

For browsers, the latest release browser versions were used. For Flash Player, I used the latest labs release (Flash Player 10.1 Beta 3 : 10,1,51,95).

Mac OS X Versions
=================

Mac OS X 10.6.2
Google Chrome 5.0.307.9 beta
Safari 4.0.4 (6531.21.10)
Firefox 3.6
Flash Player MAC 10,1,51,95

Windows 7 Versions
==================

Windows 7 7600
Google Chrome 4.0.249.89 (38071)
Safari 4.0.4 (531.21.10)
Firefox 3.6
Internet Explorer 8.0.7600.16385
Flash Player WIN 10,1,51,95

Sublime HTML 5 HD Video Example
===============================

Mac Windows
Google Chrome 85% 24%
Safari 21% 104%
Firefox 85% 80%
Internet Explorer NA Did Not Work

http://jilion.com/sublime/video

An other interesting HTML5 Video Sample page (Opera)

http://annevankesteren.nl/2008/fronteers-html5-video

And Finally a future yet to be release HTML5 book

http://diveintohtml5.org/video.html

Other interesting benchmark

http://themaninblue.com/writing/perspective/2010/03/22/

Conclusion HTML5 is catching up...

Android WebView

2010-04-05T14:03:00.001-07:00

WebView allows you to create your own window for viewing web pages (or even develop a complete browser). In this tutorial, you'll create a simple Activity that can view and navigate web pages.

1.Create a new project named HelloWebView.
2.Open the res/layout/main.xml file and insert the following:

android:layout_width="fill_parent"
android:layout_height="fill_parent"/>

3.Now open the HelloWebView.java file. At the top of the class, declare a WebView object:

WebView mWebView;

Then use the following code for the onCreate() method:

public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
mWebView = (WebView) findViewById(R.id.webview); mWebView.getSettings().setJavaScriptEnabled(true); mWebView.loadUrl("http://www.thomasyounsi.com");
}
This initializes the member WebView with the one from the Activity layout;
requests a WebSettings object with getSettings();
and enables JavaScript for the WebView with setJavaScriptEnabled(boolean).
Finally, an initial web page is loaded with loadUrl(String).

4.Because this application needs access to the Internet, you need to add the appropriate permissions to the Android manifest file.
Open the AndroidManifest.xml file and add the following as a child of the element:

What is very powerful with WebView is that you can use a two way communication between the content which is display in the web view and the Java application. This can be accomplished by using JavaScript running inside the WebView calling out Java code to get the updated fragment for the HTML div bloc that require to be use to update the content running inside the view. This means you can use HTML div to layout your content and expand/collapse a div based on user action. The content can come from a remote database, a web service or as a JSON Object.

http://www.youtube.com/watch?v=Ex7YsQ_YH2U

Apple iPad / Microsoft Surface

2010-04-05T11:18:00.000-07:00

In 2007, Microsoft annonced Microsoft Surface

Microsoft Surface represents a new category of computing. With capabilities like direct interaction, multi-touch, multi-user, and object recognition, Microsoft Surface computing is a unique and cutting edge platform for application development.

The Microsoft Surface platform goes beyond the capabilities of its core operating system foundation running Windows Vista SP1, yet it keeps the development process simple. The Microsoft Surface SDK 1.0 SP1 provides all the controls a developer needs to create innovative experiences on Microsoft Surface. And with the new capabilities that come with Service Pack 1, application development is easier than ever with new WPF controls and API enhancements that give developers more control, flexibility, and efficiency in creating applications.

Plus, in order to enable a broad developer audience, Microsoft Surface is compatible with familiar programs and tools developers use today, such as:

Microsoft® Windows Presentation Foundation (WPF)
Microsoft® XNA™
Microsoft® Visual C#® 2008 Express Edition
Microsoft® Visual Studio® 2008 SP1
Microsoft® Expression® Studio 2
Microsoft® Expression Blend™ 2

http://www.microsoft.com/surface/en/us/Pages/Product/Platform.aspx

In 2010 Apple launched the iPad.

The sdk is the same than the sdk used by the Apple iPhone

http://developer.apple.com/ipad/sdk/

The specs have been posted on Apple's web site.

http://www.apple.com/ipad/specs/

Screen size = 1024x768 and my interest will go immediately for TV and video

Support for 1024 by 768 pixels with Dock Connector to VGA Adapter; 576p and 480p with Apple Component AV Cable; 576i and 480i with Apple Composite AV Cable
H.264 video up to 720p, 30 frames per second, Main Profile level 3.1 with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; MPEG-4 video, up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second, Simple Profile with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; Motion JPEG (M-JPEG) up to 35 Mbps, 1280 by 720 pixels, 30 frames per second, audio in ulaw, PCM stereo audio in .avi file format.

iPad Price starting at 499$

It would be nice to see microsoft coming with a small tablet "surface capable" 1280x720 P resolution where people could put there camera or phone in place on top of the tablet running an application in "surface application mode" to exchange and share contents (picture/music/video).

A commercial Microsoft Surface unit is $12,500 (unit only), whereas a developer Microsoft Surface unit costs $15,000 and includes a developer unit, five seats and support. However, Microsoft said it expects prices to drop enough to make consumer versions feasible in 2010. Microsoft would have to come with a price 20x lower than the actual Microsoft Surface unit to compete with the iPad. I think it is time to come up with a product...

how to Install Apache, PHP, MySQL and phpMyAdmin on Windows XP

2010-03-18T13:10:00.000-07:00

This tutorial will show you step-by-step how to install:
Apache 2
PHP 5
MySQL 5
phpMyAdmin on Windows

For those who want to install an all in one solution on Windows I recommend
WampServer

http://www.wampserver.com/en/

or XAMPP

http://www.apachefriends.org/en/xampp-windows.html

The Apache Server combined with the power of PHP, MySQL, and phpMyAdmin, creates one of the best possible development environments for a web programmer. Getting everything properly configured can take 20-30 minutes. And it can work on a non expensive OS such as Windows XP or Windows 7 Home Edition.

Installing Apache:
Follow the steps carefully.

1 Go to http://httpd.apache.org/download.cgi and download "Win32 Binary (MSI Installer): apache_2.2.4-win32-x86-no_ssl.msi" to your desktop.

Note: Make sure that you download Apache version 2.2.4 (Win32 Binary MSI Installer)!

2 Double click "apache_2.2.4-win32-x86-no_ssl.msi", and if prompted, click "run".

3 An installation wizard will appear:

Click "Next".

4 The next page contains the terms of agreement. Select "I accept", and click "Next".

5 Read about the Apache Server, and click "Next"

6 The next screen will ask you for specific server information. Enter the values seen below:

Click "Next".

7 On the next screen, select "Typical Installation" and click "Next".

8 Click "Next".

9 Click "Install".

10 Open up Internet Explorer and type in "http://localhost". If you see a page that says "It works!" then the Apache server has been installed successfully.

Note that if you install Flash Media Server an other instance of Apache will be installed which could cause conflict on the following default Apache server. It would be nice if the FMS team could handle this nicely in their installer....

A few notes on your Apache Server Configuration:
Apache is installed by default in your "C:\Program Files\Apache Software Foundation\Apache2.2" directory.

Inside that directory there is a folder called "htdocs" (matching of your \www\ or \public_html\ directory on a unix system). You can develop your applications inside this folder and access them by going to http://localhost/my_file_name.html

The Apache Configuration settings are defined in a file named "httpd.conf" located in the "conf" directory. Do not attempt to change these settings unless you know what you're doing.

Installing PHP:

Next we will be installing PHP version 5. Follow the steps carefully.
1 Go to http://www.php.net/downloads.php and download the "PHP 5.2.0 zip package" to your desktop. (Be patient while it downloads, the ZIP file is over 9MB!)

Note: Make sure that you download the PHP 5.2.0 zip package! The rest of the tutorial is written using this version.

2 Create a new folder called "php" in your C Drive. Copy the "php-5.2.0-Win32.zip" file to there ("C:\php") and extract it using WinZIP or a similiar program.

3 Your "C:\php" directory should now look like:

4 Next copy the "php.ini-dist" file from "C:/php/" to "C:/WINDOWS" and rename it to "php.ini". This is your PHP configuration file. We'll come back to this later.

5 Now it's time to tell Apache that PHP exists. Open up your Apache configuration file ("C:\Program Files\Apache Software Foundation\Apache2.2\conf\httpd.conf") in notepad and add these four lines to the bottom of the "LoadModule" section:

LoadModule php5_module "c:/php/php5apache2_2.dll"
AddHandler application/x-httpd-php .php
# configure the path to php.ini
PHPIniDir "c:/windows"

6 In your "htdocs" directory, create a file called "info.php". Open it in notepad and add this line of code to it:

7 Restart your Apache Server for the changes to take effect:

Start > All Programs > Apache HTTP Server 4.2.4 > Control Apache Server > Restart
or faster use the Apache Service Monitor seating in the tray icon bottom right bar on Windows XP

8 Open up Internet Explorer and type in: http://localhost/info.php. If your browser takes you to a page that looks like this, then PHP has been installed successfully!

Modifying your PHP Configuration File:

1 Your PHP configuration (php.ini) file is located in "C:/WINDOWS/php.ini". You can modify it with notepad or a similiar text editor. My favorite is Notepad++

2 Open it up and find the line that says:

extension_dir = "./"

and change it to

extension_dir = "C:\php\ext"

Find the line that says:

;session.save_path = "/tmp"

and change it to

session.save_path = "C:\WINDOWS\temp"

Installing MYSQL:

Next we will be installing MySQL version 5.
Follow the steps carefully.

1 Go to http://dev.mysql.com/downloads/mysql/5.0.html#downloads and download the "Windows (x86) ZIP/Setup.EXE (version 5.0.27)" to your desktop. (To do this you'll need to register an account with MySQL.)

2 Once "mysql-5.0.27-win32.zip" has finished downloading, you can extract it using WinZIP or a similiar program.

3 Once extracted, double click on the "Setup.exe" file. An installation wizard will appear.

Click "Next".

4 Select "Typical" Installation and click "Next".

5 Click "Install". (Be patient, this can take up to several minutes).

6 The next screen will ask you to "Sign Up". Select "Skip Sign-Up" for now.

7 The next screen will tell you that the installation wizard is complete. Make sure that the "Configure the MySQL Server now" field is checked before clicking "Finish".

8 The MySQL Server Instance Configuration Wizard should appear. Click "Next".

9 Select "Detailed Configuration" and click "Next".

10 Select "Developer Machine" and click "Next".

11 Select "Multifunctional Database" and click "Next".

12 Click "Next".

13 Select "Decision Support (DSS)/OLAP" and click "Next".

14 Select "Multifunctional Database" and click "Next".

15 Make sure "Enable TCP/IP Networking" is checked, the Port Number is set to "3306", and "Enable Strict Mode" is checked. Click "Next".

16 Select "Standard Character Set" and click "Next".

17 Check "Install As Windows Service", set the Service Name to "MySQL", and check "Launch the MySQL Server automatically". Make sure that the "Include Bin Directory in Windows Path" is NOT checked. Click "Next".

18 On the next screen, check the box that says "Modify Security Settings". Enter a password for the default "root" account, and confirm the password in the box below. Do NOT check the boxes "Enable root access from remote machines" or "Create An Anonymous Account". Click "Next".

19 Click "Execute". (This may take a few minutes. Be patient).

20 Click "Finish".

21 To test if MySQL was installed correct, go to: Start > All Programs > MySQL > MySQL Server 5.0 > MySQL Command Line Client. The MySQL Command Line Client will appear:

22 It will ask you for a password. Enter the password you created in step 18. (If you enter an incorrect password MySQL will automatically close the command line)

23 Next, type in the commands shown below: (shown in blue)

If you don't get any errors, and it returns the information shown above, then MySQL has been successfully installed! Next we will need to configure PHP to work with MySQL.

Configuring PHP to work with MySQL:

Now that both PHP and MySQL are installed, we have to configure them to work together.

1 Open up your php.ini file (C:/WINDOWS/php.ini) and find the line:

;extension=php_mysql.dll

To enable the MySQL extension, delete the semi-colon at the beginning of that line.

2 Next we must add the PHP directory to the Windows PATH. To do this, click: Start > My Computer > Properties > Advanced > Environment Variables. Under the second list (System Variables), there will be a variable called "Path". Select it and click "Edit". Add ";C:\php" to the very end of the string and click "OK".

3 Restart your computer for the changes to take effect.

4 Create a new file in your "htdocs" directory called "mysql_test.php".

5 Copy the following code into "mysql_test.php" and click save. (Make sure to replace the MYSQL_PASS constant with the MySQL Password you specified during the MySQL installation).

6 Open up Internet Explorer and type in "http://localhost/mysql_test.php". If the "mysql_test.php" page returns something similiar to:

ID: 1
Name: John

Then PHP & MySQL have been successfully configured to work together. Congratulations! The next and final step is to install phpMyAdmin.

Installing phpMyAdmin:

Now that both Apache, PHP and MySQL are installed, we can install phpMyAdmin, a tool that allows you to easily manage your MySQL databases.
1 Go to http://www.phpmyadmin.net/home_page/downloads.php and download "english.zip" under the phpMyAdmin 2.9.2 section to your desktop (I assume that since you are reading this article that you understand English).

2 Create a new folder called "phpmyadmin" in your "htdocs" directory. Extract the contents of the "phpMyAdmin-2.9.2-english.zip" ZIP file here. Your C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\phpmyadmin" directory should now look like:

3 Create a new file in the "phpMyAdmin" directory (above) called "config.inc.php". Place this code inside it and be sure to replace "YOUR_PASSWORD_HERE" (in both places below) with your MySQL Password:

4 phpMyAdmin has now been successfully installed! To use it, open up Internet Explorer and type in "http://localhost/phpmyadmin". This will bring you to the main phpMyAdmin page. Note is is always recommended not to install admin tool in default location if deployed on a server open to internet access for security reason.

Enjoy using Apache, PHP, MySQL, and phpMyAdmin!

My Favorites Flash AS3 Component/FLA Part II

2010-03-16T23:56:00.000-07:00

3D BUSINESS CARD SLIDE SHOW AS3

This is a XML controlled 3D slideshow, very easy to use and very customizable. It uses the 3D functions of Flash Player 10 (you need to install it if you do not have it); you need Flash CS4 if you want to open the FLA file!

This component can be used as a simple image/product slideshow, a 3d banner rotator or a business card slide show.
Settings you will find in the XML file:
- component width and height and card holder width and height
- mask width and height (you can display one image at a time or multiple images at once)
- transition times and types
- space between the cards
- arrows positioning, description positioning and transparency and also description text (html text)

http://activeden.net/item/3d-business-card-slide-show-as3/91738

AMAZING TWO LEVELS ACCORDION MENU AS3

This is an AS3 vertical accordion menu, XML driven and resizable. It has a structure of two levels. Each main item can have a submenu or it can open a link. For each item you can set a title and a HTML formatted description.
XML Settings:
- component width and height
- main item width and minimum height
- animation time
- items title and description
- items thumbnail image (optional)
- items link and link target

http://activeden.net/item/amazing-two-levels-accordion-menu-as3/88453

HORIZONTAL RESIZABLE ULTRA MENU AS3

This amazing menu can host an virtually UNLIMITED number of items organized on an unlimited number of levels.

The menu can auto-hide or stay visible, all colors can easily be changed in the xml file and.

It also supports scrolling, so if you have a lot of menu items (on any level) they will be scrolled if they don’t fit inside the display area.

This menu is ideal for displaying a great amount of menu items in a well structured manner.

It can open urls or trigger actions in flash !

Each level can have a style (colors, spacing etc.) assigned by specifying the xml corresponding to the specific style !
Settings you can change in the XML file (35+):
- auto-hide on/off
- open sub menu on click or on mouse-over
- open direction down or up
- auto-hide wait time
- sub-level open speed, transition time and type (ex. easeOutQuad)
- sub-level close speed, transition time and type
- use temporary display bar for auto-hide on/off, bar height, hit zone height, bar text (ex. “Move over to open”), bar background color, text color, arrow color
- menu width (can be set to 0 in order to make it expand to the entire stage)
- horizontal item spacing
- menu alignment
* Each style has the following options (each level can have a style xml assigned) :
- background colors for normal, mouse over and selected states
- delimiter width
- delimiter color
- button height
- text padding
- text font size
- text colors for normal, mouse over and selected states
- alignment for the level (left/center/right)
* Each menu item has the following options :
- menu item text (display label)
- action type (link or actionscript)
- url and target for link
- gotoandstop/gotoandplay and frame label/number for action

http://activeden.net/item/horizontal-resizable-ultra-menu-as3/88606

AS3 BUTTON CLASS

* Item Details
* Discussion

3comments
AS3 Button Class

by Flactor

Very easy to use class! you just need to use the interface to make the button and copy the code provided with the interface, then open a new fla file and paste the code in the first frame actions panel and import the needed font in the library and finished! Using this class you could arrange unlimited number of buttons, horizontally or vertically in 3 styles (simple, gradient and web 2.0). Complete documentation with examples and interface are available in the source file.

Could be used both in “time line” and “document Class”.

http://activeden.net/item/as3-button-class/81946

iButton TOGGLE SLIDER

Update: the sliders can now be dragged ON or OFF using the mouse.

All 100% vector graphics.

Easy to implement into your flash file. Just copy & paste!

Customizable settings:

* the text displayed for the ON and OFF states
* the easing used for the sliding animation
* the duration of the sliding animation
* the default state (ON or OFF )
* a callback function to run when the button has been toggled.

Font used on button: Lucida Gr

http://activeden.net/item/ibutton-toggle-slider/78111

POWERFULL FLASH ACCORDION MENU UNLIMITED LEVELS V3

This flash component allows you to create accordion menu’s and combobox’s in a few minutes and customize every detail without opening the flash file, because everything is xml driven.

As it says in the title, using this component you can create accordion menu’s with as many levels as you set in the xml file, there is no limit. Also you can customize each level individually, allowing you to create complex menus and desings.

In this new version you can set 4 different actions for the button, such as launch a link, go to a frame, load an image/swf or call a function.

Also this menu includes some nice API features that allows you to manipulate/navigate the menu dynamically.

http://activeden.net/item/powerful-flash-accordion-menu-unlimited-levels-v3/75262

CLEAM MEDIA PLAYER BUTTONS

Simple and easy to use and modify.

A collection of media player buttons,clean and modern, glossy, completely resizable vectors.

Just copy/paste or drag the buttons into your own project. It’s that easy.

The Zip contains an CS4 Fla, CS3 Fla, CS AI file and CS EPS file. I have included the Illustrator vectors in the pack.

For additional help contact me here at Graphic River or you can find my email address in the help file that comes with this product.

Tags: media player, buttons, player, style, clean, glossy, gloss, play, pause, stop, next, previous, forward, backward, star

http://activeden.net/item/clean-media-player-buttons/69078

AS3 WEB 2.0 BUTTON CLASS

Features:

Label, Label Color, Label Size, Font name, Colors of button layers(up, over, down), Width, Height, x Margin, y Margin, corner curves, ButtonMode, dropShadow, Activeness.

Can be used both in Document Class and time line.

http://activeden.net/item/as3-web-20-button-class/63030

THE SPINE XML IMAGE MENU

The Spine XML Image Menu is an image based menu with lots of flexibility that is straight-forward and simple, but also fun and creative. It scales the menu image items on mouse over and you can also choose to have a tooltip. On click, the menu will link out to a URL . If the stage is wider than the menu, the menu will be centered, otherwise, if the menu is wider than the stage, it will scroll left to right on the mouse’s horizontal position. It works great as a products menu that would link out to the specific product page.
The menu is XML driven and you can set the following things in the XML file:
– the background color
– the width of the menu items
– the height of the menu items
– the thickness of the border on mouse over of the menu items
– the amount of scaling on mouse over of the menu items
– whether the tooltip is on or off
– the background color of the tooltip
– the background transparency of the tooltip
– the image/SWF path for each of the menu items
– the tooltip text for each of the menu items
– the link URL for the on click of each of the menu items
– the link target for the on click of each of the menu items
So you can have as many images/SWFs as you want and they can be any size you want!

http://activeden.net/item/the-spine-xml-image-menu/50142

XML VERTICAL ACCORDION

XML Accordion generated from XML .

Each item in the xml has a title and a content attribute, allowing the flash file to load external contents into each item. The example above loads .jpg images, but these can be .swf, .png, .gif. (Basically any format allowed by Loader.load())

* Easy do edit xml file
* add as many items as your site can handle
* change which item opens by default
* clearly labeled layers and symbols for easy editing

http://activeden.net/item/xml-accordion/36743

HORIZONTAL XML ACCORDION

XML Accordion generated from XML .

Each item in the xml has a title and a content attribute, allowing the flash file to load external contents into each item. The example above loads .jpg images, but these can be .swf, .png, .gif. (Basically any format allowed by Loader.load())

* Easy do edit xml file
* add as many items as your site can handle
* change which item opens by default
* clearly labeled layers and symbols for easy editing

http://activeden.net/item/horizontal-xml-accordion/43382

PREMIUM TWO LEVEL EXPANDING MENU

Premium Two Level Expanding Menu

This is an XML driven vertical expanding menu designed to be clean, functional, easy to implement, and very customizable. All graphics are vector, and all is editable incliding colors, sizes, fonts etc easily from Flash. Each button either expands to show a sub menu, or links out to a url (“_self” or “_blank” can be set). You can also call javascript functions with it as well.

http://activeden.net/item/premium-two-level-expanding-menu/23880

CIRCLE MENU

Highly customizable menu made in ActionScript 3.
Any number of items with own colors and selected colors are supported. Many editable properties which vary the look and feel a lot.

Properties :
innerRadius, radius, angle, radiusDecrement, angleDecrement, angleIncrement, motionType, motionTime

http://www.ultrashock.com/#/asset/39553/circle-menu.html

ODOMETER AS3

A number Odometer - will 'odo' to any number it's set to, up or down, from any number it was last set to. Useful for Game score displays, hit counters etc.

http://www.ultrashock.com/#/asset/43513/odometer-as3.html

FLASH TOOLTIP AS3 V1.0.3

The flashTooltip component allows you to easily add a descriptive window that appears when the user moves their mouse over Flash buttons or movie clips. The tooltip may contain text, images or SWF's. Includes 5 built-in opening and closing effects. Fully customizable. .

http://www.ultrashock.com/#/asset/42610/flashtooltip-as3-v1.0.3.html

PROP3D 60s TV

Prop3D is a unique interactive Papervision3D media player component which can be customized and preloaded with your original videos, images & audio. The player itself is a 3D object, and can auto spin or be mouse tracked in a 3D space.

Prop3D includes a Collada 3D model and an ActionScript 3 component that loads it in a specific position using the component inspector. The really impressive thing about this component is that it allows you to load videos, images and sounds (displaying an equalizer) over a canvas within the model via an XML playlist. Finally, being able to customize the png meshes which construct the 3D object, makes it the most complete Papervision3D based component on the market.

We've teamed up with Zero Fractal Studios (the makers of the popular Tree3D component) to bring you these premium quality, unique and exclusive UltraComponents. Stay tuned for more!

Additional features include:
* Great Memory and CPU Handling (this feature requires flash player 9.0.115 or higher).
* Data Driven - Prop3D loads information from XML objects so you can customize your play list according to your needs.
You can also modify the play list with the API.
* Customizable mouse interaction - You can set the prop to face the mouse vertically, horizontally or both, with the screen always visible, or configure it by simple API calls.
Auto Spin Spin Speed - You can set the prop to spin automatically and change its speed, even with mouse interaction.
* Model customization - You can create your own props or use the props adding elements to the scene.
* Customizable UI Settings - Developers can easily customize every possible aspect of the prop display: position, rotation, camera, and even mouse interaction. .

http://www.ultrashock.com/#/asset/45591/prop3d-60s-tv.html

PROP3D MACBOOK

rop3D is a unique interactive Papervision3D media player component which can be customized and preloaded with your original videos, images & audio. The player itself is a 3D object, and can auto spin or be mouse tracked in a 3D space.

Prop3D includes a Collada 3D model and an ActionScript 3 component that loads it in a specific position using the component inspector. The really impressive thing about this component is that it allows you to load videos, images and sounds (displaying an equalizer) over a canvas within the model via an XML playlist. Finally, being able to customize the png meshes which construct the 3D object, makes it the most complete Papervision3D based component on the market.

http://www.ultrashock.com/#/asset/45589/prop3d--macbook.html

LOADBAR

Very easy to implement, use, and customise. Loadbar can be used for any file loading process. The progress bar is resized using some simple tweening to produce a smooth animation.

http://www.ultrashock.com/#/asset/38155/loadbar.html

CUSTOMCURSOR

CustomCursor is an AS3 class that allows you to quickly and easily add custom cursors to your Flash movies. Custom cursors can be created from bitmap images or MovieClips, so there really is no limit to the custom cursor designs you want to create.

Setting up your custom cursors is effortless. You simply tell the CustomCursor class which custom cursor an interactive object should use, and the everything is taken care of for you. Adding a drop shadow to your custom cursors is as simple as passing a DropShadowFilter to the CustomCursor class.

If you want to get cursor creative, CustomCursor is probably the only class you will need.

http://www.ultrashock.com/#/asset/37933/customcursor.html
http://www.ultrashock.com/#/asset/38155/loadbar.html

Internet Speeds and costs around the world

2010-03-03T16:43:00.001-08:00

http://www.geek2god.com/articles/brain_farts/internet-speeds-and-costs-around-the-world/

Flash PLayer 10.1 on the Google Nexus One

2010-02-26T14:45:00.001-08:00

Thibault Imbert and Michael Chaize demonstrate the power of the new Flash PLayer 10.1 on the Google Nexus One. http://vimeo.com/9596010 I apologize for my bad battery management shooting the video. For those who wants to see how the battery reacts playing Flash content on the Google Nexus One, please check that blog post: flashmobileblog.com/2010/02/24/battery-performance-with-flash-player-10-1-on-nexus-one/

Where Microsoft's Profits Come From

2010-02-18T10:12:00.000-08:00

http://www.osnews.com/story/22871/Where_Microsoft_s_Profits_Come_From

the evolution of Photoshop

2010-02-18T10:10:00.001-08:00

http://ronation.co.uk/photoshop/the-evolution-of-photoshop-1988-2010/

Erik Natzke

2010-02-09T20:49:00.000-08:00

Erik Natzke’s generative paintings are made using Flash, sometimes from sampled photos and video and other times from scratch. He controls very specifically the environment in which his creations thrive, leaving the artwork’s specificities to the whim of the code.

http://jot.eriknatzke.com/
http://vimeo.com/2090593
http://centripetalnotion.com/2007/11/30/03:35:23/

Android

2010-02-03T16:35:00.000-08:00

The Applications layer hosts all Android and third-party applications, and several or more third-party applications can execute simultaneously. However, as noted, doing so can shorten battery life.

Beneath the Applications layer is the Android Frameworks layer. This layer consists of Java classes that provide application functions such as window management, window content display, application messaging, and handling phone calls. Obviously the interface Android presents at this level uses the Java programming language, and because the source code is available, you can modify these classes to extend their capabilities or over override their behavior. Note that some of the lower levels in the stack present C++ interfaces.

Next on the software stack comes the Libraries and Runtime layer. The libraries implement 2D and 3D graphics support, along with multimedia content decoding. This layer has engines to support application features, such as a SQLite database engine and WebKit, which handles web content rendering.

Like Java ME, Android strives for hardware independence by using a bytecode interpreter to execute Android applications. However, it doesn't use Sun's JVM, but instead uses its own Dalvik Virtual Machine (DVM). The advantage to Android's use of a different bytecode interpreter is that the DVM was designed so that multiple instances of it can run, each in their own protected memory space, and each executing an application. While this approach offers stability and a robust environment for running multiple applications, it does so at the expense of compatibility with Java ME applications.

The lowest layer of the stack is the Linux kernel. It provides preemptive multitasking and system services such as threads, networking services, and process management. It handles all low-level drivers and manages the device's power

My favorites device right now is the

Samsung Behold II which is now official. It is offered by T-Mobile and run on Android OS. Behold II is also known as SGH-t939 and is quite an impressive phone.

The device has a 3.2″ AMOLED touch-screen, supports 3G networks and T-Mobile promises it will be out before the holidays.

Samsung Behold II will be Samsung’s first Android-powered device with T-Mobile and will have an integrated GPS receiver
so you can take full advantage of Google Maps, and hundreds of others apps that uses location information.

Samsungs Touchwiz 2.0 and Cube Interface is pretty slick and is a great demonstration of what Open GL can deliver on handled handset

Samsung Behold II Feature list

How to retrieve XMP Data/Cuepoints using the FLVPlayback

2010-01-27T19:28:00.000-08:00

Some users may wonder how they can retrieve the XMP data using the FLVplayback Component.

The best approach is based on the following article

http://www.adobe.com/devnet/flash/articles/flvplayback_fplayer9u3_04.html

and consist of implementing your own Custom callbacks via a custom client class

The FLVPlayback component automatically creates an instance of the class fl.video.VideoPlayerClient, assigns it to the NetStream's client property, and handles all callback messages that come through the NetStream. The default class fl.video.VideoPlayerClient handles only the callbacks onMetaData() and onCuePoint(). Both of these messages generate events (MetadataEvent.METADATE_RECEIVED and MetadataEvent.CUE_POINT) so that you do not need to register a custom class to handle these callbacks.

However, if you do wish to use custom callbacks, you must register a custom client class. You should extend fl.video.VideoPlayerClient to ensure that the onMetaData() and onCuePoint() handling supplied by VideoPlayer and FLVPlayback will continue to work properly.

The requirements for a custom client implementation are as follows:

* The constructor method must take an fl.video.VideoPlayer instance as its only parameter.
* The custom class must include a ready property which should be set to true when all messages expected at the very beginning of the NetStream have been received. This step is necessary because the VideoPlayer class initially hides the video and plays the beginning of the file to access the correct dimensions and duration of the video. It then quickly rewinds the video to the beginning and unhides it. If the rewind occurs before all messages at the very beginning of the file are received by VideoPlayer, there's a chance those messages may never be received.
* It is highly recommended that you declare the custom class as dynamic to avoid encountering runtime errors. Errors may appear if any callbacks are triggered that the class is not set up to handle.
* It is also recommended to extend fl.video.VideoPlayerClient to ensure proper onMetaData() and onCuePoint() handling.

1) Create a new extented Metadata EVENT

Copy IVPEvent.as from the source code of FLVplayback locally under your FLA project under fl\video sub folder

Use the code below to register a new extended event save it in a file ExtendedMetadataEvent.as

package fl.video {

import flash.events.Event;

/**
* Flash^® Player dispatches a ExtentedMetadataEvent object when the user
* requests the FLV/F4V/H264 file's metadata information packet (NetStream.onXMPData)
*
* @langversion 3.0
* @playerversion Flash 9.0.28.0
*/
public class ExtendedMetadataEvent extends fl.video.MetadataEvent {

/**
* Defines the value of the
* type property of a xmpDataReceived event object.
*
* @see FLVPlayback#event:xmpDataReceived xmpDataReceived event
* @eventType xmpDataReceived
* @langversion 3.0
* @playerversion Flash 10.0.0.0
*/
public static const XMPDATA_RECEIVED:String = "xmpDataReceived";

/**
* Creates an Event object that contains information about metadata events.
* Event objects are passed as parameters to event listeners.
*
* @param type The type of the event. Event listeners can access this information
* through the inherited type property. Possible values are MetadataEvent.XMPDATA_RECEIVED.
*
* @param bubbles Determines whether the Event object participates in the bubbling
* stage of the event flow. Event listeners can access this information through the
* inherited bubbles property.
*
* @param cancelable Determines whether the Event object can be canceled. Event listeners can
* access this information through the inherited cancelable property.
*
* @param info Determines the dynamic properties to add.
*
* @param vp Determines the index of the VideoPlayer object.
*
* @langversion 3.0
* @playerversion Flash 9.0.28.0
*
*/
public function ExtendedMetadataEvent( type:String, bubbles:Boolean=false, cancelable:Boolean=false,
info:Object=null, vp:uint=0) {
super(type, bubbles, cancelable);
super.info = info;
super.vp = vp;
}

/**
* @private
*/
override public function clone():Event
{
return new ExtendedMetadataEvent(type, bubbles, cancelable, info, vp);
}

} // class ExtendedMetadataEvent

} // package fl.video

2) Use the code below to register the custom client class:

package {

import fl.video.VideoPlayer;
import fl.video.VideoPlayerClient;
import fl.video.ExtendedMetadataEvent;

import flash.events.Event;
import flash.events.EventDispatcher;

import flash.display.Loader;
import flash.display.DisplayObjectContainer;
import flash.utils.ByteArray;

/**
* NetstreamDataVideoClient subclasses VideoPlayerClient, the default
* VideoPlayer.netStreamClientClass value. This way all
* the metadata and cue point handling built in the
* VideoPlayer works properly.
*
* The class is declared dynamic so if any other
* messages are received that we do not support in
* this class (onTextData(), other custom
* messages) no runtime errors will occur.
*/

dynamic public class NetstreamDataVideoClient extends VideoPlayerClient
{

/**
* This variable is set in onImageData and is used to help
* determine when the ready property should be true.
*/

protected var gotXMPData:Boolean;
protected var gotImageData:Boolean;
public var XMPString:String = "";
protected var verbose:Boolean = false;

/**
* The constructor must take a VideoPlayer as its
* only parameter. It needs to pass that argument
* along to the super constructor.
*/

public function NetstreamDataVideoClient(vp:VideoPlayer) {
super(vp);
gotImageData = false;
gotXMPData = false;
}

/**
* Handling for onImageData() message
* Loads the image bytes into a flash.display.Loader
* and adds the image to the
*/

public function onImageData(info:Object):void {
// Only handle onImageData() once. Any time we seek to the
// start of the file, the message will call this function
// again
trace("onImageData");
if (gotImageData)
return;
var loader:Loader = new Loader();
loader.loadBytes(info.data);
var parent:DisplayObjectContainer = _owner.root as DisplayObjectContainer;
if (parent) {
parent.addChildAt(loader, 0);
}
gotImageData = true;
}

public function onTextData(info:Object):void {
trace(info);
recurseTrace(info, "");
}

// FOR LOCAL FILE OR HTTP
public function onXMPData(info:Object):void {
if (gotXMPData)
return;

if (verbose)
trace("NetstreamDataVideoClient onXMPData");

// F4V/H264 uses data to pass raw XMP
if (info.data!= undefined)
{
if (verbose)
trace(info.data);
}
else
{
if (info.liveXML!= undefined)
{
// FLV uses liveXML to pass raw XMP
if (verbose)
trace(info.liveXML);
}
}

gotXMPData = true;

// for (var i in info)
// {
// trace(i + " is " + info[i]);
// }
// trace("####\n");

// XMP came from Adobe Media Encoder for Flash
if (info.data!= undefined)
{
XMPString = info.data;

_owner.dispatchEvent(new ExtendedMetadataEvent(ExtendedMetadataEvent.XMPDATA_RECEIVED, false, false, info));
}
else
{
if (info.liveXML!= undefined)
{
XMPString = info.liveXML;

_owner.dispatchEvent(new ExtendedMetadataEvent(ExtendedMetadataEvent.XMPDATA_RECEIVED, false, false, info));
}
}
}

private function recurseTrace(info:Object, indent:String):void
{
for (var i:* in info) {
if (typeof info[i] == "object") {
trace(indent + i + ":");
recurseTrace(info[i], indent + " ");
} else {
trace(indent + i + " : " + info[i]);
}
}
}

/**
* property that specifies whether early messages have been
* received so it is OK for the player to rewind back to the
* beginning. If we allow the VideoPlayer to rewind before
* all messages at the very beginning of the file are received,
* we may never receive them.
*
* The default class, VideoPlayerClient, only requires
* onMetaData() to be received before rewinding. onImageData()
* also appears at the beginning of the file, so we might miss
* that if we do not override this property and include a check
* for this data.
*/

override public function get ready():Boolean {
return (super.ready && gotImageData);
}

}
}

IMPORTANT: Don't try to parse the XMP data in the callback as it might be causing some timing issue and you want to give the hand back to the Netstream Object ASAP. Instead fire an event back to your client event listener and make sure you will interpret the data when the video will be in a READY to seek state.

3) Receive XMP Data using FLVPlayback

import NetstreamDataVideoClient;
import fl.video.ExtendedMetadataEvent;
import flash.events.*;
import fl.video.*;

VideoPlayer.netStreamClientClass = NetstreamDataVideoClient;

_playback = new FLVPlayback();
_playback.width = 1280;
_playback.height = 720;
_playback.autoRewind = false;
_playback.bufferingBarHidesAndDisablesOthers = true;
_playback.visible = true;
addChild(_playback);
_playback.addEventListener(MetadataEvent.METADATA_RECEIVED, metadataListener);
// the XMP one
_playback.addEventListener(ExtendedMetadataEvent.XMPDATA_RECEIVED,xmpListener);

private function xmpListener(inEvt:fl.video.ExtendedMetadataEvent):void {
var XMPString:String = "";
if (this.verbose)
trace("--- xmpListener ----");
if (this.verbose) {
if (inEvt.info.data!= undefined)
{
XMPString = inEvt.info.data;

trace("RECEIVED XMP DATA = " + XMPString);
// ready to parse
}
else
{
if (inEvt.info.liveXML!= undefined)
{
XMPString = inEvt.info.liveXML;

trace("RECEIVED XMP DATA = " + XMPString);
// ready to parse
}
}
}
}

Hope you enjoy this article !
Time to interpret the data now

http://younsi.blogspot.com/2008/12/interactive-video-in-flash-using-f4v.html

and store some useful XMP Data

http://www.actimus.com/

Free AS3 Interactive Video FLVPlayback component for FLASH CS5

http://shop.actimus.com/product_info.php?products_id=122

Urgence Haïti. Internet is finally up

2010-01-19T11:19:00.000-08:00

Bill (woody) is an independant internet guru who is highly respected.

On Jan 18, 2010, at 3:46 PM, @…edu.ht wrote:
| > The Teleco Building where ns1.nic.ht and ns2.nic.ht are (were) is completely dust.
| > Thanks a lot for your time to keep .ht up and running well.
|
| Believe me, that's the least we could do.
| And please know that you have our deepest sympathy.
|
| In case you have time to look it over, here are the other things we've been focusing our effort on.
| I'd appreciate a sanity-check, and any help you might be able to give us in prioritizing,
| or letting us know when you know that someone else is already covering something:
|
| - Arranging US military deliveries of diesel to Reynold for the two generators at Boutilliers Hill.
|
| - Coordinating Columbus, Tyco, the Marine Research labs at the University of Puerto Rico, and the US Navy,
| to try to get a festoon cable run from Santo Domingo to Port au Prince, and/or an extension
| from the Columbus branching unit that lies between Port au Prince and Guantanamo.
| We're making sure that people understand that if this comes to fruition, ownership of anything
| that's been aid-funded needs to be divided among Haitian ISPs, not monopolized within Columbus.
|
| - Arranging delivery of SIP VoIP phones (again to Reynold) for the use of the ISPs, emergency responders,
| and Haitian government. Questions here: Are stand-alone phones preferred, or FXS ports on routers,
| with analog phones? How many? Is the local Haitian ISP community prepared to support them with
| an Asterisk or equivalent back-end? Is there anyone there who's prepared to configure each of
| a batch of stand-alone phones?
|
| - Helping coordinate international law enforcement and the technical community to shut down and prosecute
| con-artists who are setting up fake relief donation web sites and spamming to promote them.
|
| What else can we do to help you?
| -Bill

I'm sure other people involved in the relief work can suggest other things, but a few comments from my point of view:

- Communications capability underpins the ability of other relief workers to do their jobs effectively, so although we, as a community, aren't feeding people or tending to their medical needs, we are helping those who are doing those crucial jobs by allowing them to focus on their work.

- In the short-term, the equipment that's been requested by people on the ground has either already been delivered, is onboard a ship that left Jacksonville about twelve hours ago, or is being containerized to load on a ship that's leaving from Port Everglades tomorrow.

- Also in the short-term, keep an eye out for con-artists who are trying to lure people in to fake aid-donation web sites with spam. Law enforcement is coordinating internationally to take those offline as promptly as possible.

- In the mid-term, what our community needs to do is to make sure that backhaul infrastructure gets into place to move traffic in the 1Gbps-10Gbps range from Port au Prince to Miami. There are several cable systems which land in Santo Domingo, and Columbus has a branching unit off Guantanamo, so our main efforts have been focused on getting a festoon cable run around from the Santo Domingo landing (the University of Puerto Rico Marine Research labs have committed their cable-laying ship, crew, and divers, but we're still looking for an appropriate spool of armored singlemode in the 12-24 core range (more certainly wouldn't hurt, as this would be unrepeatered), and on finding funding to get Columbus to run the spur in from their BU. BTC apparently has fiber already existing or in process of turn-up between Port au Prince and the Bahamas, but nobody's been able to get a response from them yet about its status.

- More generally, as a community, we do good when we make sure that places like this, places that may not have large or lucrative markets, are still served by diverse fiber, rather than by a single fragile monopoly, or not at all, as in Haiti's case. There are many countries as vulnerable as Haiti, and many of them have no fiber. Most humanitarian disasters happen in poor countries and these are generally the countries our community currently has the least capacity to serve. We can think a little more broadly than that, looking to a future when people in poor countries have more smartphones, and students and small businesses are getting online. We don't need to wait for markets to develop... we can invest in those markets, and _cause_ them to develop. Then they won't be as vulnerable to disasters like this.

- Thinking to the longer term... The majority of people who die in humanitarian disasters die of second-order effects like starvation and disease that come in the wake of an earthquake or flood or whatever. That's just beginning now in Haiti, and will continue for some time. The people who died in the earthquake itself will be far outnumbered by those who will die as a result of insufficiently prepared emergency response. PCH and Cisco have been trying for _years_ to get donors to support a ready-to-go emergency communications team for disaster response, but it's been impossible to get donors to fund _preparedness_ rather than after-the-fact response. But immediately after an emergency is the _most expensive_ time to acquire generators and fuel and solar panels and wind generators and batteries and satphones and fiber and space-segments and so forth. All of that can be _much more cheaply_ purchased or contracted for beforehand, and delivered on-site weeks earlier. A!
and those weeks are the weeks of effective response that reduce second-order deaths in the wake of an emergency. People who think they're being helpful with a donation now should understand that the donation would have saved ten times as many lives if it had been made a year ago, than if it's made now. If your companies have charitable foundations, please get them to think about that.

-Bill

avatar vs roger dean

2010-01-18T21:10:00.000-08:00

Did Prog Rock's Greatest Artist Inspire Avatar? All Signs Point To Yes

James Cameron spent years creating Avatar's floating islands and crazy dragons, and then an army of concept artists brought them to life. But maybe they had some inspiration from somewhere else? Like classic album-cover artist Roger Dean? Behold the evidence.

Chances are, if you've looked at a weirdshistic record cover by Yes, Asia or other bands, you've admired Roger Dean's paintings of surreal landscapes. If you've ever seen all good people turn their heads each day, then you're already a Dean fan.

Connor Freff Cochran, founder of Conlan Press (which is busy putting out a bunch of Peter S. Beagle books, hosting Beagle's 52/50 poetry subscription service, and putting out art books) contacted us and suggested that Avatar's lush moon might have gained some inspiration from Dean. And when you look at Dean's artwork and compare it to the concept art we posted the other day, it's hard not to see the resemblance.

All of this makes me want to rent Avatar (when it's released on DVD) and see if I can sync it up with YesSongs.

Original Post

http://io9.com/5426120/did-prog-rocks-greatest-artist-inspire-avatar-all-signs-point-to-yes/

Other post

http://blog.signalnoise.com/2010/01/06/avatar-vs-roger-dean/
http://www.yannicklejeune.com/2010/01/avatar-roger-dean.html

Web Analytics

2009-12-02T11:15:00.000-08:00

With the recent news on Yahoo Finance regarding Omniture-Adobe acquisition, I was curious to know a bit more about Web Analytics and provide pointers to anyone reading my blog. I posted an article some time ago on how to add Google Web Analytics to a SWF. Anyhow, here is a very great blog that I found at Tealium.com for those interested in Web Analytics. The blog is really well written by web Analytics Experts. Former Web Side Story, Visual Science and Omniture folks...

http://www.tealium.com/blog/