[ckan-dev] Hello-word-type theme extension

[Rufus Pollock]

On 11 April 2011 08:47, Seb Bacon <seb.bacon at okfn.org> wrote:
> Hi,
>
> I did see that & decided to leave it as it is, as it's a usefully
> different thing: a true helloworld, i.e. bare bones extension.
>
> Mine is meant as scaffolding specifically for local, mainly theme-like
> customisations, hence including an extra.css and lots of other bits
> and bobs.

Agreed (and didn't mean you should have used it ;) )

BTW: helloworld was supposed to develop to include e.g. controller stuff :)

Rufus

> Thanks,
>
> Seb
>
> On 11 April 2011 08:40, Rufus Pollock <rufus.pollock at okfn.org> wrote:
>> BTW I started a helloworld extension here (back in Feb):
>>
>> <http://bitbucket.org/okfn/ckanext-helloworld>
>>
>> Associated (incomplete) tutorial here:
>>
>> <http://wiki.ckan.net/Extensions_Tutorial>
>>
>> Prepared for the tutorial at Dev8D:
>>
>> <http://ckan.org/2011/02/17/dev8d-ckan-workshop/>
>>
>> Rufus
>>
>> On 8 April 2011 16:07, Seb Bacon <seb.bacon at okfn.org> wrote:
>>> Looks right to me.
>>>
>>> Once we've iterated it a bit more, it strikes me that the extension
>>> route could *possibly* become the recommended route to customising --
>>> we could make a paster template etc.
>>>
>>> Not sure, just a thought.
>>>
>>> SEb
>>>
>>> On 8 April 2011 15:47, David Read <david.read at okfn.org> wrote:
>>>> Seb,
>>>>
>>>> I added a section to our theming wiki about your example extension here:
>>>>
>>>> http://wiki.okfn.org/ckan/doc/theme
>>>>
>>>> Do correct it if I've missed anything.
>>>>
>>>> Dave
>>>>
>>>> On 1 April 2011 19:42, Seb Bacon <seb.bacon at gmail.com> wrote:
>>>>> Done.
>>>>>
>>>>> On 29 March 2011 13:26, James Gardner <james at 3aims.com> wrote:
>>>>>> Hi Seb,
>>>>>>
>>>>>> Good stuff. I've noticed the Debian packaging (see
>>>>>> https://bitbucket.org/okfn/ckan/src/default/doc/deb.rst) doesn't always like
>>>>>> extension points in __init__.py files. Haven't been able to work out why,
>>>>>> but to solve the issue I've been moving all such code to a "plugin.py" file
>>>>>> instead and I think this should now be considered best practice instead. For
>>>>>> example:
>>>>>>
>>>>>> https://bitbucket.org/okfn/ckanext-harvest/changeset/784c90306f4b
>>>>>>
>>>>>> Could you please apply this change to your example too?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> James
>>>>>>
>>>>>>
>>>>>>
>>>>>>  On 29/03/11 12:58, Seb Bacon wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I've just created a new CKAN extension to demonstrate some evolving
>>>>>>> best-practices regarding encapsulating all your customisations and
>>>>>>> changes to core CKAN in a single package.
>>>>>>>
>>>>>>> As I say, it's evolving, so perhaps some people have other / better
>>>>>>> ideas about how to structure it.
>>>>>>>
>>>>>>> Anyway, a first version is at
>>>>>>> https://bitbucket.org/okfn/ckanext-exampletheme; the README should
>>>>>>> provide some basic orientation.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> ckan-dev mailing list
>>>>>>> ckan-dev at lists.okfn.org
>>>>>>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> skype: seb.bacon
>>>>> mobile: 07790 939224
>>>>> land: 0207 183 9618
>>>>> web: http://baconconsulting.co.uk
>>>>>
>>>>> _______________________________________________
>>>>> ckan-dev mailing list
>>>>> ckan-dev at lists.okfn.org
>>>>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> ckan-dev mailing list
>>> ckan-dev at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>>
>>
>>
>>
>> --
>> Co-Founder, Open Knowledge Foundation
>> Promoting Open Knowledge in a Digital Age
>> http://www.okfn.org/ - http://blog.okfn.org/
>>
>



-- 
Co-Founder, Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/