创建调度程序WinFOrm [英] Creating Scheduler WinFOrm

问题描述

大家好，

我需要一些帮助。

我想申请规划，我坚持创建时间线或显示日历周视图。你可以把物品从日期拖放到另一个。

这样的东西：



http://planningboard.muehlgasse.de/ [ ^ ]



我不想给我代码，只是建议我怎么试试要做这个。





先谢谢你，

Hi Guys,
I need a little bit help.
I want to make application for planning, I'm stuck to create time line or to display calendar in week view. Where you can drag and drop items from on date to another.
Something like this:

http://planningboard.muehlgasse.de/[^]

I don't want to give me code, just suggestion how I can try to make this.


Thanks in Advance,

推荐答案

你真的没有给我们提供很多帮助你的信息。



你知道怎么画网格吗？你知道如何实现拖放吗？你甚至知道如何获得光标位置吗？



创建你所描述的应用程序涉及很多东西 - 而不仅仅是技术细节而是应用程序设计。



我建议写一份全面而详细的清单，列出申请必须做的事情。如（例如）：

*文件|打开命令 - 接受用户的文件名;打开文件并显示包含的日历;如果文件没有正确的扩展名，或者其内容格式不正确，则向用户显示错误。

...

*用户拖动约会的一端 - 系统根据需要更改开始/结束日期或时间（开始或结束，日期/时间取决于拖动的结束）。如果开始被拖过结束，反之亦然，直观的事情发生（即旧的结束成为新的开始，等等）

*用户从约会的主体拖延 - 系统更改开始和结束日期/时间，保持持续时间不变。

...

*显示日期范围 - 显示一组单选按钮，允许用户选择日历是显示单日，一周，一个月，一整年还是即将到来的约会列表。

...



一旦你写下你的应用程序必须展示的所有行为，你就可以逐一解决技术问题。



有一套书面要求通常会降低不确定性，使其更容易上手。另外 - 如果你真的不清楚应用程序应该做什么，你就无法完成它，是吗？



通过分组要求来组织您的想法可能会有所帮助。没有强硬的分组;对于你想写的应用程序，我会建议像：持久性;个性化（用户偏好）;约会（定义约会的所有信息的集合 - 所需信息 - 或者可以与一个 - 可选信息相关联）;与其他民族的日历互动;用户界面交互模式;等等。


如果不确定你的应用程序应该做的一切，也许建立一个原型 - 模拟用户交互的某个部分但不会持久化任何价值观 - 都会有用。



另外 - 从敏捷方法游戏书中剔除：迭代。构建一个部分，功能的一个子集，并使其达到有用的程度。然后，通过添加另一块可用行为来扩展。记住保持每个块很小（1-4周的工作）。

You really havent given us much information with which to help you.

Do you know how to draw a grid? Do you know how to implement drag/drop? Do you even know how to get the cursor position?

There are many many things involved in creating an application that you have described - and not just the technology details but the application design.

I would recommend writing down a comprehensive and detailed list of EXACTLY the things the application must do. Such as (for example):
* File | Open command - accepts an file name from the user; opens the file and displays the contained calendar; if the file doesn't have the right extension, or if its contents are not in the right format, displays an error to the user.
...
* User drags one end of an appointment - system changes the start / end date or time as needed (start, or end, date/time depending on which end was dragged). If the start is dragged past the end, or vice versa, the intuitive thing happens (i.e. the old end becomes the new start, etc.)
* User drags from the body of an appointment - system changes the start AND end date / time, keeping the duration constant.
...
* Displayed date range - a set of radio buttons is presented that allows the user to select whether the calendar displays a single day, a week, a month, a whole year, or a list of upcoming appointments.
...

Once you have written down all the behaviours your application must exhibit, you can start addressing the technical problems one-by-one.

Having a written set of requirements often reduces the level of uncertainty and makes it easier to get started. Also - if you're really not clear what the app is supposed to be able to do, you're not going to be able to finish it, are you?

It may help to organise your thoughts by grouping the requirements. There are no hard-and-fast groupings; for the app you want to write I would suggest things like: persistence; personalisation (user preferences); appointments (the set of all information that defines an appointment - required information - or can be associated with one - optional information); interaction with other peoples' calendars; user-interface interaction modes; etc.

In the case of not being sure of everything your application should do, perhaps building a prototype - that models a certain part of user interaction but doesn't persist any values - would be useful.

Also - take a leaf out of the Agile methodology play-book: iterate. Build a part, a subset of the functionality, and get it to the point that it is useful. Then, extend by adding another chunk of usable behaviour. Remember to keep each chunk small (1-4 week's work).

这篇关于创建调度程序WinFOrm的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！