[CarCdr]

Originally Posted by nexialys

hum.. looks like i see where is your point... you would like to have parts of vB to become OOP... i don't think it's planned... OOP is not even recognised at php.net, even in PHP5...

your leveled navbar example is not concise...:

PHP Code:

$navbits = construct_navbits(array(
                                    'element_url.html'  => 'element_name',
                                    ''                  => 'last_element_name_without_link'
                            )   ); 


is it so complicated to build ?!... you tell in your explanation that our actual structure is hard to understand... i think that OOP is complicated, not pure php...

It could just as easily be straight functions. using a class is a simple means of keeping information without using global variables. (Classes does require PHP 4. Creating a class does not require that vB be OOP. It's just standard PHP.)

As for my navbar call, it would work fine. In the initial call we were supplied the page title and the page URL. We save three pieces of information in globals:

1) The file name, saved in say $EXT_filename. E.g., foo.php
2) The URL, in say $EXT_url. E.g., ./foo.php
3) The page title, in say $pagetitle.

A call to generate a two-level navbar then only requires the page title of the sub-page. Hence, the call:

PHP Code:

$navbar = get_navbar('Sub-page name'); 


would contain code along these lines:

PHP Code:

construct_navbits(array($EXT_url => $pagetitle, 
                        ''       => 'Sub-page name'
                        )); 


It is the most common sort of design consideration to hide the structure of data where feasible. We now have the details of building a navbar in exactly one place, called by extensions.