[geeklog-devel] Plugin development guides out of date

[Javed Khan]

Hi Ramindu,

Sure, I could use your help. Seems like the boilerplate plugin was created
before 1.6.0. I found the list of plugin API functions added to 1.6.0 useful
[0]. Is there a similar list for changes in 1.7.0? If no, maybe we can dig
through the logs and create one :)

I couldn't find any information about the the boilerplate plugin on the
wiki. I would like to write about it. And yes, this can go in the Plugin
Developer's Handbook.

[0] wiki.geeklog.net/index.php/New_Plugin_API_Functions_in_Geeklog_1.6.0

Thanks,
Javed

On Sat, Apr 17, 2010 at 11:42 AM, Ramindu Deshapriya <rasade88 at gmail.com>wrote:

> Thanks, all!
> Randy, I'm looking at the plugin, will work with Javed on bringing it up to
> date. Thanks, Stanislav, will add pgSQL to the boilerplate. Thanks Javed for
> your support. I hope we can discuss this soon and work it out? It would be
> great if we could use this the 'example' to be included with the Plugin
> Developer's Handbook on the wiki.
>
> Thanks again!
>
>
> On Sat, Apr 17, 2010 at 10:26 AM, Javed Khan <tuxcanfly at gmail.com> wrote:
>
>> Randy, I'm on it! Let me update the plugin to work with the latest version
>> of geeklog. autoninstall.php seems to be the obvious first step. I am also
>> following Ramindu's documentation on the wiki.
>>
>>
>> On Sat, Apr 17, 2010 at 1:20 AM, Randy Kolenko <Randy.Kolenko at nextide.ca>wrote:
>>
>>>  If someone likes, they can graciously take over the maintenance of the
>>> boilerplate plugin.. my official blessings etc etc.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* ṨϮⱥȵίṥʟɑ√ [mailto:yankees26an at gmail.com]
>>> *Sent:* Friday, April 16, 2010 3:21 PM
>>>
>>> *To:* Geeklog Development
>>> *Subject:* Re: [geeklog-devel] Plugin development guides out of date
>>>
>>>
>>>
>>> Hey, Ramindu,
>>>
>>>
>>>
>>> Attached the pgSQL sample class(which is just the MySQL class, barely
>>> ported), and the pgSQL install file. Let's not forget that we suppost that
>>> too :)  I guess this needs to be included in the plugin files(Randy)
>>>
>>> On Fri, Apr 16, 2010 at 2:09 PM, Ramindu Deshapriya <rasade88 at gmail.com>
>>> wrote:
>>>
>>> Thanks Randy! I'm not sure about replacing the existing skeleton plugin,
>>> will have to discuss that with Dirk I guess. Right now I'm concentrating on
>>> the documentation itself.
>>>
>>> Thanks again!
>>>
>>>
>>>
>>> On Wed, Apr 14, 2010 at 10:27 PM, Randy Kolenko <
>>> Randy.Kolenko at nextide.ca> wrote:
>>>
>>> I wrote a boilerplate plugin to show off how you can write a multi-db
>>> supported plugin when I did the MSSQL port.
>>>
>>> Not sure if Stan wanted to update it to include PGSQL support as well..
>>> but it might be a good start for a skeleton plugin..
>>>
>>>
>>>
>>> http://www.geeklog.net/filemgmt/index.php?id=757&query=boilerplate
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* Ramindu Deshapriya [mailto:rasade88 at gmail.com]
>>> *Sent:* Wednesday, April 14, 2010 12:36 PM
>>> *To:* Geeklog Development
>>> *Subject:* Re: [geeklog-devel] Plugin development guides out of date
>>>
>>>
>>>
>>> Dirk, I totally understand. I just thought through some form of sheer bad
>>> luck I might be downloading the wrong tarball as Ben said something about
>>> COM_output not being there as well. Anyway, I guess that's all cleared up
>>> now!
>>>
>>> Thanks!
>>>
>>> On Wed, Apr 14, 2010 at 6:15 PM, cordiste <cordiste at free.fr> wrote:
>>>
>>> oups  I mistyped the function name.
>>>
>>> Sorry for this. I need a vacation...
>>>
>>> ::Ben
>>>
>>> 2010/4/13 cordiste <cordiste at free.fr>:
>>>
>>> > Hello,
>>> >
>>> > I do not found a COM_ouput() function in the lib-common.php file
>>> > version 1.7.0b1.
>>> >
>>> > ::Ben
>>> >
>>> > 2010/4/13 Ramindu Deshapriya <rasade88 at gmail.com>:
>>> >> Hi all,
>>> >> I was looking into developing a mockup of the e-commerce plugin. For
>>> this I
>>> >> read up on the Plugin Developers Handbook and downloaded the Universal
>>> >> Plugin Toolkit. Both of them seem to be a bit outdated. The first bit
>>> of
>>> >> evidence I found for this is that they use a simple echo statement in
>>> place
>>> >> of the COM_ouput() function. Would you like these guides to be brought
>>> up to
>>> >> date? Is there some initiative in place to do this?
>>> >> Just thought I'd ask.
>>> >> Thanks!
>>> >>
>>> >> --
>>> >> Yours Truly,
>>> >> Ramindu Deshapriya.
>>> >>
>>> >> _______________________________________________
>>> >> geeklog-devel mailing list
>>> >> geeklog-devel at lists.geeklog.net
>>> >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>> >>
>>> >>
>>> >
>>> _______________________________________________
>>> geeklog-devel mailing list
>>> geeklog-devel at lists.geeklog.net
>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>>
>>>
>>>
>>>
>>> --
>>> Yours Truly,
>>> Ramindu Deshapriya.
>>>
>>>
>>> _______________________________________________
>>> geeklog-devel mailing list
>>> geeklog-devel at lists.geeklog.net
>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>>
>>>
>>>
>>>
>>> --
>>> Yours Truly,
>>> Ramindu Deshapriya.
>>>
>>>
>>> _______________________________________________
>>> geeklog-devel mailing list
>>> geeklog-devel at lists.geeklog.net
>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>>
>>>
>>>
>>>
>>> --
>>> Warmly,
>>>
>>> Stanislav
>>>
>>>
>>> _______________________________________________
>>> geeklog-devel mailing list
>>> geeklog-devel at lists.geeklog.net
>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>>
>>>
>>
>> _______________________________________________
>> geeklog-devel mailing list
>> geeklog-devel at lists.geeklog.net
>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>
>>
>
>
> --
> Yours Truly,
> Ramindu Deshapriya.
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20100417/97aa30b7/attachment.html>