Deprecated: Optional parameter $default declared before required parameter $err_msg is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php on line 1401

Deprecated: Optional parameter $memorize declared before required parameter $err_msg is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php on line 1401

Deprecated: Optional parameter $default declared before required parameter $err_msg is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php on line 2320

Deprecated: Optional parameter $memorize declared before required parameter $err_msg is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php on line 2320

Deprecated: Creation of dynamic property GeneralSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: Creation of dynamic property AbstractSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: Optional parameter $coll_ID declared before required parameter $selected_value is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/collections/model/_blog.funcs.php on line 1942

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home4/tylering/public_html/b2e/inc/links/model/_link.funcs.php on line 1024

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home4/tylering/public_html/b2e/inc/links/model/_link.funcs.php on line 1024

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home4/tylering/public_html/b2e/inc/links/model/_link.funcs.php on line 1024

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home4/tylering/public_html/b2e/inc/links/model/_link.funcs.php on line 1024

Deprecated: Optional parameter $action declared before required parameter $read_only_list is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/maintenance/model/_maintenance.funcs.php on line 624

Deprecated: Optional parameter $overwrite declared before required parameter $read_only_list is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/maintenance/model/_maintenance.funcs.php on line 624

Deprecated: Optional parameter $renderers declared before required parameter $params is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 2013

Deprecated: Optional parameter $current_renderers declared before required parameter $params is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 2158

Deprecated: Optional parameter $current_renderers declared before required parameter $params is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 2336

Deprecated: Creation of dynamic property UserSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_init_login.inc.php on line 81

Deprecated: Optional parameter $prefix declared before required parameter $dbIDname is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/_core/model/dataobjects/_dataobjectcache.class.php on line 133

Deprecated: Creation of dynamic property CollectionSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/inc/_core/_template.funcs.php on line 467

Deprecated: Optional parameter $chapter_mode declared before required parameter $item_index is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/items/model/_itemlistlight.class.php on line 2404

Deprecated: Optional parameter $params declared before required parameter $content_is_displayed is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/items/model/_itemlistlight.class.php on line 2593

Deprecated: Creation of dynamic property ItemList2::$filterset_name is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlistlight.class.php on line 114

Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php on line 1407

Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php on line 1407

Deprecated: Optional parameter $dbprefix declared before required parameter $dbIDname is implicitly treated as a required parameter in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 76

Deprecated: Creation of dynamic property ItemQuery::$dbtablename is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 78

Deprecated: Creation of dynamic property ItemQuery::$dbprefix is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 79

Deprecated: Creation of dynamic property ItemQuery::$dbIDname is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 80

Deprecated: Creation of dynamic property ItemQuery::$Blog is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 231

Deprecated: Creation of dynamic property ItemQuery::$cat_array is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 232

Deprecated: Creation of dynamic property ItemQuery::$cat_modifier is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 233

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: Creation of dynamic property ItemQuery::$assignees_logins is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 525

Deprecated: Creation of dynamic property ItemQuery::$author_assignee is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 557

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: Creation of dynamic property ItemQuery::$m is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 842

Deprecated: Creation of dynamic property ItemQuery::$w is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 843

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Deprecated: Creation of dynamic property Item::$objtype is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 164

Deprecated: Creation of dynamic property Item::$datestart is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemlight.class.php on line 175

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/inc/_core/_template.funcs.php on line 40

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/inc/_core/_template.funcs.php on line 405

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/inc/_core/_template.funcs.php on line 406

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/inc/_core/_template.funcs.php on line 407

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/inc/_core/_template.funcs.php on line 408

Deprecated: Creation of dynamic property ItemQuery::$dbtablename is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 78

Deprecated: Creation of dynamic property ItemQuery::$dbprefix is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 79

Deprecated: Creation of dynamic property ItemQuery::$dbIDname is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 80

Deprecated: Creation of dynamic property ItemQuery::$Blog is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 231

Deprecated: Creation of dynamic property ItemQuery::$cat_array is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 232

Deprecated: Creation of dynamic property ItemQuery::$cat_modifier is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 233

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: Creation of dynamic property ItemQuery::$assignees_logins is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 525

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10535

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/_core/_misc.funcs.php on line 10540

Deprecated: Creation of dynamic property ItemQuery::$m is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 842

Deprecated: Creation of dynamic property ItemQuery::$w is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_itemquery.class.php on line 843

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/skins/_rss2/index.main.php on line 45

Warning: Cannot modify header information - headers already sent by (output started at /home4/tylering/public_html/b2e/inc/_core/_param.funcs.php:1401) in /home4/tylering/public_html/b2e/skins/_rss2/index.main.php on line 46
Switched Keys - Category: "Design" https://tylerhosting.com/b2e/dbell.php Switched Keys, the blogs of Dana Bell of Tyler, Texas en-US http://blogs.law.harvard.edu/tech/rss 60 Images in b2evolution https://tylerhosting.com/b2e/dbell.php/images-in-b2evolution Sat, 12 Aug 2017 03:04:00 +0000 Dana Bell Information Technology Site Small Talk Design Computing 394@https://tylerhosting.com/b2e/
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property tinymce_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property calendar_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property calendar_plugin::$dbtable is deprecated in /home4/tylering/public_html/b2e/plugins/_calendar.plugin.php on line 53

Deprecated: Creation of dynamic property calendar_plugin::$dbprefix is deprecated in /home4/tylering/public_html/b2e/plugins/_calendar.plugin.php on line 54

Deprecated: Creation of dynamic property calendar_plugin::$dbIDname is deprecated in /home4/tylering/public_html/b2e/plugins/_calendar.plugin.php on line 55

Deprecated: Creation of dynamic property quicktags_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property auto_anchors_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property shortlinks_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property custom_tags_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property archives_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property archives_plugin::$dbtable is deprecated in /home4/tylering/public_html/b2e/plugins/_archives.plugin.php on line 54

Deprecated: Creation of dynamic property archives_plugin::$dbprefix is deprecated in /home4/tylering/public_html/b2e/plugins/_archives.plugin.php on line 55

Deprecated: Creation of dynamic property archives_plugin::$dbIDname is deprecated in /home4/tylering/public_html/b2e/plugins/_archives.plugin.php on line 56

Deprecated: Creation of dynamic property email_elements_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property financial_contribution_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property inlines_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property ping_b2evonet_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property ping_pingomatic_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property twitter_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property webmention_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property webmention_plugin::$ping_service_process_message is deprecated in /home4/tylering/public_html/b2e/plugins/webmention_plugin/_webmention.plugin.php on line 52

Deprecated: Creation of dynamic property webmention_plugin::$ping_service_setting_title is deprecated in /home4/tylering/public_html/b2e/plugins/webmention_plugin/_webmention.plugin.php on line 53

Deprecated: Creation of dynamic property autolinks_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property videoplug_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property auto_p_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property mermaid_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property texturize_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property nofollow_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property content_blocks_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property table_contents_plugin::$classfile_path is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_plugins.class.php on line 413

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<p>Many years ago I started using <a href="http://b2evolution.net/">b2evolution</a> for my blog even though it was not the most popular platform. I'm still using it. Although it is complex, it gives me options that don't exist in other platforms. Now that it has expanded to include other types of collections (photo blogs, manuals, etc), it is even more complex. Unfortunately, the image insertion routines in b2evolution are quite inflexible, and I suspect that is one reason it will never be very popular.</p> <p>The guide says you should attach the image where you want it, but it doesn't include the file in the page markup and instead includes a tag that identifies the image. The logic presented in the on-line forums is that you can adjust the stylesheet and php to apply uniformly to all images. You can put the image in different sections (teaser, cover, in-line) of the post and it supposedly is more efficient that way.</p> <h3>The Issue</h3> <p>Although you have multiple options for placement (vertically) in a post, if it's an in-line image you can't see it in the editor. Instead you see . Additionally you can't modify the formatting of the image. That's where the problems resides. If b2evolution included the code in-line (like it used to) I could modify the HTML/CSS to format the image. </p> <p>Emulating a print publication, I like to wrap text around some images, and like adjusting the size to make it look more balanced. Well, there is a way to include the markup, but it's not intuitive.</p> <h3>The Work Around</h3> <p>I've discovered after inserting all my images that there is a viable workaround to get the code into the post, something that used to be an option in the editor in past versions.</p> <p>1. Go to the b2e Back-office and select Files &gt; Browse and upload the images for the post. I prefer to put them in the root collection folder, not the quick-uploads.<br /> <br />2. From the post, attach any image to the post (ideally an inline). The easiest way is to select Attach existing files and select one. You won't be including that in the post, but you will be using that image to get to other files you would like to insert. If an image tag is inserted into the post you can delete it if you want. </p> <p> <a href="http://www.tylerhosting.com/b2e/media/blogs/dbell/attachimage.png?mtime=1502468848"><img src="http://www.tylerhosting.com/b2e/media/blogs/dbell/attachimage.png?mtime=1502468848" alt="" width="431" height="56" /></a></p> <p>3. Position your cursor at the point in your post where you want to include one of your uploaded images.</p> <p>4. Go to the attached image in the Images and Attachments section and click on the Locate file icon (bull's eye).</p> <div class="image_block" style="float: right; margin-left: 20px;"><a href="http://www.tylerhosting.com/b2e/media/blogs/dbell/locateimage.png?mtime=1502468848"><img class="loadimg" src="http://www.tylerhosting.com/b2e/media/blogs/dbell/locateimage.png?mtime=1502468848" alt="" width="115" height="121" /></a> </div> <p>5. When the Attach files dialog box is displayed find the file you really want. You may have to change folders to find it. Again, I prefer to use images in the root collection folder.</p> <p>6. Check the box for the file to select it. Don't press Attach. </p> <p>7. Finally, at the bottom, with selected files: change the option to Insert IMG/link into post and press Go.</p> <h3>Formatting Images </h3> <p>The main reason I want the code in the post is so I can customize the image. In order to do that switch to Markup view and find the image's code. It'll begin with something like</p> <blockquote> <pre>&lt;div class="image_block"&gt;&lt;a href=".."&gt;</pre> </blockquote> <p>Two of the modifications that I generally make are to position the image and resize the image to look good in the post. By positioning, I generally float it left or right.</p> <h4>Floating Images</h4> <p>In markup, find the image markup as noted above and change the div to add</p> <blockquote> <pre>style="float:right"</pre> </blockquote> <p>so it looks like this</p> <blockquote> <pre>&lt;div class="image_block" style="float:right"&gt;&lt;a href=".."&gt;</pre> </blockquote> <p>If you are floating, it might also be necessary to adjust the margins by changing it to </p> <blockquote> <pre>style="float:right; margin-left:20px"</pre> </blockquote> <h4>Resizing</h4> <p>The image should show the actual size in the img tag and would look something like this.</p> <blockquote> <pre>width="431" height="56" /&gt;</pre> </blockquote> <p>If the size is not appropriate for the post, I simply change the width to a percentage and drop the height so it would look something like this</p> <blockquote> <pre>width="35" /&gt;</pre> </blockquote> <p>I have used b2evolution for many years, and find it useful for multiple blogs, but I guess these kinds of challenges are one reason it is not so popular as a blogging platform.</p><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/images-in-b2evolution">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>
Deprecated: Creation of dynamic property autolinks_plugin::$setting_nofollow_auto is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 439

Deprecated: Creation of dynamic property autolinks_plugin::$setting_autolink_defs_coll_db is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 442

Deprecated: Creation of dynamic property autolinks_plugin::$setting_autolink_urls is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 443

Deprecated: Creation of dynamic property autolinks_plugin::$setting_autolink_emails is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 444

Deprecated: Creation of dynamic property autolinks_plugin::$setting_autolink_username is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 445

Deprecated: Creation of dynamic property autolinks_plugin::$setting_autolink_tag is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 446

Deprecated: Creation of dynamic property PluginSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: Creation of dynamic property PluginSettings::$plugin_ID is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_pluginsettings.class.php on line 36

Deprecated: Creation of dynamic property PluginSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: Creation of dynamic property PluginSettings::$plugin_ID is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_pluginsettings.class.php on line 36

Deprecated: Creation of dynamic property autolinks_plugin::$replacement_link_array is deprecated in /home4/tylering/public_html/b2e/plugins/_autolinks.plugin.php on line 341

Deprecated: Creation of dynamic property videoplug_plugin::$video_width is deprecated in /home4/tylering/public_html/b2e/plugins/videoplug_plugin/_videoplug.plugin.php on line 152

Deprecated: Creation of dynamic property videoplug_plugin::$video_height is deprecated in /home4/tylering/public_html/b2e/plugins/videoplug_plugin/_videoplug.plugin.php on line 153

Deprecated: Creation of dynamic property PluginSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: Creation of dynamic property PluginSettings::$plugin_ID is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_pluginsettings.class.php on line 36

Deprecated: Creation of dynamic property PluginSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121

Deprecated: Creation of dynamic property PluginSettings::$plugin_ID is deprecated in /home4/tylering/public_html/b2e/inc/plugins/model/_pluginsettings.class.php on line 36

Deprecated: Creation of dynamic property auto_p_plugin::$use_auto_br is deprecated in /home4/tylering/public_html/b2e/plugins/_auto_p.plugin.php on line 126

Deprecated: Creation of dynamic property auto_p_plugin::$add_p_in_block is deprecated in /home4/tylering/public_html/b2e/plugins/_auto_p.plugin.php on line 127

Deprecated: Creation of dynamic property auto_p_plugin::$skip_tags is deprecated in /home4/tylering/public_html/b2e/plugins/_auto_p.plugin.php on line 128

Deprecated: Creation of dynamic property nofollow_plugin::$setting_rel_options is deprecated in /home4/tylering/public_html/b2e/plugins/_nofollow.plugin.php on line 159

Deprecated: Creation of dynamic property nofollow_plugin::$setting_target_options is deprecated in /home4/tylering/public_html/b2e/plugins/_nofollow.plugin.php on line 172

Many years ago I started using b2evolution for my blog even though it was not the most popular platform. I'm still using it. Although it is complex, it gives me options that don't exist in other platforms. Now that it has expanded to include other types of collections (photo blogs, manuals, etc), it is even more complex. Unfortunately, the image insertion routines in b2evolution are quite inflexible, and I suspect that is one reason it will never be very popular.

The guide says you should attach the image where you want it, but it doesn't include the file in the page markup and instead includes a tag that identifies the image. The logic presented in the on-line forums is that you can adjust the stylesheet and php to apply uniformly to all images. You can put the image in different sections (teaser, cover, in-line) of the post and it supposedly is more efficient that way.

The Issue

Although you have multiple options for placement (vertically) in a post, if it's an in-line image you can't see it in the editor. Instead you see . Additionally you can't modify the formatting of the image. That's where the problems resides. If b2evolution included the code in-line (like it used to) I could modify the HTML/CSS to format the image. 

Emulating a print publication, I like to wrap text around some images, and like adjusting the size to make it look more balanced. Well, there is a way to include the markup, but it's not intuitive.

The Work Around

I've discovered after inserting all my images that there is a viable workaround to get the code into the post, something that used to be an option in the editor in past versions.

1. Go to the b2e Back-office and select Files > Browse and upload the images for the post. I prefer to put them in the root collection folder, not the quick-uploads.

2. From the post, attach any image to the post (ideally an inline). The easiest way is to select Attach existing files and select one. You won't be including that in the post, but you will be using that image to get to other files you would like to insert. If an image tag is inserted into the post you can delete it if you want. 

 

3. Position your cursor at the point in your post where you want to include one of your uploaded images.

4. Go to the attached image in the Images and Attachments section and click on the Locate file icon (bull's eye).

 

5. When the Attach files dialog box is displayed find the file you really want. You may have to change folders to find it. Again, I prefer to use images in the root collection folder.

6. Check the box for the file to select it. Don't press Attach. 

7. Finally, at the bottom, with selected files: change the option to Insert IMG/link into post and press Go.

Formatting Images 

The main reason I want the code in the post is so I can customize the image. In order to do that switch to Markup view and find the image's code. It'll begin with something like

<div class="image_block"><a href="..">

Two of the modifications that I generally make are to position the image and resize the image to look good in the post. By positioning, I generally float it left or right.

Floating Images

In markup, find the image markup as noted above and change the div to add

style="float:right"

so it looks like this

<div class="image_block" style="float:right"><a href="..">

If you are floating, it might also be necessary to adjust the margins by changing it to 

style="float:right; margin-left:20px"

Resizing

The image should show the actual size in the img tag and would look something like this.

width="431" height="56" />

If the size is not appropriate for the post, I simply change the width to a percentage and drop the height so it would look something like this

width="35" />

I have used b2evolution for many years, and find it useful for multiple blogs, but I guess these kinds of challenges are one reason it is not so popular as a blogging platform.

]]>
https://tylerhosting.com/b2e/dbell.php/images-in-b2evolution#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=394
DBS Tyler Update https://tylerhosting.com/b2e/dbell.php/dbs_tyler_update Fri, 25 Apr 2008 00:09:00 +0000 Dana Bell Business Religion Design 208@https://tylerhosting.com/b2e/
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<div class="content_full"> <div class="bText"> <p>An update on the logo design for <a href="http://www.dbstyler.com/">DBS</a>. This one changes the color a bit and adds a pie chart in the back. A pie demonstrates how business and DBS is involved in multiple areas while at the same time using a presentation graphic suggests the professional nature of the services to be offered. </p> <p><img src="http://www.dbstyler.com/images/dbstylerpie2.jpg" alt="" title="" /> </p> <p>I'm still considering other graphics that might better illustrate the segmented nature of business management something like a segmented orange. Still they do not present the significance that what happens in one area affects other areas. I do like orange juice but that would really be too oblique. </p> <p>As Eastman put it "The project continues!!!"</p></div></div><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/dbs_tyler_update">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>

