Sort transactions by date within a day

GT-I9070 H gti9070h at gmail.com
Fri Jul 3 23:56:12 EDT 2015


2015-07-03 3:22 GMT-04:00 Geert Janssens <geert.gnucash at kobaltwit.be>:

>
> Hi GTI,
>

Hi Geert,

Thanks for your attention!

You spoke with propriety and spoke very well. I understood your thinking on
community and motivations, you made me feel what it's thinking as a
community!



> In the end you are free to do whatever you like of course. If you are
> most experienced in VB/VBA, I understand that is your preferred language
> to solve your needs.
>
> Going that route you will however immediately loose the interest of most
> people that are most likely able to help you...
>

I'm sorry to have frustrated the not-Windows community when I opted for
Windows and VB/VBA.
If I knew anyone care that my choice maybe I would not have done. At the
time I almost chose C.

I never thought about being a developer, I never thought as a
cross-platform community, I hope not too late.

I understand that people would have more motivation to help me if they had
the hope of being able to benefit from my code, but I hope they have other
motivations to help others.



> VB/VBA is a Windows only thing while gnucash is a cross-platform
> application. I guess your preferred platform is Windows, otherwise
> VB/VBA would not have been your language of choice :)
>

Surely. You're right again.
The number of Win users is much higher.
I've worked with UNIX but never fascinated me.
You know how we are, we like beautiful things even if the times are not the
most functional.



> There is not much I can add here. John already explained why we insist
> on using the API's we offer.
>
> One possible other motivation could be that gnucash is a community
> effort and we try to leverage this as much as possible. So if someone
> writes an improvement and is willing to share it, we gladly include it
> in the project as a whole. For this to be possible, it must be written
> in a language that is universally available wherever we support
> installing gnucash and should really use the gnucash engine code to
> modify data.
>

As you said, VB/VBA is not a universal language. I'm sorry I can not help
with improvements.

I understood, John explained very well technically but I think you
explained better, you explained humanly the importance of Commity thinking.

Frankly I came here thinking to integrate me as a user and not as a
developer. I will help as I can, perhaps, if I be proud of something I
wrote (Only VB/VBA), I will share. At this point the only thing I have is
an Excel exporter to QIF very customized. There began the problems to enter
the exchange rate in GnuCash what made me think about writing directly into
the GnuCash XML data file.

I plan to write a GnuCash exporting to Excel to close the circle, this I
need to write to feel freer and more comfortable.

If anyone knows one ready and free, please inform and spare me this job.



> I'll add that unfortunately Windows is by far the most difficult
> platform to develop for gnucash on. The python bindings are not
> available and building the C code is ... clumsy and slow.
>
> So I'm not sure what would be your best route. Good luck.
>

Thanks.
I have no choice, or a developer implements what I need or I will do in
VB/VBA.

My best route is to play with the codes if it works I'll tell you  :)


Best Regards
GTI


More information about the gnucash-user mailing list