1[[PageOutline(1-2)]] 2 3== Is Padre for Perl only? == 4 5While the main focus of Padre is to provide excellent support for both beginner and advanced Perl developers 6it is not restricted to Perl development only. 7It provides syntax highlighting to most of the languages out there and if you are missing something just ask on the mailing list or open a ticket. 8It is also planned to be integrated with [http://www.parrot.org/ Parrot] that will allow writing plug-ins in any language running on Parrot. 9 10== Why not just reuse an existing Editor? == 11 12We hope that by writing it in Perl we will make it easy for any user of Padre to contribute back to the project and/or to add plug-ins. 13 14 * vi and emacs -- while being excellent tools -- are not very beginner-friendly. 15 * Komodo costs money and is not Free/Open Source software. 16 * Eclipse is huge and you need to know Java to extend it. 17 * Various editors such as Ultra-Edit, Notepad++ etc. are Windows-only 18 19== Why does Padre use wxWidgets and not ...? == 20 21wxWidgets uses the native windowing widgets of each operating system and in theory that should be the nicest 22and most "native looking" on all operating systems. So while it has it own problems and it is not the easiest 23to write in it, it might have the best potential. 24 25== Why using Subversion when Git is so much better? == 26 27We started to use SVN as Gabor did not know Git. 28We keep it as it works well for us and a lot more people know SVN than Git. 29 30With that said if someone implements an awesome and simple-to-use 31plugin for Padre to integrate with Git that works well on both Windows 32and Linux then we can consider switching. 33 34== Why using ithreads when forks/coro is so much better? == 35 36Threads are the only Perl concurrency system that is portable and actually runs things in parallel and makes use of multiple cores. We needed something portable that does real concurrency (i.e. no cooperative multi-threading or event loop), so fork was out of the loop due to portability and POE/Coro due to cooperative multithreading. 37 38== I have trouble installing Padre. Where can I find help? == 39See [wiki:Download] and the pages linked there for installation instructions. 40If this does not bring you any further, [http://padre.perlide.org/contact.html contact us], we will see how we can help us. 41 42== I have found a bug. What do I do now? == 43Report it. Either by [http://padre.perlide.org/contact.html contacting us], or by [wiki:Tickets creating a new ticket in Trac]. 44 45== Padre lacks feature XY. What can I do about it? == 46Tell us. Either by [http://padre.perlide.org/contact.html contacting us], or by [wiki:Tickets creating a new ticket in Trac]. 47 48Or even better: Implement it yourself. Hacking Padre isn't that hard if you know some Perl. And the developer community is very open and welcoming towards new developers. 49See [wiki:Howto] and [http://padre.perlide.org/getting_involved.html Getting Involved] for more information. 50 51== How do I checkout a trunk version of padre? == 52This is described on the [wiki:Howto] page. 53 54== My Perl script expects user input from STDIN, but I cannot enter anything when executing it inside Padre. What can I do? == 55 56There is a setting in the Preferences dialog, under "Run parameters" (or under "Language Perl 5", depending on your version of Perl, called 57"Use external window for execution". 58 59If you activate that setting, you can make inputs to STDIN. 60 61See also ticket #743. 62 63== I am not getting output console when I Run a script (press F5) == 64 65There is a setting in the Preferences dialog, under "Run parameters" (or under "Language Perl 5", depending on your version of Perl, called 66"Use external window for execution". 67 68Try to check / uncheck that. 69 70 71== Can I edit remote files on an FTP server with Padre? == 72 73Yes, just use "File"->"Open ..."->"Open URL ..." and enter your file's URL. 74HTTP and HTTPS are also supported, by the way. 75 76== How can I add/modify keyboard shortcuts? == 77 78There is a keyboard shortcut editor in the menu under "Tools" -> "Key Bindings". 79 80