You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(6) |
Jul
(21) |
Aug
(40) |
Sep
(7) |
Oct
(41) |
Nov
(52) |
Dec
(19) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(49) |
Feb
(37) |
Mar
(84) |
Apr
(11) |
May
(29) |
Jun
(9) |
Jul
(19) |
Aug
(9) |
Sep
(6) |
Oct
(5) |
Nov
(15) |
Dec
(3) |
2008 |
Jan
(7) |
Feb
(11) |
Mar
(25) |
Apr
(50) |
May
(7) |
Jun
(8) |
Jul
(10) |
Aug
(18) |
Sep
(1) |
Oct
(15) |
Nov
(1) |
Dec
(9) |
2009 |
Jan
(5) |
Feb
(2) |
Mar
(3) |
Apr
(5) |
May
(10) |
Jun
(4) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(15) |
Nov
(13) |
Dec
(6) |
2010 |
Jan
|
Feb
(3) |
Mar
(4) |
Apr
(6) |
May
|
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2011 |
Jan
(19) |
Feb
(39) |
Mar
(28) |
Apr
(6) |
May
(7) |
Jun
(9) |
Jul
|
Aug
(1) |
Sep
|
Oct
(8) |
Nov
(3) |
Dec
(12) |
2012 |
Jan
(2) |
Feb
(1) |
Mar
(3) |
Apr
(4) |
May
(4) |
Jun
(3) |
Jul
(10) |
Aug
(2) |
Sep
(13) |
Oct
(24) |
Nov
(3) |
Dec
(1) |
2013 |
Jan
(11) |
Feb
(5) |
Mar
(4) |
Apr
(3) |
May
(3) |
Jun
(5) |
Jul
(7) |
Aug
(16) |
Sep
|
Oct
(7) |
Nov
(11) |
Dec
|
2014 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
(3) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
(11) |
May
(8) |
Jun
(3) |
Jul
(1) |
Aug
(3) |
Sep
(5) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
2016 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
|
Jul
(4) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2019 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: tony y. <gao...@gm...> - 2006-07-30 13:18:56
|
I don't think the push() and pop() pairs can really resolve my problem. As previous example shows, I need remember all children positions(indexes). if I invoke many times push(), when pop() from stack who knows which child pop up? Remember the DOM reference all node it parsed. As for VTD-XML, it need to be condidered the similar feature. -- Kindly Regards Tony =============================== |
From: Jimmy Z. <cra...@co...> - 2006-07-30 07:33:58
|
There is a global stack that you can access. Since it is a stack it is = first-in last out, so you can push in a node then pop it back out... vn.push(); // save the location ....// do what ever you want, such as navigation vn.pop(); // instantly restore cursor to the saved location... Have you tried the demo on the sourceforge web page? it seems to do what = you have described ... ----- Original Message -----=20 From: tony yin=20 To: vtd...@li...=20 Cc: vtd...@li...=20 Sent: Sunday, July 30, 2006 12:15 AM Subject: Re: [Vtd-xml-users] Need more arbitrary random access Well. For example: <root> <child>AAA</child> <child>BBB</child> <child>CCC</child> ... </root> When processing XML doc in DOM I can reserve every node references in = my code and exactly retrieve the 2nd "<child>" node back at anytime I = wanted, there is no need to traverse. That's the point I want to be done = in VTD-XML Model if I can save the 2nd "<child>" token's index in my = code. The necessary situation is, I generate a tree in my UI from an XML = and I want mouse click linking to correct node and display information = of that node.=20 Sounds reasonable? --=20 Kindly Regards Tony = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=20 -------------------------------------------------------------------------= ----- = -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to = share your opinions on IT & business topics through brief surveys -- and earn = cash = http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV -------------------------------------------------------------------------= ----- _______________________________________________ Vtd-xml-users mailing list Vtd...@li... https://lists.sourceforge.net/lists/listinfo/vtd-xml-users |
From: tony y. <gao...@gm...> - 2006-07-30 07:15:50
|
Well. For example: <root> <child>AAA</child> <child>BBB</child> <child>CCC</child> ... </root> When processing XML doc in DOM I can reserve every node references in my code and exactly retrieve the 2nd "<child>" node back at anytime I wanted, there is no need to traverse. That's the point I want to be done in VTD-XML Model if I can save the 2nd "<child>" token's index in my code. The necessary situation is, I generate a tree in my UI from an XML and I want mouse click linking to correct node and display information of that node. Sounds reasonable? -- Kindly Regards Tony =============================== |
From: Jimmy Z. <cra...@co...> - 2006-07-29 17:26:54
|
The navigation has to be based on some criteria (such as specificied in = an XPath expression). VTD navigator uses an array of integers to represent a particular = location in XML, "getCurrentIndex" only returns one those integers in the array... What would be the equivalent function calls in DOM that does what you = described?? ----- Original Message -----=20 From: tony yin=20 To: vtd...@li...=20 Sent: Saturday, July 29, 2006 8:20 AM Subject: [Vtd-xml-users] Need more arbitrary random access Hi all: I know the VTD-XML is based on some kind of cursor navigation. But I = searched all API docs and can't find how to random access the token I = wanted. Just a method: if (vn.toElement(VTDNav.NEXT_CHILD,"*")) {=20 //any action } I think it's not good enough to process my xml. I need another method = to achieve this: method(){ ancestorTokenIndex =3D vn.getCurrentIndex(); } ... foo(){ vn.toIndex(ancestorTokenIndex); int t =3D vn.getText(); String text =3D vn.toNormalizedString(t) ; ... } Why I need more arbitrary random access? I just need it. And I think = it's easy to implement because VTD-xml design concept, isn't it?=20 --=20 Kindly Regards Tony = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=20 -------------------------------------------------------------------------= ----- = -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to = share your opinions on IT & business topics through brief surveys -- and earn = cash = http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV -------------------------------------------------------------------------= ----- _______________________________________________ Vtd-xml-users mailing list Vtd...@li... https://lists.sourceforge.net/lists/listinfo/vtd-xml-users |
From: tony y. <gao...@gm...> - 2006-07-29 15:24:12
|
Hi all: I know the VTD-XML is based on some kind of cursor navigation. But I searched all API docs and can't find how to random access the token I wanted. Just a method: if (vn.toElement(VTDNav.NEXT_CHILD,"*")) { //any action } I think it's not good enough to process my xml. I need another method to achieve this: method(){ ancestorTokenIndex = vn.getCurrentIndex(); } ... foo(){ vn.toIndex(ancestorTokenIndex); int t = vn.getText(); String text = vn.toNormalizedString(t) ; ... } Why I need more arbitrary random access? I just need it. And I think it's easy to implement because VTD-xml design concept, isn't it? -- Kindly Regards Tony =============================== |
From: Jimmy Z. <cra...@co...> - 2006-06-14 06:50:26
|
Similar issues have been raised before, yes we are still thinking about = that...=20 original design goal is to keep as much complexity out of the = implementation as possible, the problem of=20 multiple context object is that once we give people more than one = cursor, people will want even more,=20 potentially making position tracking difficult ... the goal is KISS, = keep it simple and stupid... regarding LC entry, yes, there is a way, but requires hacking on your = side, also for nodes that goes beyond depth 4, linear scan is used to locate child nodes... so the best/simplest way is to wrap around vn.toElement(FIRST_CHILD).... it will take care of everything...=20 ----- Original Message -----=20 From: Aakash Jain=20 To: Jimmy Zhang=20 Sent: Tuesday, June 13, 2006 11:28 PM Subject: Re: multiple context objects In place of providing multiple context object, it can provide context = save and load methods. Currently it provides push and pop methods that = operate on VTD's stack only. But the user cannot save and load the = context in his defined stack or some other array.=20 Regarding the hasChild() problem: The lower 32 bits in LC entry contains -1 if there is no child of a = node. Is there a way to access that entry. Because this will be a = straight forward check to know if the node has child or not.=20 --=20 Aakash Jain PUCSD Ph : 91 9844223652=20 " There are 10 types of people in this world, those who understand = binary and others who don't. " On 6/14/06, Jimmy Zhang <cra...@co...> wrote: Sorry for the late reply... right now VTD-XML doesn't implement multiple context object, because = a context object is a global variable so you can use it across procedures... = and we have yet to come across a scenario where multiple context object is needed...=20 the best way to check whether a node has child or not is navigate to = it and check the result value... if (vn.toElement(VTDNav.FC) =3D=3D false) {// no child } else { vn.toElement (VTDNav.P); // return to the orginal node // has child... } let me know if there is any further question... |
From: Jimmy Z. <cra...@co...> - 2006-06-14 06:44:14
|
Yes, but vn.getCurrentIndex() will get you the index value of the cursor = element... ----- Original Message -----=20 From: Aakash Jain=20 To: Jimmy Zhang=20 Sent: Tuesday, June 13, 2006 11:36 PM Subject: Re: find attribute value by index getRootIndex() returns the inddex of the root element of the xml tree. eg: <root> <child attr1=3D"val1"/> <child attr1=3D"val2"/> </root> so, no matter where your context object is , it will always return = index for "root".=20 On 6/14/06, Jimmy Zhang <cra...@co...> wrote: It can be done let me give an example.. The XML snippet is as follows: <test attr1=3D'val1' attr2 =3D 'val2' /> vn.getRootIndex() will get you the index value of "test" element, = which is root....=20 say its index is 1; then next few tokens attr1 ---> index value is 2 val1 =3D=3D>index value is 3 attr2 ----> index is 4 val2 =3D=3D> index value is 5 make sure you check for the token type at the given index values=20 using vn.getTokenType(int i).. possible token types are ATTR_VAL, ATTR_NAME, ATTR_NS (for = namespace) >How can we find an attribute's value by number? >Like we have VTDNav.getAttrValue(String)=20 >but that gives the value given the key. >What if i dont know the key? >Help!!!!!!!!!!!!!! --=20 " There are 10 types of people in this world, those who understand = binary and others who don't. "=20 Aakash Jain PUCSD Ph : 91 9844223652 |
From: Jimmy Z. <cra...@co...> - 2006-06-14 06:41:59
|
VTD-XML's XML content exchange is at the byte level, which is different = from DOM. VTD-XML allows you to update the individulal token value, or cut away a = chunk... there is going to be an article called "cut, paste, split and assemble = XML with VTD-XML" coming out next month in Javaworld that will dig into those features.... |
From: Jimmy Z. <cra...@co...> - 2006-06-14 06:30:34
|
It can be done let me give an example.. The XML snippet is as follows: <test attr1=3D'val1' attr2 =3D 'val2' /> vn.getRootIndex() will get you the index value of "test" element, which = is=20 root.... say its index is 1; then next few tokens attr1 ---> index value is 2 val1 =3D=3D>index value is 3 attr2 ----> index is 4 val2 =3D=3D> index value is 5 make sure you check for the token type at the given index values using vn.getTokenType(int i).. possible token types are ATTR_VAL, ATTR_NAME, ATTR_NS (for namespace) >How can we find an attribute's value by number? >Like we have VTDNav.getAttrValue(String) >but that gives the value given the key. >What if i dont know the key? >Help!!!!!!!!!!!!!! |
From: Jimmy Z. <cra...@co...> - 2006-06-14 06:29:23
|
Sorry for the late reply... right now VTD-XML doesn't implement multiple context object, because a=20 context object is a global variable so you can use it across procedures... and = we=20 have yet to come across a scenario where multiple context object is needed... the best way to check whether a node has child or not is navigate to it = and=20 check the result value... if (vn.toElement(VTDNav.FC) =3D=3D false) {// no child } else { vn.toElement(VTDNav.P); // return to the orginal node // has child... } let me know if there is any further question... |
From: Sun Z. <zhi...@gm...> - 2006-06-07 20:39:19
|
Hello everyone Node Operation Question, How To Insert , Delete , Update Node with VTD-XML? |
From: Aakash J. <aak...@gm...> - 2006-05-24 16:34:14
|
How can we find an attribute's value by number? Like we have VTDNav.getAttrValue(String) but that gives the value given the key. What if i dont know the key? Help!!!!!!!!!!!!!! --=20 " There are 10 types of people in this world, those who understand binary and others who don't. " Aakash Jain PUCSD Ph : 91 9844223652 |
From: Aakash J. <aak...@gm...> - 2006-05-22 16:11:18
|
Can we have multiple context objects in VTD? As we can have multiple nodes in a DOM parse tree? Also is there a way to check whether an element has some children. One possible way is: vn.toElement(VTDNav.FC) but this changes the current context is there some function like hasChild() --=20 " There are 10 types of people in this world, those who understand binary and others who don't. " Aakash Jain PUCSD Ph : 91 9844223652 |