Re: [Geany-devel] geany-newsletter: License of newsletter
On Fri, 8 Apr 2011 13:45:12 -0500 Randy Kramer wrote: > On Friday 08 April 2011 01:54:13 pm Dominic Hopf wrote: > > Am Freitag, den 08.04.2011, 18:28 +0200 schrieb Thomas Martitz: > > > I never heard of licenses for newsletters. > > > > Me neither. > > Well, it is written material, and, automatically (iiuc, according to > the Berne Treaty) subject to copyright (i.e., it is copyrighted). > So, who/how do you want to allow anyone else to use it? > > That's what a license is. If you don't specify a license, I guess (I > think) no one has a right to copy and use it for any purpose, but, > ianal (i am not a liar^H^H^H^Hlawyer). Yepp. That is issue I had in my mind. Cheers, Frank -- http://frank.uvena.de/en/ pgpSh51zSP4AM.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-newsletter: License of newsletter
On Sat, 9 Apr 2011 10:01:25 +1000 Lex Trotman wrote: > On 9 April 2011 08:39, Matthew Brush wrote: > > On 04/08/11 09:18, Frank Lanitz wrote: > >> > >> I just want to ask about which license we shall use for the > >> newsletter in future. I'd like to prefer to put it under terms of > >> one of the CC-family licenses. CC-BY (by = Geany Newsletter Team) > >> would fit most IMHO. What's your opinion? > > > > Anything with free distribution seems reasonable. I'm not sure why > > modification permissions would need to available, just for the sake > > of keeping each issue "a slice in time" and/or not to be mangled > > out of context, but it's probably no big deal anyway. > > Well IIUC without modification I couldn't use just part of the > newsletter, so I couldn't just distribute the tutorials for example, I > 'd have to distribute the whole thing. But CC-BY is allowing this. Maybe CC-BY-SA would be a more GPL-like flavor of CC. I don't think NC or ND is making any big sense. Cheers, Frank -- http://frank.uvena.de/en/ pgpEC5L28wMRL.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-newsletter: License of newsletter
On Sat, 9 Apr 2011 11:17:20 +1000 Lex Trotman wrote: > > But CC-BY is allowing this. Maybe CC-BY-SA would be a more GPL-like > > flavor of CC. > > Yes, CC-BY allows modification. IIUC CC-BY-SA would preclude any more > than "fair use" quantities of material anywhere that is not itself > licensed by CC_BY_SA. For example this might preclude use of > newsletter articles on software blogging sites if they have > non-CC-BY-SA licenses. So I am not in favor of CC-BY-SA. Well, I think its not 100% true. Short, you can do what every you want with it if you keep points in mind: BY and redistribute derivates and the original by CC-BY-SA. This is not enforcing you to move your whole blog to CC. > If using CC-BY how should attribution be required? Perhaps "Geany > newsletter team" and (if online) link to Geany website. Yepp, that's what I had in my mind. Cheers, Frank -- http://frank.uvena.de/en/ pgpA9K1ncJogl.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] POLL: Usage of geanyVC
Hi, After long time I'm doing some maintenance work on geanyVC and now I'm interested which VCS are used by the users. Therefor I did create a doodle at http://www.doodle.com/5d7mi43raww2wnrq I'd like to ask you to insert which of the supported VCS you are using. Thanks in advance ;) Cheers, Frank -- http://frank.uvena.de/en/ pgpqEfvY0Zpky.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SF.net SVN: geany:[5724] trunk
Hi, On Wed, 13 Apr 2011 21:55:31 + colomb...@users.sourceforge.net wrote: > Revision: 5724 > http://geany.svn.sourceforge.net/geany/?rev=5724&view=rev > Author: colombanw > Date: 2011-04-13 21:55:31 + (Wed, 13 Apr 2011) > > Log Message: > --- > Avoid triggering autocompletion on PHP open tags (closes #3199442) I'm not sure whether this is really useful as this is adding (not much) complexity and more check on typing time, but not increasing typing comfort much IMHO. Cheers, Frank -- http://frank.uvena.de/en/ pgpdaZTMwhtUb.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] {datetime} & {date} are updated only after config reload
On Fri, 15 Apr 2011 22:57:00 +1000
Lex Trotman wrote:
> On 15 April 2011 21:51, Randy Kramer wrote:
> > On Thursday 14 April 2011 08:02:17 pm Lex Trotman wrote:
> >> Yes the {datetime} and {date} are substituted when the templates are
> >> initialised, usually when Geany is opened. As you say this may not
> >> be very useful.
> >>
> >> This can be changed just by moving the call to
> >> templates_replace_default_dates, but where to?
> >>
> >> Options are:
> >>
> >> 1. when the document is created from the template
> >> 2. when the document is saved as a file (when untitled gets replaced)
> >>
> >> Votes please.
> >
> > I haven't yet used those templates (and might never, my file format is a
> > multi-record format and I will want to timestamp the creation of each
> > record, but I anticipate doing that with a recorded (or Lua) macro).
> >
> > I can't remember how those dates are handled in something like Microsoft
> > Word (the last time I can remember using something like those
> > tempates--but close to 10 years ago, now), but I'm pretty sure it would
> > *not* be a good idea to change them each time the document is saved.
>
> Apologies if it was unclear, but after the {date} or {datetime} marker
> is *replaced* by the date/time the first time it no longer exists so
> no further updates occur.
What about moving this to request time? So not parsing at startup but
parsing it when requested by user to insert?
Cheers,
Frank
--
Frank Lanitz
pgpnIK3BFrv89.pgp
Description: PGP signature
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SF.net SVN: geany:[5724] trunk
On Thu, 14 Apr 2011 20:37:01 +0200 Colomban Wendling wrote: > Le 14/04/2011 19:15, Frank Lanitz a écrit : > > Hi, > > Hi Frank, > > > On Wed, 13 Apr 2011 21:55:31 + > > colomb...@users.sourceforge.net wrote: > > > >> Revision: 5724 > >> http://geany.svn.sourceforge.net/geany/?rev=5724&view=rev > >> Author: colombanw > >> Date: 2011-04-13 21:55:31 + (Wed, 13 Apr 2011) > >> > >> Log Message: > >> --- > >> Avoid triggering autocompletion on PHP open tags (closes #3199442) > > > > I'm not sure whether this is really useful as this is adding (not much) > > complexity and more check on typing time, but not increasing typing > > comfort much IMHO. > > I saw you responded to the bug report and said wontfix, but I personally > agree with the reporters of #3199442 that when writing PHP code it's > common to type " length set to 3 or less it's annoying to have the completion coming up. > Generally I don't even notice the completion came up and get the first > item where I wanted nothing, forcing me to remove it/undo. > So I think it's a useful thing for PHP writers, worth having a special > case for it. And I think Geany is widely used for PHP code editing, so I > think (again) that it'd help many users, not only a few ones. > > Moreover, I don't think the check I added is likely to have a real > overhead on typing, especially with non-PHP code. I tried to built the > condition correctly for it not to match as soon as possible (e.g. the > less likely stuff first) but you might want to optimize it even further > (maybe at the cost of a little readability) by e.g. > > *) use G_UNLIKELY() > *) reorder the check even better, though I think it's less readable: >ft->id == GEANY_FILETYPES_PHP && >rootlen == 3 && >startword >= 2 && >style == SCE_HPHP_DEFAULT && >strcmp(&root[-2], " > However, I agree that this adds a little complexity in the code, but > AFAIK we don't have (currently?) any other solution to support this -- > and I don't think it's really useful to have a generic solution, since > there's not so many special cases like this. > > That's my opinion, but feel free to convince me it's wrong (e.g. > measurements of the speed cost showing it's a significant overhead, or > whatever) -- or even that it's just "bad, that's all" and I must go with > it [1] :D Well, its hard to say, but maybe you are right. At least your points do sound reasonable. ;) Cheers, Frank -- Frank Lanitz pgpzYjrXm5s2L.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GeanyCFP
Hi William, Am 17.04.2011 13:45, schrieb William Fraser: First of all - appologies as I've not been in contact for a couple of months. Have moved house and the phone company/ISP royally fouled up, and had to change providers so no internet access for about 8 weeks :( Also a couple of family emergencies, and I've a major exam looming, so may be a little slow for the next month or so. However, welcome back ;) Frank Lanitz suggested splitting geanycfp into separate plugins. I think this makes sense for several reasons: by splitting it into GeanyMacros, and GeanyNumberedBookmarks it makes it clearer what the plugins do, and it keeps it more in-keeping with the light-weight/only add what you use mentality of Geany and Geany-Plugins. I have therefore split it into 2 separate plugins. Will this deprecate geanycfp? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] hex mode
Am 14.04.2011 22:29, schrieb Liviu Andronic: Does Geany have a hex mode, that is can I open files in hex mode? And a bit more OT, Geany refuses to force-open a PDF file. Nano, for example, opens the PDF. Is it normal? As already mentioned, this is intended behavior due Scintilla. But maybe this could be a cool feature for Scintilla in general. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] hex mode
Am 19.04.2011 09:12, schrieb Lex Trotman: On 19 April 2011 16:50, Frank Lanitz wrote: Am 14.04.2011 22:29, schrieb Liviu Andronic: Does Geany have a hex mode, that is can I open files in hex mode? And a bit more OT, Geany refuses to force-open a PDF file. Nano, for example, opens the PDF. Is it normal? As already mentioned, this is intended behavior due Scintilla. But maybe this could be a cool feature for Scintilla in general. I don't think that there would be enough demand for Scintilla to break clients, but there is nothing stopping a Geany plugin converting a file to hex codes before loading it into Scintilla and converting it back again when saving (well except someone has to write it :-). Which feature should such a plugin have? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GeanyCFP
On Tue, 19 Apr 2011 17:50:33 +0100 WILLIAM FRASER wrote: > Yes, it would. I'm not sure how soon to to remove geanycfp though. > I've not > done any major re-coding, and have not encountered any bugs, but I'm > not sure when to remove geanycfp from Geany-Plugins. Well, if all functions are moved to the new plugins we should do it as soon as possible. Cheers, Frank -- http://frank.uvena.de/en/ pgpC5knrmRDb1.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GProject - missing Geany patches
On Tue, 26 Apr 2011 11:18:16 +0200 Jiří Techet wrote: > On Sun, Apr 10, 2011 at 15:03, Jiří Techet wrote: > > Hi, > > > > first sorry for disappearing for such a long time - I didn't have > > much free time left in the past months and from the time I had I > > dedicated most of it to the libchamplain library I maintain to make > > some bigger changes and adapt it to GTK 3 in time for Gnome 3. The > > good news is that I didn't convert to Eclipse or Emacs > > meanwhile ;-). > > > > There are still quite many patches I have against geany in my > > repository and I'd like to have at least part of them merged so I > > don't have to maintain my own geany branch. So at the moment the > > highest-priority patches for me are those which are necessary in > > order to make GProject working so it can become one of official > > geany plugins. The patches can be found at usual place: > > > > https://gitorious.org/~techy/geany/gproject-geany > > > > under the for_review4 branch. Only the first three of them are > > needed for GProject so they should have the highest priority when > > reviewing: > > > > 4774306b7f65237ef75b01e8d6c8312dcc5c526e Make project patterns > > visible 57b4120f94e611e8143fba89e397588de8693ec3 Use project > > patterns in the FIF dialog 2edb068b81cb6d541d667efecd0ec4c346f0df51 > > Open the file in the msgwindow even if no linenumber is specified > > > > More info about the patches is in the commit description. If there > > are some questions, please ask me. Also if you prefer the patches > > in the form of ordinary patches rather than git repo, just let me > > know. > > > > Cheers, > > > > Jiri > > Hi, > > more than two weeks have passed without any response and I fear it > will end the same way as many times before - that I post my patches, > nobody looks at them and they get forgotten. I fully understand that > people have limited time to work on geany (so do I), the problem is > that most of the patches are 9 months old and they haven't been > reviewed so far. > > Of course I understand that you may not want to have some patches > merged to geany - just tell me and I'll either remove or rework them. > I'd just like to get some sort of feedback - positive or negative. > > Please let me know if there's anything I can help with to get the > patches reviewed. Or, if you don't want my patches at all for some > reason, please tell me as well so I stop spamming the mailing list > with them. As from my point, I'm afraid I cannot add much value to this as I'm not very experienced with GOBject and stuff. That's why I didn't mess around with your patches also. And as I mentioned according to plugin interface discussion, I like to have it this way for enabling GObject fun: I want to have someone with experince managing this kind of stuff. Cheers, Frank -- http://frank.uvena.de/en/ pgpEd55FDoo00.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GObject, new plugin interface ....
Hi, Am 12.03.2011 19:11, schrieb Frank Lanitz: During the last weeks a huge number mails at this list was stating to make usage of GObject on building up a new plugin interface. It has been talked about libpeas and adding support for Vala, Python etc. Before we do discuss any further I'd like to point to an email Enrico sent earlier this year onto this list: http://lists.uvena.de/geany-devel/2011-February/003905.html Originally Geany wasn't designed/coded to work with GObject. Moving to an plugin interface using this would most likely cause rewriting of a lot of code. However, if really somebody of you like to go this further I suggest to start a new branch where all changes can be tracked in. But before we can discuss about the positive/negativ points I just want to ask who likes to take over this task as a kind of lead engineer and project manager to be the lead here having in mind it will most likely not a 5-minute-task? What's the outcome here? I saw a lot of technical discussion followed up by my original posting but nobody took over the rule to bring all the idea into synch. Not sure whether I might did miss something. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Plugins quality
Hi Plugins-Devs, As you might did see I did some work during the weekend to fix make check (and break it during this also again ;) ) as well as did some minor code changes where I thought they don't hurt much but would improve something. However, I recognized tons of compiler warnings which did make me upset. I know, many of them might not be any dangerous but I really like to ask you to to have a look onto it and fix where possible/useful. Cheers, Frank P.S. Well, I'm, not sure for how long make check didn't work, but based on commits I would say for a couple of weeks. Does actually anybody of you use this? ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GObject, new plugin interface ....
Am 28.04.2011 09:32, schrieb Matthew Brush: > On 04/28/11 00:01, Frank Lanitz wrote: >> Hi, >> >> Am 12.03.2011 19:11, schrieb Frank Lanitz: >>> During the last weeks a huge number mails at this list was stating to >>> make usage of GObject on building up a new plugin interface. It has been >>> talked about libpeas and adding support for Vala, Python etc. Before we >>> do discuss any further I'd like to point to an email Enrico sent >>> earlier this year onto this list: >>> >>> http://lists.uvena.de/geany-devel/2011-February/003905.html >>> >>> Originally Geany wasn't designed/coded to work with GObject. Moving to >>> an plugin interface using this would most likely cause rewriting of a >>> lot of code. However, if really somebody of you like to go this >>> further I suggest to start a new branch where all changes can be >>> tracked in. >>> But before we can discuss about the positive/negativ points I just >>> want to ask who likes to take over this task as a kind of lead >>> engineer and project manager to be the lead here having in mind it will >>> most likely not a 5-minute-task? >> >> What's the outcome here? I saw a lot of technical discussion followed up >> by my original posting but nobody took over the rule to bring all the >> idea into synch. Not sure whether I might did miss something. > > I had offered to work on this, but I wanted to make sure someone would > be willing to review/commit all the changes, the responses were: > > From Lex: > "I currently have a looong commute where I can't actually code or > compile or test things (my tablet is just not suited), but I can > review and discuss things by the magic of wifi." > > From Colomban: > "However, even though I like the idea of creating this new plugin API > supporting other languages, I will not tell I'll help a lot because I'm > really not sure of the amount of time I could spend on it. However, I'd > be happy to help from time to time, when I can :)" > > In another thread from you: > "And as I mentioned according to plugin interface discussion, I like to > have it this way for enabling GObject fun: I want to have someone with > experince managing this kind of stuff." > > Nothing from Enrico, Nick or other core developers with commit access. > So I pretty much decided I would be wasting my time on this if the code > won't get committed and the core developers aren't even very much > interested in this. I think we had an agreement that we can develop it inside a new branch (where of course you can commit) and once its stable its getting merged into trunk. If everybody is fine with it I'd suggest to give Matthew commit rights for new branch to build up the GObject plugin interface as some kind of project leader. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugins quality
Am 28.04.2011 09:47, schrieb Matthew Brush: > On 04/28/11 00:10, Frank Lanitz wrote: > >> However, I recognized tons of compiler warnings which did make me upset. >> I know, many of them might not be any dangerous but I really like to ask >> you to to have a look onto it and fix where possible/useful. > > My plugin's 'make check' output, unlike its source code, is clean. This wasn't onto some special plugin but whole plugins project in general. I don't see it as single task for a single maintainer, but as a common task for whole project to keep overall quality high inside all plugins. >> P.S. Well, I'm, not sure for how long make check didn't work, but based >> on commits I would say for a couple of weeks. Does actually anybody of >> you use this? > > I do, though I haven't actually worked on the Devhelp plugin in some time. > > BTW, for me the 'make check' fails with, not sure if it's supposed to > fail the build on these cases or not: > > make[3]: Entering directory > `/home/mbrush/Projects/Geany/geany-plugins/geany-plugins/pretty-printer/src' > > /usr/bin/cppcheck -q --template gcc --error-exitcode=2 . > ./PrettyPrinter.c:110: error: Common realloc mistake: "xmlPrettyPrinted" > nulled but not freed upon failure > ./PrettyPrinter.c:183: error: Common realloc mistake: "xmlPrettyPrinted" > nulled but not freed upon failure Did you use clean sources? Which is you system as on my Debian unstable with AMD64 there have been no issues Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SVN Log Stats
Am 03.05.2011 03:28, schrieb Matthew Brush: > Hi, > > I was curious about the statistics for the Geany project so I hacked > together some Python code to peel out some values from the SVN log. If > anyone cares, the following are some of what I found: > > Total commits: > eht16: 2466 > ntrel: 2182 > frlan: 413 > colombanw: 87 > kretek: 74 > elextr: 18 > peterscholtens: 9 > dmaphy: 8 > clytie: 2 > > Total lines changed: > ntrel: 6195 > eht16: 4174 > frlan: 455 > colombanw: 326 > kretek: 103 > elextr: 34 > dmaphy: 9 > peterscholtens: 9 > clytie: 4 > > Since the log doesn't attribute patch authors normally, I was going to > try and parse the "Thanks, Foo bar" messages to get counts for read-only > developers from the commit messages, but it's too much trouble. If > anyone is curious, the word 'thanks' occurs 410 times in the log. > > Anyway, I thought others might be interested to see these numbers, since > I couldn't find them through SF/otherwise. Ohloh is offering some stats too: http://www.ohloh.net/p/geany/contributors Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SVN Log Stats
Am 03.05.2011 10:43, schrieb Matthew Brush: > On 05/03/11 00:21, Frank Lanitz wrote: >> Am 03.05.2011 03:28, schrieb Matthew Brush: >>> >>> Anyway, I thought others might be interested to see these numbers, since >>> I couldn't find them through SF/otherwise. >> >> Ohloh is offering some stats too: >> http://www.ohloh.net/p/geany/contributors > > I knew it must be somewhere out there! Thanks Frank. You are welcome. And of course cgit if offering some little stats too: http://git.geany.org/geany/stats/ Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Newsletter issues #2 reaching target line
Hi folks, About two month ago we released issues 1 of Geany newsletter and we are thinking of doing a new one upcoming week. Not all work is done yet, some contents are missing (mea culpa e.g. some parts I wanted to write) as well as some optical corrections needs to be done on both, HTML and PDF version of the newsletter. However, if you like to contribute some content or some patch for buildsystem, CSS and other templates for issue 2 -- now its a good time to let us know ;) You will find current 'devel' version at http://git.geany.org/newsletter/tree/ Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Getting ready for GTK+ 3.0 - upgrading deprecated calls
Am 01.05.2011 02:51, schrieb Lex Trotman: > On 1 May 2011 10:37, Matthew Brush wrote: >> Hi, >> >> In reference to the recent post on the scintilla-interest mailing list >> posting with the same title[1]. >> >> Would this affect Geany's support for older GTK+ versions? > > > Neil states that it runs on gtk2.8 which is the version supported by > Geany, so far so good. > > Most of his changes are in Scite. Way too early to think about > changing Geany to GTK3, let it stabilise for a while yet. I agree for the meanwhile we shouldn't do any big progress to port it to 3. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Newsletter issues #2 reaching target line
Am 05.05.2011 07:17, schrieb Lex Trotman: > On 5 May 2011 15:00, Matthew Brush wrote: >> On 05/04/11 01:09, Frank Lanitz wrote: >>> >>> Hi folks, >>> >>> About two month ago we released issues 1 of Geany newsletter and we are >>> thinking of doing a new one upcoming week. Not all work is done yet, >>> some contents are missing (mea culpa e.g. some parts I wanted to write) >>> as well as some optical corrections needs to be done on both, HTML and >>> PDF version of the newsletter. However, if you like to contribute some >>> content or some patch for buildsystem, CSS and other templates for issue >>> 2 -- now its a good time to let us know ;) You will find current 'devel' >>> version at http://git.geany.org/newsletter/tree/ >> >> The last paragraph[1] under "Significant updates on Split Window Plugin" >> needs to be removed since, after all the time I spent on this bug, the patch >> has been forgotten and Windows support has never been enabled. > > Or maybe be hopeful and leave it there and call it coming soon ;-S My understanding was that this has been fixed and now is working also on Windows. What is pending here? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Planning bugfix release 0.20.1
Am 04.05.2011 22:53, schrieb Enrico Tröger: > I'd say let's make a 0.20.1 bugfix release soon. > So we can release the fixes made since the 0.20 release for users. > > If no one beats me by time, I'll create a 0.20.1 branch based on the > 0.20 tag on Sunday and then we can backport relevant fixes. A new relase is a good point I guess. But why not building a complete 0.21 from trunk or is it a bit early? Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Newsletter issues #2 reaching target line
On Wed, 4 May 2011 18:41:41 -0400 Nicholas Manea wrote: > Never mind, I've figured it out :) > > I've attached some patches that fix a typo and a formatting issue at > the end. I've put them into git. Thanks ;) Cheers, Frank -- http://frank.uvena.de/en/ pgp80VJciuTB3.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SplitWindow Windows support/fixes (was: Re: Geany-Newsletter issues #2 reaching target line)
Am 09.05.2011 15:27, schrieb Colomban Wendling: > Le 08/05/2011 23:18, Matthew Brush a écrit : >> On 05/08/11 10:08, Colomban Wendling wrote: >> >>> just need to re-apply the commits: >>> >>> http://git.geany.org/geany/commit/?id=757654e14b40d85c95c50ab422e3bcd63fa7fd29 >>> >>> http://git.geany.org/geany/commit/?id=1788dfa8dc6ba106a16069cf4ca79d3ee2a5533f >>> >> >> Yep, that should do it. > > Applied again. I tested under Linux, and it works OK, no more selection > problems, nor weird cursors. I haven't tested on Windows, but I guess > that nothing changed on this side since Enrico tried it last time? > Though if somebody have the time/courage/will to test it on Windows > again, it'd be great :) Will give it a try once a Windowsbuild with this change is available. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Newsletter issues #2 reaching target line
Am 09.05.2011 15:34, schrieb Colomban Wendling: > Le 05/05/2011 16:45, Matthew Brush a écrit : >> On 05/05/11 02:11, Frank Lanitz wrote: >> >>> My understanding was that this has been fixed and now is working also on >>> Windows. What is pending here? >> >> I don't think it ever got fixed/applied. Last I remember, Enrico said >> he will do in the next few days, and then I never heard anything more. >> What's pending is the patch to fix the original Windows bug[1][2] and >> re-enabling the Split Window plugin for Windows build[3][4]. > > Now done. Sorry for the long delay, and thanks again for the hard work! Cool, so we don't need to change the newsletter at this point ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Newsletter issues #2 reaching target line
Am 10.05.2011 01:54, schrieb Lex Trotman: >>> Now done. Sorry for the long delay, and thanks again for the hard work! >> >> Cool, so we don't need to change the newsletter at this point ;) >> > > Hey, new workflow, get a new feature described in the newsletter and > then it will be added to Geany so the newsletter isn't wrong :-) Let me add M-X butterfly to the newsletter ... ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] [RFC] Plugin Template
Am 03.05.2011 03:54, schrieb Matthew Brush: > Hi, > > I was thinking it would be useful to have a template directory with all > the "boiler-plate" for a Geany plugin under version control to get > people started quicker writing a new plugin that could become part of > the Geany Plugins project easier. I saw something similar[1] in the > GStreamer project. > > My ideas was to put in the directory the files required for the build > system(s), a generic README template, a GPL2 COPYING, etc, and a src/ > dir with a basic demo plugin (maybe from the Geany plugins/ dir?). > > What other common files besides these should be in there? > AUTHORS > COPYING > ChangeLog > Makefile.am > NEWS > README > THANKS > TODO > wscript_build > wscript_configure (are both these Waf files needed?) > ../build/foo.m4 (how to include if it's in .. ?) > src/foo.c > src/Makefile.am > configure.ac? (for building before it's in Geany Plugins proper) > > What do you guys think? > Is it worthwhile? > Have I missed any important files? > > I was going to follow this up with a tutorial on the Wiki explaining how > to check-out the template, describe which files needed to be modified > and how to do so, etc. Also it would have some more general notes from > HACKING, getting commit access, the cppcheck stuff and so on. This > would be a good companion to the plugin howto I think. > > I was also thinking about doing a similar template/tutorial for a Vala > plugin. > > Feedback would be appreciated. I like this idea, but really think it would fit better inside upcoming wiki. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SplitWindow Windows support/fixes
Am 09.05.2011 20:25, schrieb Oliver Krystal: > Just tried this with the nightlies on windows, and it doesn't crash or > anything like that. None off the right click functions work in the > split off window. I can second this (Windows7 64Bit running 32Bit Geany) Also the copy from second window is not working, but the graphical issues seems to be gone. Nice job! Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Fix crash and memory leak in treebrowser.c.
Am 12.05.2011 22:58, schrieb Colomban Wendling: > Le 12/05/2011 21:54, Enzo Matrix a écrit : >> Hello, >> >> sorry for my laggy response, i have no possibilities to apply and commit >> the patch in short time, (i am replacing linux with windows last month >> :( for a while, for doing msaccess and msexcel diploma work). >> If anybody have spare time to do that, will be great, if no, i think >> after week i will be ready to get back :) > > Done, as you asked on IRC (I just mail here to notify others and > especially Thomas). Great to hear ;) cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Collecting patches inside wiki
Hi, Not sure whether this is the best idea, but I've jsut created a page inside the wiki at http://wiki.geany.org/patches/review_list where we could collect patches/patchsets to just keep an overview as it appears on this mailing list some patches might get lost due lot of traffic/discussion. Tell me what you think about and maybe make some usage of it ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Build System User Guide
Am 18.05.2011 14:26, schrieb Randy Kramer: > All, > > Lex and I have had a little bit of off-line conversation about his > document, the Build System User Guide. He suggested that I put it on > the wiki. > > I made a feeble attempt, and now recommend instead that, at least on a > temporary basis, it be put on the geany.org website with one or more > links from the wiki to the document. This is because: >* the document is a fully formed, standalone HTML document >* and, in that form, is not directly "pastable" into the wiki > > Instead, unless I'm missing something, it would have to be copied and > pasted in as plain text, and then marked up with DokuWiki markup. The sourcecode of this document looks pretty much like generated code. Maybe Lex could use the original and put it into wiki as I don't think having another standalone document is making much sense when we already started to have a wiki as storing such things was the intention behind IIRC. cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Collecting patches inside wiki
Am 18.05.2011 16:28, schrieb Matthew Brush: > On 05/18/11 01:22, Frank Lanitz wrote: >> Hi, >> >> Not sure whether this is the best idea, but I've jsut created a page >> inside the wiki at http://wiki.geany.org/patches/review_list where we >> could collect patches/patchsets to just keep an overview as it appears >> on this mailing list some patches might get lost due lot of >> traffic/discussion. Tell me what you think about and maybe make some >> usage of it ;) > > It's better than having patches get buried in the mailing list, but > still there are better ways (see Git Switch (again) discussion) which > requires less effort for everyone. Even on a git switch (I'm honest didn't read the complete thread by now) you will have pending pull requests that might get lost. ;) > Slightly off-topic, I'm pretty new with this Wiki software (and wikis in > general). How do you create a new page? The only option I see is "Edit > this page". On DokuWiki just search for a page. In case of its not finding anything you can create it. > Also, is there (going to be) a "table of contents" on the > main page where all of the pages link from to make navigation easier? Or > is it just the Sitemap feature for this purpose? Yepp, there are plugins available doing this. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Collecting patches inside wiki
Am 18.05.2011 16:45, schrieb Frank Lanitz: > Am 18.05.2011 16:28, schrieb Matthew Brush: >> On 05/18/11 01:22, Frank Lanitz wrote: >>> Hi, >>> >>> Not sure whether this is the best idea, but I've jsut created a page >>> inside the wiki at http://wiki.geany.org/patches/review_list where we >>> could collect patches/patchsets to just keep an overview as it appears >>> on this mailing list some patches might get lost due lot of >>> traffic/discussion. Tell me what you think about and maybe make some >>> usage of it ;) >> >> It's better than having patches get buried in the mailing list, but >> still there are better ways (see Git Switch (again) discussion) which >> requires less effort for everyone. > > Even on a git switch (I'm honest didn't read the complete thread by now) > you will have pending pull requests that might get lost. ;) > >> Slightly off-topic, I'm pretty new with this Wiki software (and wikis in >> general). How do you create a new page? The only option I see is "Edit >> this page". > > > On DokuWiki just search for a page. In case of its not finding anything > you can create it. > >> Also, is there (going to be) a "table of contents" on the >> main page where all of the pages link from to make navigation easier? Or >> is it just the Sitemap feature for this purpose? > > Yepp, there are plugins available doing this. And give http://wiki.geany.org/start?do=index a try ;) Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany Newsletter Vol. 2
file(s) every time they were saved. A version control system such as GIT, Subversion or Mercurial is definitely recommended instead when possible. Feature Focus ^ Append Toolbar to the Menu ** The popularity of the netbook means that many people are looking at screens which are less than the desktop PC sizes of 15 inch and above. A netbook's screen format is usually widescreen, so vertical space is more limited than horizontal space. If you navigate to Edit -> Preferences you'll find an option titled "Append Toolbar to the Menu". Checking this option will result in the toolbar being moved from below the menu bar to beside it, resulting in more vertical space being available. Other screen-space-saving tips ** Geany has several other options which increase the amount of room available for the editing pane. In the View menu you'll find an option titled "Toggle all Additional Widgets" which hides all elements of the user interface except for the menu bar and scrollbars. Also in the View menu is an option titled "Fullscreen" which maximizes the Geany window to take up the entire screen, also turning off the window's titlebar and borders. This view can be especially useful if you want to minimize distractions from other applications. Geany local === Geany at Chemnitzer LinuxTage (March, 19th-20th) Together with the guys of Xfce, Geany was presented with a booth at the annual Chemnitzer LinuxTage event in March, a convention about all topics around Linux, BSD and free software in general. The booth was well visited and people came not only to ask questions or report a bug but also to tell us what they are using Geany for. So Dominic, Enrico and Frank had a lot of questions to answer and a lot of feedback to respond to. 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, Dominic Hopf, Enrico Tröger, Frank Lanitz, Matthew Brush, Nicholas Manea, Russell Dickenson pgp5oSHAE4Oab.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Build System User Guide
Am 22.05.2011 16:50, schrieb Enrico Tröger: > I don't like linking to yet another document. If you are in the Wiki, > you want just information, not download and open another document. IMO > this is quite distracting and unnecessarily circumstantial. > I really don't want to have your great docs in a third, separate place. > Either we put it into the Wiki or we put it into Geany's manual. > Basically, I do think it would fit best into the manual but it would > make the manual even bigger. This is why I personally would prefer the > wiki, now that we have it and it just needs to get ready to use (e.g. > by choosing a theme) and filled with a bit content. I second this. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Build System User Guide
Am 24.05.2011 10:04, schrieb Lex Trotman: > Just need to find out how to set max-width for these pages. This can and should be only done in a valid way by a theme for the wiki which needs to be provided by anybody. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Patch Tracker
On Fri, 27 May 2011 14:31:29 -0700 Matthew Brush wrote: > Hi, > > Would it be useful for someone with admin rights on SourceForge.net > to create a "Patch Tracker"? I've seen some projects with this[1]. > > [1] https://sourceforge.net/tracker/?group_id=6556&atid=306556 I thought collecting them inside wiki as most seems to push them via git etc. Cheers, Frank -- http://frank.uvena.de/en/ pgpwjXSRTIwWI.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Newsletter: Markuplangauge
Hi, You might have recognized that there have been a discussion on which markuplangauge/technique we will use for future Geany newsletter to write and create PDF/HTML/other output formats in. During this discussion a lot of different languages and ways have been suggested so decision is not easy. However, we (well, I) decided to do it on a more democratic way by doing a poll about. But before we are doing this poll we need to collect all possible ideas and put some basic facts together. To do so I did create a wiki page (please don't care about the theme for the moment as this is under discussion inside another thread) at http://wiki.geany.org/newsletter/markuplanguages where I like to ask everybody to enter suggestions based on a minimal feature list I put together you can also find at this page. Based on that list I will create a poll upcoming weekend (around June, 4th) - I will announce tis inside another mail with some basic rules. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] POLL started (was: Re: Newsletter: Markuplangauge)
Hi, On Wed, 01 Jun 2011 10:54:18 +0200 Frank Lanitz wrote: > Based on that list I will create a poll upcoming weekend (around June, > 4th) - I will announce tis inside another mail with some basic rules. I've just started the poll with all options given inside the wiki at http://wiki.geany.org/newsletter/markuplanguages You can join the poll at http://doodle.com/nnrmb2bakye8m4sz Please be so fair and do only do participate, if you really want to contribute or have any other connection to the newsletter. I will close the poll upcoming weekend (11. June) Cheers, Frank -- http://frank.uvena.de/en/ pgpKUuwF4CZuY.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] New Wishlist
Am 06.06.2011 00:07, schrieb Maciej Ciemborowicz: > As we all know, first version of the wishlist wasn't prepared for such > big number of future requests. So it had to be closed. Now people may > post them at the Sourceforge tracker. But it also isn't too readable. So > here is my idea: > > 1. Users should have ability to vote for future requests > 2. Users should have ability to sort future requests by number of votes > and timestamp > 3. Future requests should have tags > > What do you think about it? In general good idea, but, well, as far as I know this is not supported by SF wish list, so this would mean to have something else installed. I've got nothing against, but will not actively look for any suitable solution. Cheers, Frank (P.S. Please don't hijack other thread) ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] POLL started (was: Re: Newsletter: Markuplangauge)
Hi, On Sun, 5 Jun 2011 19:26:16 +0200 Frank Lanitz wrote: > On Wed, 01 Jun 2011 10:54:18 +0200 > Frank Lanitz wrote: > > > Based on that list I will create a poll upcoming weekend (around > > June, 4th) - I will announce tis inside another mail with some > > basic rules. > > I've just started the poll with all options given inside the wiki at > http://wiki.geany.org/newsletter/markuplanguages > > You can join the poll at > http://doodle.com/nnrmb2bakye8m4sz > > Please be so fair and do only do participate, if you really want to > contribute or have any other connection to the newsletter. > > I will close the poll upcoming weekend (11. June) Well, still early in the morning CEST, but I guess the outcome was clear: Currently we do have 6 participants. 5 votes for ReST, 2 for AsciiDoc and one for LaTeX. Beside one which voted for ReST all of the participants don't care much about in addition to its favorite choice. So we do have a decision: issue 3+ will be done in ReST. Next steps (just a few points): Colomban did some nice work on creating the pdf from ReST a couple of days ago. I will merge his changes into master and will start to convert issue 1 and 2 to latest version so newsletter looks the same. Also Russell did start to write some cool content for issue 3 as well as there have been some discussion on linking and putting which content to newsletter/wiki during last days on mailing list. I did not yet set a release date but I guess sometime mid July would be a good idea. Cheers, Frank -- http://frank.uvena.de/en/ pgpewC59qIfoS.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Bumping Geany's GTK minimum requirement to 2.12
On Mon, 13 Jun 2011 17:26:06 +0200 Enrico Tröger wrote: > On Mon, 13 Jun 2011 16:45:38 +0200, Colomban wrote: > > >Le 04/05/2011 23:00, Enrico Tröger a écrit : > >> Hi, > >> > >> any objections in increasing the GTK minimum requirement of Geany > >> to GTK 2.12 (and GLib 2.16)? > >> > >> [...] > > > >Any new on the subject? Should we go on an start moving? > > Yeah, I'd say let's go! I second this. Cheers, Frank -- http://frank.uvena.de/en/ pgpwuJ2pgUSyN.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Plugins: Bump dependencies also to GTK 2.12 / GLIB 2.16?
Hi developers, As currently the dependencies for Geany are getting bumped to GTK 2.12 and GLIB 2.16 I'm wondering whether we should also bump dependencies of current devel version of geany-plugins to Geany 0.21 and with this step also to this versions of GTK/glib? Cheers, Frank -- http://frank.uvena.de/en/ pgpPVec5dntwF.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Compiler warnings
Hi folks, Didn't had any deeper check but with recent svn I'm getting these compiler warnings on build with waf ../src/plugins.c:341:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:341:2: warning: (near initialization for ‘stash_funcs.stash_group_add_toggle_button’) [enabled by default] ../src/plugins.c:342:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:342:2: warning: (near initialization for ‘stash_funcs.stash_group_add_radio_buttons’) [enabled by default] ../src/plugins.c:343:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:343:2: warning: (near initialization for ‘stash_funcs.stash_group_add_spin_button_integer’) [enabled by default] ../src/plugins.c:344:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:344:2: warning: (near initialization for ‘stash_funcs.stash_group_add_combo_box’) [enabled by default] ../src/plugins.c:345:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:345:2: warning: (near initialization for ‘stash_funcs.stash_group_add_combo_box_entry’) [enabled by default] ../src/plugins.c:346:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:346:2: warning: (near initialization for ‘stash_funcs.stash_group_add_entry’) [enabled by default] ../src/plugins.c:347:2: warning: initialization from incompatible pointer type [enabled by default] ../src/plugins.c:347:2: warning: (near initialization for ‘stash_funcs.stash_group_add_widget_property’) [enabled by default] Its a Debian/Unstable here running on AMD64. Cheers, Frank -- http://frank.uvena.de/en/ pgpMTTvWqsND2.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugins: Bump dependencies also to GTK 2.12 / GLIB 2.16?
Hi, On Sun, 19 Jun 2011 15:18:33 +0200 Colomban Wendling wrote: > Le 13/06/2011 23:12, Frank Lanitz a écrit : > > Hi developers, > > > > As currently the dependencies for Geany are getting bumped to GTK > > 2.12 and GLIB 2.16 I'm wondering whether we should also bump > > dependencies of current devel version of geany-plugins to Geany > > 0.21 and with this step also to this versions of GTK/glib? > > Yes, I think so. This wouldn't force plugins writers to do the bump, > but IMHO it doesn't make much sense for plugins to have a tighter > dependency than Geany itself. I did try to do this with svn r2095. I hope I didn't break anything or miss something. The glib dependency is still missing at least on waf. On autotools I didn't found any gtk dependency inside general section at all... Did I just miss them? Cheers, Frank -- http://frank.uvena.de/en/ pgpEPN9WlgOyN.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SF.net SVN: geany-plugins:[2096] trunk/geany-plugins/gproject/src/ gproject-project.c
Hi folks, On Sun, 19 Jun 2011 22:30:57 + tec...@users.sourceforge.net wrote: > -#include > +#include I'm not 100% sure, but is this really correct? Cheers, Frank -- http://frank.uvena.de/en/ pgpqixAosmLUl.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins: Updated POTFILES.in
Hi folks, I've updated the POTFILES.in for combined Geany-Plugins project based on output of find ./ -name "*.c". I kept the .h files which have been already be inside the list but would like to ask pliugin developers to double check whether all important files which might contain translatable strings are inside the list. Cheers, Frank -- Frank Lanitz pgpMooKi6YyN1.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Status of SM-Branch
Hi folks, I saw that the SM-branch is merged with trunk on a regular basis, but not sure what's the current status of that branch. Can someone help me out there? Cheers, Frank -- http://frank.uvena.de/en/ pgpocEgMznA6l.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Status of SM-Branch
On Thu, 30 Jun 2011 11:31:21 +0400 Eugene Arshinov wrote: > On Thu, 30 Jun 2011 08:02:48 +0200 > Frank Lanitz wrote: > > > Hi folks, > > > > I saw that the SM-branch is merged with trunk on a regular basis, > > but not sure what's the current status of that branch. Can someone > > help me out there? > > > > Cheers, > > Frank > > Hi Frank. > > Well, I periodically merge trunk into SM branch, because > > - I use SM branch myself and, at the same time, I want to try new > features which become available in Geany; > - the more often you perform the merge, the easier it is to resolve > conflicts (which occur rather often because SM contains many > changes). > > The status of the branch is a hard question :) This branch contains > > - session management support; > - minor improvements in project handling etc.; > - some experiments like frequent saving of recent file list to the > file, so that no recent files are lost when several Geany instances > are running side by side. > > Now > > - a better session management support is implemented by Dimitar (if a > decision is made to include session management in Geany, I'd prefer > this implementation to be chosen); > - experiments should not go to trunk in any case. > > So, the only useful thing in SM branch is the minor improvements. > Even if someone has time to discuss them and decide to include them > in trunk, it may be rather hard to cleanly extract the necessary > patches from SM so that they apply to trunk. Well, not sure and just a thought. Would it be possible to extract the little improvements so they could be merged to trunk? Can you give a more detailed view on the et? What do the improvements include? Cheers, Frank -- http://frank.uvena.de/en/ pgpxJj7FkAVFa.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Newsletter issues #3 final zone
Hi folks, I has been about two month since last release of the Geany newsletter and even not this much happened during this time I'm planning to do a new release by about first weekend of August so its the right moment for you to think whether you have something interesting, which might could be part of the next newsletter. Maybe a little how to or a new plugin you want to introduce. Please feel free and welcome to submit your article ;) Cheers, Frank -- http://frank.uvena.de/en/ pgpqlhLrJqxoB.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] POLL started (was: Re: Newsletter: Markuplangauge)
Hi, On Sat, 11 Jun 2011 01:16:06 +0200 Frank Lanitz wrote: > Next steps (just a few points): > Colomban did some nice work on creating the pdf from ReST a couple of > days ago. I will merge his changes into master and will start to > convert issue 1 and 2 to latest version so newsletter looks the same. This has been done with merging the working branch back into master. Cheers, Frank -- http://frank.uvena.de/en/ pgpM5cLGk7pKH.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany-plugins waf install is slow
On Sun, 17 Jul 2011 10:42:43 +0200 Thomas Martitz wrote: > has the waf install step gotten very slow for everyone, or only for > me? > > It takes 36s or longer here, and this laptop has an SSD. Well, I don't think this is caused by waf itself. How do other IO-actions, in special write actions, perform on your box? BTW: Installing took 3.4s here Cheers, Frank -- http://frank.uvena.de/en/ pgp2AM7oMEX8L.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Me, Geany and the future
On Wed, 10 Aug 2011 12:53:13 +0300 Dimitar Zhekov wrote: > > I'd like to find a new project maintainer who keeps the development > > going on, coordinate the project with the community, reviews patches, > > makes releases and so on. > > The first candidate is of course Colomban if he wants. > > Agreed. Where is Frank BTW? I will be still aboard but will not take over some rule in terms of reviewing and applying patches etc. I will keep on taking care at the translation of Geany as well as doing some work related to the plugins and newsletter. Of course from time to time I will add some code to the core but number r size of patches will not raise from level I currently do. There are a lot of reasons but most important is lag of time and a bunch of other projects I'm involved in. Cheers, Frank -- Frank Lanitz pgpRFBI4M8cp0.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Me, Geany and the future
On Tue, 9 Aug 2011 20:38:27 +0200 Enrico Tröger wrote: > If anyone wants to adopt the Addons plugin, I'd be happy. If not, I'd > continue maintaining it as well. As I already added some code to it in past I'd take it over. Cheers, Frank -- Frank Lanitz pgpfCH8PbPDow.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Me, Geany and the future
On Fri, 12 Aug 2011 09:42:22 +1000 Lex Trotman wrote: > Note: why not multiple instances? Can't edit different parts of the > same file, clashes over changing preferences, locking or corrupting > shared files... And don't forget Windows, where something like this is always challanging. Cheers, Frank -- Frank Lanitz pgpe1bOzkYIqO.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Me, Geany and the future
On Wed, 10 Aug 2011 23:38:24 +0200 Colomban Wendling wrote: > Fine with it, Frank already spoke about it and I and Dominic agreed with > him: we should release 0.21 soon (the meaning of this word being vague, > I guess it's OK to use it :D). Maybe end of September to leave the > summertime alone, leaving time for translation updates too. OK. Let's set the release date for end of September. Maybe: Release: October, 1st String freeze: September, 17th Feature freeze: September, 17th I will take care as usual about the i18n stuff. Cheers, Frank -- Frank Lanitz pgp7hHF7llUxx.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Broken geany-plugins build (was: Re: SF.net SVN: geany:[5882] trunk)
On Sat, 13 Aug 2011 15:18:18 +0200 Enrico Tröger wrote: > On Wed, 03 Aug 2011 15:20:26 +, colomb...@users.sourceforge.net > wrote: > > >Revision: 5882 > > http://geany.svn.sourceforge.net/geany/?rev=5882&view=rev > >Author: colombanw > >Date: 2011-08-03 15:20:26 + (Wed, 03 Aug 2011) > > > >Log Message: > >--- > >Only include config.h when building Geany > > > >config.h is not distributed, and we includ it from geany.h. Even > >though it was only included it HAVE_CONFIG_H was defined, an Autotools > >based build system is likely to define it, and it becomes a problem if > >that very build system uses another header name than config.h. > > > >Closes #3384026 > > While this was good to change, it broke building (probably) all plugins > of the geany-plugins project. > > We would need to add > #include "config.h" > to the plugins' main source files to fix the build. This should not be > a big problem in most cases, before I do that, I would just see if > there are any objections > > So, if any of the plugin maintainers, don't want that I touch their > code slightly, either tell me or fix it yourself. I hope I did fix it for all my plugins. Cheers, Frank -- Frank Lanitz pgpmh3t6FlbPd.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Broken geany-plugins build
Hi, On Sun, 14 Aug 2011 12:46:56 +0200 Hans Alves wrote: > El dom, 14-08-2011 a las 12:29 +0200, Enrico Tröger escribió: > > On Sat, 13 Aug 2011 17:12:08 +0200, Colomban wrote: > > However, some plugins compile without any change and without an > > inclusion of config.h. I'm not entirely sure why but leave this to the > > plugin authors. > > My plugin (GeanyPG) still worked, I think it is because i didn't add any > internationalization support yet, but i'm working on that now I should at > least be able to make spanish and dutch translations. However, I'm not > familiar with the whole generalization process, is there a document with > steps i need to take or some other guide? > Right now i placed all translatable strings in a _() macro, but i'm not > sure what to do next. A couple of day ago I've added some info to plugin howto. Please check http://www.geany.org/manual/reference/howto.html Maybe it solves a couple of oyur questions. Cheers, Frank -- Frank Lanitz pgpE4eP9LvZJ6.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Broken geany-plugins build
On Sun, 14 Aug 2011 22:27:13 +0200 Enrico Tröger wrote: > On Sun, 14 Aug 2011 11:37:42 -0700, Matthew wrote: > > Hola, > > >P.S. Above are you saying the Devhelp plugin *won't* build on your > >system or that it just didn't need any changes to build? I'm just > >wondering because I've received very little feedback on it, so maybe > >it's not building for people? > > Sorry for not being clear, on my system it is just because I have > libdevhelp in version 3.0.0 (Debian Testing, 3.0 is the only version > available) and the plugin wants 2.x. So I just couldn't test it > because of missing build requirements, not the plugin's fault :D. Unfortunately the same here. But I did use it for some time and liked it. Cheers, Frank -- http://frank.uvena.de/en/ pgpgG77CPcBLi.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Adding a list of filetypes intodevel documentation?
Hi folks, Last days I worked a bit using the filetype struct inside a plugin and I was searching for a constant for some special filetype. At the end (ok, I didn't search this much ...) I was able to find it inside filetypes.h, but wondering whether we might could add this (maybe automatic) somehow also to API reference. What do you think? Cheers, Frank -- http://frank.uvena.de/en/ pgpaQQkrldv6T.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Mon, 15 Aug 2011 09:57:01 -0700 Matthew Brush wrote: > There's a lot of stuff missing from the API reference, even entire > structs and some functions. So I think anything to make it even > slightly better would be good. I agree. As you you did a lot of work for your Python binding as well as there have been some discussion on the list, I like to ask you whether you might like to take over the challenge and provide a patchset (or a git maybe) with some improved API documentation? We could also set up a new branch on geany-svn > Another thing that would be really helpful is to add something to the > doxygen comments like '@since' and to put the plugin API number when > that function/member/struct became available. I'm not sure about. The most interesting number is die Geany main version as you want to build something up to recent Geany version. However, I do understand your suggestion with API number and IIRC we had something like this under discussion earlier. Cheers, Frank -- http://frank.uvena.de/en/ pgpjaUgYoBC8H.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Mon, 15 Aug 2011 10:45:30 -0700 Matthew Brush wrote: > On 08/15/11 10:21, Frank Lanitz wrote: > > On Mon, 15 Aug 2011 09:57:01 -0700 > > Matthew Brush wrote: > > > >> There's a lot of stuff missing from the API reference, even entire > >> structs and some functions. So I think anything to make it even > >> slightly better would be good. > > > > I agree. As you you did a lot of work for your Python binding as > > well as there have been some discussion on the list, I like to ask > > you whether you might like to take over the challenge and provide a > > patchset (or a git maybe) with some improved API documentation? We > > could also set up a new branch on geany-svn > > If I get some time, I could try and do this. Is anybody opposed to > putting the API docs in reStructuredText files and generating the API > docs using Sphinx? I've been using this for the Python bindings and > it's quite nice and easy, and there's support for C domain as well. I saw a nice talk about Sphinx a couple of month ago and wanted to have a look but didn't had any chance to. So at least I didn't do anything with it. > >> Another thing that would be really helpful is to add something to > >> the doxygen comments like '@since' and to put the plugin API > >> number when that function/member/struct became available. > > > > I'm not sure about. The most interesting number is die Geany main > > version as you want to build something up to recent Geany version. > > However, I do understand your suggestion with API number and IIRC we > > had something like this under discussion earlier. > > > > Which reminds me, should someone update the Plugin Howto so that it > checks for a API version number that's more up-to-date? Currently it > checks for 147, whenever that was. Yes, good point. Will do it. Cheers, Frank -- http://frank.uvena.de/en/ pgpuzj1tNacxo.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Tue, 16 Aug 2011 08:45:28 +1000 Lex Trotman wrote: > How would you show API and ABI info? I think: Since Geany 0.21 / API 221 or something like that. > IIRC the theory is that ABI > changes don't require unchanged plugins to be recompiled (for example > if a structure is extended) but API changes require at least > recompile. But I am not sure it is working that way though? No. ABI changes need a recompilation while API don't necessary do. Cheers, Frank -- http://frank.uvena.de/en/ pgp76tn6SNxgi.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Tue, 16 Aug 2011 21:01:42 +0800 Chow Loong Jin wrote: > On 16/08/2011 20:03, Thomas Martitz wrote: > > > > > > Correct. ABI changes do need a recompilation. API changes need > > nothing. > > > > Sometimes both the API and ABI "break", and then you need changes > > in the source and of course a recompilation. > > > > Extending a structure is ABI breakage if its size changes and the > > size is exposed (i.e. struct_ptr++ has a different effect in Geany > > and the plugin). That's why some projects pad structures to make > > extensions not change the size. > > Doesn't an API change need a code change as well? For example, if you > changed the number of arguments a function took.. AFAIK that's both > API and ABI breakage. Yes. This will increase API and ABI change and on recompiling it won't compile due wrong signature. Cheers, Frank -- http://frank.uvena.de/en/ pgpiFj5dkwbPE.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Tue, 16 Aug 2011 22:53:23 +0200 Colomban Wendling wrote: > Le 16/08/2011 10:05, Lex Trotman a écrit : > > On 16 August 2011 12:19, Matthew Brush wrote: > >> On 08/15/2011 03:45 PM, Lex Trotman wrote: > > If I get some time, I could try and do this. Is anybody opposed > to putting > the API docs in reStructuredText files and generating the API > docs using Sphinx? I've been using this for the Python bindings > and it's quite nice and easy, and there's support for C domain > as well. > > >>> > >>> I personally don't care, but being cautious, can you provide a C > >>> example? > >> > >> Sure thing: > >> http://codebrainz.github.com/geany-sphinx/ > > > > Nice, so I read the Sphinx doco (havn't looked at it for a while) > > but IIUC either you have to repeat the C declarations that appear > > in the documentation or use doxygen and breathe to extract it. > > > > 1. The repeat option is unacceptable. > > > > 2. Although the output is nice I don't see enough is gained by the > > second option to justify having to use two tools (sphinx and > > breathe) on top of the current one (doxygen). > > > > So at the moment I don't see that this justifies the change. > > +1 here, but I'd be fine to be proven wrong. But anyway copying the > function signature or any other information that could be > automatically found by Doxygen, GtkDoc or whatever > source-comment-and-analysis-based documentation tool is not an > option. This kind of thing would be the easiest way to have > documentation and code out-of-sync. I agree. Documentation and Code shall not be split. Not sure whether Sphinx can do this for C. Cheers, Frank -- http://frank.uvena.de/en/ pgpKp7msIgaO3.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Mon, 15 Aug 2011 19:19:35 -0700 Matthew Brush wrote: > I probably don't understand the topic enough, but to me, it would be > cool to say: > > PLUGIN_VERSION_CHECK(0, 20, 42) > > To mean: "This plugin will only work on the 42nd API change since the > 0.20 release or later". This will end up in a real mass and will cause some unneeded maintenance effort on plugin side. So e.g. would be a (0, 21, 45) something like (0, 20, 87)? You got the point? > And the Doxygen comments for an API function > could look like: > > /** >* Does something to foo with bar. >* @since 0.20.42 >*/ > void baz(int foo, int bar); > > Or at least something along these lines, so that it relates to > release version numbers of Geany. Would be great to then get a macro > like GLib/GTK has: > > #if GEANY_VERSION_CHECK(0, 20, 42) > baz(1, 2); > #else > /* Do nothing on older APIs */ > #endif > > Just some thoughts, I have no idea if it's realistic. I disagree. I'm fine to put some information about API revision inside documentation also, but I don't see any need to check for Geany version inside a plugin. Goal of plugin development is to work with certain Geany versions and upcoming ones. (There might be some special case, but in general). I vote to keep the normal incremental API number as this is enough for a plugin author to know. Only the API version per release could be a nice information. Cheers, Frank -- http://frank.uvena.de/en/ pgpsx1kN5pqDj.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] List of Plugin API/ABI versions vs. Geany version inside Wiki
Hi devs, I've just put a list with Geany version and its fitting API/ABI version into wiki. I hope its correct as I harvest them from svn tags :) However, you can find it at: https://wiki.geany.org/plugins/development/api-versions for the meanwhile. Cheers, Frank -- http://frank.uvena.de/en/ pgpYA0sNgA5P2.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] How to demark words from inside a plugin
Hi folks, Today I'm looking for a nice way how to unmark words which have been marked with Geany's GEANY_KEYS_SEARCH_MARKALL. Does anybody of you know a way through plugin API or do I need to hack something? ;) Cheers, Frank -- http://frank.uvena.de/en/ pgpJjtSyGpo8u.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Wed, 17 Aug 2011 15:37:15 +1000 Lex Trotman wrote: > 2. structures should not be visible in the interface, instead they > should be hidden behind getter/setter functions, and > > 3. interface wrapper functions should be used to hide the > implementation and side effects. > > The last two have not been Geany policy to date but I now propose > that they be. I guess this will change the way plugin developers currently working with the API. Give that this will stabilize the ABI even more I would second this. Can you go a bit more into detail what would need to be changed here? Cheers, Frank -- http://frank.uvena.de/en/ pgpMw3juRpax8.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] How to demark words from inside a plugin
On Wed, 17 Aug 2011 20:20:14 +0200 Enrico Tröger wrote: > On Wed, 17 Aug 2011 18:07:06 +0200, Frank wrote: > > >Hi folks, > > > >Today I'm looking for a nice way how to unmark words which have been > >marked with Geany's GEANY_KEYS_SEARCH_MARKALL. Does anybody of you > >know a way through plugin API or do I need to hack something? ;) > > GEANY_KEYS_DOCUMENT_REMOVE_MARKERS A cool. Missed that. And there is already a keybinding available... hmmm... Cheers, Frank -- http://frank.uvena.de/en/ pgpMRuXb0xYjV.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Wed, 17 Aug 2011 12:09:53 -0700 Matthew Brush wrote: > This isn't as bad as it sounds, but at this point I don't think it's > very important anyway, the current API docs are, for the most part, > pretty good. My only complaint is that the structs/typedefs are > documented in the header files and functions are documented in the > source files, but I guess there advantages to this also. Well, source files are parsed by doxygen. Why not adding the missing documentation and ensuring, doxygen is fetching them when running make apidoc? (not sure whats missing to have this full work.) Cheers, Frank -- http://frank.uvena.de/en/ pgpsRfT3Wu5pX.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Wed, 17 Aug 2011 11:34:11 -0700 Matthew Brush wrote: > +1 ... Franks list on the Wiki is an great start! Thx ;) > IMO, it's quite useful/important that each function/member's > doc-comments be annotated with the API version number as well, as has > been discussed. This would let developers reading the API docs know > *exactly* which API version they should check against to use a > certain thing, even between releases. I disagree on the between releases point. Plugin developers are asked to develop against latest stable release of Geany. If they need something more recent, they know what they are doing. My suggestion is to add this information with next API extensions. If somebody likes to dig into source history and check, which API version which API call is needed, I'm also fine with ;) Cheers, Frank -- http://frank.uvena.de/en/ pgpA51CYEez9E.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Wed, 17 Aug 2011 12:28:17 -0700 Matthew Brush wrote: > On 08/16/2011 11:38 PM, Frank Lanitz wrote: > > On Mon, 15 Aug 2011 19:19:35 -0700 > > Matthew Brush wrote: > > > >> I probably don't understand the topic enough, but to me, it would > >> be cool to say: > >> > >>PLUGIN_VERSION_CHECK(0, 20, 42) > >> > >> To mean: "This plugin will only work on the 42nd API change since > >> the 0.20 release or later". > > > > This will end up in a real mass and will cause some unneeded > > maintenance effort on plugin side. So e.g. would be a (0, 21, 45) > > something like (0, 20, 87)? You got the point? > > > > Unfortunately I don't understand your point :( > > It's not really important anyway, I just think in general it would be > nice to have it be easier to make new plugins work with older Geany > versions. > > Probably the biggest problem I've had is not being able to check if > GEANY_API_VERSION is < 200, but this will be less and less of an > issue over time :) As discussed on some other place this is most likely something needs to be done on compiletime and, well, I don't see any reasons why coding for Geany 0.19 or 0.18. Cheers, Frank -- http://frank.uvena.de/en/ pgpqiVxSYHezY.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Wed, 17 Aug 2011 12:38:49 -0700 Matthew Brush wrote: > On 08/17/2011 12:26 PM, Frank Lanitz wrote: > > On Wed, 17 Aug 2011 11:34:11 -0700 > > Matthew Brush wrote: > > > > >> IMO, it's quite useful/important that each function/member's > >> doc-comments be annotated with the API version number as well, as > >> has been discussed. This would let developers reading the API > >> docs know *exactly* which API version they should check against to > >> use a certain thing, even between releases. > > > > I disagree on the between releases point. Plugin developers are > > asked to develop against latest stable release of Geany. If they > > need something more recent, they know what they are doing. > > > > I never heard this advice before, but I guess it's good advice. > Though I still think from a user's point of view, the wider range of > Geany versions supported by a plugin, the better. I agree at this point. The only way currently is to use older API calls. Most of the new functions do already have a since entry, e.g. since 0.16. If you chose 0.19 and below it will work for 0.19 and 0.20. Burt as of the ABI change you will need to recompile it. Reasons for this have been discussed elsewhere. Cheers, Frank -- http://frank.uvena.de/en/ pgprkN41I9MZf.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Wed, 17 Aug 2011 12:39:17 -0700 Matthew Brush wrote: > On 08/17/2011 12:30 PM, Frank Lanitz wrote: > > > > > As discussed on some other place this is most likely something > > needs to be done on compiletime and, well, I don't see any reasons > > why coding for Geany 0.19 or 0.18. > > > > Because a lot of people use packages from their distro, which may be > quite out of date (ex, up to 2 years for Ubuntu LTS), so they might > still be using one of those older versions. I understand your thoughts here. Its the old issue with outdated packages here. Most of them will not compile their plugins at their own and the distribution will most likely not add new plugins. Debian is having backports for such matters, but Ubuntu is missing something like that (at least I know of). I don't know how SuSE, RH/Fedora, * is handling this, but they could use it to also updated Geany. However, once a user is compiling its own plugin, they can also compile Geany. The dependencies are most likely similar and the efforts not much bigger, once you have set up gcc, libgtk2-dev etc. Cheers, Frank -- http://frank.uvena.de/en/ pgpcVNaNpAaiP.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Thu, 18 Aug 2011 12:01:09 +1000 Lex Trotman wrote: > Oh yeah the wiki, I forgot about that :-) > > @Enrico, When will it be declared online, ie prominently pointed to > from the website? There will be a note inside the next newsletter. Cheers, Frank -- http://frank.uvena.de/en/ pgp25oZh96VTx.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Thu, 18 Aug 2011 17:14:10 +1000 Lex Trotman wrote: > > However, once a user is compiling its own plugin, they can also > > compile Geany. The dependencies are most likely similar and the > > efforts not much bigger, once you have set up gcc, libgtk2-dev etc. > > Why would we expect a PHP or Python developer on Windows to have the > ability to build plugins, they would have to set up the whole mingw > thing as well as compiler and gtk and other tools. Huge disincentive. We talked about outdated distribution as e.g. Ubuntu LTS. A windows dev could use latest stable release of plugins and Geany as provided on homepage or nightly. Cheers, Frank -- http://frank.uvena.de/en/ pgpRDxfnbdpNO.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Wed, 17 Aug 2011 22:16:00 -0700 Matthew Brush wrote: > On 08/17/2011 08:56 PM, Lex Trotman wrote: > > [...] > >> > >> That was *extremely* useful information, you should put that on > >> the Wiki too :) > >> > > > > Sure if no one says its wrong. > > > > Only thing left out is how there's a separate struct for each set of > function types, like `DocumentFuncs`, and `SciFuncs`, and so on, > which are themselves members of a the `GeanyFunctions` struct. Just > to add a little more detail. I'd suggest just start to put the things into wiki. Its much easier to check and correct something over there instead of discussion on mailing list without having some fixed version. Cheers, Frank -- http://frank.uvena.de/en/ pgppqZrf8cKJZ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Wed, 17 Aug 2011 22:16:00 -0700 Matthew Brush wrote: > Agreed, something like: > > /* >* Does stuff with bar >* @param bar A bar to perform foo on. >* @return A new baz >* >* @since 0.21 (<= API v212) >*/ > baz_t *foo(bar_t *bar); +1 Cheers, Frank -- http://frank.uvena.de/en/ pgpFNNObSS6u3.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Thu, 18 Aug 2011 18:21:04 +1000 Lex Trotman wrote: > > We talked about outdated distribution as e.g. Ubuntu LTS. A windows > > dev could use latest stable release of plugins and Geany as > > provided on homepage or nightly. > > You are right, windows stuff is under our control and shame on us if > we get them out of sync. BTW when is the Geany plugins release for > Geany 0.21 going to be? :-D I was thinking about short after 0.21 Geany release. > But even so we shouldn't make the assumption that every Linux user is > a C developer and shouldn't force them to be one if their distro is a > bit behind, especially with plugin packages. Well, there are only two possibilities that count IMHO: 1. compiling on their own: Once compiling your plugins package, you can do also Geany 2. The distributor is providing recent Geany packages. So its his topic to provide also fitting packages for the plugins. (most ikely just recompiling against the Geany version he is offering) We cannot offer packages for distributions and their different arch and versions IMHO. Think of libc, glibc, gtk > IIRC Suse has their factory where things can be built, not just for > Suse, but for debian, fedora etc. Those repos seem to have 0.18.1 and > 0.20 for all versions but only plugins for 0.20. I had a talk with a couple of people during the weekend (Chaos Communication Camp) and well... their feedback was quiet unfriendly about the build service. (As kids might also reading this list, I will not translate the words they did use) > OTOH I still use a distro based on Ubuntu LTS (10.04) but 0.20 is > available in the package manager via the underlying debian packages. So plugins are too I assume? Cheers, Frank -- http://frank.uvena.de/en/ pgp7HDUZ5D7rC.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Thu, 18 Aug 2011 18:45:09 +1000 Lex Trotman wrote: > >> But even so we shouldn't make the assumption that every Linux user > >> is a C developer and shouldn't force them to be one if their > >> distro is a bit behind, especially with plugin packages. > > > > Well, there are only two possibilities that count IMHO: > > 1. compiling on their own: Once compiling your plugins package, you > > can do also Geany > > But why do we force them to compile? We should use our best endeavors > to keep old plugins working, especially if there is any delay in > getting plugins released. From time to time you have to break the ABI. To reduce number of breakings is discussed on other point. Right now its like that. Cheers, Frank -- http://frank.uvena.de/en/ pgpbusFu049BQ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Adding a list of filetypes into devel documentation?
On Thu, 18 Aug 2011 12:11:57 +0200 Frank Lanitz wrote: > On Thu, 18 Aug 2011 18:45:09 +1000 > Lex Trotman wrote: > > > >> But even so we shouldn't make the assumption that every Linux > > >> user is a C developer and shouldn't force them to be one if their > > >> distro is a bit behind, especially with plugin packages. > > > > > > Well, there are only two possibilities that count IMHO: > > > 1. compiling on their own: Once compiling your plugins package, > > > you can do also Geany > > > > But why do we force them to compile? We should use our best > > endeavors to keep old plugins working, especially if there is any > > delay in getting plugins released. > > From time to time you have to break the ABI. To reduce number of > breakings is discussed on other point. Right now its like that. Well, I think there have been a number of ideas to decrease the number of ABI breaks in future. Why not adding this as main goal for 0.22: Enhancement of plugin API Cheers, Frank -- http://frank.uvena.de/en/ pgp2ksNm9FpAz.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany on github; why not?
On Fri, 19 Aug 2011 00:23:42 -0500 Josh wrote: > The subject says it all; why shouldn't we move geany to github? I'm > willing to help with the migration, especially this weekend. I'd also > like to note that we could continue to use svn > (https://github.com/blog/626-announcing-svn-support and > https://github.com/blog/644-subversion-write-support) if we'd like, > but we'd get plenty of features for free. Like I said I'd like to > help get this going, so if we all agree, let's do this! Please check the archive of this mailing list. There have been tons of discussion. Personally I don't want to bring this up at the moment again, as there are a bunch of other topics under heavy discussion. Cheers, Frank -- http://frank.uvena.de/en/ pgp9ZYqSsO3rL.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Fri, 19 Aug 2011 10:02:23 +1000 Lex Trotman wrote: > > > > IMO Geany should use the exact same API than plugins to do one > > thing. > > Of course Geany should call the wrapper too. Basically its ok for > Geany to do implementation stuff directly, but only if its in one > place. As soon as it is in the API it isn't one place any more. Depending on the part of Geany, its really already doing this. But surely a couple of places might be missing and useful to do it the same wa< there. > > This would avoid having a broken getter in the API (or whatever) > > that we don't notice just because the core doesn't use it. > > With the past non-proactive adding of things to the API there should > not be too much in that category, but over time it may accumulate as > we add more but don't remove stuff so we don't break the ABI. Well, I don't think this is a reason for using the same functions in core, but a good one to use a test framework which is testing the API maybe as a post commit hook. > PS probably be a week or so before I get time to put stuff in the wiki Looking forward to. Cheers, Frank -- http://frank.uvena.de/en/ pgpspwtDFnpJO.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Fwd: Geany: Cython Keywords
On Fri, 19 Aug 2011 03:00:06 -0700 Matthew Brush wrote: > Patch forwarded from AlekzE from IRC to add some more missing Cython > keywords. Has been applied with svn r5892. Please check. Cheers, Frank -- http://frank.uvena.de/en/ pgpIEK2LGKIvl.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany on github; why not?
On Fri, 19 Aug 2011 08:57:36 -0500 Josh wrote: > @Lex: That makes sense. After this weekend I'll still have time, but > it'll be more sparse. I'd like to be a part of it; so let me know what > we/I need to do to get this going. Thanks! 1st step: We need to check for points the new system needs to offer (just because github is cool at the moment, I would have a bad feeling if we don't think about what we need before doing anything) and which system might could solve them. There is at least github, gitourios and google code if we just have a view onto git. There are also a couple of services offering hg or bzr which are pretty similar to git. So pretty much I'm looking for a specification sheet with possible matches for solution. I suggest to collect this inside the wiki. 2nd step: Decide which system fits best (doodle maybe) 3rd step: Collect what needs to be done in terms of transition. Maybe you can use the wiki for. 4th step: Setting up plan. Cheers, Frank -- Frank Lanitz pgp9knPSzAcfN.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany on github; why not?
On Fri, 19 Aug 2011 15:08:16 -0700 Matthew Brush wrote: > On 08/19/2011 02:11 PM, Frank Lanitz wrote: > > On Fri, 19 Aug 2011 08:57:36 -0500 > > Josh wrote: > > > >> @Lex: That makes sense. After this weekend I'll still have time, but > >> it'll be more sparse. I'd like to be a part of it; so let me know what > >> we/I need to do to get this going. Thanks! > > > > 1st step: We need to check for points the new system needs to offer > > (just because github is cool at the moment, I would have a bad feeling > > if we don't think about what we need before doing anything) and which > > system might could solve them. > > According to the long drawn-out discussions we've had for some time on > this topic, I felt the overwhelming opinion was to use Git for version > control. As for your concerns about GitHub, it's important to remember > that it's just a server to host one of the repositories. They could go > offline a week after switching and we would still have all of our code > and history. The main reasons people are mentioning GitHub is because > it's extremely popular, developer friendly, and a lot of open source > projects are hosting their code there. > > > There is at least github, gitourios and google code if we just have a > > Nope, I think it's just GitHub and Gitorious if we want > contributor-friendly Git project hosting. I don't think Google Projects > does Git at all. I understand this. But, and maybe I'm a bit to demanding here, I would really like to see some clean collection at which somebody really thought about this. I was seeing to many things on FLOSS and related projects, where some decision was made by some feeling from mailinglist and at the end nobody felt responsible or nobody remembering the reasons. I want to prevent this at a point where we do have a chance to. > > view onto git. There are also a couple of services offering hg or bzr > > Except most of the developers don't already know and use Mercurial or > Bazaar as much Git (I think). The basic feeling is the same in terms of commit, push and pull. They are all dvcs. ;) > > which are pretty similar to git. So pretty much I'm looking for a > > specification sheet with possible matches for solution. I suggest to > > collect this inside the wiki. > > > > We could do this, but it's just more "beating around the bush". We > already did have long discussions about this in multiple threads and I > think everyone who would like to contribute (besides yourself?), at > least those who have spoken up, would prefer Git and a better project > site. How much more discussion is needed? > > IMO, the only remaining questions are: > > 1) GitHub or Gitorious or Other (maybe a poll needed?) > 2) When (maybe after next release) > 3) Does anyone actually like or want to keep using SVN/SourceForge/the > current development process? I don't want to impolite so I'm just asking for two things to everybody: 1.) Who likes to take over responsibility? (yepp, I really asking for a project manager here) 2.) Can you please careful clean the facts and put them together as I suggested (was demanding ;) ) in one of my previous postings. At the end, this needs to be done anyway (and you are right. Making the long discussions on mailing list short it really was a huge pro for some git based solution and the next open question would be were to host) - but I really like to have a clean documentation of facts ;) Cheers, Frank P.S. And yes, I still don't see any good reasons for a change as the issues we currently are experiencing, e.g. low an resources for code review will not be solved by any VCS IMHO. I might be wrong, but these are my thoughts. It just doesn't matter how patches are coming in, we need people reviewing them and applying them to main tree. We need people taking care on special parts of Geany as the libsm stuff and other open points and we need less novelistic discussion on mailing list but good usage of wiki. But these are just my 2ct. -- Frank Lanitz pgp6Nzc0aTcwq.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany on github; why not?
On Fri, 19 Aug 2011 16:40:21 -0700 Matthew Brush wrote: > With the current way we do things, no one even *can* take care of > special parts because only 2 or 3 people have commit access and it's a > PITA to contribute by squashing all your commits into a patch and > bumping the ML till one of those 2 or 3 people have time to act on it. > With a more open/social-type project site, you'll get people making > forks to implement a feature, then they'll make a pull request, which > others will see and then they will try this feature and test it, and so > on. All of this can happen without having to wait for one of the 2 or 3 > committers to review and apply a patch. I'm afraid you got me wrong. I was looking for somebody saying, I'm feeling responsible for XYZ. Adding them to commiters list on SF currently is not a big deal. Even its sometimes a pain in the ass, also branching on svn is possible and working. So I'm not talking about sending patches, but feeling responsible and taking care of which differs a lot IMHO. Cheers, Frank -- Frank Lanitz pgpZwy2IBn0XZ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Plugin Version control (explained?)
On Sat, 20 Aug 2011 17:18:24 +0200 Colomban Wendling wrote: > Le 19/08/2011 08:40, Frank Lanitz a écrit : > > On Fri, 19 Aug 2011 10:02:23 +1000 > > Lex Trotman wrote: > > > > [...] > >>> This would avoid having a broken getter in the API (or whatever) > >>> that we don't notice just because the core doesn't use it. > >> > >> With the past non-proactive adding of things to the API there should > >> not be too much in that category, but over time it may accumulate as > >> we add more but don't remove stuff so we don't break the ABI. > > > > Well, I don't think this is a reason for using the same functions in > > core, but a good one to use a test framework which is testing the API > > maybe as a post commit hook. > > Would be really good. Not sure how to do this however, we'd need to > spawn Geany, load a test plugin… any idea? Unfortunately no. I put it on the help wanted for page on every talk I was doing for Geany but nobody was asking me to help ;) > I'm afraid we can't do a classic suite of unit tests since we don't have > real "units" (maybe we should, but that's another problem...). h... Cheers, Frank -- Frank Lanitz pgp3ooLOganbI.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SF.net SVN: geany-plugins:[2161] trunk/geany-plugins/debugger
On Mon, 22 Aug 2011 00:33:50 + cess...@users.sourceforge.net wrote: > Revision: 2161 > > http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=2161&view=rev > Author: cesspit > Date: 2011-08-22 00:33:50 + (Mon, 22 Aug 2011) > > Log Message: > --- > debugger: odd files removed Unfortunately this is not compiling on waf here: [116/172] c: debugger/src/gui.c -> _build_/debugger/src/gui.c.1.o [117/172] c: geanycfp/src/geanycfp.c -> _build_/geanycfp/src/geanycfp.c.1.o ../debugger/src/gui.c: In function 'create_button': ../debugger/src/gui.c:35:48: error: 'DBGPLUG_DATA_DIR' undeclared (first use in this function) ../debugger/src/gui.c:35:48: note: each undeclared identifier is reported only once for each function it appears in ../debugger/src/gui.c: In function 'create_toggle_button': ../debugger/src/gui.c:69:48: error: 'DBGPLUG_DATA_DIR' undeclared (first use in this function) ../debugger/src/gui.c: In function 'set_button_image': ../debugger/src/gui.c:86:48: error: 'DBGPLUG_DATA_DIR' undeclared (first use in this function) Cheers, Frank -- http://frank.uvena.de/en/ pgpKo1ATwTctE.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany on github; why not?
On Tue, 23 Aug 2011 15:21:40 +1000 Lex Trotman wrote: > @All, what about plugins? I guess, once we did this for core, plugins should be switched also. But here it will need some further discussion as what you are defining a atomar project / what shall be T for the DVCS. Cheers, Frank -- http://frank.uvena.de/en/ pgp7h9QlkdSR1.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany Newsletter Vol. 3
g option is similar to Line Breaking but the lines are only wrapped visually; no carriage returns or line feeds are added. This option is best used when you want to be able to see the entire file within the current window. So that it's obvious which lines have been wrapped, a visual indicator is added to the end of each wrapped line. Line Wrapping is very CPU-intensive and can slow down Geany if it's enabled while editing a very large file. If you prefer to have Line Wrapping enabled by default, there is an option for this in the Preferences dialog box Editor > Features. With this option enabled, you can disable Line Wrapping via the menu option Document > Line Wrapping. People behind Geany -- Interview = This is the first 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. Columban Wendling ^ Thank you to Colomban Wendling for agreeing to an interview and congratulations for being the very first. Now on to the questions... *What motivates you to develop Geany?* I use Geany on a daily basis, so I'm concerned about its development and improvement. I'm also happy to give back a little bit of all the good Geany given me through the years I used it :) And don't be silly: the FAME! :D *Why do you develop for free instead of devoting this time to paid projects?* Philosophy, naivety... Actually I don't "develop for free" if it only means "without being paid", I develop for free "as in freedom" software because I like the ideology behind it. Not being paid is only a concern in the way I need to do some other stuff beside to get money in. What I probably prefer in free software is the fact one can learn from reading the code. It was a great source of help and knowledge when I started learning programming, and it still is. A related thing is the ability to modify the software to better fit my needs, or simply to fix a bug that concerns me. It serves me from time to time (once I discover an annoying bug ^^) and allows me to send back the fix to upstream developers, hopefully helping other users. I won't give all the philosophy behind free software, I think you've got my point :) *Do you do development on other projects that are of interest to you?* Not really beside my personal projects. As said above, I send patches from time to time to developers of software I use, but I'm not really involved in any other project than Geany. *Do you have a favourite Geany feature and if so, what is it?* Most probably the tag completion; but also that almost everything is configurable to fit ones needs. *Do you have a favourite Geany plugin and if so, what is it?* If I'd not fear to sound selfish, I'd say GeanyGenDoc :D Otherwise, SpellCheck without a doubt. *What do you do when you're not developing Geany?* I continue studying programming, or work on personal projects though it's almost the same thing. *What do you use Geany for?* Every one of my programming tasks, and some other text editing. *Do you use any editors other than Geany? (Of course the answer here should be "Absolutely not!" but I'm asking it anyway. :)* I use Nano for commit messages and administration tasks I need to do as root, but for all serious text editing I use Geany. *In which environments do you use Geany?* GNU/Linux (with GNOME), and occasionally Windows (but only when I'm forced to use Windows). 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, Russell Dickenson pgptIEPuJUZLd.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geany-Plugins 0.21: Release plan
Hi plugin developers, As we discussed a release for Geany 0.21 around October, 1st I'm thinking also that it would make sense to do a geany-plugins release around this time. Unfortunately I'm not sure, beside the string freeze and translation stuff, which goals need to be matched until release. What do you think? If there are no show stopper I suggest a cycle 2 weeks after Geany core, so release date would be October, 15th. Any opinions? Cheers, Frank -- http://frank.uvena.de/en/ pgpPwJZmZzFyP.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins 0.21: Release plan
On Wed, 24 Aug 2011 00:28:54 +0200 Dominic Hopf wrote: > Am Dienstag, den 23.08.2011, 11:47 +0200 schrieb Frank Lanitz: > > Hi plugin developers, > > > > As we discussed a release for Geany 0.21 around October, 1st I'm > > thinking also that it would make sense to do a geany-plugins release > > around this time. Unfortunately I'm not sure, beside the string > > freeze and translation stuff, which goals need to be matched until > > release. What do you think? > > The project at least should successfully build. I agree. Also I would like to put focus on documentation as some parts are ... well... undocumented. > At present it doesn't, it seems, see attached output. I reported these errors earlier this week but no feedback by now. Cheers, Frank -- http://frank.uvena.de/en/ pgplxlLuvMzjY.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins 0.21: Release plan
On Wed, 24 Aug 2011 07:01:54 +0200 Frank Lanitz wrote: > On Wed, 24 Aug 2011 00:28:54 +0200 > Dominic Hopf wrote: > > > Am Dienstag, den 23.08.2011, 11:47 +0200 schrieb Frank Lanitz: > > > Hi plugin developers, > > > > > > As we discussed a release for Geany 0.21 around October, 1st I'm > > > thinking also that it would make sense to do a geany-plugins > > > release around this time. Unfortunately I'm not sure, beside the > > > string freeze and translation stuff, which goals need to be > > > matched until release. What do you think? > > > > The project at least should successfully build. > > I agree. Also I would like to put focus on documentation as some parts > are ... well... undocumented. Another release goal is not to have any critical warnings/errors on compile time with waf and autotools. Cheers, Frank -- http://frank.uvena.de/en/ pgp1baAtV99g8.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Git for plugins (was: Re: geany on github; why not?)
On Wed, 24 Aug 2011 23:56:52 +0200 Jiří Techet wrote: > About plugins - I'd like to see them converted to git too but for me > it's much less important. Plugins are usually one-man-show and require > much less cooperation than Geany itself and their authors already have > SVN access. Due the huge number of contributors at the plugins project and the, well quiet often broken build, a more decentralized process would be good for the plugins. We talked about this a couple of days ago inside IRC and we came to that point, that it would be might useful to make more usage of branches and only merge to trunk, when its apply correct and build is not broken and some other points of policy is met - Well I'm imagine a bit the Linux Kernel development model even of course the plugins are not that big - not yet ;) This could be done on svn its a bit a more complicated so maybe a git (or brz, hg) would be useful here. But this is something for post-21-plugins release. Cheers, Frank -- http://frank.uvena.de/en/ pgpsdqq4CiKVz.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SF.net SVN: geany-plugins:[2161] trunk/geany-plugins/debugger
On Thu, 25 Aug 2011 00:37:47 +0400 Alexander Petukhov wrote: > fixed. Approved ;) But still get an compiler warning with waf (@AMD64) ../debugger/src/dconfig.c: In function 'dconfig_save': ../debugger/src/dconfig.c:264:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] Cheers, Frank -- http://frank.uvena.de/en/ pgpGAbhyvg1yo.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] geany on github; why not?
On Wed, 24 Aug 2011 23:56:52 +0200 Jiří Techet wrote: > It's not perfect - the branches aren't "glued" to the trunk in merge > points and the tags are squashed with the previous commits which I > don't like but it gives you an idea how a complete Geany's history > looks like. Is there a way to prevent from such things? Cheers, Frank -- http://frank.uvena.de/en/ pgpNLaLOGdnrd.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Git for plugins (was: Re: geany on github; why not?)
On Thu, 25 Aug 2011 15:51:24 +1000 Lex Trotman wrote: > [...] > > Due the huge number of contributors at the plugins project and the, > > well quiet often broken build, a more decentralized process would be > > good for the plugins. We talked about this a couple of days ago > > inside IRC and we came to that point, that it would be might useful > > to make more usage of branches and only merge to trunk, when its > > apply correct and build is not broken and some other points of > > policy is met - Well I'm imagine a bit the Linux Kernel development > > model even of course the plugins are not that big - not yet ;) > > Only a minor change to your new name, Frank Linus? > > > This could be done on svn its a bit a more complicated so maybe a > > git (or brz, hg) would be useful here. But this is something for > > post-21-plugins release. > > Yes, with DVCS each plugin can have its own repository and the Geany > project only needs to manage the aggregated build. Yes, this was the outcome on IRC. So once a feature is ready/bug has been fixed a pull request is send to maintainer who is including them into his/her tree. Once this has been done a snapshot of that tree will be the release. > The rule would be > like the Linux one, don't break Franks tree :-) ;) Yepp. > Looks like the policy needs include 64 bit test builds (at least until > the int/pointer errors go away). I agree. I'd like to have also some tests on PPC and IA64. At least a PPC (G4 or G5 Mac) I have here (only I need is somebody who is able to set it up) Cheers, Frank -- http://frank.uvena.de/en/ pgpwaCHIsCmtS.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] Geanyembrace: Anybody who like to maintain it?
Hi folks, I had a short email conversation with Prim András the original author of geanyembrace.He did not touch this plugin for quiet a long time and doesn't plan to do so in future. Does anybody of you use the plugin and might like to become maintainer? If not, what we going to do with it? Cheers, Frank -- http://frank.uvena.de/en/ pgp2hy70ZdefZ.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
