GCube Widgets Library - General guidelines about Portlet StyleSheets

From Gcube Wiki
Revision as of 15:50, 4 January 2013 by Massimiliano.assante (Talk | contribs) (First Step - Download gWL)

Jump to: navigation, search

gCube GWT Widgets Library (gWL)

gWL has been created to uniform the Look & Feel for gCube Portlets using plain GWT (Not GWT-Ext).

Note:

This guide is divided in two parts, in the first part you will learn how to configure/setup you GWT Application to use gWL, in the second one a tutorial will show you how to actually exploit gWL in your GWT Application.

Setup you GWT Application to use gWL

Your existing GWT Portlet needs few changes to make use the of gWL

First Step - Download gWL

You can download the gWL from here: nexus-search;quick~gcube-widgets. Make sure you always get the latest version.

If you maven you can add the following dependency

Invalid language.

You need to specify a language like this: <source lang="html4strict">...</source>

Supported languages for syntax highlighting:

4cs, 6502acme, 6502kickass, 6502tasm, 68000devpac, abap, actionscript, actionscript3, ada, aimms, algol68, apache, applescript, arm, asm, asp, asymptote, autoconf, autohotkey, autoit, avisynth, awk, bascomavr, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, caddcl, cadlisp, cfdg, cfm, chaiscript, chapel, cil, clojure, cmake, cobol, coffeescript, cpp, csharp, css, cuesheet, d, dart, dcl, dcpu16, dcs, delphi, diff, div, dos, dot, e, ecmascript, eiffel, email, epc, erlang, euphoria, ezt, f1, falcon, fo, fortran, freebasic, freeswitch, fsharp, gambas, gdb, genero, genie, gettext, glsl, gml, gnuplot, go, groovy, gwbasic, haskell, haxe, hicest, hq9plus, html4strict, html5, icon, idl, ini, inno, intercal, io, ispfpanel, j, java, java5, javascript, jcl, jquery, kixtart, klonec, klonecpp, latex, lb, ldif, lisp, llvm, locobasic, logtalk, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, magiksf, make, mapbasic, matlab, mirc, mmix, modula2, modula3, mpasm, mxml, mysql, nagios, netrexx, newlisp, nginx, nimrod, nsis, oberon2, objc, objeck, ocaml, octave, oobas, oorexx, oracle11, oracle8, oxygene, oz, parasail, parigp, pascal, pcre, per, perl, perl6, pf, php, pic16, pike, pixelbender, pli, plsql, postgresql, postscript, povray, powerbuilder, powershell, proftpd, progress, prolog, properties, providex, purebasic, pycon, pys60, python, q, qbasic, qml, racket, rails, rbs, rebol, reg, rexx, robots, rpmspec, rsplus, ruby, rust, sas, scala, scheme, scilab, scl, sdlbasic, smalltalk, smarty, spark, sparql, sql, standardml, stonescript, systemverilog, tcl, teraterm, text, thinbasic, tsql, typoscript, unicon, upc, urbi, uscript, vala, vb, vbnet, vbscript, vedit, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, whois, winbatch, xbasic, xml, xpp, yaml, z80, zxbasic


<dependency>
  <groupId>org.gcube.portlets.user</groupId>
  <artifactId>gcube-widgets</artifactId>
  <version>1.4.0-SNAPSHOT</version> <!-- Check the latest -->
</dependency>

Second Step - Add gWL to your Build Path

Place gCube-Widgets-Library.jar in a convenience folder, we suggest ./lib, and add it to your project build path.

Once the jar file is added in the build path edit your GWT Application configuration file (file.gwt.xml). Add the following:

   ...
   <!-- inherits gCube Widgets Library  	               -->
   <inherits name='org.gcube.portlets.user.gcubewidgets.WidgetFactory'/>
   ...
   ...
   ...

Third Step - Remove the default GWT style sheet (if any)

edit your GWT Application configuration file (file.gwt.xml). remove or comment the following:

   ...
      <!-- Inherit the default GWT style sheet.  You can change       -->
      <!-- the theme of your GWT application by uncommenting          -->
      <!-- any one of the following lines.                            -->
      <inherits name='com.google.gwt.user.theme.standard.Standard'/> 
       ....
      <!-- inherits name='com.google.gwt.user.theme.dark.Dark'/ -->
   ...
   ...
   ...
 </module>

You should also remove all the .gwt-* css classes from your portlet css (if any) e.g. .gwt-Button, .gwt-TextBox etc.

You are now ready to use gWL!!

gCube Widgets Library Tutorial

Using gWL is a straight forward operation, it defines css classes for all GWT Widget, hence you don't need to define css classes anymore for them.

However you should make use of the org.gcube.portlets.user.gcubewidgets.client.GCubePanel class as main panel in your entry point class.

  • the GCubePanel class constructor can be instanciated in two ways:
    • GCubePanel(String helpLink)
    • GCubePanel(String headerCaption, String helpLink)

Note: a helpLink parameter must be always passed to the constructor, if you don't have any help url for your portlet just pass an empty String to the constructor. Make sure to edit it once the portlet is deployed in production though.


GCubePanel usage examples:

Panel with Header and Caption

  /**
   * This is the entry point method.
   */
  public void onModuleLoad() {	    
	GCubePanel mainLayout = new GCubePanel( "My Header Caption", "http://myporlet-usersguide-url");
        ...
        ...

gives the following result (panel content is arbitrary):

Gcube-panel-s1.jpg

Panel with Header NO Caption

  /**
   * This is the entry point method.
   */
  public void onModuleLoad() {	    
	GCubePanel mainLayout = new GCubePanel("http://myporlet-usersguide-url");
        ...
        ...

gives the following result (panel content is arbitrary):

Gcube-panel-s2.jpg

Adding custom widgets to gCubePanel Header

If you want to add your widget to the header you'll need to use the addHeaderWidget(Widget toAdd) method.

in the example shown below a MenuBar widget has been added to the header, no css styles need to be defined for your Menubar widget

Gcube-panel-s3.jpg

Panel without Header

If you don't want to have a header in your gCubePanel you just need to use the enableHeader(boolean enable) to disable it.

Gcube-panel-s4.jpg

GCubeDialog usage examples:

When you need to whether use a Popup or a Dialog Box you may use the org.gcube.portlets.user.gcubewidgets.client.popup.GCubeDialog class.

Just use it as you would use a Standard GWT DialogBox.

Overridden css styles

gWL overrides css styles for the following GWT Widgets:

  • Button
  • PushButton
  • TextBox
  • TextArea
  • TabPanel
  • DecoratedTabBar
  • MenuBar
  • Tree & Tree Item
  • StackPanel

This means that you either don't have to apply styles to the widgets above nor to define .gwt-* style for any of them.

However, if you wish to add your own style to the widget you can do it by using the GWT native addStyleName method. Do not forget to Remove the default GWT style sheet (Third Step in this guide)

For PopupPanels - DialogBoxes you should use the org.gcube.portlets.user.gcubewidgets.client.popup.GCubeDialog class provided with this Library.