Fork me on GitHub

Block Dev HOWTO?  Bottom

Go to page [-1] 1 - 2 - 3:

  • Callouts/baloon have nothign to do with navigation really, they are just tools for pulling/presenting data. So it really has nothing to do with accessability, which is not a concern for most developers anyway. The end users/markets drive what makes up the web, not standards/rules/ or really even laws in most cases.

    As far as third party blocks not working. I have tried a few (simple xmenu, dynamenu, and updownload) with no luck. Even after removing them, i still have some issues with "Core /" showing up in the new blocks list. No clue where those came from really.
  • In talking about this at length with the Dev team, it sounds like my inital proposal is rejected, but the plan is to basically encourage devs to convert all stand-along blocks into 'mini-modules'. If you want to put an existing stand-alone block in .8, you *might* be able so simply put it in a folder like so:

    modules/<block name="name">/pnversion.php
    modules/<block name="name">/pnblocks/blockfile.php

    those two files should do it.</block></block>
  • Right, but thats overkill and not a good way to seperate things for organizational purposes. Why put a standalone BLOCK in the MODULES folder? Especially if they arent associated with any module.

    I really think that something like blocks/blockname.php and blocks/pntemplates/templatename.htm is a much better way. Maybe even have subfolders to seperate system and thirdparty blocks.

    /blocks/system/ or /blocks/custom/

    Core modules and third party modules are already seperated, why not do the same with blocks?
  • Sorry Mark but I don't believe that the one extra version file is that much more complex. However the benefits gained from treating everything as a module are clear

    1) Locations already exist for stylesheets, javascript, templates associated with the block - under the proposal of a stand-alone blokcs directory new locations for all of these would be needed meaning that the core would have to scan further directories

    2) Methods exist for the versioning of blocks to to handled. No such version handling exists at the moment nor would under the proposal of stand-alone blocks directory.

    3) All the mechanisms for overriding of templates, stylesheets, images etc. are already built around the modules system. Adding this for blocks would mean yet more paths to be scanned.

    Further once you look beyond the most simple one file block to say dynamenu and you'd end up with a structure like

    /blocks/<block name="name">/block file
    /blocks/<block name="name">/<pnlang>
    /blocks/<block name="name">/<pntemplates>
    /blocks/<block name="name">/<pnimages>
    /blocks/<block name="name">/<pnjavascript>
    /blocks/<block name="name">/<pnstyle>

    at which point this starts to look suspiciously like a module to me.....

    -Mark

    --
    Visit My homepage and Zikula themes.</pnstyle></block></pnjavascript></block></pnimages></block></pntemplates></block></pnlang></block></block>
  • lol, ok, fine, u got me =P. I ended up just making a generic module with the blank module and renamed it as OldBlocks. From there im going to try and port some existing blocks that i need to use. Unfortunately I have had no luck with non API compliant blocks so far. But with the example code you posted earlier, im going to take another crack at it. Will request nate to look into converting his dynamenu block into a module as well.
  • Figured i would post a link to this tutorial. Very useful for block dev.

    http://www.dordrak.com/dokuwiki/doku.php?id=blockprogramming:writingablock
  • MACscr

    Figured i would post a link to this tutorial. Very useful for block dev.

    http://www.dordrak.com/dokuwiki/doku.php?id=blockprogramming:writingablock


    Thanks for the link!

    --
    WIRE SERVICE

    Free Press Releases

Go to page [-1] 1 - 2 - 3:

  • 0 users

This list is based on users active over the last 60 minutes.