Okay, curious.
What exactly does not work with the corrected newsfeed.ini or what error is output in the LOG?
With me the feed runs WITHOUT error in the LOG. Only the time manipulation problem is still there
Okay, curious.
Please pack the config and upload it. I think would be easiest way to get the working skin.Youkai1977 wrote: ↑April 3rd, 2021, 12:51 pm Okay, curious.
What exactly does not work with the corrected newsfeed.ini or what error is output in the LOG?
With me the feed runs WITHOUT error in the LOG. Only the time manipulation problem is still there
Ok, here the NewsFeedReader als rmskin-Package.
Alright, now got it working.
Mhh, I think we're talking past each other here.
The website, in the <lastBuildDate>(.*)</lastBuildDate> tag is returning the date and time of the load (when have you accessed the content of the site). You can easily see what am I talking about if you load the content of the site into your browser, then try to refresh manually a few times, one after the other, following the date and time contained in the lastBuildDate tag. You can see you get the results with a difference of just a few seconds. So this tag is returning the date of access of the site. This is approximately the local date and time, there might be differences of a few seconds only.Youkai1977 wrote: ↑April 4th, 2021, 5:52 pm And the other measure [mLBTSF], should ONLY format the read <lastBuilddate> (Index1) of the [mRSS] measure from (example): Sun, 04 April 2021 19:20:20 GMT to --> 04.04.2021 19:20:20 <---.
And the latter does NOT work. Because here then the minutes and seconds of the real time, for whatever reason, are taken over.
ARRRRGGGHHH ...oh man, right, now I see it too.You can easily see what am I talking about if you load the content of the site into your browser, then try to refresh manually a few times...
Yeah, indeed makes not too much sense, but that's it.Youkai1977 wrote: ↑April 5th, 2021, 8:35 am ARRRRGGGHHH ...oh man, right, now I see it too.
Man ne, I thought the <lastBuildDate> was the timestamp where Google News was updated altogether. I noticed that when you are on the website, about every 20-30 minutes (haven't checked exactly yet) a message appears at the bottom left of the Screen that there is an updated version and if you want to update.
Therefore, as I said, the assumption that this is the <lastBuildDate>.
But now that you have found out that this is only the timestamp when I or the [mRSS] Measure has accessed the page, this is for me all ad absurdum.
No, it's not a big deal at all. It can be done extremely easily. Here is an example:Youkai1977 wrote: ↑April 5th, 2021, 8:35 am And now for each feed to take the <PupDate> I find exaggerated ... or in other words, this is like shooting with cannons on sparrows.
Code: Select all
[Variables]
...
NF1=.*<item.*<title.*>(.*)</title>.*<pubDate>(.*)</pubDate>
NF2=.*<title.*>(.*)</title>.*<pubDate>(.*)</pubDate>
NF3=.*<title.*>(.*)</title>.*<pubDate>(.*)</pubDate>
NF4=.*<title.*>(.*)</title>.*<pubDate>(.*)</pubDate>
NF5=.*<title.*>(.*)</title>.*<pubDate>(.*)</pubDate>
Code: Select all
[mRSSItem1]
...
StringIndex=3
...
[mRSSItem2]
...
StringIndex=5
...
[mRSSItem3]
...
StringIndex=7
...
[mRSSItem4]
...
StringIndex=9
...
[mRSSItem5]
...
StringIndex=11
...
Code: Select all
[mRSSDate1]
Measure=WEBPARSER
URL=[mRSS]
StringIndex=4
Disabled=1
Group=mCHILDS
[mRSSDate2]
Measure=WEBPARSER
URL=[mRSS]
StringIndex=6
Disabled=1
Group=mCHILDS
[mRSSDate3]
Measure=WEBPARSER
URL=[mRSS]
StringIndex=8
Disabled=1
Group=mCHILDS
[mRSSDate4]
Measure=WEBPARSER
URL=[mRSS]
StringIndex=10
Disabled=1
Group=mCHILDS
[mRSSDate5]
Measure=WEBPARSER
URL=[mRSS]
StringIndex=12
Disabled=1
Group=mCHILDS
No, I don't get this. The only different colored character is the | itself. See my screenshot (click it to enlarge): Another comment related to the code: I definitely would move the included newsfeeddata.inc file into the @Resources folder (which doesn't yet exist but can easilly be created). This folder has been added exactly to store such resources, included files and so on.Youkai1977 wrote: ↑April 5th, 2021, 8:35 am Then still something to my COLOR PROBLEM (InlineSettings).
I found out that if special characters occur in the feed, I then have this color play. So a feed is COLORFUL (multicolored), or in WHITE instead of e.g. blue.
If a feed has e.g. the character | in it, the coloring breaks off at that point, and AFTER the | character the feed has a different color.
If the feed contains the characters +++ three times in a row, the feed is COLORFUL.
So your solution from the other day to put a (?iu) in front of my [mRSSItem] seems either NOT to be enough, or not quite the correct way to do it.
That's why I've completely removed it from my NewsFeed skin now.
Oh man you are crazy. It's meant nicely and I thank you for the example, but I think it will be too much of a good thing, if I now also add this to the skin.No, it's not a big deal at all. It can be done extremely easily. Here is an example:
Yes as I said, possibly in a different skin. From these I probably leave it out for now[*]Additional Time measures might be needed, to get the appropriate format for dates / times. Don't post the for now, hope you can add them if you want.[/list]
Now you have to use the acquired dates somehow, to add them to string meters or whatever. I leave this for you, add them where you like them.
Correct, if the special character | is in a feed, it will NOT be colored. But I also experience that AFTER the special character | the text is NOT colored anymore or OTHER.No, I don't get this. The only different colored character is the | itself.
Mhh, ok I don't really understand why I should do that. I find a lot of skins on the net that have a *.inc file always in the order of the respective skin.Another comment related to the code: I definitely would move the included newsfeeddata.inc file into the @Resources folder (which doesn't yet exist but can easilly be created). This folder has been added exactly to store such resources, included files and so on.
No, I don't think, but it's your choice.Youkai1977 wrote: ↑April 6th, 2021, 9:39 am Oh man you are crazy. It's meant nicely and I thank you for the example, but I think it will be too much of a good thing, if I now also add this to the skin.
I will keep your example for later times, but in my current skin there I leave it out rather. That is otherwise too much, if I stuff for each feed now also still the PupDate with purely.
Nevertheless, many many thanks for it :rosegift:Yes as I said, possibly in a different skin. From these I probably leave it out for now
Ok, please do so. Couldn't discover this coloring problem so far, however I'm not running the skin continuously.Youkai1977 wrote: ↑April 6th, 2021, 9:39 am Correct, if the special character | is in a feed, it will NOT be colored. But I also experience that AFTER the special character | the text is NOT colored anymore or OTHER.
Likewise if the special characters +++ are used in a feed, I have color problems.
So something is definitely wrong.
I am currently already thinking about whether I make a separate meter for each feed to avoid the InlineSetting problem.
Currently there is no feed running with the mentioned special characters, so I could present you a screenshot of what I mean. But as soon as one comes, submit such a screenshot
No, you don't have to put them in the @Resources folder. It was just an idea, which I always apply. But the skin does perfectly work in the existing format as well. Keep the .inc file near the main .ini file, if you like more it this way.Youkai1977 wrote: ↑April 6th, 2021, 9:39 am Mhh, ok I don't really understand why I should do that. I find a lot of skins on the net that have a *.inc file always in the order of the respective skin.
Therefore, I think the thing with the @Resources folder will have its sense and purpose. But I don't understand why I should put my *.inc. files in there.