[prev in list] [next in list] [prev in thread] [next in thread]
List: mtos-dev
Subject: Re: [MTOS-dev] Expectations for plugins in MT5
From: "Doug Schaefer" <groups () salguod ! net>
Date: 2009-12-05 23:05:53
Message-ID: E487D6CF46A2458C85B1B5D0E9C91D94 () DOUG
[Download RAW message or body]
Hmm, hadn't looked I a while, so I had to check.
I'm using acronym.pl, which I could live without, scripturizer.pl, which I can \
replace with a non-plugin solution, I think, and there are some in the Photo gallery \
set, but I'm not sure I have the latest version (2.1?). Not currently using it, but \
plan to start a new gallery blog soon. Those are the only ones that show up as *.pl \
in the plugins listing.
Doug
-----Original Message-----
From: Byrne Reese [mailto:byrne@majordojo.com]
Sent: Saturday, December 05, 2009 4:52 PM
To: Doug Schaefer
Cc: Jay Allen; Jun Kaneko; mtos-dev@sixapart.com
Subject: Re: [MTOS-dev] Expectations for plugins in MT5
Which do you use?
Sent from my iPhone
On Dec 5, 2009, at 12:03 PM, "Doug Schaefer" <groups@salguod.net> wrote:
> I wouldn't have the foggiest idea how to convert them. I use a few
> on my blog and was asking simply to determine if that was going
> to be a roadblock to upgrading.
>
> Doug
>
> -----Original Message-----
> From: jayallen@gmail.com [mailto:jayallen@gmail.com] On Behalf Of
> Jay Allen
> Sent: Saturday, December 05, 2009 2:59 PM
> To: Jun Kaneko
> Cc: Doug Schaefer; mtos-dev@sixapart.com
> Subject: Re: [MTOS-dev] Expectations for plugins in MT5
>
> Oh, one more thing which underscores the point: We are very seriously
> considering deprecating them in either Melody 1.0 or, at latest, 1.1.
> The only question is whether the two currently have or when they will
> have total feature parity.
>
> Jay Allen
> Endevver Consulting
> (415) 702-0045
>
> On Sat, Dec 5, 2009 at 11:47 AM, Jay Allen <jay@endevver.com> wrote:
> > I would be remiss if I were not to say that creating *.pl initialized
> > plugins is not recommended and considered bad style. In fact, when
> > working on client sites, I take the 5 minutes it requires to convert
> > nearly every third-party plugin I use to config.yaml initialized
> > plugins. Perl initialized plugins greatly increase the overhead of
> > running MT in comparison to config.yaml plugins and should be avoided
> > if at all possible. And I have yet to find a plugin that actually
> > required Perl-based initialization.
> >
> > Jay Allen
> > Endevver Consulting
> > (415) 702-0045
> >
> > On Sat, Dec 5, 2009 at 3:59 AM, Jun Kaneko <jkaneko@sixapart.com>
> > wrote:
> > > Hello Doug
> > >
> > > ".pl" style plugin is supported with MT5.
> > > There is no change on it.
> > >
> > >
> > > Jun Kaneko
> > > jkaneko@sixapart.com
> > >
> > >
> > >
> > >
> > > On 2009/12/05, at 12:28, Doug Schaefer wrote:
> > >
> > > > I know this goes back a couple of weeks, but I have a concern about
> > > > this answer:
> > > >
> > > > "And it tends to be incompatible if the plugin is written in old
> > > > ".pl" style."
> > > >
> > > > Does that mean that old *.pl plugins won't work with MT5 or am I
> > > > misunderstanding this?
> > > >
> > > > Doug Schaefer
> > > > www.salguod.net
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: mtos-dev-bounces@sixapart.com [mailto:mtos-dev-
> > > > bounces@sixapart.com
> > > > ] On Behalf Of Beau Smith
> > > > Sent: Tuesday, November 17, 2009 5:56 PM
> > > > To: Neil Epstein
> > > > Cc: mtos-dev@sixapart.com
> > > > Subject: Re: [MTOS-dev] Expectations for plugins in MT5
> > > >
> > > > Neil_
> > > >
> > > > I asked Jun Kaneko (Product Manager at Six Apart Japan) about
> > > > this and
> > > > have wrapped this into my blog post for tomorrow...
> > > >
> > > > Jun's answer:
> > > >
> > > > > One of the developer in Japan did a great research for MT5 plugin
> > > > > compatibility .
> > > > >
> > > > > http://www.zelazny.mydns.jp/archives/001617.php
> > > > > http://www.zelazny.mydns.jp/archives/001627.php
> > > > >
> > > > > He probably checked most of the popular plugins.
> > > > >
> > > > > As a result, some of the plugins have a problem if they are
> > > > > using a
> > > > > transformer ( obviously due to the app change ) or incompatible
> > > > > with
> > > > > YAML::Syck or UTF-8. And it tends to be incompatible if the plugin
> > > > > is written in old ".pl" style.
> > > > >
> > > > > But other than those issues, it looks well compatible enough.
> > > >
> > > > It'd be great to update or at least add a comment/note to all the
> > > > plugins which work with MT5.
> > > >
> > > > I'll do this as I can, I'd hope that other's would do the same. =)
> > > >
> > > > _beau
> > > >
> > > >
> > > >
> > > >
> > > > On Nov 17, 2009, at 12:11 PM, Neil Epstein wrote:
> > > >
> > > > > Sorry if this has been answered before, tried searching around but
> > > > > no luck.
> > > > >
> > > > > Is there any posted expectations about MT4 plugins in MT5? Has
> > > > > there
> > > > > been changes to the structure that plugins use, and is there any
> > > > > documentation on those changes?
> > > > >
> > > > > Been testing MT5 and wound up making a site for my own use that I
> > > > > might want to launch publicly eventually. But would love to use
> > > > > plugins that exist (like the subscribe to entry comments that Beau
> > > > > mentioned), and curious what the best method to go about those is.
> > > > >
> > > > > I know from history of MT, that plugins break on ever major
> > > > > release.
> > > > > It would help to understand the timeline of a potential MT5 based
> > > > > site of how much refactoring plugins might need. Something must be
> > > > > up with them, as I did try the Subscribe plugin in MT5, and had no
> > > > > luck (but not sure if it's my system or the architecture).
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Neil
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > MTOS-dev mailing list
> > > > > MTOS-dev@sixapart.com
> > > > > http://www.sixapart.com/mailman/listinfo/mtos-dev
> > > >
> > > > _______________________________________________
> > > > MTOS-dev mailing list
> > > > MTOS-dev@sixapart.com
> > > > http://www.sixapart.com/mailman/listinfo/mtos-dev
> > > >
> > > > _______________________________________________
> > > > MTOS-dev mailing list
> > > > MTOS-dev@sixapart.com
> > > > http://www.sixapart.com/mailman/listinfo/mtos-dev
> > >
> > > _______________________________________________
> > > MTOS-dev mailing list
> > > MTOS-dev@sixapart.com
> > > http://www.sixapart.com/mailman/listinfo/mtos-dev
> > >
> >
>
>
> _______________________________________________
> MTOS-dev mailing list
> MTOS-dev@sixapart.com
> http://www.sixapart.com/mailman/listinfo/mtos-dev
_______________________________________________
MTOS-dev mailing list
MTOS-dev@sixapart.com
http://www.sixapart.com/mailman/listinfo/mtos-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic