RE: NewEra Window Painter Editor

> >One of the big problems working with NewEra is the programming editor within >the Window Painter. It hasn't, for a example, "search & replace"? it doesn't >look good to me! > >Informix recommends to use CodeWright, it looks great, but I realize that it >cannot be used at all, because the Window Painter has not regenerability >features: If U make a change in the NewEra code using another editor, U >cannot re-edit the original window in order to keep your changes! > >If you are developing or developed applications using INFORMIX-NewEra, how >do you solved this situation? > >TO INFORMIX: I THINK THAT YOU HAVE TO CHECK THIS. IN THE DEVELOPMENT >PROCESS, FRECUENTLY YOU HAVE TO GO TO THE CODE, KEEPING THE WYSIWYG FEATURES >BUILT IN THE IWP. FOR EXAMPLE, WHAT HAPPENS IF I WANT REUSE A SOURCE CODE >MAKING A LITTLE CHANGES REQUIRED FOR THE NEW APPLICATION? I WOULD LIKE TO >COPY THE FILE AND THEN RUN A FIND & REPLACE -> I THINK THAT'S THE EASIEST >WAY AVAILABLE! Your points are right on the money. The development tools supplied with NewEra are the products weakest points. FWIW, version 3 is supposed to be MUCH better. For now though, we deal with the situation you describe by using 3rd party editors to edit the .wif files directly. We then open the relevant .wif files in the window painter and save them out again to regenerate the associated .4gl and .4gh files. This works just fine as long as you are careful not to screw up the .wif file. Another option is to break your bigger functions out of the .wif files into their own .4gl and .4gh files (that is, w/o a corresponding .wif). You can then maintain these files without worrying about the window painter. All you need in the NewEra events are calls to your functions. If you have any questions about details, please write. --Craig (craig@chemistry.utah.edu)