Hi All, I've been playing around trying to get a kind "Code Sense" completion working for BBEdit for a while. The move to the new extended ctags format for the built-in PHP support in BBEdit 9.3 finally showed me the way.
As such I've got a very simple -- but functional -- alpha version working. You can check it out from GitHub: http://github.com/carltongibson/BBEdit-Code-Aware-Completion At the moment it only works for PHP -- and it's not very bright, but if you could check it out and provide feedback, that would be great. In essence, at the moment, you need to add a special comment indicating variable types: /* @var $test ReflectionClass */ $test = ... And at some point later you can get a list of $test's methods, choose one and have it complete with placeholder parameters and all that jazz To work the script requires a ctags file with the extended format in the ~/Library/Application Support/BBEdit/Completion Data/PHP/ folder. That means it will work for built-in classes already. You can also download the Zend Framework ctags file I made from: http://noumenal.co.uk/resources/downloads I'm writing up the process of creating the ctags files -- but if you need a ctags file for a different library before that's done let me know. My next goals are to make it smarter (I don't think the comment should be needed in most cases) and to add support for other languages. Finally, if you look at the AppleScript there should be enough there to let you wrap the ZenCoding stuff... (I'm happy to help there, but my first 30 second attempt failed and I thought it better to let someone with more time have a go.) Enjoy. Provide Feedback. Regards, Carlton -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group.
