[SM-DEVEL] Re: javascript standards in SM design

[<pdo...@an...>]

>> This happens a lot when plugin authors (including yours truly)
>> blatantly refuse to pay attention to that standard.  ;>  I suppose the
>> argument would be that said plugins require javascript, otherwise
>> you're out of luck.  There isn't a way to turn it off other than
>> deactivating the plugin that I know of.
>
> Oh, I don't mind the plugins that require javascript (in fact, I don't
> think the spelling plugin could be nearly as easy to use if it were don=
e
> in pure html), but I was concerned about the core functionality.. for
> example, if would be really nice if the "Compose in New Window" option
> would disappear if the user didn't have javascript capability or if the=
y
> chose to never use it. I really like the way the Address Book is handle=
d
> - offer javascript but provide an html alternative if this is considere=
d
> "core" functionality of SquirrelMail.
>
> For example, I submitted a bug regarding the Compose in New Window
> option (which is done in javascript) that got fixed recently; if
> "Compose in New Window" was selected and a user clicked Compose, Reply
> or Forward, SM wouldn't do anything at all.. now I see where it will
> open the Compose/Reply/Forward in the right frame using good old html i=
f
> javascript is not available, which is definitely better. =3D)

If you can list any other ones, that would help us target and fix them.  =
;>

> I just know I won't get away with rolling a CVS version of SquirrelMail
> into production - the technical review processes here at TI would shoot
> it down in a hurry, so I'm hoping for a few 1.4.1, 1.4.2, etc. releases
> in the next couple of months.

1.4.1 is coming soooon.  soonish?  open source time.

I understand that mention of "cvs" spells fear in the eyes of management,
but you could explain to them the difference in the two main SquirrelMail
cvs branches: stable and devel, where anything risky and new goes in
devel, whereas the only changes to stable cvs are bug fixes and
enhancements that have been tested and proven in the devel branch and are
back-ported to the stable branch.  Therefore, they are *more* likely to
get a solid webmail product and access to fixes for any problems that
arise much faster if you roll out with the stable cvs.

Just my 2 cents...

 - paul