PHPNB70

(Difference between revisions)
(→3. PHP Frameworks)
 
(12 intermediate revisions not shown)
Line 1: Line 1:
-
== PHP in NB 6.9.Next ==
+
== PHP in NB 7.0 ==
'''Version:''' draft 0.0.1
'''Version:''' draft 0.0.1
 +
 +
'''Disclaimer:''' The content of this NetBeans development wiki page is
 +
intended for pre-planning purposes ONLY. The development, release, and
 +
timing of any feature or functionality described here should not be
 +
treated as final, and is subject to change at any time at the sole
 +
discretion of Oracle. For information about NetBeans software releases
 +
please visit the [http://netbeans.org/community/releases/roadmap.html NetBeans Roadmap] or the [http://wiki.netbeans.org/Development NetBeans Release Planning] wiki.
__TOC__
__TOC__
Line 9: Line 16:
== Editor ==
== Editor ==
{| border=1 class="simple"
{| border=1 class="simple"
-
! ID [Priority] Task Description
+
! ID
 +
! Priority  
 +
! Task Description
! Details
! Details
! Link
! Link
|-
|-
-
| '''1.0 [P3] Configuration for coding standards'''
+
| 1.1
-
Support for configurable coding standards. If we want to spread '''''NetBeans into corporate sphere,then the codding style has to be configurable not to block Continuous Integration'''''  
+
| P2
-
|Each configuration should be defined in separate configuration file. There should be possible to add its own coding standard whereas a few predefined standards(how to write PHP code) should be delivered with Netbeans PHP. These predefined configurations could be taken from PHP Code Sniffer(called: MySource, PEAR, PHPCS, Squiz and Zend), which seems to be de facto standards.
+
|'''Bracket matcher refactoring'''
 +
| The current bracket matcher is based on the indentation of the source code. This doesn't work when the code is not indented according our rules. There are bugs that it will be solved by this.  
|
|
|-
|-
-
|'''1.1 [P2] Bracket matcher refactoring'''
+
| 1.2
-
| The current bracket matcher is based on the indentation of the source code. This doesn't work when the code is not indented according our rules. There are bugs that it will be solved by this.  
+
| P3
 +
| '''Code sniffer'''
 +
Support checking coding standards.
 +
|Each configuration of a standard should be defined in separate configuration file. There should be possible to add its own coding standard whereas a few predefined standards(how to write PHP code) should be delivered with Netbeans PHP. These predefined configurations could be taken from PHP Code Sniffer(called: MySource, PEAR, PHPCS, Squiz and Zend), which seems to be de facto standards.
|
|
|-
|-
-
|'''1.2 [P3] Formating/Indentation improvements, stabilization'''
+
| 1.3
 +
| P3
 +
|'''Formating/Indentation improvements, stabilization'''
|In NB 6.9 there is a new formatter. There are some bugs mainly in formatting PHP inside HTML files. The same applies for indentation.  
|In NB 6.9 there is a new formatter. There are some bugs mainly in formatting PHP inside HTML files. The same applies for indentation.  
|
|
|-
|-
-
|'''1.3 [P3] Model stabilization, improvements'''
+
| 1.4
 +
| P3
 +
|'''Model stabilization, improvements'''
| Model is heavily used inside PHP editor and should prepared to be useful for framework support developers  
| Model is heavily used inside PHP editor and should prepared to be useful for framework support developers  
* document it
* document it
Line 33: Line 50:
|
|
|-
|-
-
| '''1.4.[P3] Type Inference improvements (Framework support)'''
+
| 1.5
 +
| P3
 +
| '''Type Inference improvements (Framework support)'''
| Type inference based on model needs improvements for properties in interfaces| Model API/impl. needs to be improved to be able to resolve types for supporting frameworks like Zend that adds properties to interfaces. Will improve quality of code completion, goto declaration, mark occurences, find usages ...
| Type inference based on model needs improvements for properties in interfaces| Model API/impl. needs to be improved to be able to resolve types for supporting frameworks like Zend that adds properties to interfaces. Will improve quality of code completion, goto declaration, mark occurences, find usages ...
|
|
|-
|-
-
| '''1.5 [P3] Declarative Extension of Editor Features'''
+
| 1.6
 +
| P3
 +
| '''Declarative Extension of Editor Features'''
Obviously editor cannot support all extensions for the PHP language, all frameworks   
Obviously editor cannot support all extensions for the PHP language, all frameworks   
|User should be able at least to extend:  
|User should be able at least to extend:  
Line 44: Line 65:
|
|
|-
|-
-
| '''9.0 [P3] Refactorings'''
+
| 1.7
 +
| P3
 +
| '''Refactorings'''
Implements some refactoring that are missing
Implements some refactoring that are missing
| Deliver Rename Refactoring and other Refactorings like Extract to method ...
| Deliver Rename Refactoring and other Refactorings like Extract to method ...
-
|
+
| [http://netbeans.org/bugzilla/show_bug.cgi?id=189069 #189069], [http://netbeans.org/bugzilla/show_bug.cgi?id=189070 #189070]
|-
|-
-
| '''10.0 [P3] PHP 5.3 support improvements'''
+
| 1.8
-
PHP 5.3 brought many features that were not fully supported in 6.8. Phar,namespace view (analogy of package view in java) should appear in PHP project plan, but also additional editor improvemnts
+
| P3
-
|
+
| '''PHP 5.3 support improvements'''
 +
PHP 5.3 brought many features that were not fully supported in 6.8 and still are not supported in 6.9. Phar,namespace view (analogy of package view in java) should appear in PHP project plan, but also additional editor improvemnts
 +
|  
* Improve mark occurences, goto declaration, find usages for cases when the same class/function/constant names from different namespaces are used inside one file
* Improve mark occurences, goto declaration, find usages for cases when the same class/function/constant names from different namespaces are used inside one file
* additional contexts for Code completion like the one for anonymous/closures functions
* additional contexts for Code completion like the one for anonymous/closures functions
 +
| [http://netbeans.org/bugzilla/show_bug.cgi?id=178861 #178861]
 +
|-
 +
| 1.9
 +
| P3
 +
| '''Provide functionality Inspect Hierarchy, improve navigator'''
 +
| Inspect hierarchy is the same functionality like in java editor, where user can see the class hierarchy and also can inspect members. In navigater there should be implemented functionality for displaying methods and fields from parents and implements other functionality that is provided by navigator for java source files.
 +
| [http://netbeans.org/bugzilla/show_bug.cgi?id=139698 #139698]
 +
|-
 +
| 1.10
 +
| P3
 +
| '''Integrate spellchecker into PHP source code'''
 +
| The current implementation provide spell checking only in html part of PHP files. The spell checking should be also provided in PHP comments.
|
|
 +
|}
|}
Line 68: Line 106:
| P2
| P2
| '''Generating PHP Doc''' This is one of the missing features that could be coverd in the release.  
| '''Generating PHP Doc''' This is one of the missing features that could be coverd in the release.  
-
|Generate PHP documentation from PHP comments in the source files. It's similar to the generating JavaDoc for java source files. The PHP support will use the PHP documentation generater available in the PHP runtime.  
+
|Generate PHP documentation from PHP comments in the source files. It's similar to the generating JavaDoc for java source files. The PHP support will use the PHP documentation generater available in PEAR (similarly as for PHPUnit, for example).  
|
|
|}
|}

Current revision as of 10:20, 24 November 2010

PHP in NB 7.0

Version: draft 0.0.1

Disclaimer: The content of this NetBeans development wiki page is intended for pre-planning purposes ONLY. The development, release, and timing of any feature or functionality described here should not be treated as final, and is subject to change at any time at the sole discretion of Oracle. For information about NetBeans software releases please visit the NetBeans Roadmap or the NetBeans Release Planning wiki.

Contents


The NetBeans PHP support is popular and obtains many users. It's the support that attracts many new people that are switching from other IDEs. The features in the release NetBeans 6.9.Next will be mainly targeted to improve productivity of the IDE.

Editor

ID Priority Task Description Details Link
1.1 P2 Bracket matcher refactoring The current bracket matcher is based on the indentation of the source code. This doesn't work when the code is not indented according our rules. There are bugs that it will be solved by this.
1.2 P3 Code sniffer

Support checking coding standards.

Each configuration of a standard should be defined in separate configuration file. There should be possible to add its own coding standard whereas a few predefined standards(how to write PHP code) should be delivered with Netbeans PHP. These predefined configurations could be taken from PHP Code Sniffer(called: MySource, PEAR, PHPCS, Squiz and Zend), which seems to be de facto standards.
1.3 P3 Formating/Indentation improvements, stabilization In NB 6.9 there is a new formatter. There are some bugs mainly in formatting PHP inside HTML files. The same applies for indentation.
1.4 P3 Model stabilization, improvements Model is heavily used inside PHP editor and should prepared to be useful for framework support developers
  • document it
  • stabilize implementation
  • provide needed changes to support Cake PHP and other similar frameworks.
1.5 P3 Type Inference improvements (Framework support) Model API/impl. needs to be improved to be able to resolve types for supporting frameworks like Zend that adds properties to interfaces. Will improve quality of code completion, goto declaration, mark occurences, find usages ...
1.6 P3 Declarative Extension of Editor Features

Obviously editor cannot support all extensions for the PHP language, all frameworks

User should be able at least to extend:
  • code completion for individual contexts
  • add signatures for extensions
1.7 P3 Refactorings

Implements some refactoring that are missing

Deliver Rename Refactoring and other Refactorings like Extract to method ... #189069, #189070
1.8 P3 PHP 5.3 support improvements

PHP 5.3 brought many features that were not fully supported in 6.8 and still are not supported in 6.9. Phar,namespace view (analogy of package view in java) should appear in PHP project plan, but also additional editor improvemnts

  • Improve mark occurences, goto declaration, find usages for cases when the same class/function/constant names from different namespaces are used inside one file
  • additional contexts for Code completion like the one for anonymous/closures functions
#178861
1.9 P3 Provide functionality Inspect Hierarchy, improve navigator Inspect hierarchy is the same functionality like in java editor, where user can see the class hierarchy and also can inspect members. In navigater there should be implemented functionality for displaying methods and fields from parents and implements other functionality that is provided by navigator for java source files. #139698
1.10 P3 Integrate spellchecker into PHP source code The current implementation provide spell checking only in html part of PHP files. The spell checking should be also provided in PHP comments.

Project

ID Priority Task Description Details Link
2.1 P2 Generating PHP Doc This is one of the missing features that could be coverd in the release. Generate PHP documentation from PHP comments in the source files. It's similar to the generating JavaDoc for java source files. The PHP support will use the PHP documentation generater available in PEAR (similarly as for PHPUnit, for example).

PHP Frameworks

ID Priority Task Description Details Link
3.1 P3 CakePHP framework support One of the most used PHP framework these days should have the similar support as Symfony or Zend Framework have in NB 6.9. BZ, 158 votes
Retrieved from "http://wiki.netbeans.org/PHPNB70"
Not logged in. Log in, Register

NetBeans Wiki
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo