Hi folks,
Since a few releases I'm experiencing some not optimal way of
development which is surely caused by the long history we already have
on g-p as well as by the many people around luckily contributing to the
plugins collection: More and more plugins are going into some kind of an
orphaned state. There is some maintainer available but not really
responsive e.g. due to workload at reallife etc. However, at the end
some of the plugins are still compiling but not effectively working any
more with recent Geany version or its documentation is really outdated
-- when I was preparing the commits for waf removing I have seen plugins
still depending on Geany 0.16 ... I'm pretty sure, if they would, they
would compile any more ;)
Also the documentation of each plugin are differing in style, size and
quality much. (and I have to include the plugins I'm maintaining here
100% too). At github we already got a bunch of bug reports and pull
requests for plugins waiting for any response. Also there is a long
backlog at sf I've been told.
This is what I was thinking of to improve the situation (the overall
experience for our users)
1) Deactivating all plugins / out comment all plugins from MAINTAINERS
2) Cleaning off NEWS, Changelog etc. from individual plugin folders
3) Moving documentation of all plugins into a structure like
doc/<pluginname> to get a real fitting (online) manual. At this
point update documentation and bring them to some markup stil (Rest?
md? Docbook? I don't care at this point)
4) Moving all plugins into a subfolder like plugins/<pluginname> to
clean up / of g-p a little
5) Reactivating plugins by a pull request of the actual (old|new)
maintainer maybe doing steps 2-4 and comment back in the plugin in
MAINTAINERS. Also I would be happy if at this point po/POTFILES.in
is reviewed etc.
6) Release a cleaned up g-p
7) Post 1.27 puring not update plugins from src tree
What do you think about this idea? I would combine this with some
release goals like complete support of Geany Gtk3 stack (if applicable).
Timeschedule: 1-4 until Xmas 2015, 5-6 until March.
Cheers,
Frank
Hi, All,
I see that the Scope plugin is marked in autotools as gtk+2 only,
and rightly so. At some point, gtk+3 broke GtkTextView: instead
of a reasonable default size, a view without text is 0 pixels
high (actually 1, gtk+ does not support zero). One of these views
is critical for the Scope UI. Interestingly, even after typing
some text in it (I managed to do that somehow), the view remains
1 pixel high. :)
I can find some workaround for this, though there doesn't seem to
be any good ones [1]. And create a PR to fix the insane statusbar
padding [2]. And find some non-tabletish theme, and fix it for
Windows Medium fonts [3], and...
Enough. If the gtk+3 developers want to target the mobile market
or something, so be it. I'm switching to another editor. It has
disadvantages, but is stable, and gets the job done.
It'll be nice if somebody makes the vte and headers checks in
scope.m4 as unix-only (there's already a "case" for the non-unix
platforms). Personally I'll dump a TODO list for the plugin, and
mark it as "Orphaned", along with geanyinsertnum and
geanyextrasel.
Please, spare me any reproaches, I feel unpleasant as it is.
*** I wish Geany, and all of you, the best of luck. ***
--
[1] For example, set height request 80, as somebody did for the
Project Description field, though using a fixed height is against
everything gtk+. That Description is broken for me BTW, neither
the arrows nor Enter scroll it, and the cursor happily disappears
below the lower border after entering a few lines. YMMV.
Another approach is to put some text in the textview, prefferably
with new lines, but that worked for me with mixed success.
[2] "gtk 3.16 statusbar size under Win~1" in the maining list.
[3] That doesn't appear as easy as setting a smaller default font
for all views, and the gtk+3 programs can't be marked as "DPI
unaware" by Windows 7 "Troubleshooting" feature.
--
E-gards: Jimmy
All the Gmane searchable archives are unavailable.
Does anyone know if this is just a temporary glitch, or do we need to
consider other arrangements?
Cheers
Lex
Hi,
I made a script and to generate a Geany installer. I had to make a few
patches to Geany and it's probably not exactly stable/release-worthy,
but it seems to work OK here, if not a bit slow.
I tested the 32 and 64-bit installers on Windows 10 and also the 32-bit
one on Windows Vista.
Branch is here:
https://github.com/codebrainz/geany/tree/win32-installer
The script is in the branch, here:
https://github.com/codebrainz/geany/blob/win32-installer/scripts/win32-inst…
With a MSYS2 install and desired toolchain installed in it, after
possibly editing the top of `scripts/win32-installer-msys2.sh` for a
couple paths, run from appropriate 32 or 64-bit msys2 shell in a
directory where the build cruft can go. After too many minutes it will
output installer .exe in the current dir. Pass `i686` or `x86_64` as
argument depending on the output architecture (default is i686). See top
of the `win32-installer-msys2.sh` script for more details.
Please excuse my lack of Bash scripting skills.
Cheers,
Matthew Brush
Geany Dev Team:
I will create a GTK3-based application that creates Debian (*.deb)
files. Once it is done, I will upload the src to my website
(DCJTech.info), and then, I will share the link to the application.
Thus, we can more easily generate *.deb files for Geany.
By the way, sometime this week or next week, I will add the Squirrel
filetype to the wiki.
--
Thanks,
Devyn Collier Johnson
DevynCJohnson(a)Gmail.com
Who is gonna make the PR (for milestone 1.27, after a whole 1.26
release deprecated) ready to remove Waf, not forgetting the
documentation, README, INSTALL etc and the website (hint Enrico ;)
Cheers
Lex
We are happy to announce a new release of Geany!
For a comprehensive list of changes please see:
http://www.geany.org/Documentation/ReleaseNotes
Some highlights:
* New plugin API (Thomas Martitz).
* Add support for "proxy" plugins (Thomas Martitz).
* Fix spurious "source file has been modified" messages (Jiří Techet).
* Update Scintilla to version 3.6.1.
* Keeping undo history when reloading files is now enabled by default.
* Restore modern design of native file dialogs under Windows.
* Update translations: de, el, es, fr, hu, id, kk, pt, sk, sv, ru.
We want to thank all developers, translators and everyone who
contributed to this release with patches, feedback, bug reports and so
on. Thank you!
As usual, all downloads can be found on
http://www.geany.org/Download/Releases.
- Colomban
Hi,
We are happy to announce a new version of the combined Geany-Plugins
release -- right after Geany 1.26 has been released.
There have been a lot of changes, but here are some of the most
prominent or noteworthy ones:
* Add GTK3 support to Addons and GeanyVC
* Addons: new Copy Path feature
* Addons: Fix bookmark list when the document changes
* Spellcheck: Add support for showing suggestions directly in the
editor menu
* Scope: Improve GDB communication
* Update translations: de, fr, nl, pt
* New translation: kk
A more complete list of changes can be found in the
https://raw.githubusercontent.com/geany/geany-plugins/1.26.0/NEWS file
Thanks to all people involved and to you for using it ;)
As usual, you can find source tarballs and Windows installer for the new
release on http://plugins.geany.org/downloads.html.
Cheers,
Frank