ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Keeping the Wheels Greased (a.k.a. Add-on Submission Changes)

September 21, 2007 12:25pm

Subscribe [5]
  • #1 / Sep 21, 2007 12:25pm

    Derek Jones

    7561 posts

    Recently we rolled out a set of Developer Guidelines, including a promise of news regarding changes to the submission process to ensure higher quality add-ons and a faster turnaround on reviewing your submissions.  Today is part one of those changes.

    We had already linked to the guidelines and made mention on the submission form that the add-on needed to meet those requirements, but we also understand the excitement of a new add-on and submitting something for the community.  It tends to make one not read a paragraph or two above the submission form, and one either forgets about the guidelines altogether, or doesn’t realize that they are not optional.  Naughty!

    Continue…

  • #2 / Sep 21, 2007 12:33pm

    PXLated

    1800 posts

    Is this what god was referring to?

  • #3 / Sep 21, 2007 1:21pm

    Derek Jones

    7561 posts

    No, that’s actually something altogether different, though it does reinforce the thought of the amount of time it takes to review someone else’s code.

  • #4 / Sep 21, 2007 2:19pm

    Leslie Camacho

    1340 posts

    Is this what god was referring to?

    It is against the ExpressionEngine Community forums usage policy to feed Paul’s ego in such a unhealthy manner.

  • #5 / Sep 21, 2007 2:25pm

    PXLated

    1800 posts

    feed Paul’s ego in such a unhealthy manner

    Shame on me…I should have known better 😉

  • #6 / Sep 21, 2007 3:43pm

    BlackHelix

    226 posts

    I thought Paul was dead… he was killed on Abbey Road, right?  As such, he may well be up there….  though I draw the line if someone asks for a goat sacrifice. 


    Anyway, minor question about the dev guidelines.  It says to avoid heredoc syntax; I assume that doesn’t apply to a plugin documentation function?  I.E. the function that outputs the info on the plugin page.

  • #7 / Sep 21, 2007 4:19pm

    Derek Jones

    7561 posts

    Anyway, minor question about the dev guidelines.  It says to avoid heredoc syntax; I assume that doesn’t apply to a plugin documentation function?  I.E. the function that outputs the info on the plugin page.

    Because of some PHP bugs in how heredoc strings are handled in various point releases, I’d recommend avoiding unless unavoidable.  That makes sense, right?  In the case of the usage() method of a plugin, you can use output buffering instead.  On PHP versions where the bug is not present, it’s essentially a wash on memory and speed to use output buffering vs. heredoc.  Only after thousands of iterations does a difference become measurable, and even then only marginally so.

  • #8 / Sep 24, 2007 1:07pm

    Visiluna

    92 posts

    Hmm…I pictured Paul as more of the nun’s habit-wearing, knuckle-smacking type.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases