-
1. Re: Looking for SEAM iText Features
norman.richards Aug 15, 2007 12:45 AM (in response to marthoff)1 - I think you need to set all the cell border widths to 0
2 - Add spacing before/after your elements?
3 - I don't think those are compatible. -
2. Re: Looking for SEAM iText Features
marthoff Aug 15, 2007 8:07 AM (in response to marthoff)Thanks for your answer!
1- Setting the borders to 0 works fine. I just didn't found the border parameter description in the reference.
2- I fixed the newline problem by inserting a #{messages.newline} which points to newline=\n. Btw, I'm not that happy with white space handling of the seam-pdf tag library. It would be nice to set a parameter to ignore leading white spaces.
3- It would be a nice feature to have a compatible tag for the pdf library. -
3. Re: Looking for SEAM iText Features
norman.richards Aug 15, 2007 12:43 PM (in response to marthoff)It might be doable, but since we don't have any concept of a pdf style sheet, I'm not sure you'd get anything that interesting out of it.
-
4. Re: Looking for SEAM iText Features
bakuzozi Aug 17, 2007 4:04 AM (in response to marthoff)Hi!
I would like to applicable the very useful pdf-feature of Seam,
but I have some aesthetically problems:
- firstLineIndent attribute not works in paragraph tag,
but first line shift right with alignment="justify" attribute
(I like DO NOT indent in first line)
- every p:text tag trimmed before whitespaces,
thus the words merges
- national characters lossly, what signed in JBSEAM-1039
and resolved in 2.0.x, but I uses 1.2.1.GA. Because patch
(for 1.2.0.GA) of JBSEAM-1039 not perfect for me...
I had a narrow escape rebuild of my 1.2.1.GA Seam?
Possible put for me JBSEAM-1039 bug-free jboss-seam-pdf.jar?
Very-very grateful!
BakuZozi -
5. Re: Looking for SEAM iText Features
bakuzozi Aug 17, 2007 6:44 AM (in response to marthoff)I'm sorry indent problem solved...
(cause of ugly formatting) -
6. Re: Looking for SEAM iText Features
norman.richards Aug 17, 2007 12:32 PM (in response to marthoff)Please open JIRA issues for any bugs you find so they don't get lost. I'll make sure they all get addressed before 2.0 is out.
-
7. Re: Looking for SEAM iText Features
bakuzozi Aug 21, 2007 5:45 AM (in response to marthoff)Uff! It's not easy come to know Seam-pdf features...
(Documentation is insufficient for practice!)
An wiki can be an big support and timesave for user,
who first meeting with iText (and Seam-pdf).
(I would like writing, but I'm not sure, that's my shod
solutions is the best. My english is not perfect too...)
Considering that much rejected JIRA issues,
already signed (and resolved) reopen of problem
is redundant thing - in my opinion...
I placed I wished jboss-seam-pdf.jar for Seam 1.2.1.GA this:
http://jira.jboss.org/jira/browse/JBSEAM-1039
(Thanks for Petr Ferschmann his patch)
Above jar handle encoding attribute in p:font tag, as in iText:
http://itext.ugent.be/library/api/constant-values.html#com.lowagie.text.pdf.BaseFont.CP1250
Themes for pdf-wiki:
- XHTML-formatting for expected pdf-formatting
- border attribute in p:cell tag
- use of horizontalAlignment (and verticalAlignment?) attribute
- differences EL between p:text tag (trimmed whitespaces)
- pagenumber and listsymbols (hardwired font-family?)
- and many-many undocumented (without values, examples) attributes
... -
8. Re: Looking for SEAM iText Features
bakuzozi Aug 21, 2007 6:58 AM (in response to marthoff)Latest feature (or bug):
In case of following code:<p:text value="#{contract.beginDate}"><f:convertDateTime type="date" /></p:text>
andCalendar calendar = Calendar.getInstance(); calendar.clear(); calendar.setTime(new Date()); Date beginDate = calendar.getTime();
then by 1 day before value of beginDate (DBMS table is correct)
displaying in pdf document...
...or what I'm doing wrong? -
9. Re: Looking for SEAM iText Features
norman.richards Aug 21, 2007 11:15 AM (in response to marthoff)The bug you mentioned is fixed in CVS. There are no plans right now for another 1.2 release. Bug Gavin if you think we should do one. :)
I don't understand your date issue. -
10. Re: Looking for SEAM iText Features
bakuzozi Aug 21, 2007 1:39 PM (in response to marthoff)OK, new 1.2 release is undesirable evidently.
(Encoding bug resolved by my lazy-eliminating :-)
There is bugfree jar for other users...)
On the other hand date-issue important for us:
Let's observed symptome today: 2007-AUG-21
Then 2007-AUG-21 in classmember or memory-
variable and certainly DBMS table column, but
2007-AUG-20 is in pdf-document! It's correct...?
Maybe not p:text caused, but f:convertDateTime? -
11. Re: Looking for SEAM iText Features
bakuzozi Aug 22, 2007 8:15 AM (in response to marthoff)It seems to me that date issue caused of input side.
Here xhtml-fragment:<s:decorate id="anyDateDecorate" template="edit.xhtml" required="true"> <ui:define name="label">An date:</define> <h:inputText id="anyDate" value="#{myBean.anyDate}" required="true"> <s:convertDateTime pattern="yyyy.MM.dd"/> </h:inputText> <s:selectDate for="anyDate" dateFormat="yyyy.MM.dd"> <h:graphicImage url="img/dtpick.gif" style="margin-left:5px;cursor:pointer"/> </s:selectDate> </secorate>
Then#{myBean.anyDate}
is correct (though not except formed) in pdf, but<p:text value="#{myBean.anyDate}"><f:convertDateTime type="date" /></p:text>
is incorrect: by 1 day earlier (though wellformed) in pdf...
Avoiding of above input-mechanism make displaying
correct date in pdf too. What"s wrong, watts romp...? -
12. Re: Looking for SEAM iText Features
bakuzozi Aug 23, 2007 5:47 AM (in response to marthoff)Maybe my issue caused of differences
<s:convertDateTime>
tag in input-side between<f:convertDateTime>
tag in output-side...?
HEEEEEEEELP...! -
13. Re: Looking for SEAM iText Features
bakuzozi Aug 23, 2007 10:34 AM (in response to marthoff)timeZone attribute of f:convertDateTime doesn't play:
formatter tag:
s:convertDateTime
f:convertDateTime
origin of value:
without timeZone
with timeZone
h:inputText
OK
-1 day
-1 day
new Date()
+1 day
OK
+1 day -
14. Re: Looking for SEAM iText Features
bakuzozi Aug 23, 2007 11:50 AM (in response to marthoff)I'm very sorry...
Still timeZone!
(and "lenient" date-arithmetic in Calendar.add method
and differences CET between CEST... :-)
Date issue closed.