As for the gui buttons, there seems to be two problems. 1) The plugin
script doesn't really properly run the code.embed pages through the
BOLTMembed function (but rather the snippets). Probably because the
embed capabilities didn't exist back then. And 2) The embed function
itself no longer works properly as it now inserts line breaks (this
has to do with the recent vspace changes). I will release a lightly
upgraded gui plugin and soon a new release to BoltWire that will
repair this issue. In fact, we will no longer even need the php
script--just two code.embed pages.
I also changed the images in the default code.embed.gui page to take a
class rather than a style and will add the appropriate style to the
default style sheet in the next release. Previously the default
settings give the buttons a generous margin/padding, spreading them
out too far. This change keeps the spaciousness around most graphics
but disables it in the gui buttons. On custom css pages it might be
worth adding this line:
img.fmt, a img.fmt { padding: 0px; margin: 0px; }
Now for the bullets, in all my tests of normal markup, I am getting
the expected output. For example:
test
* one
* two
* three
test
test
* one
* two
* three
test
Outputs nicely to:
text
<ul><li>one</li><li>two</li><li>three</li></ul>
text
<p>text</p>
<ul><li>one</li><li>two</li><li>three</li></ul>
<p>text</p>
Even raw html like this works with no extra line breaks output:
<ul>
<li>one</li>
<li>two</li>
</ul>
<ul>
<li>one</li>
<li>two</li>
</ul>
I suspect your problem has something to do with the way your plugins
are sent back to the page. If you could show me a bit of the code I
might be able to offer a suggestion. It's probably as simple as
escaping the output, wrapping it in "<nolines>$output</nolines>" or
something equally insignificant.
The first priority should be to get the core code right so that any
markup we can generate give as close to what you expect in output as
possible, and then fix the plugins, to keep up. Though the process
proved more complex than I anticipated, we have definitely made
improvements, and I'm confident we have taken the right approach to
this. And hopefully we have it just about nailed down.
Cheers,
Dan
On Sun, May 2, 2010 at 1:25 PM, Kevin <[email protected]> wrote:
> This messed up GUIButtons by making them be one per line instead one next to
> each other.
>
> It is because GUIButtons output with a linefeed after each button. The new
> code makes that an unwanted <br />
>
> Same thing is happening on some code that I use for search outputs. They
> have linefeeds after them and the new code changes that to <br />
>
> Example:
>
> <ul><li><a href="http://websiteaddress/tnet/solutions/apps";
>>Apps</a></li></ul>
> <ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/acrobatreader"; >Adobe
> Acrobat Reader Exploit Temp Fix</a></li></ul></li></ul>
> <ul><ul><li><a href="http://websiteaddress/tnet/solutions/apps/cs4info"; >CS4
> Master Collection Key</a></li></ul></li></ul>
>
> <ul><ul><li><a href="http://websiteaddress/tnet/solutions/apps/eximbuild";
>>Exim Build (opt)</a></li></ul></li></ul>
> <ul><ul><li><a href="http://websiteaddress/tnet/solutions/apps/grlevel3";
>>GRlevel3 App Data</a></li></ul></li></ul>
> <ul><ul><li><a href="http://websiteaddress/tnet/solutions/apps/proftpd";
>>ProFTPD Build</a></li></ul></li></ul>
> <ul><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/proftpd/selfsign"; >Securing
> FTP</a></li></ul></li></ul></li></ul>
> <ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/studio2008vbmissingform";
>>Missing Form Designer</a></li></ul></li></ul>
> <ul><li><a href="http://websiteaddress/tnet/solutions/cellphones"; >Cell
> Phones</a></li></ul>
>
> Turns into (note that it replaced the linefeeds <br/>):
>
> <ul><li><a href="http://websiteaddress/tnet/solutions/apps";
>>Apps</a></li></ul><br /><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/acrobatreader"; >Adobe
> Acrobat Reader Exploit Temp Fix</a></li></ul></li></ul><br /><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/cs4info"; >CS4 Master
> Collection Key</a></li></ul></li></ul><br /><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/eximbuild"; >Exim Build
> (opt)</a></li></ul></li></ul><br /><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/grlevel3"; >GRlevel3 App
> Data</a></li></ul></li></ul><br /><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/proftpd"; >ProFTPD
> Build</a></li></ul></li></ul><br /><ul><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/proftpd/selfsign"; >Securing
> FTP</a></li></ul></li></ul></li></ul><br /><ul><ul><li><a
> href="http://websiteaddress/tnet/solutions/apps/studio2008vbmissingform";
>>Missing Form Designer</a></li></ul></li></ul><br /><ul><li><a
> href="http://websiteaddress/tnet/solutions/cellphones"; >Cell
> Phones</a></li></ul><br />
>
> This is a major change from how the system interprets generated output ie it
> didn't use to do this.
>
> On Sun, May 2, 2010 at 5:07 AM, The Editor <[email protected]> wrote:
>>
>> Sorry for the long delay in getting to this release. I've been busy
>> with another big project I'm working on, and to be honest--I was
>> stumped on the last few vspace problems reported. Eventually though, I
>> came up with some ideas for working around them, and it all now seem
>> to be working! Throughout the process, I was also making lot's of
>> little fixes, so this ends up being a pretty good upgrade. I would
>> consider it mildly experimental however, because there were a few
>> systemic changes to get the vspacing functions working as intended.
>>
>> http://www.boltwire.com/files/boltwire3.4.12.zip
>>
>> * Fixed error message when no data is passed to the savedata function.
>> * Search function can now take $args[1] for search query, or
>> $args['text'].
>> * A bit more work on buttons so label gets assigned properly.
>> * A bit more work on select menu options so label gets assigned properly.
>> * Now info extensions get passed the target page as well as the other
>> parameters to make it easier to modify the specified info page.
>> * Added a name=page option to the breadcrumbs function, to use page
>> instead of title.
>> * Slight tweaks to default text and box colors to give more contrast
>> and improve readability
>> * Slight reworking of the include function so now have more functional
>> options: (1) basepage=true, (2) replace=true and (3) basepage=true &
>> replace=false.
>> * More work on the vspace code to eliminate some of the remaining
>> bugs. Required tinkering with several sections of the code (including
>> templates), so consider mildly experimental.
>> * Reworked divs/spans so they can be nested properly.
>> * Slight performance tweak to the BOLTescape function.
>> * Major reworking of BoltWire's internal help system to make it into a
>> function. Split site.help into help (for members) and site.help (for
>> admins). To use, go to either page. This will prove extremely handy
>> for our upcoming documentation system.
>> * Some fixes to action.plugins to repair display errors.
>>
>> 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.
>>
>
> --
> 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.
>
--
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.
