Re: [GNC-dev] Advice on what to look at next

[jean]

That's exactly what I was looking for! Thanks!
J.

On 3/27/20 9:15 PM, John Ralls wrote:




On Mar 23, 2020, at 10:15 AM, jeanl  wrote:

Devs,
Can you point me to something you think needs to be looked at sooner rather
than later in the gnucash code? I find that bugzilla does not give a good
image of bug priority, but I'm sure you guys have a good idea of what needs
to be fixed next. I wouldn't mind helping with that.


I had a "well duh" thought about this today as I was working up the release notes for 
this weekend's release. I have a list of bugs in the "known problems" section of the 
release notes that I've decided while composing them were significant. You can see previous ones at 
https://www.gnucash.org/news.phtml and a slightly updated list will emerge in Sunday's 3.9 release 
notes.

Regards,
John Ralls



___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Advice on what to look at next

[John Ralls]

> On Mar 23, 2020, at 10:15 AM, jeanl  wrote:
> 
> Devs,
> Can you point me to something you think needs to be looked at sooner rather
> than later in the gnucash code? I find that bugzilla does not give a good
> image of bug priority, but I'm sure you guys have a good idea of what needs
> to be fixed next. I wouldn't mind helping with that.

I had a "well duh" thought about this today as I was working up the release 
notes for this weekend's release. I have a list of bugs in the "known problems" 
section of the release notes that I've decided while composing them were 
significant. You can see previous ones at https://www.gnucash.org/news.phtml 
and a slightly updated list will emerge in Sunday's 3.9 release notes.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Advice on what to look at next

[John Ralls]

Geert and I had that conversation today and we decided to proceed with starting 
3.990 test releases around the end of April, aiming for an end-of-June 4.0 
release. C++options will go into master after we release 4.0.

Regards,
John Ralls




> On Mar 23, 2020, at 5:22 PM, John Ralls  wrote:
> 
> It's up in the air. The major sticking point is that I'm working on a major 
> rewrite of the options system from an ugly mixture of C and Scheme to C++. 
> I'd hoped to have it far enough along by now to start test releases, but it's 
> not. The back end is mostly done and I'm 3/4 through with the GUI. After that 
> is making sure that the Scheme API is compatible. (It's the c++options branch 
> in my GitHub repo if you want to have a look. I haven't committed the GUI 
> stuff yet, it doesn't build.) We'll have to discuss whether to proceed to 
> user testing without it or slip the 4.0 release when Geert gets back from 
> travel.
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 23, 2020, at 2:17 PM, Jean Laroche  wrote:
>> 
>> How far along are you on 4.0? Is the planned 28 June 2020 release reasonable?
>> J.
>> 
>> On 3/23/20 2:12 PM, Christopher Lam wrote:
>>> For a /very/ high level overview, see the design goals at 
>>> https://wiki.gnucash.org/wiki/Release_Schedule
>>> Or, write tests and refactor the existing hacks.
>>> Or, feel free to squash bugs at leisure!
>>> On Mon, 23 Mar 2020 at 17:16, jeanl >> > wrote:
>>>   Devs,
>>>   Can you point me to something you think needs to be looked at sooner
>>>   rather
>>>   than later in the gnucash code? I find that bugzilla does not give a
>>>   good
>>>   image of bug priority, but I'm sure you guys have a good idea of
>>>   what needs
>>>   to be fixed next. I wouldn't mind helping with that.
>>>   Thanks,
>>>   Jean
>>>   --
>>>   Sent from:
>>>   http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html
>>>   ___
>>>   gnucash-devel mailing list
>>>   gnucash-devel@gnucash.org 
>>>   https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> ___
>> gnucash-devel mailing list
>> gnucash-devel@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] QIF Import Suggestion

[David Cousens]

Alan

Bugzilla (https://bugs.gnucash.org/) is just a web interface for filing
information about a bug and is meant for users to report problems to the
developers.  You don't really know how to administer it and set it up to
file a bug, but you do need to be a registered user on Bugzilla to file a
bug  (to reduce nuisance and prank filings etc). If you click the File a Bug
button on the web page at the above link, it will take you to a login page
which has a link to an account creation page if you are not already signed
up.

It is basically a form for entry to a database to fill out identifying which
version of GnuCash and on what OS the problem occurred and what the problem
is. Most of it is selecting options from dropdown menus  and you can just
copy your post in the User forum and paste it into the descriptionfield in
the Bugzilla form.  

It is the primary interface developers work from in fixing GnuCash problems
as bugs are addressed in a priority order depending on how severely they
affect GnuCash operation. The developers are largely volunteers, often hard
pushed for time so if things don't go into the system, there is little
likelihood they will be fixed.

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] QIF Import Suggestion

[Alan Auerbach]

Dear Geert Janssens,

 

I am a user, not an engineer or expert in developing applications. I have
never heard of Bugzilla so I read the information that you linked.
Unfortunately, it is Greek to me. I understand no more about Bugzilla today
than I did yesterday.

 

