Devel November 2011

devel@lists.geany.org

21 participants
40 discussions

Unit tests for Geany (continued from Github)
by Nathan Broadbent 01 Dec '11

01 Dec '11

(continued from github - https://github.com/geany/geany/pull/15) > I don't think any of Geany's developers will argue that having some sort of unit testing would be a good idea, especially for the plugin API, but mainly it boils down to: > > 1) What framework to use (Geany is written in plain C). >From the Stack Overflow question "Is Google Test OK for testing C code?" (http://stackoverflow.com/a/6218365/304706) : It is pretty common to test C code using a C++ testing frameworks, even the leading book on the subject (http://pragprog.com/titles/jgade/test-driven-development-for-embedded-c) follows this approach. I have used googletest extensively in the past to unit test C code and can recommend it. I have written a blog post about it that might be useful: http://meekrosoft.wordpress.com/2009/11/09/unit-testing-c-code-with-the-goo… ... As long as your headers are C++-compatible (not using C++ keywords, export symbols with correct linkage), it should be fine. > 2) How do you run unit tests on a live GUI application with no libraries (surely there's a way). I don't have much experience, so I can't offer any suggestions. But I can do the research. > 3) Who's going to do it :) > > If you want to help with this, I'm sure it would be appreciated. I could help start it off, but it would have to be an on-going thing. I wouldn't have the time to sit down and write tests for the whole application. Each developer could get into the habit of writing a test whenever they change something or add a new feature. > The only real restriction IMO is that it not add any dependencies to the > application or build system under normal conditions. For example, it would be a bummer to make Joe Hacker have to install some exotic > unit testing framework libraries just to do a `make && make install`. I totally agree with not adding dependencies under normal conditions, and I don't think that will be an issue if the code is written well. Test-driven development often enforces particular design patterns, so there will probably need to be some refactoring involved. ------------- To be honest, the real reason that I started talking about unit tests, is because I really need them in order to write a lexer for scintilla. Manual testing for lexers would be a nightmare. <editor_rant> Also to be honest, I'm still a little conflicted with regards to gedit vs. geany vs. others. Gedit uses GTKSourceView, which has definitions for many more languages, but their lexers are XML / Regex based. So they're really slow for larger files, and they don't support code folding, which I'm starting to get used to. But their community seems to be a lot bigger, and a little more active. I also experimented with an editor called 'Redcar' which now appears to be the worst of both worlds... It uses GTKSourceView, plus the main editor is written in Ruby... Ruby might be my favorite language, but it's damn slow. So yeah, I've tried everything from vim to Eclipse, but so far, only Geany seems to have the right balance. So I'd like to put in some effort to make this editor better - after all, I'm going to be using it for 8 hours a day. </editor_rant> Cheers! Nathan P.S. The documentation needs to be updated for the 'waf' build system, in quite a few places, including geany-plugins.

6 16

Re: [Geany-devel] Unit tests for Geany (continued from Github)
by Matthew Brush 30 Nov '11

30 Nov '11

Sent off-list on accident due to email client issues, forwarding back on-list. On 11/30/2011 12:10 AM, Thomas Martitz wrote: > Am 30.11.2011 08:39, schrieb Matthew Brush: >> On 11/29/2011 11:12 PM, Frank Lanitz wrote: >>> Am 30.11.2011 07:36, schrieb Nathan Broadbent: >>>> P.S. The documentation needs to be updated for the 'waf' build system, >>>> in quite a few places, including geany-plugins. >>> >>> I don't refer to other points as I would need to catch up discussion on >>> github before (wth why are we using differnt chanels? can we turn off >>> the github commenting stuff.. its a nightmare) >>> >> >> It's not a nightmare if you use it. Comments are essential for code >> review, pull requests and useful for discussion of specific code. You >> can configure your Github notifications to email you just about >> everything and you can reply using your email client, if it's too much >> trouble bouncing between web browser and email client. > > > Can new comments on github (perhaps except line-specific ones) forwarded > to this or a separate mailing list? Having to remember to always look at > github as well is annoying. > Maybe if we subscribe the `geanyadmin` user to the mailing list or something, otherwise I guess we'd need to write a script to interact with the github API and send the mails. Cheers, Matthew Brush

1 0

coffeescript lexer
by joshua.rh＠comcast.net 30 Nov '11

30 Nov '11

Hello, I've added a feature request to add a coffeescript lexer to scintilla here: https://sourceforge.net/tracker/?func=detail&aid=3436256&group_id=2439&atid… and will hopefully start on it when the semester's over (December). Also, does anyone know: 1) If the lexer needs to be written in c++ (will the lua one Matthew found work?) 2) if it's a bad idea to test this in geany? (I intentionally added the request to scintilla, and can work on it in scite if that's a better idea) 3) if this will cover everything needed for coffeescript in geany once it's done (we'll still need a filetypes.coffee, right? which is just a .conf file that contains the keywords, comment markers, and a few other small things, correct?) Thanks for any info, and I hope to work on this soon! Josh

