<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
Thank you Rafael !<br>
<br>
First we should keep portal and WCM discussions seperated, GateIn is
about the portal so I leave the WCM part apart.<br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
H2 { margin-left: 0.4in; text-indent: -0.4in; margin-bottom: 0.08in }
H2.western { font-family: "Albany AMT", "Arial"; font-size: 14pt; font-style: italic }
H2.cjk { font-family: "DejaVu Sans", "Times New Roman"; font-size: 14pt; font-style: italic }
H2.ctl { font-family: "Tahoma"; font-size: 14pt; font-style: italic }
--></style>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
H2 { margin-left: 0.4in; text-indent: -0.4in; margin-bottom: 0.08in }
H2.western { font-family: "Albany AMT", "Arial"; font-size: 14pt; font-style: italic }
H2.cjk { font-family: "DejaVu Sans", "Times New Roman"; font-size: 14pt; font-style: italic }
H2.ctl { font-family: "Tahoma"; font-size: 14pt; font-style: italic }
-->
</style>
<h2 class="western">Overall</h2>
<ul>
<li>
<p>Change messages from the default popup (error/warning/info).
It seems messy since there's already JavaScript's alerts and is not
ergonomic. JSF-like messages are much better (they appear in a box
above the form). The user only wants to correct his fields, the don't
want to click any annoying popup.</p>
<ul>
<li>
<p>eXo: request forwarded to Portal Team</p>
</li>
</ul>
</li>
</ul>
</blockquote>
<br>
Agreed, do you know if a Jira was opened ? I don't think there is one
on GTNPORTAL, we should keep this requirement for furture evolution of
WebUI so feel free to add a Jira.<br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
--></style>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<ul>
<li>
<p>There's already a Groovy cache, to save compilation AFAIK.
There could be also a HTML cache, that would cache the whole page, not
a per portlet thing.</p>
</li>
</ul>
</blockquote>
There are already multiple layers of cache, what would be interesting
would be to return the correct Last-Modified on HTTP Response but it's
tricky to get. How do you see your HTML cache working with invalidation
?<br>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
H2 { margin-left: 0.4in; text-indent: -0.4in; margin-bottom: 0.08in }
H2.western { font-family: "Albany AMT", "Arial"; font-size: 14pt; font-style: italic }
H2.cjk { font-family: "DejaVu Sans", "Times New Roman"; font-size: 14pt; font-style: italic }
H2.ctl { font-family: "Tahoma"; font-size: 14pt; font-style: italic }
-->
</style>
<h2 class="western">Language</h2>
<ul>
<li>
<p>The Language Settings should use the locales-config.xml
definitions (output-encoding and input-encoding) to encode request
parameters. There are a lot of encoding problems through eXo (try to
login with a fake username with accents, for instance)</p>
<ul>
<li>
<p>eXo: request forwarded to Portal Team</p>
</li>
</ul>
</li>
</ul>
</blockquote>
<br>
If there are encoding issues, please report them.<br>
<br>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
H2 { margin-left: 0.4in; text-indent: -0.4in; margin-bottom: 0.08in }
H2.western { font-family: "Albany AMT", "Arial"; font-size: 14pt; font-style: italic }
H2.cjk { font-family: "DejaVu Sans", "Times New Roman"; font-size: 14pt; font-style: italic }
H2.ctl { font-family: "Tahoma"; font-size: 14pt; font-style: italic }
-->
</style>
<h2 class="western">Portlets and HTML rendering</h2>
<ul>
<li>
<p><a name="line2026"></a>Don't render the div tags like
VIEW-PAGEBODY, META-DATA-BLOCK, PORTLET-FRAGMENT, etc (or render the
minimum required) with “display: none”. That pollutes the code, makes
the downloading slower, loads the browser and confuses us with eXo's
CSS. Rather these tags should not be shown by default but only in Edit
Site, Edit Mode, etc. If that was done this way because of AJAX, it's
much preferable for the web-designer to have a refresh than a end-user
to have a bloated HTML.</p>
<ul>
<li>
<p>eXo: Such a thing will be discussed internally in the new
GateIn project as I would like in WCM a “production” site without this
code.</p>
</li>
</ul>
</li>
</ul>
</blockquote>
Not sure if they are required, looks like semantic info<br>
<br>
<blockquote type="cite">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<ul>
<li>
<p>A decorator container. Something like a wrapper that would
have a before and an after field that would surround it's contents.</p>
<ul>
<li>
<p>eXo: don’t understand that point.</p>
</li>
<li>
<p>Rliu: Just like there are column, rows, tab and mixed
container, it would be useful to have a “decorator container”. A
container that would decorate it's content. Imagine (I had to do that)
that I wan a PageBody with rounded corners. There are a lot of methods
to do rounded corners in HTML/CSS, but only a few are applicable
because there's no way to surround PageBody's content (a simple case:
imagine I want a <div> tag before and a </div> after page
content. Or a <center> or <table>, etc)</p>
</li>
</ul>
</li>
</ul>
</blockquote>
A wrapper around a page ? around a content of a layout ? Not sure I
understand neither :-/<br>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<ul>
<li>
<p>Editing class/style tag of portlet's div is really useful
(used a lot of times in this project I'm in). There should be a field
for each of these (and maybe width/height would be unnecessary) in
Portlet Settings tab.</p>
<ul>
<li>
<p>eXo: that’s also part of WCM requirements for
accessibility : I’d like to add a class property for each portlet
instance and we have to remove the portlet id property for w3c
compliance. We’re on the same wave <font face="Wingdings"></font></p>
</li>
</ul>
</li>
</ul>
</blockquote>
<br>
This is the dreaded issue of the admin portal, the problem is to draw
the line between administrators and developers. Some people will want
limited but easy to understand UI and others will want advanced UI,
that leads to your introduction and you are 100% right.<br>
<br>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<ul>
<li>
<p>Portlet's id should be editable. Then I could use it as CSS
selector and have meaningful id's in my HTML.</p>
<ul>
<li>
<p>eXo: agreed, see previous answer.</p>
</li>
</ul>
</li>
</ul>
</blockquote>
True.<br>
<blockquote type="cite">
<meta http-equiv="CONTENT-TYPE"
content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<ul>
<li>
<p>Navigation, Breadcrumb and Site Map should be done with
server-side scripting.</p>
</li>
<ul>
<li>
<p>This is much less error-prone (another JavaScript error
wouldn't break my script)</p>
</li>
<li>
<p>We could use caching</p>
</li>
<li>
<p>We could use IDE goodies</p>
</li>
<li>
<p>And I think it's prettier, much more maintainable and the
concept of versioning gets more reasonable.</p>
</li>
</ul>
</ul>
</blockquote>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.1 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<br>
This is already the case in portal AFAIK.<br>
<br>
Thomas.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 01/04/2010 02:22 PM, rafael liu wrote:
<blockquote
cite="mid:f71ba8d81001040522v26401ab5ya061bcd986cf0612@mail.gmail.com"
type="cite">Hey, guys<br>
<br>
I'm an outsider, since I use GateIn/eXo a lot, I subscribed to this
list. Some time ago I wrote to both Benjamin about some suggestions
regarding the products I was using.<br>
<br>
I'm forwarding the document we exchanged with comments by exo and me. I
believe the suggestions concerning the Portal is pretty much valid
still.<br>
<br>
Could you give me a feedback for further discussions?<br>
<br>
BTW, nice work. GateIn is looking amazing.<br clear="all">
<br>
-- <br>
Rafael Liu<br>
+55 61 9608-7722<br>
<a moz-do-not-send="true" href="http://rafaelliu.net">http://rafaelliu.net</a><br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
gatein-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/gatein-dev">https://lists.jboss.org/mailman/listinfo/gatein-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>