Andrei Zmievski wrote:
I don't think that PHP 4.3.0 and PEAR have such a big interdependency.
4.3.0 can go out without having all the minute details of PEAR
management decided.
+1, only the installer stuff + package browser should really be stable
and usable with php4.3
--
PHP
Lukas Smith wrote:
The point is that PEAR needs to be ready on all levels (technical and
community) before it should go public. If PEAR will go public with php
4.3 then it needs to be complete in that respect. The damage to PEAR if
this is not the case will be great and will take a long time
You need to make sure
COMPILE_DL_(EXTENSION)
is defined...
Was the error. Can somebody write an howto for win? I work since 10am to get
this stuff working.
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Create an OO-based wrapper for the MySQL extension. The wrapper would
provide the user with access to all of a database's information without
Yeah, lets re-invent PEAR:DB :)
Such things are already on the ToDo list for PEAR::DB.
--
PHP Development Mailing List http://www.php.net/
To
1.) C: ext/phpdoc = simple XML (doc comments unparsed)
2.) PHP: standard_doctool = generates standard_intermediate XML
What would be the different between this two types of XML? And how compatible
will the xml-output to the existing xml-output?
--
PHP Development Mailing List
When running pear/PHPDoc php.exe (built from current CVS) crashes on
Win32.
set mem_limit to high value ( 32MB), running PHPDoc over PEAR is a hardcore
test...
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Is it documented somewhere?
The DTD is in php4/pear/package.dtd
Also, I fear that XML would be too slow for time-critical operation like
including files on runtime, but I might be mistaken.
Could be possible.
Solutions:
1.) creating a c-function, which parses the xml-file
2.) the
AM 2.) the PEAR-Installer create a package file of the 'your'
AM format from the XML package file
maybe would be better. Let's see what other people think.
I forgot a possiblity, one task of the installer should be to store data of the
installed pear-packages in flat-file database. This is'nt
package_load(Name)
package_is_loaded(Name)
package_set_path(path)
+1
3. The package definition file has format like the following:
PEAR has already a XML-based package file format, which is already used
for installation and information retrieving.
--
PHP Development Mailing List
I'm completely open to better solutions, but haven't actually be able to
find any. We _could_ start browser sniffing I guess.
My experience is that you have to make fonts slightly bigger for
Netscape 4.x on X11 and Opera.
It would not be simpler to avoid the use of font-size?
--
PHP
I think it looks really good and we should probably make it the default
for http://cvs.php.net. Anybody see any reason not to do that?
+1
Please, could you use relative specifications (font-size: small) instead of
absolute (font-size: 11px) in the css? It's more user-friendly and i don't
have
11 matches
Mail list logo
