[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: CVS update: ChangeLog
User: sdb
Date: 06/07/26 18:55:44
Modified: . ChangeLog README ToDos
Log:
Updated expository material to reflect current state of project.
Revision Changes Path
1.41 +9 -1 eda/geda/gaf/gattrib/ChangeLog
(In the diff below, changes in quantity of whitespace are not shown.)
Index: ChangeLog
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/gattrib/ChangeLog,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- ChangeLog 17 Jul 2006 01:50:09 -0000 1.40
+++ ChangeLog 26 Jul 2006 22:55:44 -0000 1.41
@@ -1,7 +1,15 @@
+2006-07-25 Stuart Brorson <sdb@xxxxxxxxxx>
+ * src/f_export.c, src/x_dialog.c and others: Implemented
+ ability to export CSV file of component sheet.
+
+ * ToDos, README: Updated expository material to reflect current
+ state of project.
+
2006-07-15 Ales Hvezda <ahvezda@xxxxxxxxxxxxx>
* src/gtksheet_2_2.c: Changed a g_free on a gdk_pixmap to
- g_object_unref to fix a valgrind error and the following output when
+ g_object_unref to fix a valgrind error and the following
+ output when
exiting gattrib: free(): invalid pointer 0x812a108!
* src/gattrib.c, src/gtksheet_2_2.c, src/s_object.c,
1.2 +33 -28 eda/geda/gaf/gattrib/README
(In the diff below, changes in quantity of whitespace are not shown.)
Index: README
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/gattrib/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- README 8 Aug 2004 02:46:45 -0000 1.1
+++ README 26 Jul 2006 22:55:44 -0000 1.2
@@ -13,8 +13,8 @@
attributes outside of gschem, and then save the .sch files back
out. When it is completed, it will allow the user to edit attributes
attached to components, nets, and pins. (Currently, only component
-attribute editing is implemented; pin attributes are displayed only,
-and net attributes are TBD.)
+attribute editing is implemented; pin and net attributes are displayed
+only.)
Gattrib is useful in situations where you need to view, add, modify,
or delete a number of attributes all at once. It saves you the pain
@@ -26,10 +26,10 @@
design files to attach the "footprint" attributes all at once using an
easy-to-use spreadsheet.
-WARNING NOTE: Gattrib is currently PRE-ALPHA SOFTWARE!
-It has been tested on several designs, but is not garuanteed to work.
-It may even trash your design! Therefore, if you wish to try gattrib
-out, please create a backup copy of your design before you run it!
+WARNING NOTE: Gattrib has been tested on many designs,
+but is not guaranteed to work. It may even trash your design!
+Therefore, always keep a back-up copy of your design files. Note that
+this is good advice when using any software on critical files.
------------------------------------------------------------------
USAGE
@@ -52,20 +52,22 @@
To save your design, just select "save" from the command menu. Note
that no checks are currently done when you select save. Be careful!
+You can also save out a csv (comma separated values) file, which can
+later be imported into e.g. oocalc. This is useful for BOM
+management.
+
To quit, just select "quit" from the command menu. Note that
currently no checks thet you have saved your design are done when you
quit.
If you want to add an entirely new attribute to your design (i.e. one
-which doesn't exist on any component), you must first attach at least
-one instance of that attribute to a component using gschem. Then you
-can use gattrib to attach the attribute to the remaining components.
-(The reason for this is that gattrib creates its spreadsheet columns
-based upon all attributes it finds when reading in the design.
-Therefore, to create a column for a new attribute, you need to make
-sure that that new attribute pre-exists in the design.) In the future,
-you will be able to add new attribute columns directly from gattrib,
-but this feature is currently unimplemented.
+which doesn't exist on any component), you can do this through "edit
+-> add new attribute column". You can also delete an entire attribut
+column.
+
+You can set the visibility of any particular attribute, or an entire
+column of attributes through the "visibility" menu. Just select the
+attribute or column first, then do "visibility -> <whatever>".
------------------------------------------------------------------
FEATURES
@@ -75,29 +77,30 @@
* .sch file read in from command line.
* .sch file read in from menu.
* .sch file save out from menu.
+* CSV (comma separated value) file save out from menu.
* Component attribute editing (of course).
+* Net attribute viewing.
* Pin attribute viewing.
+* Add/delete attribute columns.
+* Changing visibility of attributes.
* Quit from menu.
The following features are currently unimplemented, but will be
incorporated at some future date:
-* Throw up "Are you sure" dialog boxes upon selecting "save" and
- "quit" from menu.
-* Alphabetic sort of rows. (Should happen automatically upon read-in
- of design.)
+* Throw up "Are you sure" dialog boxes upon selecting "save" from
+ menu. (Is this really necessary?)
* Editing of net attributes (important for setting routing
attributes).
-* Adding/deleting attribute columns (to add/delete entire sets of
- attributes from a design.)
* Search/replace of individual attributes.
* Search for component refdeses & netnames.
-* Set/view component & net visibility (through options pull-down
- menu). Currently, visibility is "invisible", and both name & value
- are displayed (if you turn on the visibility).
+* Indicate component visibility by changing the color of the
+ attribute in each cell. Example: Invisible = light grey.
+ Name only = red. Value only = normal black. Name & value = bold
+ face.
-Note that if you select unimplemented features from the menu, nothing
-will happen.
+Note that if you select unimplemented features from the menu, you will
+get a warning window.
------------------------------------------------------------------
INSTALLATION
@@ -111,8 +114,10 @@
make
make install
-Note that you may need to set some environment variables first. If
-your compilation barfs, try setting these (for csh):
+Note that you may need to set some environment variables first. Also
+remember to use a date code (20040806) corresponding to the current
+gattrib distribution . If your compilation barfs, try setting these
+(for csh):
setenv LD_LIBRARY_PATH /usr/local/geda/lib:$LD_LIBRARY_PATH
setenv PATH /usr/local/geda/bin:$PATH
1.4 +5 -3 eda/geda/gaf/gattrib/ToDos
(In the diff below, changes in quantity of whitespace are not shown.)
Index: ToDos
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/gattrib/ToDos,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- ToDos 14 Jul 2005 17:29:24 -0000 1.3
+++ ToDos 26 Jul 2006 22:55:44 -0000 1.4
@@ -1,6 +1,6 @@
Gattrib todos.
-Last updated 7.13.2005 -- SDB
+Last updated 7.26.2006 -- SDB
--------------------------------------------------------------------
This is a running list of things left to be done with gattrib. Items
@@ -19,7 +19,7 @@
page1.sch, page2.sch -> page2.sch.) Currently smashes all pages
together.
* Find out why it leaves "xterm" on the command prompt when you
- invoke the prog with no files on the cmd line.
+ invoke the prog with no files on the cmd line. This may be GTK bug.
* Change save menus to: save project, save as, which cycles through
pages and saves objects out on a page by page basis.
* Incorporate a "close" item on the menu to close out the current
@@ -59,7 +59,8 @@
adjacent cells. Maybe automatically size cell to fit text? Problem is that
"file" attributes can be very long.
* Per Ales, use the gtksheet stuff as a library instead of a bunch of source
- files. Is this necessary?
+ files. Is this necessary? No. I don't want to do this since a third-
+ party library can change, which makes support a PITA.
* User should be able to set attrib visibility. How to implement & show?
* ##### Incorporate ability to add attrib columns.
* Refactor code so that it makes more sense architecturally.
@@ -70,3 +71,4 @@
* Change display of attrib text in each cell depending upon attrib
visibility state. Example: Invisible = light grey. Name only = red.
Value only = normal. Name & value = bold face.
+* Make gattrib import csv.
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs