This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 152507 - Allow to specify an interface or class name in wizard
Summary: Allow to specify an interface or class name in wizard
Status: RESOLVED DUPLICATE of bug 209402
Alias: None
Product: php
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Mysik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-06 10:30 UTC by Petr Pisl
Modified: 2013-02-15 08:13 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Pisl 2008-11-06 10:30:44 UTC
Based on the user feedback

New PHP Class and New PHP Interface don't seem to allow you to specify an 
interface or class name. Will that be possible sometime?
Comment 1 Petr Pisl 2008-11-06 10:35:07 UTC
Implementation of this enhancement is not hard:). Just to clarify the work flow. So you create a file with php
class/interface but you want to named the class/interface differently than is the name of file. I'm right?

For NetBeans 6.5 I suggest to create new php file (the empty one) and then use cls template (write cls and pres TAB
key), which will generate the class stab. 
Comment 2 rmatous 2008-11-06 12:00:21 UTC
WONTFIX from my point of view 
Comment 3 Mikhail Matveev 2008-11-06 20:02:43 UTC
I agree that it should not be implemented.
Comment 4 beberlei 2008-11-07 09:08:37 UTC
I was the user feedback :-)
My idea with this issue: I know you can use templates in a new PHP File to create class with personal name quite easy.

In most PHP projects though, you are using either PEAR Class standard or the ezComponents/symfony like class standard.
1. PEAR Folder/Folder/File.php leads to a "class Folder_Folder_File"
2. ezcComponents/sym has a scheme that does not match filename and classname at all.

Using any of those would leave "New PHP Class" and "New PHP Interface" quite useless.

My workflow usecase would be the following: Allowing to uncheck a box "Use Filename as Classname" enabling an Input
field that would allow to specifiy how to change the classname from the current filename would be a simplification in my
opinion.

That would keep the creation of "New PHP Class" inside one dialog and is easier to "learn" than "New PHP File", cls
template.
Comment 5 Petr Pisl 2008-11-07 15:13:20 UTC
I was thinking about this again. We have some not very good experience from the java class wizard. But the situation in
PHP is different. Berbelei is right.

I'm reopening this again for another evaluation. I'm not saying that we have to do it now and probably create a better
wizard for classes, which will allow specify different scenarios as is describe by Berbelei. 


Comment 6 Filip Zamboj 2010-09-15 12:27:24 UTC
batch reassigning
Comment 7 Ondrej Brejla 2012-04-10 12:16:40 UTC
Isn't that a project part?
Comment 8 Tomas Mysik 2013-02-15 08:13:30 UTC
Marking as duplicate of issue #209402 - now, when namespaces are here, the class name can be "simple" and just different namespace could be used.

Thanks.

*** This bug has been marked as a duplicate of bug 209402 ***