Win32-Web Integrator

Back








 

* FAQ *
 

 
* Why use WWI? why not use GTK?
 
* Does the client side need to install PHP manully?
 
* What kind of database can I use when using WWI?
 
* How to use ODBC settings?
 
* Can I use other version of PHP?
 
* Can I use some other PHP extensions?
 
* Is there any sample built by WWI Registered Version to download?

* Why use WWI? why not use GTK?

When you have the following needs:
    1. Want to use HTML-style interface.
    2. Just want to convert previous PHP code to Windows client-side.
    3. Need to output HTML screen (and easy for printing).
    4. Right now, designing HTML interface is easier than GTK.
    5. Want to use CGI also.
    6. Want to protect PHP code by using WWI encrypted function.
    7. Easy to use JavaApplet/Flash/MID music/...
    8. Easy to setup than using PHP+GTK.
    9. Tired to learn GTK.
    ......................
* Does the client side need to install PHP manully?

NO, WWI already includes PHP 4.x, so it will setup everything you need automatically.

* What kind of database can I use when using WWI?

WWI can setup ODBC settings automatically. So you can use Access database or EXCEL files directly. If you want to use MySQL, when distributing your program with WWI, you need to distribute and install MySQL first!

* How to use ODBC settings?

If you want to use MS-Access Files:
    Driver = "Microsoft Access Driver (*.mdb)"
    Param =

If you want to use Excel Files:
    Driver = "Microsoft Excel Driver (*.xls)"
    Param =
WWI will automatically replace the string '%DOCPATH%' with the directory name your document is located.

* Can I use other version of PHP?

Sure, just put PHP files in \php directory.
WWI will copy all the files in php directory to the released directory when generating the released package.

* Can I use some other PHP extensions?

Of course. Just put them in the php directory.

* Is there any sample built by WWI Registered Version to download?

Yes, you can download it from WWI website.


All brand names and pictures are registered trademarks of their respective owners