Calc 2 Chapter 6

[Granville Turley]

Ourin-class unit tests will largely resemble the format of the externally-moderatedAP Calculus examination (given in May) inasmuch as roughly half of the test willbe multiple-choice format, with the remaining half being of free-response format. A final comment is in order. Namely,there are a few points in the syllabus notes where I have ventured off on a some probability and statistics-related tangents. These notes should be of particular interest to students already havingexposure to these topics (say, in our AP Statistics course). By bringing of this into the foreground, I hope to give such students a better understanding ofboth statistics as well as providing some meaningful applications of calculus. However,these topics are not essential for the understanding of this course. Best wishes for a successful school year—Mr. "S."

This chapter gives an overview of the main services and interfaces used in the Calc parts of the Office API, illustrated with small code fragments. I'll revisit these topics in greater details (and with larger examples) in subsequent chapters.

If you're unfamiliar with Calc, then a good starting point is its user guide, available from -help/documentation. Chapter 8 of the Developer's Guide looks at spreadsheet programming, and is available from _OOo3.1.0.pdf. Alternatively, you can access the chapter online, starting at _Documents (or use loguide calc). The guide's examples can be found at There's also a few examples in the "Spreadsheet Document Examples" section of _examples.

Surprisingly, XSpreadsheetDocument doesn't subclass XComponent. This means that it's not possible to pass an XSpreadsheetDocument reference to a method expecting an XComponent argument, such as the original GUI.setVisible(), which had the signature:

I decided to hide this casting issue by weakening the typing of methods using XComponent parameters. For example, the current version of GUI.setVisible() assumes that its first argument is of type Object:

The data in a spreadsheet can be accessed in many ways: for example, as individual cells, cell ranges, collections of cell ranges, rows, and columns. These ways of viewing data are supported by different services which are used as labels in Figure 3.

For instance, the cell named "C5" in Figure 4 is at coordinate (2,4). Note that row names start at '1' but row positions begin at 0. A cell range is defined by the position of the top-left and bottom-right cells in the range's rectangle, and can use the same dual naming scheme. For example, the cell range B2:D3 is the rectangle between the cells (1,1) and (3,2).

A spreadsheet document may contain multiple sheets, so a cell address can include a sheet name. The first sheet is called "Sheet1", the second "Sheet2", and so on. For example, "Sheet1.A3:Sheet3.D4" refers to a cube of 24 cells consisting of 3 sheets of 8 cells between A3 and D4. Sheets can be assigned more informative names, if you wish.

A great deal of spreadsheet-related functionality is implemented as interfaces belonging to the Spreadsheet service. The most important is probably XSpreadsheet (see lodoc xspreadsheet reference ), which gives the programmer access to a sheet's cells and cell ranges via getCellByPosition(), getCellRangeByPosition(), and getCellRangeByName(). For example:

SheetCellRange supports an XSheetCellRange interface, but that interface gets most of its functionality by inheriting XCellRange from the table module. Most programs that manipulate cell ranges tend to use XCellRange rather than XSheetCellRange.

What's missing from XCellRange is a way to set the values in a cell range. This is supported by the XCellRangeData interface (see Figure 6) which offers a setDataArray() method (and a getDataArray()).

CellProperties in the table module is frequently accessed to adjust cell styling, such as color, borders, and the justification and orientation of data inside a cell. However, styling for a cell's text is handled by properties in the CharacterProperties or ParagraphProperties classes (see Figure 6).

Rows and columns of cells can be accessed using the TableRows and TableColumns services (and their corresponding XTableRows and XTableColumns interfaces). They're accessed through the XColumnRowRange interface shown in Figure 6. Code for obtaining the first row of a sheet is:

XCellRange.getCellByPosition() returns a single cell from a given cell range. However, this method can also be applied to a sheet because the API considers a sheet to be a very big cell range. For example:

The SheetCell service manages properties related to cell formulae and cell input validation. However, most cell functionality comes from inheriting the Cell service in the table module, and its XCell interface. This arrangement is shown in Figure 10.

SheetCell doesn't support an XSheetCell interface; instead most programming is done using XCell. XCell contains useful methods for getting and setting the values in a cell (which may be numbers, text, or formulae). For example, the following stores the number 9 in the cell at coordinate (2, 4) (the "C5" cell):

