Hi,
I just wanted to leave a note for everybody who is not reading the the
svn mailing list. I've just upgraded the minimum dependencies for Geany
plugins project to 0.16 since most of the included plugins will not
compile with any version below. Please note, I only did the change on
waf build support. Plugin maintainer that are using autotools needs to
update the dependencies on their own ;)
Cheers,
Frank
--
http://frank.uvena.de/en/
Hello Geany developers,
I just wanted to say a few words about the editor customization (syntax
highlighting and the likes)...
While the possibilties of customization are good already (and probably more
than enough)
I always somehow missed the possibility of defining different fonts/size for
different styles...
It's not so important, so I let it go, until I used SciTE for a while...and
passed to level of customization
that was such a luxury that it was hard to let go...
Now, it might have been obvious to most of you but I figured since Geany use
scintilla as well, it must have the same possibilities
and sure enough with some hacking of the source, i got where I wanted...see
screenshot to have a better idea
http://img201.imageshack.us/img201/4089/geanyscreenshot.png
multi-font/size possibilities, perfect dark background for the folding bar,
bigger choice of markers, size of the margins...
it's not much but it counts in the long run...
and geany is even better than before in my eyes now....
Now, to the main point, I understand the aim of developing a lightweight
sober IDE....so right from the bat, confusing the user with millions of
possibility of customization might not be suited...
I'm kinda testing the water here...if this extra customization matters to
people, I could clean up my hacks...and come up (or anyone willing to) come
up with a system to implement it...
in any case, it would be nice to have this possibilites mentionned in
Hacking Geany at least...I'm sure some people would be glad to find the
infos...
Cheers,
Jimmy
Hi Guys,
Sorry for no progress, Ive been busy finishing off work as my contract ends
at the end of the month (TODAY!!!).
Now I will have time to finish what I set out to do for you since it is
likely to be a while before the next contract starts.
I just committed to build-system a change to add a build commands tab to the
project properties dialog to save project commands from.
To save you building the branch, I've attached a screen shot. The XXX will
of course have the correct filetype when some code gets behind the dialog.
I propose to use the same for the Build menu 'set build commands' (or
whatever we are calling it) dialog.
After some thought I propose to put the error regex in both because as you
change the compiler it is likely that you may need to change the regex. So
having one associated with each set of commands is useful.
I appreciate that there will probably be no comments til after the 0.17
release. I'll just keep plodding on.
Cheers
Lex
PS Enrico, I can't help with the Addons problem since I am Autotools
illiterate, I didn't even *look* in configure.in or I'd have seen the todo.
Some of these build-system changes are to allow me to use alternatives to
Autotools..
Hi,
I hope I'm not posting this on the wrong list.
I'm trying to build Geany on Windows Vista, following the Windows build
instructions at: http://www.geany.org/Support/BuildingOnWin32
Even after adding a localwin32.mk file and changing the PREFIX as suggested,
I still get
lregex.c:22:18: glib.h: No such file or directory
when compiling through the MSYS shell. If I used the standard command
prompt, there's the makefiles would balk on the missing 'make' command.
As per the instructions, I've downloaded all the required libs to "C:\libs\"
and added that to my environment variables. I grabbed the Geany source
(trunk) using Tortoise SVN
Am I missing something here regarding compiling using makefiles?
PS: when grabbing the dependencies,
http://www.gimp.org/~tml/gimp/win32/downloads.html no longer lists the
required ones, but points to
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/ instead
Thanks,
Aligorith
>I would definitely love it, it looks fantastic. I'm not sure if it
>counts as bloat if scintilla already implements it.
>Btw, what font are you using there? The one with the slightly rotated
>'e' I mean
>Best regards.
The font is Monofur, a font that deserved to be known more in the small and
rather unexciting world of free Monospace fonts....
it can be pick up on dafont.com...
As for the rest, I'm of course not talking about reimplementing what
scintilla does....
currently I just force geany to setup more scintilla parameters, that's
all...no crazy coding...i just needed to find where in the code to it and
play around with parameters...
so when I say implement, i just mean a proper scheme to allow a user to
setup those parametes without modifying the source code by hand...(something
like a filetype.toto.extended....)
cheers,
jimmy
Hi translators and friends of Geany,
I'm glad to announce string freeze for Geany 0.17 which will be released
not far in future after about three month of developing.
I'd be very happy if you could send a patch or complete file with
translation to either the geany-i18n mailing list or direct to me
within the next week so we can include it to the next release. Deadline
will be 09-05-01.
To make it more easy for you I've already uploaded updated versions of
the po files to svn with r3726. You can access them as always at
http://geany.svn.sourceforge.net/viewvc/geany/trunk/po/
or by checking out the svn tree of Geany by using e.g.
svn co https://geany.svn.sourceforge.net/svnroot/geany/trunk geany
Fans of git can also use the interface provided by http://git.geany.org
by using
git clone http://git.geany.org/git/geany
Also at http://i18n.geany.org/ are statistics and daily updated
files available.
As mentioned before, we are trying to have all translations complete by
2009-05-01.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to translate
same things two or three times. Also please feel to ping me for every
question or if you like to start a new translation for an unsupported
language.
Thanks and happy translating ;)
Frank
--
http://frank.uvena.de/en/
Hey guys.
(For the impatient, scroll to the end of the mail.)
Some of you might that on Windows, running some commands opens an extra
console window and so capturing the program's output is not possible.
That happens e.g. when compiling, linking, or running make commands in
Geany on Windows.
There is a long story behind, IMO that should be fixed in GLib's spawn
commands but recently I read Tor, the responsibly dev, said this is not
GLib's job but instead in the app's reponsibility.
This is all ok but I and probably Nick too, won't write any code using
the Windows API and CreateProcess() just to get it working.
Some time ago, I added some code to the Windows port that creates an
additional console window on startup of Geany, this can be activated by
the "-v" command line option. This has the advantage, when running a
compiler or make or whatever, no extra console window will open and we
can capture the program's output.
But of course, it isn't nice to have always this extra console window
open. And more importantly, with this window, the Run commands
sometimes[1] don't work at all or cause weird behaviour[2].
This extra console window was also never intended for daily use, just
as a little help when testing code on Windows.
There are two ways to go:
a) fix all these problems by writing a lot new code around
Windows' CreateProcess() API and make it all working
b) run Builds commands on Windows synchronously for what we have
already that CreateProcess() code in Geany (done by Pierre Joye,
many many thanks)
Solution A would be of course the best one and desirable but it needs
someone to write the code and with the necessary knowledge and time to
do this.
So, I'd vote for solution B, attached is a quick hack on the
src/build.c with the necessary changes. Tested and seems to work.
Instead of running the Build commands asynchronously, they are run
directly. This also has disadvantages:
a) the whole Geany window freezes while the Build command is running
b) the output is "sorted", that is, first the program's stdout is put
into the Compiler window, then the program's stderr
But therefore we have the advantage that the build system on Windows
gets more usable.
###
### END ###
###
So, to not be even more boring with details, the final question is:
Are there any objections in using the attached patch and making the
Build commands on Windows running synchronously?
[1] for some commands, only noticed while testing code, not sure why
[2] In #2723005, the user reported 100% CPU usage when using the Run
command. There was also a related issue with running Java apps on
Windows, IIRC.
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
On Sun, 19 Apr 2009 17:54:09 +0000, eht16(a)users.sourceforge.net wrote:
Hey all,
>Revision: 3713
> http://geany.svn.sourceforge.net/geany/?rev=3713&view=rev
>Author: eht16
>Date: 2009-04-19 17:54:09 +0000 (Sun, 19 Apr 2009)
>
>Log Message:
>-----------
>Hide the extra file open dialog options in an expander to make the
>dialog more compact by default and to provide more space for the file
>view. Remove the filename field as it is also provided by GTK itself
>with more features like auto-completion.
This commit changed the appearance of Geany's file open dialog. This
was something which I liked to do for a long time, today I finally did
it:
the extra options like the combo boxes for setting a specific filetype
or encoding are now hidden by default and can be easily shown by
clicking on the new expander "More Options" or by pressing Alt-M.
I also removed the filename field which isn't necessary at all, at
least not with newer GTK versions as those provide a location entry at
the top of the file open dialog (toggle the "Edit" icon in the top
left corner of the dialog). And GTK's location entry even provides auto
completion which is pretty cool.
If there are any big complaints about this change, raise your voice
now!
:)
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Dear Geany Users and Geany Developers,
I'm very glad I can announce that today the geanygdb plugin was
released. The release is available for download at [1].
Please note that this is just a maintenance release which includes no
new features with it at all. This release is compatible with Geany 0.16.
You will need to install this plugin when using Geany 0.16 or higher.
If you have any questions regarding this release feel free to contact me
by email at dmaphy(a)googlemail.com, by the geany developers mailing list
or find me at IRC in #geany and #geany-de on chat.freenode.net.
If you find bugs, have feature requests or patches please use the
geany-plugins tracker at sourceforge:
https://sourceforge.net/projects/geany-plugins/
[1] http://geany-plugins.sourceforge.net/geanygdb/geanygdb-0.0.2.tar.gz
Best Regards,
Dominic
--
Dominic Hopf <dmaphy(a)gmail.com>
http://dominichopf.de/
Key Fingerprint:
A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
Hi all,
I've updated the filetype IDs so we can add filetypes without breaking
the plugin ABI. I'm not sure if this will affect any of geany-plugins,
but if so, it shouldn't take long to fix.
Just let me know if you find anything this breaks, in the core or
elsewhere.
On Fri, 03 Apr 2009 14:23:45 +0000
ntrel(a)users.sourceforge.net wrote:
> Revision: 3681
> http://geany.svn.sourceforge.net/geany/?rev=3681&view=rev
> Author: ntrel
> Date: 2009-04-03 14:23:45 +0000 (Fri, 03 Apr 2009)
>
> Log Message:
> -----------
> Merge reorder-filetypes branch:
> Make GEANY_FILETYPES_NONE = 0, sort filetype IDs randomly (so we can
> append randomly without breaking the ABI).
> Make None filetype name = title = _("None").
> Add foreach_slist() macro.
> Add filetypes_by_title list to GeanyData for plugin API access
> - a list of filetype pointers, which includes the None filetype
> first. This list stays constant by the time plugins are initialized,
> so you can use e.g. g_slist_nth_data(filetypes_by_title, n) to
> index the sorted list.
Thanks,
Nick
