I18n

i18n@lists.geany.org

301 discussions

Titlebar not visible
by Broadus Jones 04 Jun '12

04 Jun '12

Hi. I am unable to view the title bar in Geany. I am running Ubuntu 11.10 in Gnome classic mode. I am able to see the title bar in the other running programs. When i press Alt-Spacebar, a menu appears with on Minimize, (Maximize disabled), (Move disabled), (Resize disabled), Move Titlebar Onscreen, Always on top,...Close. When i choose "Move Titlebar Onscreen", either with the mouse click or the shortcut key (s), no change occurs. I cannot resize or move the Geany window either. Thanks for any help you can provide. The debug messages from Geany are: 09:56:00: Geany INFO : Geany 0.20, en_US.UTF-8 09:56:00: Geany INFO : GTK 2.24.6, GLib 2.30.0, GIO 09:56:00: Geany INFO : System data dir: /usr/share/geany 09:56:00: Geany INFO : User config dir: /home/bjones/.config/geany 09:56:00: Geany INFO : Added filetype Genie (51). 09:56:00: Geany INFO : Loaded: /usr/lib/geany/classbuilder.so (Class Builder) 09:56:00: Geany INFO : Loaded: /usr/lib/geany/export.so (Export) 09:56:01: Geany INFO : Loaded: /usr/lib/geany/filebrowser.so (File Browser) 09:56:01: Geany INFO : Loaded: /usr/lib/geany/htmlchars.so (HTML Characters) 09:56:01: Geany INFO : Loaded: /usr/lib/geany/saveactions.so (Save Actions) 09:56:01: Geany INFO : Loaded: /usr/lib/geany/splitwindow.so (Split Window) 09:56:01: Geany INFO : /home/bjones/Documents/Clearing/Fee_Package/set_up_avs_auth_20120530.sql : SQL (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/MAS/all_mas_txn_count_sum_file_v13.tcl : Tcl (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/MAS/all_mas_count_sum_file_v13.sh : Sh (UTF-8) 09:56:01: Geany INFO : /home/bjones/Documents/Clearing/End_of_month/2012/05-May/Sample Statements.eml : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/Documents/Clearing/End_of_month/2012/05-May/Sample_Statements_20120531.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/STATEMENTS/INST_447474/Merchant_statement.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/STATEMENTS/INST_447474/Merchant_statement-112.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/STATEMENTS/INST_447474/Merchant_statement-113.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/STATEMENTS/INST_447474/Merchant_statement-IPPay.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/projects/filemgr_trunk/STATEMENTS/INST_447474/Merchant_statement-JetPay.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/Documents/Clearing/On_Call/20120118_clearing_rejects.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/Documents/Clearing/On_Call/20120601_mas_suspends_ach_train.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/Desktop/TEMP/minumum_fee_charged_201205.txt : None (UTF-8) 09:56:01: Geany INFO : /home/bjones/Documents/Clearing/On_Call/20120602_mas_commands_stopped.txt : None (UTF-8) 09:56:02: LIBDBUSMENU-GTK CRITICAL : watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed -- Broadus

3 3

Re: [Geany-i18n] String freeze for Geany 1.22
by Enrico Tröger 04 Jun '12

04 Jun '12

On 03/06/12 18:22, gymka wrote: > 2012.06.03 19:13, Enrico Tröger rašė: >> On 03/06/12 18:02, gymka wrote: >>> 2012.06.03 18:48, Enrico Tröger rašė: >>>> Hey, >>> >>> >>>> I'm not sure about the search string problem. >>> >>>>> 2. patch to make strings "pos:" and "style:" translatable >>> >>>> But those two strings are not translatable on purpose. They >>>> are only used when Geany was built with debug information >>>> enabled and are not meant to be end-user visible. >>> >>> >>> >>> 1. i builded geany with default options, i didn't enabled >>> anything, so by default everybody see those strings. > >> I guess you built Geany from GIT? If so, debug support is enabled >> automatically. But it is not when built from a normal release >> tarball. > > >>> 2. maybe i changed wrong line, look to geany bottom line there >>> is "line:x/x" col:x sel:x INS TAB mode: Unix(LF) encoding: UTF-8 >>> filetype:x scope:unknwn pos:x style:x" all these are >>> translatable except "pos" and "style". so either by default >>> disable that line or make all strings translatable. it looks bad >>> then 7 strings is translated and two strings are still in >>> english. > >> As said, this is not meant for normal users. Frank already applied >> your patch. Either he keeps it and all translators have to live >> with translating two more strings for no real benefit or he reverts >> it and saves all the others translaters the trouble. Those strings >> exists for years already and never were translatable, this is >> nothing new. > > > peoples for thousands of years lived in caves, but one day someone > decided to build house... if it always was so, not means that is good. > count bugs in software which are not reported... they exists, > everybody sees them but noone takes theirs precious time and reports it... > > for the record: in archlinux repository, geany builded same as i > builded from git, so atleast asrchlinux users sees that by default. I just built Geany on ArchLinux from the official PKGBUILD and the Pos and Style strings are not included in the statusbar. This is obvious, because Geany is not built with debug support by the ArchLinux PKGBUILD. Sorry, either you are talking about the GIT Geany ArchLinux package (which is built with debug support because it is the GIT version) or you made something wrong :(. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

3 3

Geany Newsletter Issue #5
by Frank Lanitz 28 May '12

28 May '12

Geany Newsletter #5 ------------------- 1 About Geany 2 New translations and updates 3 Wiki available 4 C++ plugins supported 5 Plugins 5.1 New Plugins 5.1.1 GeanyPyflakes 5.1.2 GeniusPaste 5.2 GeanyPG 6 Geany local 7 Geany Packages for Fedora 8 About this newsletter 1 About Geany ============= Geany is a small and lightweight Integrated Development Environment. It was developed to provide a small and fast IDE, which has only a few dependencies from other packages. Another goal was to be as independent as possible from a special Desktop Environment like KDE or GNOME - Geany only requires the GTK2 runtime libraries. More information about Geany can be found at `geany.org <http://www.geany.org/>`_. 2 New translations and updates ============================== Since our last newsletter a number of translations has been updated or newly added to Geany. New translations are: * Arabian * Indonesian * Lithuanian * Mongolian (back in 2011) But also translations like German, Kazakh, Hungarian, Italian, Traditional Chinese and Swedish translations have been updated during the last roughly four month. 3 Wiki available ================ We set up a wiki for additional documentation and resources related to Geany at http://wiki.geany.org. Anyone can contribute to the wiki simply by registering and then logging in. In the wiki you can find configuration snippets and tips, snippets for various programming languages and many additional tags files to enhance Geany's autocompletion features. Everybody is welcome to add additional useful content to the wiki. 4 C++ plugins supported ======================= Geany's public plugin API headers have been updated to support inclusion into C++ code. Most of the changes involve adding `extern "C" {...}` blocks around the public headers' code (by way of GLIB's `G_BEGIN_DECLS` and `G_END_DECLS` macros) to make them easier to include, so the C++ code doesn't need to do this. You can now write plugins in C++ and they will be loadable by Geany at run-time. Of course using Geany's API will still involve using C in your code, but the rest of your plugin can use whatever C++ features you want. You can even use gtkmm [1] in your plugin if you want. Any of the symbols Geany looks up at run-time must not have their names mangled by the compiler. To avoid this, put that code inside an `extern "C"` block. Here's an example of Geany's Hello World plugin from the Plugin HowTo [2] ported to C++:: #include <geanyplugin.h> class HelloWorld { private: gchar *hello_message; GtkWidget *main_menu_item; public: HelloWorld(const gchar *message); ~HelloWorld(); void SayHelloWorld(); }; static HelloWorld *hello; extern "C" { GeanyPlugin *geany_plugin; GeanyData *geany_data; GeanyFunctions *geany_functions; PLUGIN_VERSION_CHECK(211) PLUGIN_SET_INFO("HelloWorld C++", "Just another tool to say hello world, this time in C++", "1.0", "John Doe <john.doe(a)example.org>"); void plugin_init(GeanyData *data) { hello = new HelloWorld("Hello C++ World"); } void plugin_cleanup(void) { delete hello; } static void on_menu_item_clicked(GtkMenuItem *item, gpointer user_data) { hello->SayHelloWorld(); } } HelloWorld::HelloWorld(const gchar *message) { hello_message = g_strdup(message); main_menu_item = gtk_menu_item_new_with_mnemonic("Hello World"); gtk_widget_show(main_menu_item); gtk_container_add(GTK_CONTAINER(geany->main_widgets->tools_menu), main_menu_item); g_signal_connect(main_menu_item, "activate", G_CALLBACK(on_menu_item_clicked), NULL); } HelloWorld::~HelloWorld() { g_free(hello_message); gtk_widget_destroy(main_menu_item); } void HelloWorld::SayHelloWorld() { dialogs_show_msgbox(GTK_MESSAGE_INFO, "%s", hello_message); } It's important to note that the dynamic library loading mechanism that loads plugins is C functionality and does not know about C++ constructors. This means that global and static objects in the plugin will *not* have their constructors called when the plugin is loaded. Use dynamically created objects as show in the above example. These changes will be available in the next Geany release but you can start using them right away in your C++ plugins if you Build Geany From Git [3]. 1. http://developer.gnome.org/gtkmm-tutorial/2.24/sec-basics-gobj-and-wrap.htm… 2. http://www.geany.org/manual/reference/howto.html 3. http://www.geany.org/Download/Git 5 Plugins ========= Notes from the plugin section. 5.1 New Plugins *************** 5.1.1 GeanyPyflakes ################### Pyflakes is a command line tool that statically analyzes python program and detects two kinds of errors: unused imports and undefined symbols. geany-pyflakes runs pyflakes in the background and parses its output. Afterwards puts markers on lines with errors and adds the output to the panel at the bottom of editor (the one with console, todo, etc.). Geany-pyflakes is available at its project pages at http://code.google.com/p/geany-pyflakes/ Another way to check your Python code is described inside the wiki at http://wiki.geany.org/howtos/check_python_code 5.1.2 GeniusPaste ################# GeniusPaste is a plugin which is adding the possibility to paste your code from Geany into different pastebins. It supports this services: * codepad.org * pastebin.com * pastebin.geany.org * dpaste.de * sprunge.us During the paste process GeniusPaste detects automatically the syntax of your code and paste it with syntax highlighting enabled. Once this is done it is also able to redirect you to the pasted code opening a new browser tab. 5.2 GeanyPG *********** GeanyPG is a plugin that allows the user to encrypt, decrypt text and verify signatures with GnuPG from inside Geany. It's created by Hans Alves and is part of the geany-plugins project. After the plugin has been installed successfully, it can be loaded from inside Geany's plugin manager which will add a new menu item into the Tools menu offering functions of the plugin. To decrypt or encrypt, just select the interesting parts and choose the function you wish -- If none text has been selected, the whole document will be processed. In case you like to verify a signature obviously you will have to select the whole block. When encrypting a message you can choose to sign at the same time. If a passphrase is needed, the GPGME library will decide how the user is prompted. Usually this will use gpg-agent. If gpg-agent is disabled, pinentry with one of its frontends will be used. 6 Geany local ============= 6.1 Geany at Chemnitzer Linuxtage 2012 (March 17th, 18th) ********************************************************* As last year, Geany had a booth a Chemnitzer Linuxtage 2012 in German city Chemnitz. Our booth was again located next to the guys of Xfce as well as next (that was different to last year) to 2 lecture rooms. Even though the event wasn't as much crowded as last year, a lot of people were passing by asking some question or just saying hello. So Enrico and Frank had a lot of questions to answer and a lot of feedback to respond to. 7 Geany Packages for Fedora =========================== There are new packages unofficially available for Fedora. One is containing the Geany Themes Matthew maintains at GitHub [1], the other one provides the tags files listed in the Geany Wiki [2]. The packages are not yet in Fedoras official repositories but available at Dominic's Fedora People space [3]. Note the geany-themes package is intended to work with current Git versions of Geany only. A x86_64 package from the current Git master as well as an SRPM for rebuilding is also available at [3]. The geany-tags package is split into subpackages containing the tags for each programming language. Currently these are: geany-tags-c, geany-tags-php and geany-tags-python. They can be installed independently from each other, of course. Contact Dominic if you have suggestions for improvements. 1. https://github.com/codebrainz/geany-themes 2. http://wiki.geany.org/tags/start 3. http://dmaphy.fedorapeople.org/ 8 About this newsletter ======================= This newsletter has been created in cooperation by people from Geany's international community. Contributors to this newsletter and the infrastructure behind it, ordered by alphabet: Dominic Hopf Enrico Tröger Frank Lanitz Lex Trotman Matthew Brush

1 0

Hello Everyone
by Pradeep 26 May '12

26 May '12

Hi all, I am Pradeep from Chennai, INDIA. I am interested in opensource projects (editors especially). I have contributed couple of plugins to Mozilla'a skywriter ( a browser based editor). I really like to contribute few plugins to GEANY. I was searching for the dev env set up for Geany. But couldn't find any doc on the same. Can someone give me some pointer to set up my development environment? Thanks, Pradeep.

2 1

Lithuanian translation
by gymka 26 May '12

26 May '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, updated Lithuanian geany translation. - -- gymka GPG ID: 21C70548 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAEBAgAGBQJPwGvnAAoJEAVeyH4hxwVIDYIH+wRLMY5CpjzEuws6Ee/ene6i IK4Eft2sZgRPIoe69ZABxsbTI55CA20JOU8PdMTmVj+a6Ymr/gquaVE1cQ81drz2 8tppPyJboTfkRDuKWUWOjmQCIg89+7XmIQVmRibea8CxT/wtnbFnmL/mvTHcOF8a vbmBy939KJIIW2MrVIZdCdb9N+9oLl7wW9WhV6EWxYZd+Rxge4TDKQiCASMioTW/ wAbdn7O6sOvSJpiqQ0UpYS96dic7TKvB2j8Bp7LWnRlmTxAL8vNO4qzq/ZND6jy/ 5UEaTZnPBg+wpIet6ZUZAYhv+jxea08lsXEB+QuTi9x8rSOYx1GuUucBSGgIFnQ= =TPew -----END PGP SIGNATURE-----

2 1

Kazakh translation 33.55% --> 86%
by Baurzhan Muftakhidinov 21 Feb '12

21 Feb '12

Hello guys! Please commit the updated translation for Kazakh language, which is attached. Thanks,

2 1

Geany Translation Bug in Chinese(Traditional)
by BlueT - Matthew Lien - 練喆明 06 Feb '12

06 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, There's a translation bug in zh_TW. The word "Initial:" in Template preferences should be "開發人員縮寫：" (which means "abbreviated from developer's name") instead of "初始人員：" (the person who initialed this program). I had also corrected a few other translation bugs and completed those few untranslated items. I'm a Geany user for a while but newly here. Please correct me if I made any mistake, thanks a lot! Best wishes, BlueT - -- / Just another [ Perl | FOSS | Security ] Hacker. / / BlueT = Matthew Lien = 練喆明 / / http://BlueT.org / / GPG: 4A293CBD / -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8u6TEACgkQvRNvgEopPL1hRgCePte4eazoWgU73gtB1Ig4N3zB CPMAn3Fx28gE70N3mGCWH5z1/UX6ZL1v =xMep -----END PGP SIGNATURE-----

2 2

Wiki for Geany!
by Enrico Tröger 19 Jan '12

19 Jan '12

Hi all, we set up a wiki for additional documentation and resources related to Geany at http://wiki.geany.org. Anyone can contribute to the wiki simply by registering and then logging in. In the wiki you can find configuration snippets and tips, snippets for various programming languages and many additional tags files to enhance Geany's autocompletion features. Everybody is welcome to add additional useful content to the wiki. Happy contributing, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

1 0

Fwd: Problems running a custom build command
by Lucas Vieites 05 Dec '11

05 Dec '11

Hi, I'm posting this to the "i18n" list because it just bounced off of the "devel" list (I just remembered I insubscribed some time ago), also because I know you devs are around here too ;-) I'm running Geany 0.21 on Windows Vista and I've configured the following build command for html files: C:\software\tidy.exe -i %d\%f (tidy.exe is a Windows version of the Linux "tidy" command that cleans up and validates html files) This command works perfectly in a command line window and I can even redirect the output to another file (for example: C:\software\tidy.exe -i c:\tmp\mytestfile.html > c:\tmp\tidyfile.html) But when I run it from inside Geany, as a custom build command, it only works with small files, crashing always when the output in the compiler window reaches 4069 bytes (4KB). Is this a known "bug" or is this a "feature". Is there any workaround? Also, when I use the ">" character to redirect the output to a new file, Geany complains that it cannot find a file named ">". For more information, this works perfectly on my linux box. Thanks in advance, -- Lucas Vieites lucasvieites(a)gmail.com http://blog.codexion.com

1 0

Geany Newsletter Issue #4
by Frank Lanitz 04 Dec '11

04 Dec '11

Geany Newsletter #4 ------------------- About Geany =========== Geany is a small and lightweight Integrated Development Environment. It was developed to provide a small and fast IDE, which has only a few dependencies from other packages. Another goal was to be as independent as possible from a special Desktop Environment like KDE or GNOME - Geany only requires the GTK2 runtime libraries. More information about Geany can be found at `geany.org <http://www.geany.org/>`_. Table of contents ================= 1 About Geany 2 Geany 0.21 has been released 3 Geany-Plugins 0.21 has been released 3.1 New Plugins 3.2 Updates and Bugfixes 3.2.1 General 3.2.2 Addons 3.2.3 GeanyLaTeX 3.2.4 GeanySendMail 3.2.5 Spell Check Plugin 3.2.6 Updatechecker 3.2.7 WebHelper 3.2.8 Internationalisation 4 Geany-Plugins 0.21.1 has been released 5 Geany moved to Git 6 Change of project leadership 7 Geany local 7.1 Geany at OpenRheinRuhr 2011 8 Let us introduce you 8.1 Plugin Focus 8.1.1 Split Window 8.2 Feature Focus 8.2.1 Colour Schemes 9 People behind Geany -- Interview 9.1 Enrico Tröger 10 About this newsletter Geany 0.21 has been released ============================ After about 6 months of development, on 2 October 2011 Geany 0.21 was been released. There have been a lot of changes, so only the highlights are listed below: * Add support for real-time symbol parsing. * Fix loading of non-UTF-8 templates. * Update Scintilla to version 2.25. * Add Scala custom filetype (werg). * Add Cython custom filetype (Matthew Brush). * Add support for separate single and multiline comments. * Add support for filetype-specific indentation settings. * Add filetype Cobol (Seth Keiper). * SplitWindow plugin now works on Windows too. * Add translations: fa. * Update translations: ca, cs, de, en_GB, es, fi, fr, gl, it, ja, nl, pt, pt_BR, sl, sv, tr, vi, zh_CN, zh_TW. A more complete list can be found on http://www.geany.org/Documentation/ReleaseNotes Source tarballs as well as Windows binaries can be found as always on http://download.geany.org. Geany-Plugins 0.21 has been released ==================================== On 23 October 2011, about three weeks after Geany 0.21, Geany-Plugins in its final version has been released. As seen in former newsletters it has been a quite active time on plugin development, so we are trying to give you an overview on one hand as well as digging into some of the bigger changes that have happened. New Plugins ^^^^^^^^^^^ Most of the new plugins have been already described in one of the previous editions of this newsletter. However, so only a short overview is provided here. * **Debugger**: A plugin to integrate debuggers like GDB. This is replacing GeanyGDB in many places. * **Devhelp**: Integration for GNOME's Devhelp and google code search. * **GeanyPG**: Encryption, decryption, signing etc. from within Geany via GnuPG. * **GeanyMacro**: A plugin to record and apply macros. * **GeanyNumberedBookmarks**: A plugin to store bookmarks to files and access them easily via a number. * **Tableconvert**: A plugin to convert lists into tables. * **XMLSnippets**: Helps on inserting (common) XML-snippets. Updates and Bugfixes ^^^^^^^^^^^^^^^^^^^^ General ####### Significant rework has been done on the Autotools build system as well as some maintenance work on the Waf-build system. Addons ###### * DocList addon: Add preference to define the order of the documents in the list (#3204573) * Tasks addon: Activate and update the task list when the Tasks addon is enabled GeanyLaTeX ########## * Moved LaTeX menu to a separate menu inside Geany main menu * Added a feature to autocapitalise letters on typing at the beginning of a sentence * Added a way to put an icon for LaTeX wizard into Geany's main toolbar * Added a dialog for inserting BibTeX references based on available \*.bib-files * Upgrade plugin API to version 199 * Ensure not to insert {} after \^ and \_ * Adding a keystroke to toggle inserting {} after ^ and _ * Fixed an issue with wrong inserted formatting using a keybinding * Small update to enable i18n also on Geany >= 0.21 * Various bugfixes and memory leak fixes. GeanySendMail ############# * Some minor cleaning up of code * Fix for an issue with replacing of command string when %r was not used * Don't double free a variable which might end up in a segmentation fault when using plugin function more than once. * Small update to enable i18n also on Geany >= 0.21 Spell Check Plugin ################## * Reduce artifacts on partially checked words * Improve \`Check as you type' feature, making it more reliable Updatechecker ############# * Fix an issue with init threads for older GTK/glib versions by updating to Geany API version 203. * Small update to enable i18n also on Geany >= 0.21 * Fix a typo inside Waf-build system WebHelper ######### * Fix creation of configuration directory in some cases * Fix missing update of navigation buttons on anchor links * Fix thread initialization problem * Fix some issues with keybindings on secondary windows * Add a keybinding to show/hide web view's window (bug #3156262) * Allow for better configuration of secondary windows Internationalisation #################### * Updated translations: de, pt, ru, tr Geany-Plugins 0.21.1 has been released ====================================== Shortly after the major release of Geany-Plugins 0.21, an issue with the build system was found which blocked installation of source tarballs using the Waf-build system. This has been fixed inside a minor source release. The Windows binary release isn't affected by this issue. Geany moved to Git ================== After a long discussion on the mailing list Geany finally moved to Git as the main version control system. The goal is to be more flexible on including patchsets from non-core-developers as well as making use of a number of other features of Git. The new home of the Git repository is http://github.com where you can access Geany's sources at https://github.com/geany/geany During this switch, sources of other Geany-related resources have been moved to GitHub as well and can be found on the overview page at https://github.com/geany Change of project leadership ============================ If you have been using Geany for a while and read the announcement of Geany 0.21's release, you might have noticed something important. The leadership of the Geany project has changed from Enrico Tröger to Colomban Wendling, a current member of the development team. Enrico's priorities changed so he decided it would be best if someone else took on the leadership role. During Enrico's time as leader, Geany has continued to gain in popularity and improve, whilst staying true to its original design goals. Thank you, Enrico, for all that you have done, and thanks for taking over Colomban. Geany local =========== Geany at OpenRheinRuhr 2011 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Together with the guys of Xfce, Geany was presented with another booth at the annual OpenRheinRuhr at November, 11th and 12th in Oberhausen, Germany -- A convention about all topics around Linux, BSD and free software in general. The booth was again well visited and people came not only to ask for help, but also just for having a little chat with Enrico and Frank and discuss about Geany releated topics. Let us introduce you... ======================= This section is intended to introduce particular plugins or features on a regular basis. Plugin Focus ^^^^^^^^^^^^ Split Window ############ The Split Window plugin provides a feature which is so useful you'll never want to be without it. When enabled, choose Tools > Split Window > Side by side | Top and bottom from the main menu and the active window is split into two editing panes. Each pane can be navigated independently of the other, complete with its own scrollbar. In each window you can edit separate parts of the same file, with each pane updated instantly with the changes made in the other. When you want to return to "normal" view, choose Tools > Split Window > Unsplit from the main menu. It's not possible to again split the active window, only unsplit. The plugin was intended to allow you to work on the *same* file but thanks to a "hidden" feature you can work on two different files loaded in the split view. If you open a file while in split window mode, it's loaded in the inactive pane. You can then switch between the split view of the same file or the different files via the file tabs (under the menu bar) as normal. Note that it's not possible to change the file shown in the right-hand pane when Split Window is active. Feature Focus ^^^^^^^^^^^^^ Colour Schemes ################ Introduction ++++++++++++ Geany supports colour schemes which allow you to change the colours applied to various code elements. Two colour schemes are provided with Geany: Default and Alternate but many more are available (see below). To change the colour scheme, select from the menu View > Editor > Colour Schemes > PREFERRED_COLOUR_SCHEME. The colour scheme change is immediate but the list of available schemes is only loaded when Geany starts. Adding Colour Schemes +++++++++++++++++++++ More colour schemes are listed on the Geany Add-ons web page. For the individual schemes, follow the instructions given by their authors. One of the biggest set of schemes was created by codebrainz. The collection is listed on the add-ons page but is hosted at https://github.com/codebrainz/geany-themes Follow the installation instructions given on the page, then restart Geany and all schemes will then be listed in the Colour Schemes menu. How Colour Schemes Work +++++++++++++++++++++++ Geany's colour schemes' format has changed over time, so there's a "legacy" format and the current, preferred format. Schemes in the different formats can be mixed but the current format is easier to maintain and modify. In this issue the focus is on the new format but if readers want it, the legacy format could also be featured in a future newsletter. Current colour scheme format ++++++++++++++++++++++++++++ The current colour scheme format works by first defining the colours to be applied to a file type's elements. This is an extract from a colour scheme named "Oblivion2": default=0xffffff;0x2e3436;false;false tag=0x729fcf;0x2e3436;true;false tag_unknown=0xffffff;0x8C0101;true;false File types and their elements are defined in a file named filetypes.<FILETYPE>: e.g. filetypes.xml, filetypes.html. All filetype files are stored in the 'filedef' directory in Geany's personal data directory. This is an extract from the file type file for HTML: [styling] # Edit these in the colorscheme .conf file instead html_default=default html_tag=tag html_tagunknown=tag_unknown When Geany applies syntax highlighting to a file which matches a filetype, it matches the element (defined in the filetype's file) with the matching colour (defined in the colour scheme's file). The advantage of this scheme over the legacy version is that modifying a colour scheme for all filetypes requires changes to just one file. People behind Geany -- Interview ================================= This is the second in a series of interviews with Geany's contributors: core developers, plugin developers, translators, wiki maintainers and any other job we can think of. The purpose of the interviews is to get to know each of these people a little better: their hopes, dreams, plans and favourite Geany plugin. Enrico Tröger ^^^^^^^^^^^^^ As is mentioned above, Enrico Tröger recently stepped down as leader of the Geany project. In this interview he talks about his history with the project. *What motivates you to develop or contribute to FLOSS projects?* There are different reasons. Most often it is that I want to improve existing software by fixing bugs, adding features I'd like to use and so on. So this is a rather pragmatic reason. Nevertheless, I believe in Free Software and this is another reason why I contribute to Free Software. Free Software allows people to read and modify the source code to their needs, so in theory everyone can make the software or change it to his/her needs. Based on my experience, most people push back their changes and so the developers can include them if appropriate. This is only one of the advantages of Free Software. I doubt this would be possible with paid software projects, at least not as long as they are not free. *How did you become Geany's project leader?* This was much simpler than you might imagine: I created the project :). *What is involved in being Geany's project leader?* Many different things. It all starts with knowing the project, knowing the people involved and ideally knowing the code base :). I think the project leader should coordinate the development and communicate with the community, making the project a project and not just a bunch of lines of code. Also, at least in the Geany case in the past, the project leader makes the releases though this is not necessarily a project leader task. Users, package maintainers and other external people often contact the project leader directly via mail or on IRC to say 'thank you', ask questions about Geany or to discuss project related topics. So this is another task for the project leader. And certainly there are many other aspects which I forgot to list. *What goals did you have when you started as project leader? Did you achieve those goals?* As I didn't explicitly start as project leader but instead just started the project, I didn't have any specific goals to achieve as project leader however I did have goals to achieve with Geany as project. These goals mostly were to create an editor which fits my needs so that I can use it to write code and other text documents without thinking about the editor, how it behaves, why it is so slow or doesn't do what I want. As you see, these were quite personal goals. In the meantime, as those goals basically were achieved with Geany 0.1, the goals changed to be more general: a light and fast editor with basic features of an IDE, without unnecessary dependencies to other libraries yet with useful features. Oh, and we achieved these goals as well though that doesn't mean Geany can't get better anymore. There is always room for improvements and new useful features. *What were some of the highlights of your time as project leader?* Hard to name particular highlights. One great thing which kept from the beginning to now is to receive mails from users who just say 'thank you, Geany is great program'. This is always great to read and always increases motivation to continue working on Geany (in whatever way). I didn't experience anything like this before and would have never expected it. But it's really nice. Maybe another highlight worth mentioning is the many things I learned during time working on Geany. This includes learning how other people use Geany or certain features of Geany, to work with the community and to read other people's code and learn from it. *Are there particular improvements/change/features of which you're proud?* The community. Ok, the community is not an improvement, change or feature :). But this is what Geany makes Geany. Without the many users and contributors, Geany would not be as cool and as stable and as feature-rich as it is now. Thank you all for using and improving Geany, keep up! *How does a FLOSS project balance welcoming contributions with keeping within the project's original goals and scope? In other words, avoid scope creep?* In Geany's case, luckily there were not much conflicts in accepting new features and the overall goal to keep fast and lightweight. However, I think a few times we had to deny a feature request for such reasons or because it the requested feature didn't fit into Geany. This went much better since Nick introduced the plugin interface so that features which don't fit into Geany's core, can be easily implemented as a plugin. Nevertheless, denying a feature request, especially when it was obvious that it would actually help the user who requested it but still doesn't fit into Geany, was hard for me. It's like "I decide that you will not get this functionality". Not a nice job. As said, luckily this didn't happen so often. *Do you have any hopes or dreams for Geany's future?* Of course: Geany should stay on its road it has been all the time. This is, keeping fast and lightweight while offering many useful features to the user. Moreover, I really hope and wish, the current fast and intense development in the community keeps going so that Geany will evolve further and get even better than it is already :). About this newsletter ===================== This newsletter has been created in cooperation by people from Geany's international community. Contributors to this newsletter and the infrastructure behind it, ordered by alphabet: * Colomban Wendling * Enrico Tröger * Frank Lanitz * Lex Trotman * Russell Dickenson

1 0

← Newer
1
...
16
17
18
19
20
21
22
...
31
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

I18n