Hi Dimitri

I appreciate everybody has their views on features etc, but could I request

1) Intelli-type support for phpDoc, when I'm inside /** comment tag and use the @ symbol just show a drop down with all the possible features.
2) Enhance the Integration options - People would like to integrate more things (Parsers, SVN etc etc), if more options such as being able to request input (@input@) then we'd see much more integration.
3) Wizard/Code/WSDL generation for PHP 5's native soap support.
4) Native support for SVN.

I appreciate these may not be top priority, but are these item's you would add? could be achieved easily?

I honestly think small enhancements like this will give Nusphere a greater edge over Zend, we'll see a much greater number of people developing enhancement scripts - i have several I'd like to develop including integrating Seapine SCM, but I can't simple because i need to add comments etc when adding/check out files.

Cheers

Apologies for bumping this, my subscription is due for renewal + I need additional licenses for my new developers, so I need to be sure Nusphere will meet our future requirements in both features and extensibility, we're now reaching a size where SCM and PHPDoc are becoming incredibly important (so if the IDE makes them easy to use, the developers are more likely to do it properly!).

we have this in our plans

I'm not sure what you meant under @input@. Would you please provide an example of its usage?

NuSoap library provides on-the-fly generation for WSDL. Why not to use it?

TortoiseSVN, that PhpED integrates with, is a native SVN client.

PHP Doc

Thats great news

@input

Sorry I wasn't specific with this one, the CVS integration has the @Comment@ which doesn't appear to be a useable feature for anything other than CVS - it'd be good to have a generic input tag which pops up a dialog and allows input to be requested before firing off an integrated tool, why? I may need to enter a path, some config options or even a comment before commiting stuff back.

SOAP Support

I appreciate your comment about NuSOAP and know it has a wide user-base, but we've already pretty established with using the native SOAP - as a progressive IDE will it not pay to support the native features in such a manner?

SVN

ToirtoiseSVN is not the best tool and I still have to manually install/integrate it - Why not ship PhpED with support allready added like you do CVS?

Hmm but @input@ alone (as a word) has very little info about what's supposed to appear in the input dialog. A more adequate macro would be like @input{filename|dialogname}@ but it will require to have this dialog created/designed somehow and what you type in it should be converted into the command line options. Not a trivial feature.

I'm not sure if a software written in php is less native than one written in C or C# or java. Would you please comment?


Not at all. You don't need to integrate it. It will appear in the popups automatically right after installed.

it wouldn't be as native as TortoiseSVN is

I was initially thinking along these lines but thought it a little too much, but since you mention it, I'm not suggesting its a trivial feature, but it could be as simple as a couple of pre-defined dialogs, or go the whole hog and allow custom dialogs to be defined.



Ok, I use the term "native" to freely, but your dodging the issue.

The reason for us not using NuSOAP is we're already well established with PHP's native/builtin soap wrapper, and if I'm being brutally honest I think the adoption of the native/builtin soap is/will eclipse that of 3rd party libraries, it might be that these 3rd party libraries offer superior features, but the the native/builtin library is more convenient and probably faster.

Can Nusphere afford to ignore this?



Again, perhaps I've used the term "native" to freely. But still your dodging the issue, why doesn't Nusphere ship with SVN support? I've seen lots of requests for this on the forum and people always get pointed to how to integrate ToirtoiseSVN, wouldn't it be more convenient for customers if SVN was intrgrated in the same fashion as CVS?

By the way, I'm only being such a pain in the ass because I truly enjoy using PhpED- its cruel to be kind

Over on the Mac, this sort of thing is handled by supplying hooks to run AppleScript scripts (as well as UNIX shell scripts). This opens one's program to a whole world of extremely flexible automation without having to code any of it. Is there any equivalent on Windows that you can use? Seems silly to have to reinvent the automation wheel in every program.



You misread the statement: OP meant 'native' as in built into PHP, not 'native' as in supported on the hardware or OS platform without translation.

As for the question at hand, shouldn't it not make any difference on the consumption side how a WSDL file was generated? That is, is it feasible to use NuSoap to generate a WSDL file that is then consumed by PHP 5's native SOAP support?



I've not used PhpED's native CVS client so I can't use it for comparison, but my suspicion is that anything NuSphere would build in for SVN wouldn't be nearly as capable as TortoiseSVN. For instance, would it have the diff feature, or the logging and browsing features?

Perhaps better would be if NuSphere tied into TortoiseSVN more than just the Explorer shell integration in the Workspaces tab. For instance, it could integrate it directly into the open and saving functions to give us additional options there. In other words, break the integration out of the confines of the Shell menu in the Workspaces tab. I don't know if this is possible, but it would be nice.

Thoughts?

I agree with the needed support for PHPdoc. It should use the code insight/completion for this also making it 10 times easier to write documentation.