An update on the logo design for DBS. This one changes the color a bit and adds a pie chart in the back. A pie demonstrates how business and DBS is involved in multiple areas while at the same time using a presentation graphic suggests the professional nature of the services to be offered.

I'm still considering other graphics that might better illustrate the segmented nature of business management something like a segmented orange. Still they do not present the significance that what happens in one area affects other areas. I do like orange juice but that would really be too oblique.

As Eastman put it "The project continues!!!"

]]>
https://tylerhosting.com/b2e/dbell.php/dbs_tyler_update#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=208
DBS Tyler https://tylerhosting.com/b2e/dbell.php/dbs_tyler Wed, 23 Apr 2008 08:01:59 +0000 Dana Bell Business Religion Design 207@https://tylerhosting.com/b2e/ <p><a href="http://www.dbstyler.com/">http://www.dbstyler.com/</a></p>
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<div class="content_full"> <div class="bText"> <p>I started working on developing Diversified Business Services again over the weekend. I registered the domain <a href="http://www.dbstyler.com/">dbstyler.com</a> and designed a new logo for it. I've actually been playing with this for decades so the new logo is not the first design or even the best design. It is just another effort to create a distinctive logo that is representative of the organization. </p> <p>Diversified Business Services or DBS Tyler is the name of a business consulting and services company that I've used over the years. On the one hand it is a simple operation while on the other there are multiple areas of specialty that actually deserve to have their own identity. Thus the problem with designing a logo for the company is analagous to painting a picture of a family with everyone in it bearing the family resemblance while making sure that individual members are also distinguishable. </p> <p>To do that I decided to focus on the abbreviations DBS and add "tyler" or the name of the specialty at the end. In sketching the logo I almost always run the two together or overlap them. I designed a DBS graphics logo for a teeshirt advertisement a few years ago using that concept. It is simply the text fancied up. But the style doesn't ID the company as a business consulting company. </p> <p><img src="http://www.dbstyler.com/images/dbsgraphicsgoldall.jpg" alt="" title="" /> </p> <p>I've tried adding an icon to the logo but always ended up dropping it because it made it too busy. The current plan is to develop a base logo for DBS and append either the city or specialty in a style that identifies that area. The most recent development uses that idea. </p> <p><img src="http://www.dbstyler.com/images/dbstylermedium.jpg" alt="" title="" /> </p> <p>I'm still not impressed so the work continues. So it is with this kind of art. There always seems to be room for improvement. There always seems to be something missing. And so it is with life too. Without the fellowship of Jesus and the guidance of the Holy Spirit there always seems to be something missing.</p></div></div><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/dbs_tyler">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>
http://www.dbstyler.com/