3 3

I'd like to write a lexer for HAML. Can I invoke sub-lexers, and can I set up simple TDD?
by Nathan Broadbent 29 Nov '11

29 Nov '11

Dear Scintilla & Geany mailing lists, I would like to write a Scintilla lexer for the HAML syntax. HAML is used by many (if not most) Ruby on Rails developers. It is an indented HTML markup language with inline Ruby evaluation. It also needs to support many embedded syntaxes, such as javascript, ruby, css, markdown, textile, and plain HTML. I've been studying the HTML lexer for the last 5 hours, and I'm beginning to understand how everything fits together. But before I start the lexer, I would like to please ask a few questions. I've noticed that the HTML lexer function is passed 6 sets of keywords, including HTML elements, Javascript keywords, Python keywords, etc. It then defines 'classifyWordHT***' functions in order to classify words for each of those sub-languages. I was wondering if it would be possible / advisable to invoke a different lexer for each sub-language, instead of trying to support them all from one lexer? For example, I could detect the opening tag for javascript, scan down the file and count the character length until the javascript block ends. Then I could pass the original Accessor to the javascript lexer (LexerCPP) with the start position and length. This 'sub-lexer' would colorize the text, and the main lexer could then skip that block of text. It seems that a Scintilla lexer isn't designed to do this on it's own, since Geany passes it all of the data about filetypes, keywords, and highlighting mappings. But is there any reason why I couldn't hard-code "javascript => SCLEX_CPP" in my HAML lexer? Or is there an abstract way to query lexer mappings and keywords from scintilla's caller application? My other question is: How do you test your lexers? Do you just compile them and check them manually in SciTE or Geany? I'd really like to start with some sample files, hand-code the expected highlighting, then compile and run the sample files through the lexer until all the expectations are met. I haven't been able to find any documentation about testing, but please let me know if someone has already written a script to automate this process. Thanks a lot for your time! Best regards, Nathan B

1 0

geany-plugins I18N
by Johann SAUNIER 28 Nov '11

28 Nov '11

Hello, Is it possible that someone who is granted to commit to geany-plugins to run the command "./waf updatepo" on the plugins project ? I could run the command myself and join a patch for it on sourceforge, but I guess that would be more work for me and the one who is going to apply the it. I have a few patches to send for geanyprj but I can't do it before I18N is fixed up. Thanks, Johann.

2 2

Some sort of thoughts about geany-plugins-devel-git-repo
by Frank Lanitz 27 Nov '11

27 Nov '11

Hi developers, It has been a while when I first announced a mail about my idea of process after transition of geany-plugins repository. As from my understand the only open point is to have clarified the svn-url-reference question its a good point to tell you what I'm thinking of. Currently we do have about 25 people which are allowed to commit to geany-plugins svn. Not all of them are active at the moment (and might won't get active again sometime in future), some of them are low in time or no responsive at the moment. On the other hand we do have about 30 plugins, which are mostly maintained. As you know from discussion about e.g. geanydbg/debugger and the project plugins, some of them are currently not maintained very actively and are getting obsolete. Given the changes for Python plugin support in pipeline of Geany I'm in a good mood that we will have a increasing number of contributors and plugins available for Geany. Some of the new plugins will be distributed via the geany-plugins-project for sure as well as contributors like to add maybe features, bugfixes etc. to existing code basis. Unfortunately in past we had not really some kind of a quality assurance on committing code beside authors and maybe devel users. We introduced the make check build target a couple of month ago which gave a more critical view onto code. Based on this a huge number of warnings, memory leaks and bugs has been able being removed. But still issues are left. As we will have some kind of a reset with movement to github, its a good point to rethink about the way, how patches are introduced to geany-plugins. So this is my idea how to do so: We will have one master branch where all changes intended for releasing are going in. Features and new plugins are going to be developed inside branches (more late onto this topic) and once they are in a suitable status, they are getting merged into master branch. Release are generated from master branch and are getting marked with a tag. If there is any need for some minor release as we had e.g. with 0.21.1 there will be a release branch that will include all patches going in. If they are also needed to get applied on master, we can cherry-pick them or find some other way of merging them back. We can divide contributors for plugins into 2 groups: 1: Contributors to existing plugins or general infrastructure as e.g waf/autotools 2: Contributors of new plugins Here we should set up 2 processes: Contributions of group 1 should clone the repository and sending a pull request or patch to maintainer of plugins. Once they did this, the maintainer is reviewing the changes and including them into his branch. Contributors of new plugins shall send a pull request of full diff to release team. And this is another point. I imagine to have a release team which is taking care of overall quality of geany-plugins. This is including following: If a plugin maintainer is finishing a change or a review he is sending a merge request to the release team. After they did a review based on criteria given e.g. inside HACKING they are merging it into master branch. If the patch is not hitting a minimum on quality its getting refused. Thins to be done in front if you like this change: - Defining release team - Reviewing HACKING and defining basic quality criteria - Pushing all to github ;) What do you think? Feedback is highly welcome ;) Cheers, Frnak

