I would like t o quote a famous Dutch soccer trainer
Translated into English it would be something like:
Am you so dumb or am I now so smart?
I have read some tutorials about XPages and I have started with upgrading an existing Domino application with XPage technology. Basically I want to display documents with an XPage instead of a web enabled Form.
I have some nice center layered container layout with sections for a header, leftside menu, main and a footer. With a bit of help of CSS it looks fine. Now I have started to transform the subforms into custom controls and the structure of the Form into an XPage. In stead of DIVs I am using Panels (I should or not?).
First thing I notice that panels in XPage technology only can get a name, when rendering this will be transformed into an ID. I have added my CSS for now in several files, later I will merge them together. For now for each custom control I have a CSS file attached to it.
What is happening is that the CSS get rendered well in Designer but when I look at the XPage in a browser the styling iscompletely gone! If I check in the source I see that all the ID’s have been modified, so I wonder if my CSS is still valid?
For example the original code:
<xp:panel id=”headerName”>application name</xp:panel>
get’s rendered as:
- Uhm, can somebody explain how to correctly code my CSS? (it is being loaded).
- Why have they done this? This makes converting current Domino applications into copy & paste & ready to run XPages enabled applications time consuming.
- I guess the reasoning behind it is not logical for normal web developers so it makes the adaption of Domino harder for them.
Here how it looks: