just a short question. Is there technically a chance to find out if the RSS feed download is finished?
I don't mean this from the GUI. I think about a flag in an INI-file or a field entry in a table in feeds.db.
For sure a flag that QuiteRSS is currently downloading would help as well.
Thanks in advance!
I received your letter and could not immediately respond to forum because I had a little vacation
Unfortunately, there is no flag, but may be implemented.
No problem! I hope you had a good time during your vacation!
A flag would be great. I would appreciate it in an INI-File and not in the db. That would be easier to grab.
If this is to complicated to implement easily or quickly as a first step
something like "QuiteRSS - Downloading news" showing up in the main window title would be already helpful.
That would be easy to grab! This would not need to much inplementation!
What do you think about this?
I can add a line with the flag in the file debug.log. As you look at this?
Oh that's pobably not so good! This would appear there several times then. Right?
That would make it hard to find the current one because it's not neccessarily the last entry in the log.
Something like a download status in QuiteRSS.ini f.e. would be easier to find.
Or as I suggested something like "QuiteRSS - Downloading news" in the main window title.
The window title I can grab easily. From my perpective and for my needs that would be perfect.
What I want to achieve is that I simply can wait until QuiteRSS has finished its' downloads and start my process.
If you f.e. put it to the window title I could loop until the download news phrase is no longer in the window title.
That would also not irritate or annoy the other users.
What's your opinion?
Ah! if you worry to irritate the other users by putting a phrase to the window title you could also create a simple empty text file named downloading.txt f.e. in the directory that holds the database feeds.db if the download starts. If the download is done you would delete this file. So it would exist only temporary during the downloading process. In this case I could simply check for the exisitance of this file.
I'll add a flag in ini-file.
If I will have reading rights to the INI-file while QuiteRSS is running this is fine.
Ah! By the way. A flag that shows that the QuiteRSS shutdown is finished would be helpful as well.
Currently you show a window that tells the user that the data gets saved.
Maybe the flag you want to implement can be a status holding values like:
- downloading feeds
- saving database from memory
and so on. So it can be used for many different situations.
What's your opinoin?
If I implement execution of a command when the upgrade is complete news feeds? For example, run an external program or a bat-file. http://quiterss.org/en/node/180
I think it would be useful to many, not only for you.
Hi, ah, I see! So we have two possible perspectives on this topic.
Once there is what I would call the internal perspective there you react on an internal run-time status of QuiteRSS (f.e. "update done") and start an external process (f.e. exe, bat and so on). That would be a great feature that I guess also many other users would appreciate. If it fits to your development planning you should definitely implement it.
But this doesn't cover the whole picture. In the internal scenario the external process is triggered by QuiteRSS. This is a restriction. There is also a external perpective on the topic. If I f.e. want to schedule an external procees depending on QuiteRSS data it would be neccessary to look up the QuiteRSS run-time status and react on it. So f.e. the external process should not start before the QuiteRSS data has been updated.
But I think this two perpectives could be covered by introducing a status concept. Internally you have to lookup this status somehow anyway. So you would start the external process if the internal status "update done" is reached. If you would maintain this status in the INI-file f.e. an external process would be able to fetch it and react on it. So both perpectives could be satisfied. And maybe this status concept can be useful for further QuiteRSS development, too. You could f.e. allow to run external processes by QuiteRSS depending on the status not only on "update done".
I think as a first step writing the current status to the INI-file would be enough. Further uses of this can follow later depending on the requirements.
What's your opinion? Kind regards,
I just do not implement the functions of a personal issue and the features that you only need one person.
Even this issue will not soon made since the issue only one person (marked with one star): https://code.google.com/p/quite-rss/issues/detail?id=481
What about the status entry in the INI-File?
See above. You can use this resource to create a issue: https://code.google.com/p/quite-rss/issues/list
I don't have a Google account and honestly I don't want one.
Can you create this issue for me please?
I totally understand that you don't want to implement functions only required by a small group of users.
That's the right way. Otherwise you get lost.
But what about a compromise for the first step.
Currently you show a progress bar if the update is running.
Adding the text "Updating news" to the QuiteRSS window title while the update is running should not be a big deal.
That would help already.
Is this possible?
I added an option in the ini-file: updatingFeeds - can be true or false.
Thank you very much! Can you already say when it will be available?
Did you find the time to create the issue for the stuff we discussed?
New version will be available later this month.
I just updated QuiteRSS from PortableApps to version 0.16.0 and found the flag "updatingFeeds". in the INI-file.
Great! Thanks a lot for the implementation!