A place to invest time in technology.

Keyboard functions

Here are 2 sites that show how to use the keyboard to navigate and more.

http://www.davidalison.com/2008/04/windows-to-mac-keystroke-mapping-quic...

http://guides.macrumors.com/Keyboard_shortcuts

Maybe we can use this to change the keyboard to function maps.

http://developer.apple.com/documentation/Cocoa/Conceptual/EventOverview/...

MSFT Powershell

As you, the loyal reader of my blog, know, I love the DOS "FOR" command. Yet today I found out about MSFT's "Power Shell". You can see "Getting Started with Windows Power Shell" here:

http://www.microsoft.com/technet/scriptcenter/topics/winpsh/manual/defau...

The Makefile, Project, and Workspace Creator (MPC)

http://www.ociweb.com/products/mpc maybe a good tool.

From above site:
"A fragile build system may preclude you from supporting diversity. Diversity in terms of platform targets for your software enables you to keep your vendor options open. Makefile, Project, and workspace Creator was originally developed by OCI to assist the ACE and TAO open source development community in supporting multi-platform software.

Developing applications that span platforms (portable code) has the beneficial side effect of producing more robust implementations. It does this by keeping your developers close to the mainstream of language features. MPC minimizes the additional cost normally associated with supporting more than one platform.

Team Settings in Visual Studio 2005

http://msdn.microsoft.com/en-us/library/bb245788(VS.80).aspx#vs05idetips_topic5

Shows how to have an entire team use the same setting. One will have to watch out for hard coded paths since one machine may have a different folder structure.

Basically, you save the settings you want to use and place them on a UNC location. Then you have your team use those settings.

Private Branches take setup and practice.

http://farrago.sourceforge.net/privateBranch.html

is a good page on branching in P4. It does not help towards automating the use of a Private Branch, but covers the topic well.

http://kb.perforce.com/UserTasks/CodelinesAndBranching/BranchingCod..gin...

is the Perforce article on Branching. It doesn't discuss using branches for other activities such as private branching.

http://geekswithblogs.net/EltonStoneman/archive/2008/04/04/scripting-bra...

uses a tool from codeplex one has to download. Why? Anything a P4 client can do can be scripted in lowly batch files. Ant is better, especially with the exec target in 1.7.0. Yet, Perforce gives out API's for Perl, Python and C++. But, it does show a good plan for those who may want a starting point.

Basically, to branch code one needs to set up Perforce first.

1) Decide what kind of branch you want:

Is this worthwhile?

"The p5layer product attempts to implement Private Developer Branches (PDB's) on top of Perforce. It is currently in beta, but seems to work well enough under load."

This is a product in open source from Release Engineering, Inc. It has been around since 1999. http://www.releng.com/company.html

http://www.releng.com/p5layer.html

A common issue with MSFT Tools

" Executing Adobe Begin on Windows XP on a Non-Development Machine

When an app is built using a version of MSVC, that version of Microsoft's Runtimes Libraries must be 'findable' by the OS in order to launch the application. Part of Microsoft's solution to this problem includes the embedding of an application manifest file into the application. On development machines, these files are automatically installed in C:\WINDOWS\system32\. The manifest file describes the binary's dependencies to external DLLs, and the OS reads the file and hunts down the dependencies to load them. In a clean-install XP system, the Runtime Libraries for MSVC 7.0, 7.1, and 8 do not exist, which will lead ultimately to the failure to launch applications built with these compilers on non-development machines.

Perforce and xCode, still an issue.

Having looked at the actual code, we could use a little touch up.
http://www.math.columbia.edu/~bayer/OSX/Perforce/

is a somewhat old but good source for XCode developers.

"p4files:
#! /bin/bash

find . -type f -print | egrep -v '^\./build/|\.DS_Store$|~\.nib' | rev | sort | rev "

or getting developers to keep the build folder out of the source!

CVS from the wikipedia

http://en.wikipedia.org/wiki/Concurrent_Versions_System

Where I found Bonzai and just a great article!

Syndicate content