jsmorley wrote: ↑March 15th, 2019, 2:29 pmOf course as usual, I have no idea what you are trying to accomplish.
Yes, I know, I'm an enigma to you, but can't say I dislike that though.
My goal is trying to load the links of the visited feed items from an external file - nothing fancy. As explained in my previous reply, I'm successfully doing it using WebParser measures to parse the local file where I store those links, and I was looking for alternatives that would minimize the amount of memory used to store those strings (i.e. avoid them being stored twice, basically).
The file looks something like (I write into it using
!WriteKeyValue, but I currently read from it using WebParser, not an
@Include):
Code: Select all
; Stores the links of up to (Feed Limit x Feed Limit) visited feeds, in order to change the Feeds skin's title color based on the feed's read status.
; VisitedLinkIndex (initially -1) is the index of the last written visited link, and it endlessly cycles between 0 and (Feed Limit x Feed Limit - 1).
[Variables]
VisitedLinkIndex=0
VisitedLink0=https://www.cnn.com/2019/03/14/europe/jan-kuciak-murder-marian-kocner-ordered-killing-intl/index.html
VisitedLink1=https://www.cnn.com/collections/intl-ethiopian-airlines-crash/
VisitedLink2=https://www.cnn.com/2019/03/14/us/winter-storm-blizzard-thursday-wxc/index.html
Because I have to do either a WebParser
RegExp (or an
IfMatch in the measure, if I wouldn't use WebParser) to check if the link of the current feed item is present in the list from the file, the visited link strings have to be "stored" in a measure (so that I can attach those options to it). The problem is that both WebParser and "loading" the strings using variables create "duplicates", as all or a part of those strings are stored in
both the WebParser parent and the corresponding child(ren), or in
both the variable and the measure that I assign that variable to in its
String option.
This is why I tried this unorthodox approach of loading an entire String measure
directly in an @Include, bypassing the need to have an "intermediary" (like a variable, a WebParser parent, etc). Hopefully this make things more clear now...
jsmorley wrote: ↑March 15th, 2019, 2:29 pmDid you trying something like...
That leads to pretty much having the included content stored twice, as explained above.
