Themeing about feed-on-feeds HOT 6 CLOSED

What do you mean by theming? Thylacine has put in some stuff for changing the header style (fancy, simple, etc.) and other than that most things could be handled by changing the fof-custom.css file.

IMO, FoF should be kept simple.

from feed-on-feeds.

Well, I would like a mobile interface. That might be more interesting than just another look.

from feed-on-feeds.

There's already a mobile interface - mobile.php. It's pretty minimal but it does the job.

On Oct 14, 2013, at 2:10 PM, Stefan Misch [email protected] wrote:

Well, I would like a mobile interface. That might be more interesting than just another look.

—
Reply to this email directly or view it on GitHub.

http://beesbuzz.biz/
http://sockpuppet.us/

from feed-on-feeds.

@iantearle
As far as themes go -- while I don't personally feel there's a huge need to completely modularize the rendering components -- there are only so many ways to display a list of items, after all -- an effort to separate the current mess of html generation into a proper presentation layer could conceivably make the whole system more maintainable, and then different layouts would be a low-cost extra.
That said, I'd also prefer not to see such happen if it involved grafting on some big templating framework, or the like. I use FoF mostly because it's so succinct and frill-less.

@plaidfluff
Well, let's be fair, the current minimal mobile interface is nigh on useless for any of us with even one high-volume subscription. :) (Though the addition of a feed-selection panel would, at least, make it usable..)

from feed-on-feeds.

I do have a sort of abstract wishlist item of wanting to just make
an API layer, maybe one that's compatible with some existing
synchronization API (like Google Reader's or something, since a lot of
folks seem to still support that one), so that you can use something
like NetNewsWire or Flipboard or whatever as your presentation layer.
Why do a big hodgepodge of HTML-layout trainwrecks when you can just let
other apps handle the hard parts of making it work well in mobile?

On
2013-10-15 12:49, Justin Wind wrote:

@iantearle [1]
As far as
themes go -- while I don't personally feel there's a huge need to
completely modularize the rendering components -- there are only so many
ways to display a list of items, after all -- an effort to separate the
current mess of html generation into a proper presentation layer could
conceivably make the whole system more maintainable, and then different
layouts would be a low-cost extra.
That said, I'd also prefer not to
see such happen if it involved grafting on some big templating
framework, or the like. I use FoF mostly because it's so succinct and
frill-less.

@plaidfluff [2]
Well, let's be fair, the current
minimal mobile interface is nigh on useless for any of us with even one
high-volume subscription. :) (Though the addition of a feed-selection
panel would, at least, make it usable..)

Reply to this email
directly or view it on GitHub [3].

Links:

[1]
https://github.com/iantearle
[2] https://github.com/plaidfluff
[3]
#16 (comment)

from feed-on-feeds.

Closing because there are no updates for 5 years.

Concerning mobile use I recently made the UI responsive (starting with b3e45c6). Also all JS has been ported from prototype.js to vanilla javascript (from e1dc3a1), so there's no need for jQuery anymore either.

from feed-on-feeds.