Re: parsing data returned from the foundLine
Try: get the value of the foundline -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com That is definitely a step much closer. :) I usually keep the dictionary open as a reference while I'm working, but it certainly didn't help in this case. ...I think I'm gonna revisit *all* of the documentation covering chunking again before I go much further with this little project. It seems that I am still missing some of the concepts, methods and/or possibilities that Rev offers when it comes to parsing textual data. Thank you, Jacque! Regards, David C. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: parsing data returned from the foundLine
On Wed, Mar 3, 2010 at 1:43 PM, David Coker davidoco...@gmail.com wrote: ...I think I'm gonna revisit *all* of the documentation covering chunking again before I go much further with this little project. It seems that I am still missing some of the concepts, methods and/or possibilities that Rev offers when it comes to parsing textual data. David, are you sure you need to be going through the UI to do this? I mean, would it not be better to use something like 'filter' or 'matchText', or one of the variants of 'offset'? Bernard ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: parsing data returned from the foundLine
On Mar 3, 2010, at 6:43 AM, David Coker wrote: Try: get the value of the foundline That is definitely a step much closer. :) I usually keep the dictionary open as a reference while I'm working, but it certainly didn't help in this case. ...I think I'm gonna revisit *all* of the documentation covering chunking again before I go much further with this little project. It seems that I am still missing some of the concepts, methods and/or possibilities that Rev offers when it comes to parsing textual data. David, I have an overview of Rev's chunking, text parsing and find tokens at http://revolution.byu.edu/textfind/TextandFind.php . You may find it useful. Regards, Devin Devin Asay Humanities Technology and Research Support Center Brigham Young University ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: parsing data returned from the foundLine
David Coker wrote: ...I think I'm gonna revisit *all* of the documentation covering chunking again before I go much further with this little project. It seems that I am still missing some of the concepts, methods and/or possibilities that Rev offers when it comes to parsing textual data. Chunking is such an integral part of Rev that a good understanding is essential. But actually, what you needed to do probably isn't under the text chunking category. The problem was that the foundline returns a reference to a line, and what you wanted was the text of that line. That means we have to force Rev to evaluate the reference, which is what the value function was made to do. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: parsing data returned from the foundLine
I thank you all for the info and suggestions! ...this little project has a bunch of twists and turns due to the amount and depth of recursion involved, but I've got a pretty good portion of it figured out now. This one has been in one stage of development or another for 2-3 months now... I do a bit on it and then set it aside for awhile when I tire of it. We'll get there eventually. (maybe) I do appreciate you good folks! David C. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: parsing data returned from the foundLine
David Coker wrote: Hello folks, I have a small 3 column list (tab delimited) where I need to check the contents for duplicate data that may be found in any of two fields or columns, then act on the line that contains that data if found. As an example, in my handler I'm using: find ABC-5678-A in tData put the foundLine into tLineFound answer tLineFound which correctly returns something like: line 2 of field 2 I've tried -several- different ways to parse the returned data for additional processing, but have yet to come up with the right solution. I know this must be extremely easy to do in Rev (there always is, it seems like), but I've run out of hair to pull in trying to figure out what I'm overlooking. Any ideas or maybe a better approach that can be recommended? Try: get the value of the foundline -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
