unfocus / scripts-n-styles Goto Github PK

This is easily implemented in SnS_Admin_Meta_Box, but we don't have the UI. To get 3.0 out, punting to Future...

Scripts n Styles should be able to handle widget-adding code like

    <script type="text/javascript" src="http://widgets.twimg.com/j/2/widget.js"></script><script type="text/javascript">
    // < ![CDATA[
    new TWTR.Widget(
        { 
            version: 2, 
            type: 'search', 
            interval: 6000, 
            width: 'auto',  
            height: 450, 
            theme: { 
                shell: { background: '#85110f', color: '#ffffff' }, 
                tweets: { background: '#ffffff', color: '#444444', links: '#ee4022' } 
            }, 
            features: { 
                scrollbar: true, 
                loop: false, 
                live: true, 
                hashtags: true, 
                timestamp: true, 
                avatars: true, 
                behavior: 'all' 
            }
        }
    ).render().start();
    // ]]>
    </script>

This would be nice to have. Not really needed for 3.0

Create shortcode to embed html/javascript snippets. See http://scribu.net/wordpress/optimal-script-loading.html in which this is already figured out :-)

I've got a patch in...

use WP_Comments_List_Table as a template.

Codemirror is at 2.15 which has a markdown mode and might be useful.

A lot has changed since the files been updated...

CMD+S should trigger save :-)

The look of the plugin changed, features have been added, screenshots are outdated.

There's a ticket somewhere with the updated screens api. need screen options in some places like the usage table.

http://codex.wordpress.org/Class_Reference/WP_List_Table

Need to fix or move to own page.

Not sure. Maybe another option...

An adcSTUDIO (paid, thank you) feature request. This is a priority.

http://theme.fm/2011/09/introducing-pointers-in-wordpress-3-3-2407/

Settings Page and Metabox will have to be updated too

I'd be cool to take LESS in the Styles areas.

Both are added to TinyMCE at the same level, while on the theme side, it's a hierarchy. Could be a gotcha.

support for writing a widget as an html page, which is servered to a widget via ajax or via shortcode.

self explainitory

Worked out on metabox already.

like #42

done! (here for archival.)

The javascript currently doesn't account for not having a wp editor, so doesn't check before attempting to initiate the tinymce enhancements.

The select element sucks. #7 related. Should have a way to add external/uploaded scripts. The current beta list can serve as a resource to a user slimmed/selected list (more manageable, better experience)

This would be a widget that wraps arbitrary HTML in an iframe.

To enhance UX, Styles should be labeled "CSS" and be decoratively wrapped with <style ...>

Same for scripts...

add a check

wp_get_nocache_headers might be useful

As an example, GravityForms is generating notices on it's form notification screens because of SnS. As a guess, I would think that it's using a CPT internally with the wp multi post editor functionality. This means I need better CPT selects again, or support multi post editor more formally.

This is a maybe.

Some other plugin's info (Font-Size drop-down) is showing as SnS info under usage.

A lot of the inline documentation is outdated.

some code relies on the post object, for example: $post->ID

The post object is empty on 404 pages and so generates notices.

It's dog ugly.

Right now we auto select. perhaps a user choice. maybe.

the theme branch has theme style support. Duplicate functionality for editor style, and share the common data.

If I include an Apache 2.0 library, I must release the "combined" package as GPLv3. I hate licensing.

This would be nice. It's worked out on global.

Following suit, we should do Unit Testing, and move to more of a BDD methodology for new features.

Codemirror has multiple themes to choose from for example.

1.0.2 and 1.0.3-alpha are currently each other and incorrectly marked.

Added a toggle and set it off by default. 3.0 has a more robust solution.