Re: [Tikiwiki-devel] custom tiki / adding modules

[Luis A. <lu...@fu...>]

Making the DHTML menus work for Smarty is certainly a good way to start.
Everybody knows I don't like rejecting code
but I'd have to reject code if it implies using phplib templating, it would
make everything just too complex.
I'm sure the DHTML menu guys would love a Smarty version and it should be
fairly easy to code if it works for PHPLIB.


----- Original Message -----
From: "Greg Rundlett" <gr...@fr...>
To: "Tiki-devel" <tik...@li...>
Sent: Friday, June 20, 2003 12:30 PM
Subject: Re: [Tikiwiki-devel] custom tiki / adding modules


> On Fri, 2003-06-20 at 10:59, Luis Argerich wrote:
> > Hi Greg,
> >
> > About the DHTML menu you can integrate them easily by creating a theme,
in
> > the theme you can redefine all the templates
> > where you want to use the menus. Add the Javascript libraries needed in
the
> > header.tpl template for the theme and use it
> > as needed. This should be absolutely trivial since it's just a change in
the
> > interface. Themes can redefine the interface to Tiki
> > as they want.
>
> Thanks, that helps me out.  It's not that easy, because there is a whole
> PHP class that generates the menu structures, and uses PHPLIB
> templating.  (Uggh, two template systems in use at the same time.)  I am
> inclined to rewrite phpLayersMenu to use Smarty rather than PHPLIB.
>
>
> > Integrating osCommerce should be as simple as integrating any other API.
> > Create the interfaces you want where osCommerce
> > should be used and then in the .php scripts "include" what you need and
use
> > it. I don't understand how can this be a problem
> > or how can you need to "bridge" classes...
>
> Upon closer examination of how you integrated Richard Heyes HTMLMimeMail
> class, I can see how to add 'external classes' to Tiki.
>
> > Both things would be really welcome as contributions to the Tiki project
as
> > long as they are included as "optional" modules that
> > "extend" Tiki without modifying the existing Tiki distribution. As a
> > guideline you can first start "extending" Tiki to support the new
> > theme and the osCommerce module, contribute that back to the project if
you
> > want, and then customize whatever you may need
> > for your particular implementation if you find that necesary.
>
> I would love to contribute to Tiki, so I'll do what I can.  Thanks.
>
>
> --
> FREePHILE
> We are 'Open' for Business
> Free and Open Source Software
> http://www.freephile.com
> (978) 270-2425
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>