[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Documentation's modification
From:       Jérémy_Lugagne <lugagne.jeremy () gmail ! com>
Date:       2009-01-26 19:51:11
Message-ID: a4dc807e0901261151x79e55e87vb596a9dd445420bc () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


HI,
thanks for this answer, but i've looking for the forEachElement in the Qt's
API but i haven't find it. In fact, my notice is about the absence of links
to the KoXml namespace (where forEachElement is documented).

Regards.

P.S. : Sorry if my english is approximate, but i'm french and i've a bad
level in english

2009/1/26 Cyrille Berger <cberger@cberger.net>

> On Sunday 25 January 2009, Lugagne J=E9r=E9my wrote:
> > Hi,
> >
> > I'm working on koffice and i must use KoXml but some information wasn't
> > easy to find.
>
>
> Not sure if you are aware, but KoXml mimicks Qt's XML API. So if you need
> to know how to use KoXml, I would suggest to read Qt's API documentation.
>
>
> > So I propose you one modification in the KoXmlDocument's
> > documentation. Add a sentence like :
> > "To find all child elements whitout text nodes, use
> > KoXml::forEachElement( KoXmlElement e, KoXmlNode parent )."
>
>
> If you keep in mind what I just said, the following:
> * To find all child elements with a given name, use
> * QDomElement e;
> * forEachElement( e, parent )
>
>
> is quiet clear that you are going to iterate over {Q|Ko}DomElement, which
> exclude text node.
>
>
> --
> Cyrille Berger
>

[Attachment #5 (text/html)]

HI,<br>thanks for this answer, but i&#39;ve looking for the forEachElement in the \
Qt&#39;s API but i haven&#39;t find it. In fact, my notice is about the absence of \
links to the KoXml namespace (where forEachElement is documented).<br> \
<br>Regards.<br><br>P.S. : Sorry if my english is approximate, but i&#39;m french and \
i&#39;ve a bad level in english<br><br><div class="gmail_quote">2009/1/26 Cyrille \
Berger <span dir="ltr">&lt;<a \
href="mailto:cberger@cberger.net">cberger@cberger.net</a>&gt;</span><br> <blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"><div style="font-family: &#39;DejaVu Sans&#39;; \
font-size: 9pt; font-weight: 400; font-style: normal;"> <div class="Ih2E3d">On Sunday \
25 January 2009, Lugagne Jérémy wrote:<br> &gt; Hi,<br>
&gt;<br>
&gt; I&#39;m working on koffice and i must use KoXml but some information \
wasn&#39;t<br> &gt; easy to find.<br>
<p style="margin: 0px; text-indent: 0px;"><br></p></div>Not sure if you are aware, \
but KoXml mimicks Qt&#39;s XML API. So if you need to know how to use KoXml, I would \
suggest to read Qt&#39;s API documentation.<div class="Ih2E3d"> <br>
<p style="margin: 0px; text-indent: 0px;"><br></p>&gt; So I propose you one \
modification in the KoXmlDocument&#39;s<br> &gt; documentation. Add a sentence like \
:<br> &gt; &quot;To find all child elements whitout text nodes, use<br>
&gt; KoXml::forEachElement( KoXmlElement e, KoXmlNode parent ).&quot;<br>
<p style="margin: 0px; text-indent: 0px;"><br></p></div>If you keep in mind what I \
                just said, the following:<br>
 * To find all child elements with a given name, use<br>
 * QDomElement e;<br>
 * forEachElement( e, parent )<br>
<p style="margin: 0px; text-indent: 0px;"><br></p>is quiet clear that you are going \
to iterate over {Q|Ko}DomElement, which exclude text node.<br> <p style="margin: 0px; \
text-indent: 0px;"><br></p>-- <br><font color="#888888"> Cyrille \
Berger</font></div></blockquote></div><br>



_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]