Tags
Keine Tags

Frequently used words (click to add to your profile)

javaandroidc++linuxc#windowsobjective-ccocoaqtpython誰得phprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer

最近の作業部屋活動履歴

2018-03-27

最近のWikiの更新 (Recent Changes)

No changes on this wiki.

Wikiガイド(Guide)

サイドバー (Side Bar)

dia_improved

  • R/O
  • R/O (HTTP)
  • R/W (SSH)
  • R/W (HTTPS)
Fork

作図ソフト dia の改良版

Release Files

No download files.

Recent Commits

Rev.ZeitAutorNachricht RSS
3cfcb99a2017-09-11 20:24:06Sebastian RasmussenUpdate Swedish translation
b86085df2017-06-23 04:50:13Piotr DrągAdjust translations for the Postscript > PostScript chang...
79f241e42017-06-23 04:18:04Piotr DrągCorrect PostScript capitalization https://bugzilla.gnome...
5071577d2017-06-11 03:41:22Kristjan SCHMIDTUpdated Esperanto translation
cdfa0df72017-03-05 19:37:00Inaki Larranaga MurgoitioUpdate Basque language
761c2a7a2017-03-05 19:35:43Inaki Larranaga MurgoitioUpdate Basque language
5ddb1ac82017-03-05 19:34:41Inaki Larranaga MurgoitioUpdate Basque language
3326bf102016-11-25 01:41:15Ask Hjorth LarsenUpdated Danish translation
ef46a1172016-10-22 07:42:05Piotr DrągUpdate Polish translation
e45409762016-10-22 07:16:31Piotr DrągUpdate Polish translation
Dia is a program for drawing structured diagrams.

Dia is a GNU program, and is Free Software.  See the COPYING file for
the licence.

Documentation is a bit sparse at the moment.  Some info can be
found in the doc/ directory.

--

I haven't had time to write anything here yet.
Read INSTALL for some brief installation instructions.

Homepage for Dia is at:
 https://wiki.gnome.org/Apps/Dia

Some comments about the source:
-------------------------------

 Everything on the screen 'inherits' from the structure Object 
in lib/object.h. (ps. this is a nice place to start reading the code.).
Inherits in C means (as in gtk) that it begins with a copy of that structure. 
Some base classes exists in lib/, like element.h (for doing 'box-like' 
objects), connection.h (for doing 'line-like' objects), orth_conn.h (for doing 
connections with orthogonal lines, like the uml-stuff) and render_object.h 
(for doing picture-like objects). These base classes are then subclassed in 
the different object in the object-libraries like objects/standard object/UML 
and object/network.

 The objects work by filling out two structures that the main program (app/*) 
uses to handle the objects. The ObjectType structure which consists of some 
info and a pointer to the type-operations (create+load+save). There's one 
ObjectType per object type currently loaded. Then the Object structure, there 
exists a copy of this for each object of the kind on screen (and in 
copy-buffers). This contains some info like: type, bounding_box, position, 
handles (the rectangles you move with the mouse) and connections. It also 
contains a pointer to the object-operations. These are called from the main 
program when if wants the object to do something. All ops take an Object as 
the first argument. This is usually casted to the subtype in the function 
headed (gives all those pita warnings) so that you directly can use the info 
stored in the subclasses. Most ops are quite self-describing, and the code can 
be copy-pasted from an object like the one you're doing. Rendering to 
screen/postscript is done through a 'Renderer' abstraction that can be found 
in lib/render.h.
 
XML based objects:
------------------
You can (from version 0.80) create new objects using a SVG like XML languange.
The file doc/custom-shapes has more information about this.
 
Note on handles and connection points:
--------------------------------------

An object has handles to resize it. A handle can be moved either because
the user dragged it with the mouse, or the handle is attached to another
object, which moved itself. The handles are diplayed as little squares
(red: normal, green: attached to an object, blue: can't be moved).

When the handle of an object is connected to another object, it's always
on special points called connection points, displayed as crosses.

Implementation:
- each object has an array of pointer to ConnectionPoint.
- each object has an array of pointer to Handle.
- each Handle has a pointer to 1 ConnectionPoint (NULL if the handle if
the Handle is not connected).
- each ConnectionPoint has a list of all objects connected to it.

The Object type does not manage the allocation/deallocation of handles and
connection points. When saving a diagram the pointer from the handle to
the connectionpoint is saved as the index of the connectionpoint. So make
sure the order of the connectionpoints is the same when loading the saved
object.

Notes on static analysis
------------------------
Some of the recent changes (log message starting with [scan-build] are suggested
by static source analysis, see http://clang-analyzer.llvm.org/scan-build
To use it just run ./configure and make through the scan-build script, like:

PATH=/mnt/Home/from-svn/llvm/Release/bin:$PATH /mnt/Home/from-svn/llvm/tools/clang/tools/scan-build/scan-build ./configure --prefix=/opt --enable-debug=yes
  and
PATH=/mnt/Home/from-svn/llvm/Release/bin:$PATH /mnt/Home/from-svn/llvm/tools/clang/tools/scan-build/scan-build -v -v make -j3
  view with
PATH=/mnt/Home/from-svn/llvm/Release/bin:$PATH /mnt/Home/from-svn/llvm/tools/clang/tools/scan-view/scan-view

(given an uninstalled checkout of llvm to /mnt/Home/from-svn/llvm)

Latest updated Tickets

No tickets

About Chamber Wiki

Welcome to OSDN Wiki system. Here is your chamber Wiki space.

Check Wiki Guide (English) to refer syntax and functions.