[Pythoncard-cvs] PythonCard/tools/resourceEditor multireadme.txt,NONE,1.1 resourceEditor.py,1.221,1.222

[Alex T. <ale...@us...>]

Update of /cvsroot/pythoncard/PythonCard/tools/resourceEditor
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20465

Modified Files:
	resourceEditor.py 
Added Files:
	multireadme.txt 
Log Message:
Added separate readme file for multiresourceEditor.


Index: resourceEditor.py
===================================================================
RCS file: /cvsroot/pythoncard/PythonCard/tools/resourceEditor/resourceEditor.py,v
retrieving revision 1.221
retrieving revision 1.222
diff -C2 -d -r1.221 -r1.222
*** resourceEditor.py	17 May 2005 14:25:21 -0000	1.221
--- resourceEditor.py	9 Aug 2005 13:56:51 -0000	1.222
***************
*** 66,70 ****
  
          try:
!             self.readme = open('readme.txt').read()
          except:
              self.readme = ''
--- 66,70 ----
  
          try:
!             self.readme = open('multireadme.txt').read()
          except:
              self.readme = ''

--- NEW FILE: multireadme.txt ---
Last updated: 2005-08-09

This represents the beginnings of a GUI resource (layout) editor for PythonCard.

This experimental version (multiresourceEditor) allows various operations to be performed on multiple selected components (eg. move, align, distribute, etc.)

You can view the attributes for all components and menus by selecting the Resource... menu item in the View menu prior to doing a Save or Save As... under the File menu to output a new file.

Known Bugs and Issues:
There are no constraints applied when the shift key is held down, but there is a grid for the widgets to "snap to".

Sizers and anchors are not supported. It is likely anchors will be supported before sizers.

Some of the components don't move or resize correctly all the time, you should report problems to the mailing list. The Choice component seems prone to this movement problem. If a component is difficult to select or move, you can always select it via the Property Editor and then change its position attribute via the Property Editor rather than trying to drag the control itself; the sizing handles should also work.

When editing a dialog or other window that doesn't have a menubar, you'll probably need to increase the vertical size of the window by 20 or 30 pixels to compensate for the resourceEditor menubar. Once your layout looks the way you want it you can subtract the pixel padding you added earlier. On Microsoft Windows, the menubar may wrap if the width of the window is not wide enough, in which case you'll need to add even more padding.

Some future revision of the resourceEditor will use a separate window for doing layout so that the size of a window is always accurate and shows the menubar of the app you're editing.