On Mon, Feb 23, 2009 at 2:37 PM, Hans <[email protected]> wrote:

> I did not think to utilise $BOLTconfig. This is actually quite nice!
>
> I implemented  this solution for the ShowHide plugin:
>
> The function has a $defaults array for showhide defaults.
> Then it checks for $BOLTconfig['showhide'],
> then it merges the arrays $args (supplied parameters),
> $BOLTconfig['showhide'] and $defaults:
>
> $config =  (is_array($BOLTconfig['showhide'])) ?
> $BOLTconfig['showhide'] : array();
> $args = array_merge($defaults, $config, $args);
>
> That's all. No need to call BOLTconfig(), or the function I proposed.
> And the BOLTFshowhide() function $defaults do not need to be global.
> I think this si a good blueprint. What do you think?

This is WAY cool... I think I may need to rewrite some of the
functions in BoltWire!  Quick, somebody document this somewhere...

> BTW: in engine.php lines 16-33 you don't need to call BOLTdefault(),
> as nothing has been set yet in any case, the script is just starting.

We do, actually. Because if you have a non-default installation, these
settings will be modified in index.php before the engine loads.

> BUT (different question this) I would like a different permanent
> error_reporing level.
> I need to see the normal php errors, and not have the screen just white!

Not sure what is happening here. You can put $errorReporting = true;
in index.php before calling engine.php. You can also add &error=true
to a url and get the same thing. (Maybe the latter is not a good idea
now that I think about it...)  See if this doesn't help. It may
interfere with indexing though and other background functions. I use
it offline for development and keep it off (default) for live sites.

> AND I have problems editing engine.php with my favourite text editor,
> as it screws it up!!!
> This has something to do with the utf code characters lines 1900...
> they look all weird in my editor...

Not sure what to suggest about this either. I still find charsets
confusing. I'm sure there are ascii escape codes for those chars.
Perhaps we can rewrite that function using those codes somehow. I'm
open to suggestions...

Cheers,
Dan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to