My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
ProjectOverview  
Provides information on the project. Its target audience is both reviewers and new project members.
Featured
Updated Feb 26, 2011 by theafr...@gmail.com

Table of Contents

Introduction

This project is being undertaken as part of UCLA course CS130. It is intended to be a microcosm of the software engineering experience, and as such involves a client, Dan Kegel, and multiple team members (14), listed below.

Teams

  • Team "A"
    • Andrew Freer: theafreer@gmail.com
    • Drew Wilder-Goodwin: tacomanator@gmail.com
    • Steve Feng: lokiazh@gmail.com
    • Sheng Lu: sheng255@gmail.com
    • Victor Zhu: victorrzhu@gmail.com
  • Team "B"
    • Bijan Beglari: link7909@gmail.com
    • Eulogio Gallo: eulogiogallo@ucla.edu
    • Bryan Chaidez: bryanch27@ucla.edu
    • Abimael Arevalo: abi62arevalo@ucla.edu
  • Team "C"
    • Alex Wong: mailto.alexk.wong@gmail.com
    • Samuel Karp: samuelbkarp@gmail.com
    • Christopher Barakian: barakianc@gmail.com
    • Andrew Webber: awebber90@gmail.com
    • Andy Reyes: mastertaxton@gmail.com

Description

The project is to get WINE's version of dxdiag to be more feature complete. Please refer to Dan Kegel's excellent project website for a more thorough explanation.

It should be noted that although Window's version of dxdiag.exe is easily obtainable via web downloads, it is intended for use on valid copies of Windows only, and is illegal to use or distribute otherwise. This is a key component of our project's motivation.

Team-Development Tools

  • Google Code Project: serves as a source code repository (subversion) for the project. As the final product should eventually reside entirely in the WINE repository, this repository acts as a staging ground.
  • Google Groups: serves as a mailing list/forum for all involved project members, including the client, Dan Kegel.

Build and Setup

dxdiag is designed to run natively on Windows. As such, it may be built and run on Windows, and also on Windows emulators (e.g. WINE). Currently, our team develops on a mixture of Windows and Linux-based systems (mostly Ubuntu). For those wishing to build WINE themselves, Dan Kegel has provided an excellent guide here.

The build script for dxdiag (source code obtainable here) is simple, and is located at (project)/2011/src/build.sh. To run it, enter "sh build.sh" from a BASH-like shell (Windows users typically use Cygwin). This will create an output directory at (project)/2011/src/bin, where dxdiag.exe can be found. Running dxdiag.exe will yield the UI interface. However, dxdiag.exe can be run as a command line tool as well. For full details, please see the User Guide.

Task Division and Progress

Architecture and Design

  • TabDefinition: Creating a tab for yadxdiag.
  • DxdiagnUsage: yadxdiag's DxDiag COM Interface usage.
  • ConformanceTestList: Conformance tests for dxdiag.
  • WineAndDotNET: Why .NET and other UI frameworks are not viable for our project.

Team-developed Guides and Resources

Links

Group Submissions

Group A


Sign in to add a comment
Powered by Google Project Hosting