Hi all,
I'm writing a plugin which integrates Devhelp documentation browser into Geany (similar to Anjuta). The code is currently on my github site:
https://github.com/codebrainz/geany-devhelp
It's working quite well as is, but I can think of some more things to improve it. It kinda mangles Geany's notebook layout a fair bit and I'm not sure what the repercussions of this are (if any) although I'm fairly satisfied with the results.
It also adds a menu item on the editor's context menu to look up the current symbol/tag in the built-in devhelp, which is a nice feature (thanks to b4n for suggesting this on IRC).
Obviously it requires having the Devhelp libraries installed as well as WebKit GTK.
If anyone has any feedback (especially opinions about the way it lays out the UI), I would very much appreciate hearing it. If you don't want to install it, there's a screen shot in the repository:
https://github.com/codebrainz/geany-devhelp/raw/master/geany-devhelp.png
Thanks for your time,
Matthew Brush (codebrainz)
On 18.12.2010 19:00, Matthew Brush wrote:
If anyone has any feedback (especially opinions about the way it lays out the UI), I would very much appreciate hearing it. If you don't want to install it, there's a screen shot in the repository:
https://github.com/codebrainz/geany-devhelp/raw/master/geany-devhelp.png
The screen shot looks interesting. Without having tried your plugin I'm not sure if that's the best way to integrate devhelp. The geanydoc plugin provides a means to launch devhelp externally (via a keyboard shortcut) which I always found quite convinient so far.
Best regards.
On Sat, 18 Dec 2010 21:59:40 +0100 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
On 18.12.2010 19:00, Matthew Brush wrote:
If anyone has any feedback (especially opinions about the way it lays out the UI), I would very much appreciate hearing it. If you don't want to install it, there's a screen shot in the repository:
https://github.com/codebrainz/geany-devhelp/raw/master/geany-devhelp.png
The screen shot looks interesting. Without having tried your plugin I'm not sure if that's the best way to integrate devhelp. The geanydoc plugin provides a means to launch devhelp externally (via a keyboard shortcut) which I always found quite convinient so far.
I agree with Thomas, but I do now a bunch of people which prefer something like that. So, without digging into code and based on screenshot I think a nice approach.
Now I only need to get it compiled here :D
Cheers, Frank
On Sun, 19 Dec 2010 14:13:32 +0100 Frank Lanitz frank@frank.uvena.de wrote:
On Sat, 18 Dec 2010 21:59:40 +0100 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
On 18.12.2010 19:00, Matthew Brush wrote:
If anyone has any feedback (especially opinions about the way it lays out the UI), I would very much appreciate hearing it. If you don't want to install it, there's a screen shot in the repository:
https://github.com/codebrainz/geany-devhelp/raw/master/geany-devhelp.png
The screen shot looks interesting. Without having tried your plugin I'm not sure if that's the best way to integrate devhelp. The geanydoc plugin provides a means to launch devhelp externally (via a keyboard shortcut) which I always found quite convinient so far.
I agree with Thomas, but I do now a bunch of people which prefer something like that. So, without digging into code and based on screenshot I think a nice approach.
Now I only need to get it compiled here :D
I did get it compiled with help of Matthew and uhm...well.. I need to revert my opinion. Its fun to play around with it. Could be really helpful. :)
Cheers, Frank
Hi,
I would like to add my geany-devhelp[1] plugin to the geany-plugins project. On SourceForge, my username is 'codebrainz', if it's OK to get commit access.
I also had a couple questions:
1) Who integrates the build system? I'm using autotools, and I could probably integrate that part, but I don't know Waf at all. 2) Is it possible to continue using Git (on GitHub) and still commit to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS so pointers on this would be great.
[1] https://github.com/codebrainz/geany-devhelp
Thank you, Matthew Brush (codebrainz)
On Sun, 06 Mar 2011 03:12:25 -0800, Matthew wrote:
Hi,
I would like to add my geany-devhelp[1] plugin to the geany-plugins project. On SourceForge, my username is 'codebrainz', if it's OK to get commit access.
Added.
I also had a couple questions:
- Who integrates the build system? I'm using autotools, and I could
probably integrate that part, but I don't know Waf at all.
Usually me and hyperair. Don't worry about Waf, I'll update it once your plugin is in the repos.
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Regards, Enrico
Am 06.03.2011 13:36, schrieb Enrico Tröger:
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Indeed. You can continue using git and use git-svn to commit to the g-p svn repo whenever you feel it's the right time.
Best regards.
Am 06.03.2011 14:01, schrieb Thomas Martitz:
Am 06.03.2011 13:36, schrieb Enrico Tröger:
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Indeed. You can continue using git and use git-svn to commit to the g-p svn repo whenever you feel it's the right time.
This might will create some issues with build system etc. but in general you are right.
Cheers, Frank
On 08.03.2011 15:15, Frank Lanitz wrote:
Am 06.03.2011 14:01, schrieb Thomas Martitz:
Am 06.03.2011 13:36, schrieb Enrico Tröger:
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Indeed. You can continue using git and use git-svn to commit to the g-p svn repo whenever you feel it's the right time.
This might will create some issues with build system etc. but in general you are right.
Might or will? :)
Anyway, what problems do you see?
Best regards.
Am 08.03.2011 15:18, schrieb Thomas Martitz:
On 08.03.2011 15:15, Frank Lanitz wrote:
Am 06.03.2011 14:01, schrieb Thomas Martitz:
Am 06.03.2011 13:36, schrieb Enrico Tröger:
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Indeed. You can continue using git and use git-svn to commit to the g-p svn repo whenever you feel it's the right time.
This might will create some issues with build system etc. but in general you are right.
Might or will? :)
Anyway, what problems do you see?
Moving around files or adding new files will cause a patch which will be more hard to apply on the other branch.
Cheers, Frank
On 03/08/11 06:15, Frank Lanitz wrote:
Am 06.03.2011 14:01, schrieb Thomas Martitz:
Am 06.03.2011 13:36, schrieb Enrico Tröger:
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Indeed. You can continue using git and use git-svn to commit to the g-p svn repo whenever you feel it's the right time.
This might will create some issues with build system etc. but in general you are right.
I've been using git-svn for a few commits now and it seems to be working OK, please correct me if I've been causing problems yet :)
I've been doing normal Git where I make a branch to work on a specific thing, then merging into master branch. When I'm done making commits/merges, then I use 'git svn rebase' to resync with SVN and then doing a 'git svn dcommit' to push the commits to SVN. I added a .gitignore file containing a list of all the Autotools cruft and other files that change when configuring and building, and I also added .gitignore to the .gitignore so I don't accidentally put that file in SVN.
Does this sound reasonable?
Cheers, Matthew Brush
On Tuesday 08,March,2011 11:26 PM, Matthew Brush wrote:
On 03/08/11 06:15, Frank Lanitz wrote:
Am 06.03.2011 14:01, schrieb Thomas Martitz:
Am 06.03.2011 13:36, schrieb Enrico Tröger:
- Is it possible to continue using Git (on GitHub) and still commit
to geany-projects SVN at the same time (when code on Git is good enough to go into the official Projects SVN)? I'm pretty new with VCS
Why not. I'd say it's your business how you organise your development cycle. If you prefer to use mainly GIT and use the Geany-Plugins repository to put in some more matured code, why not. Just be aware, most of the Geany-Plugins users will use the SVN repository, I guess.
Indeed. You can continue using git and use git-svn to commit to the g-p svn repo whenever you feel it's the right time.
This might will create some issues with build system etc. but in general you are right.
I've been using git-svn for a few commits now and it seems to be working OK, please correct me if I've been causing problems yet :)
I've been doing normal Git where I make a branch to work on a specific thing, then merging into master branch. When I'm done making commits/merges, then I use 'git svn rebase' to resync with SVN and then doing a 'git svn dcommit' to push the commits to SVN. I added a .gitignore file containing a list of all the Autotools cruft and other files that change when configuring and building, and I also added .gitignore to the .gitignore so I don't accidentally put that file in SVN.
You could actually use .git/info/exclude instead for that functionality. Then you can use stuff like git clean -fdx, and not worry about accidentally purging your .gitignore. .gitignore should only be used if you want to commit it into the repository.
On Sun, 13 Mar 2011 12:08:32 +0800 Chow Loong Jin hyperair@gmail.com wrote:
You could actually use .git/info/exclude instead for that functionality. Then you can use stuff like git clean -fdx, and not worry about accidentally purging your .gitignore. .gitignore should only be used if you want to commit it into the repository.
I had a talk with a git expert a couple of days ago and he mentioned that this (.git/info/exclude) is the better approach on doing this.
Cheers, Frank
On 03/13/11 07:17, Frank Lanitz wrote:
On Sun, 13 Mar 2011 12:08:32 +0800 Chow Loong Jinhyperair@gmail.com wrote:
You could actually use .git/info/exclude instead for that functionality. Then you can use stuff like git clean -fdx, and not worry about accidentally purging your .gitignore. .gitignore should only be used if you want to commit it into the repository.
I had a talk with a git expert a couple of days ago and he mentioned that this (.git/info/exclude) is the better approach on doing this.
Assuming that the svn:ignore properties are configured/up-to-date, to be able to use it with 'git-svn show-ignore >> .git/info/exclude'.
Cheers, Matthew Brush (codebrainz)