10:25:37 <opk> I'm trying to use vhs in flux and I can't get current CE
10:26:10 <opk> {v:content.info(contentUid: 7347, field:'sys_language_uid')} works
10:26:16 <opk> {v:content.info(field:'sys_language_uid')} does not
10:28:51 <NamelessCoder> opk if you're in a content template and have correctly transferred the variable, {record} is available and contains {record.uid} which you can feed to various content viewhelpers
10:43:48 <opk> maybe you could help with the displayCond problem.
10:45:29 <opk> I can't get it to work displayCond="{v:content.info(field:'sys_language_uid',contentUid:'{record.uid}')} == 0" or displayCond="FIELD:sys_language_uid:<=:0"
10:54:16 <NamelessCoder> if you need a very complex condition (note: arrays are now supported as displayCond in TCA) you can still <f:if> around the Flux component you want to condition
10:54:47 <opk> i'm truing to hide field's for translation
10:55:56 <NamelessCoder> displayCond should work for that but I'm not sure about the syntax given that this is in a flexform context - please check the almighty core TCA docs ;)
11:08:30 <NamelessCoder> well you can use VHS to define the string that becomes the displaycond - but the displaycond itself is treated by typo3 internally
11:08:53 <NamelessCoder> if you want to only rely on vhs, f:if around the field
17:14:32 <tv_sebastian> You're not allowed to use it within a flux:form
17:25:27 <NamelessCoder> you should be able, but may need arguments="{_all}" for everything to be appended correctly (or a new Form instance is created as ad-hoc parent Form in your partial and this Form can never be retrieved)
20:15:58 <Jomungand> just read your article regarding phoenix/nes @NamlesCoder
20:25:38 <Jomungand> thx for the hard work btw :-)
20:26:08 <NamelessCoder> Alex Schnitzler has the completely correct point: viewing neos/flow as experimental and R&D makes so much sense - it's what I touch in my letter about "taking the lessons learned from Neos and applying them to TYPO3" to paraphrase
20:26:55 <Jomungand> cutting of the weak parts and focus on one strong thing, too
20:26:56 <NamelessCoder> heh, you're welcome :) I was mostly proving a point about the decoupling having been drawn out needlessly for a long, long time. All it takes is willingness to sacrifice some of the TYPO3-ness about Fluid.
20:27:29 <NamelessCoder> I even did it once before - but that time, in a much less refined way
20:29:48 <NamelessCoder> are you from the US Jomungand? You're always on late and your English is good enough that I'd guess it ;)
20:39:20 <opk1> NamelessCoder > There was a way in templavoila to disable TOC fields from translation . Is there some way for flux/extbase for enabling inheritance for fields?
20:40:47 <opk1> ie. monitor in store. Different description in different languages but the same diagonal in all of them
20:41:15 <NamelessCoder> still undocumented, but see recent addition for flux:form option "translation"
20:41:48 <NamelessCoder> I can't decouple Fluid, write a FAL driver *AND* Flux 7.2 release notes on the same weekend :p
20:42:33 <Jomungand> if there is something i could do to improve the documantation, let me know. got some free time on my hand
20:43:48 <opk1> i must say that fluidtypo3 is the best thing that happen to typo3 since the sliced bread :)
20:44:25 <NamelessCoder> Jomungand be VERY VERY careful what you offer ;)