headers
Sylvain Wallez | 1 Oct 10:48
Picon
Favicon

Re: CForms: on-action handling

Simone Gianni wrote:
> Hi Vadim,
> I can't remember, but without validating before executing it's
> possible to make buttons like "Fill with default values" or "Use the
> same address for delivery" which could not be possible if the form
> gets validated before performing the action. Wasn't there a
> validate="true|false" attribute on actions?

Yup, you're right. Actions can change the contents of the form, and thus
validation occurs after actions are run.

As for the validate="true|false", it is meant to allow actions that
should exit form.show() without even trying to validate. This for
actions such as "cancel".

> Vadim Gritsenko wrote:
>> Hi All,
>>
>> Just recently noticed that on-action events are fired before form is
>> validated :)
>>
>> Can anybody recall the reason why this was done? Any reason why not
>> do it after validation? Since most of the time actions will
>> manipulate forms content, it makes sense to validate complete form
>> first, or so it seems. WDYT?

--

-- 
Sylvain Wallez - http://bluxte.net
(Continue reading)

Permalink | Reply | 1 comment |
headers
Vadim Gritsenko | 1 Oct 13:29

Re: CForms: on-action handling

Sylvain Wallez wrote:
> Simone Gianni wrote:
>> I can't remember, but without validating before executing it's
>> possible to make buttons like "Fill with default values" or "Use the
>> same address for delivery" which could not be possible if the form
>> gets validated before performing the action.

How validation would prohibit changing the form data?

>> Wasn't there a
>> validate="true|false" attribute on actions?
> 
> Yup, you're right. Actions can change the contents of the form, and thus
> validation occurs after actions are run.

And after that form is displayed again, and will get re-validated on next user 
action, so it does not seem like a show stopper.

The only scenario I can think of which might cause a problem: If above mentioned 
delivery address is mandatory, it would be marked as invalid before action fills 
it in. But after action sets its value, validation error will be cleared anyway.

> As for the validate="true|false", it is meant to allow actions that
> should exit form.show() without even trying to validate. This for
> actions such as "cancel".

Nope, "validate" flag is defined only on submit widgets currently, not on actions.

Now, it is possible to define it on action widgets as well (in case if current 
"pre-validate" actions are deemed necessary).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Carsten Ziegeler | 1 Oct 16:04
Picon
Favicon

Re: FYI : MNG-1797 fixed in latest snapshots

Nice!

I haven't followed the Maven mailing lists lately - is there any
timeframe for a 2.0.5 release?

Carsten

Jorg Heymans wrote:
> I haven't had a chance to test it out (will do so at the hackathon),  
> but according to http://jira.codehaus.org/browse/MNG-1797 it seems  
> that you can now safely exclude a dependency without wrecking the  
> rest of your build - how cool is that :-P
> 
> 
> Jorg
> 
> ps Snapshots can be downloaded from http://maven.zones.apache.org/ 
> ~maven/builds/branches/maven-2.0.x/
> 

--

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Permalink | Reply | 1 comment |
headers
Joerg Heinicke | 1 Oct 16:55
Picon
Picon

Re: [RT] Simplify flow usage

On 29.09.2006 09:19, Carsten Ziegeler wrote:

> Now what about the other directories we currently have:
> config/spring, config/xconf and config/properties?
> Should we leave them where they are or move them one directory up?

I'd prefer the flat variant, i.e. without config subdir.

Jörg
Permalink | Reply | 3 comments |
headers
Vadim Gritsenko | 2 Oct 09:51

Re: BUILD SUCCESSFUL (Was: Maven info wanted)

Jorg Heymans wrote:
> On 30 Sep 2006, at 15:03, Jean-Baptiste Quenot wrote:
> 
>> Did  you turn  on  Maven's  offline mode?   In  my experience  the
>> offline  mode is  not  reliable,  you often  have  to switch  back
>> online, and  then you  don't have the  same build  duration!  It's
>> something  I  can't bear  with  Maven  2:  why bother  doing  HTTP
>> requests as the jar is already fetched?!
> 
> Does this really matter? How often during development of a typical 
> webapplication do you invoke your build system?

At least once for each commit ;-)

At least that's how it should be. Since it's too slow, I'm now resolved to doing 
it once a week :-P

