Welcome![Sign In][Sign Up]
Location:
Search - Microsoft Visual Studio 8

Search list

[BREWBREWAppWizard

Description: brew sdk2.0 for vs2005 产生C++ hellowolrd示例程序框架的向导工程 使用方法: 1、解压缩 2、将BREWAppWizardForCpp文件夹拷到vc2005的向导目的下(比如c:\\Program Files\\Microsoft Visual Studio 8\\VC\\VCWizards) 3、将BREWAppWizardForCpp.vsdir和BREWAppWizardForCpp.vsz拷到C:\\Program Files\\Microsoft Visual Studio 8\\VC\\vcprojects下 4、重新启动VS2005,就可以看到创建项目换向导了。
Platform: | Size: 59482 | Author: wigo | Hits:

[Algorithmhyplas

Description: ************************************************************************ * * * * * THIS IS THE H Y P L A S 2.0 README FILE * * ----------------- * * * * HYPLAS is a finite element program for implicit small and large * * strain analisys of hyperelastic and elasto-plastic two-dimensional * * and axisymmetric solids * * * * HYPLAS v2.0 is the companion software to the textbook: * * EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for * * Plasticity: Theory and Applications. Wiley, Chichester, 2008. * * (www.wiley.com/go/desouzaneto) * * * * Copyright (c) 1998-2008 EA de Souza Neto, D Peric, D.R.J. Owen * *----------------------------------------------------------------------* * File last updated: 18 October 2008 * * * * This file belongs in the directory ../HYPLAS_v2.0 * ************************************************************************ * * * I M P O R T A N T * * * * READ SECTIONS 0 TO 3 OF THIS FILE CAREFULLY BEFORE ATTEMPTING * * TO COMPILE AND RUN THE PROGRAM HYPLAS ON YOUR COMPUTER !! * * * * THE AUTHORS DO NOT GUARANTEE THAT ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN IN THIS README FILE WILL WORK ON ANY PARTICULAR OPERATING * * SYSTEM. IF YOU DECIDE TO FOLLOW ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN HERE YOU MUST DO SO AT YOUR OWN RISK. * * * * * * BUG REPORTS: Please send bug reports to * * * * hyplas_v2.0@live.co.uk * * * * Messages sent to the authors' personal email addresses * * will NOT be answered. * ************************************************************************ This file contains the following sections: 0. Copyright statement and disclaimer 0.(a) Copyright statement 0.(b) Disclaimer 0.(c) Conditions of use 1. Introduction 1.(a) Note on portability 2. Compiling and running HYPLAS 2.(a) Memory requirements 2.(b) Testing a newly compiled executable 3. The HYPLAS directory tree 4. Cross-referencing between the source code and the textbook 5. HYPLAS error messaging 6. Further remarks on HYPLAS ************************************************************************ 0. COPYRIGHT STATEMENT AND DISCLAIMER ================================== 0.(a) Copyright statement ------------------- You may only use this program for your own private purposes. You are not allowed, in any circumstances, to distribute this program (including its source code, executable and any other files related to it, either in their original version or any modifications introduced by you, the authors or any other party) in whole or in part, either freely or otherwise, in any medium, without the prior written consent of the copyright holders. 0.(b) Disclaimer ---------- This program (including its source code, executable and any other files related to it) is provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of fitness for purpose. In particular, THIS PROGRAM IS BY NO MEANS GUARANTEED TO BE FREE FROM ERRORS. This program (or any modification incorporated to it by you, the authors or any other party) will run entirely at your risk. The results produced by this program are in no way guaranteed to be fit for any purpose. Under no circumstances will the authors/copyright holders be liable to anyone for damages, including any general, special, incidental or consequential damages arising from the use or inability to use the program (including, but not limited to, loss or corruption of data, failure of the program to operate in any particular way as well as damages arising from the use of any results produced by the program for any purpose). 0.(c) Conditions of use ----------------- You may only use this program if you fully understand and agree with the terms of the above disclaimer. You must not use this program if you do not agree with or do not understand (fully or in part) these conditions of use. 1. INTRODUCTION ============ HYPLAS is a finite element code for small and large strain analysis of hyperelastic and elasto-plastic solids. Most procedures implemented in HYPLAS are described in detail in its companion textbook: EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for Plasticity: Theory and Applications. Wiley, Chichester, 2008 (www.wiley.com/go/desouzaneto). 1.(a) Note on Portability ------------------- HYPLAS has been written in standard ANSI FORTRAN 77. Currently, the only known (and deliberate) exceptions to the FORTRAN 77 ANSI standard are the instructions: INCLUDE '' used in many routines to include the HYPLAS database files (common blocks and global variables), and; CALL GETENV('HYPLASHOME',HYPLASHOME) used in subroutine "ERRPRT" (file ../HYPLAS_v2.0/src/GENERAL/errprt.f). This instruction inquires the name of the system environment variable HYPLASHOME and writes it on the character string HYPLASHOME. This instruction is NOT part of the ANSI FORTRAN 77 standard, but seems to work in most currently available FORTRAN 77 compilers. 2. COMPILING AND RUNNING H Y P L A S ================================== The HYPLAS source code is stored in directory ../HYPLAS_v2.0/src/ (../HYPLAS_v2.0/ being the current directory) and all its subdirectories. To generate an executable file, you just need to compile the FORTRAN source files: ../HYPLAS_v2.0/src/hyplas.f and ../HYPLAS_v2.0/src/*/*.f together. We recommend that the executable HYPLAS be stored in the directory ../HYPLAS_v2.0/bin to which the environment variable HYPLASHOME should be set (see below how to set a system environmental variable). WINDOWS (R) systems ------------------- On Microsoft Windows(R) systems, HYPLAS has been successfully compiled using Intel Visual Fortran Compiler(R) integrated with Microsoft Visual Studio(R). Here you only need to create a project that contains all Fortran source files mentioned above as well as the include files ..\HYPLAS_v2.0\src\*.INC On a Windows XP system, the system environment variable HYPLASHOME can be set as follows: 1. Open a File Manager 2. Right-click on the "My Computer" icon 3. Select "Properties" on the drop-down menu 4. A new window named "System Properties" will pop-up. Here select the "Advanced" tab. 5. On the "Advanced" tab, click the "Environment Variables" button. 6. A new window titled "Environment Variables" will pop-up. Here click the button "New" in the "System Variables" section of the window. 7. A new window will pop-up titled "New System Variable". Here you should fill the fields "Variable name" and "Variable Value", respectively, with HYPLASHOME and the path name (in full) of the directory ..\HYPLAS_v2.0\bin. 8. Press "OK" on the relevant pop-up windows. 9. The next time the computer is REBOOTED, this variable will be set to the correct path and HYPLAS should be able to find the error messages file ERROR.RUN if required. UNIX/LINUX systems ------------------ In a UNIX/LINUX operating system using a C-shell, for instance, the HYPLASHOME environment variable should be set with the command: setenv HYPLASHOME where here denotes the full path to the directory ../HYPLAS_v2.0/bin. To compile HYPLAS (from directory ../HYPLAS_v2.0/src) with a FORTRAN 77 compiler such as g77, you can use the command: g77 -o ../bin/hyplas hyplas.f */*.f Note that the executable file "hyplas" will be stored in the directory ../HYPLAS_2.0/bin (i.e. the directory set in the HYPLASHOME environment variable). Alternatively, you may use the Makefile provided (with suitable modifications, if needed) to create the HYPLAS executable. IMPORTANT: Before generating a HYPLAS executable, read Sections 2.(a) and 2.(b) below. 2.(a) Memory Requirements ------------------- HYPLAS memory requirements depend on the array dimensioning parameters set in files: ../HYPLAS_v2.0/src/ ELEMENTS.INC GLBDBASE.INC MATERIAL.INC MAXDIM.INC Files ELEMENTS.INC, GLBDBASE.INC and MATERIAL.INC contain parameters which are associated with the currently implemented finite elements and materials. DO NOT MODIFY THEM ! unless you are absolutely sure of what you are doing (only developers coding new elements or new material models/analysis types may need to modify them by changing the existing dimensioning parameters and/or including new parameters). The ONLY dimensioning file that can be safely modified by the average user is the file MAXDIM.INC This file contains the array dimensioning parameters related to the maximum permissible dimension of problems to be analysed by HYPLAS. These parameters include the maximum number of nodes, elements, element groups, etc. If necessary, CHANGE THESE PARAMETERS TO SUIT YOUR PROBLEM SIZE/MEMORY REQUIREMENTS before compiling HYPLAS. 2.(b) Testing a newly compiled executable ----------------------------------- After you have successfully compiled the HYPLAS source code and created an executable file, the next step is to run some tests to verify that HYPLAS is working well. To do this, proceed as follows: The directory ../HYPLAS_v2.0/book_examples/data_files contains a series of data files named .dat of benchmarked examples described in the companion textbook. The corresponding (benchmarked) result files are in the directory ../HYPLAS_v2.0/book_examples/result_files This directory contains a series of result files named .res generated with the current version of HYPLAS on a tested platform. All these files have been named such that their names start with the textbook section number where the corresponding example is described. For instance, files 14_9_2_tresca.dat and 14_9_2_tresca.res refer to a problem described in section 14.9.2 of the textbook, and so on. To check that HYPLAS is working well on your platform, after compiling HYPLAS, run the program HYPLAS for the examples of files .dat and compare the newly generated results .res with their benchmarked counterparts (of the same filename) in the result_files directory. To run an example, execute HYPLAS and use the keyboard to enter the name of the corresponding data file in full (including the extension .dat). To compare the benchmarked .res files against their newly generated you may proceed as follows: 1. On MICROSOFT WINDOWS systems - Here we have successfully used the software "ExamDiff" (the task was made particularly easy by selecting "View" and then the "Show Differences Only" option - this refers to version 1.8 of this software). 2. On UNIX/LINUX systems - Here we use the "diff" command from a shell window (and set the option to ignore blank spaces). A shell script may be used to perform this task automatically (including running HYPLAS and checking for result file differences) for all benchmarked examples provided. IMPORTANT: THE ONLY ACCEPTABLE DIFFERENCES BETWEEN A THE NEWLY GENERATED RESULT FILES AND THEIR BENCHMARKED COUNTERPARTS ARE THE DIMENSIONING PARAMETERS (FROM FILE MAXDIM.INC) USED TO COMPILE THE NEW EXECUTABLE (THESE PARAMETERS ARE PRINTED RIGHT AT THE BEGINNING OF THE RESULT FILES) AND NUMERICAL DIFFERENCES IN RESULTS DUE TO NUMERICAL "ROUNDING-OFF" (THESE ARE VERY SMALL DIFFERENCES THAT DEPEND ON THE PRECISION OF ARITHMETIC OPERATIONS IN THE PLATFORM USED). ALSO NOTE THAT THE EXAMPLES OF THE COMPANION TEXTBOOK DO NOT COVER ALL FEATURES OF HYPLAS. HENCE THIS TEST DOES NOT GUARANTEE THAT EVERYTHING IS WORKING PROPERLY. 3. THE H Y P L A S DIRECTORY TREE ================================ 3.(a) Summary ------- ../ HYPLAS_v2.0/ bin/ book_examples/ data_files/ result_files/ man/ html/ src/ CRYSTAL/ DAMAGE/ DAMAGED_ELASTIC/ DRUCKER_PRAGER/ ELASTIC/ ELEMENTS/ GENERAL/ MATERIALS/ MATHS/ MOHR_COULOMB/ OGDEN/ TRESCA/ VON_MISES/ VON_MISES_MIXED/ 3.(b) Description ----------- The HYPLAS program directory tree is organised as follows: ../HYPLAS_v2.0/ (this directory) This is the HYPLAS root directory, where the HYPLAS directory tree starts. ../HYPLAS_v2.0/bin/ This directory contains the file ERROR.RUN where most HYPLAS error/warning messages are. IMPORTANT: the environment variable HYPLASHOME should be set to this directory. Otherwise, HYPLAS will not find its error/warning messages when required. We also recommend that the EXECUTABLE of HYPLAS be stored in this directory. ../HYPLAS_v2.0/book_examples/ This directory has the following subdirectories: ../HYPLAS_v2.0/book_examples/data_files ../HYPLAS_v2.0/book_examples/result_files Refer to Section 2.(b) above for further details. ../HYPLAS_v2.0/man/ This is the HYPLAS documentation/manuals directory. It contains the following files: input_man.txt - A concise input data manual for HYPLAS in ASCII format; hyplas_calltree.txt - Contains a flowgraph (shows the call tree) of HYPLAS in ASCII-format. Note: calls to function subprograms are not included in this flowgraph; and the subdirectory: ../HYPLAS_v2.0/man/html This directory contains the hypertext (HTML) format Fortran source code and of manual pages of the entire HYPLAS program. Manual pages with descriptions of each function/subprogram including their argument list are linked to their corresponding HTML-format source code. This allows the user the navigate through the HYPLAS source code using a web browser. To start at the main program, use your web browser to open the file hyplas.html. This facility should be helpful to those trying to understand the flow of program HYPLAS. ../HYPLAS_v2.0/src/ This directory (and its subdirectories) contains the Fortran source code of HYPLAS. The files containing the sources are named following the standard practice: .f where is the name of the FORTRAN procedure (subroutine, function subprogram, etc.) whose source code is in file .f. The source code of the HYPLAS main program is in file hyplas.f and the HYPLAS database (COMMON blocks, array dimensioning parameters and other global parameters) is coded in the "include files" ELEMENTS.INC GLDBASE.INC MATERIAL.INC MAXDIM.INC in this directory. In addition, this directory contains a file named "Makefile" (UNIX-LINUX Release only) which may be used for compiling and linking HYPLAS in UNIX/LINUX systems. The subdirectories of ../HYPLAS_v2.0/src are as follows: ../HYPLAS_v2.0/src/CRYSTAL Contains the source code of all procedures related to the finite strain single crystal plasticity model implemented in HYPLAS. ../HYPLAS_v2.0/src/DAMAGE Source files of the procedures related to the Lemaitre ductile damage model implementation. ../HYPLAS_v2.0/src/DAMAGED_ELASTIC Source files of the procedures related to the damaged elasticity model with crack closure effect. ../HYPLAS_v2.0/src/DRUCKER_PRAGER Source files of the procedures related to the implemented Drucker-Prager plasticity model. ../HYPLAS_v2.0/src/ELASTIC Source files of the procedures related to the linear elasticity model (Hencky model under large strains) implemented. ../HYPLAS_v2.0/src/ELEMENTS Source files of the element interfaces and element-related procedures. ../HYPLAS_v2.0/src/GENERAL Source files of general procedures. ../HYPLAS_v2.0/src/MATERIALS Source files of the material interfaces. ../HYPLAS_v2.0/src/MATHS Source files of the mathematical procedures. ../HYPLAS_v2.0/src/MOHR_COULOMB Source files of the procedures related to the implemented Mohr-Coulomb plasticity model. ../HYPLAS_v2.0/src/OGDEN Source files of the procedures related to the implemented Ogden hyperelasticity model. ../HYPLAS_v2.0/src/TRESCA Source files of the procedures related to the implemented Tresca plasticity model. ../HYPLAS_v2.0/src/VON_MISES Source files of the procedures related to the implemented von Mises plasticity model with isotropic hardening. ../HYPLAS_v2.0/src/VON_MISES_MIXED Source files of the procedures related to the implemented von Mises plasticity model with mixed isotropic/kinematic hardening. 4. CROSS-REFERENCING BETWEEN THE SOURCE CODE AND THE TEXTBOOK ========================================================== Many references are made in the textbook to various subprograms of HYPLAS. These are usually made when a particular procedure described in the text is implemented in the program. The reader should refer to the textbook index. Also, a substantial number of comment lines have been added to the source code of HYPLAS with reference to sections, figures, boxes, etc of the textbook related to the part of the code in question. Such references are usually displayed after the word "REFERENCE:" (in capitals) on commented lines. Searching for this word will take you to the line of code where the particular routine has a reference to the textbook. NOTE: Occasional references to other textbooks/journal papers are also made following the word "REFERENCE:" on commented lines. 5. HYPLAS ERROR MESSAGING ====================== Most error/warning messages issued by HYPLAS are in the ASCII-format file ERROR.RUN (kept in the HYPLASHOME directory - ../HYPLAS_v2.0/bin). All such error/warning messages have an identification code (e.g. ED0015) which is printed both to the standard output (this is usually the computer screen) and to the relevant results file. If you wish to find where in the source code a particular message is being issued, then perform a search for the corresponding message identification code in the entire source code of HYPLAS. 6. FURTHER REMARKS ON HYPLAS ========================= 6.(a) Program efficiency THIS SECTION IS OF INTEREST ONLY TO THOSE WANTING TO MAKE HYPLAS RUN FASTER. It is particularly stressed in the textbook that this program has not been designed having efficiency in mind (refer to Section 5.1.2 of the textbook). Its structure has been designed mainly to illustrate in a relatively clear manner the computer implementation of the techniques and algorithms described in the text, with a particular view to the implementation of solid constitutive models and finite elements. For those who are especially interested in the speed of the code, there are a few tips that could help in this direction. Unfortunately, these involve modifications to the source code which is probably most appropriate to readers with a good level of experience in finite element programming. To those with this particular interest, we can suggest the following: (i) The use of faster linear solvers This is probably the change that would result in a greater gain in efficiency. The Frontal Method adopted in subroutine FRONT (file ../HYPLAS_v2.0/src/GENERAL/front.f) has been designed originally to save memory (back in the days when computer memory was severely limited). There are currently a vast number of methodologies which focus on speeding up the linear solution, in addition to reducing memory storage requirements (which is a particularly important issue in the solution of large scale problems). Some of these are extensions/refinements of the original Frontal solver. We remark that a number of such procedures (with their respective source codes) are available (conditions may apply) from the LAPACK (Linear Algebra PACKage - http://www.netlib.org/lapack) repository or from the HSL Library (http://www.cse.cse.scitech.ac.uk/nag/hsl). For the reader interested in gaining speed, we would recommend the replacement of the existing solver of FRONT by a faster one. We remark though that this is a substantial programming task. Another aspect here is the fact that computing times in FRONT are directly linked to the frontwidth of the system which, in the present version of HYPLAS is fixed and depends, for a given mesh, on how the degrees of freedom are numbered (node numbering). The incorporation of a frontwidth optimiser (which re-numbers the degrees of freedom in order to minimise the frontwidth) in FRONT could produce some good savings in computing times. Such savings become particularly noticeable in larger problems where the original node numbering produces an excessively large frontwidth. (ii) Material-specific computations The issues pointed out here affect only the computing times for specific material models and are expected to have a much lower impact in overall speed than the linear solver issue discussed above. Some of the material model-specific computations carried out in HYPLAS could be made a bit faster. For example, for isotropic models whose stress update is carried out in the principal stress space (such as the Tresca and Mohr-Coulomb models - see routines SUTR and SUMC, files ../HYPLAS_v2.0/src/TRESCA/sutr.f and ../HYPLAS_v2.0/MOHR_COULOMB/sumc.f, respectively) the spectral decomposition of the stress in carried out in the state update update routine and then repeated in the corresponding routine for computation of the consistent tangent operator (refer to files ../HYPLAS_v2.0/src/TRESCA/cttr.f and ../HYPLAS_v2.0/src/MOHR_COULOMB/ctmc.f, respectively, for the Tresca and Mohr-Coulomb plasticity models). Some savings in computing time can be achieved here by storing the stress eigenprojection tensors (these can be stored as state variables) during the execution of the state updating and then retrieving them later for use in the computation of the consistent tangent operator. This change can be incorporated to the code relatively easily. The computation of the exponential map and is derivative for the single crystal plasticity model (routines EXPMAP, file ../HYPLAS_v2.0/src/CRYSTAL/expmap.f and DEXPMP, file ../HYPLAS_v2.0/src/CRYSTAL/dexpmp.f) is carried out in three dimensions (these routines have been adapted from an earlier three-dimensional code). To improve efficiency, these can be adapted to work only in two-dimensional problems by removing the unnecessary operations related to the third dimension. 6.(b) Output of nodal averaged values The reader should be aware that the way in which nodal averaged values of stresses and other variables are calculated in HYPLAS is very basic (and rudimentary). This feature of the program is made available only to help those interested in producing contour plots, etc from results presented in HYPLAS result files and should be useful in many circumstances of interest. This facility has in fact been used in producing many of the figures presented in the textbook. But note, for example, that the values of incremental plastic multipliers for plasticity models may take (inadmissible) negative values when extrapolated from Gauss-point to nodes and averaged. We remark that more sophisticated and refined techniques of transferring Gauss point values of variables to nodal points and obtaining the corresponding smoothed field are available in the current literature. These fall outside the scope of the companion textbook of HYPLAS.
Platform: | Size: 11008084 | Author: gtcewli3 | Hits:

[Game EngineAres1.0引擎代码

Description: Ares1.0引擎代码,Ares引擎是由Honeysuckle(快乐魔导师)推出的用于游戏开发的开放源码引擎。这套引擎是基于Microsoft Windows 2000,DirectX 8.0,Visual Studio .NET开发,特点是“服务聚合,面向用户,开放源码,代码重用,跨用户平台”。使用这套引擎,你可以轻易的写出基于DirectX的游戏,可以对图像,声音,网络,视频等服务进行方便的访问和控制。由于完全基于面向对象编写,引擎本身具有很强的扩展性,用户可以在引擎的基础上,添加少量的代码即可获得需要的服务。各模块独立开发的同时又继承统一的体系结构,为后续版本的开发奠定了良好的基础-Ares1.0 engine code, Ares engine from Honeysuckle (Happy Modaoshi) launched for the development of the game open source engine. This engine is based on Microsoft Windows 2000, DirectX 8.0, Visual Studio.NET development, which is characterized by "service aggregation, user-oriented, open-source, code reuse, cross-platform users. " The use of this engine, you can easily write DirectX-based games, right image, voice, network, video services convenient access and control. Because of the total based on object-oriented development, the engine itself is very scalable, users can on the basis of the engine, add a small amount of code is required to access the services they need. The independent development of the module also inherit a unified architecture for the follow-up version of the
Platform: | Size: 60416 | Author: 我是谁 | Hits:

[OpenGL programMicrosoft_Visual_Studio_8

Description: vc.net2005下开发OpenGL程序的框架-vc.net2005 procedures developed under the framework OpenGL
Platform: | Size: 689152 | Author: WestWeald | Hits:

[BREWBREWAppWizard

Description: brew sdk2.0 for vs2005 产生C++ hellowolrd示例程序框架的向导工程 使用方法: 1、解压缩 2、将BREWAppWizardForCpp文件夹拷到vc2005的向导目的下(比如c:\Program Files\Microsoft Visual Studio 8\VC\VCWizards) 3、将BREWAppWizardForCpp.vsdir和BREWAppWizardForCpp.vsz拷到C:\Program Files\Microsoft Visual Studio 8\VC\vcprojects下 4、重新启动VS2005,就可以看到创建项目换向导了。-brew sdk2.0 for vs2005 generated C++ hellowolrd Framework sample project using the wizard: 1, extract 2, will BREWAppWizardForCpp folder wizard Kaodao vc2005 purposes (such as c: Program FilesMicrosoft Visual Studio 8VCVCWizards) 3, will BREWAppWizardForCpp.vsz Kaodao BREWAppWizardForCpp.vsdir and C: Program FilesMicrosoft Visual Studio 8VCvcprojects under 4, restart the VS2005, you will see the Create Project wizard for the.
Platform: | Size: 59392 | Author: wigo | Hits:

[SQL Servernovel

Description: 在线小说阅读,网站主要实现以下3个功能模块:(1)管理员模块(2)读者模块(3)作者模块;每个模块下边又细分了功能小模块。本系统以中文版Microsoft Visual Studio 2005为前台开发工具,用中文版SQL作为后台数据库。Macromedia Dreamweaver 8辅助页面的美化。-Online novels to read, websites to achieve the following three main functional modules: (1) the administrator module (2) reader module (3) Author module below each module also features a breakdown of small modules. This system to the Chinese version of Microsoft Visual Studio 2005 development tools for the future, using the Chinese version of SQL as a back-end database. Macromedia Dreamweaver 8 ancillary landscaping page.
Platform: | Size: 441344 | Author: 瓶子 | Hits:

[BREWBREW_Addins_3.0_for_Microsoft_Visual_Studio

Description: 用Visual Studio开发BREW应用程序的插件。可用于VC6和VC.NET。-Visual Studio Add-in for developing BREW applications. Can be used in VC6 or VC.NET.
Platform: | Size: 1392640 | Author: Pikoona | Hits:

[File Formatdoc

Description: 1. Download the version you want: * Version 1.3.4 (30 Aug 2007) -- this is the latest version for UNIX/Linux and Windows * Previous versions 2. Unzip the file, which will create a directory called klt and place all the files there 3. Compile and run the code * On UNIX / Linux, move to the klt directory, type make. Now try some examples, by typing example1, etc. * For Microsoft Visual C++ 6.0, open the klt.dsw file, compile, and run. Change the constant in main.cpp to run the different examples. * For Microsoft Visual Studio .Net/7/8, open the klt.sln file, compile, and run. Change the constant in main.cpp to run the different examples. 4. Notice that, for your convenience, unofficial copies of the User and Reference Manuals can be found in the doc directory. - 1. Download the version you want: * Version 1.3.4 (30 Aug 2007) -- this is the latest version for UNIX/Linux and Windows * Previous versions 2. Unzip the file, which will create a directory called klt and place all the files there 3. Compile and run the code * On UNIX/Linux, move to the klt directory, type make. Now try some examples, by typing example1, etc. * For Microsoft Visual C++ 6.0, open the klt.dsw file, compile, and run. Change the constant in main.cpp to run the different examples. * For Microsoft Visual Studio .Net/7/8, open the klt.sln file, compile, and run. Change the constant in main.cpp to run the different examples. 4. Notice that, for your convenience, unofficial copies of the User and Reference Manuals can be found in the doc directory.
Platform: | Size: 44032 | Author: Alex | Hits:

[VC/MFCProfessionalMFC

Description: Professional MFC. Chapter 1: The Microsoft Developer Studio Chapter 2: The Wizards and The Gallery Chapter 3: The Application Architecture Hierarchy Chapter 4: The Document/View Architecture Chapter 5: Using Dialogs and Controls in MFC Chapter 6: User Interface Issues Chapter 7: Advanced User Interface Programming Chapter 8: Using the Windows Common Controls Chapter 9: Writing Programs for the Windows Shell Chapter 10: Utility and Exception Classes Chapter 11: Writing Multithreaded Applications with MFC Chapter 12: Creating Dynamic-link Libraries Chapter 13: Writing Database Applications Chapter 14: Writing OLE Containers Chapter 15: Writing OLE Servers Chapter 16: ActiveX Controls Chapter 17: ActiveX Control Containers Chapter 18: Internet Client Programming Chapter 19: Internet Server Programming Appendix A: Installing Visual C-Professional MFC. Chapter 1: The Microsoft Developer Studio Chapter 2: The Wizards and The Gallery Chapter 3: The Application Architecture Hierarchy Chapter 4: The Document/View Architecture Chapter 5: Using Dialogs and Controls in MFC Chapter 6: User Interface Issues Chapter 7: Advanced User Interface Programming Chapter 8: Using the Windows Common Controls Chapter 9: Writing Programs for the Windows Shell Chapter 10: Utility and Exception Classes Chapter 11: Writing Multithreaded Applications with MFC Chapter 12: Creating Dynamic-link Libraries Chapter 13: Writing Database Applications Chapter 14: Writing OLE Containers Chapter 15: Writing OLE Servers Chapter 16: ActiveX Controls Chapter 17: ActiveX Control Containers Chapter 18: Internet Client Programming Chapter 19: Internet Server Programming Appendix A: Installing Visual C++
Platform: | Size: 2899968 | Author: Minh | Hits:

[OtherMyCircle_v2_test

Description: ActiveX Control: hand (analog) indicator. - Microsoft Visual Studio 2005 (v. 8.0.5) - Microsoft .NET Framework v. 2.0.50727
Platform: | Size: 242688 | Author: Sofienko | Hits:

[Windows MobileMyProgressBar

Description: Gradient ProgressBar for PDA (Windows Mobile) - Microsoft Visual Studio 2005 (version 8.0.5) - Microsoft .NET Framework v. 2.0.50727
Platform: | Size: 129024 | Author: Sofienko | Hits:

[Game EngineReflection_Mir

Description: 镜面反射ClipMir实例------Microsoft Visual Studio 8(即VS2005)Win32SDK 程序-Specular reflection ClipMir instance------ Microsoft Visual Studio 8 (ie VS2005) Win32SDK procedures
Platform: | Size: 3439616 | Author: weiguian | Hits:

[Windows CEMicrosoft-Mobile-Development-Guild

Description: 第Ⅰ部分 移动应用程序开发基础  第1章 .NET Compact Framework移动平台 1.1 Visual Studio移动应用程序开发快速入门   1.1.1 Visual Studio版本的选择   1.1.2 其他软件  1.1.3 目标、半台:Pocket PC,Smartphone还是Windows CE  1.1.4 Windows CE与Windows Mobile的差异  1.1.5 选择.NET Compact Framework的版本 1.2 .NET Framework 2.0与.NET Compact Framework 2.0的差异  1.2.1 应用程序配置文件   1.2.2 ClickOnce   1.2.3 Ngen.exe   1.2.4 远程功能    1.2.5 序列化   1.2.6 打印   1.2.7 Web窗体 1.3 .NET Compact Framework 1.0版和2.0版的差异   1.3.1 Windows窗体   1.3.2 显示与布局的管州   1.3.3 数据 .  1.3.4 通信   1.3.5 COM互操作   1.3.6 图形编程   1.3.7 安全   1.3.8 线程   1.3.9 性能监视 1.4 .NET Compact Framework 3.5版简介 1.5 使用社区资源  1.5.1 Microsoft patterns&practices移动应用程序构建块   1.5.2 OpenNETCF Smart Device Framework 1.6 总结  第2章 构建Windows窗体GUI 2.1 了解2.0版本Windows窗休的改进 2.2 使用桌面应用程序丌发流程 2.3 设备屏幕与设-Part Ⅰ based mobile application development Chapter 1. NET Compact Framework mobile platform 1.1 Visual Studio Mobile Application Development Getting Started 1.1.1 Visual Studio version of the selection 1.1.2 Other software 1.1.3 goals, and a half units: Pocket PC, Smartphone or Windows CE 1.1.4 Windows CE and Windows Mobile differences 1.1.5 Select. NET Compact Framework version 1.2. NET Framework 2.0 and. NET Compact Framework 2.0 Differences 1.2.1 Application Profiles 1.2.2 ClickOnce 1.2.3 Ngen.exe 1.2.4 Remote function 1.2.5 Serialization 1.2.6 Print 1.2.7 Web Form 1.3. NET Compact Framework 1.0 and 2.0 differences 1.3.1 Windows Forms 1.3.2 Display and control the layout of the state 1.3.3 Data . 1.3.4 Communication 1.3.5 COM Interoperability 1.3.6 Graphics Programming 1.3.7 Security 1.3.8 Threads 1.3.9 Performance Monitoring 1.4. NET Compact Framework 3.5 Version Description 1.5 Use community resources 1.5.1 Microsoft patte
Platform: | Size: 5668864 | Author: 宋阳 | Hits:

[DirextXDirectx-8.1-Programming-for-CPP

Description: 应用程序向导。此工具提供了一个应用程序向导创建一个DirectX应用程序与DirectX组件的任意组合。这个工具是在安装过程中的软件开发工具包(SDK)安装,并创建一个新的应用程序时,可以在Microsoft Visual Studio® 访问。欲了解更多信息,请参阅应用程序向导。 错误查找工具。使用这个工具,采取十六进制的错误代码,并期待一个基于文本的错误信息。 SDK安装的一部分安装此工具,可以从开始,程序,微软DirectX8.1 SDK,DirectX的公用事业,DirectX错误查询访问。 DirectX图形的新功能-AppWizard. This tool provides an application wizard for creating a DirectX application with any combination of DirectX components. This tool is installed during the software development kit (SDK) install and can be accessed within Microsoft Visual Studio® when creating a new application. For more information see AppWizard. Error Lookup Tool. Use this tool to take the hexadecimal error codes and look up a text-based error message. This tool is installed as part of the SDK install and can be accessed from Start, Programs, Microsoft DirectX 8.1 SDK, DirectX Utilities, DirectX Error Lookup. New Features in DirectX Graphics
Platform: | Size: 9304064 | Author: lijing | Hits:

[Othersrc

Description: C/C++标准库源码,想研究标准库的朋友可以下来看下,如果你安装了VS的话,在F:\Microsoft Visual Studio 8\VC\crt也可以看到相应的源码。-The the C/C++ standard library source code, want to study the standard library friends down the look, if you install the VS in F: \ the Microsoft Visual Studio 8 \ VC \ crt can also see the corresponding source code.
Platform: | Size: 4521984 | Author: 李经 | Hits:

[OtherMicrosoft.Press.Programming.Windows.6th.Edition.J

Description: Programming Windows 6ed. by Charles Petzold This book—the 6th edition of Programming Windows—is a guide to writing applications that run under Microsoft Windows 8. To use this book, you’ll need a computer running Windows 8, on which you can install the Windows 8 development tools and software development kit (SDK), most conveniently in the form of the free download of Microsoft Visual Studio Express 2012 for Windows 8. That download is accessible from the Windows 8 developer portal: http://msdn.microsoft.com/windows/apps To install Visual Studio, follow the "Downloads for developers" link on that page and then the “Download the tools and SDK” link on the following page. This page also provides information on obtaining a Windows 8 developer account that lets you upload new applications to the Windows Store.
Platform: | Size: 28812288 | Author: timerune | Hits:

[ActiveX/DCOM/ATLVC2000-forARX

Description: 将.NET2002中的如下文件 mfc70.lib mfc70d.lib mfc70u.lib mfc70ud.lib mfcs70.lib mfcs70.pdb mfcs70d.lib mfcs70d.pdb mfcs70u.lib mfcs70u.pdb mfc70ud.lib mfc70ud.pdb 复制到\Program Files\Microsoft Visual Studio 8\VC\atlmfc\lib。-To the. NET2002 following documents mfc70.lib mfc70d.lib mfc70u.lib mfc70ud.lib mfcs70.lib mfcs70.pdb mfcs70d.lib mfcs70d.pdb mfcs70u.lib mfcs70u.pdb mfc70ud.lib mfc70ud.pdb copied to \ Program Files \ Microsoft Visual Studio 8 \ VC \ atlmfc \ lib.
Platform: | Size: 4019200 | Author: 李媛 | Hits:

[Multimedia Developglext

Description: OpenGL 资源头文件,glext.h。是纹理操作的必备文件。将此文件放入C:\Program Files\Microsoft Visual Studio 8\VC\include\GL即可-OpenGL resource header file, glext.h. Texture is an essential file operations. Place this file in C: \ Program Files \ Microsoft Visual Studio 8 \ VC \ include \ GL can
Platform: | Size: 30720 | Author: 李冬冬 | Hits:

[MiddleWareThe-user-subroutine-needed-files

Description: DFORMD.lib DFPORTlib KERNEL32.lib libifcoremd.lib libifportmd.lib libirc.lib libmmd.lib MSVCRT.lib WS2_32.lib将文件夹中所有的文件放到ADAMS安装目录下的win32文件夹内 ***ADAMS2007\win32 设置环境变量path=C:\SOFTWARE\Microsoft Visual Studio 8\VC\bin C:\SOFTWARE\Microsoft Visual Studio 8\Common7\IDE -DFORMD. Lib DFPORTlib KERNEL32. Lib Libifcoremd. Lib Libifportmd. Lib Libirc. Lib Libmmd. Lib MSVCRT. Lib WS2_32. Lib put all files in the folder in ADAMS in the win32 folder under the installation directory *** ADAMS2007 \ win32 Set the environment variable path = C: \ SOFTWARE \ Microsoft Visual Studio 8 VC \ \ bin C: \ SOFTWARE \ Microsoft Visual Studio 8 \ Common7 \ IDE
Platform: | Size: 259072 | Author: guoningjing | Hits:

[OtherTdbgrid8

Description: True DBGrid Pro 8.0 含注册机(True DBGrid Pro 8.0 True DBGrid Pro 7.0 is a data-aware ActiveX grid control for Microsoft Visual Studio)
Platform: | Size: 9731072 | Author: 清风不笑 | Hits:
« 12 3 »

CodeBus www.codebus.net