Hi.
With the Livedocs system about to become live, does this impact on how
the xCHM manual is to be built? I've not followed Livedocs, but the name
suggests that commits are live in the docs (obvious really).
So, this suggests that Livedocs is another tool to access the CVS which
means that
With the Livedocs system about to become live, does this impact on how
the xCHM manual is to be built? I've not followed Livedocs, but the name
suggests that commits are live in the docs (obvious really).
So, this suggests that Livedocs is another tool to access the CVS which
means that there
Hello everyone!
I've created a draft Livedocs proposal for the SoC, it can be seen here:
http://wiki.phpdoc.info/LiveDocs/SocProposal
Please feel free to make suggestions and provide feedback, I plan to
submit it within a couple days. Thanks!
Regards,
Philip
Well I think it is pretty good, as long as you implement all the primary and
longer term ideas ;) Really, I like your ideas.
So far we haven't had any application to Livedocs, so I think yours is
likely to be accepted.
Nuno
Hello everyone!
I've created a draft Livedocs proposal for the
I also read through the application, and it seems to be decent. Although
documentation writing is not something supported by the SoC program,
hopefully documentation tools are something to stand behind.
Goba
Nuno Lopes wrote:
Well I think it is pretty good, as long as you implement all the
Hi,
I didn't followed all the mail you said about livedocs but since all the
updates, I have some problems... I was building everything but the
constant ROOT_NODE was not found, so I reconfigure again. If I set
caching enable, I receive ROOT_NODE undefined for manual.html.
For all other
Sean Coates wrote:
http://www.phpdoc.info/livedocs/built/
It's built nightly. I know today's (20050621) works well.
Recent builds have 46 bytes - brilliant shrink but I'm afraid
something is missing inside ;-).
Not sure what that's all about, but I'll look into it once I'm out from
under
http://www.phpdoc.info/livedocs/built/
It's built nightly. I know today's (20050621) works well.
Recent builds have 46 bytes - brilliant shrink but I'm afraid
something is missing inside ;-).
Not sure what that's all about, but I'll look into it once I'm out from
under my pile of email. (I
Sean Coates wrote:
http://www.phpdoc.info/livedocs/built/
It's built nightly. I know today's (20050621) works well.
Recent builds have 46 bytes - brilliant shrink but I'm afraid
something is missing inside ;-).
Jakub Vrana
In response to the conversation we had last week (you remember: the one
where Goba shot down my XUL docs idea, and I conceded? (-; ), I've been
working on packaging a pre-built Livedocs distribution. Ilia's recent
changes have also been a catalyst for me to actually do something about
this.
On little note, for all who will be testing livedocs in the next while.
At this time development is done ONLY using the English translation.
Until we confirm that it works as intended I will ignore bugs with other
localizations. Once English works, then we can try to identify and
resolve
- Distribute as a PEAR package (PEAR's new channels seem like the
perfect candidate, as does the upcoming PHP_Archive package).
I didn't thought in PEAR initially, but seems to be a good idea, althought
I've never used it :) (but this remainds me to work on the generalization
of the code)
Nuno Lopes wrote:
I didn't thought in PEAR initially, but seems to be a good idea,
althought I've never used it :) (but this remainds me to work on the
generalization of the code)
To be clear: I don't want to put it IN PEAR. I want to distribute it via
an independent PEAR channel, as ONE
Branching livedocs would only complicate things, if there are patches
open bug reports and I'll review them or if these are features simple
e-mail them to me (or Wez or Derick).
Ilia
Hello fellow phpdocers.
In response to the conversation we had last week (you remember: the one
where Goba shot down my XUL docs idea, and I conceded? (-; ), I've been
working on packaging a pre-built Livedocs distribution. Ilia's recent
changes have also been a catalyst for me to actually do
Sean Coates wrote:
Tarred and bzipped, we're to be slightly under 7 megs. Not too bad.
It's now 4.5 MB (I forgot, and included notes -- this shouldn't be).
(fixed, BTW)
S
Sean Coates wrote:
Feedback, please.
Works for me without any problems (Win XP, Apache 2, PHP 5). Maybe it
will be worthwhile to create a version without phpdoc/en/ as everyone
already has a CVS version.
I also wonder where en/*.ent and entities/*.ent are hidden.
Jakub Vrána
Jakub Vrana wrote:
Works for me without any problems (Win XP, Apache 2, PHP 5). Maybe it
will be worthwhile to create a version without phpdoc/en/ as everyone
already has a CVS version.
Thanks -- glad it works on Windows (-:
WE have a CVS version, yes.
This is targetted at a wider audience,
I think it could be cool to remove the errors in the search.php and a
way to select easily iso-8859-1 like illa said me in
http://bugs.php.net/30440 for a public release.
OoOoO, it seems that search.php is now corrected :) just suggesting the
new feature for encoding now :)
Long time ago, I
||*()*|| Hi, Sean.
I don't know of a showstopper. It will probably only turn out, if we
push it out to a lot of testers. It might be a good idea to package up a
manual with some pregenerated sqlite db, and offer it as some BETA (how
popular this designation is nowadays :). Since the code gets
Is there any reason why the docbook sources aren't distributed ?
Seems that would remove some dependancies, and allow other
viewers to pull the book(s) direct.
They are...
http://cvs.php.net/phpdoc/
Post ./configure'd, and ready to use.
Don't know if you remember I was the bod that
-Original Message-
From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]
Sent: 14 June 2005 09:20
To: [EMAIL PROTECTED]
Cc: 'Sean Coates'; phpdoc@lists.php.net
Subject: Re: [PHP-DOC] Livedocs Deployment to End Users (WAS:
some gobblygookabout theCHM)
Is there any reason why
I think livedocs is trying to solve a different problem, I think. (Reducing
time between edit/view?)
Livedocs is trying to a solve the problem of displaying a docbook
document on the fly (with as small amount of preprocessing as possible).
I just want something I can dump several documents
Gabor Hojtsy wrote:
Who has no webserver on his machine nowadays? Especially if he is
interested in PHP? Livedocs offers a lot more possibilities also in an
offline (ie without internet connection, with local webserver) setting,
if used appropriately.
You know.. I've been thinking about this.
Who has no webserver on his machine nowadays? Especially if he is
interested in PHP? Livedocs offers a lot more possibilities also in an
offline (ie without internet connection, with local webserver) setting,
if used appropriately.
You know.. I've been thinking about this.
In order for
1. We can easily ship an sqlite db for the complete manual, as we are
going to do with all the mirror sites, when livedocs will be ready to
handle serving the manual.
Good point (-:
2. We can provide a web service for users to pick their customized
manual, and get a customized sqlite db plus
1. We can easily ship an sqlite db for the complete manual, as we are
going to do with all the mirror sites, when livedocs will be ready to
handle serving the manual.
Good point (-:
2. We can provide a web service for users to pick their customized
manual, and get a customized sqlite db
Well, sad thing is that we have some good perspectives with livedocs,
but not much work is done on this front. We might have had some good
chance to grab some coding hands with Google SOC, but we are quite late
in the game :) Any ideas to help recruit more developers?
I often think about
Well, sad thing is that we have some good perspectives with livedocs,
but not much work is done on this front. We might have had some good
chance to grab some coding hands with Google SOC, but we are quite late
in the game :) Any ideas to help recruit more developers?
I often think about
Gabor Hojtsy wrote:
Well, sad thing is that we have some good perspectives with livedocs,
but not much work is done on this front. We might have had some good
chance to grab some coding hands with Google SOC, but we are quite late
in the game :) Any ideas to help recruit more developers?
I
1. We can easily ship an sqlite db for the complete manual, as we are
going to do with all the mirror sites, when livedocs will be ready to
handle serving the manual.
Good point (-:
2. We can provide a web service for users to pick their customized
manual, and get a customized sqlite db plus
Nuno Lopes wrote:
What a nice idea :) Maybe I could apply at Google summer of code and get
livedocs forward :)
Well, we missed the window, but Chuck from the Horde project (which is
on the list) has graciously suggested that if someone wants to piggyback
on his project for PEAR development,
What a nice idea :) Maybe I could apply at Google summer of code and
get livedocs forward :)
Well, we missed the window, but Chuck from the Horde project (which is
on the list) has graciously suggested that if someone wants to piggyback
on his project for PEAR development, he will consider
-Original Message-
From: Sean Coates [mailto:[EMAIL PROTECTED]
Sent: 13 June 2005 17:16
To: Gabor Hojtsy
Cc: phpdoc@lists.php.net
Subject: [PHP-DOC] Livedocs Deployment to End Users (WAS:
some gobblygook about theCHM)
Gabor Hojtsy wrote:
Who has no webserver on his machine
Is there any reason why the docbook sources aren't distributed ?
Seems that would remove some dependancies, and allow other viewers to pull the
book(s) direct.
They are...
http://cvs.php.net/phpdoc/
S
Is there any reason why the docbook sources aren't distributed ?
Seems that would remove some dependancies, and allow other
viewers to pull the book(s) direct.
They are...
http://cvs.php.net/phpdoc/
S
Post ./configure'd, and ready to use.
Don't know if you remember I was the
Jared Williams wrote:
Post ./configure'd, and ready to use.
Don't know if you remember I was the bod that appeared in #phpdoc with the
beginnings of a general docbook/xml viewer.
I guess I could do that.. it's like 10 mins of scripting..
I'll put it on phpdoc.info.. and let you know when
Jared Williams wrote:
Post ./configure'd, and ready to use.
Don't know if you remember I was the bod that appeared in
#phpdoc with the beginnings of a general docbook/xml viewer.
I guess I could do that.. it's like 10 mins of scripting..
I'll put it on phpdoc.info.. and let you
Jared Williams wrote:
Jared Williams wrote:
Post ./configure'd, and ready to use.
I guess I could do that.. it's like 10 mins of scripting..
I'll put it on phpdoc.info.. and let you know when it's running.
Here: http://www.phpdoc.info/docs_prepared/
It should run every morning at 4:15AM
Hi Sean,
Livedocs isn't woking with peardoc, but I can't remember why (the last/only?
guy who worked on this was Medhi).
Some tweaking of the mk_peardoc.php file should do the trick.
Nuno
P.S.: anyway, I wouldn't spend much time on this, as I think the indexing
process of livedocs should be
Anyone know the current status of livedocs and PEARDoc?
I'd like to know what is/isn't working so I can attempt to get the
latter fixed.
I've built --with-build-type=peardoc, and got a really messed up
livedocs.. I'm wondering if others suffer the same problem, or if I'm
doing something wrong
There's an increasing number of patches waiting to be applied to livedocs -
is someone able to look after them? Pretty please!
Also, after trying to hack a couple of things in, I noticed include used
instead of require where it really should not. (Just noting this to whoever
happens to have
On Mon, 4 Oct 2004, Aidan Lister wrote:
There's an increasing number of patches waiting to be applied to livedocs -
is someone able to look after them? Pretty please!
File bugreports.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
Hi,
Where can i find a specification design for the livedocs system?
Just curious what it will be like. Until now it sounds sexy. Keep up the
good work!
Cheers Sander
Where can i find a specification design for the livedocs system?
Just curious what it will be like. Until now it sounds sexy. Keep up the
good work!
A lot of Livedocs related information (such as where to find
the source, examples, where to submit patches...) can be
found here:
This style is also simpler in my eyes. Tested with IE 6 and Opera 7.23.
I hope it works in other browsers too but I didn't test it.
I have applied your patch. It will turn out if it breaks something else
(like Mozilla browsers :).
Goba
It is still broken for me: IE 6 SP2.
Opera and Firefox work
Hi,
The tableless layout for the manual is here:
http://www.php.net/manual/en/tableless/index.php
It displays quite fine in Mozilla Firefox, but is problematic in IE,
since it does not interpret the float model correctly. I would be happy
to see patches for this though :)) I definitely expect
moshe doron i'rta:
Just to remember, we still didn't changed the output encoding of livedocs to
uft-8.
Here the patch: http://phpil.net/patchs/livedocs-utf8.patch.txt
Please cc: Ilia if posting livedocs patches. He is not on phpdoc.
Goba
Just to remember, we still didn't changed the output encoding of livedocs to
uft-8.
Here the patch: http://phpil.net/patchs/livedocs-utf8.patch.txt
--
Moshe.
Also, as an aside:
The :: chapter, should be renamed to scope resolution operator?
Maybe.
I think it should have :: somewhere in the title, how about:
Scope Resolution Operator (::)
Fine with me.
And, should this operator be listed somewhere here?
Gabor Hojtsy wrote:
The tableless layout for the manual is here:
http://www.php.net/manual/en/tableless/index.php
It displays quite fine in Mozilla Firefox, but is problematic in IE,
since it does not interpret the float model correctly. I would be happy
to see patches for this though :))
On Monday 23 August 2004 15:54, Derick Rethans wrote:
On Mon, 23 Aug 2004, Friedhelm Betz wrote:
On Monday 23 August 2004 11:03, Derick Rethans wrote:
[...]
I think we should start making the manual always output UTF8. Can
people think of reasons why NOT to do this?
Not really,
On Tue, 24 Aug 2004, Friedhelm Betz wrote:
On Monday 23 August 2004 15:54, Derick Rethans wrote:
On Mon, 23 Aug 2004, Friedhelm Betz wrote:
On Monday 23 August 2004 11:03, Derick Rethans wrote:
[...]
I think we should start making the manual always output UTF8. Can
people
On Sun, 22 Aug 2004, Gabor Hojtsy wrote:
livedocs is now running on docs.php.net (do not announce it yet!) but
not automatically updating so far.
Please fix the following errors:
[Sat Aug 21 16:49:25 2004] [error] [client 80.197.147.147] File does not exist:
according to the the last changes on ext/xml, here
(http://phpil.net/livedocs.patch.txt) patch that:
1. make the livedocs compatible with php 5.0.1
2. make livedocs on php4 the same as livedocs on php5.
Moshe.
Gabor Hojtsy [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
livedocs is
On Mon, 23 Aug 2004, moshe doron wrote:
according to the the last changes on ext/xml, here
(http://phpil.net/livedocs.patch.txt) patch that:
1. make the livedocs compatible with php 5.0.1
2. make livedocs on php4 the same as livedocs on php5.
I don't see why adding iconv calls helps with
Derick Rethans [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On Mon, 23 Aug 2004, moshe doron wrote:
according to the the last changes on ext/xml, here
(http://phpil.net/livedocs.patch.txt) patch that:
1. make the livedocs compatible with php 5.0.1
2. make livedocs on php4
On Mon, 23 Aug 2004, moshe doron wrote:
I don't see why adding iconv calls helps with this, can you also nicely
indent your changes in common.php?
The iconv make the output 8bit (according to the assumption that bandwide is
more important then generation speed of cached content). I didn't
On Monday 23 August 2004 11:03, Derick Rethans wrote:
[...]
I think we should start making the manual always output UTF8. Can people
think of reasons why NOT to do this?
Not really, but only the issue to ensure that the source .xml files are always
saved/edited as utf-8. This should not be
On Mon, 23 Aug 2004, Friedhelm Betz wrote:
On Monday 23 August 2004 11:03, Derick Rethans wrote:
[...]
I think we should start making the manual always output UTF8. Can people
think of reasons why NOT to do this?
Not really, but only the issue to ensure that the source .xml files are
With livedocs, If I update a page, is livedocs meant to regenerate that page
on the next request?
At the moment, on my build, it is not doing this. I have to delete the
cached pages first.
Is there a reason for this?
Also, as an aside:
The :: chapter, should be renamed to scope resolution
livedocs is now running on docs.php.net (do not announce it yet!) but
not automatically updating so far.
Please fix the following errors:
[Sat Aug 21 16:49:25 2004] [error] [client 80.197.147.147] File does
not exist: /local/Web/sites/livedocs/www/style.css
I've got a bunch of fixes for the
Why? It needs to be migrated to the tableless php.net layout IMHO
anyway, in which it is not possible to size the page with 100% height.
body { height: 100%; } ?
Heya,
livedocs is now running on docs.php.net (do not announce it yet!) but
not automatically updating so far.
Please fix the following errors:
[Sat Aug 21 16:49:25 2004] [error] [client 80.197.147.147] File does not exist:
/local/Web/sites/livedocs/www/style.css
[Sat Aug 21 16:49:35 2004]
Curt Zirzow wrote:
* Thus wrote Derick Rethans:
Heya,
livedocs is now running on docs.php.net (do not announce it yet!) but
not automatically updating so far.
Please fix the following errors:
[Sat Aug 21 16:49:25 2004] [error] [client 80.197.147.147] File does not exist:
Curt Zirzow wrote:
* Thus wrote Derick Rethans:
Heya,
livedocs is now running on docs.php.net (do not announce it yet!) but
not automatically updating so far.
Please fix the following errors:
[Sat Aug 21 16:49:25 2004] [error] [client 80.197.147.147] File does not exist:
Hello all,
More livedocs conversation.
I ran into Ilia on IRC, yesterday, and asked him about Goba's idea to
add Livedocs Issue to the bug types on bugs.php.net.
Ilia suggested installing cvstrac for the livedocs module.
(http://www.cvstrac.org/)
I took a quick look over that software, and it
More livedocs conversation.
I ran into Ilia on IRC, yesterday, and asked him about Goba's idea to
add Livedocs Issue to the bug types on bugs.php.net.
Ilia suggested installing cvstrac for the livedocs module.
(http://www.cvstrac.org/)
I took a quick look over that software, and it looks perfect
Well, wanted to see what others thought, before taking it to [EMAIL PROTECTED]
Seems there are a number of cvstrac vulnerabilities.. that's not good.
S
Gabor Hojtsy wrote:
Opinions?
Fine with me. You need to convince systems@ about this anyway :)
Goba
On Tue, 17 Aug 2004, Gabor Hojtsy wrote:
Opinions?
Fine with me. You need to convince systems@ about this anyway :)
It is one more thing to maintain, and I don't really see the value of
it (how cool cvstract might be)
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no |
On Tue, 17 Aug 2004 12:02:34 -0400, Sean Coates [EMAIL PROTECTED] wrote:
Well, wanted to see what others thought, before taking it to [EMAIL PROTECTED]
Seems there are a number of cvstrac vulnerabilities.. that's not good.
S
I'll add a bugs page to the livedocs patch system I'm busy
Derick told me that he added Livedocs Problem as a new Type of Bug on
bugs.php.net (should show up soon).
Problem solved (IMHO).
S
Well, only one I know of (from first-hand experience today :-/)
--Wez.
On Tue, 17 Aug 2004 12:02:34 -0400, Sean Coates [EMAIL PROTECTED] wrote:
Well, wanted to see what others thought, before taking it to [EMAIL PROTECTED]
Seems there are a number of cvstrac vulnerabilities.. that's not
I've also a bug list here, that I'll try to fix when I have some time.
I don't think that branching is the right way to go. I prefer posting my
patches somewhere with a description and then let someone to review, comment
and apply/discard them.
I agree. My branch proposal was because it seemed the
Instead of non-specific head is broken email, why not point out what
is broken?
Livedocs is running fine here; I built it only a week or so ago with
no problems.
Plus, I have a mirror that updates daily (livedocs.thebrainroom.net)
with no problems (assuming that someone hasn't broken phpdoc)
Tonight, I wasted many hours upgrading livedocs.
Many things broke, but with some help (IRC - freenode - #phpdoc (join us
(-: ) ), I finally got it working.
For anyone with the same troubles, here's what I did:
1) configure failed to detect my xsltproc binary, so I had to change
XSLTPROC='no'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[This is a follow-up post to my previous post, Livedocs woes.]
What is the current status of livedocs development?
My understanding is that anyone with phpdoc karma, also, once, had
livedocs karma. A commit was made that some maintainers did not like,
Hi Sean,
Currently the way of getting changes commited to the 'livedocs' in CVS
is to submit patches to those who have karma. When submitting
patches, remeber to do 'cvs diff -u' and save this patch to your
website and mail them the link and explain to them what you are trying
to do with the
For anyone with the same troubles, here's what I did:
1) configure failed to detect my xsltproc binary, so I had to change
XSLTPROC='no' to XSLTPROC=/usr/bin/xsltproc, otherwise, build.sh
fails because it doesn't know how to execute no
maybe you don't have /usr/bin in the PATH :)
the
What is the current status of livedocs development?
Accepting patches (applied mostly by Ilia and Wez).
There are several outstanding issues with the livedocs code. As I said
in my post, last night, HEAD seems broken. Also, Nuno has a number of
patches available at http://livedocs.aborla.net/
It
About my patches: I've posted that patches in my website just to don't lost
them. Some are tested and can be commited, but some are just
proof-of-concept. They can be used later by Ilia, Wez or Derick to fix the
problems that I've found (and they may be aware of, but hadn't time to fix
yet). The
On August 14, 2004 04:23 pm, you wrote:
There are several outstanding issues with the livedocs code. As I said
in my post, last night, HEAD seems broken. Also, Nuno has a number of
patches available at http://livedocs.aborla.net/
It would be nice if Ilia (and/or Wez) could review these
Ilia,
I reviewed the patches and applied 7 of them, thanks guys.
The Cygwin patch was not applied because I have not way to test it and the
last person I spoke to who build the manual on win32 via Cygwin had no
issues.
What in HEAD is broken?
Thank you very much. I know you're busy, I really
Hello,
I did a quick patch for the livedocs default theme:
http://aidan.dotgeek.org/livedocs_css.diff
It cleans up a bit of redudant code, and makes the method/class synopsis
look nicer by dropping the func/class size.
Is there an online version somewhere?
Regards
// Tom
We will have a livedocs on-line in the new website for the documentation
teams.
The website will be lauched soon.
Stay tuned! :)
Nuno
- Original Message -
From: Tom Sommer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 13, 2004 5:34 PM
Subject: [PHP-DOC] livedocs
It's working here, although you must copy xml_classes5.php manually (if
using PHP 5, only), because the configure script isn't handling it
automatically.
Nuno
P.S.: I already had a problem building, but then I've set
the --with-build-dir=/tmp and it worked! :)
- Original Message -
Hi there,
I've been trying to build a phpdoc-all without success for two days.
Does it works for you ?
didou
Hello,
Latest improvements on livedocs have broken it.
The problem is in handle_include(). It was modified so that it could solve
the problem with PCRE (for example).
However that implementation contains a bug. Let's see:
This 3 line long sql query never returns a result (at least on my
Hi Wez,
Today you have commited my patch, but it was modified. Check ref.spl or
ref.tidy and you will see that are broken, because you missed some parts of
my patch.
Attached is the patch to solve that issues (the parts that weren't commited)
and also a bugfix for the PCRE page.
Nuno
Index:
: Nuno Lopes [mailto:[EMAIL PROTECTED]
Sent: 23 May 2004 11:51
To: PHPdoc
Subject: [PHP-DOC] livedocs PATCH
Hi Wez,
Today you have commited my patch, but it was modified. Check
ref.spl or
ref.tidy and you will see that are broken, because you missed
some parts of
my patch
Hey Nuno,
I left out those other parts because:
1/ lookup_title() is good thing to use (take a look at what it does)
Oh, it is caching the results But SPL, Tidy,... don't work.
Mine implementation fetches the title and the description with one DB query
instead of two that you would do
2/ Although I want to solve the dom problem, I don't want
to hard code dom
specifics into the guts of livedocs
So how? How do you know if you to append 'dom-' to the id?
There should be a generic mechanism to name functions based on the extension
that they are in.
3/ the version stuff
2/ Although I want to solve the dom problem, I don't want
to hard code dom
specifics into the guts of livedocs
So how? How do you know if you to append 'dom-' to the id?
There should be a generic mechanism to name functions based on the
extension
that they are in.
For, we should
tags attributes ;). sure that i
can loop via the attibutes and add them but this looks to me unnecessary
code duplication.
--/moshe.
--Wez.
-Original Message-
From: moshe doron [mailto:[EMAIL PROTECTED]
Sent: 10 May 2004 14:10
To: [EMAIL PROTECTED]
Subject: [PHP-DOC
The following patch:
http://cvs.php.net/diff.php/php-src/ext/sqlite/sqlite.c?r1=1.58r2=1.59ty=u
is need to be adopted also for PHP_4_3 to make livedocs working on php4.
in php4 there is no sqlite_single_query() function.
--/moshe.
doron [mailto:[EMAIL PROTECTED]
Sent: 10 May 2004 11:34
To: [EMAIL PROTECTED]
Subject: [PHP-DOC] livedocs on php4 - sqlite_single_query()
The following patch:
http://cvs.php.net/diff.php/php-src/ext/sqlite/sqlite.c?r1=1.5
8r2=1.59ty=u
is need to be adopted also for PHP_4_3 to make
my mistake. sorry.
--/moshe.
Wez Furlong [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
pear upgrade sqlite
% php -v
PHP 4.3.6RC4-dev (cli) (built: Apr 9 2004 16:45:19)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
% php
Hi:
this patch allow style_mapping functions to continue transform the node via
the default transform function:
http://moshe.i-com-it.com/patchs/livedocs-styletransform.patch.txt
i run into the issue when i see i have no elegant way override the
text-align style using the transform function,
-
From: moshe doron [mailto:[EMAIL PROTECTED]
Sent: 10 May 2004 14:10
To: [EMAIL PROTECTED]
Subject: [PHP-DOC] livedocs [PATCH] - allowing style_mapping
to transform()
Hi:
this patch allow style_mapping functions to continue
transform the node via
the default transform function
1 - 100 of 164 matches
Mail list logo
