Hi,

I've got a Bootstrap 3 repsonsive theme working.  Well mostly working.  It is a php solution with some proposed changes to the core to delegate rendering to the theme.

The demo site is here.

The source is on github.

I wouldn't recommend installing it yourself, unless you're a developer at this stage.

Cambell

@Apmuthu if you've changed the code please fork the repo on github so the original author (me) can track your modification.  A zip file in this forum is unlikely to be tracked by me.

103

(7 replies, posted in Wish List)

I'm currently working on this.  The approach I'm taking is a pure php solution with no jQuery hacking of the classes.  I'm delegating the render code to a default renderer, and allowing themes to implement the render.  You can track progress if you like on my todo list

104

(4 replies, posted in Installation)

If you've checked it out of github directly you will need to run "composer install" while in the api folder.

105

(12 replies, posted in FA Modifications)

Updated code is here.  Unit tests are here.

106

(12 replies, posted in FA Modifications)

Ok. I think I've got it.  I'll add a check to ensure that voiding the original transaction does not result in a -ve balance unless the new transaction would correct that before it happens.  This should cover the special case.  The new transaction is covered by existing code.

107

(12 replies, posted in FA Modifications)

@Janusz Items 2, 3, and 4 are complete.  I've attempted 1 but I'm not that satisfied.  For example consider the following scenario:

1. Add a transfer $100 from current -> cash account at date d
2. Add a transfer $60 from cash -> current account at date d + 2 weeks
3. Add a transfer $80 from cash -> current account at date d + 1 week.

This succeeds and results in a -ve balance in the cash account of -40 in the existing code.

I've attempted a fix by setting a future date in the validation.  Please have a look and review the fix here.

This fix would fix your review #1 but would also change the existing functionality.

Note that I'm not proposing hard coding the date 2099.  I'd like to know what future date from the perspective of the transfer the date should be.  End of FY?  Current date?  Something else?

The bank edit feature can be compared to current master here.

108

(12 replies, posted in FA Modifications)

No not yet.  See my Trello board if you want to track progress on anything I'm doing with FrontAccounting.

109

(12 replies, posted in FA Modifications)

itronics wrote:

1. Edition can easily lead to negative balance on account which is not acceptable especially accounts of  on cash type. At least check_valid_entries() has to be  modified to forbid such situations testing change in transfer value against future account history.  But generally I guess it will be hard to achieve when edition is done as void/insert sequence instead of transaction modification, and without any limits (keep in mind situation, when one changes not only amount but also to/from accounts during edition).

In my testing cash accounts cannot go below zero when submitting the edition (red error box is displayed), but the current account can.  I think this is consistent with the current behavior of FA which allows -ve balance on the current account.   Let me know if there's a particular scenario you've got in mind.

itronics wrote:

2. Voided entries are still visible as zero amount transfers in bank account history.

Can you help me to see that?  Where do I get that view?  I see zero amounts for all manner of voided items in the bank reconciliation screen, and I can see zero amount transfers in the reconciliation also.

What's the preferred way to not display them.  a) delete them? (I'm guessing not)  b) not display them via some 'if voided' type function the don't display. c) something else?

itronics wrote:

3. There are a couple of small problems with variables declarations, which are not visible until debugging mode is on. Please set  $go_debug=1 in your config.php file during development to see it.

Yes, I can see those.  I'll go fix them.

itronics wrote:

4. For better UI consistency I would also add edition links to bank transfers in 'Bank Account Inquiry' page.

Will do.
Janusz

110

(12 replies, posted in FA Modifications)

I've implemented a bank transfer edit feature.  The patch is available here.

If you have some mechanism for accepting pull requests via either git or hg do let me know.

E2E tests are also available in my frontaccounting-wrapper repo.  If you're interested in incorporating the e2e tests it would be nice to push the current code down one level and have the tests in a folder that is not in the main src (htdocs) tree.

111

(5 replies, posted in Banking and General Ledger)

I've implemented a bank transfer edit feature as per the OP request.  The patch is available here.

If you have some mechanism for accepting pull requests let me know.

E2E tests are also available in my frontaccounting-wrapper repo.  If you're interested in incorporating the e2e tests it would be nice to push the current code down one level and have the tests in a folder that is not in the main src (htdocs) tree.

That should be

git://devel.frontaccounting.com/fa-stable

