Menu
▾
▴
libxmlplusplus-general — Open discusions about libXML++
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(157) |
Dec
(87) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(78) |
Feb
(246) |
Mar
(83) |
Apr
(32) |
May
(99) |
Jun
(85) |
Jul
(34) |
Aug
(24) |
Sep
(65) |
Oct
(60) |
Nov
(45) |
Dec
(90) |
| 2004 |
Jan
(8) |
Feb
(40) |
Mar
(12) |
Apr
(17) |
May
(56) |
Jun
(13) |
Jul
(5) |
Aug
(30) |
Sep
(51) |
Oct
(17) |
Nov
(9) |
Dec
(20) |
| 2005 |
Jan
(16) |
Feb
(22) |
Mar
(14) |
Apr
(6) |
May
(12) |
Jun
(41) |
Jul
(21) |
Aug
(26) |
Sep
(7) |
Oct
(42) |
Nov
(10) |
Dec
(7) |
| 2006 |
Jan
(6) |
Feb
(9) |
Mar
(19) |
Apr
(7) |
May
(1) |
Jun
(10) |
Jul
(5) |
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
| 2007 |
Jan
(1) |
Feb
|
Mar
(7) |
Apr
(5) |
May
(10) |
Jun
(32) |
Jul
(6) |
Aug
(8) |
Sep
(10) |
Oct
(3) |
Nov
(11) |
Dec
(2) |
| 2008 |
Jan
(3) |
Feb
|
Mar
(11) |
Apr
|
May
(6) |
Jun
(4) |
Jul
|
Aug
(3) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(3) |
| 2010 |
Jan
(3) |
Feb
(6) |
Mar
(16) |
Apr
(2) |
May
|
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(4) |
Oct
(3) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2003-04-21 11:53:24
|
Patches item #724953, was opened at 2003-04-21 14:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=724953&group_id=12999 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ephraim Vider (eff7) Assigned to: Nobody/Anonymous (nobody) Summary: new node types support Initial Comment: this patch adds ContentNode which is the base for all non-element type nodes. see XML_GET_CONTENT and XML_GET_LINE in libxml/tree.h for the logic in that. (the content pointer serves as line number in element). It is quite safe to return ContentNode as a default node type even if no specific types are defined. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=724953&group_id=12999 |
|
From: Ephraim V. <ef...@ep...> - 2003-04-20 16:45:25
|
I feel the assert makes the library less useful in its current state. The code may never need to access unsupported node types, since the really useful nodes are supported, but the assert will exit the program anyway. So until all types are supported, or explicitly ignored, I think the warning message _was_ the most useful solution. silently ignoring the unknown types comes second. -eff ----- Original Message ----- So now an assert replace the warning message. This means that some document containing some node type we do not wrap may crash libxml++. I guess that all the xmlElementType ending with _NODE has to be handled if we want the assert not to be reached. So the decision to make for now is do we 1) implement the missing types 2) remove the assert and silently ignore unknown types. Comments / ideas are welcome |
|
From: Christophe de V. <cde...@al...> - 2003-04-20 11:11:35
|
Le Dimanche 20 Avril 2003 12:36, Christophe de Vienne a =E9crit : > Probably, but in a very short time I'll commit the changes I spoke about = in > a previous thread. So now an assert replace the warning message. This means that some document containing some node type we do not wrap may= =20 crash libxml++. I guess that all the xmlElementType ending with _NODE has to be handled if = we=20 want the assert not to be reached. So the decision to make for now is do we=20 1) implement the missing types 2) remove the assert and silently ignore unknown types. Comments / ideas are welcome Regards, Christophe |
|
From: Christophe de V. <cde...@al...> - 2003-04-20 10:38:19
|
Le Dimanche 20 Avril 2003 13:19, Ephraim Vider a =E9crit : > Sorry to come in late, I've seen the patch has already been commited, but > including <iostream.h> is not good. > indeed. I did not see that it has been commited but my suggestion was to=20 remove it completely since it was needed for some useless tracing. We had=20 discussed a bit this issue but I did not change anything in this way so, I= =20 should have been faster to act... > The .h versions of the standard C++ includes are deprecated, in msvc at > least it includes an old version of iostream which is not compatible with > the new template based <iostream>. definitely > > I don't have access to NetBSD, but I imagine including <iostream> will wo= rk > since the h-less version is included everywhere else in the project. > Probably, but in a very short time I'll commit the changes I spoke about in= a=20 previous thread. Cheers Christophe |
|
From: Ephraim V. <ef...@ep...> - 2003-04-20 10:19:58
|
Sorry to come in late, I've seen the patch has already been commited, but including <iostream.h> is not good. The .h versions of the standard C++ includes are deprecated, in msvc at least it includes an old version of iostream which is not compatible with the new template based <iostream>. I don't have access to NetBSD, but I imagine including <iostream> will work since the h-less version is included everywhere else in the project. regards, -eff |
|
From: Stefan S. <se...@sy...> - 2003-04-12 14:26:26
|
Christophe de Vienne wrote: > Le Vendredi 11 Avril 2003 22:45, SourceForge.net a écrit : > And if this could happen, it would probably be better to throw an exception. > > Stefan, since you wrote this part, what's your opinion ? yes, absolutely. I had this code there because the set of node wrapper types wasn't/isn't complete yet, i.e. 'processing instructions' and others aren't covered. As I used that 'in house' I meant to track these messages and add the missing types. Of course in a production environment there shouldn't be any missing wrappers at all, or at least the system should bail out with a meaningful message. I'd suggest assert(), as the situation really hints at a bug in libxml++, not an (runtime) exceptional situation that could / should be treated by application code. Stefan |
|
From: Jonathan W. <co...@co...> - 2003-04-12 12:51:32
|
On Sat, Apr 12, 2003 at 01:25:22AM +0200, Christophe de Vienne wrote: > This <istream> (which should be <iostream> btw, or at least <ostream>) is I believe <iostream> gives maximum portability with pre-standard compilers. jon -- "It is absurd to divide people into good and bad. People are either charming or tedious." - Oscar Wilde |
|
From: Christophe de V. <cde...@al...> - 2003-04-11 23:26:58
|
Le Vendredi 11 Avril 2003 22:45, SourceForge.net a =E9crit : > Initial Comment: > NetBSD wouldn't compile with only <istream> included > in document.cc ... changing it to <iostream.h> works > just fine. This <istream> (which should be <iostream> btw, or at least <ostream>) is=20 needed because of a warning printed if an unknown type of node is created. The annyoing stuff is that this warning is put on std::cout. I'd prefer it = to=20 be on std::cerr but I think it is not needed at all : We know exactly what= =20 are the possible types of node of libxml, and I don't see the real need of= =20 this check. And if this could happen, it would probably be better to throw an exception. Stefan, since you wrote this part, what's your opinion ? Regards, Christophe |
|
From: SourceForge.net <no...@so...> - 2003-04-11 20:28:51
|
Patches item #719921, was opened at 2003-04-11 22:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=719921&group_id=12999 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jaka Jejcic (jejcic) Assigned to: Nobody/Anonymous (nobody) Summary: patch to make it compile on NetBSD Initial Comment: NetBSD wouldn't compile with only <istream> included in document.cc ... changing it to <iostream.h> works just fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=719921&group_id=12999 |
|
From: Stefan S. <se...@sy...> - 2003-04-11 13:34:41
|
Hi Daniel, Peter,
Daniel Veillard wrote:
> On Fri, Apr 11, 2003 at 12:49:27PM +0200, Peter Jacobi wrote:
>>void read_file(char const *input_name, FILE *output)
>>{
>> using xmlpp::DomParser;
>> using xmlpp::Node;
>> using xmlpp::Attribute;
>>
>> DomParser parser(input_name);
>> Node *root = parser.get_root_node();
>> Node::NodeList children = root->children("entry");
>
>
> you see, for me it's very hard to map that to the associated calls
> in libxml2, I can't even tell where the document is actually parsed,
> nor what root->children("entry"); actually does, is taht a call to
XPath ?
> or a direct walk of the children nodes, or ...
>
>
>> Node::NodeList::const_iterator begin = children.begin();
>> Node::NodeList::const_iterator end = children.end();
>>
>> for(int i = 0; begin != end; ++begin, ++i)
>> {
>> Node const *node = *begin;
>> Attribute const *year = node->attribute("year");
>> Attribute const *month = node->attribute("month");
>> Attribute const *day = node->attribute("day");
>> Attribute const *who = node->attribute("who");
>> Entry entry(year->value(),
>> month->value(),
>> day->value(),
>> who->value());
>
>
> I can think of ways to significantly speed up attribute value
> lookup in the general case too..
> ATM I'm working on features, maybe I will have time to do some
> speedup work before the summer..
Apparently the libxml++ version used here is an old one which didn't
really wrap libxml2, but instead used libxml2 for the streaming of the
data only, i.e. all data access and manipulation was based on C++
container types, not on xmlNode !
A couple of weeks ago I committed a patch that changed libxml++'s
implementation dramatically, such that it is now a true wrapper, i.e.
using the _private pointers of xmlNode to bind the libxml2 nodes to
C++ wrapper objects. This implementation is a true wrapper as all
operations such as navigation through the DOM as well as the DOM's
manipulation fall back to libxml2 calls.
In other words, the performance tested above isn't telling you much
about libxml2. Apparently the author didn't care enough or at least
didn't do his homework to at least tell his audience what he was really
testing. Too bad...
Regards,
Stefan
|
|
From: SourceForge.net <no...@so...> - 2003-04-10 03:26:54
|
Patches item #718753, was opened at 2003-04-09 23:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=718753&group_id=12999 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Eric Bourque (shaderman) Assigned to: Nobody/Anonymous (nobody) Summary: fix for spec file Initial Comment: Update to spec file to make it version agnostic. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=718753&group_id=12999 |
|
From: Stefan S. <se...@sy...> - 2003-04-09 15:46:01
|
Christophe de VIENNE wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Le Mercredi 9 Avril 2003 17:31, Stefan Seefeld a écrit : > >>This authority may or may not be the >>development team itself (see debian). > > > Who decides this ? In my experience people show up suggesting that they port a project to a specific platform, i.e. create packages. There isn't really any need for a decision. Neither can I stop someone from porting/distributing a package of a project I'm leading, nor do I want to. Quite in the contrary: as often such work involves at least minor changes, I'm very interested into integrating these patches into the code repository, to keep the packages as much in sync with the project itself as possible. That's the reason to include package-generating scripts (such as the '.spec' file Murray was referring to) in the project's own repository, instead of keeping it separate. As far as specific distributions such as debian are concerned, there is a whole protocol to follow to become an official package maintainer. That is outside the control of individual projects, it's part of debian administration. Regards, Stefan |
|
From: Christophe de V. <cde...@al...> - 2003-04-09 15:36:23
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 9 Avril 2003 17:31, Stefan Seefeld a =E9crit : > This authority may or may not be the > development team itself (see debian). Who decides this ? =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+lD4zB+sU3TyOQjARAgl8AJ9wpXwrkuJeczx/NOFVN9tQNF51+ACgvz/+ tSUUQkqhZeh/m6enzVYe/Cw=3D =3DkTvf =2D----END PGP SIGNATURE----- |
|
From: Christophe de V. <cde...@al...> - 2003-04-09 15:09:37
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 9 Avril 2003 08:21, Cyril Bortolato a =E9crit : > Hi, Hi, > I was wondering if you could release RPMs (source and for x86) > of libxml++ 0.22, and going forward, of future versions as well. > I noticed there was the template of a spec file in your CVS to > enable building such RPMs. > Since I don't use Red Hat, I prefer not to do it because I will not be able= to=20 test the packages. However if someone wants to do it (and for the next releases too), we can p= ut=20 the files on the sourceforge project pages. Cheers, Christophe =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+lDfrB+sU3TyOQjARAkXEAJ0UdmLlVDh1y48UsVUjboYP7TEYrgCgpQXh Dg2oiXD5e4hDOlTuoMQgNc0=3D =3D7CpC =2D----END PGP SIGNATURE----- |
|
From: Cyril B. <bo...@us...> - 2003-04-09 06:21:22
|
Hi, I was wondering if you could release RPMs (source and for x86) of libxml++ 0.22, and going forward, of future versions as well. I noticed there was the template of a spec file in your CVS to enable building such RPMs. I'm asking, because my application (http://gmodconfig.sf.net/) uses libxml++. I record the dependency on libxml++ in my RPM spec file. But I actually could not find a recent libxml++ RPM around :-) (what's on rpmfind.net is a bit old). So my users that go for the RPM have to install libxml++ manually and then install my app by calling rpm with --nodeps. I'd prefer to avoid this, and instead have users just grab the proper libxml++ RPM, as my app is likely to be installed by non-experienced users. Regards, Cyril |
|
From: Paul M. <P_M...@bi...> - 2003-04-07 12:44:43
|
Hi, Been using libxml++ on a Linux platform - very nice! I'll be porting my app to NT soon, so I was wondering if there any plans to port libxml++ to win32? Cheers, Paul |
|
From: Andrea V. <na...@ho...> - 2003-04-02 10:02:12
|
Hello to everyone. I've cleared up all problems I had with compiling libxml++ on Solaris. Indeed it was an installation problem, an older version of Libxml2 installed by default that got dynamically linked with libxml++. Setting the proper env-variables and recompiling was enough to get the whole lot working. Thanks for anyone who helped. Is there any need for compiled Solaris binaries ? I've also investigated the possibility of using the Forte compiler and unfortunately it's not installed in the set machines I can use. Bye, Andrea |
|
From: Jonathan W. <co...@co...> - 2003-04-01 22:15:44
|
Hi all, I raised something on the patch manager at sourceforge, and as I'll be offline until sunday and won't be able to dig deeper I wanted to raise it here and see if anyone knows the right answer. http://sourceforge.net/tracker/index.php?func=detail&aid=708826&group_id=12999&atid=312999 Basically I'm not sure the on_get_entity() callback I added to SaxParser is doing the right thing. As I'd been overriding this function in my code I'd not thought about the default case carefully enough, but I think just doing a lookup with xmlGetPredefinedEntity() is wrong. I think it should return NULL, so that libxml2 will fall back to doing the lookup (or maybe something else if it changes in future). The relevant libxml code is xmlParseEntityRef() in parser.c line 5800 When I'm back I'll look further, jon |
|
From: <ne...@mi...> - 2003-03-29 19:23:41
|
<HTML> <HEAD> <TITLE>Jacado Breaking News - March 30, 2003</TITLE> </HEAD> <BODY> <TABLE WIDTH=580> <TR> <TD> <table><tr><td>Please click <a href=http://www.jacado.com/news/200303/20030330_JACADO_BREAKING_NEWS.html target=_blank>here</a> if you can't read this email.</td></tr></table> <BR> <A HREF=http://www.jacado.com/product.jsp?team=jacado&code=1504&title=Gambling+Games TARGET=_blank> <IMG SRC=http://www.zindell.com/postcards/BlackJack.gif BORDER=0></A> <BR><BR><font size=2><a href=http://www.jacado.com/product.jsp?team=jacado&code=1504&title=Gambling+Games target=_blank>BlackJack</a> was developed by <a href=http://www.jacado.com target=_blank>jacado</a>. Please click <a href=http://www.jacado.com/product.jsp?team=jacado&code=1504&title=Gambling+Games target=_blank>here</a> for more info about this fantastic gambling game. If you find this game interesting, we suggest you to check some of our other magnificent gambling games such as <a HREF=http://www.jacado.com/product.jsp?team=jacado&code=1500&title=Gambling+Games target=_blank>ClassicRoulette</a>. <BR> <BR> <FONT SIZE=-2>This email was sent by Jacado news service. Please click <a href=http://www.jacado.com/remove.jsp?type=jacado target=_blank>here</a> if you wish to unsubscribe or visit at http://www.jacado.com/remove.jsp?type=jacado.</FONT> </TD> </TR> </TABLE> </body> </html> |
|
From: <ne...@mi...> - 2003-03-27 15:24:30
|
<HTML><HEAD><STYLE>
BODY {font-family="Arial"}
TT {font-family="Courier New"}
BLOCKQUOTE.CITE {padding-left:0.5em; margin-left:0; margin-right:0; margin-top:0; margin-bottom:0; border-left:"solid 2";}
SPAN.TABOOHEADER {display=none}
</STYLE></HEAD>
<BODY>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 9">
<meta name=Originator content="Microsoft Word 9">
<link rel=File-List href="cid:filelist.xml@01C26494.79C3D5D0">
<link rel=Edit-Time-Data href="cid:editdata.mso@01C26494.79C3D5D0">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Jacado Games & Fun for Mobile Telephones Newsletter</title>
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:EnvelopeVis/>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{
panose-1:2 11 5 0 0 0 0 0 0 0;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0pt;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;
text-underline:single;}
p
{margin-right:0pt;
mso-margin-top-alt:auto;
mso-margin-bottom-alt:auto;
margin-left:0pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1027"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1"/>
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-GB link=blue vlink=blue style='tab-interval:36.0pt'>
Please click <a href=http://www.jacado.com/news/200303/200303_JACADO_NEWS.html TARGET=_blank>here</a> if you can't read this newsletter. <P><P>
<a name="top"></a>
<div class=Section1>
<table border=0 cellpadding=0 width=611 style='width:458.25pt;mso-cellspacing:
1.5pt;mso-padding-alt:0pt 0pt 0pt 0pt'>
<tr>
<td width=607 style='width:455.6pt;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <img
width=604 height=76 id="_x0000_i1025"
src="http://www.zindell.com/images/jacadologonews.gif"></span></font></p>
<table border=0 cellpadding=0 width="100%" style='width:100.0%;mso-cellspacing:
1.5pt'>
<tr>
<td width="73%" style='width:73.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><b><font size=4 color="#000000" face=Arial><span
style='font-size:13.5pt;font-family:Arial;color:#000000;font-weight:bold'>Jacado Games & Fun for Mobile Telephones</span></font></b><a name=top></a></p>
</td>
<td width="27%" style='width:27.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><b><font size=4
color="#000000" face=Arial><span style='font-size:13.5pt;font-family:Arial;
color:#000000;font-weight:bold'>March 2003</span></font></b></p>
</td>
</tr>
</table>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<table border=0 cellpadding=0 width="100%" style='width:100.0%;mso-cellspacing:
1.5pt'>
<tr>
<td style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=12 color="#FF9900" face=Arial><span
style='font-size:13.5pt;font-family:Arial;color:#FF9900'>In this issue</span></font></p>
</td>
</tr>
</table>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;display:none;mso-hide:all'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></p>
<table border=0 cellpadding=0 width="100%" style='width:100.0%;mso-cellspacing:
1.5pt;mso-padding-alt:0pt 0pt 0pt 0pt'>
<tr>
<td width="2%" style='width:2.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>-</span></font></p>
</td>
<td width="98%" style='width:98.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=2 face=Arial color="#FF9900"><span style='font-size:10.0pt;
font-family:Arial'><a href="#a">Terraplay Systems and Jacado to Work on Multiplayer Games</a></span></font></p>
</td>
</tr>
<tr>
<td width="2%" style='width:2.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:
Arial'>-</span></font></p>
</td>
<td width="98%" style='width:98.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto'><font size=2 face=Arial color="#FF9900"><span style='font-size:10.0pt;font-family:
Arial'><a href="#b">Catching the Dragon in 42 Steps when Playing at Level 5</a></span></font></p>
</td>
</tr>
<tr>
<td width="2%" style='width:2.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:
Arial'>-</span></font></p>
</td>
<td width="98%" style='width:98.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto'><font size=2 face=Arial color="#FF9900"><span style='font-size:10.0pt;font-family:
Arial'><a href="#c">Jacado to Release New Color Versions for its Puzzle Games</a></span></font></p>
</td>
</tr>
</table>
<a name=temporary></a>
<p class=MsoNormal><span style='mso-bookmark:temporary'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p></o:p></span></font></span></p>
</td>
<span style='mso-bookmark:temporary'></span>
</tr>
<tr><td> </td></tr><tr><td> </td></tr>
<tr>
<td width=607 style='width:455.6pt;padding:.75pt .75pt .75pt .75pt'>
<p><p><font size=4 color="#FF9900" face=Arial><span style='font-size:13.5pt;
font-family:Arial;color:#FF9900'>Terraplay Systems and Jacado to Work on Multiplayer Games</span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><a name="a">
</p>Terraplay Systems, a spin out from Ericsson Radio Systems, are cooperating with Jacado to produce multiplayer titles for supply to operators worldwide. The Terraplay Systems allows real time interactive games to be created quickly. A range of titles can be run through a single server making the provisioning of such games far simper, and thereby increasing margin. The Jacado titles Blast'Em and Space Battle are currently being offered to service providers. Jeremy Hamill-Keays, Content Director at Terraplay said,"We are extremely happy to be working with Jacado to bring their wealth of highly attractive content to operators and users around the world".
<P><font size=2><a href="#top">Back to top</a> <a href="http://www.terraplay.com/" target="_blank">More...</a></font><BR> <BR></span></font></p>
</td>
</tr>
<tr><td> </td></tr>
<tr>
<td width=607 style='width:455.6pt;padding:.75pt .75pt .75pt .75pt'>
<p><p><font size=4 color="#FF9900" face=Arial><span style='font-size:13.5pt;
font-family:Arial;color:#FF9900'>Catching the Dragon in 42 Steps when Playing at Level 5</span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><a name="b">
</p>Adar Shani, a computer science student from Shenkar college (Israel), a <a href=http://www.jacado.com/product.jsp?team=jacado&code=1115&title=Board+Games target="_blank">Dragon</a> professional gamer, has succeeded to catch the dragon in 42 steps when playing at level 5. In his short article, Adar presents the required steps to catch the dragon in 42 steps (when playing at level 5). For more info about this awesome game we recommend you to visit at <A href=http://www.DragonConnexion.com TARGET="_blank">www.DragonConnexion.com</a>, the central web site for this game.
<P><font size=2><a href="#top">Back to top</a> <a href="http://www.dragonconnexion.com/articles/winninglevel5.htm" target="_blank">More...</a></font><BR> <BR></span></font></p>
</td>
</tr>
<tr><td> </td></tr>
<tr>
<td width=607 style='width:455.6pt;padding:.75pt .75pt .75pt .75pt'>
<p><p><font size=4 color="#FF9900" face=Arial><span style='font-size:13.5pt;
font-family:Arial;color:#FF9900'>Jacado to Release New Color Versions for its Puzzle Games</span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><a name="c"></a>
We are pleased to announce about new color versions for many of our well known puzzle games. These new versions were developed for Nokia 7650 utilizing its unique sound & graphics capabilities. Among these new versions you can find the following puzzles:
<a href=http://www.jacado.com/product.jsp?team=jacado&code=1132&title=Puzzle+Games#nokia7650Version TARGET=_blank>JokoSoko</a>,
<a href=http://www.jacado.com/product.jsp?team=jacado&code=1109&title=Puzzle+Games#nokia7650Version TARGET=_blank>JacadoIQ</a>,
<a href=http://www.jacado.com/product.jsp?team=jacado&code=1111&title=Puzzle+Games#nokia7650Version TARGET=_blank>MagicTable</a>,
<a href=http://www.jacado.com/product.jsp?team=jacado&code=1120&title=Puzzle+Games#nokia7650Version TARGET=_blank>JacadoTiles</a>,
<a href=http://www.jacado.com/product.jsp?team=jacado&code=1119&title=Puzzle+Games#nokia7650Version TARGET=_blank>JacadoJump</a>,
<a href=http://www.jacado.com/product.jsp?team=jacado&code=1121&title=Puzzle+Games#nokia7650Version TARGET=_blank>JacadoThink</a> and others.
<P><font size=2><a href="#top">Back to top</a> <a href="http://www.jacado.com/page.jsp?team=jacado&topic=puzzles" target="_blank">More...</a></font><BR> <BR></span></font></p>
<FONT SIZE=-2>This email was sent by Jacado news service. Please click <a href=http://www.jacado.com/remove.jsp?type=jacado target=_blank>here</a> if you wish to unsubscribe.</FONT>
</td>
</tr>
</table>
</div>
</body>
</html>
|
|
From: <ne...@mi...> - 2003-03-24 20:53:54
|
<HTML> <HEAD> <TITLE>Jacado Breaking News - March 25, 2003</TITLE> </HEAD> <BODY> <TABLE WIDTH=580> <TR> <TD> <table><tr><td>Please click <a href=http://www.jacado.com/news/200303/20030325_JACADO_BREAKING_NEWS.html target=_blank>here</a> if you can't read this email.</td></tr></table> <BR> <A HREF=http://www.jacado.com/product.jsp?team=jacado&code=1700&title=Sport+Games TARGET=_blank> <IMG SRC=http://www.zindell.com/postcards/Darts.gif BORDER=0></A> <BR><BR><font size=2><a href=http://www.jacado.com/product.jsp?team=jacado&code=1700&title=Sport+Games target=_blank>Darts</a> was developed by <a href=http://www.jacado.com target=_blank>jacado</a>. Please click <a href=http://www.jacado.com/product.jsp?team=jacado&code=1700&title=Sport+Games target=_blank>here</a> for more info about this fantastic game. If you find this game interesting, we suggest you to check some of our other magnificent games: <a HREF=http://www.jacado.com/product.jsp?team=jacado&code=1021&title=Arcade+Games target=_blank>Python</a>, <a href=http://www.jacado.com/product.jsp?team=jacado&code=1019&title=Arcade+Games target=_blank>SpaceInvasion</a> and <a href=http://www.jacado.com/product.jsp?team=jacado&code=1012&title=Arcade+Games target=_blank>DucksHunting</a>. <BR> <BR> <FONT SIZE=-2>This email was sent by Jacado news service. Please click <a href=http://www.jacado.com/remove.jsp?type=jacado target=_blank>here</a> if you wish to unsubscribe or visit at http://www.jacado.com/remove.jsp?type=jacado.</FONT> </TD> </TR> </TABLE> </body> </html> |
|
From: SourceForge.net <no...@so...> - 2003-03-24 14:44:52
|
Patches item #708826, was opened at 2003-03-24 14:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=708826&group_id=12999 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jonathan Wakely (redi) Assigned to: Nobody/Anonymous (nobody) Summary: Use std::string for SaxParser::on_get_entity() arg Initial Comment: This patch makes the SaxParser::on_get_entity() take a std::string argument, to hide the fact that an xmlChar* is used internally by the library and to be consistent with the other SaxParser virtual functions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312999&aid=708826&group_id=12999 |
|
From: Andrea V. <ma...@ho...> - 2003-03-21 08:14:17
|
Hello. I'm currently developing a C++ projects that needs XML and I've found Libxml++ very useful. Unfortunately, I can't get the library to work properly under Solaris. I've tried both Solaris under Sparc and X86 - same fate. The exact configuration of the Sparc machine is: SunOS 5.9 Generic_112233-02 sun4u sparc . The compiler is GCC 3.2 or 3.2.2 (for the X86 machine). The compilation goes perfectly, but the library example "dom_parser" crashes with a segfault. I did some investigations and it turns out that, in DomParser::get_root_node() root->_private is zero! I've tried both 0.21 and 0.22, no luck. All the other parser and creation examples work without trouble. My project, also using the DomParser crashes just like dom_parser. Does anyone know the cure ? Has anyone ever successfully run xmlpp::DomParser under Solaris ? Thanks for any help! Andrea. |
|
From: Jonathan W. <co...@co...> - 2003-03-20 15:52:59
|
On Thu, Mar 20, 2003 at 03:32:10PM +0000, Jonathan Wakely wrote:
> libxml++.a would contain node.o, built from node.cc, which includes
> the node.tcc and node.h headers.
>
> Users would include node.h for the common string types, and if they want
> to use a string type not supported directly they'd have to include
> node.tcc to see the bodies of the functions.
Forgot this bit, this would be a user's code, which would link to the
library containing the explicit instantiations.
----------------------------
#include "tmpl.h"
int main()
{
xmlpp::qt::Node qnode;
qnode.makeSomeNoise();
}
---------------------------
jon
|
|
From: Jonathan W. <co...@co...> - 2003-03-20 15:41:28
|
On Thu, Mar 20, 2003 at 09:44:20AM -0500, Stefan Seefeld wrote:
> >- -------
> >
> >template<typename String_t>
> >class Node { // or maybe BaseNode
> > public:
> > String_t get_content();
> >}
> >
> >namespace qt {
> > typedef xmlpp::Node<QString> Node;
> >}
> >
> >namespace glib {
> > typedef xmlpp::Node<Glib::ustring> Node;
> >}
>
> This will instantiate the actual types, and thus require the full
> template code to be seen. That's what Murray objects to. In order
> to hide the templates you really have to use compiler firewalls
> ('pimpls'), which requires more than a 'typedef': it requires
> real wrapper classes. (you can't forward declare a typedef...).
Nothing will get instantiated by this, typedefs only introduce a new
name for a type, they don't instatiate anything. As long as the
template had been forward declared before the typedef it would be ok.
In the code below (which compiles if I replace the two string types with
std::string, I don't have the QString or glib::ustring headers here to
test it) the typedefs are given before seeing the body of the Node
template.
--------------------------
// node.h
// declares typedefs for common string types and defines class interface
// included by users who want to use Node<T>, qt::Node or glib::Node
#include <glibmm/ustring.h> // or whatever the right header is
#include <qt/qstring.h> // or whatever the right header is
namespace xmlpp {
template<typename StringT> class Node; // fwd decl of template
namespace qt {
typedef Node<QString> Node; // typedef without seeing template
}
namespace glib {
typedef Node<glib::ustring> Node; // another typedef
}
// now give template definition, but no function definitions
template<typename StringT>
class Node {
public:
Node();
void makeSomeNoise() const;
};
}
--------------------------
--------------------------
// node.tcc
// template definitions for xmlpp::Node<StringT>
// Only included by users for "uncommon" string types,
// otherwise only used in lib
#include "node.h"
#include <iostream>
template <typename StringT>
xmlpp::Node<StringT>::Node()
{
}
template <typename StringT>
void
xmlpp::Node<StringT>::makeSomeNoise() const
{
std::cerr << "RAAAAA!\n";
}
--------------------------
--------------------------
// node.cc
// explicit instantiations of template with common string types
// never seen by users, compiled in lib
#include "node.tcc"
template class xmlpp::Node<::QString>;
template class xmlpp::Node<::glib::String>;
--------------------------
libxml++.a would contain node.o, built from node.cc, which includes
the node.tcc and node.h headers.
Users would include node.h for the common string types, and if they want
to use a string type not supported directly they'd have to include
node.tcc to see the bodies of the functions.
I'm not proposing this as the way to go, (there are still the issues of
introducing deps on the two string types, and of binary-incompatible
libs if they use different string types), I'm just trying to clear up what
seem to be some misunderstandings about the language features.
jon
--
"UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing clever things."
- Doug Gwyn
|
949 messages has been excluded from this view by a project administrator.
![http://www.zindell.com/images/jacadologonews.gif"></span></font></p>](http://www.zindell.com/images/jacadologonews.gif"></span></font></p>){kind=link}
