UCOSP: status report #5
Saturday, October 24, 2009
At the meeting today, Evan, Sarah, and I, the three of us discussed the pitfalls of using xampp to make drupal to talk directly with Ingres. They helped me to discoverred that my configuration was not right and my drupal was based on mysql but not Ingres.
Besides, preparing ourselves to build the code, we were comparing our understanding of what exactly is Geospatial. Since we are all not sure if Geospatial is a "specialist" of Ingres or a plugin to Ingres. I can see that we are building the Geospatial code which is one of the branches under Ingres in the repository, and the structure is almost identical to the main Ingres code base, which suggests that it may be the former.
Next week goal: Fix the communication between Drupal and Ingres.
Posted byA nerdy girl at 4:06 PM 0 comments
Labels: status report, UCOSP
UCOSP: status report #4
Friday, October 23, 2009
Today the team of students meet up on skype and discussed our common goals, our status updates, and the grading scheme of the term
Grading scheme:
As Andrew has suggested, we should be graded 75% on 5 patches that each student archieved by the end of the term, 5% on communication, 5% for the 2 blogs, 5% pro-rated for meeting attendance, 5% for participation on the mailing list, 5% for evidence of particupation in the community - mailing list posts, IRC interactions, etc.
However, the students concluded today at the meeting that communication is a very important criteria and determining factor for us to be successful. Some student may be able to get the 5 patches done and pass the course without communicating with the rest of the team. We all wish that the other components can be weight higher to stress their importance.
Status updates:
Eva Wong: Working on her understanding of the bigger pictures of the Geospatial code base while she's working on her build. It seems that her drupal was not communicating with Ingres properly, need to go back to fix that within next week.
Evan James Bowling: Installed Apache, PHP, and Ingres seperately under Windows XP, rather than making use of XAMPP. Resolved an issue to get PHP communicating with Ingres. Next week: Intend to have drupal installed and communicating with Ingres and using the GMap and Location modules.
Mary Mootoo, Sara Castaneda- Danaher: Got linux virtual machine installed on windows laptop with the help of Dr. Steven Case.
We are all working on sync'ing what everyone has and make sure that everyone has Drupal on Ingres, next moving on will be building code, meeting again tomorrow at noon.
Related blog posts:
Mary Mootoo
Eva Wong
Posted byA nerdy girl at 9:14 AM 0 comments
Fix: Visual Studio 2005 automatic project checkout crashes
Monday, October 19, 2009
I have recently got a copy of Visual Studio 2005 and its .NET framework. I am still new to these development tools.
Problem: Every now and then since a new project has been created, Visual Studio 2005 crashes on automatic checkout on that project.
Fix: Also get Visual Studio 2005 SP1, that includes a fix to this problem
Posted byA nerdy girl at 6:43 AM 0 comments
UCOSP: status report #3
Friday, October 16, 2009
For this week, I have been getting myself working around with subversion of Microsoft Visual Studio. Ankhsvn is the one that I have got. For next week, since it is packed with midterms, I will keep on working with subversion until next Friday before I'll be resuming my work.
Posted byA nerdy girl at 9:57 PM 0 comments
Labels: status report, UCOSP
UCOSP status report #2
Friday, October 9, 2009
I have been spending this week to get myself familiar with Microsoft Visual Studio and its .NET components. Such as using debugger, watching tutorial videos and demos of how to use the tool to write C code. Next week goal: Build Ingres.
Posted byA nerdy girl at 9:13 PM 0 comments
Labels: status report, UCOSP
Human factor in software engineering
Monday, October 5, 2009
Stressed and unpleasant relationships among co-workers always brings down productivity. As quoted from my professor in one of my small scale project course: Projects are very unlikely to fail on technology, but on human.
The sad thing is, if solving human-related problem is ever a logical one, then it must be NP hard, thus P != NP. In another words, complicated. It's the thing that we programmers are usually bad at.
A friend of mine and I were having a conversation some days ago about the human factor in software engineering, and about leadership in such projects, from there we pulled up this post. The leader of the project team is like every other manager, facing new problems on top of bugs in their code everyday.
Posted byA nerdy girl at 7:59 PM 0 comments
Labels: engineering, human factor, projects, software
Using Microsoft Visual Studio to code in C
Saturday, October 3, 2009
First step prior to building of Ingres, I need to grab Microsoft Visual Studio. I have been told that Microsoft Visual Studio is a neat tool to build C++, however, I have never heard anything about it for C code. Therefore, the first thing I explore about Visual Studio is that how to get it to work with C code.
Step #0: Know more about Microsoft Visual Studio
Step #1: Get Microsoft Visual Studio
If you are a college/university student, you can get a free copy from msdnaa if your college or university has affiliation with Microsoft. I have obtained a copy under msdnaa at University of Toronto.
Step #2: How to create a new project in C
Create an empty project. You do this by selecting Visual C++ >> General from the left hand tree in the New Project screen and selecting "Empty Project" From the panel on the right. Then once in the project, right click the source files folder from the tree on the left and "Add Item". Now here it will only give you the choice of creating a .cpp file, do it. Once you have the .cpp file created, you can write straight C in there and it will work fine.
Remember that C++ is actually "C" with classes. So you can write C code in a file with a cpp extension and it will execute as C. You could even rename the file later if you like. As long as it is an empty project you won't be including any extra libraries or frameworks that will flag your C as not legit "C++ code".
Step #3: Compiling in C
Ans: Go to Project and Properties, then somewhere in the myriad of options you'll see "Compile as C++" where you can change it to "Compile as C". And while you're at it, change the source file extension to .c instead of .cpp.
Posted byA nerdy girl at 9:45 PM 0 comments