<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Geany Dev Team:<br>
<br>
I have various ideas for Geany (that do not pertain to the
file-extensions and language support) that I would like to share
before I write or submit any code.<br>
<br>
Also, I found an issue on Geany.org. On
<a class="moz-txt-link-freetext" href="http://wiki.geany.org/config/scripts/shell">http://wiki.geany.org/config/scripts/shell</a> , there is a deadlink (
<a class="moz-txt-link-freetext" href="https://svn.enlightenment.org/svn/e/trunk/devs/discomfitor/geany_tagger.sh">https://svn.enlightenment.org/svn/e/trunk/devs/discomfitor/geany_tagger.sh</a>
).<br>
<br>
By the way, thank you again, Matthew Brush, for the link to QML on
Geany. I then found <a class="moz-txt-link-freetext" href="http://wiki.geany.org/config/start">http://wiki.geany.org/config/start</a> . Why are
many of these "goodies" not in the mainstream Geany release?<br>
<br>
Unless I over-looked it in
<a class="moz-txt-link-freetext" href="http://www.geany.org/Contribute/Developers">http://www.geany.org/Contribute/Developers</a> , I assume discussion on
plugin and color-scheme development are allowed in this mailing
list, or is there a separate mailing list?<br>
<br>
<b>Ideas</b><br>
<br>
I noticed that on Geany's GitHub page under ./data/templates, there
are two license templates ("gpl" and "bsd"). These templates appear
in the "Edit > Insert Comments" menu. I would like to add some
more license templates and include them in the menu. Does anyone
disagree with this idea? I would like to add agpl, lgpl2, lgpl3,
gpl3, cc0, and others. To make it easier to add menu items, could
Geany be re-programmed to dynamically create that menu based on the
templates included in ./data/templates and ~/.config/geany/templates
, thus allowing users to add licenses to their own systems?<br>
<br>
In my opinion, ./data/templates/gpl be renamed to
./data/templates/gpl2 to indicate that this is version 2 of the GNU
General Public License. Also, should the menu entry explicitly
indicate version 2?<br>
<br>
To improve the highlighting used by C source-code, could "bool" be
added to "primary=" in ./data/filetypes.c? "bool" existed since C99
( <a class="moz-txt-link-freetext" href="http://pubs.opengroup.org/onlinepubs/9699919799/">http://pubs.opengroup.org/onlinepubs/9699919799/</a> &&
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/C_data_types#stdbool.h">https://en.wikipedia.org/wiki/C_data_types#stdbool.h</a> ). Also, what
about "true" and "false" (lowercase) as seen in the
<stdbool.h>? Currently, in Geany, "bool" looks like a variable
(no highlighting) while other data-types use highlighting. True,
"bool" is not in the "core" C-language without libraries, but it
seems to me that "bool" should be added.<br>
<br>
Could more "Independent commands" and "Filetype commands" be added
to the "Set Build Commands" window opened under "Build > Set
Build Commands"? On my system, for C and Python, I have all of the
entries filled, but I need to add more.<br>
<br>
I would also like to add additional "Build > Set Build Commands"
commands to various languages. Are there any objections to me doing
so? Obviously, I will share such ideas and apply the given feedback
before submitting a PR.<br>
<br>
Soon, I will experiment with compiling Geany using various GCC
compiler flags and parameters. When I perform such an experiment,
would you like me to share my results about successful,
unsuccessful, and optimized compiling options (with included
benchmarks)? For instance, I have configured and compiled the Linux
kernel src for my system, and I have seen significant improvements
in memory usage, speed, boot-up time, etc.. Afterwards, I had become
interested in compiling source code myself rather than using the
pre-compiled *.deb files. I would like to see if I can make Geany
faster and more light-weight (on RAM). Since I will be doing such an
experiment, the Geany Dev Team may find the results of my experiment
to be beneficial to the project.<br>
<pre class="moz-signature" cols="72">--
Thanks,
Devyn Collier Johnson
<a class="moz-txt-link-abbreviated" href="mailto:DevynCJohnson@Gmail.com">DevynCJohnson@Gmail.com</a></pre>
</body>
</html>