Greetings to whomever can help me,
I'm relatively a new BlueVoda editor user and for some time now
I've run into the problem where I want/need to edit the "grayed out code"
which BV writes for various instruction sets. I'm familiar with the "Before
Tag", "Inside Tag", and "After Tag" options, [and they are helpful] if one
wishes to "add" additional code to the existing HTML code recreated by BV
but how do we edit the existing "gray code" that is already written???
For example, I have a small test "index.html" page with a menu box
[of about a half dozen buttons] located on the left hand side of my page.
The menu box created by "default" is great however I'm finding it is not
wide enough to accommodate all the "button text" I wish to enter. I've
tried modifying the "Properties" section for the menu box, however there
apparently is no corresponding parameter to increase the actual width of
my menu buttons. I can click on the box [to "select" it] via the "4 arrows buttons that appear" to move it and reshape it, but when I attempt to
stretch the box....it only allocates more space on the webpage for the
"menu area" without doing anything to increase the overall menu size of
the buttons [themselves]. It does NOT increase the individual "width of
each menu button", it only creates more "blank space".
To further illustrate my point I have included the following code which
I'd like to edit...but can't because it is "grayed out code" and therefore
NOT ACCESSIBLE for editing:
<TABLE border="0" cellpadding="0" cellspacing="0">
<TR><TD height="10"></TD></TR><TR>
<TD align="left" valign="top" width="135" height="20"><A href="http://www.qcf.com/resources2.php"><IMG id="bv01002" src="bv01002.gif" alt="http://www.qcf.com/resources2.php" align="top" border="0" width="135" height="20" onmouseover="SwapImage(1,0,'bv01002','bv01002_over .gif')" onmouseout="SwapImage(0,0,'bv01002','bv01002.gif') "></A></TD>
</TR>.........etc, etc, etc.
Please note the instruction line:
<TD align="left" valign="top" WIDTH="135" height="20">.....
I believe we need to increase the 'WIDTH=135' value in the line to some
other value.....perhaps "WIDTH = 140. 150, or 160". But suffice to say,
I can not edit this section at all because it is "protected by the BlueVoda
Editor" [via a "gray" designation] and therefore untouchable.
As a work around I know I/we can always go edit the "html" code [after
the fact] when it is finally "published" but that scenario somewhat
defeats the purpose of having a user friendly "webpage editor" such as
BlueVoda, in the first place......does it not???? In other words, if users
need to exit edit "published html" files because we can't edit them within
the editor itself:
a) we are relegated to finding or using another editor on
the server side to tweak final designs [which in my
humble opinion defeats the purpose of needing BV], and
b) our final "html" files are no longer compatible with
the BlueVoda "bvp" files left behind on the client side.
Would appreciate any help out of this dilemma...thanks in advance for
whatever help is out there!!!!
Regards,
Dan
I'm relatively a new BlueVoda editor user and for some time now
I've run into the problem where I want/need to edit the "grayed out code"
which BV writes for various instruction sets. I'm familiar with the "Before
Tag", "Inside Tag", and "After Tag" options, [and they are helpful] if one
wishes to "add" additional code to the existing HTML code recreated by BV
but how do we edit the existing "gray code" that is already written???
For example, I have a small test "index.html" page with a menu box
[of about a half dozen buttons] located on the left hand side of my page.
The menu box created by "default" is great however I'm finding it is not
wide enough to accommodate all the "button text" I wish to enter. I've
tried modifying the "Properties" section for the menu box, however there
apparently is no corresponding parameter to increase the actual width of
my menu buttons. I can click on the box [to "select" it] via the "4 arrows buttons that appear" to move it and reshape it, but when I attempt to
stretch the box....it only allocates more space on the webpage for the
"menu area" without doing anything to increase the overall menu size of
the buttons [themselves]. It does NOT increase the individual "width of
each menu button", it only creates more "blank space".
To further illustrate my point I have included the following code which
I'd like to edit...but can't because it is "grayed out code" and therefore
NOT ACCESSIBLE for editing:
<TABLE border="0" cellpadding="0" cellspacing="0">
<TR><TD height="10"></TD></TR><TR>
<TD align="left" valign="top" width="135" height="20"><A href="http://www.qcf.com/resources2.php"><IMG id="bv01002" src="bv01002.gif" alt="http://www.qcf.com/resources2.php" align="top" border="0" width="135" height="20" onmouseover="SwapImage(1,0,'bv01002','bv01002_over .gif')" onmouseout="SwapImage(0,0,'bv01002','bv01002.gif') "></A></TD>
</TR>.........etc, etc, etc.
Please note the instruction line:
<TD align="left" valign="top" WIDTH="135" height="20">.....
I believe we need to increase the 'WIDTH=135' value in the line to some
other value.....perhaps "WIDTH = 140. 150, or 160". But suffice to say,
I can not edit this section at all because it is "protected by the BlueVoda
Editor" [via a "gray" designation] and therefore untouchable.
As a work around I know I/we can always go edit the "html" code [after
the fact] when it is finally "published" but that scenario somewhat
defeats the purpose of having a user friendly "webpage editor" such as
BlueVoda, in the first place......does it not???? In other words, if users
need to exit edit "published html" files because we can't edit them within
the editor itself:
a) we are relegated to finding or using another editor on
the server side to tweak final designs [which in my
humble opinion defeats the purpose of needing BV], and
b) our final "html" files are no longer compatible with
the BlueVoda "bvp" files left behind on the client side.
Would appreciate any help out of this dilemma...thanks in advance for
whatever help is out there!!!!
Regards,
Dan
Comment