At 08:59 PM 3/30/01 -0800, Michael R. Bernstein wrote:
"Phillip J. Eby" wrote:
Aha. I think I understand what you're doing now. You have an "Image" and
you have a "Rendering". Two classes, different behaviors. I'm assuming
that originals and thumbnails and whatever other renderings exist
"Phillip J. Eby" wrote:
At 08:59 PM 3/30/01 -0800, Michael R. Bernstein wrote:
The terminology I'm using is ArchiveImage (for the 'Image'
class) and RackImage (for the 'Rendering' class).
I'd recommend a name change for RackImage, at least at the Specialist
level. If you don't like
After playing with Page Templates I have one question/idee.
Would it be completely stupid to be able to nest Macros.
That is, you would have one MainMacroTemplate defining
several Slots/SubMacros and then make several SubMacrosTemplates
that inherents from the MainMacroTemplate, defining the
From: "Johan Carlsson" [EMAIL PROTECTED]
Would it be completely stupid to be able to nest Macros.
That is, you would have one MainMacroTemplate defining
several Slots/SubMacros and then make several SubMacrosTemplates
that inherents from the MainMacroTemplate, defining the Slots/SubMacros
as
"Phillip J. Eby" wrote:
By the way, RenderingKinds is a sort of specialist that hasn't been
discussed much outside of the apps Ty and I work with - the "constant"
Specialist, one which contains application configuration or metadata rather
than "content". Oftentimes it's handy to simply
Hi all,
I had some questions about SkinScripts:
1) Are there any naming conventions for SkinScripts?
2) Is there any reason (other than factoring) to split
SkinScripts up, or is putting all your declarations in one
SkinScript ok?
Thanks,
Michael Bernstein.
