09:38:26 <dimaip> I need a piece of strategic advice. I really enjoy using fluidpages and fluidcontent, but what do I do about more general record-like content? A lot of content on my site changes with time, like announcements, blog posts, list of events etc. Before, I used to base such kind of records on EXT:news, and would either extend EXT:news with custom fields
09:38:26 <dimaip> (takes long time), or stuff my data into unused EXT:news' fields (quick but ugly).
09:39:26 <dimaip> No I had an idea of adding flux field to EXT:news (just like fluidpages and fluidcontent do for pages and tt_content)...
09:40:23 <dimaip> Do you think it sounds as a good idea? Will I be able to use real EXT:news' fields alongside with flux's fields?
09:42:25 <dimaip> Or maybe start a completely new extension, call it fluidrecord, which would have sections for teaser and full view, some simple controller & repo, etc
16:37:54 <NamelessCoder> I assume this involves some info about paths on each system... I can provide info about Mac but haven't got a clue where the files would be on linux/win
16:38:13 <georg_t> did you also try to autoload the viewhelpers via xmlns (without {namespace flux=...})?