Devel October 2011

devel@lists.geany.org

24 participants
65 discussions

Geany Plugins SVN Commit URLs
by Matthew Brush 05 Nov '11

05 Nov '11

Hi, I haven't heard too much about the Git conversion of Geany Plugins, but I wanted to offer a suggestion that might improve the commit messages compared to Geany's. In the Geany's Git repository there's links back to the SVN repository in the commit messages (the links are broken BTW). I was wondering if it would be better to have these links point to a place we have more control over, for example using a Geany commit, instead of this in the commit message: git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@5970 ea778897-0a13-0410-b9d1-a72fbfd435f5 We could have something like this: git-svn-id: [ea778897-0a13-0410-b9d1-a72fbfd435f5](http://svn.geany.org/svnroot/geany/tr… That way we could make the links work and be able to move the old SVN repository without breaking all the links in the commit message. I guess we'd need a little redirect script or something on geany.org. Note also the use of Markdown link syntax, which might render better on Github (not sure). I guess it's too late to do this for Geany's Git repository, but we could maybe consider something like this for Geany Plugins if the software can support it? Just an idea. Cheers, Matthew Brush

6 15

Geany problems with unknown encodings names
by Lex Trotman 04 Nov '11

04 Nov '11

Dear Encoding specialist (or Colomban by default :) The thread [1] has exposed a problem with the way Geany handles encodings that it gets from the extraction regexes and from the locale. The reference thread shows that Geany gets an encoding CP1252 from the locale, this is fine for reading the file since iconv and therefore g_convert recognises it and loads it fine. Places where Geany just uses the string such as the status bar also work fine. But Geany does not recognise CP1252 (Geany only knows WINDOWS-1252) so places that use the encoding index default to UTF-8. So Geany saves the encoding in the session file as UTF-8 which is incorrect. The document->set encoding menu also defaults to UTF-8 because it uses the index to select the option. Geany could fix the sessions by just saving the encoding name not an index, but the menu is a problem and may need an "unknown (no change)" option. Or Geany could refuse to use encodings that it doesn't recognise, but that is somewhat restrictive :( And I don't know what other parts of Geany may also be affected. Any other ideas? Cheers Lex [1] http://article.gmane.org/gmane.editors.geany.general/6285

3 4

[RFC] Geany Plugin Names
by Matthew Brush 03 Nov '11

03 Nov '11

Hi all, Is anybody opposed to removing the "geany" and "Geany" prefix from the plugins in Geany-Plugins. I mean at least for the directory name in the source tree, README/Site, and PLUGIN_SET_INFO() name? It's always bothered me when I go into *Geany's* plugin manager and see plugin names like "GeanyFooBar". Obviously the plugin is for Geany and the "Geany" prefix makes the plugin not ordered correctly. Same goes for the SVN/Git repository source tree directory names. For example: Geany-Zencoding plugin could be "Zencoding" under the directory in the repo called "zencoding". This is like many plugins already, for example: addons, codenav, debugger, devhelp, gproject (sorta :), pretty-printer, shiftcolumn, spellcheck, tableconvert, treebrowser, updatechecker, webhelper, and xmlsnippets. IMO these would be reasonable renames for the others: Old Name Plugin Info Name Directory ======== ================ ========= GeanyDoc Documentation?[1] doc or geanydoc GeanyExtrasel Extra Selections extrasel Geanygdb GNU Debugger[2] gdb GeanyGenDoc Documentation Generator gendoc GeanyInsertNum Insert Numbers[3] insertnum GeanyLatex LaTeX (Addons) latex GeanyLipsum Lorem Ipsum Generator lipsum GeanyLua Lua Plugins lua GeanyMacro Macro Recorder macro GeanyNumberedBookmarks Numbered Bookmarks numberedbookmarks GeanyPg Privacy Guard pg or gpg GeanyPrj Project Manager?[4] prj or project GeanySendMail Send Mail sendmail GeanyVC Version Control vc or vcs --[coming soon]--------------------------------------------------- GeanyMultiTerm Multi-Tabbed Terminal multiterm GeanyPy Python Plugins python GeanyZencoding Zen Coding zencoding ================================================================== [1] Could we merge Devhelp and GeanyDoc? [2] Could we replace in favour of Debugger? [3] Should this go in Addons? [4] Could we merge GProject and GeanyPrj or are totally different? ================================================================== Anyway, just a thought to make things more consistent and less redundant. It seems like while converting and moving to Git would be an ideal time to do this. Feel free to +1, -1, comment or ignore. Cheers, Matthew Brush

12 30

Geany-Plugins 0.21.1 released
by Frank Lanitz 01 Nov '11

01 Nov '11

Hi all, Due a little issue with source tarball of 0.21-release of Geany-Plugins 0.21.1 has been released which fixes an issue of non working waf-build system from inside the source tarball. As usual, tarballs and their corresponding GPG signatures can be found at <http://plugins.geany.org/downloads.html>. The Windows installer has not been directly effected by this issue so renewing is not needed. Cheers, Frank -- http://frank.uvena.de/en/

2 3

gtkbuilder branch and ui_lookup_widget functions
by Nick Treleaven 31 Oct '11

31 Oct '11

Hi Matthew, I'm a bit concerned about the changed ui_lookup_widget (and hookup) functions - these are in the plugin API and can be used independently from Glade. (plugin) API function behaviour should not normally change, but it seems the owner parameter is now ignored. If we are caching lookups this is probably wrong as the widget may get destroyed. I haven't looked at the new implementation but perhaps you could help explain the changes.

2 9

Geany is on Github
by Matthew Brush 31 Oct '11

31 Oct '11

Hi all, For the tl;dr crowd: https://github.com/geany And now for the long version :) I've setup Geany as an organization on Github.com[1]. I've also setup an empty repository[2] for when the SVN conversion is ready to push. I will try and explain how this works because it's a little bit complicated at first glance. To create an Organization, you first need to create a personal account. The personal account can't have the same name as the Organization. After the personal account is created, you convert it into an Organization which is almost a separate entity but is in some ways tied to the personal account. The personal account I created to do this is called 'geanyadmin' (to avoid clashing with the Organization name). Once the organization is created, you can add "Owners" to it. Owners have the exact same access as the 'geanyadmin' user, for example, an owner could theoretically sign up the Geany organization to a pay account, the Owners have wide-open access to everything. Basically there's no real reason to ever use the 'geanyadmin' account as far as I can see, once Owners are added to the Organization. Just to start, because I had their Github usernames, I've added Enrico and Colomban as owners, as well as myself since I need access to set the stuff up. Whoever else should be an Owner (Frank, Nick, etc.) just let me (or other Owners) know. Read below as for why not too many people really need to be "Owners". Now with an Organization, and some Owners who are able to administer the Organization, we come to Teams. Teams are groups of users who all have the same permissions on one or more repository. Teams can be setup to have Pull Only, Pull and Push, and Pull, Push and Administer access. Just to give an example, we'll take the 'geany' repository which will be the main Geany core repository. We could add a team for "Core Developers", this group of users could be the existing people with commit access to SVN. In fact I've already created this team, with all 3 permissions mentioned above, and since I had their Github usernames, I've added Colomban and Enrico to this group. Now, what we could do, for example, is to create another Team called "Contributors" or something, and this Team could have Pull only access (even without being in a team, anyone can still clone/pull). Myself, I would probably go into the "Contributors" Team, since I contribute a fair bit, but I don't have commit access. Another Team could be called "Translators", and have one of the three levels of access control mentioned above, and it could be for all the Geany repositories, since translators likely work on both Geany and Geany-Plugins. Another Team could be "Newsletter Writers" or something and they could have perhaps Push and Pull access on the "newletters" repository only. For starting, I suggest the following Teams: - Core Developers (Pull/Push/Admin) - Core Contributors (Pull) - Plugin Developers (Pull/Push) - Plugin Contributors (Pull) - Translators (Pull/Push? or does it go through Frank?) - on both geany and plugins repositories? - Newsletter Editors (Pull/Push on newsletters repo) Keep in mind that any Github user can be in as many of the above Teams as needed, and we can create any? amount of teams, these are just some suggestions. So anyway, I hope that makes things a bit clear. Just to sum up some key points: * Colomban and Enrico currently have complete access to the geany organization and can do anything at all, including adding other Owners or Teams or Team members, etc. * The geanyadmin user is mostly useless, except maybe for setting up some service hooks and things like that. * I will give Colomban the password for the geanyadmin account. I can still help with setting up on Github since my own personal account is setup as an Owner (thought not with commit access on the geany repository). * On Github, the icon for the geany Organization, as well as the geanyadmin can only be show if their email addresses are attached with a Gravatar account. To avoid forcing anyone else to sign up for this service, and since I already had an account, I've setup the emails under my Gravatar account. All it does is link team(a)geany.org to the Geany logo I uploaded. The geanyadmin icon is coming from my Gravatar account, attached with matt(a)geany.org (just for the Gravatar, not for the accounts actual email address). * We need everyone's Github usernames so we can add them as appropriate (this won't be my call). I suggest the existing SVN committers get same access as before, and for now, all others go into a Pull Only Team. Anyone besides the core devs/committers should also give their Github usernames so they can be added, with Pull Only permissions, as Team members and be "associated" with the organization (at least this is my understanding). And now I have a question; now that Geany and Geany Plugins are grouped together under the same organization, should we drop the geany- prefix on the plugins repository? This would give us the following repositories to start: - geany - plugins - newsletter - talks (?) Comments, questions, and slander are welcome. And don't forget to give me your Github usernames! Cheers, Matthew Brush [1] https://github.com/geany [2] https://github.com/geany/geany

11 26

Geany Hackfest
by Matthew Brush 31 Oct '11

31 Oct '11

Hi All, Just wanted to throw out the idea of a "hackfest" for Geany and/or Geany Plugins. Obviously only a handful of us can get together in meat space but between IRC, IM, the ML, and now GitHub, I think we can manage without all of us being physically present. Here's a few possible topics/targets/ideas: - Session management - GTK+ 3 support (obviously :) - Glade3 / GtkBuilder conversion (again, obviously :) - Attacking the bug tracker and/or feature requests [ add your suggestions here ] So is anybody available for <insert length of hackfest> hours/days in the near future? I'm personally available for most of the time between Christmas and the end of the first week of 2012. Otherwise, it would need to be on a weekend for me to "attend". Cheers, Matthew Brush

4 3

Geany Plugins Warnings (again)
by Matthew Brush 31 Oct '11

31 Oct '11

Hi, I know Frank has asked a few times for people to clean up the build warnings for their plugins. There's still *way* too many warnings. I quickly went through all the warnings and "fixed" them. I just did the quick/obvious fixes and didn't test anything. I can almost guarantee that at least a few of the "fixes" aren't correct and will cause problems with the plugins. Attached are all the patches that fix the warnings. If the plugins developer(s) could each look at their respective patches and review them and either apply and thoroughly test their plugins or ignore them and otherwise fix the warnings, that would be great. The only plugin with non-trivial (by way of quantity) warnings to fix was GeanyGDB. I don't know if this is maintained any more or if it's needed with having the Debugger plugin, but if it is, the author(s) should go through and fix all their `const` usage themselves. The attached patch for GeanyGDB only fixes a few usages but exposes much more warnings, so it might be of little use. In the Treebrowser I did a little more than fix the warnings since there were some weird logic and memory issues. Again, I can't guarantee I've fixed them, but it should give some ideas. For the Gendoc plugin, I'm not sure if the warnings are false positives or not, if so, ignore the patch for that. Just to reiterate *none of the fixes were tested*, so don't just blindly apply the patches but rather use them as motivation to fix your plugin properly. Cheers, Matthew Brush

4 15

fork me on github (again, and web stuff)
by Josh 31 Oct '11

31 Oct '11

Hey, Last time Matt noted I should've provided code to go with the 'fork me on github' banners. So the following will get a 'fork me' banner on geany.org (if that's desired; also, this scrolls w/the page): <https://github.com/about#media_downloads><a href="https://github.com/geany/geany"><img src="http://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png" style="position: fixed; right: 0; top: 0;"></a> However that one's black. A white one can be found here: https://github.com/about#media_downloads Also, if there's anything stupid/fancy/new/cool you want on geany.org I'd be willing to try. I have web development experience, so let me know! Thanks, Josh

4 3

Re: [Geany-devel] [geany/geany] a23e99: Bump GTK+ version to 2.16
by Matthew Brush 30 Oct '11

30 Oct '11

Hi, It would be great to get a little more testing on this, especially with Waf and Windows. @Enrico When you get back from your visit or whenever you have time, could update the GTK+ (and friends) documentation on geany.org? Cheers, Matthew Brush On 10/28/2011 10:35 AM, Matthew Brush wrote: > Branch: refs/heads/master > Home: https://github.com/geany/geany > > Commit: a23e999b7bde54cc23184e6991ca5fdb58cdc47c > https://github.com/geany/geany/commit/a23e999b7bde54cc23184e6991ca5fdb58cdc… > Author: Matthew Brush<mbrush(a)codebrainz.ca> > Date: 2011-10-28 (Fri, 28 Oct 2011) > > Changed paths: > M HACKING > M README > M configure.ac > M doc/geany.html > M doc/geany.txt > M geany.pc.in > M plugins/filebrowser.c > M src/callbacks.c > M src/dialogs.c > M src/ui_utils.c > M src/utils.c > M wscript > > Log Message: > ----------- > Bump GTK+ version to 2.16 > > > _______________________________________________ > Geany-commits mailing list > Geany-commits(a)uvena.de > https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-commits

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel October 2011