I started working on developing Diversified Business Services again over the weekend. I registered the domain dbstyler.com and designed a new logo for it. I've actually been playing with this for decades so the new logo is not the first design or even the best design. It is just another effort to create a distinctive logo that is representative of the organization.

Diversified Business Services or DBS Tyler is the name of a business consulting and services company that I've used over the years. On the one hand it is a simple operation while on the other there are multiple areas of specialty that actually deserve to have their own identity. Thus the problem with designing a logo for the company is analagous to painting a picture of a family with everyone in it bearing the family resemblance while making sure that individual members are also distinguishable.

To do that I decided to focus on the abbreviations DBS and add "tyler" or the name of the specialty at the end. In sketching the logo I almost always run the two together or overlap them. I designed a DBS graphics logo for a teeshirt advertisement a few years ago using that concept. It is simply the text fancied up. But the style doesn't ID the company as a business consulting company.

I've tried adding an icon to the logo but always ended up dropping it because it made it too busy. The current plan is to develop a base logo for DBS and append either the city or specialty in a style that identifies that area. The most recent development uses that idea.

I'm still not impressed so the work continues. So it is with this kind of art. There always seems to be room for improvement. There always seems to be something missing. And so it is with life too. Without the fellowship of Jesus and the guidance of the Holy Spirit there always seems to be something missing.

]]>
https://tylerhosting.com/b2e/dbell.php/dbs_tyler#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=207
Resume Work https://tylerhosting.com/b2e/dbell.php/http://www.saltatoria.com/dbell/resume/index.html Tue, 11 Mar 2008 22:26:00 +0000 Dana Bell Business Design Computing Personal Thoughts 197@https://tylerhosting.com/b2e/
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<div class="content_full"> <div class="bText"> <p>Over a week ago I got my layoff notice at The University of Texas Health Science Center at Tyler. I was one of 60 people selected for that privilege. Today I began the long process of updating my <a href="http://www.saltatoria.com/dbell/resume/index.html">resume</a>.</p> <p>It is a long process because there are so many things that I can do and because I have so many interests. One thing leads to another and that to another until after three decades I'm all over the place and can adapt to any number of situations. In printing I developed an interest in design as well as operation management. Then when I started using computers in the 1980's I developed interest in programming. Computers merged with design and business interests and Design evolved to include photography. And of course I began writing when I was in high school and now I have so many things to write about.</p> <p>I suppose I inherited a lot of that ability from my family. High levels of intelligence and good business skills are characteristic of my extended family. Then there is the fact that I was raised by my grandparents who instilled in me a strong work ethic. And finally I suspect my faith has something to do with my choices and willingness to serve. That's not to say that my independent nature didn't have something to do with it. I didn't need to take a class in Photoshop to learn and get certified in it or InDesign. Everything I learned about computers was before I took any computer classes. I don't need a teacher or a class. Give me a book and I'll learn from it and figure out the rest. That's not to say education is worthless but to me it is so slow and boring.</p> <p>It will also be a long process because it might be easier to start my own business. Diversified Business Services is the name I used for much of my previous after hours work and I could easily (relatively speaking of course) expand that. So I will be working on both.</p> <p>And finally off-line resume development will require that I create separate resumes for each area. Employers don't understand the concept that a person with a broad range of skills can learn and adapt to most any job without having specific job qualifications. I've spent enough of my time cleaning up after some of those qualified applicants to know better. But that is another discussion topic.</p> <p>This post is really a plug for my <a href="http://www.saltatoria.com/dbell/resume/index.html">resume</a>. If you are local and want to <a href="http://www.saltatoria.com/dbell/resume/contact.html">contact</a> me about a position use the contact form on my resume. In the past couple of years I have discovered that it is difficult to solicit response on a web site because of the amount of form spam. I get as much as 30 spam messages a day on one of my email accounts. I could employ more vigorous spam control but then there is the risk of losing valid email messages. So be sure to use a name subject and content that doesn't look like spam.</p> </div> </div><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/http://www.saltatoria.com/dbell/resume/index.html">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>

Over a week ago I got my layoff notice at The University of Texas Health Science Center at Tyler. I was one of 60 people selected for that privilege. Today I began the long process of updating my resume.

It is a long process because there are so many things that I can do and because I have so many interests. One thing leads to another and that to another until after three decades I'm all over the place and can adapt to any number of situations. In printing I developed an interest in design as well as operation management. Then when I started using computers in the 1980's I developed interest in programming. Computers merged with design and business interests and Design evolved to include photography. And of course I began writing when I was in high school and now I have so many things to write about.

I suppose I inherited a lot of that ability from my family. High levels of intelligence and good business skills are characteristic of my extended family. Then there is the fact that I was raised by my grandparents who instilled in me a strong work ethic. And finally I suspect my faith has something to do with my choices and willingness to serve. That's not to say that my independent nature didn't have something to do with it. I didn't need to take a class in Photoshop to learn and get certified in it or InDesign. Everything I learned about computers was before I took any computer classes. I don't need a teacher or a class. Give me a book and I'll learn from it and figure out the rest. That's not to say education is worthless but to me it is so slow and boring.

It will also be a long process because it might be easier to start my own business. Diversified Business Services is the name I used for much of my previous after hours work and I could easily (relatively speaking of course) expand that. So I will be working on both.

And finally off-line resume development will require that I create separate resumes for each area. Employers don't understand the concept that a person with a broad range of skills can learn and adapt to most any job without having specific job qualifications. I've spent enough of my time cleaning up after some of those qualified applicants to know better. But that is another discussion topic.

This post is really a plug for my resume. If you are local and want to contact me about a position use the contact form on my resume. In the past couple of years I have discovered that it is difficult to solicit response on a web site because of the amount of form spam. I get as much as 30 spam messages a day on one of my email accounts. I could employ more vigorous spam control but then there is the risk of losing valid email messages. So be sure to use a name subject and content that doesn't look like spam.

]]>
https://tylerhosting.com/b2e/dbell.php/http://www.saltatoria.com/dbell/resume/index.html#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=197
Organized Web Design https://tylerhosting.com/b2e/dbell.php/organized_web_design Sun, 09 Mar 2008 05:57:14 +0000 Dana Bell Design Computing 196@https://tylerhosting.com/b2e/
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<div class="content_full"> <div class="bText"> <p>This week I started updating a website for a local non-profit organization. The most important part of the project was studying the site and understanding how it is built. As I studied this site I learned a little about why it can be difficult for an amateur to maintain their own websites or for an outsider to come in and work on an existing site. First is the organization or lack of organization and second is the massive amount of code and files and in particular unnecessary code and files. Keeping a website's style cohesive makes it more attractive but it should also be easier to maintain. </p> <p>In this site some of the links on the main page had been changed to refer to updated or moved files but the same links on inside pages were not updated and gave you the 404. The main problem in this case was when the page file was put in a folder the document relative links didn't work. The Javascript menu references were also an issue on those moved pages for the same reason. </p> <p>Another problem I found was that some of the files were present in both the root folder and a folder for that section. Many of these files were identical. Which file you linked to depended on what page you were on. They would seem to work but instead of linking to the file you intended it brought up one of the duplicates from which other links didn't work. This setup just creates confusion and when dealing with someone else's system you need some clarity. I'm actually one that prefers sections and a logical hierarchy but it order to simplify the mess I worked with the files in the root directory with a plan to create sections when I had everything defined. </p> <p>The graphics were created by a Fireworks function with an image for each section of the menu. I've used these before in Imageready and they can be nifty if you don't take all of the shortcuts. However there were multiple versions of the full image. They were also named with numbers based on which section it was. </p> <p><strong>The plan</strong> With Dreamweaver in hand my first priority is to repair and organize the site files. Once that is done I can do some creative work. </p> <p><em>Tread softly.</em> Because this was an active site I started the redesign by creating all new files. The names were not an issue since all of the old files used the htm extension instead of html. Everything would work for the old site until I renamed the home page. Of course I also made a backup copy of the old site. </p> <p>If you want to simplify the current site you can do that by downloading the site and moving things around. Dreamweaver will help you keep most document or root relative links working. That's not part of my plan. I have the time to do a complete rewrite and that would just take more time. New wine new wineskin. </p> <p><em>Establish order.</em> Following the adage a place for everything and everything in its place I defined the structure I was going to use. Very simply all images go in the images folder and all html files go in the root folder for now that is. For a simple site like this the css file could stay in the root folder but since it was already in a separate css folder I defined it that way. Should the site grow and require more css styles they have a neat place to go. Files that are downloaded from the site alse need a separate folder so I used Documents although there are other commonly used names. </p> <p><em>Create templates.</em> Second thing I did was create a Dreamweaver template. With Dreamweaver templates can be used to define the appearance of a page. When a page is created from the template it can be set up to be automatically updated when the template changes. This will solve the problem of keeping the menu links up to date. </p> <p><em>Simplify and name the images.</em> Use a simpler set of graphics. Instead of using the numbered image files I copied then to names that reflect what the graphic was. If it was the word "About" that was used to go to a page about the organization I named it about.jpg about.gif or about.png. </p> <p><em>Name the css properties.</em> If you mark some text and start formatting it Dreamweaver names those styles numerically as style1 style2 etc. For a simple page this can work but for a larger more complex site these styles make for a massive amount of code you would have to sort through to understand the pages. For those who don't reference css styles explicitly the problem is not visible. For the designer that is creating a standard style for the pages css styles are very useful. Having a folder full of the automatically generated css styles can be confusing. You might unknowingly update a style at one location that affects another location. Name those styles and you will know what it is used for when you want to format another section the same way. This also helps maintaining cohesion on a site. </p> <p><em>Creating pages.</em> All of the above is done only on the template. There is only one thing that's left to do on the template create the links. I don't do that yet because I haven't created the files that I will be linking to. At this stage I will create the pages based on the template and add the content for each page. I can simply copy and paste from the old page or any new content that has been added checking all of the style references. </p> <p><em>Create the links.</em> Now back to the template. Reset all links and references to use document relative links. There are advantages and disadvantages to this but using Dreamweaver the disadvantages will be taken care of. Don't forget to check the javascript menus. When you save the template Dreamweaver should ask if you want to update the pages. Just say Yes. </p> <p><em>Clean up and upload.</em> This is something that should be done in a full session. It sounds simple and usually is but if something goes wrong or there are other issues to deal with you need to have time to restore the previously saved copy of the site. The clean up has two aspects. One is clean out the Dreamweaver site folder of any files that you don't want to be uploaded. Second as a part of the upload or after you do the initial check delete any files on the server that don't need to be there. This will create less confusion for the next web guy. </p> <p><em>Check your work.</em> Clear your cache then view the site and try the links on multiple pages. Closely watch all graphics including the mouseover graphics. Ask someone else to check. This may be where you show off your work depending on your confidence level. </p> <p>Once the site is functional you can use Dreamweaver to move the files where you want them. Dreamweaver can update all of the document relative links. So if I want a separate folder for all files related to donors I could create a Donors folder and move them there. Dreamweaver will then update the links. </p> <p>In the future if you want to create a new page create it based on the template then change the template to link to it and allow Dreamweaver to update all of the other pages. Do a synchronized upload and check it in a browser. Simple.</p></div></div><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/organized_web_design">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>

This week I started updating a website for a local non-profit organization. The most important part of the project was studying the site and understanding how it is built. As I studied this site I learned a little about why it can be difficult for an amateur to maintain their own websites or for an outsider to come in and work on an existing site. First is the organization or lack of organization and second is the massive amount of code and files and in particular unnecessary code and files. Keeping a website's style cohesive makes it more attractive but it should also be easier to maintain.

In this site some of the links on the main page had been changed to refer to updated or moved files but the same links on inside pages were not updated and gave you the 404. The main problem in this case was when the page file was put in a folder the document relative links didn't work. The Javascript menu references were also an issue on those moved pages for the same reason.

Another problem I found was that some of the files were present in both the root folder and a folder for that section. Many of these files were identical. Which file you linked to depended on what page you were on. They would seem to work but instead of linking to the file you intended it brought up one of the duplicates from which other links didn't work. This setup just creates confusion and when dealing with someone else's system you need some clarity. I'm actually one that prefers sections and a logical hierarchy but it order to simplify the mess I worked with the files in the root directory with a plan to create sections when I had everything defined.

The graphics were created by a Fireworks function with an image for each section of the menu. I've used these before in Imageready and they can be nifty if you don't take all of the shortcuts. However there were multiple versions of the full image. They were also named with numbers based on which section it was.

The plan With Dreamweaver in hand my first priority is to repair and organize the site files. Once that is done I can do some creative work.

Tread softly. Because this was an active site I started the redesign by creating all new files. The names were not an issue since all of the old files used the htm extension instead of html. Everything would work for the old site until I renamed the home page. Of course I also made a backup copy of the old site.

If you want to simplify the current site you can do that by downloading the site and moving things around. Dreamweaver will help you keep most document or root relative links working. That's not part of my plan. I have the time to do a complete rewrite and that would just take more time. New wine new wineskin.

Establish order. Following the adage a place for everything and everything in its place I defined the structure I was going to use. Very simply all images go in the images folder and all html files go in the root folder for now that is. For a simple site like this the css file could stay in the root folder but since it was already in a separate css folder I defined it that way. Should the site grow and require more css styles they have a neat place to go. Files that are downloaded from the site alse need a separate folder so I used Documents although there are other commonly used names.

Create templates. Second thing I did was create a Dreamweaver template. With Dreamweaver templates can be used to define the appearance of a page. When a page is created from the template it can be set up to be automatically updated when the template changes. This will solve the problem of keeping the menu links up to date.

Simplify and name the images. Use a simpler set of graphics. Instead of using the numbered image files I copied then to names that reflect what the graphic was. If it was the word "About" that was used to go to a page about the organization I named it about.jpg about.gif or about.png.

Name the css properties. If you mark some text and start formatting it Dreamweaver names those styles numerically as style1 style2 etc. For a simple page this can work but for a larger more complex site these styles make for a massive amount of code you would have to sort through to understand the pages. For those who don't reference css styles explicitly the problem is not visible. For the designer that is creating a standard style for the pages css styles are very useful. Having a folder full of the automatically generated css styles can be confusing. You might unknowingly update a style at one location that affects another location. Name those styles and you will know what it is used for when you want to format another section the same way. This also helps maintaining cohesion on a site.

Creating pages. All of the above is done only on the template. There is only one thing that's left to do on the template create the links. I don't do that yet because I haven't created the files that I will be linking to. At this stage I will create the pages based on the template and add the content for each page. I can simply copy and paste from the old page or any new content that has been added checking all of the style references.

Create the links. Now back to the template. Reset all links and references to use document relative links. There are advantages and disadvantages to this but using Dreamweaver the disadvantages will be taken care of. Don't forget to check the javascript menus. When you save the template Dreamweaver should ask if you want to update the pages. Just say Yes.

Clean up and upload. This is something that should be done in a full session. It sounds simple and usually is but if something goes wrong or there are other issues to deal with you need to have time to restore the previously saved copy of the site. The clean up has two aspects. One is clean out the Dreamweaver site folder of any files that you don't want to be uploaded. Second as a part of the upload or after you do the initial check delete any files on the server that don't need to be there. This will create less confusion for the next web guy.

Check your work. Clear your cache then view the site and try the links on multiple pages. Closely watch all graphics including the mouseover graphics. Ask someone else to check. This may be where you show off your work depending on your confidence level.

Once the site is functional you can use Dreamweaver to move the files where you want them. Dreamweaver can update all of the document relative links. So if I want a separate folder for all files related to donors I could create a Donors folder and move them there. Dreamweaver will then update the links.

In the future if you want to create a new page create it based on the template then change the template to link to it and allow Dreamweaver to update all of the other pages. Do a synchronized upload and check it in a browser. Simple.

]]>
https://tylerhosting.com/b2e/dbell.php/organized_web_design#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=196
Quality Graphics https://tylerhosting.com/b2e/dbell.php/quality_graphics Mon, 19 Feb 2007 00:53:14 +0000 Dana Bell Design 144@https://tylerhosting.com/b2e/
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<div class="content_full"> <div class="bText"> <p>When speaking with non-designers about graphics it is often easy to forget how little they know about graphics. The most that most people know about graphics is the resolution. High resolution is good; low resolution is bad. </p> <p>Unfortunately it is not that simple. Without taking the time to include illustrations some of this may not be so obvious but it's something I'd like to try to start explaining. Consider this a first draft. </p> <p><strong>dpi and Resolution</strong> When a graphic artist thinks about resolution he is very often thinking about the dpi of a bitmap image. And while the higher the dpi the better measuring in dpi alone can be misleading. A 600 pixel x 800 pixel screen image at 72 dpi and a 600 pixel x 800 pixel screen image at 300 dpi is the same image. On computer the issue is not the dpi. 600 x 800 is 600 x 800. The total pixel size of an image is the determining factor. The computer screen only displays in one resolution. </p> <p>The difference is in reproduction. The dpi (dots per inch) translates to image size and resolution when printed on a inkjet or laser printer. If you print this image at 72 dpi it will be larger but lower resolution. If you print the image at 300 dpi it will be smaller but higher resolution. </p> <p>I'm talking pure dots here. You could enlarge a 300 x 400 image to 600 x 800 but in effect the quality of the image is still 300 x 400 since all those extra dots are created out of thin air and don't actually create any new details in the image. That's why it is important to keep the original image in its created size until you know how you are going to use it. Anytime you reduce an image you are throwing away dots dots that you can't get back by re-enlarging. </p> <p> <strong>lpi and Printing</strong> In addition to the dpi reproduction of an image there is lpi. That is the printing reproduction resolution. When a graphic is printed the print process does it's own conversion to a dot pattern where lpi stands for the numbers of lines of dots per inch. The printing lpi ranges from about 120 - 200 or more for commercial offset. In order to have the best quality conversion to printing lpi the finished graphic should be at least 1.5 times the print resolution. Thus a 300 dpi image would be used for 200 lpi printing. </p> <p> <strong>Bitmap or Vector</strong> All of the concern about bitmap images is due to the fact that bitmap images are simply color dots (squares actually) placed proportionally on a grid to represent the photo. Since there is so such thing as a half-dot the image will appear jagged where dots attempt to align on an edge. If everything you do is for the web that may be all you need to be concerned with since computer monitors are dot-based devices. If you're printing however you'll want to use vector graphics for anything but photos if possible. In short vector graphics are digitally drawn objects normally printed on a postscript device. </p> <p>Various programs create vector bitmap or combined images. Selecting the correct program or file format is critical to getting the quality image that you want. </p> <p><em>Fonts</em> By default modern font files are all vector based so in order to maintain vector quality they must be in their native format. Type formatted in a page layout program preserves the vector characteristics of the font. Similarly type created in most drawing programs will usually be vector. Cases where this type can be converted to bitmap is in graphics programs such as Photoshop. Note however if you attempt to use a custom color the image must be broken down into component colors of CMYK and represented by dots. </p> <p><em>Drawings</em> Drawings made is programs such as Illustrator are also vector based. That is not to say you cannot create bitmap characteristics in an illustrator. Some of Illustrator's effects are bitmap. </p> <p><em>Photos</em> Realistic photos are primarily bitmap images and there is very little you can do to make them into vector artwork. Things like clipping paths can be preserved in photos but they are separate items that can be created or imported from other vector programs. </p> <p><em>Effects</em> Shading and gradients are two things that are often combined with other images to enhance them. While they are bitmap effects you may have to take special steps to make sure that the vector images that they are a part of are not also rasterized or converted to bitmap images. </p> <p><em>Flattening</em> Most graphics programs now use layers for the different elements in an image or graphic. When you use the program to flatten the image in most cases the flattened file is a bitmap version of all layers combined even though some of them may be vector objects. Backup and think twice before flattening. Once the file is written to disk and the program is closed you may not be able to get the vector objects back. </p> <p><strong>File formats</strong> Often people may be misled by demanding their artwork be in various formats. Used to be that EPS files were the thing to ask for since they are vector images. The problem is again not that simple. EPS can contain both vector and bitmap images. Nowadays the same presumption is being made about PDF files. PDF files however can also contain both vector and bitmap images. The same is true of AI. Since many items contains both vector (type and drawings) and bitmap (photos) these formats are often the most logical choices. It all depends on how you create the files and the options you use when saving or exporting. Of course with the combination of various files and formats transparency is another issue but that is another dragon to slay. P.S. Present day JPEG images never contain vector artwork. It is a bitmap format designed specifically for photographers and photographs. </p> <p>Creating quality infinitely reproducible art is a process with a lot of elements to consider. The above contains just some of the things you need to be concerned with for the highest quality graphics. If it were that easy anyone could do it. Once you know how it all works you'll be on the way to a less worry-free life as a graphic designer. </p> <p><strong>Tip Summary</strong> <ul> <li>Use high resolution original images (larger image sizes) </li> <li>In press reproduction the image dpi should be at least 1.5 times the lpi being used in printing. </li> <li>Use Vector artwork for drawings and text </li> <li>Maintain vector artwork when adding bitmap effects and creating files for output.</li> </ul></p></div></div><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/quality_graphics">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>

When speaking with non-designers about graphics it is often easy to forget how little they know about graphics. The most that most people know about graphics is the resolution. High resolution is good; low resolution is bad.

Unfortunately it is not that simple. Without taking the time to include illustrations some of this may not be so obvious but it's something I'd like to try to start explaining. Consider this a first draft.

dpi and Resolution When a graphic artist thinks about resolution he is very often thinking about the dpi of a bitmap image. And while the higher the dpi the better measuring in dpi alone can be misleading. A 600 pixel x 800 pixel screen image at 72 dpi and a 600 pixel x 800 pixel screen image at 300 dpi is the same image. On computer the issue is not the dpi. 600 x 800 is 600 x 800. The total pixel size of an image is the determining factor. The computer screen only displays in one resolution.

The difference is in reproduction. The dpi (dots per inch) translates to image size and resolution when printed on a inkjet or laser printer. If you print this image at 72 dpi it will be larger but lower resolution. If you print the image at 300 dpi it will be smaller but higher resolution.

I'm talking pure dots here. You could enlarge a 300 x 400 image to 600 x 800 but in effect the quality of the image is still 300 x 400 since all those extra dots are created out of thin air and don't actually create any new details in the image. That's why it is important to keep the original image in its created size until you know how you are going to use it. Anytime you reduce an image you are throwing away dots dots that you can't get back by re-enlarging.

lpi and Printing In addition to the dpi reproduction of an image there is lpi. That is the printing reproduction resolution. When a graphic is printed the print process does it's own conversion to a dot pattern where lpi stands for the numbers of lines of dots per inch. The printing lpi ranges from about 120 - 200 or more for commercial offset. In order to have the best quality conversion to printing lpi the finished graphic should be at least 1.5 times the print resolution. Thus a 300 dpi image would be used for 200 lpi printing.

Bitmap or Vector All of the concern about bitmap images is due to the fact that bitmap images are simply color dots (squares actually) placed proportionally on a grid to represent the photo. Since there is so such thing as a half-dot the image will appear jagged where dots attempt to align on an edge. If everything you do is for the web that may be all you need to be concerned with since computer monitors are dot-based devices. If you're printing however you'll want to use vector graphics for anything but photos if possible. In short vector graphics are digitally drawn objects normally printed on a postscript device.

Various programs create vector bitmap or combined images. Selecting the correct program or file format is critical to getting the quality image that you want.

Fonts By default modern font files are all vector based so in order to maintain vector quality they must be in their native format. Type formatted in a page layout program preserves the vector characteristics of the font. Similarly type created in most drawing programs will usually be vector. Cases where this type can be converted to bitmap is in graphics programs such as Photoshop. Note however if you attempt to use a custom color the image must be broken down into component colors of CMYK and represented by dots.

Drawings Drawings made is programs such as Illustrator are also vector based. That is not to say you cannot create bitmap characteristics in an illustrator. Some of Illustrator's effects are bitmap.

Photos Realistic photos are primarily bitmap images and there is very little you can do to make them into vector artwork. Things like clipping paths can be preserved in photos but they are separate items that can be created or imported from other vector programs.

Effects Shading and gradients are two things that are often combined with other images to enhance them. While they are bitmap effects you may have to take special steps to make sure that the vector images that they are a part of are not also rasterized or converted to bitmap images.

Flattening Most graphics programs now use layers for the different elements in an image or graphic. When you use the program to flatten the image in most cases the flattened file is a bitmap version of all layers combined even though some of them may be vector objects. Backup and think twice before flattening. Once the file is written to disk and the program is closed you may not be able to get the vector objects back.

