
The previous post in this series introduced the D.Buzz Character Count Post Form. It explained how the spreadsheet-based form works from the point of view of someone using the form. So this 3-part post is about the spreadsheet behind the D.Buzz Character Count Post Form for Buzzes (and Tweets).

Cover Image made using HTML and CSS. Light edits made using MS Paint. Additional images made using Excel 2003, with edits made using MS Paint.

Post Navigation
Post Part | Topics Covered |
---|---|
Part 1 | Behind the Scenes; Elements; Simple data values; Cosmetic features; Merged cells for data entry; Named ranges |
Part 2 | Functions and Formulas |
Part 3 | Conditional Formatting; Potential Improvements; Just My Two Sats |

Click the image for a full-size view
Behind the Scenes for the D.Buzz Character Count Post Form
Even though the D.Buzz Character Count Post Form looks simple, it's surprising how much work went into it. Not so much work in terms of time, but rather work in terms of what was used to get the form to work as intended:
- User interface elements (both cosmetic and functional);
- Cells containing adjustable limits for Title and Body;
- Merged cells to accomodate data entry;
- Cells to count how many characters are in title and body fields;
- Dynamic status lines showing remaining/extra characters
- Visual changes in dynamic status lines depending on character counts.
For what I wanted to accomplish for my needs, this form does the job.
Spreadsheet Elements Used
These are the spreadsheet elements I used to make the D.Buzz Character Count Post Form and how this post will cover them:
Post Part | Topics Covered |
---|---|
Part 1 | ● Simple data values ● Cosmetic features ● Merged cells for data entry ● Named ranges |
Part 2 | ● Functions ● Formulas |
Part 3 | ● Conditional Formatting |
Here are the Part 1 elements in more detail:
Simple Data Values
These take the form of text for headings and form labels as well as adjustable MAX settings which can be adjusted as needed. D.Buzz uses buzz titles of 60 characters or less, and the body of the buzz is set for 280 characters.
If the headings, form labels, or even MAX settings need to be changed for some other task-- for example, copywriting for e-mail marketing or other social media-- they can be modified as needed. The spreadsheet doesn't care as long as it functions properly.
Cosmetic Features
Black text on white background is used for the headings and form labels and the default state of the dynamic status lines.
The data entry fields needed to pop, and I wanted them to reflect the basic color scheme of D.Buzz. For those reasons, I chose solid red borders for light yellow data entry fields.
The dynamic status lines beneath the data entry fields also reflect the D.Buzz color scheme. They will be covered in greater detail in the Conditional Formatting section.
Meged Cells for Data Entry
This is a functional feature since space is needed to type content. The title field is 2 rows by 7 columns for an area of 14 merged cells. The body field is 10x7 for an area of 70 merged cells.
The top left cell of an area of merged cells is considered the cell address of the merged cells. This means that cell $A$4
is the address of the title field and cell $A$9
is the address of the body field.
Alignment for these data entry fields was set for horizonal left and vertical center. These alignment settings should be OK, but they can be changed from spreadsheet program menus as desired.
Named Ranges

Click the image for a full-size view
Named Ranges are used to identify key cells or regions. They are also used as building blocks for other names to be defined as fomulas.
Named ranges containing just 1 cell were made for the MAX settings (nMaxTitle
and nMaxBody
) as well as for the character counts (nTitle
and nBody
).
Named ranges were made for the data entry areas (formTitle
and formBody
):
formTitle
is a range of 14 merged cells laid out in a grid of 2 rows by 7 columns. The top left cell in this range is $A$4, so that is how formulas and functions identify this range.formBody
is a range of 70 merged cells laid out on a 10x7 grid. The top left cell in this range is $A$9, so that is how formulas and functions identify this range.
Names (not really named ranges) were made for calculating the difference between the MAX settings and the character counts (fxRemainingTitle
and fxRemainingBody
). These are needed to build the dynamic status lines which change when certain counts are reached.
Just My Two Sats
This post was so long it needed to be split into 3 parts. Some elements explained themselves, but others required more explanation and context.
Simple data values for headings and MAX settings don't need much explanation. Headings are descriptive, so no calculation or processing is needed by them or for them. MAX settings are the limits used by the spreadsheet for counting characters and providing a status; when D.Buzz changes character limits again (or if the form is adapted for other situations), the values for the MAX settings can change.
Cosmetic features are mainly for looks, although they offer minimal functionality from a form usage perspective. Choice made for looks are based partly on D.Buzz and partly on personal preference. These can be changes at the program level.
Merged cells are used for data entry. Counts are delayed until the data entry is finished. A later version of the form can use genuine form controls which allow counts in real-time, as typing takes place.
Named Ranges require the most explanation here. Usually they are aliases for cell addresses or a range of cell addresses. If the Define Name dialog box is used to create named ranges, then it's possible to create "named" unattached to a range; these names can be used like aliases for fixed values like numbers or text strings, or they can be aliases for functions or formulas.
Speaking of functions and formulas, they will be covered in Part 2.

● If you liked this post, please give it an upvote. ● If you liked this post but it's past the 7-day payout window, please tip using PIZZA, BEER, or the engagement token of your choice (or just send something from your account to mine). ● Please reblog or re-Hive this post if you found it useful. ● If there are corrections or clarifications I need to make concerning post content, let me know in a comment so I can update the post and give you credit for the correction. ● As I am neither a certified professional accountant nor a licensed broker, posts concerning cryptocurrency, commodities, securities, and money are presented for informational purposes only; DYOR. |
---|
● If you're new to cryptocurrency and want to know what people think, feel free to drop by the Daily Crypto Markets Live Blog at LeoFinance. It's a free-wheeling text conversation comment thread that takes place in (more or less) real-time. ● Although I've learned a lot about Hive and its ecosystem of dApps, there's much more I don't know. Where can Hivers new and old learn more? Visit TheTerminal for FAQs, tips, references, and terrific how-to content. ● Did you know that there are 156 dApps built by Hive community members, and more to come? Discover them at Hive Projects. ● If your voting power is beneath dusting threshold, follow and use @dustsweeper and @dustbunny to boost your voting power. Authors you upvote will be glad you did, and you'll be happy to start claiming curation rewards. |
Sometimes I discover posts way after the initial earnings period. It's too late for me to upvote posts then, so to make up for the lost upvote I send a slice of PIZZA instead. My main focus is cryptocurrencies from a number of angles (educational, commentary, observations, even pop culture). A secondary focus is sharing my discoveries about the world of Hive Social. Most of my posts can be found at these two locations: ● LeoFinance : @magnacarta ● Proof of Brain : @magnacarta Follow me at this D.Buzz-only account : ● D.Buzz : https://blog.d.buzz/#/@magnacarta.buzz-- note the ".buzz" at the end! If you follow me at @magnacarta.buzz, please follow me at this account as well I expect 2022 to be the year I go from being crazy or weird to being eccentric. If that doesn't happen, then Festivus will last longer than I can stand. |