37881[FEATURE] Introduce System Information dropdown item
Commit message
Review
-
Code review CR +2
- Jigal van Hemert +2
- Markus Klein +1
-
Verified V +2
- Jigal van Hemert +2
- Markus Klein +1
- Frank Nägler +1
Issues 1
Files 19
- typo3/sysext/backend/Classes/Backend/ToolbarItems/AbstractToolbarItem.php7new+49 −0
- typo3/sysext/backend/Classes/Backend/ToolbarItems/SystemInformationToolbarItem.php6new+322 −0
- typo3/sysext/backend/Classes/Toolbar/Enumeration/InformationStatus.php1new+64 −0
- typo3/sysext/backend/Resources/Private/Language/locallang.xlf3+10 −0
- typo3/sysext/backend/Resources/Private/Templates/ToolbarMenu/SystemInformation.html1new+32 −0
- typo3/sysext/backend/Resources/Public/JavaScript/Toolbar/SystemInformationMenu.js1new+42 −0
- typo3/sysext/backend/ext_localconf.php+1 −0
- typo3/sysext/belog/Classes/Controller/SystemInformationController.php1new+71 −0
- typo3/sysext/belog/Resources/Private/Language/locallang.xlf1+3 −0
- typo3/sysext/belog/ext_localconf.php1new+12 −0
- typo3/sysext/core/Classes/Core/SystemEnvironmentBuilder.php7+29 −4
- typo3/sysext/core/Classes/Database/DatabaseConnection.php+9 −0
- typo3/sysext/core/Documentation/Changelog/master/Feature-65767-SystemInformationDropdown.rstnew+93 −0
- typo3/sysext/dbal/Classes/Database/DatabaseConnection.php1+22 −0
- typo3/sysext/lang/locallang_core.xlf2+18 −0
- typo3/sysext/t3skin/Resources/Private/Styles/TYPO3/_element_badges.lessnew+15 −0
- typo3/sysext/t3skin/Resources/Private/Styles/TYPO3/_topbar.less2+21 −0
- typo3/sysext/t3skin/Resources/Private/Styles/t3skin.less+1 −0
- typo3/sysext/t3skin/Resources/Public/Css/visual/t3skin.css+37 −0
Review log 36
Show 11 earlier messages
-
Andreas Kienast uploaded patch set 1 03/16/15, 13:52
-
Andreas Kienast updated the commit message in patch set 2 03/16/15, 13:52
-
Andreas Kienast uploaded patch set 3 03/16/15, 13:54
-
Andreas Kienast uploaded patch set 4 03/16/15, 14:00
-
Andreas Kienast uploaded patch set 5 03/16/15, 14:05
-
Markus Klein commented on patch set 4 03/16/15, 14:10
What I dislike a bit is that we have HTML code in the PHP code again. This means that other extensions will take this as example and will have the HTML in their ext as well. If we need to change the HTML these will break. I opt for a clear interface that only hands the information needed, but rendering should be done in Core only.SystemInformationToolbarItem.php:67StringUtility::endsWithSystemEnvironmentBuilder.php:56string[]SystemEnvironmentBuilder.php:499, TRUElocallang_core.xlf:1076GIT -
Andreas Kienast commented on patch set 4 03/16/15, 14:15
SystemInformationToolbarItem.php:67ReplyDoneSystemEnvironmentBuilder.php:56ReplyDoneSystemEnvironmentBuilder.php:499ReplyDonelocallang_core.xlf:1076ReplyDone -
Andreas Kienast uploaded patch set 6 03/16/15, 14:43
-
Andreas Kienast uploaded patch set 7 03/16/15, 15:29
-
Mathias Brodala commented on patch set 7 CR -1 03/16/15, 15:43
Generally +1 but yeah, passing around data to render would be cleaner instead of prepared HTML.SystemInformationHookInterface.php:35Please introduce an SystemInformationStatus enumeration for these instead. -
Andreas Kienast commented on patch set 7 03/16/15, 16:03
Is \TYPO3\CMS\Backend\Toolbar\Enumeration\SystemInformationStatusEnumeration alright to you?
-
Mathias Brodala commented on patch set 7 03/16/15, 16:05
No need for the "Enumeration" suffix but generally yes. -
Andreas Kienast uploaded patch set 8 03/16/15, 17:06
-
Andreas Kienast commented on patch set 8 03/16/15, 17:07
I made the approach more general by introducing an abstract class that has only the "addItem" method. If that goes in, we can adjust all other classes to use that method as well. -
Andreas Kienast uploaded patch set 9 03/16/15, 17:11
-
Frank Nägler commented on patch set 9 03/16/15, 20:07
works great, looks great, but I absolutely dislike the HTML code in PHP classes. Can we use a standalone view for the rendering? -
Benjamin Kott commented on patch set 9 03/16/15, 20:56
AbstractToolbarItem.php:35do we really need a link here? i think it should only display informations about the current systen._topbar.less:271we should not define a color here - please use the css classes for that -
Wouter Wolters commented on patch set 9 03/16/15, 21:00
AbstractToolbarItem.php:20useless imports here ;) -
Georg Ringer commented on patch set 9 V +1 03/16/15, 21:01
AbstractToolbarItem.php:54for me the link is leading to nowehre,... so why a link? -
Andreas Kienast commented on patch set 9 03/17/15, 06:57
AbstractToolbarItem.php:20Replycopy/paste is not good, mkay? ;)AbstractToolbarItem.php:35ReplyMy idea was to make a more general approach. I thought we can port all other menus to use "addItem()" then, having only one part that handles all the HTML stuff. The link would be required by Cache Menu, Open Docs, Workspaces etc.AbstractToolbarItem.php:54ReplyIt's more like a workaround here so have a consistent layout. I had some ideas what we can do with these "links", but that needs more brainstorming if it makes sense etc._topbar.less:271ReplyUnfortunately there is only the "badge" class in twbs. Should we introduce more global classes like "badge-success", "badge-danger" and so on? -
Andreas Kienast uploaded patch set 10 03/17/15, 14:47
-
Andreas Kienast uploaded patch set 11 03/17/15, 14:59
-
Andreas Kienast uploaded patch set 12 03/31/15, 05:51
-
Andreas Kienast commented on patch set 12 03/31/15, 05:52
rebased -
Markus Klein commented on patch set 12 CR -1 03/31/15, 09:16
Very nice thing, but still I'm not yet satisfied ;-)AbstractToolbarItem.php:41What is this getter good for? If it is used only internally, please do not expose it to the outside.SystemInformationToolbarItem.php:130you need to check if git is really available! Some use a dev version via the nightly build downloads and have no git availablelocallang.xlf:12this is not needed here. There is no linebreaks.locallang.xlf:15same here.locallang.xlf:19I would avoid having <br> here. Just use a normal line break and do the LF->br conversion on output.SystemInformation.html:2just define the extension name in the StandaloneView and you don't need to put the whole path here all the time.SystemInformationMenu.js:36no need for the extra function wrapSystemInformationController.php:31shortenlocallang.xlf:357not neededext_localconf.php:5combine into a single ifSystemEnvironmentBuilder.php:476I'm almost certain that we already have such a check for disabled functions somewhere. (maybe install tool)SystemEnvironmentBuilder.php:476shortenDatabaseConnection.php:3169we usually have no dot at the end -
Andreas Kienast commented on patch set 12 03/31/15, 10:31
SystemEnvironmentBuilder.php:476ReplyThat's a protected function in there doing more stuff than I need. -
Andreas Kienast uploaded patch set 13 03/31/15, 10:31
-
Andreas Kienast uploaded patch set 14 03/31/15, 10:33
-
Markus Klein voted on patch set 14 CR +1 03/31/15, 10:46
-
Xavier Perseguers voted on patch set 14 V +1 03/31/15, 10:53
-
Xavier Perseguers commented on patch set 14 03/31/15, 19:01
SystemInformationToolbarItem.php:138why do you rely on shell_exec? you could do the same with exec(), which is supposed to be always available and furthermore, Core should use \TYPO3\CMS\Core\Utility\CommandUtility::exec() instead of directly calling exec()SystemInformationToolbarItem.php:296nitpicking: 2 spaces hereSystemInformationToolbarItem.php:317No need for fully qualified call to GeneralUtility, you aliased it at the top -
Andreas Kienast uploaded patch set 15 04/01/15, 17:32
-
Markus Klein voted on patch set 15 V +1 CR +1 04/01/15, 17:58
-
Frank Nägler commented on patch set 15 V +1 04/01/15, 18:46
InformationStatus.php:46maybe STATUS_INFO = -1 and STATUS_NOTICE = -2 like for FlashMessages and Modals? -
Jigal van Hemert voted on patch set 15 CR +2 V +2 04/01/15, 19:12
-
Jigal van Hemert merged patch set 15 04/01/15, 19:12