113

(10 replies, posted in Installation)

Maybe the permissions in the .git folder are not allowing us to fetch all the refs.

114

(10 replies, posted in Installation)

As far as I can tell its down.  Seems to be a firewall, or no daemon running on port 9418.  Last time I fetched was 19 June 2014.  See this post.

I've got two github repos.

1. A mirror of the front accounting git repo when it was online
2. A wrapper one level up, that I used for e2e tests and build infrastructure.

If you fork those then there is some chance that changes could be merged upstream.

Yes, I understand that there is the intention to have a git repo.  I'm pointing out that it is not currently operational.  I have cloned it before, and pulled from it before.  The last time I pulled from it was June 19, 2014.  You can view it via http, but that's not supporting the git protocol for fetch.  In the past I've fetched via the git protocol on port 9418.  Now I cannot do so.  As far as I can tell no other protocol is available.  You can see all the protocols that git supports here:

http://git-scm.com/book/en/Git-on-the-Server-The-Protocols

If one of those protocols is available and currently working do let me know. :-)

A couple of things

Is the table name really hard coded to be TB_PREFtable_name?  Or is table_name a variable in which case it should be $table_name.  It would make more sense to me for the column name you are adding to be a constant e.g. 'some_column' rather than a variable.

Does the database user have permission to alter table structure?  Most likely does worth checking though.

Check the syntax against this:

http://dev.mysql.com/doc/refman/5.1/en/alter-table.html
http://dev.mysql.com/doc/refman/5.1/en/create-table.html

You can also get good help on sql here:

http://stackoverflow.com/

ALTER TABLE  `0_users` ADD  `test` INT( 10 ) NOT NULL ;

117

(4 replies, posted in FA Modifications)

The GitHub Readme has a badge on it that shows the status of the build; passing or failing.

The full build log can be found on Travis.

Protractor uses the Jasmine test language framework.  Here's a snippet of the test code; it is very easy to read for code, and quite easy to write.

  it('transfers ok', function () {
    page.get('/gl/bank_transfer.php');
    expect(page.getTitle()).toEqual('Bank Account Transfer Entry');
    expect(page.getReference()).not.toEqual('');
    page.transfer('Current account', 'Petty Cash account', '1/2/2013', '11', 'Some memo', null);
    expect(page.getNoteMessage()).toEqual('Transfer has been entered');
  });

If folk would like to contribute tests I can give some guidance in getting setup.

118

(4 replies, posted in FA Modifications)

The tests are now running on Travis-CI

119

(4 replies, posted in FA Modifications)

I've started making some end to end tests using Protractor in order to test the FrontAccounting UI.  This will help keep the product stable during any refactoring / improvement.

If anyone would like to add to the test suite (which only has 1 test in it right now) please make a pull request against this GitHub repository.

Currently I've configured the tests to use either Chrome or PhantomJS (which works headless and slightly faster than Chrome).  I'll have a look at putting them up on Travis.

Or a bootstrap like typeahead like this one might work well.

121

(7 replies, posted in Modules Add-on's)

I've been looking into what it would take to get bootstrap3 working in a theme.  It would be more than just a theme as defined currently.  We would need to abstract some of the ui rendering into the theme.  i.e. many of the files under includes/ui which currently include a lot of inline styling on the tables for example.

The current render class could be extended for this purpose.

If you're using Windows you might need to apply this fix

Around about line 327 of includes/archives.inc, change:

  'name' => $temp['prefix'] . $temp['name'],

to:

   'name' => rtrim($temp['prefix']) . rtrim($temp['name']),

So, no official git repo at the moment then?

Yes, I can see the changesets on the official git repo.  put I can't pull them via git, the remote is set to:

origin    git://devel.frontaccounting.com/fa-stable (fetch)

Are you able to fetch from the official git repo?  If so what protocol / setting do you use?

Where can I find the current source code repository?  Currently I get a connection error on git:

$ git fetch origin
fatal: unable to connect to devel.frontaccounting.com:
devel.frontaccounting.com[0: 176.31.120.126]: errno=Connection refused

and sourceforge hg is no longer current.

I can see commits on:

http://devel.frontaccounting.com/git/?p=fa-stable.git;a=shortlog

If you have moved to git, any chance of moving to github?  It makes contributing so much easier for everyone.

Regards,
Cambell