[
https://issues.apache.org/jira/browse/TOMAHAWK-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Marinschek resolved TOMAHAWK-1069.
-
Resolution: Fixed
Fix Version/s: 1.1.7-SNAPSHOT
Assignee:
[
https://issues.apache.org/jira/browse/MYFACES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Silaghi updated MYFACES-1689:
---
Status: Patch Available (was: Open)
Reload of web.xml file if changes are detected
[
https://issues.apache.org/jira/browse/MYFACES-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516654
]
Martin Marinschek commented on MYFACES-1689:
This looks very good now - one thing is still missing,
Hello
I just hope that if the internal system can send me a notification
mail that my patch has been submitted (This will be very great) to
continue working at the next features.
here it is:
http://tinyurl.com/2job68
via the svn commit emails (there is a mailing list for that ([1]).
-M
[1]
Database in Schedule Tomahawk
Search:
Hi, i am very new jsf an java, so i am making a project using schedule from
tomahawk myfaces, and i need some help in puting a database to read de
entries and save. i am using hibernate and mysql.
If someoane have any examples to help me...i apreciate.
Tks
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'll write up a JIRA ticket on this.
On 7/30/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Yes, Trinidad is fine - just use ViewHandler.createViewRoot()
regards,
Martin
On 7/30/07, Adam Winer [EMAIL PROTECTED] wrote:
OK, yes, but Trinidad *does not need an alternative ViewRoot*.
So,
StateManagerImpl is not fully compatible with JSR-301
-
Key: TRINIDAD-134
URL: https://issues.apache.org/jira/browse/TRINIDAD-134
Project: MyFaces Trinidad
Issue Type: Bug
Add non-final getPartialTriggers method to XhtmlRenderer
Key: TRINIDAD-135
URL: https://issues.apache.org/jira/browse/TRINIDAD-135
Project: MyFaces Trinidad
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/TRINIDAD-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved TRINIDAD-135.
Resolution: Fixed
Applied the path to the trunk.
Add non-final getPartialTriggers
Add ability to move lightweight dialogs around the page
---
Key: TRINIDAD-136
URL: https://issues.apache.org/jira/browse/TRINIDAD-136
Project: MyFaces Trinidad
Issue Type: Improvement
Hi,
I noticed the issue in the past as well,
but I tried Sunday evening, with trunk worked here (at least)
can one test as well ?
-Matthias
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
[
https://issues.apache.org/jira/browse/TRINIDAD-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516709
]
Martin Marinschek commented on TRINIDAD-2:
--
Matthias has just posted on the dev-list that this worked for
[
https://issues.apache.org/jira/browse/TRINIDAD-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-133.
-
Resolution: Fixed
Fix Version/s: 1.2.2-core
Completed: At revision: 561398
All,
I think we're about ready to release Trinidad 1.0.2. Any
thoughts on the subject? If not, I'll start a vote.
-- Adam
Hello Cristi,
It would sure be nice to have an independent common skinning module for
custom component libraries. However, I wonder what version of the skinning
module you used and how you handled dependencies while refactoring it
because there's many changes with skinning with every releases.
The rendering capabilities are set in the CoreRenderingContext in the
_initializeAgent method. This is based off of the outputMode which is
returned by the RequestContext. Basically the capabilities for
TrinidadAgent.CAP_PARTIAL_RENDERING are set to false on the Trinidad
agent and there are
I'd like to get 'movable' lightweight dialog feature in, also I think we
could do with adding a 'X' icon to close the dialog, much like its
heavyweight brother. Other than that, I'd be +1.
On 7/31/07, Adam Winer [EMAIL PROTECTED] wrote:
All,
I think we're about ready to release Trinidad
Those'd be great features... but can they weight 'til 1.0.3?
We don't always have to wait this long for a release - it's
mostly that the XMLHttp stuff could be destabilizing (and was,
to some extent)...
-- Adam
On 7/31/07, Danny Robinson [EMAIL PROTECTED] wrote:
I'd like to get 'movable'
CAP_PARTIAL_RENDERING is only partly used these days - it
once was followed religiously, as all Java code rendered both
PPR and non-PPR versions, but now some code now only renders
PPR markup and relies on the client code to switch back to
full page rendering if needed.
-- Adam
On 7/31/07,
Hi Scott,
but essentially, with all these checks in place, still the
partialPageSubmit function is rendered out in this part of the code.
Therefore, only client-side code can change something about the
partial page submit, which it doesn't, if _checkLoadNoPPR is not
called.
regards,
Martin
On
yes, and exactly such a piece of code I must have found - obviously
the client-side switch to full page submit is not fully implemented in
the portlet case.
regards,
Martin
On 7/31/07, Adam Winer [EMAIL PROTECTED] wrote:
CAP_PARTIAL_RENDERING is only partly used these days - it
once was
I am fine with starting the release procedure
1.0.2 of plugins, followed by 1.0.2 of core
-Matthias
On 7/31/07, Adam Winer [EMAIL PROTECTED] wrote:
Those'd be great features... but can they weight 'til 1.0.3?
We don't always have to wait this long for a release - it's
mostly that the XMLHttp
Martin,
So I guess my question is, then, why aren't you using the body renderer?
I suppose that we could switch the partialPageSubmit function itself
based on the capabilities. It's not something I did initially.
Scott
Martin Marinschek wrote:
Hi Scott,
but essentially, with all these
Adam,
I know, but the functionality of the partialSubmit javascript changes
based on capability. So any renderer using this function will do a full
page submit instead of a partial one. This means that only when the
full page submit is unacceptable does a component need to worry about
OK, that works too.
+1
On 7/31/07, Adam Winer [EMAIL PROTECTED] wrote:
Those'd be great features... but can they weight 'til 1.0.3?
We don't always have to wait this long for a release - it's
mostly that the XMLHttp stuff could be destabilizing (and was,
to some extent)...
-- Adam
On
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 7/31/07, Danny Robinson [EMAIL PROTECTED] wrote:
OK, that works too.
+1
On 7/31/07, Adam Winer [EMAIL PROTECTED] wrote:
True. And unfortunately, we don't require any special root
component for PPR.
For 1.0.3, I'd like to look at adding support for booting up
parts of the RenderingContext on the fly, during rendering,
so that we're no longer quite so dependent on having
FormRenderer or BodyRenderer execute for
Hey, that's an interesting idea. It's so crazy it just might work.
For the short term, I'm sure we can modify the _partialPageSubmit script
to just call the full submit script. I looked at doing that when I
first added in the portal code, but the current mechanism seemed to work
correctly
Hello Cristi
I'm working in adding skinning support to non trinidad components like
tomahawk and sandbox components like you did (as a part of a Google Summer
of code project), but using a different approach. I'm not an expert, just a
student that wants this behaviour in my projects to simplify
right,
also, do you've documentation already ?
On 7/31/07, Simon Lessard [EMAIL PROTECTED] wrote:
Hello Cristi,
It would sure be nice to have an independent common skinning module for
custom component libraries. However, I wonder what version of the skinning
module you used and how you
Hi guys,
sure, both propositions will work. For now (and for my purposes, and
maybe also the one of others who have followed this thread), also my
workaround does.
However, should I file an issue, so that you have something you can
rely on if need be?
regards,
Martin
On 8/1/07, Scott O'Bryan
32 matches
Mail list logo
