02:03:07 <Outdoorsman> I don't really know how it would work conditionally because there's no option on every image to checkbox "responsive" so it would work with twitter bootstrap.
02:04:47 <Outdoorsman> Maybe randomresult has already thought about this?
02:11:29 <Outdoorsman> On a different but somewhat related note, there's the issue of not being able to use FAL with images that is talked about here https://github.com/FluidTYPO3/flux/issues/468 and here https://github.com/FluidTYPO3/flux/issues/175
11:15:43 <jlumpe> morning! I'm encoutering a weird issue: after creating some content elements with fluidcontent, when I add nested content elements to them, they aren't added in the correct order and sometimes are removed from the content element and moved to the root of the page. Has anybody encountered this issue before?
12:49:47 <soee> guys when can we expect stable version of fluidboostrapteme ?
12:53:54 <NamelessCoder> if you want to help that along, soee, assist Danilo with testing and reporting on https://github.com/FluidTYPO3/flux/pull/524 - until that is done, no Flux TER and until that happens, no fluidbootstraptheme
12:55:22 <jlumpe> NamelessCoder: are you aware of an issue which leads to fluidcontent elements not being properly nested?
12:55:43 <jlumpe> for example when copying them around
12:55:47 <soee> NamelessCoder: will take a closer llook, thanks
12:55:53 <NamelessCoder> jlumpe see same issue I just linked to
13:10:54 <jlumpe> thanks so much. getting back into typo3 atm. any way i can help with things maybe? (might also help me to understance fluidtypo3 better)
13:13:07 <NamelessCoder> there might be - are you comfortable with php in general?
13:13:46 <NamelessCoder> we have https://github.com/FluidTYPO3/vhs/pull/545 which is fairly simple work but time consuming
13:14:08 <jlumpe> of course there is always room for improvement, but yeah i can read and write php
13:14:38 <NamelessCoder> making pull requests into vhs's branch workbench/namespaces will add your commits to this one - if you do start refactoring some classes, please write in the issue comments which ones you're handling so we don't do double
13:17:07 <NamelessCoder> basically the process is: 1) add the namespace in php class, 2) rename class, 3) if used by other classes, correct references, 4) in ClassAliasMap.php, find the entry and reverse the map so the new name points to the old
13:51:15 <NamelessCoder> in unix commands it would be, after you have a commit and then made code changes you wan to amend: "git commit --amend -a" then "git push --force" to force update your remote branch
13:51:24 <NamelessCoder> sourcetree is probably the best option for windows yes
13:52:29 <NamelessCoder> it's about the same procedure - in sourcetree you would add the changed file, commit and toggle on amend - then force-push to remote exactly like in cli
13:53:00 <jlumpe> ok i will try, if i fail i can still delete my branch and start over
13:53:10 <jlumpe> oh and is there any way to run the unit tests without a full typo3 install?
13:53:20 <NamelessCoder> for *this* pull request it is not so important that you amend, since it will all be squashed later - but this is the exception ;)
13:53:50 <NamelessCoder> unfortunately no - there is not. Fluid ViewHelpers require the base class from Fluid and Extbase's object manager and class registry :/
13:54:23 <NamelessCoder> but you can create your pull request now - that way, your commits will be tested by travis when you push to your own remote branch
13:54:51 <jlumpe> yeah that is much more comfortable
13:54:52 <NamelessCoder> or you can simply sign into travis.org yourself and toggle on the vhs repository to have your very own builds running ;)
13:57:09 <jlumpe> I'll just have one big pull req in the end, is that fine?
13:57:32 <NamelessCoder> we will be more people working on this so we would like it in smaller chunks
14:11:36 <jlumpe> Then I can just keep doing stuff
14:12:09 <NamelessCoder> oh misunderstood: as long as it is NOT merged you can keep pushing. When merged, commits get picked. If you then recreate the PR after adding more commits, the comparison base will be renewed and only your new commits get added
14:12:59 <NamelessCoder> you should also "git remote add upstream https://github.com/FluidTYPO3/vhs.git"
14:13:19 <NamelessCoder> that way you can get the changes we make, using "git pull upstream workbench/namespaces --rebase"
14:15:58 <NamelessCoder> just to make sure (you're probably already doing this) do a search on the old class name after renaming. The only result should be in ClassAliasMap.php
14:16:58 <NamelessCoder> now you can try that rebase thing
14:20:54 <bjo3rn> hi guys. what's the policy re: fqn and use again? I see mostly fqns in recent commits.
14:21:46 <NamelessCoder> bjo3rn it's a two-step operation: until *our* classes also use namespaces, we keep the FQN. When we use namespaces, we start importing FQN by use instead
14:22:07 <NamelessCoder> the reason being bad results if "use" is mixed with a non-namespace class file
14:26:35 <jlumpe> NamelessCoder: is there a reason (i assume there is) why you wrote \FluidTYPO3\Vhs\Utility\ViewHelperUtility in most classes when updating the viewhelperutility to namespaces insteaf of doing use \FluidTYPO3\Vhs\Utility\ViewHelperUtility and then just ViewHelperUtility?
14:27:01 <NamelessCoder> jlumpe I just wrote the explanation to bjo3rn ;)
14:27:24 <bjo3rn> hehe, welcome to the club jlumpe ;)
14:27:25 <NamelessCoder> after you make the switch to namespaces in each class, importing the FQN by "use" is next
14:55:16 <jlumpe> NamelessCoder: started doing the math viewhelpers. Question: I started updating the abstract classes now (and all their references). now i also need to update the unit tests. I'll have to update all the extends as well. is that fine in a single commit?
14:56:20 <NamelessCoder> it's a lot of code but yes, a single commit is fine
15:03:55 <bjo3rn> ok guys, unit tests left to do. need to do something else now but will finish the rest later (just for the record and to avoid redundancy). cya later.