IEEE - Author Digital Tool Box
Here there are templates in both Word and Latex formats.
Latex:
Use \include to include a section would cause the included content to start on a new page.
To avoid starting on a new page, use \input instead of \include.
HomeTom - CS
Thursday, November 12, 2009
Thursday, October 29, 2009
Wednesday, October 28, 2009
Linux admin notes
10/28/2009
- Install software on Unix/Linux
- ./configure, make, su, make install
- Redhat: rpm. Debian: apt-get. Mandrake: urpm. Fedora: yum. Slackware: . Gentoo: Emerge.
- Install binary (.BIN, .SH):
- Install package:
- Install software on Unix/Linux
- ./configure, make, su, make install
- Redhat: rpm. Debian: apt-get. Mandrake: urpm. Fedora: yum. Slackware: . Gentoo: Emerge.
- Install binary (.BIN, .SH):
- Install package:
Thursday, September 17, 2009
Linkers and Loaders
Linkers and Loaders
By John R. Levine. 2000. ISBN 1-55860-496-0
- linkers and loaders are part of the software toolkit for almost as long as there have been computers.
- This book is for: students, programmers, computer language designers and developers.
- All the linker writers in the world could probably fit in one room, and half of them would already have this book because they reviewed the manuscript.
Chapter 1. Linking and Loading
1.1 What do linkers and loaders do?
- Basic job of linker/loader: binds more abstract names to more concrete names. (name management, address binding)
1.2 Address binding: A historical perspective
- Linker and Loader divides the job: Linker do part of address binding, assign relative addresses. Loader do final step of assigning actual addresses.
1.3 Linking and Loading
- linker does 1) symbol resolution, loader does 2) program loading. Either can do 3) relocation.
- There are linking loaders that do all 3 functions
- Both patch object code
- Two-pass linking: linking is fundamentally a 2-pass process: step 1) collecting info, 2) linking
object files + shared lib + normal lib + linker control files + cmd line args --> (linker) -->
Debug symbol file + Executable file + link/load map
- Object code libraries
- Relocation and code modification
1.4 Compiler drivers
- assembly code --> object code --> link object code and library together
- Linker command languages. Ways of passing commands to a linker:
1) command line, 2) intermixed with obj files, 3) embedded in obj files, 4) separate config language.
1.5 Linking: A true-life example
By John R. Levine. 2000. ISBN 1-55860-496-0
- linkers and loaders are part of the software toolkit for almost as long as there have been computers.
- This book is for: students, programmers, computer language designers and developers.
- All the linker writers in the world could probably fit in one room, and half of them would already have this book because they reviewed the manuscript.
Chapter 1. Linking and Loading
1.1 What do linkers and loaders do?
- Basic job of linker/loader: binds more abstract names to more concrete names. (name management, address binding)
1.2 Address binding: A historical perspective
- Linker and Loader divides the job: Linker do part of address binding, assign relative addresses. Loader do final step of assigning actual addresses.
1.3 Linking and Loading
- linker does 1) symbol resolution, loader does 2) program loading. Either can do 3) relocation.
- There are linking loaders that do all 3 functions
- Both patch object code
- Two-pass linking: linking is fundamentally a 2-pass process: step 1) collecting info, 2) linking
object files + shared lib + normal lib + linker control files + cmd line args --> (linker) -->
Debug symbol file + Executable file + link/load map
- Object code libraries
- Relocation and code modification
1.4 Compiler drivers
- assembly code --> object code --> link object code and library together
- Linker command languages. Ways of passing commands to a linker:
1) command line, 2) intermixed with obj files, 3) embedded in obj files, 4) separate config language.
1.5 Linking: A true-life example
Scalable System Design
- one header file for each role v.s. one header file (with lots of if/else) for all roles
- assign ID to each page, assign ID list to each role
- DB access, business logic, HTML, CSS
- uniqueness
- reusability
- accumulation of code/solution
- Client requirements analysis
- technical requirements analysis
- risk points, risk control
- configuration, separate control points from code
- data dictionary, allow user to adjust this themselves
- guide/educate clients
- source control
- no new assignment before end of current assignment period even if current assignment is done before schedule
- grow together
- mutual tech evaluation/no boss participation
Saturday, September 12, 2009
Friday, August 21, 2009
Manipulate PDF in .NET
To convert PDF into image, we have the GFL SDK/GFLAx library as discussed in an earlier post.
Now the problem is how to convert image into PDF, or how to draw onto PDF. One needs to rely on 3rd party module for this function.
PDFSharp (http://www.pdfsharp.net/) works well for this. It can create new PDF file, or draw text and image onto existing PDF files. It even can generate barcode image (but guess it can't do recognization). The current version is 1.3, providing both source and assembly download at sourceforge.net. The source code can be used in one's own application, unless is for commercial purpose and needs support. It is written from scratch in C#. The only limit is that it requires .NET version 2.0 or above. To use this in .NET 1.1 or from other framework such as J2EE/LAMP, I think one can do something like a web service call.
Some people say in web applications PDFSharp cannot run under medium security level. I didn't have this problem, probably because I'm running it on a trusted server, so there is no security restriction.
One last word: it seems that PDF is frequently used in business applications. Now we have these open source projects that allows PDF convertion to and from other formats. Good to have these.
Now the problem is how to convert image into PDF, or how to draw onto PDF. One needs to rely on 3rd party module for this function.
PDFSharp (http://www.pdfsharp.net/) works well for this. It can create new PDF file, or draw text and image onto existing PDF files. It even can generate barcode image (but guess it can't do recognization). The current version is 1.3, providing both source and assembly download at sourceforge.net. The source code can be used in one's own application, unless is for commercial purpose and needs support. It is written from scratch in C#. The only limit is that it requires .NET version 2.0 or above. To use this in .NET 1.1 or from other framework such as J2EE/LAMP, I think one can do something like a web service call.
Some people say in web applications PDFSharp cannot run under medium security level. I didn't have this problem, probably because I'm running it on a trusted server, so there is no security restriction.
One last word: it seems that PDF is frequently used in business applications. Now we have these open source projects that allows PDF convertion to and from other formats. Good to have these.
Subscribe to:
Posts (Atom)