Skip to main content

Google Code Repositories

Google is indeed conquering everything . I usually use Google Mail (gmail) , Google Docs , Google Calendar , Google Talk , Google Map , Google Pages , Blogger , Chrome (before my OS got hit by a virus last month , ill reinstall chrome soon) and yes Google Search . No wonder Google is all over .

Just last night , while searching for some articles on Model-View-Presenter topic , I downloaded a sample source code from a source which has "google" on its URL . The code was actually hosted by Google Code repository running Subversion. The main Google Code page displays most of the current development done and link to those projects . This include a link to Android , Googles platform for Mobile Development. Under Developers Resources you will find the Project Hosting link. This allows you to host your own project (up to 10 projects) and make it available to the web. Whats cool is that a Wiki page , Issue Tracker , Download Page , Source Code Page and Description page is provided . This is a good avenue for open source developers who wants their codes to be looked upon and being changed by the community . Im planing to host one of my initial open source web project here once it is ready for alpha relase. By the way , I found the C#-Ported DotNetNuke hosted in Google Code.

If I could remember it well , my previous officemate (Meng) once sent me a link to an article about Googlism, discussing profane thoughts on Google being a God .

Comments

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...