5 10

Greetings from an IDE refugee
by Nathan Broadbent 26 Nov '11

26 Nov '11

Hello, I'm a Ruby on Rails programmer with a bit of C and C++ experience. I was using gedit 2.x & the gmate plugins happily for over a year, until Ubuntu 11 decided to go to GTK3, and bump gedit to 3.x. All my plugins are no longer compatible, so I decided that it was about time to find a new editor. I've tried all the editors I can find, and I've decided that Geany wins. But I'm not completely satisfied with it, and there's plenty of things I'd like to work on. Here's my list: 1) I'd like to expand the behaviour of 'Auto-close quotes and brackets', and make it work like the 'Pair char autocomplete' gedit plugin - http://code.google.com/p/gedit-pair-char-autocomplete/: The plugin is smart enough to automatically overwrite existing closing brackets when appropriate. Selecting a block of text and typing an opening parenthesis or quote character will enclose the selection in quotes or parenthesis. 2) I'd like to fix a weird bug with 'haml' templates - Any file that starts with an '=' character is treated as a giant comment. This destroys syntax highlighting for most of our haml files. I can't figure out why this is happening. 3) I really like the TreeBrowser plugin. In fact, I really wouldn't have considered Geany if it didn't exist. So I'd like to add file-system monitoring to auto-refresh directories, and cut/copy/paste of multiple files. I think a file browser is a pretty critical feature of any editor, so I was also wondering if this plugin deserves to be merged into core. 4) I would love to write some plugins in Ruby. The GeanyLua plugin could be a good base for this, but it would be great if the core had native bindings for Python and Ruby. 5) I'd love to see more 'Ruby on Rails'-related plugins, such as test suite integration (RSpec/Cucumber), built-in Rails API documentation (similar to railsapi.com), and caching/invoking rake & capistrano tasks. It would also be nice if the compile/build buttons could be automatically hidden while editing a scripting language. 6) It would be cool to have some simple integrations with git and github. Well, those are some of the things I'd like to work on. Thanks to everyone who has worked on Geany so far! It's a great IDE, and I look forward to contributing. Regards, Nathan B

4 6

Plugin : Geanyprj
by Johann SAUNIER 25 Nov '11

25 Nov '11

Hello world, I tried to defend Geanyprj a few weeks ago because I heard it will be removed from the plugins project due to a lack of maintenance. So, I decided to maintain it myself because I would really miss it (I can't get used to Gproject). First of all, is there a specific mailing list for Geany-plugins ? I couldn't find it. My questions if I'm already at the right place : 1) In a previous post, Lex told me that he couldn't create a new project because of a crash : Unfortunately compiled against Geany Git it crashes creating a new > project. I don't have time (or interest I admit) to find out why, but > it may need some maintenance. > Cheers > Lex I can't reproduce this crash as everything works perfectly on my machine. I build against : - https://geany-plugins.svn.sourceforge.net/svnroot/geany-plugins/trunk/geany… and - branch 'master' of git://github.com/geany/geany Am I wrong ? 2) I tried "./waf updatepo" and the results are big changes in .po files, like if they were all much out of date -> do we have to use "updatepo" each time we add a translatable string or should we add it by hand in the .po file of our native language (and the other ones we know how to translate) ? 3) by executing step 2, I noticed an error in the README. waf. Do I have to send a patch or just tell it to a maintainer on this list ? 4) I saw a Tracker->Patches page on http://sourceforge.net/projects/geany-plugins/, is this the right place to submit patches ? If so, do I have to tell someone before submitting ? Cheers, Johann

3 6

Slight problem with autocomplete and Haskell
by Erik de Castro Lopo 24 Nov '11

24 Nov '11

Hi all, I'm using current geany SVN head and coding quite a bit of Haskell. One pretty significant annoyance is that one common way of formating Haskell code results in something that looks like this: functionName :: Type1 -> IO Type2 functionName param = do putStrLn "In functionName" ..... The problem is that when I type the above in, I add the " = do" and then hit Tab for indentation and thats when geany decides to delete the "do" I've just typed. Would be nice if this could be fixed. Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

3 4

--readonly handling
by Dimitar Zhekov 21 Nov '11

21 Nov '11

Hi, Is there any technical reason to check cl_options.readonly in document.c, and clear it load_startup_files(), instead of simply invoking document_open_file(filename, cl_options.readonly, ...) from main_handle_filename()? -- E-gards: Jimmy

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel November 2011