|
From: Sean A C. <se...@co...> - 2002-11-05 04:44:25
|
On Friday, Nov 1, 2002, at 16:19 US/Pacific, Nathan Dintenfass wrote:
> Well, I've managed to eat up sizable portions of my Friday talking
> Modus.
> Which is fun.
:)
> Yes, definitely not just persistence. It's about doing away with a
> lot of
> mundane, repetitive tasks while offering a tight metaphor for coding.
I guess my concern is that I believe we need a solid persistence layer
first, on which to build an application framework. I'm worried that by
trying to create a single all-purpose layer, it won't do either very
well.
> Jeremy has demonstrated, that Modus 1.0 could be used in the
> context of Fusebox -- though eventually Modus (or a related project)
> may
> grow to supersede much of what Fusebox is about.
I think it will be interesting to see how "Fusebox MX" will be
received... but Fusebox does not address persistence so I believe a
focused persistence layer can coexist peacefully with Fusebox MX :)
> True, true. Though, personally performance tends to be a lower
> priority for
> me because I rarely work on sites that have huge volume.
I think performance is important enough in real life for enough CFers
that we do need to consider it.
> wouldn't be a big deal in my mind if Modus 1.0 was not an "Enterprise
> Class"
> system if it is useful to a large swath of CF folks.
It would be nice if Modus 2.0 was not radically different to Modus 1.0
tho' so I think we need to get enough confidence in the APIs and
architecture of Modus 1.0 in terms of basic performance - or the
ability to improve performance without changing the API / architecture.
> Well, depends on what "fast" means. Is less than 500 ms for a page
> that
> both displays all the press releases and has everything necessary to
> edit
> one (including having retrieved one from persistence to get it ready to
> edit)? For most applications that is acceptable performance. Is it
> great?
I don't believe it's acceptable.
> "Linked" components (the "foreign key" reference model) are the way to
> go
> for Modus.
Agreed.
> Oh, yes. I never intended for pressRelease.renderHTML(), only
> pressRelease.getField("image").renderHTML() -- which just outputs:
>
> <img src="http://[serverPath]/imageName.gif">
OK. I'd still prefer separation of presentation from persistence of
course :)
> Yes, label is "friendly name" -- localization is a great issue. I
> guess it
> seems like someone who is building a multi-lingual site will need to
> find an
> alternative way if they want some generic form generation to happen (or
> submit changes to Modus that allow it ;)
As long as the Modus architecture doesn't *preclude* localization, I'll
be reasonably satisfied...
"I can smell your brains!"
-- Mittens the Kitten : http://www.matazone.co.uk/theotherside.html
|