Thanks for your thoughts Anthony. I had gotten the same impression from
San Diego that there is a desire to move away from fluid.
With the Respondr work much of the dependency upon fluid has been
removed. The fluid class names are still present because uPortal 4.1
must still support universality and mUniversality, but bootstrap class
names have been added to support the Respondr theme. There are still a
few places where fluid components are used (the paging component comes
to mind, email preview uses it quite a bit), but there is a desire to
replace them with non-fluid components over time.
I agree with you Anthony. Portlets should import their needed libraries
(ideally using resource server taglibs for optimization) and not assume
the portal has any specific library or version.
This isn't exactly the forum but in light of my 2nd paragraph I thought
I'd add there has been some discussion about the maintenance challenge
of supporting two very different themes. There is not a plan yet but if
the Respondr theme is very popular, perhaps we can remove the fluid
class names completely in 4.2 or after to reduce maintenance costs. The
plan will unfold as we get an idea about Respondr adoption. We don't
want to force Respondr adoption (there are a lot of custom portlets
running on universality), but if it is done well, the advantages of it's
mobile-friendly and tablet-friendly rendering might bring a lot of
adopters. In the mean time, I personally think we need to have both
theme sets (Respondr and universality/mUniversality) supported as best
we can.
I favor patching Fluid; I think there is value in the excellent
contribution, but I'm interested to hear other opinions on the topic.
Thanks for the comments and discussion. I appreciate our vibrant community!
James Wennmacher - Unicon
480.558.2420
On 11/19/2013 01:50 PM, Anthony Colebourne wrote:
Hi,
On 19/11/13 17:10, James Wennmacher wrote:
The question is do we want to patch the version of fluid 1.4 included in
uPortal to support newer versions of jQuery. With the addition of
bootstrap 3.0 in the Respondr theme auxepaul notes that bootstrap 3.0
requires jQuery 1.9.0 or greater. Bootstrap 3.0 is currently running
with jquery 1.6.4/jqueryui 1.8.13 in master in the Respondr theme.
At the conference in San Diego the strong opinion was that Fluid is
not needed/wanted going forward. It was noted that some portlets also
have a dependency on it.
I believe the plan of action was to re-write uPortal JS and create a
skin that does not use Fluid/FSS.
In an effort to support existing portlets, those portlets should
provide a preference that allows a locally name-spaced version of
Fluid to be included. For FSS the css can be scoped to the .portlet
class.
If we also need an interim way to keep Fluid at the uPortal level then
the patch looks perfect!
-- Anthony.
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
