Hi,
I've committed Lex Trotman's geany.txt changes in the build-system
branch, slightly edited.
https://geany.svn.sourceforge.net/svnroot/geany/branches/build-system
I made some formatting changes:
.. note:: syntax (space after ..)
break lines - I used the 'Format->Send selection to command' with the
fmt command.
On to the changes - in general I agree with them, but some points:
1. 'Make Commands' is mentioned, perhaps this should be renamed 'Global
Commands', as these may well be nothing to do with 'make'.
2.
+* From the user preferences if the user has make commands defined.
+* From the global preferences/defaults.
Not sure about this - currently we only have user prefs for geany.conf.
Maybe global prefs too, but would it be confusing?
3. Do we need the table of default filetype build commands? If so, IMO
it should be autogenerated and included/referenced from geany.txt
rather than writing by hand.
4. I think 'Project Make' should be configured from the Project
Properties dialog. In this case the global Make command could be
grayed out in the Configure Commands dialog.
5.
+Remember that menu item two (default the 'Make Custom Target' item)
+will pop up a dialog to ask for additional targets/options when invoked
+allowing you to add to the command you define here.
Should this just be the 'Make Custom Target' item? (not menu item two)
Regards,
Nick
On Thu, 9 Oct 2008 23:43:16 +1100
"Lex Trotman" <elextr(a)gmail.com> wrote:
> > Could you send the geany.txt file so I can diff it?
>
>
> Ok,I was just looking for a way of making changes visible easily,
> personally I have trouble reading diffs of any substantial size.
I use Meld:
http://meld.sourceforge.net/
> No problem, we can each use our own method for finding the changes and
> exchange the .txt file, attached.
Thanks. I'll commit it to an SVN branch and post back here with
comments.
> Once we get over the hurdle of this first set of changes we can also
> discuss individual items in the ML without the whole .txt file but
> the initial changes were IMO too big to just put the diffs here.
OK, I think bigger conceptual changes can be discussed on the geany
users list, but implementation details here on geany-devel.
Regards,
Nick
On Thu, 9 Oct 2008 23:43:16 +1100, "Lex Trotman" <elextr(a)gmail.com>
wrote:
>> > > What I will do over the next few days is to write a
>> > > proposed Build System section for the manual which can be
>> > > discussed, agreed and act as a specification.
>> > >
>> > As promised, attached is a Geany.html with my first cut at
>> > documenting the proposed changes to the build system. To help you
>> > find the changes which are in several places I have attached an
>> > OpenOffice document version of the geany.txt file with changes
>> > marked using writers change marking facility. You may want to mark
>> > this up further with your comments so we can keep track.
>>
>> Maybe it's just me but working through OpenOffice is not a good
>> option. OpenOffice is a big suite of software and many people using
Full ACK.
>> and developing Geany don't have it installed. For discussing changes
>> I would prefer we did it on the ML.
>>
>> Could you send the geany.txt file so I can diff it?
>
>
>Ok,I was just looking for a way of making changes visible easily,
>personally I have trouble reading diffs of any substantial size.
It's just a matter of training :).
>No problem, we can each use our own method for finding the changes and
>exchange the .txt file, attached.
>Once we get over the hurdle of this first set of changes we can also
>discuss individual items in the ML without the whole .txt file but the
>initial changes were IMO too big to just put the diffs here.
And what about moving this discussion to geany-devel?
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Hi
Nick T (ntrel) suggested we move discussion of a symbol tree patch to the list
- https://sourceforge.net/tracker/index.php?func=detail&aid=2083110&group_id=…
>Comment By: Nick Treleaven (ntrel)
>Date: 2008-10-03 15:17
>
>Message:
>I have some ideas to make the code more straightforward and robust:
>
>1. Replace the GeanySymbol list with a TMTag list. This avoids having to
>parse the parent name, avoiding possible bugs.
I'm not exactly sure what you mean - I thought that parsing the symbol
names was the only way to determine symbol tree structure?
E.g. given a list of symbols
B.c.d
A
A.b
B.c
B
We can construct a tree:
A
|_ b
B
|_c
|_d
The information on the tag type is simply used to determine the
icon/type to use in the tree.
>
>2. Sort the tags by appearance before adding to the tree model. This
>ensures that parent items are added before children, and we can remove all
>the complex 'skipped' code. The model can then be sorted after all entries
>have been added (for the 'sort by name' case).
Yes, presorting sounds like a good idea to avoid modifying the list of
symbols. FWIW the current logic is to move a symbol to the end of the
list if its parent cannot be found.
Note that the 'skipped' list is actually not used in the current
version of the patch - it was there to catch errors caused by a bug in
the the C++ tag generator (nested namespaces, see bug "[ 2141317 ] C++
nested namespace tags created incorrectly")
>
>3. Instead of looking for children for certain tags (e.g. class, etc),
>just see if the TMTag struct has a parent field. This should be much more
>flexible for filetypes that overload e.g. the tm_tag_class_t fields to mean
>something else.
>
>I'm happy to work on these changes over time. If you want to discuss them,
>the geany-devel list might be better than here.
Of course you're welcome to do that - I'm simply happy to have the
feature since it really helps navigating complex code.
Thanks again for your and all the other geany developers' work :-)
Cheers,
Conrad
Hi translators and friends of Geany,
After a long period of developing we decided to make a string freeze in
preparation of a new upcoming release: Geany 0.15
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 two weeks so we can include it to the next release
(around October, 16).
To make it more easy for you I've already uploaded updated versions of
the po files to svn (r3040). You can access them from
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
Also on http://www.geany.org/i18n/ are statistics and daily updated
files available.
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