to be added.
Hope this helps, Carsten
Keith Carlton wrote:
Keith wrote:
Carsten,
I am working on a similar problem, can you please post your xml addition
to the faces-config.xml
that get the renderer to see you renderKit?
Thanks,
Keith
Carsten Pieper wrote:
If anyone
Andrew Robinson-5 wrote:
tr:selectOneRadio and optionally put it in a popup?
Well, that would offer a similar functionality but wouldn't look as much
like a
combobox as our guidelines require...
Anyhow, as I mentioned IE6' z-index bug, I found out that a neat little
jQuery plugin
called
Thank you guys!
@Harald:
I.e. the renderer
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TableRenderer has
a
static private class NavBar extends SelectRangeChoiceBarRenderer
That's a very good hint. So probably I'm just writing our own TableRenderer
and put our stuff
directly
SelectRangeChoiceRenderer (i.e.
MySelectRangeChoiceRenderer). The reason for this most probably is, that
it's not a
real component but more of a sub-component of the table...
Cheers, Carsten
Carsten Pieper wrote:
Harald wrote:
I.e. the renderer
Hi there,
as our applications still have to be compatible to IE6 we're quite unhappy
with
the tr:selectOneChoice as is makes use of the HTML select component which
is a pain in IE6 (IE6 being the culprit, not the select, of course; e.g. the
good
old z-index bug...).
So, here's my question:
Hello,
we want to overwrite Trinidad's default SelectRangeChoiceRenderer. We
already do this with other renderer. We have a class ExtendedCoreRenderKit
extends CoreRenderKit. In the constructor we are
calling the RenderKitBase's addRenderer(String family, String rendererType,
Renderer
Hi, a little question: According to the Trinidad documentation (e.g.
http://myfaces.apache.org/trinidad/trinidad-api/apidocs/org/apache/myfaces/trinidad/context/RequestContext.html#getTwoDigitYearStart()
here ) the year offset for parsing two
digit year entries is 1950. However, when I look
Oops, of course it should be out-of-date
Carsten Pieper wrote:
Does this mean, the documentation is out-out-date?
--
View this message in context:
http://www.nabble.com/-TRINIDAD--Conversion-of-two-digit-years-tp25959326p25969991.html
Sent from the MyFaces - Users mailing list archive
Hello,
we'd like to use tr:table with facet detailStamp but are not particularly
happy with the
default texts that come with it. In the CoreBundle.xrts (or, in our case,
the CoreBundle_de.xrts)
you find entries with the following keys:
af_table.DISCLOSED
af_table.UNDISCLOSED
Hi,
Trinidad's selectOneChoice ignores contentStyle settings if readOnly=true
(we're on Trinidad 1.0.10). Imho, this seems to be a bug. Or is it a feature
;-} ?
Best regards, Carsten
--
View this message in context:
Hi Florian,
although this is an older thread... Your solution seems to be interesting
but we're wondering whether it's only technically feasible in JSF 1.2?
(we're still on Trinidad 1.0.x)
If not, it would be very nice of you, if you could share some more details!
Thanks in advance,
Carsten
Hi,
we would like it very much, if we could really trigger the tr:panelPopup
from Java/server-side (in contrast to Renzo's original question no
menu or any other view member should be involved). Is this possible?
Background: We're using Trinidad in a portal environment in which
ordinary popups
/to the directory
workspace-dir/.metadata/.plugins/org.jboss.tools.common.model)
Hope that helps anyone else!
Carsten
http://www.nabble.com/file/p19857253/Palette.xml Palette.xml
http://www.nabble.com/file/p19857253/Preferences.xml Preferences.xml
Carsten Pieper wrote:
Hello Andrew,
If you have
Hello Andrew,
If you have the incentive, this would be a good WIKI page to write and
attach your palette.xml to that page.
I would like to do so, alas, I have been too hasty and didn't check
all functionality: On my colleagues computer everything runs fine,
but when we copy the Palette.xml to
-namejavax.faces.CONFIG_FILES/param-name
param-value/META-INF/faces-config.xml/param-value
/context-param
Everything including code assist for tags, attributes, beans and bean
properties works fine now!
Cheers, Carsten
Carsten Pieper wrote:
Hi Adil,
sorry for my late reply - have been
,
Did you remove the previous .classpath , .project, .setting and .metadata
files?
2008/9/23 Carsten Pieper [EMAIL PROTECTED]
Hello Adil, thanks for your message,
make sure that your project is a 2.5 dynamic web module
How do I achieve that? I looked around a bit and found this
http
focussed on question about the Eclipse JSF
tooling:
http://www.eclipse.org/newsportal/thread.php?group=eclipse.webtools.jsf
Carsten Pieper wrote:
But when I open the Web Perspective the only drawer in the Snippets
view (which
seems to be the equivalent of the Xxx Palette view) is JSP
/thread.php?group=eclipse.webtools.jsf
Carsten Pieper wrote:
But when I open the Web Perspective the only drawer in the Snippets
view (which
seems to be the equivalent of the Xxx Palette view) is JSP. No
Trinidad, no
Facelets, even no ordinary JSF stuff :-O
--
View this message
2.5 dynamic web module and don't
include JSF facet even if the project is a JSF one. So, you can't have jsf
functionnalities (visual editor, faces config editor...)
Regards,
Adil
2008/9/23 Carsten Pieper [EMAIL PROTECTED]
Answer to self:
Do only Dynamic Web Projects get the whole benefit?
Yes
Hi there,
does anyone know how to integrate MyFaces (especially Trinidad) tag
libraries
properly in RichFaces VE (Visual Editor)?
If there's some documentation in the
web a link would be welcome (I did quite some searching but couldn't find
anything that really helped me further than what I
Sidenote: We're on eclipse-jee-europa-winter release...
And RichFaces-VPE-win32-2.1.1.GA.zip (forgot to mention, sorry...)
Carsten Pieper wrote:
Hi there,
does anyone know how to integrate MyFaces (especially Trinidad) tag
libraries
properly in RichFaces VE (Visual Editor
Cagatay Civici wrote:
afaik, eclipse wtp 3.0 has visual support for Trinidad,
http://www.eclipse.org/webtools/releases/3.0.0/newandnoteworthy/jsf.php
On Fri, Sep 19, 2008 at 10:37 AM, Carsten Pieper
[EMAIL PROTECTED] wrote:
Sidenote: We're on eclipse-jee-europa-winter release
be a thing to evaluate.
-M
On Fri, Sep 19, 2008 at 4:35 AM, Carsten Pieper
[EMAIL PROTECTED] wrote:
Hello Cagatay,
thank you for the hint, but wtp 3.0 is for Ganymede
(http://wiki.eclipse.org/WTP_FAQ#What_version_of_Eclipse_does_WTP_work_with.3F)
and we're still on Eclipse Europa
example, this panelFormLayout shortDesc
even overrules the label tooltip if it's not defined at all.
Is this really meant to be like that??
Regards, Carsten
Carsten Pieper wrote:
Hi all,
is this a bug or a (strange?) feature?
Normally (or at least, how I expected things to be), when I
Hi all,
is this a bug or a (strange?) feature?
Normally (or at least, how I expected things to be), when I define a tooltip
on an inputText, inputDate, etc. via shortDesc, then the tooltip is shown
when the cursor hovers over either the label or the field. But as soon
as the inputXxx is nested
Hi,
probably this is related and might help: In some cases (portal environment,
but
browser-independent...) we also experienced problems with popup positioning
(using tr:panelPopup...).
We introduced a local patch for the trinidad-impl file
-SNAP and IE7)
( ) ... layout stays the same meaning: The page is still looking as it
should and the fidgeting has disappeared. Fix helped.
( ) none of the above
Thanks, Carsten
Matthias Wessendorf-4 wrote:
Hello Carsten,
On Fri, Apr 4, 2008 at 8:24 AM, Carsten Pieper
[EMAIL PROTECTED
Hi Paul,
thanks for the hint - yes, it might very well be related to TRINIDAD-992,
as your solution given there solves this problem, too!
Best regards,
Carsten
Carsten Pieper wrote:
Hi,
yes, TRINIDAD-992 is described as IE only!
Cheers, Carsten
Matthias Wessendorf-4 wrote
Hi,
this just seems to happen in Internet Explorer (tested in IE6):
Assume you have an tr:panelFormLayout with one or more tr:inputDate
components in it.
When you then press a button or a link, the inputDate causes some vertical
fidgeting.
To reproduce this, you can take the example code
/TRINIDAD-992
for which I have proposed a solution.
Carsten Pieper wrote:
Hi,
this just seems to happen in Internet Explorer (tested in IE6):
Assume you have an tr:panelFormLayout with one or more tr:inputDate
components in it.
When you then press a button or a link
2008/2/20, Carsten Pieper [EMAIL PROTECTED]:
Hi,
strange that nobody mentioned this before (at least I can't find any
posts
here
or in JIRA), the broken links seem to be there for quite a while...
I'm talking about the links in the top left navigation bar thing on the
pages
http
Carsten Pieper wrote:
Hi,
I filed the JIRA issue right now (took a while because I have been in
holidays...).
Cheers, Carsten
Forgot to mention the link:
https://issues.apache.org/jira/browse/TRINIDAD-1000
Carsten
--
View this message in context:
http://www.nabble.com
Hi Rafa,
if I get you right, you don't want to style the whole content of the
selectOneChoice
(which could be done via the selector af|selectOneChoice::content, as you
might
know...) but only some of those options.
As far as I know, there's no way to achieve this :-(
(no attribute styleClass
Hi Rafa,
Should I file a enhancement bug?
I'm only a user myself, so I can't really answer this. But indeed, I
could think of situations when the option to style options would come
in very handy...
Cheers, Carsten
Hi Carsten,
yes, that is right, I need to style only some options. Should I
Hi,
strange that nobody mentioned this before (at least I can't find any posts
here
or in JIRA), the broken links seem to be there for quite a while...
I'm talking about the links in the top left navigation bar thing on the
pages
http://myfaces.apache.org/trinidad/trinidad-api/tagdoc.html (tag
Thus, whatever browser hack you might try (e.g. * html
af|inputDate::launch-icon ...)
- and which well makes it to the generated .css - is overwritten by the
img's
style-attribute :-(
Has anyone have any clue how to skin icons for different browsers currently?
Thanks, Carsten
Carsten Pieper
be touched as browser
hacks won't be
needed anymore once http://issues.apache.org/jira/browse/TRINIDAD-495
(@platform
support for skinning icons) and
http://issues.apache.org/jira/browse/TRINIDAD-799
(Add agent version support in skinning) are resolved?
Thanks, Carsten
Carsten Pieper wrote:
Hi
Hi,
in some cases the nice @agent feature can't help your skinning efforts for
different browsers, for example if you want to
differentiate between different versions of Internet Explorer (see this
thread:
http://www.nabble.com/Skinning-for-specific-%40agent-_versions_---to13572999.html)
or
Hi,
I have been fiddling around with the improved tree skinning recently.
Looks fine (thanks to Cristi!), but I have a question concerning the
alignment of those node-icons (e.g. look here, if in doubt what these
might be:
, Carsten Pieper [EMAIL PROTECTED]
wrote:
Hi,
I have been fiddling around with the improved tree skinning recently.
Looks fine (thanks to Cristi!), but I have a question concerning the
alignment of those node-icons (e.g. look here, if in doubt what these
might be:
http://www.nabble.com/Tree
Hi again,
in the Maven console stuff that I attached, there were also hints on new
things from
myfaces-core-project:1.1.6-SNAPSHOT.
When I change the entry in my pom.xml to this:
!-- myfaces-impl --
dependency
of your projects have a dependency on *myfaces*
snapshots then you might also have ended up downloading these, which could
possibly be affecting your app. Check the timestamp on the myfaces jars in
your local repo (~/.m2/...).
Regards,
Simon
Carsten Pieper [EMAIL PROTECTED] schrieb
Hi,
(this topic has been dealt with before:
http://www.nabble.com/Problems-with-Maven-Pluginstf4769772.html
Well, in fact, is hasn't really been dealt with, probably nobody reacted
because
of the misleading subject problems with Maven Plugins. That's why I
reopen
it with a more appropriate
Hi, simple question this time...
Many Trinidad components offer an attribute accessKey. Documentation just
speeks of its type as character resp. char. I fiddled around with this
for a little while and came to this conclusion:
Character here means plain old English characters A-Z (no special
+ä didn't work in FF2.
replacing ä w/ a and doing ALT+SHIFT+a wörks :-)
On 11/7/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi, simple question this time...
Many Trinidad components offer an attribute accessKey. Documentation
just
speeks of its type as character resp. char. I fiddled
Wouldn't a method in your API like getAllRowKeys() be advisable?
+1 from us, such a method would really be helpful!
Maik77 wrote:
Hi Matthias,
so it is the way, that I have to implement a loop where I have to use
setRowIndex() and getRowData() for every row and child (check with
Hi,
probably a very simple question, but I can't find anything relevant...
There are selectors for numeric stuff in table column, e.g.
af|column::cell-number
af|column::header-number
I have something like:
tr:column headerText=bigDec
in the
tr:column.
Regards,
Venkata
On 9/12/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi,
probably a very simple question, but I can't find anything relevant...
There are selectors for numeric stuff in table column, e.g.
af|column::cell-number
af|column::header-number
I have
,
this might be a browser-related issue. Did you check both FF and IE?
Is there any difference? is a short-desc supported in a td at all?
regards,
Martin
On 9/4/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi everyone,
either this is a bug or I'm not using it correctly, so:
How
Hi,
this is the situation:
tr:table value=#{search.resultList} var=person
tr:column headerText=Name width=10%
tr:outputText value=#{person.name}/tr:outputText
/tr:column
!-- more columns --
/tr:table
When now the bean return value for the outputText's value is null
in my example, you're welcome to give
a hint
but most probably the public should ignore this thread and let me find chase
my own bug...
Carsten
Carsten Pieper wrote:
Hi,
this is the situation:
tr:table value=#{search.resultList} var=person
tr:column headerText=Name width=10
]--
span class=af_outputText null title=some tooltip John Doe/ span
/td
And, as stated before, for the null value case, the table rows in Firefox
get
too high...
Any ideas welcome, thanks,
Carsten
Carsten Pieper wrote:
Argh,
BTW, I turned on my custom
skin to exclude homegrown issues (thus, I
Hi everyone,
either this is a bug or I'm not using it correctly, so:
How is the attribute shortDesc in tr:column supposed to work?
I have something like
tr:column headerText=Title shortDesc=My column tooltip
...
/tr:column
and I never see this column tooltip, neither on the header nor on
Hi everyone,
we sometimes need buttons without a text (in their disabled state we don't
want to
show the text, just an icon in its disabled form). A code snippet might look
like this
(ignoring icons...):
tr:panelBorderLayout
f:facet name=bottom
Wow... you're right... JIRA issue please.
Done (https://issues.apache.org/jira/browse/TRINIDAD-631)
Best regards,
Carsten
--
View this message in context:
http://www.nabble.com/-Trinidad--Skinning---no-CSS-selector-for-tr%3AoutputText--tf4247489.html#a12177494
Sent from the MyFaces - Users
the text normally
super.encodeAll(context, rc, component, bean);
// Close the wrapping span element
writer.endElement(span);
}
}
Regards,
~ Simon
On 8/13/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi,
as most of you might have
Hi,
for me these selectors (no focus on the style definitions here...) worked:
af|column::cell-text, af|column::cell-number, af|column::cell-icon-format {
-tr-rule-ref: selector(AFMediumBackground:alias);
}
af|column::cell-text-band, af|column::cell-number-band,
still seems to function properly, but I got the
impression, that afterwards
something else is called, which then resets the shortDesc to just the
shortDesc :-O
Any ideas?
Thanks in advance,
Carsten
Carsten Pieper wrote:
Thanks a lot for the valued advice, Simon and Martin,
so I'll have a go
()
{
super(CoreInputText.TYPE);
}
Help would be greatly appreciated,
Carsten
Carsten Pieper wrote:
Hi,
as Simon adviced, I'm implementing the getXyz(FacesBean) methods now. In
my
new OutputTextSkinnedRenderer (extending CoreOutputTextRenderer) this
method
worked fine (if no tooltip
)
{
super(type);
}
@Override
protected String getShortDesc(FacesBean bean)
{
return super.getShortDesc (bean) + whateverExtraInfo;
}
}
Regads,
~ Simon
On 8/14/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi,
I tried to debug the strange InputTextRenderer
what the markup/JS/CSS looked like for this to
work in CIS (your existing web-framework)? Maybe we could replicate it
from there?
regards,
Martin
On 8/13/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi Adam,
perhaps I should be a little more speicific:
We want to be able to delimit
Hi Martin,
yes, that works, thank you!
Some thoughts, though: Without touching the renderer this would mean that
(as in your example) the inputText's attribute readOnly must not be set or
else the effect of these onxxx methods returning false would be bypassed.
When chosing to extend the
=readOnly/tr:inputText
Cheers, Carsten
-
Carsten Pieper wrote:
Hi Martin,
yes, that works, thank you!
Some thoughts, though: Without touching the renderer this would mean that
(as in your example) the inputText's attribute readOnly must not be set or
else the effect of these onxxx methods
writer.endElement(span);
}
}
Regards,
~ Simon
On 8/13/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hi,
as most of you might have noticed the topic of this thread somehow
drifted
from
tr:outputText to tr:inputText...
Anyhow, I implemented my option 2
wrote:
Generally speaking, you don't want to do this for
outputText: you want to style parent components
and/or the default font of the skin, not the outputText
itself.
-- Adam
On 8/10/07, Carsten Pieper [EMAIL PROTECTED] wrote:
OK, thanks for the speedy answer!
So it look's we should
or
styleClass attributes available on the TAG / COMPONENT
-M
On 8/10/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hello everyone,
I have been trying to skin the tr:outputText but haven't been able to
find a
fitting selector. At first, I intuitively tried af|outputText but to no
avail. I could
Hello everyone,
I have been trying to skin the tr:outputText but haven't been able to find a
fitting selector. At first, I intuitively tried af|outputText but to no
avail. I could neither find anything in the selectors' list (i.e.
the link Simon gave recently:
Hello everyone,
is this a bug or am I missing something? The situation is as follows:
tr:inputText label=My short inputText value=Hello inputText
contentStyle=width: 50px; readOnly=true
/tr:inputText
The text then exceeds the actual text area as shown in the
wrote:
Hi Carsten,
what is the rendered HTML-output of both cases for this field?
regards,
Martin
On 8/8/07, Carsten Pieper [EMAIL PROTECTED] wrote:
Hello everyone,
is this a bug or am I missing something? The situation is as follows:
tr:inputText label=My short inputText
-only fields,
or increase the width (problem can still exist if the value is of
greater length), or use tr:outputText when you want it to be read-only(I
guess this is the best).
Thanks.
~Sandeep
-Original Message-
From: Carsten Pieper [mailto:[EMAIL PROTECTED]
Sent: Wednesday
Thanks Martin,
yes, clipping helps in a way, but things really seem to become complicated
then.
Clipping plus absolute positioning (which seems to be required by clip to
work)
and then, for some reason, I had to fiddle with the margins, too, which
leads to this
(still everything done directly in
Hi Martin,
you might also want to try with:
display:block;
overflow:hidden;
yes, that seems nicer, thanks again!
So, to sum up, the only way to get the complete text out with read-only
fields
who aren't long enough for the actual text, is to provide it via the tooltip
(shortDesc)?
Best
Carsten wants to have the exact number of pixels, I heavily suppose ;)
You bet! That's why they call me the Pixel-Schubser (pixel jostler?)
'round here ;-)
Carsten
--
View this message in context:
Hi Matt,
thanks for the insight. Well, it seems we have to accept this behaviour
then.
Coming from a framework that heavily depended on iframes I'm having a hard
time getting used to these things ;-}
Best regards,
Carsten
--
View this message in context:
Hi everyone,
we're having problems in getting the tr:panelAccordion to behave as we want
it to, which is this:
The panelAccordion should stretch (vertically) above the whole height of ist
parent container.
The expanded item should get all the inner place (we don't define
discloseMany, so only
Hi Abhi,
we're using it in a facelet context (maybe I should have mentioned that
earlier...). My XHTML source looks like this:
?xml version=1.0 encoding=ISO-8859-1?
ui:composition title=Apache MyFaces Trinidad Archetype Demo
xmlns=http://www.w3.org/1999/xhtml;
76 matches
Mail list logo