[wp-hackers] wp-hackers Digest, Vol 93, Issue 36

jihan amrani jihan735 at hotmail.com
Mon Oct 29 12:59:06 UTC 2012 

hello dear can you fix me back my password for this email
ama_zone at hotmail.fr
thanks a lot

> From: wp-hackers-request at lists.automattic.com
> Subject: wp-hackers Digest, Vol 93, Issue 36
> To: wp-hackers at lists.automattic.com
> Date: Mon, 29 Oct 2012 12:00:01 +0000
> 
> Send wp-hackers mailing list submissions to
> 	wp-hackers at lists.automattic.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.automattic.com/mailman/listinfo/wp-hackers
> or, via email, send a message with subject or body 'help' to
> 	wp-hackers-request at lists.automattic.com
> 
> You can reach the person managing the list at
> 	wp-hackers-owner at lists.automattic.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Fetch Feed (Ryan McCue)
>    2. Re: Fetch Feed (Ryan Frankel)
>    3. Re: pluggable functions (Mike Schinkel)
>    4. Re: auto-loading plugin deps ( prev: pluggable functions )
>       (Ben Lobaugh)
>    5. Re: auto-loading plugin deps ( prev: pluggable	functions )
>       (Mike Schinkel)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 28 Oct 2012 23:06:11 -0400
> From: Ryan McCue <lists at rotorised.com>
> Subject: Re: [wp-hackers] Fetch Feed
> To: wp-hackers at lists.automattic.com
> Message-ID: <508DF2A3.6040005 at rotorised.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Ryan Frankel wrote:
> > 1. If I use fetch_feed() multiple times on a page does it cache the results
> > separately?  I assume it does.
> 
> It caches it based (mainly) on the URL, so if the URL of the feed is 
> different, then they will be cached separately; if they're the same feed 
> loaded twice, it should load it from the cache. If possible, avoid doing 
> this, because it means that SimplePie has to be run twice to parse the 
> data (the data is cached at a low-level, only a step or two higher than 
> the raw XML).
> > 2. Since fetch_feed caches the results is there any way to tell if an
> > 'item' is new? For example, something like...
> >
> There's a tutorial on how to do this natively with SimplePie: 
> http://simplepie.org/wiki/tutorial/how_to_display_previous_feed_items_like_google_reader
> 
> Your best bet is to adjust that tutorial and adapt it to WordPress using 
> options instead.
> 
> -- 
> Ryan McCue
> <http://ryanmccue.info/>
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sun, 28 Oct 2012 23:15:47 -0400
> From: Ryan Frankel <ryan.frankel at gmail.com>
> Subject: Re: [wp-hackers] Fetch Feed
> To: wp-hackers at lists.automattic.com
> Message-ID: <572E0BFC-E21F-456D-89CB-F1E86ABACFDE at gmail.com>
> Content-Type: text/plain; charset=us-ascii
> 
> 1. Thanks for the info.
> 2. Good point.
> 
> Ryan
> 
> On Oct 28, 2012, at 11:06 PM, Ryan McCue wrote:
> 
> > Ryan Frankel wrote:
> >> 1. If I use fetch_feed() multiple times on a page does it cache the results
> >> separately?  I assume it does.
> > 
> > It caches it based (mainly) on the URL, so if the URL of the feed is different, then they will be cached separately; if they're the same feed loaded twice, it should load it from the cache. If possible, avoid doing this, because it means that SimplePie has to be run twice to parse the data (the data is cached at a low-level, only a step or two higher than the raw XML).
> >> 2. Since fetch_feed caches the results is there any way to tell if an
> >> 'item' is new? For example, something like...
> >> 
> > There's a tutorial on how to do this natively with SimplePie: http://simplepie.org/wiki/tutorial/how_to_display_previous_feed_items_like_google_reader
> > 
> > Your best bet is to adjust that tutorial and adapt it to WordPress using options instead.
> > 
> > -- 
> > Ryan McCue
> > <http://ryanmccue.info/>
> > 
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sun, 28 Oct 2012 23:21:36 -0400
> From: Mike Schinkel <mike at newclarity.net>
> Subject: Re: [wp-hackers] pluggable functions
> To: wp-hackers at lists.automattic.com
> Message-ID: <51B39795-1FDE-412E-8718-44F8C861CD1C at newclarity.net>
> Content-Type: text/plain;	charset=iso-8859-1
> 
> On Oct 28, 2012, at 11:04 PM, Daniel Dvorkin <elrabino at gmail.com> wrote:
> > I've been wondering about this for a while. WP_Dependencies (the class
> > extended by WP_Scripts and WP_Styles) seems well suited to handle some sort
> > of library load in the same way we can register, unregister
> > and prioritise scripts and styles.
> 
> Yes, it does look like WP_Dependencies would be a good base for dependency management.  That is, however, a large scope and I'd fear a larger scope would be beyond consideration.  
> 
> WP_Dependencies helps manage the tree of dependencies; the smaller scoped need would be to collect up a list of latest needed libraries and load the latest one of each or fire an action to notify a plugin that its library load request can't be fulfilled so it can notify the admin user and avoid using the library.
> 
> -Mike
> 
> ------------------------------
> 
> Message: 4
> Date: Sun, 28 Oct 2012 22:17:51 -0700
> From: Ben Lobaugh <lists at lobaugh.net>
> Subject: Re: [wp-hackers] auto-loading plugin deps ( prev: pluggable
> 	functions )
> To: wp-hackers at lists.automattic.com
> Message-ID: <508E117F.9010706 at lobaugh.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hey Mike,
> 
> I think it would be great to see something similar to the enqueue 
> scripts that you can pass required dependencies to, probably the slug of 
> the plugin from the repo. If it does not exist then WP will disable the 
> plugin and/or prompt you to install the dependency to enable the plugin.
> 
> I have written a few library plugins as well and I can sympathize with 
> the dependency management and load order of plugins. It is tricky with 
> the current way WP works, but I do not think it would be too difficult 
> to add something of that sort to the system. Check and see if anything 
> like that exists on Trac, if not would you be interested in exploring a 
> solution to patch core to do that with me?
> 
> Cheers,
> Ben
> 
> On 10/28/12 8:21 PM, Mike Schinkel wrote:
> > On Oct 28, 2012, at 11:04 PM, Daniel Dvorkin <elrabino at gmail.com> wrote:
> >> I've been wondering about this for a while. WP_Dependencies (the class
> >> extended by WP_Scripts and WP_Styles) seems well suited to handle some sort
> >> of library load in the same way we can register, unregister
> >> and prioritise scripts and styles.
> > Yes, it does look like WP_Dependencies would be a good base for dependency management.  That is, however, a large scope and I'd fear a larger scope would be beyond consideration.
> >
> > WP_Dependencies helps manage the tree of dependencies; the smaller scoped need would be to collect up a list of latest needed libraries and load the latest one of each or fire an action to notify a plugin that its library load request can't be fulfilled so it can notify the admin user and avoid using the library.
> >
> > -Mike
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Mon, 29 Oct 2012 02:38:30 -0400
> From: Mike Schinkel <mike at newclarity.net>
> Subject: Re: [wp-hackers] auto-loading plugin deps ( prev: pluggable
> 	functions )
> To: wp-hackers at lists.automattic.com
> Message-ID: <413E4C91-4720-4CD8-8F47-C78862E17E89 at newclarity.net>
> Content-Type: text/plain;	charset=us-ascii
> 
> Hi Ben,
> 
> Thanks for the follow up.
> 
> On Oct 29, 2012, at 1:17 AM, Ben Lobaugh <lists at lobaugh.net> wrote:
> > I think it would be great to see something similar to the enqueue scripts that you can pass required dependencies to, probably the slug of the plugin from the repo. If it does not exist then WP will disable the plugin and/or prompt you to install the dependency to enable the plugin.
> > 
> > I have written a few library plugins as well and I can sympathize with the dependency management and load order of plugins. It is tricky with the current way WP works, but I do not think it would be too difficult to add something of that sort to the system. 
> 
> 
> For clarity I was explicitly proposing simple PHP libraries and not wanting to open the can of worms that would be plugin dependency management.  After considering the problem for a long time I think the reason this has not gotten addressed yet for plugins is that plugins are for users not for developers. Developers need something lower level, i.e. ability to just safely "require()" a PHP library.  
> 
> There's really no need for tree-based dependency management and no need for all the complexity or overhead of making sure plugins are auto-downloaded, safely activated and then loaded in the correct order.  All that's needed is the ability to signal to WordPress that we need a bit of PHP code that someone else developed, named and versioned and that please WordPress only require() one of them.
> 
> > Check and see if anything like that exists on Trac,
> 
> My memory is that there's been several discussions about parts of this on trac or here on wp-hackers over the years.  I'm not particularly good at finding them though so I'll leave that to others to find.
> 
> > if not would you be interested in exploring a solution to patch core to do that with me?
> 
> I was proposing to offer a strawman patch if anyone of the core team would be open to considering it.  Otherwise it would rather be a waste of effort, I think.
> 
> -Mike
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> 
> End of wp-hackers Digest, Vol 93, Issue 36
> ******************************************

More information about the wp-hackers mailing list