As I user, I figured out a workaround (it took many hours) when the QIF
import kept failing. I am glad I was able to make it work for me. I shared
the experience on the mailing list-also a new concept to me-so that others
that run into the same failure can understand it. I cannot fix the problem
in the application. I do not understand how to use Bugzilla. I have done my
best to bring the issue to the attention of the people who (I thought) can
address it for others (I have no plans to run any more imports). If it is
not sufficient, all I can say is that I did the best I know how.

 

Best wishes,

14343 North Frank Lloyd Wright Boulevard, Apt. 1009 
Scottsdale, AZ 85260-3634 
(480) 657-7543 Home 

(480) 922-0484 Text
(844) 395-7098 Fax

 

From: Geert Janssens  
Sent: Thursday, March 26, 2020 2:28 AM
To: gnucash-devel@gnucash.org; aauerb...@poolthing.com
Subject: Re: [GNC-dev] QIF Import Suggestion

 

Can you report this as a bug in bugzilla [1] please ?

 

Messages on the mailing list are a nice heads up, but tend to get lost.

 

Thanks!

 

Geert

 

[1] Refer to http://wiki.gnucash.org/wiki/Bugzilla on how to use our bug
tracker

 

Op dinsdag 17 maart 2020 23:40:33 CET schreef Alan Auerbach:

> Importing data from Quicken 2000 Home & Business revealed a bug after many

> unsuccessful attempts. I found that if a split transaction has any blank

> lines before the first line with data, the import will fail. I eventually

> located all the records with blank lines in the splits, moved the actual

> data to those blank lines, reran the import and completed it successfully.

> Now that I have resolved the issue for myself, there is nothing that I
need,

> but I thought that the information would be useful for others and/or for

> development.

> 

> 

> 

> I am very pleased with the application after just a few days. Thank you.

> 

> 

> 

> Best wishes,

> /s/ Alan Auerbach

> 14343 North Frank Lloyd Wright Boulevard, Apt. 1009

> Scottsdale, AZ 85260-3634

> (480) 657-7543 Home

> (480) 922-0484 Text

> (844) 395-7098 Fax

> 

> 

> 

> ___

> gnucash-devel mailing list

> gnucash-devel@gnucash.org  

> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

 

 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Ideas for account type-ahead modification

[John Ralls]

> On Mar 27, 2020, at 8:16 AM, jean  wrote:
> 
> I gave that a shot. See
> https://github.com/jeanlaroche/gnucash.git
> eea20a8da..d0ee8a161  fix_autocompletion_master
> But see comments below:
> 
>> Imagine we have the following account tree:
> >
>> Assets:Cash
>> Assets:Bank
>> Income:Salary
>> Expenses:Bets
>> Expenses:Bets:Blue
>> Typing 'et' will filter the list of accounts to show to
>> Assets:Cash
>> Assets:Bank
>> Expenses:Bets
>> Expenses:Bets:Blue
>> Subsequently typing ":" will autocomplete 'et' to 'ets:' and reduce the list 
>> to >
>> Assets:Cash
>> Assets:Bank
>> Expenses:Bets:Blue
> 
> I haven't implemented the autocomplete because in most cases I"m not sure 
> what to do:
> 
> What if you have:
> 
> Assets:Cash
> Expenses:Bets
> Forgeta:Foo
> 
> All three match "et" but what do we do if the user type ":" ? In which 
> situation can we autocomplete? In the current search, ":" autocompletes the 
> current match (i.e., it moves the cursor to the next :). But in the mixed 
> search, it's not clear what it should do.
> Should I treat ":" as .*: (non greedy) in regexp? I think that would be 
> pretty cool and it would be consistent with the legacy behavior.
> 
> In any case, the merging of the two searches actually does work currently and 
> is fairly intuitive. So if you guys like this solution then I could remove 
> the option, which would be really good!
> 

That's pretty cool, better than the preference.

As for typing et: I think the separator (note that it can be set with a 
preference, ':' is only the default) would act as a barrier so at that point 
only accounts that have children would match so Expenses:Bets would drop out.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Ideas for account type-ahead modification

[jean]

I gave that a shot. See
https://github.com/jeanlaroche/gnucash.git
eea20a8da..d0ee8a161  fix_autocompletion_master
But see comments below:


Imagine we have the following account tree:

>

Assets:Cash
Assets:Bank
Income:Salary
Expenses:Bets
Expenses:Bets:Blue

Typing 'et' will filter the list of accounts to show to

Assets:Cash
Assets:Bank
Expenses:Bets
Expenses:Bets:Blue

Subsequently typing ":" will autocomplete 'et' to 'ets:' and reduce the list to 
>
Assets:Cash
Assets:Bank
Expenses:Bets:Blue


I haven't implemented the autocomplete because in most cases I"m not 
sure what to do:


What if you have:

Assets:Cash
Expenses:Bets
Forgeta:Foo

All three match "et" but what do we do if the user type ":" ? In which 
situation can we autocomplete? In the current search, ":" autocompletes 
the current match (i.e., it moves the cursor to the next :). But in the 
mixed search, it's not clear what it should do.
Should I treat ":" as .*: (non greedy) in regexp? I think that would be 
pretty cool and it would be consistent with the legacy behavior.


In any case, the merging of the two searches actually does work 
currently and is fairly intuitive. So if you guys like this solution 
then I could remove the option, which would be really good!

Jean
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel