Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
SilverStripe Core Development
Home
About this group
Apply for group membership
Message from discussion 3.1 CMS actions enhancements
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
drzax  
View profile  
 More options Nov 13 2012, 5:22 pm
From: drzax <elvery....@gmail.com>
Date: Tue, 13 Nov 2012 14:22:50 -0800 (PST)
Local: Tues, Nov 13 2012 5:22 pm
Subject: Re: 3.1 CMS actions enhancements
Print | View thread | Show original | Report this message | Find messages by this author

These changes should also flow through to the actions panel on the edit
form for DataObjects managed via ModelAdmin. As far as I can tell it's
currently not possible to change the actions there *at all* which is crazy.

Cheers,
Simon

On Tuesday, 13 November 2012 08:30:56 UTC+10, Sam Minnée wrote:

> I'm not sure where this work is being tracked, but I know that Paul has
> done a redesign of the page actions panel for the 3.1 CMS:
> https://skitch.com/clarkepaul/849t1/actions-panel-and-status

> This is a huge improvement and I'm very supportive of it, but I think we
> need to be careful about how we extend the actions API to support this.

> For example, the workflow module modifies the actions available fairly
> extensively.
> https://github.com/silverstripe-australia/advancedworkflow/issues/50

> Can we please build the enhanced API in such a way that modules don't need
> to fork in order to support both 3.0 and 3.1?

> A few thoughts:

>  - The different button locations (disabled/enabled, 'more actions menu'
> vs main list, etc) could be added some generic meta-data such as classes,
> that 3.0 can simply ignore.
>  - If the meta-data is stored in different fields, it should be
> straightforward to introspect, and fill out that meta-data only if 3.1 is
> installed.

> ----
> Sam Minnée
> Chief Executive Officer
> SilverStripe Limited

> Mobile: 021 311 441
> Skype: sam.minnee


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google