GitHub PushEvent at 2014-08-15 22:14:29
Repository: liferay-portal
Actor: peterfellwock
Payload: {"shas":[["605b551a43b35e7edd7f3d9a95e544a2871b7334","ce58d1482977d7bcfcd814c87ddb7d49f7a3fbef@liferay.com","LPS-49360 Javascript bug when setting \"company.settings.form.miscellaneous\" without \"display-settings\" in portal.properties.","John Zhao",false],["9af3759136945f740618f7c743318c12d742dd46","b33a07bde6cf01862fa0417102134758a8e84ec3@liferay.com","LPS-43745 - The remove page button is cutoff in a minimized interface","michael.bradford@liferay.com",false],["3b417c502cb52682530bef4eea260b483cab0bff","b78ef181aebf70ccabbdb95f1d659cc2ac00ca49@liferay.com","LPS-43745 - Source formatting","Jonathan Mak",false],["b70f61ea1f8c1430e9d07ce86c4c82f5d3fffe02","c45c4b71188d075a199e3c570b2c836d306241c0@liferay.com","LPS-49301 Add int input field cssClass","Bejond Shao",false],["abb3a10d3a613640f4210c7d17a5c17a4f564189","689850a986ab997890b8be94836e9497b75fb1e9@liferay.com","LPS-49301 use css form-control to any type by default","Dale Shan",false],["558b45b1ac3d33079a366bcd3705e98988c1ad05","689850a986ab997890b8be94836e9497b75fb1e9@liferay.com","LPS-49301 fix simliar issue for timezone in display setttings","Dale Shan",false],["54237d4ecbf4a4fe72fc223e75d1749774a12f74","b78ef181aebf70ccabbdb95f1d659cc2ac00ca49@liferay.com","LPS-49301 - General source formatting","Jonathan Mak",false],["c72182403600ebacb99a28617891c276f555b7ef","c45c4b71188d075a199e3c570b2c836d306241c0@liferay.com","LPS-49328 Add Tags permission button lock icon","Bejond Shao",false],["3897fc859ef1f9f6bc08232d8ae0b200cd48c022","19d87895fd866a870172ad2efba03013e296358f@liferay.com","LPS-49301 SF","Brian Chan",false],["767a8169b5a40e37012ef11f766fb1eaacdc2a47","bd0f59d2d3174f2cc054cb1dbae471640d962a7c@liferay.com","LPS-49199 'Show No Border' causes long portlet title text to overflow","Patrick Yeo",false],["e285016be3d82d04f79a2aab139a0061b392b35f","bd0f59d2d3174f2cc054cb1dbae471640d962a7c@liferay.com","LPS-49199 Convert to mobile first","Patrick Yeo",false],["3d311fe41e8d63fef5440db3ca647060b7428851","b78ef181aebf70ccabbdb95f1d659cc2ac00ca49@liferay.com","LPS-49199 - General source formatting","Jonathan Mak",false],["18e5d7dec2588ac62b9bc467047cc916b331d4bb","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Define a common interface for all Document Library DisplayContexts. If we see it fits we can further generalize this pattern to the whole portal but I prefer to start with document library as a prototype first.","Iván Zaera Avellón",false],["effc49646aafd1736a876c695aab4e2f639c290d","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Create a base implementation class for the DLDisplayContext interfaces. DLDisplayContext can be chained linearly (like servlet filters, for instance) so that overriders can delegate in the default portal implementation and also to be able to install more than one overriding plugin. Thus, they always receive a parent display context. Also, a DLDisplayContext is always be associated to a request and a response (given that it lives in the presentation layer).","Iván Zaera Avellón",false],["fa4e496448dd6f48781d9983317871b8b7e7c47f","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Create a base implementation class for the DLFileEntryActionsDisplayContext interface. A DLFileEntryActionsDisplayContext is always associated with a FileEntry and a FileVersion, representing the business objects from which we want to query available actions.","Iván Zaera Avellón",false],["76d5191a2370fa3c64872b424b77d4d923fdb74b","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Create the DLFileEntryActionsDisplayContext. This type of display context is used to know which actions are available in the UI for a given FileEntry and FileVersion.","Iván Zaera Avellón",false],["ba70e3bd0d83077d0d6bc94deba8b56cbb6419dc","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Create an interface to register factories for DLFileEntryActionsDisplayContext as OSGi components. This is the interface that extension plugins will use. The factory can wrap the given parentDLFileEntryActionsDisplayContext inside a decorator or return it without modification if it cannot handle the given FileEntry and FileVersion.","Iván Zaera Avellón",false],["77f88f57e64a583b6c9535017f994064bc352742","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Adapt the old DLFileEntryActionsDisplayContext class to the newly created interface. I rename it to DefaultDLFileEntryActionsDisplayContext since it will be the default portal implementation of DLFileEntryActionsDisplayContext. I also remove the method getDLActionsDisplayContext() since we need to decouple the different display contexts to be able to override them via OSGi easily.","Iván Zaera Avellón",false],["068bbdb210f4f6e8ab1775aff737e2d641669ceb","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Create a helper class for the portal to chain the DefaultDLFileEntryActionsDisplayContext with the DLFileEntryActionsDisplayContexts coming from OSGi extension plugins.","Iván Zaera Avellón",false],["8acfc37fdf359cbeebae974c91839ed2018041d3","9b95ce62b57d299cd99a3d268f375e473aac272b@liferay.com","LPS-49146 Adapt JSPs to the new DLFileEntryActionsDisplayContext lifecycle.","Iván Zaera Avellón",false]],"size":85,"ref":"refs/heads/LPS-49192","head":"b847c419edcbbcca21ede829881a13f6b1886efe"}