well, I refactored the old RenderingContext into more simple classes and
with a lot less dependencies
my approach was also Decorating existing renderers
but for Tomahawk, I did one generic Renderer for all components, based on
reflection
it just searches for any Class' or 'StyleClass' ending
Hi,
I just added the first things to Brett's vmbuild box.
vmbuild1.apache.org
please request an account, if you like.
Brett is the admin, to grant rights.
-Matthias
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Hi,
Now that ChangeManager supports the core operations like
Add/Remove/Reorder. But it would be nice to have a support for the Move
operation also.
With this, one can persist the moving of a component from one container
to another.
Effectively the move operation involves the two changes to
Hi,
I remember there was a build issue, when building Trinidad w/ java 6
see jira:
https://issues.apache.org/jira/browse/TRINIDAD-65
The new continuum server is running w/ Java 6..
For now, we don't deploy the artifacts, built by vmbuild-server, to
the m2-snapshot repo, just testing that no
Freemarker Template rendering enabled by default whenever Sandbox is added to
project
-
Key: TOMAHAWK-1070
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1070
Make JSP 2.1 optional
--
Key: MYFACES-1693
URL: https://issues.apache.org/jira/browse/MYFACES-1693
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-252
Affects Versions: 1.2.0
[
https://issues.apache.org/jira/browse/TOMAHAWK-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516901
]
Martin Marinschek edited comment on TOMAHAWK-1070 at 8/1/07 2:02 AM:
-
I've
[
https://issues.apache.org/jira/browse/TOMAHAWK-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516901
]
Martin Marinschek commented on TOMAHAWK-1070:
-
I've only now seen that the template renderer was
Myfaces 1.2 doesn't start without web.xml
-
Key: MYFACES-1694
URL: https://issues.apache.org/jira/browse/MYFACES-1694
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-252
Hi *,
maybe someone of you has a short answer - is there a way to disable
the JavaScript obfuscator in Trinidad? For debugging, I'd rather see
the full JavaScript-code. I suspect it's a simple switch, but I don't
seem to find it... do I have to configure the maven-javascript-plugin,
or can I do
Enhance TrNumberConverter, by providing accessors
-
Key: TRINIDAD-137
URL: https://issues.apache.org/jira/browse/TRINIDAD-137
Project: MyFaces Trinidad
Issue Type: Improvement
Affects
[
https://issues.apache.org/jira/browse/TRINIDAD-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-2.
---
Resolution: Fixed
Fix Version/s: 1.0.2-core
Broken client decimal number
[
https://issues.apache.org/jira/browse/TRINIDAD-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516930
]
Matthias Weßendorf commented on TRINIDAD-2:
---
luka confirmed it works now
Broken client decimal number
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project myfaces has an issue affecting its community integration.
This issue affects 2
I use the t:dataScroller tag ,I find that the the #{displayedRowsCountVar}
display wrong number in my query
---
Key: TOMAHAWK-1071
URL:
Alignment for label
---
Key: TOBAGO-459
URL: https://issues.apache.org/jira/browse/TOBAGO-459
Project: MyFaces Tobago
Issue Type: Improvement
Components: Core
Affects Versions: 1.0.12
Environment: All
Thanks a lot!
regards,
Martin
On 8/1/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
given the fact that this is useful,
I'd not mind to make it *public*
-M
On 8/1/07, Danny Robinson [EMAIL PROTECTED] wrote:
That also prompts a question. Should we change
That also prompts a question. Should we change
org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION
to
org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION
Given this is so critical to successful skinning, shouldn't we make it a
public setting?
Danny
On 8/1/07, Danny Robinson
given the fact that this is useful,
I'd not mind to make it *public*
-M
On 8/1/07, Danny Robinson [EMAIL PROTECTED] wrote:
That also prompts a question. Should we change
org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION
to
Here's the two settings I use, one for javascript and another for css
compression.
context-param
param-nameorg.apache.myfaces.trinidad.DEBUG_JAVASCRIPT/param-name
param-valuetrue/param-value
/context-param
context-param
param-name
Along the same lines, I think we should move the iframe popup's context
param to .trinidad rather than .trinidadinternal as well. Actually, I don't
think any context param should be namespaced in trinidadinternal.
Regards,
Simon
On 8/1/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Thanks a
that's fine.
has been non-public s long :-)
On 8/1/07, Danny Robinson [EMAIL PROTECTED] wrote:
Prior to 1.0.2 being released I guess.
On 8/1/07, Simon Lessard [EMAIL PROTECTED] wrote:
Along the same lines, I think we should move the iframe popup's context
param to .trinidad rather than
Yeah, I would so it doesn't fall through the cracks. There are a number
of JIRA issues logged which I haven't really thought about fixing yet.
I'm not sure it needs to be fixed for the next release (especially
because I'm assuming I'll have some 301 work to do when we get the
bridge checked
Aw, crud... so we will need to address this, but can we do
it after 1.0.2? It's pretty important that the build does
deploy the artifacts, otherwise we get failures when
when need to take a plugin snapshot.
-- Adam
On 8/1/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I remember
Hello,
yes, after 102 that's fine.
the build does no deployment, because the box is new.
not production ready he wrote me :-)
They're aware of the deployment issue and they'll offer a working solution.
(they=apache infra team)
I just added Trinidad, because of random failures on the zone. It's
Things should be trinidadinternal if we don't want to
document or support them; but if we need to doc and
support them, I totally agree - they've got to be
in trinidad.
-- Adam
On 8/1/07, Simon Lessard [EMAIL PROTECTED] wrote:
Along the same lines, I think we should move the iframe popup's
I'd love to see this exposed, and I think it'd be a great thing for the JSF
community. It's also something we could look at during the development of
JSF 2.0.
~~~
Kito D. Mann - Author, JavaServer Faces in Action
Hi everybody.
There has been a post recently regarding [Trinidad] page refresh
on return from a dialog. I have a similar problem that I am trying to
solve... but since I am looking for something slightly different than
just refreshing the same page, I am starting a different post so
Hi Cristi
In order to give you feedback, and gain some feedback too, I have some
comments and questions about this topic:
You wrote:
my approach was also Decorating existing renderers
but for Tomahawk, I did one generic Renderer for all components, based on
reflection
it just searches for any
FF - add agent capability that FF supports legends and fieldsets
Key: TRINIDAD-138
URL: https://issues.apache.org/jira/browse/TRINIDAD-138
Project: MyFaces Trinidad
Issue
Well the nice thing was that I don't need to define the selectors statically
somewhere
f.e. the selectors for tomahawk are made on this rule:
mf|fully_qualified_component_Class::style_property_name:css_pseudo_class
mf - is the prefix from MyFaces
fully_qualified_component_Class - is the full
David,
Instead of calling sendRedirect(), in your return listener
you could simply get the NavigatioHandler and invoke it
directly:
nh.handleNavigation(context, null, afterDialogOutcome);
... and any navigation rule attached to that outcome will happily
fire, redirect or no (it'll get turned
Oh, OK. Thanks Adam. I thought the sendRedirect() might have been
required because it was a partial submit.
But what about the thoughts around separating the launching of a
dialog from the actual action of the button? With the way that I would
like to use the dialog, it seems
Hello both of you,
We might have to deal with that redirect automatically even with
NavigationHandler though. We had the issue recently in a project where we
were losing our hidden parameters because of that, resulting in some nasty
effect that could only be solved by forcing the user to accept a
Matthias, could you get some bits ready for us to vote on?
Thanks, Adam
On 7/31/07, Simon Lessard [EMAIL PROTECTED] wrote:
I agree, and dragging the popup around will be a shiny feature for the next
release, while we have a decent amount already for this one. So
+1 to start a vote.
On
Hi Cristi!
Here are some comments about this:
Well the nice thing was that I don't need to define the selectors statically
somewhere
f.e. the selectors for tomahawk are made on this rule:
mf|fully_qualified_component_Class::style_property_name:css_pseudo_class
I get to the same selector
smart boy, you figured it out
yes, I try to get the translated styleClass and if I don't get anything, I
do nothing
about ..Classes properties
as mentioned above I try to get 'rowClass1', 'rowClass2' and so on until I
don't get the translated styleClass
about registering renderers
well, I have a
You might want to look at the Redirect-Tracker in MyFaces for inspiration.
regards,
Martin
On 8/1/07, Simon Lessard [EMAIL PROTECTED] wrote:
Hello both of you,
We might have to deal with that redirect automatically even with
NavigationHandler though. We had the issue recently in a project
[
https://issues.apache.org/jira/browse/MYFACES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517111
]
Martin Marinschek commented on MYFACES-1689:
Brilliant! I really love the results, plus played around
[
https://issues.apache.org/jira/browse/MYFACES-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517110
]
Martin Marinschek commented on MYFACES-1688:
Brilliant! I really love the results, plus played around
[
https://issues.apache.org/jira/browse/MYFACES-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517114
]
Martin Marinschek commented on MYFACES-1688:
Hi Sorin,
very good - I like both the algorithm you
[
https://issues.apache.org/jira/browse/MYFACES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Marinschek updated MYFACES-1689:
---
Resolution: Fixed
Fix Version/s: 1.1.6-SNAPSHOT
Assignee: Martin
[
https://issues.apache.org/jira/browse/MYFACES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517112
]
Martin Marinschek commented on MYFACES-1689:
Sorin,
can you do me one favor - can you checkout the
43 matches
Mail list logo
