On Fri, Mar 12, 2010 at 7:29 PM, Adam Thompson wrote:
> Chris Travers wrote:
>> LedgerSMB::Web::Request is designed specifically to provide HTTP
>> wrappers for workflow scripts. Thick clients wouldn't use it.
>
> I'm not sure this is really the best way to handle workflow - what about
> workflow
Chris Travers wrote:
> LedgerSMB::Web::Request is designed specifically to provide HTTP
> wrappers for workflow scripts. Thick clients wouldn't use it.
I'm not sure this is really the best way to handle workflow - what about
workflow in the non-web (CLI, thick client, etc.) scenario? OTOH, I
d
Hi all;
I think we should look at branching LedgerSMB 1.3 off this next week
since the basic ideas of 2.0 are starting to take shape. What do
folks think?
Best Wishes,
Chris Travers
--
Download Intel® Parallel Studio Ev
On Fri, Mar 12, 2010 at 5:40 PM, Adam Thompson wrote:
> Chris Travers wrote:
>> Here are some proof of concept struct definitions for 2.0. What do folks
>> think?
>
> I'm assuming you are indicating data types, not literal strings of '$'
> et al., right? Working on that assumption, for now.
$
Chris Travers wrote:
> Here are some proof of concept struct definitions for 2.0. What do folks
> think?
I'm assuming you are indicating data types, not literal strings of '$'
et al., right? Working on that assumption, for now.
> Also do you like right-justification or left justification of h
Here are some proof of concept struct definitions for 2.0. What do folks think?
Also do you like right-justification or left justification of hash keys?
Best Wishes,
Chris Travers
struct LedgerSMB::User, {
role_prefix => '$', # formerly from $request
username => '$', # normally