SheetCell inherits the same properties as SheetCellRange. For example, CellProperties stores cell formatting properties, while text styling properties are supported by CharacterProperties and ParagraphProperties (see Figure 10).

The Cell service supports both the XCell and XText interfaces. Via the XText interface, it's possible to manipulate cell text in the same way that text is handled in a text document. However, for most purposes, it's enough to use XCell's setFormula() which, despite its name, can be used to assign plain text to a cell. For instance:

Under 28 U.S.C. 1930(a)(6), a quarterly fee shall be paid to the United States Trustee System Fund at Treasury in each case under chapter 11 (except small business cases under Subchapter V of chapter 11) for each calendar quarter, or portion thereof, between the date a bankruptcy petition is filed and the date the court enters a final decree closing the case, dismisses the case, or converts the case to another chapter in bankruptcy.

The addresses shown above are a lockbox at a bank. Do not use these addresses for service of process, correspondence, or any purpose other than paying quarterly fees. Any other correspondence or documents sent to the lockbox other than the payment form will be destroyed.

Cisowski Law Chapter 13 Calculator is an algorithm that uses 4 pages of information from the user and combines them with a number of assumptions, legal rules, and standard variables to reach a precise approximation of what your Chapter 13 repayment plan monthly payments would end up being.

I initially wanted to add a fun and simple chapter 13 calculator for my prospective clients in Eastern Tennessee; however, I noticed more and more people using it from areas far and beyond rural Tennessee. Once I started to get traffic hitting this page and calculator, I worried people were using it and getting poor information since it was calibrated for Tennessee filers.

I spent some time redesigning the calculator with a new goal in mind: being easy and accessible to filers all around the county, as well as being a fairly accurate tool to help prospective filers decide whether or not to file Chapter 13 bankruptcy. I am happy how the calculator turned out. It includes detailed calculations for anyone in the United States and US Territories.

Producing a quick and easy chapter 13 repayment calculator requires the use of a few assumptions. Although these assumptions hold in the majority of cases, they do not always apply. This is why it is important to seek independent counsel.

This calculator is constantly changing with the law and with the support of its users.

Cisowski Law would appreciate feedback to improve its use.

If you would like to embed this calculator on your website, please contact oli...@cisowskilaw.com.

Demonstrated by James Please, the designer and developer of the FI Calc Retirement planning calculator.

Hosted by the Chicago virtual Bogleheads chapter. Recorded on May 5, 2021.

Chapter meetings are listed in the Bogleheads blog calendar. You can add this calendar to your Google account. Notifications are also sent from an email subscription list. See the blog for more information.

James Please: Perfect. Yeah, so thanks for taking the time again on such short notice to join this chat with me and hear a little bit about FiCalc. I guess a little bit of history on the app is that I've been a big fan of FIRECalc and cFIREsim and other retirement calculators for some time and I had three goals going into building this app.

One was I wanted it to work on a mobile phone because I use my mobile phone a lot and just in my experience in the industry. I know more and more people are using their mobile phones so that was one goal that I wanted. And then another goal that I wanted was--you know when I first went to those calculators I was a little bit overwhelmed because they seemed so complex--so it was really important to me that I create a lot of guides that document how the calculator works. And really that the goal of the guides is if anyone has any questions about it they should be able to find it here.

I'm not sure how successful I was. Maybe you guys can let me know. But yeah, so that was the goal behind the guides. And then the third thing that I wanted was for there to be at least the same amount of features as FIRECalc and cFIREsim, and ideally a little bit more. Just so that there's also some added functionality to the calculator as well.

I don't think FIRECalc has been updated in some time. But I know cFIREsim just had a rewrite. I'm not too sure, I haven't had a chance to look at it too closely, so I'm not too sure, there may be things that are in cFIREsim that aren't in FiCalc, and vice versa. I'm not too sure but what I can do is I can speak to what is in FiCalc.

So that's a little bit of a tangent there. But I'll move on, and we can talk about the portfolio. So in FiCalc you can put your initial portfolio value in a dollar amount and then what you get to do is specify the allocation that you want. So for instance, 80% equities/ 15% bonds/ and 5% cash. That's the default, and then also the default is that it rebalances annually.

3a8082e126