Has the planned tutorial ever materialized:
how to use tDOM's XSLT engine (http://wiki.tcl.tk/1948)
Can someone outline their experience with tDOM as an XSLT-processor?
How would it work?
Thanks.
--- In tdom@yahoogroups.com, Rolf Ade <rolf@...> wrote:
> Well, yes, autoclosing is a weak point of the html parser. Thanks for
> your patch.
>
Similar code is needed for <dd> and <dt>. So this is my suggested patch
(combined with the <li> change as that does not yet seem to be in CVS):
Index: domhtml.c
===================================================================
RCS file: /usr/local/pubcvs/tdom/generic/domhtml.c,v
retrieving revision 1.19
diff -u -b -r1.19 domhtml.c
--- domhtml.c 4 Mar 2008 20:52:47 -0000 1.19
+++ domhtml.c 17 Jul 2009 19:00:42 -0000
@@ -1184,6 +1184,10 @@
break;
case 'b': if(!strcmp(e,"b")&&!strcmp(pn,"b"))
autoclose=1;
break;
+ case 'd': if((!strcmp(e,"dd")||!strcmp(e,"dt"))
+ &&(!strcmp(pn,"dd")||!strcmp(pn,"dt")))
autoclose=1;
+ break;
+ case 'l': if (!strcmp(e,"li")&&!strcmp(pn,"li"))
autoclose = 1; break;
case 'o': if
(!strcmp(e,"option")&&!strcmp(pn,"option")) autoclose = 1; break;
case 'p': if((!strcmp(e,"pre")&&!strcmp(pn,"pre"))
||(!strcmp(e,"p")&&!strcmp(pn,"p")))
autoclose=1;
Schelte.
Schelte Bron wrote:
> Is this the right place to send small patches?
Yes.
> I found out that autoclosing of HTML <li> tags doesn't yet fully
> work in the current CVS head. I figured out that the problem is
> that a new <li> tag doesn't close the previous one. Only </ol>
> and similar tags do. So if there was more than one <li> in the
> list, those earlier ones are not closed and parsing may fail.
Well, yes, autoclosing is a weak point of the html parser. Thanks for
your patch.
rolf
Hi,
Is this the right place to send small patches?
I found out that autoclosing of HTML <li> tags doesn't yet fully
work in the current CVS head. I figured out that the problem is
that a new <li> tag doesn't close the previous one. Only </ol>
and similar tags do. So if there was more than one <li> in the
list, those earlier ones are not closed and parsing may fail.
The solution seems simple:
Index: domhtml.c
===================================================================
RCS file: /usr/local/pubcvs/tdom/generic/domhtml.c,v
retrieving revision 1.19
diff -u -b -r1.19 domhtml.c
--- domhtml.c 4 Mar 2008 20:52:47 -0000 1.19
+++ domhtml.c 15 Jul 2009 10:22:07 -0000
@@ -1184,6 +1184,7 @@
break;
case 'b': if(!strcmp(e,"b")&&!strcmp(pn,"b")) autoclose=1;
break;
+ case 'l': if (!strcmp(e,"li")&&!strcmp(pn,"li")) autoclose = 1;
break;
case 'o': if (!strcmp(e,"option")&&!strcmp(pn,"option"))
autoclose = 1; break;
case 'p': if((!strcmp(e,"pre")&&!strcmp(pn,"pre"))
||(!strcmp(e,"p")&&!strcmp(pn,"p"))) autoclose=1;
Regards,
Schelte
--- In tdom@yahoogroups.com, Rolf Ade <rolf@...> wrote:
>
> No, I didn't know about that things. Is that discussion archived
> public available, somewhere and do you have a link to it?
>
> rolf
>
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344122 is the report I saw
today that brought it to mind. However, I've not taken a look through their
database to see if other issues have arisen.
Larry W. Virden wrote:
> Are the maintainers of tdom notified when changes occur in the tdom
> package for specific distributions? I noticed recently a series of
> emails, and finally a patch, discussed in the Debian Tcl mailing
> list. There were some changes made so that installation included
> tdomhtml and tnc, an example directory created, etc.
>
> I didn't know if they bothered to submit bug reports and the patches
> to you or not.
No, I didn't know about that things. Is that discussion archived
public available, somewhere and do you have a link to it?
rolf
Are the maintainers of tdom notified when changes occur in the tdom package for
specific distributions? I noticed recently a series of emails, and finally a
patch, discussed in the Debian Tcl mailing list. There were some changes made so
that installation included tdomhtml and tnc, an example directory created, etc.
I didn't know if they bothered to submit bug reports and the patches to you or
not.
Thanks for the heads up. This did in fact allow me to successfully install
tDOM, which in turn allowed a successful install of my target app.
My thanks to all!!!!!!!!
--- In tdom@yahoogroups.com, "stefan.sobernig" <ss@...> wrote:
>
> > Finally, as for the dropping of tdom from Ubuntu, perhaps someone on
> > this mailing list can bring that issue up with the appropriate team.
>
> tdom has already been reintroduced successfully, and comes with debian
{stable|unstable|testing}:
>
> see http://packages.qa.debian.org/t/tdom.html
>
> as ubuntu retrieves package drops from debian unstable at regular intervals,
tdom is featured in ubuntu starting with jaunty:
>
> see http://packages.ubuntu.com/jaunty/tdom
>
> (btw. a hint for custom builts: the debian package manifestos, especially the
rules script, are rich sources of adequate configure settings, see e.g.
>
> http://svn.debian.org/viewsvn/pkg-tcltk/tdom/trunk/debian/rules?view=markup
>
> //stefan
>
> Finally, as for the dropping of tdom from Ubuntu, perhaps someone on
> this mailing list can bring that issue up with the appropriate team.
tdom has already been reintroduced successfully, and comes with debian
{stable|unstable|testing}:
see http://packages.qa.debian.org/t/tdom.html
as ubuntu retrieves package drops from debian unstable at regular intervals,
tdom is featured in ubuntu starting with jaunty:
see http://packages.ubuntu.com/jaunty/tdom
(btw. a hint for custom builts: the debian package manifestos, especially the
rules script, are rich sources of adequate configure settings, see e.g.
http://svn.debian.org/viewsvn/pkg-tcltk/tdom/trunk/debian/rules?view=markup
//stefan
Larry, I thank you for the continuing dialog. My error in not describing myself
as a newbie to Linux. I must proceed with my assembly code project, but if you
would follow through with me on the environment variables that would be great.
As Mathias stated in a separate post, I really should improve my understanding
of Linux.
--- In tdom@yahoogroups.com, "Larry W. Virden" <lvirden@...> wrote:
>
> On Sun, Mar 29, 2009 at 11:55 AM, Barry Demers <sdad@...> wrote:
>
> > What put me over the edge is the fact that the $PATH variable will not
> > remain updated with the additional info. I can put it in, then do an echo,
> > see its there, do a which, close terminal, reopen do a where, get a "not
> > recognized command", do an echo $PATH and have the variable in its original
> > state. Egads!!!!!!!!!!!
>
> I apologize - I made the assumption that you were familar with Linux
> or Unix and should not have made that assumption.
>
> To make a change to PATH that you want to keep, you must edit the
> personal config file that your login shell supports. Some shells
> support $HOME/.profile , some support a file set in $ENV, some a
> $HOME/.bashrc , etc.
>
> In that file you would either edit the existing PATH and MANPATH
> setting statements or you would add statements that would do something
> like
>
> export PATH=/path/to/ActiveTcl/bin:$PATH
> export MANPATH=/path/to/ActiveTcl/man:$MANPATH
>
> The default install location is truly up to the user - there isn't any
> real difference between installing in /opt or /home, as far as I am
> aware.
>
> As for running the ActiveTcl installer under sudo, I would suggest
> dropping a message to ActiveState's tcl support team and ask if they
> have any recommendations.
>
> Finally, as for the dropping of tdom from Ubuntu, perhaps someone on
> this mailing list can bring that issue up with the appropriate team.
>
> I am so sorry you had a tough time getting things to work.
>
> --
> Tcl - The glue of a new generation. http://wiki.tcl.tk/
> Larry W. Virden
> http://www.xanga.com/lvirden/
> Even if explicitly stated to the contrary, nothing in this posting
> should be construed as representing my employer's opinions.
>
On Sun, Mar 29, 2009 at 11:55 AM, Barry Demers <sdad@...> wrote:
> What put me over the edge is the fact that the $PATH variable will not
> remain updated with the additional info. I can put it in, then do an echo,
> see its there, do a which, close terminal, reopen do a where, get a "not
> recognized command", do an echo $PATH and have the variable in its original
> state. Egads!!!!!!!!!!!
I apologize - I made the assumption that you were familar with Linux
or Unix and should not have made that assumption.
To make a change to PATH that you want to keep, you must edit the
personal config file that your login shell supports. Some shells
support $HOME/.profile , some support a file set in $ENV, some a
$HOME/.bashrc , etc.
In that file you would either edit the existing PATH and MANPATH
setting statements or you would add statements that would do something
like
export PATH=/path/to/ActiveTcl/bin:$PATH
export MANPATH=/path/to/ActiveTcl/man:$MANPATH
The default install location is truly up to the user - there isn't any
real difference between installing in /opt or /home, as far as I am
aware.
As for running the ActiveTcl installer under sudo, I would suggest
dropping a message to ActiveState's tcl support team and ask if they
have any recommendations.
Finally, as for the dropping of tdom from Ubuntu, perhaps someone on
this mailing list can bring that issue up with the appropriate team.
I am so sorry you had a tough time getting things to work.
--
Tcl - The glue of a new generation. http://wiki.tcl.tk/
Larry W. Virden
http://www.xanga.com/lvirden/
Even if explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.
Barry Demers schrieb:
> What put me over the edge is the fact that the $PATH variable will not
> remain updated with the additional info. I can put it in, then do an
> echo, see its there, do a which, close terminal, reopen do a where, get
> a "not recognized command", do an echo $PATH and have the variable in
> its original state. Egads!!!!!!!!!!! Tried export using sudo (sudo
> export ....) and that also fails with "not recognized sudo export".
>
> Little frustrated with Ubuntu as well since I was never allowed to
> install ActiveTcl in /opt, which appears to be the desired default for
> ActiveTcl.
Frankly, some basic Linux knowledge would be of help. Invest the time,
it will safe you more troubles!
kind regards
--
Matthias Kraft
Software AG, Germany
You've spent a great deal of time and effort with me here and I really
appreciate it. At this point I am pulling the plug, and live without installing
this program. May not like it anyway.
What put me over the edge is the fact that the $PATH variable will not remain
updated with the additional info. I can put it in, then do an echo, see its
there, do a which, close terminal, reopen do a where, get a "not recognized
command", do an echo $PATH and have the variable in its original state.
Egads!!!!!!!!!!! Tried export using sudo (sudo export ....) and that also fails
with "not recognized sudo export".
Little frustrated with Ubuntu as well since I was never allowed to install
ActiveTcl in /opt, which appears to be the desired default for ActiveTcl.
Ubuntu doesn't allow a root logon, and the graphical installer for ActiveTcl
doesn't appear to do sudo, so.../home it is
Ubuntu appears to have removed tDOM from their repository, so all around I'm
having road bumps.
Venting complete
Thanks again, you're a good man!
--- In tdom@yahoogroups.com, "Larry W. Virden" <lvirden@...> wrote:
>
> --- In tdom@yahoogroups.com, "Barry Demers" <sdad@> wrote:
>
> >
> > barry@polly-control:~$ teacup install tdom
> > Resolving tdom ... [package tdom 0.8.3 linux-glibc2.3-ix86 ... Already
installed in repository, probing dependencies]
> > Resolving Tcl 8.4 -is package ... [package Tcl 8.5.6 _ ... Installed outside
repository, probing dependencies]
> >
> > So, above means that tdom isn't in or I once again have a path issue. I am
using Gnome, and a search for tdom returns nothing to do with tdom, though it
did find 3 unrelated strings. Where would tdom go so I can tell the installer
for mcu8051ide(the app I want) where tdom is? ----From the name of my target
app, you may have surmised that what I really am after is being able to generate
some assembly code for a microcontroller. I am interested in seeing if his ide
will be of value------
>
>
> Here's how _I_ found my tdom.
>
> $ where teacup
> /var/tmp/ActiveTcl/bin/teacup
> $ /var/tmp/ActivetTcl/bin/tclsh8.5
> % package require tdom
> 0.8.3
> % exit
> $ find /var/tmp/ActiveTcl/lib/. -type f -print | grep -i tdom
>
/var/tmp/ActiveTcl/lib/./teapot/package/solaris2.8-sparc/lib/tdom0.8.3/tdom.tcl
>
/var/tmp/ActiveTcl/lib/./teapot/package/solaris2.8-sparc/lib/tdom0.8.3/libtdom0.\
8.3.so
>
/var/tmp/ActiveTcl/lib/./teapot/package/solaris2.8-sparc/lib/tdom0.8.3/pkgIndex.\
tcl
> /var/tmp/ActiveTcl/lib/./teapot/package/tcl/teapot/tcl8/8.4/tdomhtml-0.1.0.tm
>
--- In tdom@yahoogroups.com, "Barry Demers" <sdad@...> wrote:
>
> barry@polly-control:~$ teacup install tdom
> Resolving tdom ... [package tdom 0.8.3 linux-glibc2.3-ix86 ... Already
installed in repository, probing dependencies]
> Resolving Tcl 8.4 -is package ... [package Tcl 8.5.6 _ ... Installed outside
repository, probing dependencies]
>
> So, above means that tdom isn't in or I once again have a path issue. I am
using Gnome, and a search for tdom returns nothing to do with tdom, though it
did find 3 unrelated strings. Where would tdom go so I can tell the installer
for mcu8051ide(the app I want) where tdom is? ----From the name of my target
app, you may have surmised that what I really am after is being able to generate
some assembly code for a microcontroller. I am interested in seeing if his ide
will be of value------
Here's how _I_ found my tdom.
$ where teacup
/var/tmp/ActiveTcl/bin/teacup
$ /var/tmp/ActivetTcl/bin/tclsh8.5
% package require tdom
0.8.3
% exit
$ find /var/tmp/ActiveTcl/lib/. -type f -print | grep -i tdom
/var/tmp/ActiveTcl/lib/./teapot/package/solaris2.8-sparc/lib/tdom0.8.3/tdom.tcl
/var/tmp/ActiveTcl/lib/./teapot/package/solaris2.8-sparc/lib/tdom0.8.3/libtdom0.\
8.3.so
/var/tmp/ActiveTcl/lib/./teapot/package/solaris2.8-sparc/lib/tdom0.8.3/pkgIndex.\
tcl
/var/tmp/ActiveTcl/lib/./teapot/package/tcl/teapot/tcl8/8.4/tdomhtml-0.1.0.tm
Followed instructions regarding teacup. It is certainly in. Feel a bit
sheepish on path issue. I think that my ignorance extends beyond that, though.
When trying to install the app that I really want to use I get a message back
saying that tdom isn't installed. In following your instructions I get this
returned:
barry@polly-control:~$ teacup install tdom
Resolving tdom ... [package tdom 0.8.3 linux-glibc2.3-ix86 ... Already installed
in repository, probing dependencies]
Resolving Tcl 8.4 -is package ... [package Tcl 8.5.6 _ ... Installed outside
repository, probing dependencies]
So, above means that tdom isn't in or I once again have a path issue. I am
using Gnome, and a search for tdom returns nothing to do with tdom, though it
did find 3 unrelated strings. Where would tdom go so I can tell the installer
for mcu8051ide(the app I want) where tdom is? ----From the name of my target
app, you may have surmised that what I really am after is being able to generate
some assembly code for a microcontroller. I am interested in seeing if his ide
will be of value------
--- In tdom@yahoogroups.com, "Larry W. Virden" <lvirden@...> wrote:
>
> I can help you with using teacup.
>
> 1. at your command line prompt, type
> which teacup
>
> 2. If the response is
> no teacup in ...
> that means you have not yet followed the instructions displayed at the end
> of the ActiveTcl installer program, putting /home/user/activetcl8.5.6/bin in
> your $PATH variable, so
> type
> export PATH=$PATH:/home/user/activetcl8.5.6/bin;export
> MANPATH=$MANPATH:/home/user/activetcl8.5.6/man
> and then type
> which teacup
> again.
>
> 3. When the "which teacup" returns a path, type
> teacup timeout 120
> teacup update-self
> so that you have the latest version of teacup.
>
> 4. Then type
> teacup install tdom
>
> 5. Then, I recommend typing
> teacup update
>
> to get everything else installed.
> You are done.
>
> On 3/27/09, Barry Demers <sdad@...> wrote:
> >
> >
> > I just installed activetcl 8.5.6, into /home/user/activetcl 8.5.6/
> > and got same results when trying to install the tdom 0.8.2 located from the
> > /home/user/tdom-0.8.2/unix/ dir. A suggestion has been made to install tdom
> > using teacup, but with that I am totally clueless.
> >
> > .
> >
>
>
> Read http://wiki.tcl.tk/teacup_install
>
>
> >
>
>
>
> --
> Tcl - The glue of a new generation. http://wiki.tcl.tk/
> Larry W. Virden
> http://www.xanga.com/lvirden/
> Even if explicitly stated to the contrary, nothing in this posting
> should be construed as representing my employer's opinions.
>
Barry Demers wrote:
> I removed 8.5 and ran: sudo apt-get install tcl8.4 tcl8.4-dev tk8.4
> tk8.4-dev.
>
> When doing ../configure on tdom-0.8.2 I got:
>>> checking for correct TEA configuration... ok (TEA 3.6)
>>> checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions.
>
> Same issue as earlier attempts. Is Ubuntu putting tcl in a dir that
> tdom is expecting? Is some file still not being installed?
The configure file looks for the information about the installed tcl
in 'usual' places (like /usr/local/lib). If Ubuntu puts that into an
'unusual' place, it may not find it by itself.
Search for where the file tclConfig.sh is on your system. Then call
the tDOM configure from the unix directory with
../configure --with-tcl=/path/to/your/tclConfig.sh
rolf
2. If the response is
no teacup in ...
that means you have not yet followed the instructions displayed at the
end of the ActiveTcl installer program, putting
/home/user/activetcl8.5.6/bin in your $PATH variable, so
type
export PATH=$PATH:/home/user/activetcl8.5.6/bin;export MANPATH=$MANPATH:/home/user/activetcl8.5.6/man
and then type
which teacup
again.
3. When the "which teacup" returns a path, type
teacup timeout 120
teacup update-self
so that you have the latest version of teacup.
I just installed activetcl 8.5.6, into /home/user/activetcl 8.5.6/
and got same results when trying to install the tdom 0.8.2 located from
the /home/user/tdom-0.8.2/unix/ dir. A suggestion has been made to
install tdom using teacup, but with that I am totally clueless.
-- Tcl - The glue of a new generation. http://wiki.tcl.tk/ Larry W. Virden http://www.xanga.com/lvirden/
Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions.
I just installed activetcl 8.5.6, into /home/user/activetcl 8.5.6/
and got same results when trying to install the tdom 0.8.2 located from the
/home/user/tdom-0.8.2/unix/ dir. A suggestion has been made to install tdom
using teacup, but with that I am totally clueless.
--- In tdom@yahoogroups.com, "Barry Demers" <sdad@...> wrote:
>
> I removed 8.5 and ran: sudo apt-get install tcl8.4 tcl8.4-dev tk8.4 tk8.4-dev.
>
> When doing ../configure on tdom-0.8.2 I got:
> > > checking for correct TEA configuration... ok (TEA 3.6)
> > > checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions.
>
> Same issue as earlier attempts. Is Ubuntu putting tcl in a dir that tdom is
expecting? Is some file still not being installed?
>
>
> --- In tdom@yahoogroups.com, "Michael A. Cleverly" <michael@> wrote:
> >
> > On Fri, Mar 27, 2009 at 2:06 PM, Barry Demers <sdad@> wrote:
> > > Tried again got this message:
> > > checking for correct TEA configuration... ok (TEA 3.6)
> > > checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions
> > >
> > > I had installed Tcl/Tk by doing sudo apt-get install tcl8.5 tk8.5
> > > I have an app written using Tcl/Tk which does work. �Where to from here?
> >
> > apt-get install the tcl8.5-dev and tk8.5-dev packages (so you have the
> > necessary Tcl header files, etc.) and then re-run tdom's ../configure.
> >
> > Michael
> >
>
I removed 8.5 and ran: sudo apt-get install tcl8.4 tcl8.4-dev tk8.4 tk8.4-dev.
When doing ../configure on tdom-0.8.2 I got:
> > checking for correct TEA configuration... ok (TEA 3.6)
> > checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions.
Same issue as earlier attempts. Is Ubuntu putting tcl in a dir that tdom is
expecting? Is some file still not being installed?
--- In tdom@yahoogroups.com, "Michael A. Cleverly" <michael@...> wrote:
>
> On Fri, Mar 27, 2009 at 2:06 PM, Barry Demers <sdad@...> wrote:
> > Tried again got this message:
> > checking for correct TEA configuration... ok (TEA 3.6)
> > checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions
> >
> > I had installed Tcl/Tk by doing sudo apt-get install tcl8.5 tk8.5
> > I have an app written using Tcl/Tk which does work. �Where to from here?
>
> apt-get install the tcl8.5-dev and tk8.5-dev packages (so you have the
> necessary Tcl header files, etc.) and then re-run tdom's ../configure.
>
> Michael
>
On Fri, Mar 27, 2009 at 2:06 PM, Barry Demers <sdad@...> wrote:
> Tried again got this message:
> checking for correct TEA configuration... ok (TEA 3.6)
> checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions
>
> I had installed Tcl/Tk by doing sudo apt-get install tcl8.5 tk8.5
> I have an app written using Tcl/Tk which does work. Where to from here?
apt-get install the tcl8.5-dev and tk8.5-dev packages (so you have the
necessary Tcl header files, etc.) and then re-run tdom's ../configure.
Michael
Tried again got this message:
checking for correct TEA configuration... ok (TEA 3.6)
checking for Tcl configuration... configure: WARNING: Can't find Tcl
configuration definitions
I had installed Tcl/Tk by doing sudo apt-get install tcl8.5 tk8.5
I have an app written using Tcl/Tk which does work. Where to from here?
--- In tdom@yahoogroups.com, Rolf Ade <rolf@...> wrote:
>
>
> Barry Demers wrote:
> > I am using Ubuntu 8.10 and am trying to install an application that
> > requires tdom. I went to tdom page an downloaded tdom 0.8.2.
> > Readme file says to goto unix directory and do ./configure........My
> > download has CONFIG, not configure, but tried CONFIG anyway. NO go.
> > How do I get around this issue? I see install scripts all over the
> > place, but uncertain about those, so I though I would admit to my
> > stupidity so that I can get on with what I really need to be doing.
>
> The README say, go to the unix directory and do ../configure
> (Note the ../ !)
>
> rolf
>
--- In tdom@yahoogroups.com, "Barry Demers" <sdad@...> wrote:
>
> I am using Ubuntu 8.10 and am trying to install an application that requires
tdom. I went to tdom page an downloaded tdom 0.8.2. Readme file says to goto
unix directory and do ./configure........My download has CONFIG, not configure,
but tried CONFIG anyway. NO go. How do I get around this issue? I see install
scripts all over the place, but uncertain about those, so I though I would admit
to my stupidity so that I can get on with what I really need to be doing.
>
> Any help you can provide would be hugely appreciated!
>
My personal recommendation would be to install ActiveState's ActiveTcl (pick the
version that you need), and then use their "teacup install tdom" to install the
extension simply.
Or, if you are going to be doing a lot of tcl development, take a few minutes
and run "teacup update" which will install a large suite of tcl add-ons for you
to use.
Barry Demers wrote:
> I am using Ubuntu 8.10 and am trying to install an application that
> requires tdom. I went to tdom page an downloaded tdom 0.8.2.
> Readme file says to goto unix directory and do ./configure........My
> download has CONFIG, not configure, but tried CONFIG anyway. NO go.
> How do I get around this issue? I see install scripts all over the
> place, but uncertain about those, so I though I would admit to my
> stupidity so that I can get on with what I really need to be doing.
The README say, go to the unix directory and do ../configure
(Note the ../ !)
rolf
I am using Ubuntu 8.10 and am trying to install an application that requires
tdom. I went to tdom page an downloaded tdom 0.8.2. Readme file says to goto
unix directory and do ./configure........My download has CONFIG, not configure,
but tried CONFIG anyway. NO go. How do I get around this issue? I see install
scripts all over the place, but uncertain about those, so I though I would admit
to my stupidity so that I can get on with what I really need to be doing.
Any help you can provide would be hugely appreciated!
Asher Klatchko wrote:
> The DTD is alright as a hydra for the XML data-structure. But we often times
skip it in our amateurish approach to data and yet have it as well formed
document.
> If the parser would be able to to the job of a validating agent we would be
ahead of ourselves... what do you say?
I'm not sure, I understand the question. Do you ask for DTD
validation? If yes, look at the tnc extension (which is bundled with
the distribution).
> Had a chance to look into your starDom editor - nice piece of work!
> would be nice if you could add some more text editing features to it
> (e.g. cut n' paste ).
I did only some improvements to the stardom viewer, that Richard
Suchenwirth started. IIRC, Arjen Markus, published a version, which
allowed actually pcdata editing.
If we talk about the same thing, then this is just a small tcl
script. Adjusting that to your needs should be easy, even for Joe Tcl
Programmer.
rolf
The DTD is alright as a hydra for the XML data-structure. But we often times skip it in our amateurish approach to data and yet have it as well formed document. If the parser would be able to to the job of a validating agent we would be ahead of ourselves... what do you say?
Had a chance to look into your starDom editor - nice piece of work! would be nice if you could add some more text editing features to it (e.g. cut n' paste ).
p.s. the AIX linker to tDom misses a -lm for "ceil" and "floor"
Thanks a bunch,
~reb
A goal is not always meant to be reached, it often serves simply as something to aim at. Bruce Lee
From: Rolf Ade <rolf@...> To: tdom@yahoogroups.com Sent: Friday, March 6, 2009 6:50:00 PM Subject: Re: [tdom] Re: Uset tdom from C
Asher Klatchko wrote: > Gotcha. Indeed it works with a built in DTD but would be nice to > have the lookup-id-table.
Well, it also works with
an external DTD, if you prefer that. In that case, you've to provide an -externalentitycomm and as URI resolver. In other words, the usual limbo dance, which at least provides the maximal freedom to the script author, after you've got to it.
Asher Klatchko wrote:
> Gotcha. Indeed it works with a built in DTD but would be nice to
> have the lookup-id-table.
Well, it also works with an external DTD, if you prefer that. In that
case, you've to provide an -externalentitycommand as URI resolver. In
other words, the usual limbo dance, which at least provides the
maximal freedom to the script author, after you've got to it.
What would be nice to have?
rolf
Gotcha. Indeed it works with a built in DTD but would be nice to have the lookup-id-table.
Thanks, reb.
==
A goal is not always meant to be reached, it often serves simply as something to aim at. Bruce Lee
From: Rolf Ade <rolf@...> To: tdom@yahoogroups.com Sent: Friday, March 6, 2009 10:22:54 AM Subject: Re: [tdom] Re: Uset tdom from C
rebosher wrote:
> getElementById doesn't work for me.
>
> $nodeObj find "id" "idname" will get the right tag.
>
> Does getElementById needs a DTD validation? How about a schema (xsd)?
No, it doesn't need DTD validation, but of course a parsed DTD. (Note
the 'parsed', that's a hint in case you've an external DTD subset.)
This is needed because the parser needs to know which attributes are
of the attribute type ID. The name of the attribute is completely
irrelevant, its the attribute type, which makes it to an ID attribute.
Without a DTD, getElementById returns always the empty string. Provide
the correct DTD and it works pretty well.
No, there isn't xsd support.
Note, that the html parser does fill the internal lookup table used by
getElementById if it sees an attribute with the name "id" (in recent
tDOM).
If you know the name of the ID attribue, you could always get the node
with (say, the attribute name is 'id')
$doc selectNodes //*[@id='your_ id_value_ here']
though that is much lesser efficient that getElementById (with a DTD
in place), because the first does a complete tree scan and the later
uses a lookup hash table.
If you need several lookups (and still want/could not provid a DTD)
you could easily build your own lookup table at script level.