Getting to uniPaaS How to get from here to there

1 Getting to uniPaaSHow to get from here to thereBy Heidi SchuppenhauerGetting to uniPaaSWith apologies to Robert BurnsShould old long programs be forgotand never brought to mind?Should old long programs be forgot,or be brought up with time?For uniPaaS , my mate,For uniPaaS we cheer!We'll take a new conversion yet,For uniPaaS is surely you'll buy your pint cup!and surely I'll buy mine!And we'll take a cup o' Guiness yetFor uniPaaS is old long programs be forgot, or should they be made new?With uniPaaS the answer's clearby the time, you start, you're to uniPaaS !1 Getting Started in eDeveloper 104 2010 Enter your company name1 Welcome to uniPaaS !Magic Programs just keep going and going .. Magic Programs never give up. After all these years, I'm still converting programs from no, even V3! .. into the latest version, which is now uniPaaS . Thing is, those oldprograms still work. How many programs do you know from the 1980's that still work?And it's not even that hard to convert them, as you'll , you can waste a lot of time doing conversions.

2 The first few I did took many,many hours. Then I got smart. Now they don't take long at all. So, here are the tricks thatI've learned, in hopes they help you ExportIn general, it is easier to work with the application in the newer versions of Magic. The toolsare better: you have nice things like good cross-referencing and better error to uniPaaS !5 Getting Started in eDeveloper 10 However, there are a few things you should so before you export, or your conversion mightfail entirely. These principles apply no matter what version you are currently sure you have all the RightsThis may seem intuitively obvious, but it's a common cause of conversion problems. Youmay be able to work fine with the application, but be missing a Right to, say, the item you do not have a Right to will not be sure you have good backupsOK, this may seem obvious too. But it is very likely you will need to go back to "the original"at some point for reference, if not recovery. Have your backup control file in some placethat is really easy to reference.

3 Back up early and often!Delete unused itemsIf you have items you know are unused and unneeded, this is a good time to get rid of a syntax checkBefore you export, do a syntax check on each of the repositories: types, files, programs. Fixany problems that may the application, then re-import itExporting and re-importing will fix some internal errors that may exist. Or, if the export orimport crashes, you will know there is a corrupted program that you need to fix (or lose). This SectionYou probably won't need all the steps I'm showing here. It depends what version of Magicyou are currently running. Originally this material was in several different books, but I'mincluding it all here for convenience, and also because you really do not need to know howGetting Started in eDeveloper 106 2010 Enter your company nameto convert from 7 to 8 to 9, if you are converting from 7 to 10. The intermediate steps aren'tneeded, except for a simple you start though, you should read the "Migration" materials that come with will be updated with whatever current changes exist.

4 Then, start with your currentversion: If you are in V5, start with exporting from V5. If you are in V7 or V8, start with Export From V7. If you are in V9, start with exporting From of the examples that follow assume you exported from V5. That is because, it is thehardest case. If you can convert from a DOS program, converting from V7 is easy! Also, some of the screen prints are from V9. This is because some of this material wasadopted from a "Conversion to 9" document. The differences are minor, but, since you allare programmers, I know that you are attuned to minor differences. That is what we section assumes you know the basics of how uniPaaS works, which was covered inthe previous section of this book. If you don't, spend some time learning it before youchange your programs too much. Work with some simple programs with 2 or 3 fields,before you try to figure out why a DOS program from 15 years ago acts differently inWindows. Most programs will convert nicely, but the ones that don't require some learningon your From V52 Getting Started in eDeveloper 108 2010 Enter your company name2 exporting From V5 The first step is to export your application from V5 ApplicationHere is a typical V5 that all the text is fixed (this is DOS, after all).

