Re: [Hastymail-devel] Post 1.3, separation of presentation & app layers

[Mrten <mrt...@ii...>]

Om 21:57 op vrijdag 18 maart 2005, Jason Munro:

> Now, for me, the only question is performance. If the performance
> hit is within my acceptable limits I see no reason not to go
> mainline CVS after a bit of branch testing and tweaking.

i have one other objection perhaps: right now hastymail is easily
installed on a fairly restricted server.

overhere we run php in safe_mode, have quite a few functions disabled
("disable_functions =3D popen, shell_exec, exec, system, dl, passthru,
proc_open, readfile, proc_nice, proc_terminate, ini_set", why anyone
would have a web-scripting language start shell-programs on its own is
beyond me), are anal about open_basedir, have error_reporting set to
E_ALL, have register_globals off (ok, enough :), and hastymail Just
Works.

i hope that advantage won't be lost using smarty.

and while all the arguments about a writing a *completely* different
interface is not possible with CSS are true, i wonder if you're not
steadily moving into the "everything and the kichen sink" mode with
these all-powerful templates.

an extra left-hand folder-listing is easily added with an iframe that
can be set to display: none in the sheets that dont need it. but it's
true that it would be harder to accomodate *every*one with CSS.


(and i couldnt resist: i created http://kyra.ii.nl/~mrten/hasty/ to
demonstrate the ease of RTL vs LTR with CSS. choose the alternative
stylesheet to see the layout reversed)

Mrten.
--=20
Reverse-engineering design assures 'bug-for-bug' compatibility