You send off a load command and then the handler continues, windows can still be moved and resized so it doesn't feel as if your app has frozen. Callbacks are used to track the progress of the download and to detect the end of the download. Compile the script, close the editor and change to the browse tool. Then click the button to test it. Watch the Message box as the file downloads and you will see various messages appear. Now you have seen what messages the libURLSetStatusCallback produces, so let's go on to do something more interesting with this data,.
These are what is sent to the status callback handler as it's second parameter. The first parameter is the URL of the file being downloaded. The "cached" status message is actually sent to the "downloadComplete" handler, which we haven't written yet. The messages of interest when scripting a progress indicator are the "loading" messages which come as a line with three items.
These two numeric items give us the data we need to set up a progress bar and script the changing display. Drag a progress bar into the window from the Tools palette. Make it wider if you like, although it doesn't matter.
Firstly, it checks the number of items in the status report. The progress bar is only interested in those with three items, showing the numeric progress of the download. If there are three items, it checks to see if the progress bar is visible. If it is not visible, then the download has only just started and the progress bar needs to be set up to match the length of the incoming file.
The properties of a scrollbar that specify the range are startValue and endValue. So we set the startValue to 0 and the endValue to the total number of bytes in the file being downloaded. Really we don't need to set the startValue every time, but I like to do it anyway, just in case I have another function that uses the same progress indicator. Once the progress bar has been initialized, it can be shown. This tells the script that the endValue has been set, so it doesn't have to be set every time the status callback handler runs.
The property of a scrollbar that shows progress is called the thumbPosition, or thumbPos for short. This gets set to the second item of the status report, so it shows the progress as the file comes in. Apply this script, switch to run mode and click the Download button to test it.
You should see the progress bar appear, the progress indicator move along it and stop at the end. Note: if you click the button again, you will not see any progress indication. This is because the downloaded file is still cached in memory and so LiveCode knows that there is no need to download it again. If you look back to the last line of the mouseUp handler, where the download is actually started, you will see that it has a callback message.
When the download has finished, we need to do something useful with the downloaded file which is only in stored in memory at that point. This handler will be called when the download is complete, either due to an error or after a complete download.
First thing is to hide the progress bar, since there will be no more progress after this. If the download is OK, then we will save the downloaded file to the desktop. Work out a file path for this, using the last portion of the download address remember this is sent to the handler as the first parameter and the specialFolderPath function.
Once a file has been downloaded and is cached in memory, it can be accessed any time using the URL keyword. So to save the file, just "put" the URL into the file path. Don't forget to use binfile: not file: since this is not just a text file. We should really check to see that the save worked, but for now, we are just going to open the downloaded PDF in the default PDF application.
The final step is to unload the downloaded file from memory. This saves memory, so it is a good idea after a download, once the downloaded file has been saved. For this example, it is essential to allow repeated tests.
If this doesn't happen, any further download attempts will just go straight to the downloadComplete handler with a status of "cached". So we now have a nice bar that shows the progress of the download, but there are some other details that would be nice to display. The progress bar doesn't tell us anything about the size of the download, or the speed of download.
We have the number of bytes downloaded in the URL status, so if we record the starting time of the download, we can calculate the speed and display this information. To store the start time of the download, we are going to use a script local variable.
This is a variable that is declared as a local variable outside any handler. The top of the script is usually the best place for these. The value of this variable is available to any handler in the script, but not to anything outside the script.
Using this technique, we can store a starting time in the mouseUp handler and use it in the showProgress handler to see how much time has elapsed and how fast the data is coming through. The other neat thing we can do is to change the download figures from bytes to kilobytes. This makes the numbers much more readable, especially as they are changing fast. Drag a field from the Tools palette and use the Inspector to name it "ProgressField". Drag the handles to make it nearly as wide as the stack.
Edit the script of the Download button and insert the following line at the top of the script, before the mouseUp handler starts. This line must be outside all of the handlers.
Add these two lines to the mouseUp handler - I have them just after the line hiding the scrollbar, but they can be anywhere, so long as they are before the line that starts the download. The first part is exactly the same, but there is a new part added on to show the text data. It gets the two numbers bytes received and total bytes and divides them by to convert to kilobytes.
I use the "div" command as that divides and rounds, so we will get integers here instead of numbers with lots of decimals. The sDownloadStart script local variable was set to the seconds in the mouseUp handler, now we use it to work out the number of seconds that have elapsed since the download started. At the start, this may by zero seconds, so I have added a check to make sure we don't get a divide by zero error. Then the KB received divided by the elapsed seconds gives KB per second.
This time I use the round function to get a number with one decimal place. The rest of the script just displays the text in the ProgressField field. The text progress section duplicates the check for the number of items in pStatus, but I wanted to make each section independent. Now the scripts are all in place, you can arrange the interface to suit your application. Choose "Show Invisible Objects" from the View menu to see the hidden progress bar so that you can move it around and resize it.
You can also add a section to the downloadComplete handler that tidies up the text display at the end of the download. It could blank it or change it to show the result of the download and the overall download speed. If you have a fast connection, you may want to download a larger file to test these progress displays.
There is a line at the start of the mouseUp handler that sets the tDownloadLink variable. Replace it with the following line for a bigger PDF:. For details on uploading a file, check out Uploading a file using FTP. Another simple option is a Post-It grid. If you are dealing with a ridiculous amount of work to do, you can always use this system to break things into workable chunks.
All you have to do is divide your project into small tasks. Write these tasks on the Post-It notes and put them all on your wall in a grid.
As you complete each task, you can remove the Post-It note from the wall until your wall is completely blank again. Traditionally, people have used basic tactics like the ones mentioned above to track progress on different assignments or jobs. While these traditional options are still a great idea for some, there are newly created platforms to help track progress and set goals. The following progress tracking tools are a useful way to organize your own projects as well as the things your team members are working on.
With Teamweek , you can organize your to-do list and make productivity checklists with a simple drag-and-drop feature. Teamweek makes it simple to schedule your team members and delegate different tasks. When it comes to progress tracking tools, Teamweek is an excellent visual aid. Start by determining your major goals and then break these major tasks into more manageable ones.
As you go through each task, you can cross it off your virtual checklist. As your team members do the same thing for their assigned tasks, you can see the changes once they happen. When you have everything done, you can step back and admire your progress.
Toggl is a useful tool you can integrate for time tracking. More importantly, it remembers tracked time, so you never have to. Idle detection, notifications, and tracking reminders help you stay on task, no matter what you are doing.
With Toggl, you can also do useful things like monitor how much you are earning per hour. You can break down your workday according to your clients, projects, and tasks. Then, you can check out which projects and tasks are making you money. The progress tracking tool can be synchronized across multiple platforms. You can use it on your tablet, smartphone, or computer browser. No matter what device you use, Toggl immediately syncs it across your other devices, so you can instantly check to see your progress no matter where you are.
Trello is a flexible, free way to organize your to-do list. It can be integrated into more than other apps and offers a number of different ways to organize your tasks. You can use cards, boards, and to-do lists to track your ongoing projects in a simple, clear way. This platform helps you work with teams and organize your side projects.
When looking at your tasks, you can review the details, leave comments, or add attachments. If you need a way to collaborate with your team, Trello is another good option to test out. WorkOtter helps you track progress online as well with a cloud-based platform that offers customized project overviews and the ability to aggregate several different projects in the same dashboard. If you need help managing your time or scheduling team members, WorkOtter can help.
This SaaS platform offers portfolio management, scheduling, resource management, and time management tools for individuals, teams, and businesses. For smaller teams, ClickUp is a cloud-based solution that is ideal for task management and productivity. You can use your dashboard to track your progress, view tasks, and create Gantt charts. Within each task, you can create subtasks as you collaborate with your team members in real-time.
While some of the features require an upgrade to use, there are still a number of options in the free plan. This program offers time tracking, drag-and-drop task reordering, and other task management options with the basic version.
Human brains are naturally wired to track progress and achieve each goal. Your mind enjoys a sudden boost of dopamine whenever you finish another goal. By making your goals visual and easier to track, you can harness this inborn, natural tendency to accomplish even more at work.
From a simple notebook to project management platforms, there are multiple ways you can document, track, and achieve progress in your day-to-day life and career. To stay up-to-date on great insight like the details in this article, make sure you follow the Teamweek Facebook page as well as the Teamweek Twitter feed! It has been exactly four years since I joined the truly awesome team at Toggl. Coincidentally, that was also the time when Toggl switched from a traditional office to remote working.
That changed. Products News. Sign Up. Filter By: Featured. Download The App. Written by Logan Derrick.
0コメント