Vadim
Permalink | Reply | 0 comments |
headers
Lars Trieloff (JIRA | 2 Oct 10:13
Picon
Favicon

[jira] Created: (COCOON-1922) [PATCH] cocoon-core-sample should be part of the default build, because it is required by the default example webapp

[PATCH] cocoon-core-sample should be part of the default build, because it is required by the default
example webapp
--------------------------------------------------------------------------------------------------------------------

                 Key: COCOON-1922
                 URL: http://issues.apache.org/jira/browse/COCOON-1922
             Project: Cocoon
          Issue Type: Bug
          Components: * Cocoon Core
    Affects Versions: 2.2-dev (Current SVN)
            Reporter: Lars Trieloff
         Attachments: cocoon-core-samples-in-default-build.patch

The cocoon-webapp depends on cocoon-core-sample, but this is not part of the default build, causing a mvn
install in trunk to fail.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 2 comments |
headers
Lars Trieloff (JIRA | 2 Oct 10:13
Picon
Favicon

[jira] Updated: (COCOON-1922) [PATCH] cocoon-core-sample should be part of the default build, because it is required by the default example webapp

     [ http://issues.apache.org/jira/browse/COCOON-1922?page=all ]

Lars Trieloff updated COCOON-1922:
----------------------------------

    Attachment: cocoon-core-samples-in-default-build.patch

This patch adds cocoon-core-sample to the default build profile.

> [PATCH] cocoon-core-sample should be part of the default build, because it is required by the default
example webapp
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: COCOON-1922
>                 URL: http://issues.apache.org/jira/browse/COCOON-1922
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Lars Trieloff
>         Attachments: cocoon-core-samples-in-default-build.patch
>
>
> The cocoon-webapp depends on cocoon-core-sample, but this is not part of the default build, causing a mvn
install in trunk to fail.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniele Madama (JIRA | 2 Oct 12:25
Picon
Favicon

[jira] Commented: (COCOON-1314) Validation on HTMLArea fields doesn't work correctly

    [ http://issues.apache.org/jira/browse/COCOON-1314?page=comments#action_12439086 ] 

Daniele Madama commented on COCOON-1314:
----------------------------------------

Hi,
I try with the actual 2.1.10-dev (Revision: 451904) and I check the htmlarea sample at
http://localhost:8888/samples/blocks/forms/htmlarea; I don't get the '<br/>' tag but a 'nbsp;' in
the data1 response. 
Lookin for where it get this value, I  see at
src/blocks/forms/resources/org/apache/cocoon/forms/resources/htmlarea/htmlarea.js,
changing in the follow way

Index: src/blocks/forms/resources/org/apache/cocoon/forms/resources/htmlarea/htmlarea.js
===================================================================
--- src/blocks/forms/resources/org/apache/cocoon/forms/resources/htmlarea/htmlarea.js  
(revision 451904)
+++ src/blocks/forms/resources/org/apache/cocoon/forms/resources/htmlarea/htmlarea.js  
(working copy)
@@ -2038,7 +2038,7 @@
            case 3: // Node.TEXT_NODE
                // If a text node is alone in an element and all spaces, replace it with an non breaking one
                // This partially undoes the damage done by moz, which translates '&nbsp;'s into spaces in the data element
-               if ( !root.previousSibling && !root.nextSibling && root.data.match(/^\s*$/i) ) html = '&nbsp;';
+               if ( !root.previousSibling && !root.nextSibling && root.data.match(/^\s*$/i) ) html = '';
                else html = HTMLArea.htmlEncode(root.data);
                break;
            case 8: // Node.COMMENT_NODE

So I can check the correct value of the form and use the required attribute of the widget.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Vadim Gritsenko (JIRA | 2 Oct 12:34
Picon
Favicon

[jira] Closed: (COCOON-1906) [PATCH] simple-xml binding does not work with non file sources

     [ http://issues.apache.org/jira/browse/COCOON-1906?page=all ]

Vadim Gritsenko closed COCOON-1906.
-----------------------------------

    Fix Version/s: 2.2-dev (Current SVN)
                   2.1.10-dev (current SVN)
       Resolution: Fixed
         Assignee: Vadim Gritsenko

Patch applied.

> [PATCH] simple-xml binding does not work with non file sources
> --------------------------------------------------------------
>
>                 Key: COCOON-1906
>                 URL: http://issues.apache.org/jira/browse/COCOON-1906
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Forms, * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Lars Trieloff
>         Assigned To: Vadim Gritsenko
>             Fix For: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)
>
>         Attachments: cocoon-forms-javascript-disambiguation.patch,
cocoon-formsbinding-sample.patch, cocoon-formsbinding-sourceutil.patch
>
>
> The cocoon forms flowscript API comes with a helper method form.loadXML, that retrieves data from an xml
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniele Madama (JIRA | 2 Oct 12:34
Picon
Favicon

[jira] Commented: (COCOON-942) [Roadmap] Default values for fields

    [ http://issues.apache.org/jira/browse/COCOON-942?page=comments#action_12439092 ] 

Daniele Madama commented on COCOON-942:
---------------------------------------

Is not the fd:initial-value enough? Do you mean a default value if the field was leaved null?

> [Roadmap] Default values for fields
> -----------------------------------
>
>                 Key: COCOON-942
>                 URL: http://issues.apache.org/jira/browse/COCOON-942
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: Blocks: Forms
>    Affects Versions: 2.1.8
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Reinhard Poetz
>         Assigned To: Cocoon Developers Team
>            Priority: Minor
>
> Make it possible to set default values for fields.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |

Gmane