Update on View Updates

[icedlava]

I don't mind changing things to match the consensus view of what's best.

I'm in a similar position and currently maintain a few different branches of the code.

For myself, right now I am keeping track of all updates to the main branch and trying to isolate my changes so that it will be mergeable with no change in functionality. That will likely become difficult if I keep going without merging, it's true.

Yes I have the same issues. Subversion is not ideal for branch management so I keep the code in an additional SCM to Subversion where I can more easily manage the branching and merging.

... thread about desired functionality, who wants to work on it, and timelines for implementation plus a discussion of what wishlist developments are likely to conflict?

I find the forums a little cumbersome but I'd be happy with that.

TWIG looks interesting, I'll give it a look,

I already know that a templating system is not currently on the books for webERP from prior discussion. That's fine, but I need it to reduce updating/maintenance of all the views in webERP. I'm happy to keep my custom branch updated and still have some views to go. Perhaps it might be an option in the future and I'll have something 'nearly' there already we can convert.

As to TWIG, I've used a number of template systems and wary of them depending on the objectives. However TWIG is very lightweight, has a good caching system, and the pros seem to out weight any cons that I can think of for webERP.

Again, thanks for the feedback,

Cheers,