Wednesday, 19 May 2004

There are always finite limits

Something that we just came across today doing some J2EE dev. work. In our app, there's a huge form where the users will do a lot of their work. (It was the user's decision to make it that big, not ours). Well, we're externalizing the strings 'cause of course it's got to work in French too. It blew up. There's a limit of how big the java complier will accept jsp's. I think that it's got something to do with all the struts libs bring pretty big, but whatever. So, we're going to break out the form into a bunch of includes and hope that works. I'll update later today.

It just goes to show that computers always have finite limits, even most of the time it doesn't seem like it. And at some point people will always hit that limit, perhaps by not doing things they were originally designed / intended for. Hit a wall, push it back, repeat.

As a side note, I just had to point out something the Peter posted about. Check out the atkins diet part, with sound. It's got swearing, so you might not want to do it on your speakers at work. I was hard pressed this morning not to laugh out loud... it would have been hard to explain. :-)

Update: It looks like using includes will work fine. ;-)
Listening to: Shakira - Eyes like yours


5 comments:

  1. ah. I was going to suggest breaking the form down into a number of tabs. That was what we did where I'm working (had a form with 190+ fields which rightly got split into a few pages...)

    ReplyDelete
  2. Ya, we have stuff in a bunch of tabs... but they wanted all this stuff on ONE tab 'cause they think that it will be slow... they asked it to be "faster" before we had any code written. It's more to do with psychology than technology at this point.
    The form wasn't even *that* big field wise. It's all the string externalization (struts stuff) that made it HUGE going to the complier. I think that the file was like < 30k, and was breaking on the complier that had a limit of 64 k... Yikes.

    ReplyDelete
  3. Our requirements for the form with 190+ fields came directly from the users as well.
    It's weird how your perception changes once you down into the details of how something is actually done.

    ReplyDelete
  4. Yeah, that bilingualism in the government causes no end of problems when it comes to development. I haven't really seen a good solution to it when I was there. There was solutions, they worked, but they were by no means good solutions.

    ReplyDelete
  5. For java stuff, google i18n. I would call this a good solution, but there are some things that you have to do slightly differently. And it's a good idea when building an app to not rely for code (functionality) what UI strings you are showing to the user for it to work.
    I'll do a post about it another time if anyone is interested. (i18n from a struts perspective)

    ReplyDelete