On 8 Nov, 14:37, "Paddy O'Brien" <
paddysem...@gmail.com> wrote:
> It seems to me that you shouldn't be putting anything that requires a
> WYSIWYG editor in a configuration file.
Well this is a slight beef I've had with joomla for some time.
basically the component consists of 1) a form and 2) a response to
that form. The client has asked for html content (that is to say the
ability to embed images and formatting into the text) before and after
the form, and on the response page.
>
> Are you not mixing content with configuration by doing that? A
> database table seems like a more appropriate place for this sort of
> data.
>
Is a database table that has three rows that consist of nothing but id
and content somehow not overkill for this feature? There are plenty
of components, even stock ones, that allow for a text area in places
like this which can be very long and involved, and into which a user
can (and often does) type html.
These aren't pages that will be accessed by direct link or something
like that, they're just small spots on a larger component page that
should be able to embed images and stuff without the user having to be
html-savvy. I strongly dislike the hackish "pick an image from this
drop-down" method, especially since several images may be called for
in some instances, and flash may be needed as well.
I guess I fail to see how 1000 or so characters of basic html differs
so fundamentally from a similar amount of plain-text.
As it stands, with my timeframe and the current state of my thinking,
a database table is probably exactly where this content will end up
for lack of anything else to do with it, but I'm really not happy with
this solution.
Thanks for your input though.