In this tutorial you will learn how to use XSLT to transform XML documents into other formats, like HTML.
what is XML?
XML stands for eXtensible Markup Language.
XML is designed to transport and store data.
XML is important to know, and very easy to learn.
refer:http://www.w3schools.com/xml/default.asp
what is XSLT?
XSL stands for EXtensible Stylesheet Language, and is a style sheet language for XML documents.
XSLT stands for XSL Transformations.
refer:http://www.w3schools.com/xsl/
Where to Start?
http://www.php.net/manual/en/xsl.examples.php
System Requirements?
Programming tools: PHP, XSL,XML, DOM
Server Requirements: PHP-XML, PHP-XSL ( check for module installation on your host, using simple php code: < ?php phpinfo(); ? > )
Cross platform : Yes (Safari, Firefox, Opera )
note: no space between < or > and ? in above example
Saturday, December 19, 2009
Monday, October 26, 2009
Installing multiple versions of Python from Source
The first step is to ensure that all dependencies are installed. Run the following once:
sudo apt-get build-dep python2.5
That will install a bunch of dev packages. Which packages get installed will likely depend of each specific system.
As the remaining commands will need to be repeated for each version of python, I will list them once with X's in place of the version numbers. Be sure to replace the X's with the appropriate version numbers. The various versions and download links can be found on the Python download page.
wget http://python.org/ftp/python/X.X.X/Python-X.X.X.tgz
tar xvfz Python-X.X.X.tgz
cd Python-X.X.X
./configure --prefix=/opt/pythonX.X
make
sudo make install
In a couple versions I got some warnings after running make about missing dependencies for things I don't need or use, so I ignored them and everything worked fine. Of course, these need to be on my path to be useful so I created some links:
sudo ln -s /opt/pythonX.X/bin/pythonX.X /usr/bin/python-X.X
While I only needed to do the above once, I needed to install it in each version:
sudo python2.X setup.py install
sudo apt-get build-dep python2.5
That will install a bunch of dev packages. Which packages get installed will likely depend of each specific system.
As the remaining commands will need to be repeated for each version of python, I will list them once with X's in place of the version numbers. Be sure to replace the X's with the appropriate version numbers. The various versions and download links can be found on the Python download page.
wget http://python.org/ftp/python/X.X.X/Python-X.X.X.tgz
tar xvfz Python-X.X.X.tgz
cd Python-X.X.X
./configure --prefix=/opt/pythonX.X
make
sudo make install
In a couple versions I got some warnings after running make about missing dependencies for things I don't need or use, so I ignored them and everything worked fine. Of course, these need to be on my path to be useful so I created some links:
sudo ln -s /opt/pythonX.X/bin/pythonX.X /usr/bin/python-X.X
While I only needed to do the above once, I needed to install it in each version:
sudo python2.X setup.py install
Wednesday, September 9, 2009
RPM File Naming Convention
RPM File Naming Convention
While RPM will run just as well if a package file has been renamed, when the packages are created during RPM's build process, they follow a specific naming convention. The convention is:
name-version-release.architecture.rpm
where:
*name is a name describing the packaged software.
*version is the version of the packaged software.
*release is the number of times this version of the software has been packaged.
*architecture is a shorthand name describing the type of computer hardware the packaged software is meant to run on. It may also be the string src, or nosrc. Both of these strings indicate the file is an RPM source package. The nosrc string means that the file contains only package building files, while the src string means the file contains the necessary package building files and the software's source code.
A few notes are in order. Normally, the package name is taken verbatim from the packaged software's name. Occasionally, this approach won't work — usually this occurs when the software is split into multiple "subpackages," each supporting a different set of functions. An example of this situation would be the way ncurses was packaged on Red Hat Linux Linux. The package incorporating ncurses basic functionality was called ncurses, while the package incorporating those parts of ncurses' program development functionality was named ncurses-devel.
The version number is normally taken verbatim from the package's version. The only restriction placed on the version is that it cannot contain a dash "-".
The release can be thought of as the package's version. Traditionally it is a number, starting at 1, that shows how many times the packaged software, at a given version, has been built. This is tradition and not a restriction, however. Like the version number, the only restriction is that dashes are not allowed.
The architecture specifier is a string that indicates what hardware the package has been built for. There are a number of architectures defined:
*i386 — The Intel x86 family of microprocessors, starting with the 80386.
*alpha — The Digital Alpha/AXP series of microprocessors.
*sparc — Sun Microsystem's SPARC series of chips.
*mips — MIPS Technologies' processors.
*ppc — The Power PC microprocessor family.
*m68k — Motorola's 68000 series of CISC microprocessors.
*SGI — Equivalent to "MIPS".
This list will almost certainly change. For the most up-to-date list, please refer to the file /usr/lib/rpmrc. It contains information used internally by RPM, including a list of architectures and equivalent code numbers.
While RPM will run just as well if a package file has been renamed, when the packages are created during RPM's build process, they follow a specific naming convention. The convention is:
name-version-release.architecture.rpm
where:
*name is a name describing the packaged software.
*version is the version of the packaged software.
*release is the number of times this version of the software has been packaged.
*architecture is a shorthand name describing the type of computer hardware the packaged software is meant to run on. It may also be the string src, or nosrc. Both of these strings indicate the file is an RPM source package. The nosrc string means that the file contains only package building files, while the src string means the file contains the necessary package building files and the software's source code.
A few notes are in order. Normally, the package name is taken verbatim from the packaged software's name. Occasionally, this approach won't work — usually this occurs when the software is split into multiple "subpackages," each supporting a different set of functions. An example of this situation would be the way ncurses was packaged on Red Hat Linux Linux. The package incorporating ncurses basic functionality was called ncurses, while the package incorporating those parts of ncurses' program development functionality was named ncurses-devel.
The version number is normally taken verbatim from the package's version. The only restriction placed on the version is that it cannot contain a dash "-".
The release can be thought of as the package's version. Traditionally it is a number, starting at 1, that shows how many times the packaged software, at a given version, has been built. This is tradition and not a restriction, however. Like the version number, the only restriction is that dashes are not allowed.
The architecture specifier is a string that indicates what hardware the package has been built for. There are a number of architectures defined:
*i386 — The Intel x86 family of microprocessors, starting with the 80386.
*alpha — The Digital Alpha/AXP series of microprocessors.
*sparc — Sun Microsystem's SPARC series of chips.
*mips — MIPS Technologies' processors.
*ppc — The Power PC microprocessor family.
*m68k — Motorola's 68000 series of CISC microprocessors.
*SGI — Equivalent to "MIPS".
This list will almost certainly change. For the most up-to-date list, please refer to the file /usr/lib/rpmrc. It contains information used internally by RPM, including a list of architectures and equivalent code numbers.
Wednesday, September 2, 2009
Python egg is:
If you don’t know what a Python egg is, it’s simply a way of distributing Python packages, similar to RPM. There is also an easy method of installing them, using easy_install.
Where do I find Python Eggs?
You can find Python Eggs on quite a few places on the web, e.g. at a package author’s website. The biggest repository of eggs is the Cheeseshop (or PyPI) though), an index for Python packages. In order to be able to install eggs you simply need to install easy_install which is easily done by downloading ez_install.py (you can download it here) and calling it (you need to have rights to install components in your python installation of course).
Once you have done this you can simply install an egg by calling:
easy_install somepackage.egg
You can also give a URL to an egg and use
easy_install http://somehost.somedomain.com/somepackage.egg
If an egg is not found at that location or in the directory you give, easy_install will automatically query the Cheeseshop for the egg location. So if you want to install SimpleJSON you simply give
easy_install simplejson
and it will download and install the most recent version. If you are not running as root and you have Python installed as root you of course need to use something like “sudo easy_install” instead (e.g. on MacOSX).
A great additional feature is also that Eggs can define dependancies on other packages which easy_install will then try to automatically download and install aswell.
BTW, the easy_install program is part of the setuptool package by Philip Eby and is based on the distutils package which is part of the standard python distribution.
refer more : click here
http://onlamp.com/pub/a/python/2005/01/27/ipython.html
============================================
try this to install ipython for python2.4
=============================================
[root@root]# wget http://pypi.python.org/packages/2.4/s/setuptools/setuptools-0.6c9-py2.4.egg
[root@root]# sh setuptools-0.6c9-py2.4.egg
[root@root]# easy_install-2.4 http://ipython.scipy.org/dist/ipython-0.8.4-py2.4.egg
[root@webdev tgzfiles]#
Where do I find Python Eggs?
You can find Python Eggs on quite a few places on the web, e.g. at a package author’s website. The biggest repository of eggs is the Cheeseshop (or PyPI) though), an index for Python packages. In order to be able to install eggs you simply need to install easy_install which is easily done by downloading ez_install.py (you can download it here) and calling it (you need to have rights to install components in your python installation of course).
Once you have done this you can simply install an egg by calling:
easy_install somepackage.egg
You can also give a URL to an egg and use
easy_install http://somehost.somedomain.com/somepackage.egg
If an egg is not found at that location or in the directory you give, easy_install will automatically query the Cheeseshop for the egg location. So if you want to install SimpleJSON you simply give
easy_install simplejson
and it will download and install the most recent version. If you are not running as root and you have Python installed as root you of course need to use something like “sudo easy_install” instead (e.g. on MacOSX).
A great additional feature is also that Eggs can define dependancies on other packages which easy_install will then try to automatically download and install aswell.
BTW, the easy_install program is part of the setuptool package by Philip Eby and is based on the distutils package which is part of the standard python distribution.
refer more : click here
http://onlamp.com/pub/a/python/2005/01/27/ipython.html
============================================
try this to install ipython for python2.4
=============================================
[root@root]# wget http://pypi.python.org/packages/2.4/s/setuptools/setuptools-0.6c9-py2.4.egg
[root@root]# sh setuptools-0.6c9-py2.4.egg
[root@root]# easy_install-2.4 http://ipython.scipy.org/dist/ipython-0.8.4-py2.4.egg
[root@webdev tgzfiles]#
Tuesday, September 1, 2009
cherrypy
CherryPy is a pythonic, object-oriented HTTP framework.
CherryPy allows developers to build web applications in much the same way they would build any other object-oriented Python program. This results in smaller source code developed in less time.
CherryPy is now more than six years old and it is has proven very fast and stable. It is being used in production by many sites, from the simplest ones to the most demanding ones.
Oh, and most importantly: CherryPy is fun to work with :-) Here's how easy it is to write "Hello World" in CherryPy 3:
import cherrypy
class HelloWorld(object):
def index(self):
return "Hello World!"
index.exposed = True
cherrypy.quickstart(HelloWorld())
Find More on http://www.cherrypy.org/
CherryPy allows developers to build web applications in much the same way they would build any other object-oriented Python program. This results in smaller source code developed in less time.
CherryPy is now more than six years old and it is has proven very fast and stable. It is being used in production by many sites, from the simplest ones to the most demanding ones.
Oh, and most importantly: CherryPy is fun to work with :-) Here's how easy it is to write "Hello World" in CherryPy 3:
import cherrypy
class HelloWorld(object):
def index(self):
return "Hello World!"
index.exposed = True
cherrypy.quickstart(HelloWorld())
Find More on http://www.cherrypy.org/
Wednesday, July 15, 2009
journals, book series, books, reference works and the Online Archives Collection
Interactive databases for high-quality STM journals, book series, books, reference works and the Online Archives Collection. SpringerLink is a powerful central access point for researchers and scientists.
For more click http://www.springerlink.com
For more click http://www.springerlink.com
Tuesday, May 12, 2009
TestDisk : free data recovery utility
TestDisk is a free data recovery utility. It was primarily designed to help recover lost data storage partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses or human error (such as accidentally erasing a partition table).
Latest release 6.11 / 2009-04-19; 22 days ago
Platform Multiplatform
Type Data recovery
License GNU General Public License
Website www.cgsecurity.org/wiki/TestDisk
Latest release 6.11 / 2009-04-19; 22 days ago
Platform Multiplatform
Type Data recovery
License GNU General Public License
Website www.cgsecurity.org/wiki/TestDisk
Monday, May 11, 2009
PhotoRec: data recovery software tool
PhotoRec is a data recovery software tool designed to recover lost files from digital camera memory (CompactFlash, Memory Stick, Secure Digital, SmartMedia, Microdrive, MMC, USB flash drives etc.), hard disks and CD-ROMs. It recovers most common photo formats, including JPEG, and also recovers audio files including MP3, document formats such as Microsoft Office, PDF and HTML, and archive formats including ZIP.
PhotoRec does not attempt to write to the damaged media you are about to recover from. Recovered files are instead written to the directory from where you are running PhotoRec or any other directory you choose. PhotoRec is shipped with TestDisk.
Latest release 6.11 / 2009-04-19; 22 days ago
Operating system Cross-platform
License GNU General Public License
Website http://www.cgsecurity.org/wiki/PhotoRec
PhotoRec does not attempt to write to the damaged media you are about to recover from. Recovered files are instead written to the directory from where you are running PhotoRec or any other directory you choose. PhotoRec is shipped with TestDisk.
Latest release 6.11 / 2009-04-19; 22 days ago
Operating system Cross-platform
License GNU General Public License
Website http://www.cgsecurity.org/wiki/PhotoRec
Monday, February 9, 2009
NetBeans - Development Simplified
A free, open-source Integrated Development Environment for software developers. You get all the tools you need to create professional desktop, enterprise, web, and mobile applications with the Java language, C/C++, and even dynamic languages such as PHP, JavaScript, Groovy, and Ruby. NetBeans IDE is easy to install and use straight out of the box and runs on many platforms including Windows, Linux, Mac OS X and Solaris.
The NetBeans IDE 6.5 provides several new features and enhancements, such as rich PHP, JavaScript and Ajax editing features, improved support for using the Hibernate web framework and the Java Persistence API, and tighter GlassFish v3 and MySQL integration.
NetBeans IDE Installation Guide
Learn More about NetBeans IDE
The NetBeans IDE 6.5 provides several new features and enhancements, such as rich PHP, JavaScript and Ajax editing features, improved support for using the Hibernate web framework and the Java Persistence API, and tighter GlassFish v3 and MySQL integration.
NetBeans IDE Installation Guide
Learn More about NetBeans IDE
Wednesday, February 4, 2009
Meetings Events Conferences TOOL
The Indico tool allows you to manage complex conferences, workshops, and time-tables of meetings, to attach multimedia files to each event item and to store the resulting agendas in a multi-level hierarchical tree. Install the Indico software locally under GNU General Public License (see the project web site).
Subscribe to:
Posts (Atom)