ruby-****@sourc*****
ruby-****@sourc*****
2012年 12月 10日 (月) 12:58:09 JST
-------------------------
REMOTE_ADDR = 184.145.81.223
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dnd-intro
-------------------------
@@ -808,4 +808,4 @@
What we are interested in, is the overall design or architecture of the top window encapsulated in DndTbWindow class. You can learn all about the layout of this window by reading its 'initialize' method, focusing on Gtk widgets built and gathered in the hierarchy of containers, and for the moment ignoring the drag-and-drop related methods, such as 'set_dnd_source_frame_widget' and 'set_dnd_destination_frame_widget'. We'll talk about these only after we understand the structure and design of the top window.
-In summary the main window consists of two parts, the edge frames (on the top, and on the left side of the main window), and the working area in the middle between the two frames. The two frames are the placeholders for our toolbar. Originally the top frame contains the toolbar. When the toolbar is dragged from its original position (frame) onto the other currently empty frame, we have to remove the toolbar from its current (source) frame and place it into the other empty (destination) frame. In this process we also have to shrink the vacated frame and indeed, change the toolbar orientation and size parameters accordingly.
+In summary the main window consists of two parts, the edge frames (on the top, and on the left side of the main window), and the working area in the middle between the two frames. The two frames are the placeholders for our toolbar. Originally the top frame contains the toolbar. When the toolbar is dragged from its original position (frame) onto the other currently empty frame, we have to remove the toolbar from its current (source) frame and place it into the other empty (destination) frame. In this process we also have to shrink the vacated frame and indeed, change the toolbar orientation and size parameters accordingly. Of course we could prepare this window layout, including the toolbar in either position, without the knowledge of how the drag-and-drop features are implemented, and let a software engineer next-door implement the dnd features. This is just to illustrate the two step approach here. After we have our GUI design or window infrastructure established we can st
art focusing on drag-and-drop issues.