bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bugs #9955] Gorm parse outlets redundantly.


From: Gregory John Casamento
Subject: [bugs #9955] Gorm parse outlets redundantly.
Date: Sat, 27 Nov 2004 06:20:20 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040921

This mail is an automated notification from the bugs tracker
 of the project: GNUstep.

/**************************************************************************/
[bugs #9955] Latest Modifications:

Changes by: 
                Gregory John Casamento <address@hidden>
'Date: 
                Sat 11/27/2004 at 11:14 (US/Eastern)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
I have added a new class parser which corrects this issue.  The class in the 
description now parses correctly.

I have also attached the file I created to test with.

GJC






/**************************************************************************/
[bugs #9955] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9955>
Project: GNUstep
Submitted by: Yen-Ju Chen
On: Tue 08/10/2004 at 16:12

Category:  Gorm
Severity:  5 - Average
Item Group:  Bug
Resolution:  Fixed
Privacy:  Public
Assigned to:  gcasa
Status:  Closed


Summary:  Gorm parse outlets redundantly.

Original Submission:  1. Open gorm.
2. "Document" -> "New Module" -> "New Empty"
3. Select "Classes" in main window.
4. "Classes" -> "Load Class..." to load this header:

#include <AppKit/AppKit.h>

@interface LibraryLocationPanel: NSObject
{
    IBOutlet id locationTextField;
    IBOutlet id panel;
    int buttonResult;
}

@end

5. Look at the outlet of this class in inspector.
  The "panel" outlet appears redundantly.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Sat 11/27/2004 at 11:14       By: Gregory John Casamento <gcasa>
I have added a new class parser which corrects this issue.  The class in the 
description now parses correctly.

I have also attached the file I created to test with.

GJC

-------------------------------------------------------
Date: Fri 11/26/2004 at 10:40       By: Gregory John Casamento <gcasa>
I am in the process of writing a new class parser.  I'm wondering if the 
submitter could attach an example of the header which was causing the issue.  
GJC

-------------------------------------------------------
Date: Fri 08/13/2004 at 22:37       By: Gregory John Casamento <gcasa>
I've tried the attached parser.   It has promise and I believe it's got the 
right idea.   

I believe, however, a general objc header parsing framework should be written.  
 Since I want to keep Gorm's external dependency list short, I am going to 
write the library as another lib which is built and installed with Gorm (like 
the GormLib/InterfaceBuilder) library.

GJC

-------------------------------------------------------
Date: Fri 08/13/2004 at 22:24       By: Gregory John Casamento <gcasa>
Several people have complained about the header parser causing issues.  I have, 
therefore, disabled it in current Gorm CVS.  I am currently in the process of 
re-writing the class parser.   I should be done sometime this weekend.

In the mean time, people should add classes by hand.  In case anyone is 
wondering the procedure is (and has always been):

1) create a new document (app, inspector, etc...)
2) Click on the classes toolbar item
3) Select the parent class
4) Click "Gorm->Classes->Subclass"
5) Rename the new class from NewClass to the name you want.
6) Use the class inspector or the outline view+classes menu to add 
actions/outlets to the new class.

Thanks, GJC

-------------------------------------------------------
Date: Wed 08/11/2004 at 16:08       By: Yen-Ju Chen <yjchen>
I made a simple header parser (see attached file).
It uses a general code parser in CodeEditor and MyLibrary.
The idea is the same as SAX.
It only parses the outlet starting with "IBOutlet" or "id".
It handles both /* and // comment.
use 'opentool HeaderParser <header file>' to test.
It is just a demo and is not polished.
If you like this idea of parsing header,
we can make it better.

-------------------------------------------------------
Date: Wed 08/11/2004 at 02:38       By: Gregory John Casamento <gcasa>
Thanks for the report.   The class parser currently needs some revamping.  GJC






File Attachments
-------------------

-------------------------------------------------------
Date: Sat 11/27/2004 at 11:14  Name: Test.h  Size: 614B   By: gcasa
Stress test for the class parser...
http://savannah.gnu.org/bugs/download.php?item_id=9955&amp;item_file_id=1920

-------------------------------------------------------
Date: Wed 08/11/2004 at 16:08  Name: HeaderParser.tar.gz  Size: 4.7KB   By: 
yjchen

http://savannah.gnu.org/bugs/download.php?item_id=9955&amp;item_file_id=1576






For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9955>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/







reply via email to

[Prev in Thread] Current Thread [Next in Thread]