4 Replies Latest reply on Apr 3, 2008 3:08 AM by antoine_h

    3.2.0 : Script files loading strategy / new files ?

    antoine_h
    antoine_h Apr 1, 2008 10:00 AM

      Hello,

      this feature of Script files loading strategy is great.

      In a portlet and portal, it allow to load scripts only once.

      with 3.2.0 : If I set to DEFAULT, the <rich:datascroller> works.

      if I put NONE, and set the script in the jboss-portlet.xml (injection in the header), then the <rich:datascroller> do not work.

      This NONE option is explained in the WikiJBPBRichFaces : http://labs.jboss.com/wiki/WikiJBPBRichFaces

      I have put the two files : framework.pack.js and ui.pack.js, in the web content folders.
      The new ones. The one taken from the richFaces 3.2.0 lib jar.

      => questions :
      - which script files must be set in the header of the portal page ?
      - idem for the styles xcss files ? some new files have appeared in 3.2.0 ?
      - update the wiki of configuration of the jboss portlet bridge ?
      - make a jira for that ?

      Thanks,

      • 1018 Views
      • Tags:
        • 1. Re: 3.2.0 : Script files loading strategy / new files ?
          nbelaevski
          nbelaevski Apr 1, 2008 3:22 PM (in response to antoine_h)

          Hello,

          We've added several new XCSS files for standard controls skinning. They're auto negotiated based on user-agent header, but I'm afraid that won't work well in portal environment. I've created JIRA entry for that: http://jira.jboss.com/jira/browse/RF-2921

            • Actions
          • 2. Re: 3.2.0 : Script files loading strategy / new files ?
            antoine_h
            antoine_h Apr 2, 2008 5:54 PM (in response to antoine_h)

            Thanks,

            They're auto negotiated based on user-agent header

            can you, please, give some more explaination of that (is it a new magic technologie...;-)

            I guess that adding all the files in the portal page header, won't work ?
            even if this do not allow to optimize the needs of css depending on which page is served...
            anyway about that, most of the browser put the css files in cache, so even if there is 7 of them, that won't waste the network resources...

            may be link the jira with the PortletBridge project ?



              • Actions
            • 3. Re: 3.2.0 : Script files loading strategy / new files ?
              nbelaevski
              nbelaevski Apr 2, 2008 6:40 PM (in response to antoine_h)

              No, that's not a new technology.

              We've deleloped skinning for controls based on the fact that Safari & Opera browsers apply rich controls styling that we shouldn't touch. Their controls looks just fine and our skinning makes it just worse, so we've decided to apply that for browsers that aren't Safari or Opera.

              Adding skin.xcss file in the portal page header won't work as we thought, but if you're not going to use standrad controls skinning then it's ok.

                • Actions
              • 4. Re: 3.2.0 : Script files loading strategy / new files ?
                antoine_h
                antoine_h Apr 3, 2008 3:08 AM (in response to antoine_h)

                ok

                I have not read yet the skinning part of the doc.
                I will soon.
                right now, I am on making things run.

                I will look at this css mechanism and how we may configure in a portal environnement.

                any explanation on how the whole thing works is welcome ;-)
                particularly about these multiple new xcss files...

                I guess this will be added in the doc, later ?
                (if not yet)
                make a Jira about that, not to forget it ?

                  • Actions