RE: [Modus-devs] Re: New Code Posted

[Nathan D. <na...@ch...>]

Yes, exactly.  A facade is not a User Interface.  Thus, things that are for
outputting to a user interface should not be called a facade ;)

The issue with custom tags is that they don't have access to the scope of
the calling page (absent the very ugly "caller." syntax).  My point is that
if we just have something in Application.cfm that sets something as a local
var called "modus" then a custom tag will still have to use the server.modus
or request.modus or application.modus construct -- I'm trying to keep the
code inside my custom tags looking the same as the code outside my custom
tags.  I'd rather not use application.modus because many applications don't
use the CFAPPLICATION tag.  Given that we're moving to "Modus as service" as
our model, server.modus makes the most sense to me (why copy it all into the
request scope, after all?).  Make sense?

 - n
  -----Original Message-----
  From: mod...@li...
[mailto:mod...@li...]On Behalf Of Sean A Corfield
  Sent: Thursday, November 14, 2002 12:53 PM
  To: mod...@li...
  Subject: Re: [Modus-devs] Re: New Code Posted


  On Thursday, Nov 14, 2002, at 11:56 US/Pacific, Jeremy Firsenbaum wrote:

    I do think the term "facade" is not particularly friendly.  I could even
see
    it being simple "ui" -- a term that is both well known and very
descriptive.


  But a facade is not a User Interface!


    > No problemo - this was Sean's suggestion so I thought I'd try it.
    > The UDFs are really just directing traffic to the appropriate
    > facade. This could also be implemented as a cfc. This way a
    > Application.cfm could have something like:
    >
    >      modus = server.modus.udflib
    >
    > so the calls would be: modus.get(id) and modus.put(object).


  That's sufficiently elegant for my tastes. I'm just trying to suggest ways
to reduce the amount of (unnecessary) typing people have to do.


    Yeah, I figured this was more proof-of-concept than it was API proposal.
My
    issue is that it would be great if the developer types the same thing
inside
    a custom tag as they do outside a custom tag.  That would require
something
    like server.modus.get() or request.modus.get() every time, though.


  I don't understand why custom tags makes a difference - could you explain?