On Jul 20, 2011, at 4:43 AM, Pascal Robert wrote:
>
> Le 2011-07-20 à 03:50, Amy Worrall a écrit :
>
I'm somewhat a D2W novice… is R2D2W a 'look' in the same way
ERModernLook is? Or are they different sorts of things?
>>>
>>> Yeah, it's just another look framework.
>>
>> How does it
Le 2011-07-20 à 03:50, Amy Worrall a écrit :
>>> I'm somewhat a D2W novice… is R2D2W a 'look' in the same way
>>> ERModernLook is? Or are they different sorts of things?
>>
>> Yeah, it's just another look framework.
>
> How does it compare to ERModernLook in other aspects? I was going to
> use
>> I'm somewhat a D2W novice… is R2D2W a 'look' in the same way
>> ERModernLook is? Or are they different sorts of things?
>
> Yeah, it's just another look framework.
How does it compare to ERModernLook in other aspects? I was going to
use ERModernLook, after watching the WOWODC videos about it.
On Jul 19, 2011, at 9:39 AM, David Holt wrote:
> Hi Amy,
>
> On 2011-07-19, at 9:24 AM, Amy Worrall wrote:
>
>> On Tue, Jul 19, 2011 at 4:50 PM, Ramsey Gurley
>> wrote:
>>> Personally, I find this approach the simplest. The main problem I run into
>>> here is rule system caching. ERD2W doe
If you're already using ERDirectToWeb and ERJavaMail, I won't hurt to include
it. It's a pretty nice framework, but needs some love in places (missing a
migration for instance). It provides scaffolding for mailable exceptions,
audit trails, and user preferences for things like batch size and s
> Alternately, the security manager could get the user from the thread too. The
> method signature would still look the same.
>
> ERCoreBusinessLogic does this with the 'actor'. You can look at bug tracker
> to see an example. Just store the user on the session, then you can put the
> user on t
On Jul 19, 2011, at 11:44 AM, Chuck Hill wrote:
>
> On 2011-07-19, at 11:36 AM, Amy Worrall wrote:
>
>>> I'd centralize all knowledge of this in some object like SecurityManager
>>> whose job it is authorize user actions. You could provide access to that
>>> via the session, but I think a be
On 2011-07-19, at 11:36 AM, Amy Worrall wrote:
>> I'd centralize all knowledge of this in some object like SecurityManager
>> whose job it is authorize user actions. You could provide access to that
>> via the session, but I think a better approach is to use ERXThreadStorage
>> and access it
> I'd centralize all knowledge of this in some object like SecurityManager
> whose job it is authorize user actions. You could provide access to that via
> the session, but I think a better approach is to use ERXThreadStorage and
> access it via the thread. That way you avoid needing the compo
On Jul 19, 2011, at 9:24 AM, Amy Worrall wrote:
> On Tue, Jul 19, 2011 at 4:50 PM, Ramsey Gurley wrote:
>> Personally, I find this approach the simplest. The main problem I run into
>> here is rule system caching. ERD2W does a fantastic job of caching to keep
>> the rule system really fast,
Hi Amy,
On 2011-07-19, at 5:55 AM, Amy Worrall wrote:
> Hi! I have a question about good app design.
>
> I know that, as mentioned in the WOWODC videos I've watched, a common
> beginner mistake is to put most of the logic in the page components.
> Indeed, I've been guilty of that myself in apps
Hi Amy,
On 2011-07-19, at 9:24 AM, Amy Worrall wrote:
> On Tue, Jul 19, 2011 at 4:50 PM, Ramsey Gurley wrote:
>> Personally, I find this approach the simplest. The main problem I run into
>> here is rule system caching. ERD2W does a fantastic job of caching to keep
>> the rule system really
Hi Amy,
On 2011-07-19, at 5:55 AM, Amy Worrall wrote:
> Hi! I have a question about good app design.
>
> I know that, as mentioned in the WOWODC videos I've watched, a common
> beginner mistake is to put most of the logic in the page components.
> Indeed, I've been guilty of that myself in apps
On Tue, Jul 19, 2011 at 4:50 PM, Ramsey Gurley wrote:
> Personally, I find this approach the simplest. The main problem I run into
> here is rule system caching. ERD2W does a fantastic job of caching to keep
> the rule system really fast, but in the case of auth logic, it isn't hard to
> imag
Hi Amy,
On Jul 19, 2011, at 5:55 AM, Amy Worrall wrote:
> Hi! I have a question about good app design.
>
> I know that, as mentioned in the WOWODC videos I've watched, a common
> beginner mistake is to put most of the logic in the page components.
> Indeed, I've been guilty of that myself in app
you might think of some of it like this
you want to separate things that go and get data, parse and deal with it from
the things which then present user information, contain user context and
generally navigate and control user interface.
that's always a good idea because even if it takes a bit
Hi! I have a question about good app design.
I know that, as mentioned in the WOWODC videos I've watched, a common
beginner mistake is to put most of the logic in the page components.
Indeed, I've been guilty of that myself in apps I've made in the past.
I know the fundamentals of MVC from my back
17 matches
Mail list logo