5 The "buttons", in this example, are notbuttons at all, just prompts to tell you which hot keys to press. ( there are usually hot keysthat don't show up on the screen too, because of limited real estate).The text, however, is very easy to read. there is a nice thick bar showing what line we areon. The keyboard is really easy to use, and the user does not need a mouse. The menu staysup all the time, so it's easy to find users will be used to these features. We will show you how to get into Windowswithout losing the more useful DOS From V59 Getting Started in eDeveloper the ExportExport the application as you normally would. Name the export something meaningful, incase you have to go back to it, and save the name somewhere for reference. We namedours " ".It is often helpful to do the export in "pieces", doing the Types, Files, and Programsindividually. Remember that in V5, you can't have file names over 8characters Generator ProgramsThere is no upgrade for the Report Generator programs.

6 If you have any of these in yourV5 application, they will have to be into V7 or V83 Importing into V7 or V811 Getting Started in eDeveloper 103 Importing into V7 or V8 You can't jump from V5 directly into V9. You have to import into V7 or V8 first. You do not need to work with the code much in V7 or V8. It is only an intermediate step. Ifyou don't have a copy of either, you can have someone else do this step for you and sendyou the exported version. the ImportWhen you do the import, be sure to select Import Getting Started in eDeveloper 1012 2010 Enter your company nameThe Optimization type is critical. We'll show you the effects of the optimization type in thenext section. You will want to import it with Optimization As is, which we will of the different kinds of importsThis is the most critical part of the conversion effort. The problem is, when you go fromDOS to Windows, the fonts and colors are handled very programs use a fixed-width font, and there was only one font.

7 When these programsare imported into V7 or V8, the spacing just doesn't work well. So you can spend hundredsof hours just reformatting the forms to look decent. ColorsAnother issue is color. DOS programs used a lot of color, partly to make up for the lack offonts. Some colors were used as "invisible" colors, to make a field look like it haddisappeared. Color usage is not affected by the import into V7. It is affected by the import into V9, andwe will cover it very important factor is that the V5 reports include font information in the report this example, each color represents a printer command. Also. note the graphical into V7 or V813 Getting Started in eDeveloper 10 Now, it may make sense to convert all the reports to GUI, but in real life, that just isn'talways practical. These old reports can work just fine with Windows and newer printers,using 3rd party 3 DGetting Started in eDeveloper 1014 2010 Enter your company nameHere is whathappens when weimport the screen as Optimized that the list isfar smaller.

8 The textdoes not fit well, andsome of it is cut reports haveretained their colorsand print attributes,but have lost theirgraphic into V7 or V815 Getting Started in eDeveloper 2 DIf we select to importoptimized 2D, then thefields are cramped. Muchof the text is cut print attributes areintact. However, all thegraphical lines are gonefrom the Started in eDeveloper 1016 2010 Enter your company AsISNow, suppose weimport As , all the text is in a fixed font,which is a little old-fashioned looking, butit , the graphiclines all look like weirdA's and little 3' into V7 or V817 Getting Started in eDeveloper 10So what is the solution? Letter Gothic LineThe answer is: use afont that works like aDOS there wasonly one font in theDOS days, all yourforms will, when youimport them, use Font 7. So all youhave to do is import As Is, and make sureFont 7 will displaygraphical linescorrectly. Fortunately one suchfont exists, and it'sfree. It's calledLetter Gothic Line,and is included withthis class.

9 Just drop itinto your WindowsFont Started in eDeveloper 1018 2010 Enter your company nameThen, we make surethat Magic points tothat font as font now we arealmost looking ok! Allwe need to do is fixthe colors, and theapplication will beusable, if not modernlooking. When weimport this intouniPaaS, we'llmodernize it into V7 or V819 Getting Started in eDeveloper Import LogWhen you import the application from V5, an import log will be automatically created,called , where XX is the control file prefix. You want to look at can fix these issues in V7, or wait and do them in uniPaaS . Usually it is easier to fixthings in uniPaaS . However, the "Expression parse errors" may indicate something serious, Getting Started in eDeveloper 1020 2010 Enter your company namesuch as an embedded special character, or a Right that you don't Alt-key problem can also be fixed in From V7 Once you have importedthe V5 application, checkit over. Make sure youseem to have everything,and do a syntax check.

10 Then export it and re-import it into an emptycontrol you are ready toexport it into V94 Getting Started in eDeveloper 1022 2010 Enter your company name4 Importing into V9 Your next step is to importthe application into the "Overwritedefault menus" screenappears, you might want tosay "No". Although this willcreate duplicate entries, themenu options are differentin into V923 Getting Started in eDeveloper 10 Again, a log will be created, which you should look and FontsIf you read the conversion literature for V9, you will see that you are supposed to convertyour colors and fonts in going from V8 to NOT DO THIS. Your V5, 6, 7 or 8 fonts and colors will work fine in uniPaaS . Theywon't work in V9, but you don't care at this point, because you aren't going to be running inV9. exporting from V95 exporting from V925 Getting Started in eDeveloper 105 exporting from V9 When you export from V9, the main thingyou have to do is the Export for This creates a file that is ready to beconverted to XML in uniPaaS .