You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org> on 2005/05/13 19:04:07 UTC

[jira] Created: (TAPESTRY-330) Add uninitialization tag to Script specification and component

Add uninitialization tag to Script specification and component
--------------------------------------------------------------

         Key: TAPESTRY-330
         URL: http://issues.apache.org/jira/browse/TAPESTRY-330
     Project: Tapestry
        Type: New Feature
  Components: Framework  
    Versions: 4.0    
 Environment: All
    Reporter: Andreas Andreou
    Priority: Minor


The uninitialization tag will enable components and pages to
have custom javascript executed when the page unloads. 
I am aware of many use cases where this is useful, but here is one I recently came across:
   Assume that a StylesheetSwitcher component exists (it does :) ) which allows the user to 
change the skin of a web-app. It does this by providing special javasript links that do the work.
However, in many browsers, the user can change the skin from the browser menu. Of course,
this action does not trigger any custom javascript. However, if we could have some script executed 
when the page unloads, we could determine if the user has performed the above action, and 
act appropriately!
  
I expect this new tag to be used just the way the initialization tag is used.
Also, implementing this requires nothing more than duplicating the existing code that
allows the initialization feature.



-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Updated: (TAPESTRY-330) Add uninitialization tag to Script specification and component

Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-330?page=all ]

Jesse Kuhnert updated TAPESTRY-330:
-----------------------------------

    Fix Version/s: 4.1.2
         Assignee: Andreas Andreou

> Add uninitialization tag to Script specification and component
> --------------------------------------------------------------
>
>                 Key: TAPESTRY-330
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-330
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: Framework
>    Affects Versions: 4.0
>         Environment: All
>            Reporter: Andreas Andreou
>         Assigned To: Andreas Andreou
>            Priority: Minor
>             Fix For: 4.1.2
>
>
> The uninitialization tag will enable components and pages to
> have custom javascript executed when the page unloads. 
> I am aware of many use cases where this is useful, but here is one I recently came across:
>    Assume that a StylesheetSwitcher component exists (it does :) ) which allows the user to 
> change the skin of a web-app. It does this by providing special javasript links that do the work.
> However, in many browsers, the user can change the skin from the browser menu. Of course,
> this action does not trigger any custom javascript. However, if we could have some script executed 
> when the page unloads, we could determine if the user has performed the above action, and 
> act appropriately!
>   
> I expect this new tag to be used just the way the initialization tag is used.
> Also, implementing this requires nothing more than duplicating the existing code that
> allows the initialization feature.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Resolved: (TAPESTRY-330) Add uninitialization tag to Script specification and component

Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-330?page=all ]

Andreas Andreou resolved TAPESTRY-330.
--------------------------------------

    Resolution: Won't Fix

Use dojo to trap the unload event and execute as much js as you'ld like!

> Add uninitialization tag to Script specification and component
> --------------------------------------------------------------
>
>                 Key: TAPESTRY-330
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-330
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: Framework
>    Affects Versions: 4.0
>         Environment: All
>            Reporter: Andreas Andreou
>         Assigned To: Andreas Andreou
>            Priority: Minor
>             Fix For: 4.1.2
>
>
> The uninitialization tag will enable components and pages to
> have custom javascript executed when the page unloads. 
> I am aware of many use cases where this is useful, but here is one I recently came across:
>    Assume that a StylesheetSwitcher component exists (it does :) ) which allows the user to 
> change the skin of a web-app. It does this by providing special javasript links that do the work.
> However, in many browsers, the user can change the skin from the browser menu. Of course,
> this action does not trigger any custom javascript. However, if we could have some script executed 
> when the page unloads, we could determine if the user has performed the above action, and 
> act appropriately!
>   
> I expect this new tag to be used just the way the initialization tag is used.
> Also, implementing this requires nothing more than duplicating the existing code that
> allows the initialization feature.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org