Re: [Hypercontent-users] Modify HC interface

[Alex V. <al...@bi...>]

On Dec 13, 2006, at 5:31 PM, tom tom wrote:

> Hi,
>
> After the hard work, very soon HC will go to
> production, Now time has come to customize the UI as
> we did for uPortal
>
> Is there any documentations around on how to modify
> the HC userinterface as per the institution needs.
>
> If not let us know which xsls etc that we need to
> concentrate on.

All the application screens are located in the /screens/ directory  
(e.g. localhost:8080/screens).  They are mostly velocity templates  
(.vm) and a few XSL.  All the css are in the /css/ directory.  You  
can edit them all at runtime using HC - but be careful because it is  
possible to then break the UI!  If you break the UI, you can find the  
"file.properties" for the broken file in the underlying filesystem of  
a versioning repository and subtract 1 from the currentEdition  
property to revert to a working  copy (restart required).

The primary CSS of interest are

/css/interactive.css
- defines layout and styling for the primary frame-wrapping UI

/css/common.css
- common form and button styles

/css/workflow.css
- for workflow screens

/css/uportal.css
- uportal styles are used for the editing tools for historical reasons


The main screens of interest are

/screens/interactive-header.vm
- constructs main UI header (title, search logout and breadcrumbs)

/screens/interactive.vm
- constructs main UI tabs and frame

/screens/html_skin.xsl
- used for project list, error pages, everything with the big white  
"HyperContent" on a blue background.  This is the first thing many  
people want to change!

>
>
> In addition to that when we publish or even build the
> project it does the publishing successfully but in the
> end it shows that
>
> You are not authorized to view http://......../build
>
> If there a image or index.xml in the root level it
> shows that,
>
> How can we get around with this, How can we get rid of
> the 'You are not authorized to ............' message.
> Is there any way to have a customized message.

You can control the right workflow pane for any workflow script by  
manipulating the "href" variable in the configuration script.  Any  
time a "render" or "copy" command is executed, the "href" attribute  
is set automatically (and sometimes results in the "not authorized"  
message), but you can then override it.  For example, in the /config/ 
workflow/build.xml script you could change

<event name="build" permissions="build">
		<variable name="builder" value="${actor}"/>	
		<render path="${path}" destination="/build/" force="false"  
delete="true"/>
		<nq who="${builder}"/>
		<nq q="building"/>
	</event>

to

<event name="build" permissions="build">
		<variable name="builder" value="${actor}"/>	
		<render path="${path}" destination="/build/" force="false"  
delete="true"/>
		<variable name="href" value="${abs-project-base}/my-custom- 
screen.html"/>
		<nq who="${builder}"/>
		<nq q="building"/>
	</event>

where you have a custom message in your repository at /my-custom- 
screen.html

You can also try setting the "base-url" attribute of the build or  
publish filesystem definition in project-definition.xml if you are  
building to a path which is served by an other web server.  This will  
then be used in preference to the built-in web server in constructing  
the build or publish URL.  e.g.

<build base-url="http://my.apache.host/my-project/build/">
<filesystem-def  . . .
</build>


Cheers,
	Alex