Closed GoogleCodeExporter closed 9 years ago
Hi,
I just found out about the easy cloning-features on google-code. I actually
didn't know any clones of this existed.
The feature seems to be quite useful for people who can't or don't want to use
cron and I would like to merge it with the main repository. At the moment I am
changing a lot of stuff in the GUI-part of the app since I am trying to create
a multi-pane-layout for tablets or mobile phones with big screens which
involves a whole new way of structuring the Activity-classes.
Greetings,
nils
Original comment by nils.braden
on 23 Oct 2011 at 2:34
I just merged all changes for the lazyServer-feature up to revision
[https://code.google.com/r/leskets-ttrss-reader-for-lazy-server/source/detail?r=
ca143ae2a6815485f2ddeb3a9462362adea2d0e2 ca143ae2a681]. The things regarding
the injection of an article-link and automatic loading of the article if the
content is empty have been left out of this since I wanted to do one change at
a time. I also am not sure if the behaviour is appropriate so I would suggest
we open another Issue about this.
Sadly I currently cannot test this feature as the GUI-refactoring broke some
functionality and I have to fi this first.
Greetings,
nils
Original comment by nils.braden
on 23 Oct 2011 at 4:17
The cloning feature must be quite new. I started hacking with a read only
remote repository and changed to a clone and pushed the changes right before
posting this issue.
Please, use "hg transplant ..." to fetch patches from my tree, so that I can
easily see what you have applied.
In your merge (e2acbf15235d) one line from the "UsageOpenUrlEmptyArticle" patch
(51fae55744d3) slipped in:
if (Controller.getInstance().openUrlEmptyArticle() && lastMove == ARTICLE_MOVE_NONE) {
should be:
if (Controller.getInstance().openUrlEmptyArticle()) {
in order to keep the old behaviour.
Greetings,
Thomas
Original comment by lesk...@web.de
on 25 Oct 2011 at 7:53
Oh I didn't notice it was an unrelated change (reverted it with revision
16a038a73d06).
I also just merged the fix for the updateFeed-Bug
(http://tt-rss.org/redmine/issues/375) with "hg transplant.." which is quite a
useful tool now that I know about it. Thanks :)
Original comment by nils.braden
on 26 Oct 2011 at 1:20
Original comment by nils.braden
on 22 Nov 2011 at 7:35
Hi,
is this feature still working for you? I can't get it to work since my server
responds with "500: Internal Server Error" when I request the API-function
"updateFeed", no matter which feed-id I provide. It should return "OK" though
so with the next update I'll add a check for this return-value. If this breaks
the support for lazy-servers please let me know.
Thank you,
nils
Original comment by nils.braden
on 2 Jan 2012 at 12:21
Original issue reported on code.google.com by
lesk...@web.de
on 23 Oct 2011 at 1:18