Shulou(Shulou.com)06/01 Report--

The design philosophy of DailyTick was described in the last article. After about two weeks of design and development, now the main UI of DailyTick has completed the prototype design and preliminary implementation. Since it is a prototype, of course it looks a little rough.

Master UI

The main UI is implemented using a TabbedView. One for recording, the other for statistics. Of course, the final finished version should have at least three Tab, because you also need to have a "set" Tab. Now, because I haven't thought of anything to set up yet, I haven't written it yet. In the "record" tab, there are two components: a ListView and a circular button written by NControl. When using it, you only need to click the circular button below to form a record. Of course, in order to prevent delays, I have set a limit here, that is, it takes more than 1 minute between clicks. This brings a problem: you can't record events that take less than a minute. For example, you want to see how long it takes to keep track of your time every day, which can't be done for the time being.

In fact, I am a little worried about the above list: if this software can be used for 10 years (it should not be possible, because at that time, there should be devices that are easier to use than mobile phones), according to what I have recorded now, there are about 30 records a day, 365 * 30 = 10950 in a year, and 100000 in 10 years. If you record it in more detail every day, there may be hundreds of thousands, will it collapse? Although you can use Cell's reuse mechanism, it's still a bit of a concern. Of course, I'm more worried about memory than the performance of ListView. Because the time on the left shows that it is not a Label. Because my UI design is so poor, I use ListView's built-in ImageCell, and the one on the left is an image. This image is drawn in memory and loaded using ImageSource.FromStream. So I don't know if it will consume too much memory. This may be a point that can be optimized.

Modifications to events / activities

After recording an activity / event, you need to record what has been done, that is, the subject of an event / activity, and you need to tag an event for later statistics. I originally thought that it would be implemented using ListView's Context Menu, but there is a problem with this thing, that is, it conflicts with the left and right sliding of TabbedView, so it can't display Context Menu in any way. I had to give up this plan and use DisplayActionSheet. As a result, on Android, it looks like this. It's not very beautiful. Of course, as a prototype, that's it.

Although 5 operations have been written here, I have only implemented 1.5. This 1 is:

Okay, I know this is a little ugly (it's also called a little. ). The function is simple, which is to edit the text and then update it back to the original list. The other half, is the editor tag page, this is just completed a look, but I do not feel very easy to use, may be changed later.

According to my current vision, DailyTick will not have the same function as other time recording software to edit the start and end time of an event. What I provide is to split a time period or merge two time periods. This ensures that the timeline of the day is complete, and there is no such thing as "unrecorded time". Because according to my design philosophy of this software, people can't control time, no matter how you use your time, time itself will flow away out of control. So all we can do is record what we have done in a certain period of time. There may be a problem that needs to be solved in the future, that is, where to reflect my schedule for the day, that is, where TODO will record it.

Here, there is a UI for time split. I wrote a draft, but I didn't put it up. For merge operations, there may be only confirmation prompts and there will be no separate UI.

Statistical UI

On the statistics page, there is only one WebView, which is, of course, a custom WebView, because I need to pass data between C # and JS. The basic implementation of this HybridWebView has been implemented, but there is no idea how to pass the data. According to the current preliminary vision, you should use highchart.js and jQuery to complete the implementation of the statistics page (there is no complex interaction, do not want to go to the MVVM stuff). It's mainly reports and pie charts. Although I think pie charts are of limited significance, a direct table can do a lot of work, but if the tool is spread to people from non-science backgrounds (just fantasize), then statistical charts become essential.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.