Hi guys,
I am saying this in a broader scope - not only for the AJAX features.
But our AJAX features which do make sense out of the box (and this one
does) could also be enabled like this.
best regards,
Martin
On 8/2/10, Werner Punz werner.p...@gmail.com wrote:
Hi Martin this would make only
Btw. Martin, I already gave Ed all the needed info and code on how to
implement it so that they can get everything into the spec for 2.1
(which hopefully will happen)
I think the entire issue of not being able to support a fileupload in
the non ajax and ajax case in stock jsf has been going
Hi Martin,
From what I understand the feature is disabled as long as you don't set
myfaces.config[transportAutoSelection] = true;
So why have a second param to do the same thing?
Best regards,
Ganesh
Martin Marinschek schrieb:
Perfect.
Can we talk about having the context param
Btw. another thing, I tried to enable fileupload via xhr level2
(upcoming xhr extension in html5) I was able to send the form data but
unfortunately the sent multipart form request was missing some vital
meta information and broke the spec, on both implementations I could
grasp (Firefox4 and
Hi Martin this would make only sense if we had a bunch of features which
can be turned on via such a switch, which we don´t from my perspective
because the queue control features which we have internally
cannot be turned on switch like but have to be configured with params
like
Perfect.
Can we talk about having the context param STRICT_COMPATIBILITY_MODE
again, where this is disabled, and if the param is set to false, this
feature is enabled?
best regards,
Martin
On 7/30/10, Jakob Korherr jakob.korh...@gmail.com wrote:
Really great, Werner!
2010/7/30 Hazem Saleh
Hi... theoretically it would be possible to use both at the same time.
The idea is that I have a clear boundary between api and impl. The API
is just a loosely coupled facade which routes into impl.
(I am not sure if I dont call api functions in impl though)
I could decouple it even stronger
Also if you want to use the helpers from the core, they have a double
include prevention, so what you can use is theoretically the _Runtime.js
_Lang.js, _ExtLang.js, _Dom.js (mostly in that order) they are not
directly related with the implementation but are the foundations.
But I cannot
kick ass!
great stuff, Werner!
-Matthias
On Fri, Jul 30, 2010 at 12:58 PM, Werner Punz werner.p...@gmail.com wrote:
Hello, as some people might have noticed I recently integrated the Ajax
fileupload into our trunk (2.0.2-SNAPSHOT), I also gave the code to the JSF
EG so that it might be part
Wonderful!
On Fri, Jul 30, 2010 at 2:10 PM, Matthias Wessendorf mat...@apache.orgwrote:
kick ass!
great stuff, Werner!
-Matthias
On Fri, Jul 30, 2010 at 12:58 PM, Werner Punz werner.p...@gmail.com
wrote:
Hello, as some people might have noticed I recently integrated the Ajax
Really great, Werner!
2010/7/30 Hazem Saleh haz...@apache.org
Wonderful!
On Fri, Jul 30, 2010 at 2:10 PM, Matthias Wessendorf mat...@apache.orgwrote:
kick ass!
great stuff, Werner!
-Matthias
On Fri, Jul 30, 2010 at 12:58 PM, Werner Punz werner.p...@gmail.com
wrote:
Hello, as some
Hi
I would like to know if someone has ideas about how to include the myfaces
core javascript code (partially) into tomahawk or other jsf library.
It seems to be the same problem as we have with shared (maybe use maven
shade plugin?). There is a cool api on myfaces core that someone wants to
use
Hi
Good stuff Werner!
regards,
Leonardo
2010/7/30 Leonardo Uribe lu4...@gmail.com
Hi
I would like to know if someone has ideas about how to include the myfaces
core javascript code (partially) into tomahawk or other jsf library.
It seems to be the same problem as we have with shared
13 matches
Mail list logo
