Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

jAPS 2 0 - Presentation Layer Comparison

885 views

Published on

A brief comparison, focusing on a few specific issues, between jAPS 2.0 and an "unnamed" portlet engine.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

jAPS 2 0 - Presentation Layer Comparison

  1. 1. jAPS 2.0 Platform Guess Who... Versione 1.0 1
  2. 2. Prologue Most portal interfaces are still based on HTML or poor XHTML vs. well-formed XHTML Strict. Lots of table-based layout vs. CSS-based positioning for column and portlet layout. I call this: “jumping almost ten years back in the past”. past” Accessib... what? 2
  3. 3. 1. Guess who... applies MVC Actor 1A: famous “enterprise portal solution that is used in more than 100,000 deployments worldwide”  Evidence 1A: a JSP file from the back­office. <c:if test="<%= !themeDisplay.isStateExclusive() && ! themeDisplay.isStatePopUp() %>"> [...] <table class="lfr­ctrl­panel <%= panelCategory %>"> [...] private static boolean _hasPortlet(String portletId, String  category, ThemeDisplay themeDisplay) throws Exception { List<Portlet> portlets =  PortalUtil.getControlPanelPortlets(category, themeDisplay); [...] return false; } [ad libitum...] 3
  4. 4. 1. Guess who... applies MVC Actor 1B: jAPS 2.0  Evidence 1B: a JSP file from the back­office. <h1><s:text name="document.title.main" /></h1> <p><s:text name="note.jAPS.intro" />.</p> <wp:ifauthorized permission="editContents"  var="hasEditContents" /> <wp:ifauthorized permission="manageResources"  var="hasManageResources" /> <c:if test="${hasEditContents || hasManageResources}"> <p><s:text name="note.maxiButtons.intro" />:</p> </c:if> [ad libitum...] 4
  5. 5. 1. Guess who... applies MVC Try and tell: who does apply the MVC pattern even inside the presentation layer ? Right! jAPS 2.0 does. You won't find a single bit of Java code in a JSP. A presentation layer specialist doesn't have to go for energy drinks just to understand what's the matter with a file from a Web GUI. Your own Accessibility and Usability Guru must focus on Accessibility and Usability, rather than on Java-code-in-a-JSP decrypting tecniques. 5
  6. 6. 2. Guess who... lives in the past Actor 2A: famous “enterprise portal solution that is used…”  Evidence 2A: markup from the front­end. <!DOCTYPE html PUBLIC "­//W3C//DTD XHTML 1.0 Transitional//EN" " http://www.w3.org/TR/xhtml1/DTD/xhtml1­transitional.dtd"> [...] <body class="blue controls­visible guest­community public­ page"> <p class="welcome­intro">CENSORED is a complete all­in­one open  source enterprise portal solution that is used in more than  100,000 deployments worldwide. [...] to create web­based solutions  for enterprise needs, including:</p> <table class="welcome­grid">     <tbody>         <tr class="header">             <td width="50%">INSTANT WEBSITES</td><td  width="50%">SOCIAL NETWORKS</td></tr><tr><td class="web­ publishing" valign="top"> [ad libitum...] 6
  7. 7. 2. Guess who... lives in the past Actor 2B: jAPS 2.0  Evidence 2B: markup from the front­end. <?xml version="1.0" encoding="UTF­8"?> <!DOCTYPE html PUBLIC "­//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1­strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">   [...] <body>   [...] <div id="header"> <h1>Comune di Villamarina</h1> <p>Official Site</p> <div class="noscreen"> <p>[ <a href="#a4" id="a0">Go to Contents</a> ]</p> [ad libitum...] 7
  8. 8. 2. Guess who... lives in the past  Try and tell: who does live almost ten years in the past as defined in the Prologue?  Right! The famous “enterprise portal solution that is used… whatever” does.  XHTML elements do have meanings. That is, meanings a table is meant to be a table. Not a table division in the page layout. That's the div div element.  Users with disabilities - like your stereotypical blind friend and your not-so-stereotypical and very tired, sleepy top manager at 3.00 AM - will thank you for an accessible platform. 8
  9. 9. Epilogue Most portal interfaces are still based on HTML or poor XHTML vs. well-formed XHTML Strict. Not jAPS 2.0. Lots of table-based layout vs. CSS-based positioning for column and portlet layout. Not in jAPS 2.0. I call this: “Sailing towards the future”. future” I call this the Web, made Accessible. Accessible 9
  10. 10. Thank You! Image URL: http://www.yumaaz.gov/Images/General/ss-1003945-futureSign.jpg www.japsportal .org < Do It The jAPS Way /> 10

×