07:56:02 <Torsten85> hey, I've added flux / fluid content to my typo3 v7 instance and all is working as expected except drag & drop in the page module. I guess flux is not yet fully compatible or is it a bug?
08:36:47 <jmverges> I'm taking a look to: should I do a PR and change: https://github.com/FluidTYPO3/flux/blob/development/Classes/Hooks/WizardItemsHookSubscriber.php#L265 ?
08:36:52 <Torsten85> yeah, but that part is working right noch as it should
11:18:23 <jmverges> xaver, what do you mean when you say additional containers ?
12:27:03 <jmverges> NamelessCoder, what do you think about https://github.com/FluidTYPO3/fluidcontent/issues/222 ?
12:37:59 <NamelessCoder> jmverges I think you need a bit of discipline with your git commands my friend ;)
12:40:07 <jmverges> I'm still trying to understand the approach 0_
12:40:08 <NamelessCoder> I don't mean to preach, but the formal stuff is as important as the functional stuff. They don't work well separately but together they make clarity and consistency.
12:40:59 <jmverges> you are right, then, if I open an issue, and then I want to do a PR that resolve it, what should I do?
12:43:33 <NamelessCoder> almost exactly what you did, but the commit message should be something like this: https://fluidtypo3.org/documentation/contributing/contribution-guide.html#creating-a-pull-request
12:44:48 <jmverges> [FEATURE] Made VHS more awesome
12:44:48 <jmverges> This change makes VHS more awesome by increasing the
12:45:04 <NamelessCoder> basically, the commit message must explain what's being changed so you know without reading the diff. It's great to create issues first - but to reference it, use "Fixes: #123" or "Close: #123" or whatever. GitHub detects pretty much all of them.
12:46:10 <jmverges> okey, maybe the next time I get it. At least this time I didn't get the robot saying things like "all is wrong" it is because is turning off or because I did it partially fine?
12:46:13 <NamelessCoder> in this case though I had to take this opportunity to really clean up the affected class
12:46:35 <NamelessCoder> and I don't expect you as a contributor to have to do that first, then apply your change - so I hijacked it ;)
12:47:00 <NamelessCoder> yeah it's temporarily disabled because of noise
12:47:36 <NamelessCoder> the very best recommendation is to clone the repository, run composer install from the extension root and then use ./vendor/bin/make to install git hooks that validate everything *before* the commit is created
12:47:57 <NamelessCoder> as described in https://fluidtypo3.org/documentation/contributing/contribution-guide.html#initialising-the-repository
12:48:34 <NamelessCoder> if you do that, you'll make 100% sure you don't commit anything that breaks code and violates the rules we've included so far (it is not 100% complete regarding CGL check, but it is close)
12:49:16 <NamelessCoder> last note for IRC - you really should create separate branches when you create new features, less of a headache if something has to be changed
12:49:35 <NamelessCoder> the guide describes every single step and consideration - but it is a bit long ;)
12:50:49 <NamelessCoder> we'll be just as happy as you if your next contributions just race directly through that review step - win/win ;)
12:51:54 <jmverges> your code is much cleaner, I just try to do little changes by now, once that I get the approach correct I will try to suggest crazier things. At least I'm happy because the task are included so I just need to practice and practice, just please, have patience with me in the meantime. I started to feel that I'm going to be fired from my current job so I will have a lot of time to contribute :)
12:54:02 <NamelessCoder> Practice and more practice is precisely what it takes :)
15:54:56 <jmverges> I'm following the contribution guide step by step, let's see if I'm able to do a PR for https://github.com/FluidTYPO3/fluidcontent_core/issues/135 without any problems
15:55:57 <NamelessCoder> I'm here if you need feedback
16:27:48 <jmverges> it is taking a while doing composer install almost 10 minutes with - Installing typo3/cms (6.2.10) Downloading: 100%
16:28:06 <NamelessCoder> is is craaaaazy slow, yes :(
16:28:34 <NamelessCoder> first time. Next time, also if you do it for other ft3 exts, it will get it from cache and should be much faster.
16:33:06 <jmverges> Great, let's see if it finish. I was reading https://github.com/FluidTYPO3/fluidcontent_core/issues/35 all the thread is interesting I'm thinking about if it is really necesary to use FCC, I mean, FCC is much more better than CSC however, if we are able to have as many fluidcontents as we like, what is the point of FCC? could be posible just to remove all default CTypes and just work with Fluidcontent? I was thinking about it for some time and this is th
16:33:06 <jmverges> e reason because today I was looking about allowedContentTypes information
16:34:21 <NamelessCoder> the point is to preserve those core types - text, image, media etc.
16:34:42 <NamelessCoder> many third-party extensions will for example index these differently, will restrict allowed content types and much more
16:35:45 <NamelessCoder> the other aspect is that the native CTypes are all able to be protected/granted via user group permissions - that is not true for fluidcontent elements unless such restrictions are manually made possible in (just as example) page TS config for each user group.
16:36:28 <NamelessCoder> but you are correct that they are extremely similar (on purpose hehe) except for the CType/tx_fed_fcefile situation
16:37:26 <jmverges> what about extend the group permissions to include the different Fluidcontent in the list of group permissions? too mad?
16:37:38 <NamelessCoder> from what I hear, TYPO3 7.2 will be rendering content using FLUIDTEMPLATE cObject which is a huge improvement already. When/if that happens, the only remaining reason to use FCC is the ability to use a custom controller - the rest will be possible in core.
16:37:48 <NamelessCoder> I don't think that's possible
16:38:13 <NamelessCoder> afaik no hooks exist at that point and it is unfeasible to generate the (fake) TCA it would require
16:38:57 <NamelessCoder> pageTSconfig can still remove/add elements if you set it on a user, a usergroup or at system level - it's not super user friendly, but it works
16:39:37 <NamelessCoder> there's a lot of that going around in the core btw. Some incredibly powerful features hidden away like royal gems :)
16:41:39 <jmverges> good to know, however versions and variations are part of FCC and that is nice
16:42:35 <NamelessCoder> that part is true of course
16:43:12 <NamelessCoder> arguably, one could get the same result in plain core (when it starts using extbase/fluid to render core elements) by way of an added TCA field and TS conditions
16:45:02 <NamelessCoder> but even when the core switches FCC will still have a place. We'll simply make it transparently use or at least be able to switch to the same configurations the core uses
16:45:10 <jmverges> Today I was taking a look to some WP Page Builder ( https://siteorigin.com/page-builder/ ) I don't like WP I think that it is a insult for the profession but I have to recognize that it has a lot of themes and this page builders are getting a lot of popularity so it is hard for me to defend TYPO3 when I talk with non developers
16:45:20 <NamelessCoder> so you get the whole provider, flux forms etc. without having to add it manually in TCA etc.
16:47:47 <jmverges> do you plan or do you know if anyone is doing something as visual as that WP Page Builder? I really feel sick talking about WP but the UX of that video is great
16:49:07 <NamelessCoder> it's a very, very deep topic...
16:49:25 <NamelessCoder> yes, it would be nice to have something like that to build pages or just structure page templates' grids etc.
16:49:37 <NamelessCoder> but it is an extremely big task
16:50:24 <NamelessCoder> afaik nobody is working on that (it pretty much amounts to completely recreating the TYPO3 page module - excluding the record editing module)
16:51:42 <NamelessCoder> mention the words FormEngine and ContentObjectRenderer and people usually flee
16:52:33 <jmverges> if you want to preserve all the TYPO3 functionality could be huge, but I think that mapping with Extbase pages and tt_content and some angular stuff could do the trick (at least, something to show to the community, a "mockup")
16:53:22 <NamelessCoder> it's the iceberg beneath the surface that's the problem
16:54:32 <NamelessCoder> there are SO many things you can manipulate with settings about how those interfaces behave. It's good to be brave but in this case, you'd probably end up with something that supports 10% of the original features and to add the remaining 90% would be close to impossible
16:55:25 <NamelessCoder> part of the problem here is that the original, underlying code in typo3 isn't written with modern design patterns in mind - and it is that code that everyone depends on (even Extbase depends on it)
16:56:18 <NamelessCoder> btw it was a discussion like this one that caused Neos to be invented in the first place ;)
16:57:00 <jmverges> yes, you probably are right, but there are beast developers (like you) that maybe could be amazed seeing a drag and drop page builder in admin and some real FE editing and then who knows
16:57:17 <jmverges> but Neos it is completely different to TYPO3, I love TYPO3
16:57:35 <NamelessCoder> the problem is not inspiration, it is time
16:58:14 <NamelessCoder> pay any one of those developers and they'd gladly create it - take Flow for example
16:58:47 <NamelessCoder> but it wouldn't have been created if there wasn't any money in it. The people with the skills to create it have no need to use it - they just grab the internals.
17:00:01 <jmverges> time and money :) all is related with it
17:01:24 <jmverges> no problem it is good to have someone putting my feet on the ground
17:02:30 <NamelessCoder> even so: we might not be able to change the whole thing, but we can make the smaller parts much better
17:03:20 <jmverges> I think that I'm going to be fired from my job, I have never been getting money from the state, but, if I got fired, I want to spend my time with TYPO3 and FluidTYPO3
17:04:33 <NamelessCoder> I've been sacked three times
17:04:57 <NamelessCoder> you get back up and next time, kick more ass ;)
17:05:41 <jmverges> but, you know, small company ugly code without templates just php html and js in .php, no phpstorm, no vagrant, no xdebug, no nginx, no scrum, ... I'm introducing all this and TYPO3
17:06:21 <jmverges> and it is too hard, because the developers don't want to learn anything and are just trying to arguee and complain
17:08:04 <jmverges> and as you know, I don't know as much as other developers arround but at least I'm on the right way (I think)
17:10:48 <jmverges> NamelessCoder, why were you fired? you are the fucking boss arround ;)
17:14:06 <NamelessCoder> once when I was 21 because I didn't want to work the way they wanted, then when I was 28 because they couldn't afford me any longer and then in 2013 because there wasn't enough work and money.
17:14:27 <NamelessCoder> no popcorn drama, sorry :p
17:15:04 <NamelessCoder> if you want to grow btw, you need to find a place where people are already better than you
17:15:24 <NamelessCoder> otherwise you'll be growing them and you probably shouldn't be taking that responsibility so soon
17:26:13 <jmverges> yes, I know it, but they "sell me" the job and the company as fantastic and is not that. The last two years I was working in a bigger company an I learned about PSR-2, git, jira, jenkins, etc the bad point was that we were using private code so, all was in the mind of the architect and, for sure is a good developer, but is not a team player and he doesn't know about a lot of things related with javascript or FE in genral, he stole part of my code and he
17:26:13 <jmverges> said that it was his code and then I started to feel more and more burn out and then I left the company. I could get a better payed job in a casino online company (they needed a TYPO3 guy for do all the integration) and I refused it because I don't like the casino stuff, I meet some people that lost all their things with poker and other games. So, I finished here and workmates don't want to learn anything, this is the worse part, 0 ilusion 0 iniciative.
17:27:05 <jmverges> My 30th birthday was the last sunday
17:32:00 <jmverges> well, dinner time, my fiance started to be angry with me. See you later or tomorrow.
18:05:19 <NamelessCoder> that PR is *perfect* jmverges - but I think we might be able to nip this problem deeper at the source so it never even reaches the list of content one can insert
18:05:36 <NamelessCoder> that however is a matter of ancient TS :/
18:08:50 <jmverges> lol, at least the PR is well done. The contribution guide is good, I saw one issue, I will try to do a PR tomorrow to the contribution guide and I will do it right. ;) now, its time, my fiance is more and more angry XD See you latter
18:09:53 <NamelessCoder> formals of that PR is absolutely perfect