| 1 |
=== WPide === |
| 2 |
Contributors: WPsites, Thomas Wieczorek |
| 3 |
Tags: code, theme editor, plugin editor, code editor |
| 4 |
Requires at least: 3.0 |
| 5 |
Tested up to: 3.3.2 |
| 6 |
Stable tag: 2.0.4 |
| 7 |
|
| 8 |
WordPress code editor with auto completion of both WordPress and PHP functions with reference, syntax highlighting, line numbers, tabbed editing, automatic backup. |
| 9 |
|
| 10 |
== Description == |
| 11 |
|
| 12 |
WPide is a WordPress code editor with the long term goal of becoming the ultimate environment to code/develop WordPress themes and plugins. You can edit any files in your wp-content, not just plugins and themes. Code completion will help you remember your WordPress/PHP commands providing function reference along the way. Edit multiple concurrent files with the tabbed editor. |
| 13 |
|
| 14 |
Please come forward (either on github or the WordPress support forum) with any bugs, annoyances or any improvements you can suggest. I'd like this plugin to be the best it can be and that's only going to happen if users chip in with their feedback. Code contributions welcome, over on Github. |
| 15 |
|
| 16 |
This plugin would not be possible without the Ajax.org Cloud9 Editor (http://ace.ajax.org/) which is the embedded code editor that powers much of the functionality. |
| 17 |
|
| 18 |
= Current Features: = |
| 19 |
|
| 20 |
* Syntax highlighting |
| 21 |
* Line numbers |
| 22 |
* Code autocomplete for WordPress and PHP functions along with function description, arguments and return value where applicable |
| 23 |
* Automatic backup of every file you edit. (one daily backup and one hourly backup of each file stored in plugins/WPide/backups/filepath) |
| 24 |
* File tree allowing you to access and edit any file in your wp-content folder (plugins, themes, uploads etc) |
| 25 |
* Create new files and directories |
| 26 |
* Highlight matching parentheses |
| 27 |
* Code folding |
| 28 |
* Auto indentation |
| 29 |
* Tabbed interface for editing multiple files (editing both plugin and theme files at the same time) |
| 30 |
* Using the WordPress filesystem API, although currently direct access is forced (edit WPide.php in the constructor to change this behaviour) ftp/ssh connections aren't setup yet, since WP will not remember a password need to work out how that will work. Maybe use modal to request password when you save but be able to click save all and save a batch with that password. Passwords defined in wp-config.php are persistent and would fix this problem but people don't generally add those details. Open to ideas here. |
| 31 |
* Image editing/drawing (requires Flash - will move over to HTML5 when there is a decent alternative) |
| 32 |
|
| 33 |
= Feature ideas and improvements: = |
| 34 |
|
| 35 |
* Improve the code autocomplete command information, providing more information on the commands, adding links through to the WordPress codex and PHP.net website for further info. |
| 36 |
* Add find and replace functionality |
| 37 |
* Create an admin panel to choose between syntax highlighting themes and turn on/off other Ajax.org Cloud9 functionality |
| 38 |
* Better automated file backup process |
| 39 |
* Templates/shortcuts for frequently used code snippets, maybe even with an interface to accept variables that could be injected into code snippet templates. |
| 40 |
* Integration with version control systems such as Git |
| 41 |
|
| 42 |
|
| 43 |
As with most plugins this one is open source. For issue tracking, further information and anyone wishing to get involved and help contribute to this project can do so over on github https://github.com/WPsites/WPide |
| 44 |
|
| 45 |
== Contributors == |
| 46 |
|
| 47 |
Simon Dunton - http://www.wpsites.co.uk |
| 48 |
Thomas Wieczorek - http://www.wieczo.net |
| 49 |
|
| 50 |
|
| 51 |
== Installation == |
| 52 |
|
| 53 |
1. Upload the WPide folder to the `/wp-content/plugins/` directory |
| 54 |
1. Activate the plugin through the 'Plugins' menu in WordPress |
| 55 |
1. Access WPide by clicking the WPide menu item in your main administration menu |
| 56 |
|
| 57 |
== Frequently Asked Questions == |
| 58 |
|
| 59 |
= Can I override the default file permissions when creating files/directories on the local filesystem = |
| 60 |
|
| 61 |
Yes you can using the below WordPress settings in wp-config.php which will effect files created with WPide and files added during the WordPress upgrade process. |
| 62 |
|
| 63 |
define('FS_CHMOD_DIR', (0755 & ~ umask())); |
| 64 |
define('FS_CHMOD_FILE', (0644 & ~ umask())); |
| 65 |
|
| 66 |
= Whenever I try to edit an image the application says that it could not load the image = |
| 67 |
Either the image contains no image data (its a new empty file) or the image is not accessible to the image editor. Your images need to be accessible to the web. i.e. if you're developing a site on your local machine behind a router/firewall your local web server could not be accessible to the web. |
| 68 |
|
| 69 |
== Screenshots == |
| 70 |
|
| 71 |
1. Editor view, showing line numbers and syntax highlighting. |
| 72 |
2. Image editor in action |
| 73 |
3. Showing auto complete, function reference and file tree. |
| 74 |
|
| 75 |
== Changelog == |
| 76 |
|
| 77 |
= 2.0.4 = |
| 78 |
* On startup the initial editor page now shows some startup info regarding file permissions to help with debugging. |
| 79 |
|
| 80 |
= 2.0.3 = |
| 81 |
* If WPide cannot access your files due to permissions then when it starts up it will give you an alert to say this. |
| 82 |
|
| 83 |
= 2.0.2 = |
| 84 |
* Image editing is now available using the SumoPaint image editor and drawing application http://www.sumopaint.com/ |
| 85 |
|
| 86 |
= 2.0.1 = |
| 87 |
* You can now create new files/folders |
| 88 |
|
| 89 |
= 2.0 = |
| 90 |
* Recreated this plugin as a dedicated WPide section/app rather than extending the built in plugin/theme editor (just incase WP remove it) |
| 91 |
* Now using the WP filesystem API (although currently restricted to local access) |
| 92 |
* More security checks on file opening and editing |
| 93 |
* Added new file tree for exploring the file system and opening files (any file in wp-content) |
| 94 |
* Massive overhaul to code autocomplete functionality with the addition of function information right in the app |
| 95 |
* Update the ajaxorg Ace Editor to the current branch |
| 96 |
* Tabbed editing |
| 97 |
|
| 98 |
= 1.0.6 = |
| 99 |
* Added link to meta section of plugin list for easy install of V2 Dev version if you have dismissed the alert. |
| 100 |
|
| 101 |
= 1.0.5 = |
| 102 |
* Added the facility to download and run the cutting edge development version of WPide from the Github repository |
| 103 |
|
| 104 |
= 1.0.4 = |
| 105 |
* Implemented JavaScript and CSS mode for better syntax highlighing and checking (Thanks to Thomas Wieczorek) |
| 106 |
* Organise and format source code |
| 107 |
|
| 108 |
= 1.0.2 = |
| 109 |
* Tidy and comment code |
| 110 |
* Added message when backup file is generated |
| 111 |
* Adjust code complete dropdown position |
| 112 |
* Improved editor responsiveness when using delete or enter keys |
| 113 |
|
| 114 |
= 1.0.1 = |
| 115 |
* Fixed "Folder name case" issue. |
| 116 |
|
| 117 |
= 1.0 = |
| 118 |
* Initial release. |
| 119 |
|
| 120 |
== DEV NOTES == |
| 121 |
|
| 122 |
Maybe some interesting things here we could implement to help with following the WordPress standard and more advanced code syntax checking |
| 123 |
|
| 124 |
http://magp.ie/2011/01/10/tidy-and-format-your-php-and-meet-wordpress-standards-on-coda-and-textwrangler/ |
| 125 |
|
| 126 |
Checkout the following WordPress plugin "WP Live CSS Editor" to work out how to do LIVE css editing. Combining a LESS compiler with live CSS editing/compile would be a dream. |
| 127 |
|
| 128 |
|
