java 柱形图 饼图 折线图 JFreeChart,里面包含与JFreeChart有关的所有jar包，还有我自己写的例子，通俗易懂！

Android 仿随手记的炫酷饼图源码.zip

根据省份位置，在Echarts 地图上画饼图， 可点击放大单个饼图

Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 Axure数据图表元件（柱图、饼图、雷达图、折线图、面积图）Axure数据图表元件Axure数据图表元件Axure数据图表元件 AXURE 元件 图表

浮云E绘图SDK3.2，提供完成的开发资料和工具（绘图编辑器+绘图组件DLL+4个Demo+说明文档）。支持快速开发各类状态图、流程图、平面图等。同一类绘图，一套代码通用。 比如状态图，一套源码+状态配置txt文件+绘图编辑器画图，可以支持多种状态图。后期不同场景下的状态图（如设备采集状态图、车站状态图、网络状态图等），都不需要修改源码，只需要绘图编辑器根据业务对象画物理图元+业务图元的状态配置文件实施，即可。真正做到，代码免维护，使用各类状态图。 浮云E绘图支持直线、矩形、椭圆、多点线、三角、四角、扇形、文字、图片等基础图元的绘制编辑，并支持动态组合成复合模板图元。 浮云E绘图支持复制、粘贴、撤销、重做； 支持上对齐、底部对齐、左对齐、横纵向均匀分布等； 支持置于顶层、上一层、下一次、置于底层等； 支持画布、网格、自动吸附对齐等 支持组合、打散等 支持滚动、缩放 支持打印导出等 使用浮云E绘图开发流程 1. 先使用浮云E绘图编辑器.exe绘制图形 2. 保存绘图数据文件 3. 创建第三方工程，集成FYDC.dll（参看Demo） 4. 调用API函数完成二次开发

举例：饮料自动售货机系统的状态图 投入硬币 （有效的） 按下选择饮料键 Do:显示售货机在备用 所有灯都关闭 Do:显示金额总数 Do:显示金额已够 饮料选择灯亮 取出饮料 结算找零 扣减存量 完成交易 饮料“售完”灯亮 投入硬币金额 (1元、5元、10元) 金额不足 再投币 存量为零 无效的硬币 取消 取消 回到备用状态 回到备用状态

//Set visible map extents map.Center = new SharpMap.Geometries.Point(centerX, centerY); map.Zoom = Zoom; //Generate map System.Drawing.Bitmap img = (System.Drawing.Bitmap)map.GetMap(); //Stream the image to the client context.Response.ContentType = "image/png"; System.IO.MemoryStream MS = new System.IO.MemoryStream(); img.Save(MS, System.Drawing.Imaging.ImageFormat.Png); // tidy up img.Dispose(); byte[] buffer = MS.ToArray(); context.Response.OutputStream.Write(buffer, 0, buffer.Length); public SharpMap.Styles.VectorStyle GetChartingStyle(SharpMap.Data.FeatureDataRow row) { SharpMap.Styles.VectorStyle style = new SharpMap.Styles.VectorStyle(); int numMale = int.Parse(row["male"].ToString()); int numFemale = int.Parse(row["female"].ToString()); style.Symbol = this.GetChart(numMale, numFemale); return style; }

LabVIEW状态图模块 状态图—— 用直观的方法来表达基于事件的系统 * Statecharts are an extension of the finite state machine. They were created by David Harel in the 1987 and are part of the UML standard commonly used in embedded system development. ----------------- UML stands for Unified Modeling Language (some say Universal Modeling Language). It is a modeling language consisting of several sublanguages to model structural and behavorial aspects of a software system. UML consists of multiple types of diagrams. The underlying premise of UML is that no one diagram can capture the different elements of a system in its entirety. The nine UML diagrams are: Use case diagram: Identifies the primary elements and processes that form the system. The primary elements are termed as "actors" and the processes are called "use cases“. Class diagram: Defines a detailed design of the system and classifies the actors into interrelated classes. The relationship between the classes can be either an "is-a" or "has-a" relationship. Each class may provide functionality through "methods“. Each class may have certain "attributes" that uniquely identify the class. (3) Object diagram: A special kind of class diagram. An object is an instance of a class. This essentially means that an object represents the state of a class at a given point of time while the system is running. (4) State diagram: Represents the different states that objects in the system undergo during their life cycle. Objects in the system change states in response to events. (5) Activity diagram: Captures the process flows in the system. Similar to a state diagram, an activity diagram also consists of activities, actions, transitions, initial and final states, and guard conditions. (6) Sequence diagram: Represents the interaction between different objects in the system. It is time-ordered. This means that the exact sequence of the interactions between the objects is represented step by step. Different objects in the sequence diagram interact with each other by passing "messages". (7) Collaboration diagram: Groups together the interactions between different objects. The interactions are listed as numbered interactions that help to trace the sequence of the interactions. The collaboration diagram helps to identify all the possible interactions that each object has with other objects. (8) Component diagram: Represents the high-level parts that make up the system. This diagram depicts, at a high level, what components form part of the system and how they are interrelated. A component diagram depicts the components culled after the system has undergone the development or construction phase. (9) Deployment diagram: Captures the configuration of the runtime elements of the application. This diagram is by far most useful when a system is built and ready to be deployed

仅供参考,自己做下会有很大帮助，当然量的话比较大，当时做了一个星期

示例：一卡通状态图