Your web pages need a good doc type:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
and a good encoding in the Head:
IE is not going to understand entities the way you hope unless your are using
standards - otherwise it's all hit and miss.
Here is an enourmously useful presentation on th
A while back Roy posted in his block some ideas to this end.
http://jboss.org/jbossBlog/blog/rrusso/2005/07/20/89437546793992884735F2695A62E529.txt
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890255#3890255
Reply to the post :
http://www.jboss.org/index.h
No sorry, Roy - I probably should have been more specific.
In looking over your implementation, I noticed you were using the default valid
elements which is a small subset of XHTML - some kind soul created a big ol
list of all XHTML to use with the verify.
In pasting in my test document, I noti
I meant wiki - something more formal posted on the wiki
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887279#3887279
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887279
-
No to pure div render.
I posted very pre-pre-alpha as a sort of preview because you seemed interested.
Yesterday I made some significant changes that corrects some cross-browser
problems.
The CSS is based on various techniques out there. I'll try to get something
more formal posted on the foru
What I came up with is to kick the Maximize altogether. The reason for this is
two-fold.
One - there's no precident for maximize out there "in-the-wild". i.e. There's
no web sites to my recollection that I've visited over the past five years that
have maximize button. SO - this could be consid
I'm getting kind of far on a new improved version of myLayout that does 3
columns with header and footer. This version will be tableless, standards based
and more.
I was saving the divrender for last but I'll try to get something working there.
I can tell you already that the Maximize functiona
You know, I'm re-reading this and I'm liking more the idea of keeping the
"layout" of the document out of reach of the web designer, i.e. jsp/CSS.
If you want an easy to use themeing system, you probably should keep that in a
Java class and keep it as an "Advanced" topic.
I was thinking that if
Ok, good. I'd already started a project in Eclipse to start on this.
It's interesting that you mention "ID". In muling over my "perfect world", I'd
thought that it would be clever to attach an ID attribute to everything - but
in thinking about the CSS involved, this ID would necessarily need to
Martin,
I'm interested in creating my own version of
org.jboss.portal.theme.impl.render.DivDecorationRenderer
Then I'm guessing I would change portal-renderSet.xml:
org.slholmes.MyDivDecorationRenderer
Is it intended that developers can create our own Java class for this? I'd like
simply to ch
I spent a good chunk of the holiday weekend getting Portal to work. The first
thing I did was download both JBoss and Portal distribution - but the way this
was set up, you really couldn't follow along with the user's guide.
So I downloaded JBoss 4.0.3 separately, got that working good with no e
I needed to read the following several times to figure out what was up with my
configuration:
http://docs.jboss.com/jbportal/v2.0Final/user-guide/en/html/installation.html
I'm not sure if I needed to do this or not but I did seem to get ahead a little:
Edit jboss-portal.sar/conf/hibernate/hiber
12 matches
Mail list logo
