Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 3 hrs, 5 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 4 days, 23 hrs ago - more...
|
2010-04-12
, 20:29
|
|
Posts: 7 |
Thanked: 3 times |
Joined on Apr 2010
|
#242
|
Originally Posted by Slocan
I tried, but no messages....
Can you try to open the X-Terminal, and then typing:
FeedingIt
(case sensitive), to start the application. Do the update, and see if there are any messages that appear in the terminal. Thanks.
|
|
2010-04-12
, 21:52
|
|
Posts: 180 |
Thanked: 41 times |
Joined on Mar 2007
@ Maine
|
#243
|
Slocan-
Thanks, I will try and leave it running to see how it works. I like the widget.
Fred
Thanks, I will try and leave it running to see how it works. I like the widget.
Fred
|
|
2010-04-12
, 22:14
|
|
Posts: 324 |
Thanked: 371 times |
Joined on Dec 2009
@ Vancouver, BC
|
#244
|
Originally Posted by cisqo
Can you please download this to your device (save it to MyDocs for example):
I tried, but no messages....
http://feedingit.marcoz.org/test2.py
then connect to your mobile internet, open up the X-Term and type:
python MyDocs/test2.py
and send me the output to my email slocan @AT@ marcoz .DOT. org
Thanks.
|
|
2010-04-13
, 05:17
|
|
Posts: 324 |
Thanked: 371 times |
Joined on Dec 2009
@ Vancouver, BC
|
#245
|
@dcell: I just uploaded 0.6.0-1 to extras-devel. It should fix the problem you're having with that feed.
The other main change is that the widget will now update its display as soon as the count changes in the app (either through an update, or when you close a feed after reading some articles).
The other main change is that the widget will now update its display as soon as the count changes in the app (either through an update, or when you close a feed after reading some articles).
|
|
2010-04-13
, 05:57
|
|
Posts: 42 |
Thanked: 6 times |
Joined on Nov 2009
|
#246
|
when app is running auto update works. i first thought autoupdate worked when app is closed, which is not the case apparently.
 |
|
2010-04-13
, 06:27
|
|
Posts: 290 |
Thanked: 165 times |
Joined on Sep 2009
|
#247
|
i see we have a loading indicator now, great! thx!
about auto update, can the widget not trigger that instead of the app so that the app doesnt need to be open? of does feedingit had a command lin argument that we can de the update through alarmd?
about auto update, can the widget not trigger that instead of the app so that the app doesnt need to be open? of does feedingit had a command lin argument that we can de the update through alarmd?
|
|
2010-04-13
, 13:55
|
|
Posts: 180 |
Thanked: 41 times |
Joined on Mar 2007
@ Maine
|
#248
|
Originally Posted by jcompagner
I have been using alarmed with the following command: 'FeedingIt update' which opens an instance of the application and then does the update. What I would like is for a way to close the instance after the update has occurred. I am not a UNIX expert so I have not been able to figure out how to kill the python process that is started by FeedingIt from a script that I would invoke from Alarmed ten minutes later or something like that.
i see we have a loading indicator now, great! thx!
about auto update, can the widget not trigger that instead of the app so that the app doesnt need to be open? of does feedingit had a command lin argument that we can de the update through alarmd?
Any ideas?
Fred
|
|
2010-04-13
, 17:06
|
|
Posts: 324 |
Thanked: 371 times |
Joined on Dec 2009
@ Vancouver, BC
|
#249
|
Originally Posted by ffarber
As you mentioned, you could kill the process, but I really wouldn't recommend that. I'll add something so the app can be closed easily (probably sometime before the week-end).
What I would like is for a way to close the instance after the update has occurred.
Any ideas?
Ultimately, now that the widget is getting somewhere, I want to create a way to update the feeds without having to open the full app, that would be triggered by the app, the widget, or an external command (and if it works out, maybe regulated by a status icon, a-la MfE sync, but let's not get carried away).
| The Following User Says Thank You to Slocan For This Useful Post: | ||
|
|
2010-04-13
, 18:14
|
|
Posts: 180 |
Thanked: 41 times |
Joined on Mar 2007
@ Maine
|
#250
|
Originally Posted by Slocan
Very cool, I will be patient!
As you mentioned, you could kill the process, but I really wouldn't recommend that. I'll add something so the app can be closed easily (probably sometime before the week-end).
Ultimately, now that the widget is getting somewhere, I want to create a way to update the feeds without having to open the full app, that would be triggered by the app, the widget, or an external command (and if it works out, maybe regulated by a status icon, a-la MfE sync, but let's not get carried away).
Thanks,
Fred
P.S. I have edited this in after thinking about it. Wouldn't the easiest thing to do be adding a new command line argument that was essentially 'update and exit'? That way people could use Alarmed to set up the update to happen on any schedule they would like. This would open the full app for a period of time which would only be annoying if you were doing something else at that time. Just an idea.
Last edited by ffarber; 2010-04-13 at 19:08.
| The Following User Says Thank You to ffarber For This Useful Post: | ||
@ffarber: the widget is a very early preview that I uploaded to extras-devel yesterday, so it doesn't really interact or do much yet (it only updates its display every 30 minutes). Double-clicking on a feed name will launch the app too.
But otherwise, the app is self-contained, so it needs to be running for the auto-update of feeds to happen. This might change in the future.