[JBoss JIRA] (GTNPORTAL-3454) Remove native AMD modules from requireJs config
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3454?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3454:
----------------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1090470|https://bugzilla.redhat.com/show_bug.cgi?id=1090470] from POST to MODIFIED
> Remove native AMD modules from requireJs config
> -----------------------------------------------
>
> Key: GTNPORTAL-3454
> URL: https://issues.jboss.org/browse/GTNPORTAL-3454
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.8.0.Final
>
>
> RequireJs config is a json structure renderead inline in the HTML markup of every page returned by the portal. The recent "Native AMD Support" feature has brought the possibility to work with large third-party javascript frameworks such as Dojo containing thousands of JavaScript modules. The present implementation adds an entry for every native AMD module into RequireJs config. With a dojo portlet deployed, this causes an overhead of more than 400KB per page.
> Steps to Reproduce:
> 1. Compile and deploy the dojo portlet application from https://github.com/ppalaga/dojo-portlet
> 2. Import applications
> 3. Inspect the source of any portal page, e.g. /portal/classic/home
> 4. Locate the line starting with
> var require =
> Actual results: All dojo resources are there in the json structure assigned to the require variable.
> Expected results: No resources coming from Dojo should be there.
> Additional info: Not having the resources coming from Dojo in requireJS config is technically possible as the native AMD modules are implicitly SHARED and the baseUrl is set properly in the config.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3417?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3417:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Disable users icons look like inverse
> -------------------------------------
>
> Key: GTNPORTAL-3417
> URL: https://issues.jboss.org/browse/GTNPORTAL-3417
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: 3.8.0.Beta01-SNAPSHOT
> Reporter: Vlastislav Ramik
> Assignee: Lucas Ponce
> Labels: RHJP62
> Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3470) Make permission defaults in page creation forms consistent
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3470?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3470:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.8.0.Final
Resolution: Done
> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
> Key: GTNPORTAL-3470
> URL: https://issues.jboss.org/browse/GTNPORTAL-3470
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.8.0.Final
>
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows:
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3470) Make permission defaults in page creation forms consistent
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3470?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3470:
----------------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1094154|https://bugzilla.redhat.com/show_bug.cgi?id=1094154] from NEW to MODIFIED
> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
> Key: GTNPORTAL-3470
> URL: https://issues.jboss.org/browse/GTNPORTAL-3470
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.8.0.Final
>
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows:
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3417?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3417:
----------------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1076175|https://bugzilla.redhat.com/show_bug.cgi?id=1076175] from POST to MODIFIED
> Disable users icons look like inverse
> -------------------------------------
>
> Key: GTNPORTAL-3417
> URL: https://issues.jboss.org/browse/GTNPORTAL-3417
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: 3.8.0.Beta01-SNAPSHOT
> Reporter: Vlastislav Ramik
> Assignee: Lucas Ponce
> Labels: RHJP62
> Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months