Just a question. At the moment for my terminal emulator I tear down and recreate all the field widgets each time the screen refreshes (a mixture of WText and WLineEdit).
So the user updates the screen and presses enter. The updates are sent to the mainframe which updates the mainframe screen. This is read and the Wt "screen" cleared - deleting all the widgets - and then new Widgets are created and these then are rendered for the user by Witty (not sure this longer explanation is clearer!) It works great. But I always envisaged optimising this so that if the "layout" of the screen is unchanged then only the text of changed fields would be updated and the widgets reused. So I need to develop some logic for this. The question I have is this - would Witty take advantage of this optimisation in the way that the AJAX and the communication between the browser and server works? Also IE seems to have some problems setting the focus to the right field (sometimes) - so I am hoping this might work better for IE - less confusing for the brain damaged blighter! Adrian ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
