I find it totally undesirable to make or maintain any changes in the cataloging module for the purpose of going HTML-only. Your sense of server-side processing advantage may or may not translate to an advantage in actual environment constraints. Consider that adding a repeatable field would have to constitute a new request and response for each element, parsing the marcxl each time, aggregating form state changes in some yet undefined table. The server might validate the end results faster, but getting there just became 30 times as expensive and you still need to round trip to the server to get the results. I'd wager that exactly zero of our clients would prefer scriptless cataloguing, and would likewise be upset for Koha to sacrifice scripted features for it. Cataloging is already a huge amount of logic. Duplicating the plugins to operate cleanly as server-side validators would be a major undertaking in itself, and be more likely to introduce runtime warnings and fatals. Sent from my phone,b/c my power is out! --joe On Jun 29, 2009 7:53 PM, "Rick Welykochy" <rick@praxis.com.au> wrote: Cab Vinton wrote: > This was covered on the list a while back -- in Firefox it was taking > 40-50 s... As pointed out, this is because of Javascript. Question: can Koha operate properly with JS disabled? If not, why not? Observation: JS is quite slow compared the server itself. Perhaps the *HUGE* task of validating a MARC save could be (optionally) left to the server to validate. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Debra Jackson says she likes shopping at the Dollar Palace because it's convenient and casual. "I don't have to get dressed up like I'm going to Wal-mart or something," she said. -- spotted in a newspaper _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lis...