[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tracking Customers

Our current plans are to address the accounting side in 1.4.  THink of
a lot of the contact revisions as being a sort of trial ground for the
new architecture, as well as converging with user management and
security which is a feature of the new system.  So while this is not
the highest or most urgent priority, now seems to be the best time to
attack it.

BTW, Josh is an excellent database engineer. In fact, I am personally
very greatful that our core team has grown to include so many star
engineers.  I expect that we will be able to be well positioned to
attack the accounting side in 1.4.

Best Wishes,
Chris Travers

On 3/14/07, Charley Tiggs <..hidden..> wrote:

Understood and agreed.  I like Josh's approach very much.

All that said, please know that I do understand that there are higher
priorities than this (namely, making the accounting side better/easier
for everyone).  I also know that my situation is a little extreme among
the current users of LSMB.  So I'm willing to wait.  If I can't wait,
why, I'm sure that I could roll up my sleeves and jump in and help!  :)

Charley

Chris Travers wrote:
> Understood.  In short, I think we need to support your customers needs
> in some reasonable fashion without making the workflow longer than it
> needs to be for others.  And the current plan allows for that,
> according to Josh's post above.
>
> 1)  Based on Josh's response above, I think his responses will allow
> for more effective balancing between streamlined workflow for most
> users (who do not need this) and longer workflow for those that do.
> Most of this is going to amount to engineering details that can be
> worked out as this takes shape.  It is clear from his reponse though,
> that Josh has put in a lot of thought into these issues :-).
>
> 2)  One of the points I have argued and will make again is that there
> needs to be a separation between what is possible to implement for a
> customer and what is actually implemented by default.  Even with
> Josh's comments above, until we can get an Ajax implementation in
> place, workflow is not likely to be easily optimized for the click and
> wait model.  Having a good framework which *can* do this but may be
> simple by default may be a good step forward.   Note that we are
> working on making this much easier to customize on the UI side.
>
> Best Wishes,
> Chris Travers
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Ledger-smb-devel mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Ledger-smb-devel mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel