[PLIP-Advisories] Re: [Plone] #8809: Make KSS optional

plip-advisories at lists.plone.org plip-advisories at lists.plone.org
Sat Oct 3 01:05:49 UTC 2009


#8809: Make KSS optional
------------------------+---------------------------------------------------
 Reporter:  hannosch    |        Owner:     
     Type:  PLIP        |       Status:  new
 Priority:  minor       |    Milestone:  5.0
Component:  KSS (Ajax)  |   Resolution:     
 Keywords:              |  
------------------------+---------------------------------------------------

Old description:

> = Overview =
>
> KSS is the framework used to provide a limited set of AJAX-functionality
> for Plone. Most of Plone's JavaScript is based on jQuery instead.
>
> After depending on KSS inside the Plone 3 release series, KSS has neither
> seen the kind of wide-spread adoption inside nor outside the Plone
> community which warrants it to be part of the core distribution.
>
> In the latest Plone 3.x release the main remaining feature powered by KSS
> is inline-validation of Archetypes content. The way inline editing has
> been implemented has proven to be a failure from a usability perspective.
> The overhead of KSS as a framework compared to the actual value provided
> to core Plone does no longer warrant it to be part of the core
> distribution.
>
> I'd suggest we remove the hard KSS dependency and move all KSS Plone
> integration into the plone.app.kss and archetypes.kss packages.
> Interested parties and packages can then depend on plone.app.kss.
>
> = Progress =
>
> Implemented with r25107.

New description:

 = Overview =

 KSS is the framework used to provide a limited set of AJAX-functionality
 for Plone. Most of Plone's JavaScript is based on jQuery instead.

 After depending on KSS inside the Plone 3 release series, KSS has neither
 seen the kind of wide-spread adoption inside nor outside the Plone
 community which warrants it to be part of the core distribution.

 In the latest Plone 3.x release the main remaining feature powered by KSS
 is inline-validation of Archetypes content. The way inline editing has
 been implemented has proven to be a failure from a usability perspective.
 The overhead of KSS as a framework compared to the actual value provided
 to core Plone does no longer warrant it to be part of the core
 distribution.

 I'd suggest we remove the hard KSS dependency and move all KSS Plone
 integration into the plone.app.kss and archetypes.kss packages. Interested
 parties and packages can then depend on plone.app.kss.

 From David Glick:

 These are the things that will currently stop working if you disable KSS:

     * inline editing
     * inline validation
     * lock on edit (parts of it, anyway)
     * auto-refreshing of portlets with a kssPortletRefresh class (yeah, I
 didn't know we had this feature either)
     * some of the action menu stuff (e.g. AJAX changing of workflow state)
     * navigation of the calendar portlet to different months
     * triggering the initialization of some plain Javascript features
 (form tabbing, changed form unload protection) after page load
     * AJAX update of sharing page
     * folder_contents pagination and sorting (I think someone already
 rewrote this on plone.app.javascript trunk)

 = Progress =

 Implemented with r25107 (on trunk).

--

Comment(by limi):

 Adding David Glick's list what will be affected.

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/8809#comment:26>
Plone <http://plone.org>
Plone Content Management System


More information about the PLIP-Advisories mailing list