On Sun, Aug 2, 2009 at 6:08 AM, DrunkenMonk<[email protected]> wrote: > >> The data function allows you to set certain prescribed data fields on >> a page using a function. Clever. But once that code is put on the >> page, it tells BoltWire to resave the data variable every time it >> loads the page. Highly inefficient. I think there might be some >> isolated uses for it, but at the very least it could be shunted off to >> a plugin or something don't you think? > > I'm halfway through creating a database like solution for my student- > pubs inventory using the data function. If you change it, optimize it. > If you make me rework code, I may have to scream.
Relax. If I take it out of the core, I'll put it in a plugin, so you just install the plugin, with absolutely no change in functionality for you. I am curious though how you are using the function. If it is the kind of thing that might be useful to lot's of other folks, I'd be willing too keep it in the core. >> What about the getline function, which allows you to retrieve line 7 >> of some.page? Do we really need that? I thought it was a system >> function, but it doesn't seem to be used anywhere else in the code. >> Possibly an action page though I can't imagine which one. Shouldn't >> this be a plugin as well? > > I don't know. I can't think of a single use where regions wouldn't > work better, so I don't mind. You mean, anchor sections? Well, I suppose there are uses, but you are right, probably obscure. >> Looking over the markups page I see some possibilities for improvement: ... > > Well, have you considered defining the markup rules using bison or > some other parser generator? > Done well, we would get recursive functions and cleaner rule > definitions. Regular expressions are good but hardly perfect. > > I thought about giving this a go myself a few months ago, but didnt > have the time. Still I got the feeling we could gain a lot. Never heard of Bison, but I'm not too keen on requiring another software package to get BoltWire to run. I'm pretty pleased with what we have. If there are problems in the markup rules, the problem is probably not php's regex capabilities, they are just my own lack of expertise. The tweaks I suggested just came to me looking at the code pretty much for about the first time in a month or so. Seeing things through fresh eyes highlighted some areas ready for improvement. All should be mostly transparent upgrades, and the ones I picked out all look easy enough to do. Or at least give a try. Nothing to lose... 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 -~----------~----~----~----~------~----~------~--~---