File formats Often people may be misled by demanding their artwork be in various formats. Used to be that EPS files were the thing to ask for since they are vector images. The problem is again not that simple. EPS can contain both vector and bitmap images. Nowadays the same presumption is being made about PDF files. PDF files however can also contain both vector and bitmap images. The same is true of AI. Since many items contains both vector (type and drawings) and bitmap (photos) these formats are often the most logical choices. It all depends on how you create the files and the options you use when saving or exporting. Of course with the combination of various files and formats transparency is another issue but that is another dragon to slay. P.S. Present day JPEG images never contain vector artwork. It is a bitmap format designed specifically for photographers and photographs.

Creating quality infinitely reproducible art is a process with a lot of elements to consider. The above contains just some of the things you need to be concerned with for the highest quality graphics. If it were that easy anyone could do it. Once you know how it all works you'll be on the way to a less worry-free life as a graphic designer.

Tip Summary

  • Use high resolution original images (larger image sizes)
  • In press reproduction the image dpi should be at least 1.5 times the lpi being used in printing.
  • Use Vector artwork for drawings and text
  • Maintain vector artwork when adding bitmap effects and creating files for output.

]]>
https://tylerhosting.com/b2e/dbell.php/quality_graphics#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=144
UTHCT https://tylerhosting.com/b2e/dbell.php/uthct Sun, 11 Feb 2007 00:03:23 +0000 Dana Bell Design 125@https://tylerhosting.com/b2e/
Deprecated: Creation of dynamic property Item::$cache_has_content_parts is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 4911

Deprecated: Creation of dynamic property Item::$renderers_validated is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 11107

Deprecated: Creation of dynamic property Item::$pages is deprecated in /home4/tylering/public_html/b2e/inc/items/model/_item.class.php on line 2412

Deprecated: Creation of dynamic property ItemSettings::$count_col_key_names is deprecated in /home4/tylering/public_html/b2e/inc/settings/model/_abstractsettings.class.php on line 121
<div class="content_full"> <div class="bText"> <p><strong>Another web review </strong> Having reviewed the TylerPaper web site yesterday I reminded myself that I hadn't reviewed UTHCT since it's relaunch. One of the most impressive local web sites here in Tyler is now that of <a href="http://www.uthct.edu/">The University of Texas Health Center at Tyler</a>. It was redesigned last year and launched in December I believe. </p> <p>I'm employed there in a different department and never did like the "swoops" they adopted. Technically they are difficult to manage in print media and personally can look amateurish if not done right. What it does in a website however is give the site some shape and character. Those curved lines and the image outlines are what give the website its character. Combine those with those boxy buttons and it doesn't look so bad or so unnatural. </p> <p>The overall design is well thought out and quite functional. The links at the top and to the right are logical and the highlight links do just that highlight the news items and items of interest. The rotating image links at the right are small enough to not be disturbing and yet noticeable enough to make you interested. </p> <p>Some of the inside pages of the site are also impressive most with a custom headline graphic. On some other pages you can tell they are database driven pages. Departmental pages use a unifying page structure which is a good thing. On the other hand the directories are simply lists of names numbers although databases can do more that just list things. </p> <p>That it's a database driven site is a good thing. That means it can be kept up to date by those in the know. The content management system is simple and effective but I'm more impressed by the design and integration of the graphics. </p> <p>...<!--The one thing on the site that I particularly dislike is the Careers at UTHCT link. It brings up a generic site and a note that it is in the process of change. Navigating the job search list is an annoyance. I should say job search items since you can only look at one at a time. That you must apply on line screams that we don't really have an interest in you. On line applications really are useful but demanding that all applications be online demonstrates dictatorial bossiness of an organization. But then that's not a part of the site design.--> </p> <p>Overall the site design and content is exceptional. Technically it's a model site as well. If you'll look at the bottom of a page you will notice a XHTML 1.1 icon. Click it and it will validate the page on the World Wide Web Consortium site. Today there were two errors but I'll bet they will be fixed before you try it.</p></div></div><div class="item_footer"><p><small><a href="https://tylerhosting.com/b2e/dbell.php/uthct">Original post</a> blogged on <a href="http://www.tylerhosting.com/b2e/">Switched Keys</a>.</small></p></div>

Another web review Having reviewed the TylerPaper web site yesterday I reminded myself that I hadn't reviewed UTHCT since it's relaunch. One of the most impressive local web sites here in Tyler is now that of The University of Texas Health Center at Tyler. It was redesigned last year and launched in December I believe.

I'm employed there in a different department and never did like the "swoops" they adopted. Technically they are difficult to manage in print media and personally can look amateurish if not done right. What it does in a website however is give the site some shape and character. Those curved lines and the image outlines are what give the website its character. Combine those with those boxy buttons and it doesn't look so bad or so unnatural.

The overall design is well thought out and quite functional. The links at the top and to the right are logical and the highlight links do just that highlight the news items and items of interest. The rotating image links at the right are small enough to not be disturbing and yet noticeable enough to make you interested.

Some of the inside pages of the site are also impressive most with a custom headline graphic. On some other pages you can tell they are database driven pages. Departmental pages use a unifying page structure which is a good thing. On the other hand the directories are simply lists of names numbers although databases can do more that just list things.

That it's a database driven site is a good thing. That means it can be kept up to date by those in the know. The content management system is simple and effective but I'm more impressed by the design and integration of the graphics.

...

Overall the site design and content is exceptional. Technically it's a model site as well. If you'll look at the bottom of a page you will notice a XHTML 1.1 icon. Click it and it will validate the page on the World Wide Web Consortium site. Today there were two errors but I'll bet they will be fixed before you try it.

]]>
https://tylerhosting.com/b2e/dbell.php/uthct#comments https://tylerhosting.com/b2e/dbell.php?tempskin=_rss2&disp=comments&p=125

Deprecated: substr(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 932

Deprecated: substr(): Passing null to parameter #1 ($string) of type string is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 933

Deprecated: Creation of dynamic property Hit::$is_lynx is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 571

Deprecated: Creation of dynamic property Hit::$is_firefox is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 572

Deprecated: Creation of dynamic property Hit::$is_gecko is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 573

Deprecated: Creation of dynamic property Hit::$is_IE is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 574

Deprecated: Creation of dynamic property Hit::$is_winIE is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 575

Deprecated: Creation of dynamic property Hit::$is_macIE is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 576

Deprecated: Creation of dynamic property Hit::$is_chrome is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 577

Deprecated: Creation of dynamic property Hit::$is_safari is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 578

Deprecated: Creation of dynamic property Hit::$is_opera is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 579

Deprecated: Creation of dynamic property Hit::$is_NS4 is deprecated in /home4/tylering/public_html/b2e/inc/sessions/model/_hit.class.php on line 580