Sometimes when developing we want our program to process items continually. This can be a fairly simple concept: the script sits in a loop and constantly does what we need it to until there are no items to process. Then our program is finished. If we want to run more items, we need to start the script again. As you can see, this could be a tedious, laborious, and potentially inefficient system.Continue reading "LDC #69: Running in the Background" »
Friday, January 26. 2018
Monday, January 22. 2018
The SEC’s Office of Financial Management Filing Fees announced the release of the web-based Registration Fee Estimator 1.2. Included in this release are all effective fee-bearing form types.Continue reading "SEC Releases Registration Fee Estimator 1.2" »
Friday, January 19. 2018
Way back in LDC #39, we discussed the file “ApplicationInitialize.ls” and how any script functions in it are run at application startup. With GoFiler 4.21b’s release on January 16, 2018, we’ve added support for a similar file, “ApplicationShutdown.ls”. As the name suggests, this file is called when GoFiler shuts down. This is a pretty powerful feature because it lets you do things to “clean up” your environment if you’ve modified it with other scripts or if you want to return the system to a desired state after using the application.
Continue reading "LDC #68: Application Shutdown Script" »
Friday, January 12. 2018
In past blog entries I’ve written, the topic is often about simple scripts. It’s covered a couple hundred lines of code, and the script usually handles a single function. This means that every script that’s been covered so far has been relatively simplistic in structure, with no more than 10 or so separate functions. With so little code, a script can still be easily maintainable even if no thought is given to how it’s put together. The design of the application is less important in these cases. However, what if you want to do a larger project? What if your script is going to include multiple UI screens and integrate with multiple systems? This is where you would want to pay some attention to design and apply some software design practices to the script to ensure that you get the best possible result. The blog post this week will not contain an example of the script but will rather discuss how we can apply some software engineering principles to Legato design to avoid common pitfalls.
Continue reading "LDC #67: Legato Program Design Best Practices" »
Thursday, January 11. 2018
The SEC announced on December 8th, 2017 that filing Form N-PORT on the EDGAR system will now not become mandatory until April 2019 for larger fund groups and April 2020 for smaller fund groups. However, these groups should still prepare and maintain N-PORT information in their records and make it available to the SEC upon request. This decision to modify Form N-PORT’s filing requirements comes as the agency continues its previously announced review and uplift of its EDGAR and other systems.Continue reading "SEC Changes N-PORT Filing Requirements" »
Monday, January 08. 2018
To aid filers avoid missing deadlines and reduce congestion around busy important filing dates, the SEC provides an anticipated peak filing schedule. Peak EDGAR filing times are estimated using historical data. The 2018 schedule is now available from the SEC.Continue reading "SEC's Peak Filing Schedule for 2018" »
Friday, January 05. 2018
Comma delimited data is perhaps the simplest way of representing a table of information. Many applications that export data will produce a CSV file, allowing for simple and fast extraction of data. However, despite the fact that CSV is a common format, it is not standardized. Reading and writing may also seem simple, but there are sticking points, such as how to handle commas and line returns that occur in the data itself. Wouldn’t it be nice to have tools to deal with CSV data? Legato does.Continue reading "LDC #66: CSV - The Simplest Data Format" »