The Magic of eDeveloper

More Images

2011-12-21T00:13:00.001-08:00

Testing Stuff

2011-12-14T18:32:00.000-08:00

Test Blog Article with map...

The Image Blog

2011-11-28T23:51:00.001-08:00

Nothing

2011-11-02T22:51:00.000-07:00

artwork

2011-10-24T13:33:00.000-07:00

Visual Appearance

2011-10-03T17:39:00.001-07:00

Image FIle

2011-10-02T11:06:00.001-07:00

Graphic FIle2

2011-10-01T10:40:00.001-07:00

Graphic File Display

2011-09-30T19:02:00.000-07:00

Graphics Posts

2011-06-24T12:39:00.000-07:00

miscellaneous

2010-11-23T11:01:00.001-08:00

iBOLT Graphics

2010-09-09T11:46:00.001-07:00

Graphic Images

2009-12-31T14:28:00.001-08:00

See The New uniPaaS Blog

2009-06-08T14:46:00.000-07:00

This blog has been replaced by the Magic of uniPaaS blog to reflect the name change from eDeveloper to uniPaaS. Please see the new uniPaaS Blog

MIUG Business Networking Conference 2008

2008-04-25T15:46:00.000-07:00

Just saw a preview of Avikam Perry's roadmap announcement. Wow! I can't tell you what I saw, but I can tell you it will lead to unprecedented power for developers and huge benefits for business organizations running Magic applications. It is very important that you actually be present for MIUG as this presentation is not likely to be available in any other forum until what is being shown is actually released. You will want to prepare for this and the only way to do so is to be present at MIUG.

Magic Link Interview with Steve Blank

2008-03-31T13:30:00.000-07:00

Steve Blank of S.G. Blank Consulting is no newcomer to eDeveloper™. His experience with, and advocacy of the platform, goes back more than 20 years to his introduction to Magic version 3.5 and it’s been his “tool of choice” ever since. But Steve is more than just a user; he’s an active contributor to the system’s capabilities. One example is the DDF Maker Wizard—a utility provided in eDeveloper V10—that lets developers enhance the eDeveloper studio by making their own utilities and wizards.

Magic Link: Tell us a little about your business.

Steve Blank: S.G. Blank Consulting only has one employee—me. I specialize in three different areas. First, I provide training for in-house developers on the latest aspects and features of Magic’s eDeveloper. Second, I speak at conferences and present seminars/classes on different aspects of eDeveloper. Third, I provide custom programming services to a handful of customers who, generally speaking, aren’t big enough to have their own in-house staffs, but who see the benefit of custom applications. It’s in this third area that I spend most of my time. I’ve been working with eDeveloper for about 20 years, since version 3.5, when it became my tool of choice, and I’ve been using it ever since.

ML: What types of training services are you called on to provide?

SB: Most of the companies for which I provide training are small to mid-size businesses with five or fewer developers. They are typically organizations that have developed their entire business system in Magic and, so, have a huge investment in it, and are looking for ways to improve performance or to solve other problems that have arisen as a result of their growth. So I’m usually not training people who are new to eDeveloper, but rather people in companies that have used the product for a long time and are looking for ways to make things better. The areas on which I tend to focus are multi-user concurrency, performance, database design, and data integrity.

ML: Do you typically provide training, then, for the same customers on a repeat basis?

SB: Yes. Often, I will get called in by a company that is experiencing a specific problem and, after helping them to resolve that problem, will then get called back to provide a wider scope of training. For example, a few years back, I received a call from a company in El Salvador that was experiencing increasingly serious locking and performance issues with their eDeveloper application. I went down and, after spending a couple days analyzing their application and database, showed them how to solve their problems and gave them some additional pointers on best practices. Each year since then, they’ve brought me back down for a week to train their development team on what’s new in eDeveloper, and to provide in-depth instruction on topics such as transaction processing and error recovery.

ML: You mentioned that you frequently speak at conferences. What types of things do you speak about?

SB: I tend to address many of the same topics that arise in my consulting and on which I often focus in my training, as well as to explore newer features in eDeveloper such as integrating ActiveX controls and COM objects. I really enjoy attending and presenting at conferences, for a couple of reasons: first, preparing for conferences gives me an excuse to experiment and create demo programs from which I learn something myself; and second, it’s a great way to network and to further my reputation in the business in a way that comes back to me. Plus, it’s just plain fun to meet and talk shop with people literally from all over the world.

ML: What are the kinds of issues that people have with eDeveloper that cause them to contact you?

SB: One of the strengths of eDeveloper is also one of its weaknesses: it’s really, really easy to write complex applications without a lot of formal training. Frankly, one can sit down and crank out some pretty amazing stuff without having any formal training in programming or database design because the tool abstracts the complexities to the point that the developer doesn’t really need to be aware of it. That’s one of its strengths because you can put applications together really quickly. But that also means that it’s very easy for bad habits to creep in. Take database design, for example. A Magic developer isn’t forced to be concerned about the table structures and such things that are underlying; one can just go in there and plunk things down. As a result, a lot of applications tend to have databases that aren’t at all normalized, which is OK when things are small with very few users. But as things grow and the database gets bigger and there are more concurrent users, problems can arise. That’s one example of when I might get called.

ML: What other types of issues do your clients have that you help with?

SB: A client might call up needing new reports or a change in functionality. One of the reasons I like eDeveloper so much is because it’s so much easier and faster to do not only new development, but also this kind of ongoing maintenance. One of the reasons to develop a custom application is so that one can constantly tweak it as one goes along, adding new features and functionality. With eDeveloper, that can happen a lot more quickly, which translates into lower cost (even when the customer is hiring someone like me to do it) than it can in something like Visual Basic. For example, my biggest customer in Massachusetts manufactures and distributes products for the optical industry. For lots of reasons, their software needs to evolve, practically constantly, and I make that happen. I develop a relationship with companies like that such that I’m really just an extension of their staff—almost an employee.

ML: There are some people who, like you, got started with Magic in the early days but then didn’t do much more with it. Why is that?

SB: First, Magic is a small company and suffers from a lack of brand awareness. Not enough people know Magic is out there, but it survives because of those of us who do know it are such zealous adopters that we just can’t see ourselves going anywhere else. More than that however, it often comes down to a political issue in favor of Microsoft. Whoever ever got fired for recommending Microsoft?

ML: Have you been able to observe companies like that?

SB: I knew one company that had developed its entire business system in eDeveloper and had run that way for 12 years, but then dropped it in favor of one of the major ERP vendors. They ended up shooting themselves in the foot. But once those decisions are made, people tend never to go back and revisit them or ask themselves if it turned out to be a good idea. They abandoned a significant investment in one system for another that ended up costing them many times more. But even though Magic has been around almost since the inception of the IBM PC and almost as long as Microsoft, people still ask, “Who’s Magic? Are they going to be around next year? Can we afford to take a chance with them, or should we go with Microsoft?” It’s a shame when a company turns its back on a significant legacy investment that was costing them much less money to maintain and, as a result, giving them a much better return on their investment.

ML: How can Magic go about showing those people what their prior investment in Magic could do for them now?

SB: I see a real opportunity now to speak to people who care about total cost of ownership. There are still people in this world who are willing to look at alternatives and to consider something different from the mainstream. Magic is doing a good job right now by releasing a product like eDeveloper Discovery, and by continuing to add new functionality.

ML: What advice do you have for Magic’s customers—old and new?

SB: Take a look at what Magic has done to improve the product over the years, such as addressing today’s increasing need to consume and serve web services, build and work with composite applications, and integrate with legacy applications and databases. If developers see how fast they can get the job done with eDeveloper and management sees how favorable the TCO is, they should agree that Magic is the answer.

A Little Magic History

2008-03-09T16:02:00.001-07:00

I am constantly being asked about Magic's history, about the story of how the amazing technology that we know today evolved. Well, I can only tell you what I know.

Magic Software was founded in 1983 by Mashov Computers. Magic marketed application development tools and application deployment technology in the boom years of the personal computer craze (a boom that one could argue has not yet subsided). The programmers at Magic decided that if the computer was going to be perosnal and easy enough for everyone to use, that writing software was going to have to be a whole lot easier. While there had been some initial experimental attempts out of universities to create RAD -- rapid application development tools. None of them were all that useful because they tended to either be too complex or too restrictive and limited. So the developers at Magic set out to find a paradigm that would deliver full functionality and significantly reduce complexity.

SO there first and easiest decision was what not to do. They decided not to write a new computer programming "language." In fact they avoided traditional computer programming concepts and instead introduced a "table-driven" RAD tool. Today we know about concepts like pseudo-code, but they were really doing a lot of things we talk about in IT today: pseudo-code, services, mashups, etc. before anyone knew what to call them and really before they could be done as elegantly as Magic can do them today. SO they adopted an approach that required no compiling or linking. Because the pre-compiled sturctures could be employed and tested iteratively, the users of this new tool were able to prototype very quickly and start seeing results in minutes rather than weeks or months.

Te rest as they say is history, but let's remind ourselves of what that history includes: five years of victories at the Droege International development competiton, including the final year in which Magic's customers swept every prize at the contest, forcing the organizers to give up. Why continue holding programming competitions if the results are a given, Magic is the best and fastest tool. Ah, if only the market dynamics today were that simple.

Magic has had to try to preserve it ssimple table driven concept despite massive torrents of change in the underlying architecture of the computer. Not only has there been a major shift from text-based DOS environments to newer and arguably improved GUI operating systems, I don't know why I bother to use the plural, we all know I'm talking about Windows. But there was also a major shift from standalone PCs, to networked PCs on a LAN to PCs connected over the Internet -- the "cloud" as we sometimes like to call it. Magic also got a little ambitious too. The world of DOS and Windows in the 1990s was still not where most of the Fortune 2000 companies transacted their IT business. So Magic decided to expand the concept to include VMS, Unix, OS/400 and eventually Linux. The original dos version used Btrieve, these other environments used other databases and ISAM file systems. So the Magic development tool had to be given new "gateways" to deal with these new databases. Magic was able to sell these gateways as seperate products to their customers. Of course that transition to these other environments also meant a difference in architecture for the applications. The original desktop application approach was not a broad enough paradigm for these new distributed architecturess, so Magic's tool added client-server and Internet deployment methodologies. Known today as eDeveloper V10, Magic's development tools can deliver applications over the Internet in a browser-client mode or an HTML merge mode that is similar to PHP in the way it tags the HTML and merges in the results of its processing.

I'll probably have a lot more to say about this topic in the future, but I'd better get back to the topic of migration before anyone complains that I forgot to deliver my promised final chapter on moving your application to eDeveloper V10.

Converting to eDeveloper V10 (the Migration Story continues)

2008-03-08T04:59:00.000-08:00

OK, you're probably thinking: I was a convert to the Magic way of developing a long time ago: why do I need to convert? But I'm talking about a more routine kind of conversion here, the conversion utility that automates the move from eDeveloper v9.4 to eDeveloper V10.
Needless to say, (oh don't worry, I know I say needless things all the time anyway), the Conversion Utility feature does not exist in the Discovery version. The discovery version is designed for beginners and beginners only. If you already have a big application, you're not a beginner.

Getting to Know the Conversion Utility

If you've gotten very far into this, you probably already know that eDeveloper V10 provides an Application Conversion utility for converting your eDeveloper V9 application into an eDeveloper V10 project. Please remember that this utility is designed only for full applications written in eDeveloper V9.4sp7 and onwards.So, if you have to do something to get your application to eDeveloper v9.4 sp7 (or later) first, then do that before attempting the conversion utility. Be warned.
As the documentation ably illustrates, you can launch the Application Conversion Utility from the Windows Start menu > (All) Programs > eDeveloper V10.1 > Migration > V9 Migration UI.
After you launch the application conversion utility, aka V9 Migration UI, you will see its Welcome screen. When you click the Next button, the Version 9.4 Applications Screen opens, and this is where the fun begins (OK, not really fun but I am trying to make this different from the documentation in tone and style, is it working?).

Version 9.4 Applications Screen

So you may be wondering, why do I have to add everything one by one? Well, the answer is simply that you may not feel the need to convert all your applications and components, so just choose the ones you truly want ti the new world of eDeveloper V10. (After all, why convert that cool BetaMax Catalog application? So when you convert an application, each application and its component must be added to the Version 9.4 Applications screen by clicking the Add button. If your application has references to a component that has already been converted, you should still add that component to the list at this point. That's right, do it again, you are telling the convert utility to make that component available to this application in the new world of eDeveloper V10. So just do it.
Each time you click the Add button of course, the Conversion Details screen opens and you have some disambiguation to do.

So This is How You Use the Conversion Details Screen

In addition to the how, I'll try to answer the why, without simply saying "because that's the way it is." Basically, the reason for the conversion details screen is for you to communicate your intent. Do you want to convert all of the application or just part of it? Do you want to convert a new component, or has it already been converted and you just want to reference it? These are the kinds of questions you are answering in this screen. So you simply select whether you are converting an application, part of an application, a component, or keeping the reference for a previously-converted component.
For each export file there are four possibilities (the order entered is not important):
Convert an application - The utility converts the entire application to V10 (but not its components, you are adding them separately, remember?).
Convert part of an application – Now it gets a little particular here, because this option cannot be combined with other conversion types in the same process. That doesn'tmean the very next add operation cannot use one of the other selections, it just means that in a single add operation, you are either choosing part of an application, or some combination of the other three options: convert an application, convert a component or keep a component reference. So, all the other options can be added one after another and all of them will be converted in the same conversion run or process. That is why, this option can only be selected if you have not yet selected one of the other options since starting this session of the utility.
You can continue with additional V9 export files using the Add button.

Convert a component - The utility converts the application to V10, and finds all of the references to the MCF or MFF in all of the Component repositories in the conversion list (the first screen). Then, the utility changes their references to the newly created ECF.
Keep reference for previously converted component - The utility points to the references of this component to the previously converted cabinet file. By doing this, we do not have to convert the same application twice. This is useful if we have a component with models, which is used in a number of different applications.
Depending on which option you select, you then fill in the application details and/or project details.
When you convert an application and its components, the utility will take the name of the component (entered in the Component File Name field) and change any reference to that file name in the Composite Resource Repository with the V10 cabinet file (in the V10 Project Name field).
The Cabinet file location field governs where the conversion process creates the cabinet file.

When you click the Next button, the General Settings screen opens.

Salute the General Settings Screen

The General Settings screen has the following settings:
V9.4 Magic.ini File – The Magic.ini file used in the V9.4 application.
Log file directory – A path for the log file directory.
Log Level – This setting has the following options:
• Full – Displays the full log.
• Partial – Displays errors and changes of behavior only.
Convert empty eDeveloper handlers – This property governs whether the Record Prefix, Record Suffix, Task Prefix, and Task Suffix will be converted if they are empty. In previous versions, these built-in handlers were created automatically even if they were empty. These empty handlers are irrelevant in V10. If you select this check box, the empty handlers will be included in the converted application. If this check box is not selected, the empty handlers will be removed.
"SpecialModalToolWindow" – In previous versions, the caption of Modal windows was narrow while in V10 it is a full sized caption. Select this check box if you want the Modal window height to be increased in order to fit the contents.

But as we shall see next, you can also go to directly to the conversion executable file.

Taking Command with the Command Line Conversion

eDeveloper V10 does not support the eDeveloper V9 export file structure, however it does provide a command line conversion utility called v9converter.exe that converts eDeveloper V9.4sp7 export files to a valid V10 application.
The v9converter.exe file is located in the eDeveloper V10 installation directory.
When the export file is executed with no parameters or when you enter /?,the Conversion utility help text will appear on the screen.
When you run the utility, the conversion results are displayed on the screen.
If the conversion process fails, you should verify that the command line syntax is valid and that the application is in a valid version 9 export file format. The utility will create the .edp file in the specified project directory and the project source files in the Source subdirectory.
The conversion log file will be created according to the -LOG parameter. If this parameter is not set, the log file will be created by its default name.

So remember, if you need to migrate only a partial application, you need to use the Command Line Conversion utility.

In the final entry on the migration process to eDeveloper V10, we will take a look at what the conversion utility parameters do, try to explain how application behaviors can be changed in the conversion process, and finally, recap some of the troubleshooting issues related to your conversion. Let's hope this whole approach demystifies a lot of this for those of you who have been wondering, what is really involved? As you can see, it takes about as long to explain it all in detail as it does to perform the actual migration. So much for the blah, blah, blah.

Crossing the Border to eDeveloper V10

2008-02-12T14:27:00.000-08:00

Part One: Preparing Your Application

I don't know why exactly, but somebody coined the term "migration" to describe the steps involved in bringing an existing application from an older version of its development/deployment environment to a newer version. When I think of "migration" I picture a flock of birds flying south for the winter or a long line of cars crossing the border at Tijuana. Fortunately, migrating an eDeveloper v9 application to eDeveloper V10 is considerably less exhausting than either of those images might imply. Keep in mind, that eDeveloper applications cannot be converted to eDeveloper Discovery, since the purpose of Discovery is to introduce new developers to the Magic paradigm. Migration is therefore available only to eDeveloper Express and eDeveloper Enterprise.

eDeveloper V10 offers an entirely new approach to creating, storing and handling your eDeveloper application development projects. One of the things that you will notice is that eDeveloper V10 does not support the previous version's export file structure. But not to worry, a conversion utility is provided.

So crossing the border to eDeveloper V10 involves three easy steps: prepare your application for export, export the application, and run the conversion utility. It's just that simple, but let's look into each step a little more deeply and then discuss the three utilities available once your application has been migrated.

Preparing Your Application for Export

Prior to exporting your application, you should modify your application by replacing any unsupported features that you may have used with new approaches. In this fashion, you will ensure that no program information gets lost during the conversion process.

Unsupported Features
A number of older features have been removed: DVAL3, ESTR, FLOW3, Pref, ISTR, IVAL, LSTR, WebRef, EVAL, RVAL, RSTR, LVAL, STR3, TSTR3, TVAL3, VAL3, and the Euro functions, EuroCnv, EuroDel, EuroGet, EuroSet, EuroUdp. All of these were deemed unneeded or superfluous for one reason or another. So make sure to remove them from your application if you happened to use them in the past. Chances are you did not use these functions anyway, but you should check. And remember, while you do not have to do anything to prepare for features that have been renamed, about ten functions have new names in eDeveloper V10. So the conversion utility will change these automatically, such as changing ASC to ASCIIVAL, etc.

Changing Memo Attributes
You also need to know that any variable with a Memo attribute in your v9 application is going to be changed automatically to an Alpha attribute. Database fields that had Memo attributes will be converted to Alpha attributes with Memo storage. And of course, the VarAttr function will no longer return 'M' for Memo as this is no longer an eDeveloper attribute. But once again, don't worry, the conversion process will not automatically change expressions with the VarAttr function. Nevertheless, you should probably search for the string VarAttr to see where it is equated with 'M'. You will want to adjust your program in these rare situations, because VarAttr will no longer return the value 'M'.

A Fond Farewell to Web Online
"Web Online, we're glad we knew thee, but alas it is time to departeth." Yes, Web Online is that old and it is time to abandon this approach if, tsk, tsk, you hadn't already done so. To be clear: Web Online is not supported in eDeveloper V10. Older forms with the Web Online Response interface type are not supported in eDeveloper V10. The conversion utility simply removes these types of forms from your application. So any existing Form Output operation pointing to these forms will not point to a form in the converted project. Magic recommends that you remove any form of this type before exporting your application.

And HTML Forms Must Get the Boot As Well
As a result of improvements and greater flexibility in the new Merge capabilities, and to prepare the way for even greater enhancements in the future, eDeveloper V10 will not support forms with the HTML interface type. Once again, the conversion utility simply removes these types of forms from your application, and any Form Output operation pointing to these forms will not point to a form in the converted project. So Magic recommends that you remove any form of this type before exporting your application.

So this change implies a number of changes from the way things used to work: 1) The HTML property has been removed from the Style section of the property sheet of variables, columns and models. 2) The HTML class has been removed from the Model repository. 3) The Internet Development File Root property has been removed from the Project properties. 4)The Internet APG is not supported. 5) The HTML Merge Interface Type is now named Merge. The Conversion utility will convert the HTML Merge values to Merge.

As you get deeper into eDeveloper V10, you will see this as an enhancement with a more flexible and useful approach to Merge.

Goodbye to the Old Browse Function
The browse function was rather single purpose and it is simply more flexible to replace this with an Invoke OS Command operation that gives you the flexibility to do more than just Browse. So, as a result, the Browse operation is not supported in eDeveloper V10. Magic recommends that you remove any Browse operation before exporting your application. Keep in mind, however, that the Conversion utility will replace the operation with an Invoke OS Command operation.

Other Unsupported and Removed Properties that Will Not Convert

Environment properties
The Multi User Access setting has been removed from the Environment dialog box.

Euro-Related properties
A number of older Euro Support features have been removed because they are simply not needed any longer. First of all, the European Currency Conversion File environment setting was removed from the External tab of the Environment dialog box. The EuroFile environment setting was also removed from the MAGIC_ENV section of the Magic.ini file. Needless to say, the Base Currency and European Currency Conversion File application properties were removed too. And as mentioned above, several Euro functions are no longer supported.

Java Browser Client
The browser client of old was a Java applet. No more. To reflect changes in the most commonly supported client applet technologies available for Internet Explorer, the Java option has been removed from the Browser client technology setting in the Server tab of the Environment dialog box.

Java Component Generator (JCG)
We used to have a separate generator called the Java Component Generator. This concept has been significantly expanded upon to allow composite objects of all types to be generated, including your own ability to write composite generators. All of these are now found in the new and exciting Composite Resource Repository in eDeveloper V10.

Out with the Old XML Component Generator (XCG)
Significant improvements in XML handling have been added in eDeveloper V10. You can learn about these in greater detail in one of the recent XML Webinars in the Magic Software webinar archives. Anyway, the old XML Component Generator has been removed to make way for these enhancements.

Minor Change to Application Properties
The rather obscure "Internet Development File Root" property was removed from the Application Properties dialog box.

DBMS
Three columns have been removed from the DBMS repository:

2 Phase

Excl. Trans.

In corresponding fashion, some Magic.ini settings were removed from the MAGIC_DBMS section: OnePhaseCommit, TwoPhaseCommit, NotTransLockExcl and TransLockExcl.

Databases
Several columns and properties have also been removed from the Database repository. The Magic Server column was removed from the Database repository. The Common Data Dictionary property was removed from the Options tab of the Database Properties dialog box. And the XA Transactions property was removed from the SQL tab of the Database Properties dialog box.

Internet APG is out the door
Out the door forever, I should add. The Internet APG for a table or task is no longer supported. The Internet tab was removed from the APG dialog box.

Export Document
The Export Document option was removed from the Operation list in the Export/Import dialog box.

Studio Rights
Finally, (well, with blogs, nothing is ever final) the Studio rights have been removed.

Colors and Fonts
This next consideration is optional. Some of you may prefer the new eDeveloper V10 color and font settings. Nevertheless, if you want to maintain your application's colors and fonts, you should set the Application color and font definition files and the Internal color and font definition files of the converted project to be directed to the color and font definition files of version 9. This is a onetime setting change for each application and project.

Security File
You will likely want to use your security file (such as usr_std.eng) from the previous version, but you do not have to. If you decide to convert your existing security file, run the usrupd.exe utility from the command line. The syntax is:

usrupd *input* *output*

*input* is the name of your current file name and *output* is the name that you want given to the file that is created by the usrupd.exe utility. And you should keep in mind, very importantly that in eDeveloper V10 you can only assign runtime rights.

Terminology has changed too
I won't get into terminology changes here because I don't think they are relevant to the migration itself. But you should definitely familiarize yourself with the new terminology in eDeveloper V10 as compared to the prior version.

Next time:

In my next blog entry, we'll discuss the export and conversion steps. So stay tuned.

Magic eDeveloper V10 and ROI for Start-Up Businesses

2008-01-18T16:11:00.000-08:00

The economy has been showing signs of weakness. Despite this, thousands of entrepreneurs will be launching new businesses, even in the midst of a new economy. How does that affect software development? Building the software systems for these new businesses is a critical process and one that must complete in the least possible amount of time. During slow economic times Return on Investment is on the mind of every entrepreneur who has to sign off on a development budget to get the new business systems in place that will deliver their unique competitive advantage. So in today’s business climate, the emphasis is on rapid return on investment. The break-even point needs to be achieved at the earliest possible moment. Every cost has to be analyzed against the expected returns to arrive at estimated break even dates. So here’s my claim: “You can achieve ROI in your application development process faster and with greater assurance when using eDeveloper V10.”

Application development tends to occur in phases. For our purposes, let’s consider these four phases: Design, Build, Test and Deploy. In the harried environment of a new startup business, you need to have all four of these occurring almost simultaneously, but traditional computer programming tools do not allow this. All four of these phases require an investment of time, but if you can execute some of the phases in parallel, then you can get to the final destination faster. So testing isn’t something that happens at the end of a software process, it is an iterative process that occurs throughout the project. For this reason, it may be more useful to think of Design, Build, Test, Maintain not as phases, but rather as layers of the development task. The design layer tends to be front-loaded in the project, but some design occurs while maintaining the program. The test layer tends to be back-loaded towards the end of a project, but using sound iterative design principles, testing definitely occurs throughout the life of the project.Time is money is perhaps a cliché but critical when discussing the ROI of business software development projects for new businesses.

Application Development ROI calculations must put the emphasis on the investment that goes into dollars paid to the developers on the project; i.e. how many developers will it take and for how long? The sooner the project comes to a successful end, the faster the ROI for the project, and the sooner the new business can deploy their new systems and reap the benefits.

The time saved - hence the ROI - using Magic eDeveloper V10 is significant: typically from 4 to 6 times faster than that of other development technologies.
The table below is based on extensive market research and compares each of the four phases (layers) of the application development lifecycle for 3GLs (Third Generation Languages), 4GLs (Fourth Generation Languages) and Magic eDeveloper. If X, Y, Z, and W represent the time spent on an average 3GL application for each of the application development phases, research shows that generally 4GLs cut the time in half. With Magic eDeveloper even better time- savings are achieved. The productivity gains shown below are conservative calculations by Magic Software based on interviews with eDeveloper programmers, many of whom are quoted later.

In order to achieve rapid ROI, each phase of the lifecycle must not only be completed quickly, but must also have the highest reliability to ensure the fastest payback for the investment being made.
In going through the analysis of each of the application development lifecycle phases in future blog entries, I will detail additional aspects of Magic eDeveloper that result in further ROI increases.

Magic eDeveloper’s progressive development paradigm allows prototype applications to be quickly and easily created. The eDeveloper paradigm is often used to convince venture capitalists and other investors that achievement of a new start-up businesses goals for new business systems is in fact achievable. Without eDeveloper, some businesses might not even “get off the ground.” In addition, the ability to support applications over time despite changing business models, platforms, and standards is inherent in the Magic eDeveloper development technology.

Rapid ROI remains a key critical measure for every new business and is often the difference between success and failure. I’ll comment more on the savings possible during each phase of the application development cycle in later posts.

Top Ten Ways To Gain Approval of Your eDeveloper Upgrade

2008-01-17T16:11:00.000-08:00

Getting the boss's approval to upgrade important software can be a challenge, particularly when budgets are tight. Here are a few tips on how to get approval to upgrade eDeveloper V10:

PREPARE. Go in armed with all the necessary materials to make a good case for your upgrade. Download the “Ten Reasons” brochure and visit the series of blog entries on reasons to upgrade in Glenn Johnson’s eDeveloper V10 blog.

LEARN. Attend the Magic University course “Migration to eDeveloper V10” so that you can speak with authority on the capabilities of eDeveloper V10. Download the FREE EVALUATION SOFTWARE and consult the "What's New in eDeveloper V10" and other documentation.

RELATE. Show how specific problems or issues you've recently encountered can be overcome by one of the improvements in eDeveloper V10. Ask for a Magic representative to setup a live web presentation on your upgrade to eDeveloper V10. Invite your opeers and your boss to participate in this information gathering session.

SHARE. Point others in your organization towards the new learning resources in eDeveloper V10: the “Mastering eDeveloper” book and the 22 online demonstrations.

SAVE. Point out the ROI benefits of migrating to eDeveloper now, before you release a new version of your software based on your current version. Cost savings, productivity enhancements, application improvements, user interface benefits, and much more, are all available immediately, but only if you make the leap to eDeveloper V10. A delayed start to active development using eDeveloper V10 equates to a very real loss of benefits to your company.

TEAM. Review the benefits of eDeveloper V10 with other members of your development team. Gain an understanding of how the improvements can enhance efforts across your development team.

CONSULT. Magic Professional Services can help to provide you with a migration readiness assessment. This formal consulting process will help you to plan for all aspects of your migration to eDeveloper V10.

LAUNCH. Ask for a commitment on a specific launch date for your team’s use of eDeveloper. Come in armed with a launch plan.

MEET. Set a specific meeting in which you can present your upgrade request to senior management. Make it clear to everyone that this is an important and needed decision.

DECIDE. Give a deadline to make a decision. Present the information and ask for an answer within a specified time frame. Reiterate that procrastination has real expenses and costs associated with it as well as lost business opportunities.

Developing RFID Applications with eDeveloper V10

2008-01-04T17:04:00.000-08:00

Last month, I attended the Active RFID Summit held in Dallas, Texas. In addition to enjoying a chance to sample some excellent Tex-Mex dishes, I really appreciated the chance to compare notes with colleagues on the state of the art application of RFID, especially active RFID. Regardless of whether you are developing proprietary applications, vertical applications for a specific industry or horizontal applications that serve cross-industry needs, RFID is putting a strain on IT resources. Active RFID represents a major paradigm shift in data acquisition and generation creating an onslaught of data that current applications are generally not prepared to handle.

Stephen Moody, an RFID Program Coordinator for the Combat Feeding Program of the US Army's Natick Soldier Research Development, presented a fascinating case study entitled: "DoD Active RFID Applications for Supply Chain Security and Shelf Life Management." It is easy to underestimate RFID as something akin to a glorified barcode or a "traveling database". But many active RFID tags are far more sophisticated in that they incorporate environmental sensors. The US Army sends tons of rations to the troops in Iraq and elsewhere. These shipments are made in ships holding thousands of standardized shipping containers. How can the US Army be sure the shipments have not been tampered with or exposed to unacceptable environmental conditions? The answer is active RFID tags with sophisticated sensors for a number of environmental events: temperature, radiation, light, chemical agents, biological agents, shock, door sensors, etc. If somebody is doing something to a shipment of food, or if it just gets too hot for too long, the US Army knows when it happened and where it happened. This is simply one of scores of applications for active RFID in an organization like the US Army. But what does one do with all that data? According to Moody, "the greatest barrier to the successful implementation and adoption of RFID is integration to legacy systems."

One of the other challenges for RFID is the current lack of standards. In some ways this is unavoidable: RFID is not a specific product, technology or protocol. RFID is a family of technologies that incorporate radio frequency and are used to identify "stuff." As Sue Hutchinson, the Director of Industry Adoption for EPCglobal US put it, RFID provides the answer to the question "where's my stuff?" But the type of RFID may involve passive RFID, where the tag has no power source and is a write-once technology, to active RFID, including ultra wide-band (UWB), all the way to GPS and beyond. With such a diversity of technologies, standards become even more important. Lacking these standards, however, flexible development and integration tools become even more important.

Consider the food safety example above, somewhere in an ERP system the information resides for the supplier name, items ordered, supply date, carrier and so forth. Does this information get integrated to the data on the RFID tag? What happens if food from one supplier is more prone to spoilage or to lose palatability under prolonged high temperatures? How can the US Army, or any organization for that matter, take full advantage of RFID applications if key information sits locked in a silo such as an ERP or supply chain system?

Information integration is the key. But how does one best handle RFID integration with an ERP or other existing application? To answer that, we first need to consider the RFID system being used. RFID systems involve tags (some with built in sensors), programmers, readers, networks and so on. But most do not include middleware. And the hooks provided are inconsistent. Text files, XML, .NET objects, java objects and Web Services are provided inconsistently. For an organization to be prepared to integrate the data from a reader, they can benefit from a middleware solution like iBOLT that provides the ability to consume any of these data types and orchestrate them within an overall business process. Or they can create interfaces from directly within an eDeveloper application. Even when dedicated applications are written to take advantage of RFID data, middleware and business process management software is still needed to facilitate integration to legacy systems. Ideally, these middleware systems are service-oriented including event driven capabilities, discoverable web services and more.

Unfortunately, too many RFID early adopters are resorting to hefty J2EE or.Net based programming projects rather than utilizing a development tool like eDeveloper V10 or a simplified visually-oriented business process design tools like iBOLT. As the world begins to find more and more uses for RFID, it will be useful for serious organizations to incorporate eDeveloper and iBOLT for integration to RFID data, whether it comes in raw text or XML format or is served up by a Web Service or programming object like .NET or XML.

With RFID, the emergence of integration file standards is far from certain. The Auto ID Center has proposed an XML format known as PML as a standard. You can read about it on the XML CoverPages hosted by OASIS. But the adoption of the standard is far from ubiquitous, especially in the Active RFID world which tends to look at organizations like EPCglobal with at least some degree of suspicion.

The good news for eDeveloper programmers is that since PML is just a flavor of XML, you can access RFID data with standard eDeveloper XML tools. To see what you’re avoiding, take a look at the PM example below. For more information on RFID and iBOLT, you can access Magic Software’s RFID related webinars.

Using PML in eDeveloper V10
eDeveloper V10 includes a new capability called XML Integration. This approach makes PML’s use within eDeveloper much easier. In fact, you can now develop applications using eDeveloper with no database at all and simply use XML files, including PML for RFID and other Auto ID related applications.

When using a PML data source containing RFID data, you can create eDeveloper tasks (batch and online) that use the PML files as their view (main files and linked files). You can define an PML data source in the Data repository (remember PML is XML) and define a task to manipulate and handle the PML. You can check that the XML task is compatible with the XML schema by using the XMLValidate and XMLValidationError functions. Namespaces are automatically handled by eDeveloper.

There are two XML development methodologies to choose from. You can develop applications using XML in the data repository or you can develop using XML with BLOBs. If you use both methods, then the BLOB takes precedence.

With eDeveloper V10, a task that uses XML (such as PML) will first open the entire XML file (if it is not already open) and then populate the tables. It then executes the defined task, whether that be query, insert, update or delete. Finally, when closing the task, if the data has changed, then eDeveloper V10 writes the XML BLOB or file back over the original XML source.

eDeveloper V10's XML Integration feature provides two functions that allow you to verify that the XML is compatible with the XML schema.

The functions are XMLValidate, which validates an XML document against its schema; and XMLValidationError, a function that returns the errors of the last XMLValidate. This will help you to determine whether your PML file is valid based on the PML schema, which of course is found in the .xsd file.

With eDeveloper V10, you can use the Get Definition function to discover the properties of a PML file that contains RFID data and map them to an eDeveloper table. Like all XML files, PML files are described by .xsd metadata that contains the XML schema definition. During a Get Definition, if an element’s/attribute’s type is defined using a SimpleType or as a reference to a Global element, it will be converted to the appropriate Primitive xsd data type from which it is derived.

Primitive xsd data types are mapped to corresponding eDeveloper attributes. Once this occurs, the field attributes can be changed without restriction. A default picture (most of the time you can think of this as length) will be assigned (as specified in the table). When the type is based on a SimpleType, which defines length, the picture will be updated with the length specified for the SimpleType.

What About Other RFID Data Integration Types

To be sure, RFID vendors are not uniform or universal in their support of RFID data via PML or XML. Fortunately, eDeveloper has built in functions for the other common methodologies as well. Some vendors supply RFID Web Services, which means you can use the eDeveloper V10 Web Services wizard. That’s even easier than dealing directly with PML or other forms of XML.

Occasionally, programming objects such as java objects or COM objects are provided, in which case eDeveloper can call and pass information to these objects. Keep in mind that Active RFID enables two-way data communication and write-many read-many (WMRM) storage with an RFID tag, whereas, generally speaking passive RFID is a write-once read many (WORM) technology. That means your eDeveloper applications need Active RFID if they are going to do any of the more sophisticated RFID applications.

Ways to Apply RFID Technology in eDeveloper Applications
Going back to Sue Hutchinson’s comment, RFID helps to answer the question: “where’s my stuff?” One way to determine this is to sense the immediate presence of an FID tag next to a reader. This approach works well, with say, tagged parts that are passing along an assembly line. The parts are always within range of the reader. Another example of good stationary reader approaches might be warehouse doors. Some work has even been done to create “smart shelves” that sense the RFID tag of products as they are pulled on or off the shelf. For these close proximity applications, passive RFID may be satisfactory.
But the real world does not always have these convenient thresholds.

One of the technologies developing around RFID are Real-Time Locating Systems (RLTS). These systems measure the wave properties of an RFID signal to determine the location of an RFID tag. The readers are generally placed in a grid and then tuned to a room or outdoor location. Since waves travel inconsistently through and around walls, etc., bandwidth is a consideration with RLTS. In cramped spaces, UWB is often preferred and it may offer energy saving advantages as well. Battery life in an RFID tag is another important consideration. Beacons that emit constant signals use more energy and have shorter battery life than systems that simply “chirp” at an established interval.

Software algorithms that calculate the location of a tag by comparing signal strengths on a grid of sensors are quite sophisticated. But they aren’t always accurate. Practical field applications show that errant readings are fairly common. When possible, a location should be calculated based on the average of several readings and not just a single reading. This approach leads to a great deal of accuracy.

RLTS can be used in applications such as worker safety systems. Companies like BP use active RFID in their employee badges so that if disaster strikes at a refinery or other hazardous work location, systems can be used to pinpoint the locations of workers and visitors. Needless to say, the RFID readers in these systems have to be “hardened” to withstand violent environmental conditions such as fire and explosion.

Another common use of RLTS is in asset management software systems. These often take on specialized use in various industries. Nurses need to know which room an IV cart or other mobile medical equipment was left in. Newspapers need to know where the paper stock rolls are in their automated factory. Truckyard operators need to know which spot particular trailers are located in, etc.

Glorified barcodes? Perhaps. But when was the last time a barcode could tell you whether the product it tagged has been kept at safe temperatures or automatically report its location? Sure we know we scanned it into inventory six months ago, but don’t ask us to actually find it in the store or warehouse.

A Little Thanksgiving Housekeeping for eDeveloper v9.4

2007-11-26T15:47:00.000-08:00

I know I usually write about the latest version of eDeveloper: eDeveloper V10, but last week's service pack release gives me a chance to mention the latest service pack release for our older development tool version: eDeveloper v9.4.

On Thanksgiving Day (US), November 22, 2007 Magic Software Enterprises released SP8. As always, you can install eDeveloper 9.4 Service Pack 8 using the installation wizard’s Upgrade option, the wizard automatically replaces the files that were modified since your previously-installed version. By the way, if you haven't looked at the samples for v9.4, be sure to look at the samples at:

ftp://ftp.magicsoftware.com/v9product/94Samples/

Hopefully, that gives you something to be thankful for. The Service Pack only includes fixed problems, commonly known as bug fixes, which are shown here in alphabeical order, by name, and with a reference to the relevant QCR:

1. ActiveX – CDO Library (QCR # 249783) eDeveloper failed to show the methods or properties of the Microsoft CDO type library.
2. ActiveX – MgItemSequential (QCR # 755479) The first item in a collection was not retrieved when using the MgItemSequential method of a COM object.
3. ActiveX – Return Value (QCR # 529387) The values were not properly returned when using an ActiveX control defined as "FileSystemObject" of type library "Microsoft Scripting Runtime (Ver 1.0)".
4. Application List – INIPut() (QCR # 916180) A change to the application name via the Settings menu was not saved when an INIPut() function was previously used to add entries to the [MAGIC_SYSTEMS] section of the magic.ini file.
5. AS400 – Get Definition (QCR # 931792) Performing Get Definition on a table with indexes from a database whose name was defined in small letters added the library name as a prefix to the table and indexes’ names.
6. Authorization – LDAP (QCR # 750937) Specifying the wrong password when using LDAP closed the login screen and showed the previous username as the connected user.
7. Authorization – LDAP (QCR # 751594) eDeveloper failed to use Active Directory user accounts that were defined with a comma character in their name.
8. Broker – Monitor (QCR # 769359) The Broker monitor showed a threads peak value greater than the threads maximum value.
9. Browser Client – .NET CLR 2 (QCR # 227844) Executing a Browser Client program on a machine without CLR 1.1 installed did not return the proper error message. *
10. Browser Client – Check Box Control (QCR # 914074) A Check Box control did not show the updated value in Browser Client display when a Verify statement was executed immediately after changing the value.
11. Browser Client – Context Unload (QCR # 976397) An error appeared in the mgerror log file after closing a page with a javascript function when the Context Unload Timeout environment setting was set to zero.
12. Browser Client – Contexts (QCR # 985850) A running context could close another context from another IE session when both contexts ran the same program.
13. Browser Client – Copy and Paste (QCR # 777060) The Copy and Paste options did not work in a Browser Client program that was in Query mode.
14. Browser Client – Cross-site Scripting (QCR # 988306) The eDeveloper requester (CGI /ISPI) had Cross-site scripting (XSS) flaws when using DefHtml Parameter settings in the Mgreq.ini file and writing direct scripts in front of the Arguments parameter in the URL.
15. Browser Client – Field Range (QCR # 287294) Value range on a Date field failed to work in Browser Client when the range contained spaces.
16. Browser Client – Incremental Update (QCR # 900738) Incremental updates did not work correctly in a Browser Client task when a Link Write was used.
17. Browser Client – Screen Refresh (QCR # 917684) The screen was not refreshed correctly when browsing memory tables in certain scenarios.
18. Browser Client – Signed MSI (QCR # 101633) The MSI file that installs the CAB files required for Browser Client execution was not signed, thus it could not be executed on sites using a strict security policy. *
19. Browser Client – Transaction Cache (QCR # 785229) The eDeveloper engine crashed in some specific scenarios depending on the transaction cache when running a Browser Client program.
20. Builders – Components (QCR # 939733) An error was returned when adding new tables to an existing component that already had some tables defined.
21. Builders – WSDL (QCR # 934669) The WSDL builder returned an error when tying to get the schemas from an XSD file with a URL path.
22. Builders – XML (QCR # 987568) The data was not read from the XML file through the "Read XML" program created in the XML component.
23. Cache – Changing Modes (QCR # 966543) eDeveloper switched to Create mode upon changing the mode to Modify on a screen mode program defined with no main table and the Cache Strategy set to "Position".
24. Cache Strategy – Memory Gateway (QCR # 254280) Scrolling using the PgDn and PgUp keys did not work properly when browsing a table whose Cache strategy was set to None and performing Sort by clicking on the table column's title.
25. Cache Strategy – Memory Gateway (QCR # 769691) Scrolling in a backward direction did not refresh the data properly when browsing a memory table whose Cache strategy was set to None and the column sort was used.
26. Call Remote – Performance (QCR # 248012) A performance problem occurred when using the "call remote" mechanism with a large user file. *
27. Checker – ExpCalc() (QCR # 771447) An error was shown when executing the Checker on an expression that had a nested ExpCalc function in it.
28. Checker – Missing Variable (QCR # 681399) The Checker failed to report on a missing variable that was defined in an expression of the "DB SQL Where" property.
29. Components – CallProg() (QCR # 929773) The CallProg() function executed in a component called a program from the host application instead of the program from the component application.
30. Components – Load Immediate (QCR # 915478) eDeveloper crashed when a model in the host application had a select program from a component that was defined with Load Immediate=No.
31. Components – Orphan Tasks (QCR # 991046) eDeveloper crashed upon executing a component program from a host application with orphan tasks during some scenarios.
32. Confirm Update – Nested Tasks (QCR # 929259) Updates made in a subtask were saved even when Confirm update was set to No by the end-user when exiting the subtask and immediately exiting the parent task.
33. Controls – Border Style (QCR # 974253) It was not possible to change the Border style property when selecting multiple controls and changing their style to 2D.
34. Controls – Combo Box (QCR # 937702) The wrong value was displayed in a combo box after creating a record when an expression was attached to both the Item List and Display List properties of the combo box.
35. Controls – Image (QCR # 740281) The tooltip was not displayed for Image controls when the screen resolution was changed to 1280*768.
36. Controls – Image Button (QCR # 985613) The 3D effect of an Image button in SP6c and above was different than previous versions.
37. Controls – Line (QCR # 756240) The cursor was not moved to an Edit control when there was a Line control under the Edit control and the area of the Line control was clicked on.
38. Controls – Slider (QCR # 602655) The Mouse Over/Out event did not work on Slider controls.
39. Controls – Slider (QCR # 656280) The Control Hit event handler for Slider controls was executed twice.
40. Controls – Tab (QCR # 992568) The screen flickered upon scrolling through the records when the form had a Tab control set with expressions on the tab’s Display list and Items list properties.
41. Controls – Table (QCR # 743617) It was not possible to drag and drop the table field's data when the table was wider than the MDI and the caret was positioned on the right side of the table.
42. Controls – Table (QCR # 777255) Records in a table were not correctly displayed when opening a table in create mode, inserting some records and then adding a new record in the middle of them.
43. DB2 – Decimal Value (QCR # 293057) eDeveloper did not display the decimal part of number values on a DB2 9.1 database.
44. DB2 – Expand Form (QCR # 781109) eDeveloper rounded the data when reading data from a DB2 table having a field with data type = DOUBLE.
45. DB2 – Order By Clause (QCR # 777372) The position key segments were also included in the Order By clause created for a linked table locating a non_unique index when using the DB2 and ODBC gateways.
46. Debugger – Flow Monitor (QCR # 728280) The CPU usage was sometimes increased to 100% when reaching a breakpoint.
47. Edit Control – Multi-Line (QCR # 774769) It was not possible to park on a multi-line Edit control by pressing the mouse when a 'click' event existed in the program and the Edit control had an expression on the Enable property.
48. Environment – INIPut() (QCR # 991880) Setting the value of RangePopTime and TempPopTime using the INIPut() function did not work when using it with Force write = False.
49. Events – Control Level (QCR # 915413) The control’s event handlers were not executed when modifying the field’s value, pressing Cancel, and selecting ‘No’ in the confirmation box.
50. Events – Page Header (QCR # 779133) The Page Header event was executed only once even when more than one output forms were outputted.
51. Execution – DEP (QCR # 240904) eDeveloper terminated abnormally during startup when DEP (Data Execution Prevention) was enabled for all programs. *
52. Exit Operation – Background Mode (QCR # 281614) An 'Exit' Operation command executing a batch file in background mode returned an error code (-1) as the return value.
53. Export – Document (QCR # 767712) The contents of the eDeveloper SQL Range was not written to the Export Document file when both the SQL Range and DB SQL Where Expressions were defined in the program.
54. Expression Editor – Repeat Shortcut (QCR # 288555) The repeat shortcut (@) was limited to a 3-digit expression number.
55. Flow Monitor – Variable Window (QCR # 288396) Variables that started and ended with the % (percentage) character were not displayed in the value column of the Variable window in the Flow Monitor.
56. Force Record Suffix – Add Record (QCR # 286131) A new record that was created in an online task defined with Cycle record main = No and Force record suffix = Yes, was not saved when skipping to the next record by pressing tab from the last field.
57. Form Editor – ActiveX (QCR # 764514) eDeveloper crashed when exiting a subtask with an ActiveX control on its form.
58. Forms – Tooltip (QCR # 768929) The tooltip was not displayed if it was defined as an expression that uses a variable from a Link operation when the main display form was other than the default form.
59. Functions – CtrlGoto() (QCR # 764538) eDeveloper did not respond after scrolling through the table using the scroll wheel of the mouse when CtrlGoto() was used in the Record Prefix.
60. Functions – CtxSize() (QCR # 778885) The CtxSize() function refreshed the last used context information when it was used.
61. Functions – CurRow() (QCR # 741409) The CurRow()function returned wrong results if the Resident Task property of the task was set to "Yes" and when the task range was changed so that there were no records in the range.
62. Functions – IOSize() (QCR # 997160) The IOSize()function returned negative values for files larger than 2 GB.
63. Functions – KbGet() (QCR # 772271) The KbGet() function returned a wrong value when used in the Record Main compatible logic unit.
64. Functions – VarSet() (QCR # 300356) eDeveloper crashed when a numeric expression was set to an alpha variable using the VarSet() function.
65. HTML Form – Hyperlink (QCR # 967502) An HTML form defined with Input=Yes and set with a Hyperlink that referred to an eDeveloper program, did not dynamically add the three hidden arguments, Application, Prgname, and Arguments, to the form tags that are generated at runtime when the called child task/program also output an HTML form.
66. Image – Resolution (QCR # 910920) An image was not displayed properly in some resolutions.
67. Import – Special Characters (QCR # 939169) eDeveloper could not import an export of a program that contained special characters in some of its properties.
68. Interface Builder – Web Services (QCR # 334866) When creating a Web Service using the Web Service Interface builder and clicking the Verify Structure button, an error was sometimes received.
69. LDAP – Binding (QCR # 998962) Using OU did not work when entered in the Connection String property.
70. Memo – Tab Display (QCR # 774357) Memo fields that contained the Tab character were not displayed properly when leaving the field.
71. Memory Leak – Link Write (QCR # 911077) A memory leak occurred after executing a batch program having a Link Write operation in background mode when the MaxConcurrentRequests were reached.
72. Merge – Performance (QCR # 775792) Performing a merge operation on a template that had rows and columns took a very long time when there were a lot of rows to merge.
73. MSSQL – Browser Client (QCR # 303363) Link Query defined in the main program was executed after every record execution in any task even when there was a fixed value in the Link Locate expression.
74. MSSQL – Error Handlers (QCR # 728381) eDeveloper crashed while browsing records on an MSSQL database when some rows were deleted from another session.
75. MSSQL – Hint (QCR # 910662) An error was obtained when ‘FORCE_INDEX’ was used as a hint on SQL Server 2005.
76. MSSQL – Locate (QCR # 757582) eDeveloper did not perform the incremental locate properly when typing fast.
77. MSSQL – Numeric Field (QCR # 248887) A numeric field stored as a signed integer with SQL type set to bit displayed as 1 in eDeveloper when the numeric field's picture was larger than 1 and included the N character. *
78. MSSQL – Sort (QCR # 998843) eDeveloper did not send a sort command to the RDBMS when the sort was done by the user on columns from the Main table and Link Joined table.
79. MSSQL – Stored Procedure (QCR # 784462) eDeveloper crashed when running a program that calls a generated stored procedure where a Locate is performed on a field that was moved.
80. MSSQL – View Refresh (QCR # 970880) eDeveloper crashed upon closing a DSQL task after performing a view refresh operation when the result database was MSSQL.
81. Multilingual – Trim (QCR # 912733) The MlsTrans() function returned a trimmed string when no matching translation string was found.
82. OLE – Instantiation (QCR # 782361) An OLE object was not instantiated correctly when it was part of a collection.
83. Operations – Block (QCR # 778724) The 'Block Else' condition was executed even though the 'Block If ' condition evaluated to True.
84. Oracle – Charset (QCR # 756467) The correct row was not retrieved when ranging a value using Picture on an Oracle table and using "NLS_CHARACTERSET=WE8MSWIN1252".
85. Pervasive – Deferred Transactions (QCR # 982443) eDeveloper returned an error when deleting records from a Deferred Transaction program that had a Link Inner Join operation.
86. Pervasive – Duplicate Index (QCR # 774018) eDeveloper did not show the "Duplicate Index" error message when creating records using "Link Create" in a batch program that did not use a Pervasive database transaction.
87. Pervasive – New Table (QCR # 15457) A Unique Identifier error appeared when creating a new table with a float (4) field on Pervasive 9.5 database.
88. Pervasive – ODBC (QCR # 926120) An error appeared when using the Pervasive ODBC Client Interface and executing a program with a certain index definition.
89. Pervasive – SQL Range (QCR # 913959) eDeveloper crashed when performing view refresh on a program with a Pervasive table that was once an SQL table and had an SQL range defined.
90. Print Preview – Expand Form (QCR # 780319) Table data was not displayed correctly in the Print Preview when the Expand Form option was used.
91. Print Preview – Images (QCR # 993173) The Image control on print preview had a different size and display colors compared with image controls in versions prior to SP5.
92. Printers – Number of Copies (QCR # 979100) The Copies property value defined in the default printer settings of the operating system was not shown in eDeveloper.
93. Printing – Multi- line Edit (QCR # 989830) The printed header lines of the second page and onwards were corrupted when printing a report that prints multi-line edit fields.
94. Printing – Tasks (QCR # 777828) eDeveloper sometimes crashed while printing the forms from two tasks into the same printer when headers and footers were defined.
95. Range – Cache (QCR # 994246) Records were not displayed properly when updating them from a batch task and displaying them according to range when not all the variables from the table were selected.
96. Record Suffix – Mouse Click (QCR # 770744) The Record Suffix was not executed when clicking on an Edit control in a child task in certain scenarios.
97. Records Display – No Index (QCR # 759564) Records were not displayed properly when selecting a table that does not have an index and selecting only some of the variables in the task.
98. Requester – HTTPVars (QCR # 996861) Error (-103) occurred when the HTTPVars parameter string in the Mgreq.ini file was too long.
99. Rights – Components (QCR # 765845) eDeveloper sometimes showed controls on a form defined in a component even if the user that was logged on did not have rights for them.
100. SQL – Range (QCR # 755614) An error was received when ranging on a virtual variable that was defined with Null allowed=Yes in certain scenarios.
101. Table – HitZOrder() (QCR # 996362) The HitZOrder() function returned a unique value for the controls in each row in a table instead of returning the same value for all the controls in the same column.
102. Table – Logical Names (QCR # 996418) A gateway error was returned when altering a table that was defined with a logical name in its name and had a foreign key.
103. Table – Width Recompute (QCR # 913114) The table width was recomputed every record after a window resize was done when the Table control had a placement and expression on its Width property.
104. Team Development – ACS (QCR # 292564) eDeveloper crashed on checking out a program when using ACS file for the same database as the MCF.
105. Team Development – Components (QCR # 932448) eDeveloper crashed when activating Team development for components in a specific scenario.
106. Text-based Forms – Horizontal Alignment (QCR # 931771) The Horizontal Alignment property of a variable pasted on a Text-based form could not be changed if the Text control of the variable was pasted near any of the variables on the form.
107. Tools – Export (QCR # 923487) eDeveloper crashed when trying to export an application that has a component using the Tools infrastructure in Background mode.
108. Tree Control – Drop (QCR # 941906) The Drop event did not work properly when performed on a Tree control.
109. Version Control – Folders (QCR # 765202) eDeveloper crashed after performing the version control sync operation on an application with folders.
110. Web Service – Call Operation (QCR # 773587) eDeveloper hanged when loading some WSDL files into a Call Web Service operation.
111. WSDL – Call Web Service (QCR # 996400) Some methods in a WSDL file could not be loaded using the Call Web Service operation.

Please feel free to contact us at anytime with suggestions for improvements to eDeveloper.

Happy Thanksgiving!

Unicode Makes Multiple Languages Easier In Your eDeveloper V10 Applications

2007-10-05T15:38:00.000-07:00

One of the important enhancements to eDeveloper V10 is the addition of full support for Unicode. This FAQ is designed to answer some of the high-level questions you may have regarding Unicode and its use in eDeveloper V10.

Q. What is Unicode?

A. The official definition can be found on the Unicode Consortium website in their glossary:

“Unicode. The universal character encoding, maintained by the Unicode Consortium (http://www.unicode.org/). This encoding standard provides the basis for processing, storage and interchange of text data in any language in all modern software and information technology protocols.”

Q. What are the benefits of Unicode?

A. Once again we turn to the Unicode Consortium for an answer:

“Unicode provides a unique number for every character, no matter what the platform, no matter what the program, no matter what the language. The Unicode Standard has been adopted by such industry leaders as Apple, HP, IBM, JustSystem, Microsoft, Oracle, SAP, Sun, Sybase, Unisys and many others. Unicode is required by modern standards such as XML, Java, ECMAScript (JavaScript), LDAP, CORBA 3.0, WML, etc., and is the official way to implement ISO/IEC 10646. It is supported in many operating systems, all modern browsers, and many other products. The emergence of the Unicode Standard, and the availability of tools supporting it, are among the most significant recent global software technology trends.”

“Incorporating Unicode into client-server or multi-tiered applications and websites offers significant cost savings over the use of legacy character sets. Unicode enables a single software product or a single website to be targeted across multiple platforms, languages and countries without re-engineering. It allows data to be transported through many different systems without corruption.”

Q. How extensively does eDeveloper V10 support Unicode?

A. eDeveloper V10 now includes across-the-board Unicode support within the product. Support for Unicode is provided in addition to existing support for both the ANSI and OEM standards.

Q. What specific Unicode capabilities are included in eDeveloper V10?

A. Unicode support in eDeveloper V10 includes the ability to read from and write to Unicode database fields; capability to input and output Unicode data to various Input and Output files; options to create program logic for Unicode data; techniques to perform read and write operations on Unicode files; capacity to send and receive Unicode data to and from external systems; and power to use Unicode definitions in expressions, functions, and form properties.

Q. What capabilities are there for Unicode Conversion?

A. eDeveloper V10’s implicit casting mechanism lets you select the code pages you
want to use for conversion to and from Unicode. If you don’t select the code
pages, eDeveloper V10 will use its own default code page. For purposes of explicit casting, there are two new functions:
• UnicodeFromANSI
• UnicodeToANSI

Q. Is it true that Unicode functions have been added to eDeveloper V10?

A. Yes, to complement the Unicode support, two new Unicode-related functions have
been added.
• UnicodeCHR - Converts a numeric value to a corresponding Unicode
character
• UnicodeVal - Converts a Unicode character to a corresponding numeric
value

Q. Are there utilities for Unicode Conversion?

A. Absolutely. eDeveloper V10 includes utilities that help you convert data from Unicode to ANSI and from ANSI to Unicode. The utilities let you define the input and output files as well as the code page to use, if you don’t want to use the default code page.

Q. Are there resources on the web to help us learn more about Unicode?

A. Of course. Start, of course with Unicode.org at http://www.unicode.org/

While I am sure you can google on your own, here are a couple more interesting pages to get you started on a nice long surfing expedition:

Alan Wood’s Page
http://www.alanwood.net/unicode/
This is a good resource page with links to many other useful sites.

W3C Page
And of course, W3C could not possibly be silent on a subject as important as Unicode, here is the XML/Unicode page:
http://www.w3.org/TR/unicode-xml/

Q. What character sets are supported by Unicode?

A. “More than you will ever need” is probably the shortest answer.

Specifically, Unicode 2.0 supports scripts for Arabic, Armenian, Bengali, Bopomofo, Cyrillic, Devanagari (the script employed by Hindi and Sanskrit), Georgian, Greek, Gujarati, Gurmukhi, Han, Hangul, Hebrew, Hiragana, Kannada, Katakana, Latin (including the international phonetic alphabet IPA), Lao, Malayalam, Oriya, Tamil, Telugu, Thai, and Tibetan scripts. These scripts are all written horizontally. Hebrew and Arabic are of course written right to left. Indic scripts are written variously and in ways that are sometimes described as a circular motion. Arabic and the Indic scripts must use intelligent ligature selection.

Unicode 3.0 expands some existing scripts and adds Braille, Canadian Aboriginal, Cherokee, Ethiopic, Khmer, Mongolian, Myanmar, Ogham, Runic, Sinhala, Syriac, Thaana, and Yi. Mongolian is the first script that can only be written in vertical rows.

Besides the characters for writing the world's major languages, there is a whole set of typographic, technical, graphical, mathematical, astrological and other scientific symbols and geometrical shapes in Unicode.

Q. I heard Unicode has limited support for Chinese, Japanese and Korean. Is that true?

A. Unicode supports Han scripts such as those used in Chinese, Japanese and Korean (often called CJK). Unfortunately some urban legends or myths have developed about the support of CJK characters in Unicode. According to unicode.org, “The Unicode Standard supports all of the CJK characters from JIS X 0208, JIS X 0212, JIS X 0221, or JIS X 0213, for example, and many more. This is true no matter which encoding form of Unicode is used: UTF-8, UTF-16, or UTF-32.”

In fact, Unicode supports more than 70,000 CJK characters. More will undoubtedly be added, but you can be assured that the support is comprehensive already and goes above and beyond what is expected. Unicode.org reports that “the International Standard ISO/IEC 10646 and the Unicode Standard are completely synchronized in repertoire and content. And that means that Unicode has the same repertoire as GB 18030, since that also is synchronized with ISO 10646 — although with a different ordering and byte format.” Rather a mouthful for those that do not follow these things in detail. And in the final analysis, that is the beauty of eDeveloper 10 – as with all previous versions of Magic, you do not need to get bogged down in the underlying technical details. With eDeveloper 10, just sit back, relax and enjoy full Unicode support.

Compliance Requirements Strain IT Resources

2007-10-05T13:40:00.000-07:00

For those of you keeping track of Magic Software's entry into the podcast age, here is a link to the interview on the subject of compliance with Carol Woodbury, Founder and President of Skyview Partners.

Learn more about the webinar here on Magic's website.

For information on ERP Integration, please look at the Integrate My JDE blog. You will find information on ERP and accounting interfaces and integration with CRM systems, enterprise portals, eCommerce, social media, and other business applications and software.

Thanks for the Memories: MIUG 2007

2007-05-10T13:46:00.000-07:00

What a great MIUG 2007! Thanks to everyone who participated in and attended this year's MIUG 2007. I hope that you will agree that this event provided an excellent foundation for members of the Magic community looking to advance and grow their businesses using the greatest development tool on the market today.

The key word at this year's event seems to have been "transparency." Thank you WIRED magazine for placing this concept top of mind for everyone. You probably noticed a few things that were different at this year's conference:

1. We started by showing our imminent built-in support for PDF. I am thinking that since it took us 6+ years of MIUG to release this feature, we should start each conference for the next six years by doing a PDF demo. :) The reason this is an evidence of transparency is that it showed that we listened to the input from last year, admitted our mistakes, and moved on.

2. The demonstration of he Rich Internet Client is also an evidence of transparency, in that we are showing that the input received during the CAPP migration process of last year has also influenced heavily on our development decisions.

3. Two years ago at MIUG, you may remember that we discussed the need for lower cost licensing models. It took us a little over a year to implement our solution, but we have also responded in a big way with the Discovery/Xpress/Enterprise Edition structure to answer the needs for seeding, affordability and power, respectively.

4. The focus roup sessions were invaluable. I am sure that you will see great things coming from Avishai Shafir as the lead person directing our Magic community programs and marketing.

5. Once again, we were delighted to be able to provide knowledgeable presenters from our R&D, technical support and professional services teams. We also love all of the presentations by each of you in the user community. The depth of your knowledge is invaluable.

6. Having our chairman, David Assia, present with us at MIUG was the icing on the cake this year. David's passion and vision are obvious and I hope that you can see that the future of eDeveloper is bright.

I want to take this opportunity to once again thank Dale and Heidi Schuppenauer and Cabrita Software for organizing the conference as well as SUmmer Remmert for her assistance.

See you all in 2008!

eDeveloper V10 Advanced Features Webinar

2007-03-03T12:18:00.000-08:00

eDeveloper V10 -- Advanced Features

Topic: eDeveloper V10 -- Advanced Features
Date: Wednesday, March 21, 2007
Time: 11:00 am, Pacific Daylight Time (GMT -07:00, San Francisco)

Join Roberto Ramirez, a Senior Consultant in the Professional Services Department at Magic Software Enterprises, Inc. in Laguna Hills, California, who will present three important advanced features in eDeveloper V10:

Report Generator. End users seek applications that allow them to build their own reports on the fly. The powerful new runtime report generator in eDeveloper V10 Enterprise Edition is better than ever and will be explored from both the developers' and the end users' perspective.

Team Development. It's hard enough for a solo programmer to keep track of revisions and versions of their software. When you add one or more additional developers, then team development solutions are vital. With eDeveloper V10 Enterprise Edition you can use the source code control software of your choice, including the bundled CVS software.

Graphical User Interface Enhancements. Your users will absolutely love the enhanced usability and improved aesthetics of the new applications you create with eDeveloper V10. Learn what you can do now to create immediate raves from your customers and end users.

Registration. To attend this meeting, you must first register for it. Please click here to see more information about and register for this meeting.

Once you have registered for the meeting, you will receive an email message confirming your registration. This message will provide the information that you need to join the meeting.

How do you define software quality?

2007-02-26T15:50:00.000-08:00

ISO 9126 provides a standardized way to evaluate software quality by defining six sets of attributes by which we can evaluate software. These attribute sets are functionality, reliability, usability, efficiency, maintainability, and portability. What do they mean by these standards?

Functionality refers to the existence of a set of functions and their associated properties. Functionality gets to the fundamental ability of a software application to perform the required tasks necessary to satisfy user and organizational needs.

Reliability refers to the stable performance of these functions under a variety of conditions across time.

Usability as approached by ISO 9126 deals with the effort needed for use, and user assessment and acceptance.

Efficiency is all about performance issues and the resources required to perform the software functions under various conditions over time.

Functionality, reliability, usability and efficiency are all characteristics observable by users or operators. The other two criteria for measuring software quality that are contained in ISO 9126 relate to the developers ability to interact with a given software application. It isn't only an assessment of the tools used, but also how well the tools were used to accomplish the need for these next criteria:

Maintainability looks at the effort required to make specific modifications. We all know that some applications are easier to maintain than others due to variations in documentation, organization and software architecture.

Portability, or the ability to run applications in new environments, can also be impacted by the developer, and not simply by the tools she uses. For example, an application that utilizes many environment specific utilities may be more difficult to port to a new environment where those utilities may be unavailable or handled in a different manner.

With eDeveloper V10, you gain a software development environment for application development, testing, and deployment that enhances software quality in all of these areas for a number of reasons. In future posts, will look at all of these areas in detail.

Magic eDeveloper Enters the Podcast Age

2007-02-22T09:18:00.000-08:00

Well folks, here it is the long awaited and much ballyhooed eDeveloper Contest podcast. Please click here and enjoy the first ever (and definitely not the last) Magic eDeveloper podcast.

Get Ready for Daylight Savings Time 2007

2007-02-07T16:06:00.000-08:00

Does your application use a table that lists the date and time of the switch to/from Daylight Savings time? If so, be forwarned: Congress has changed the dates in the United States beginning in 2007! Canada and many Carribean countries have changed their DST timetables as well.

Previous start to DST: First Sunday of April (1 April 2007)
New start of DST: Second Sunday of March (11 March 2007)
Previous end of DST: last Sunday of October (28 October 2007)
New end of DST: first Sunday of November (4 November 2007)

What types of applications could be afected?

Scheduling Applications. The most obvious are calendaring or scheduling applications, especially those that accomodate multiple international time zones. One example might be an international air freight scheduling system. Another example would be CRM scheduling systems that send email notices that localize the time of a scheduled appointment.

Applications with Time Calculations. An application that performs calculations using minutes or hours could be thrown off. For example, piece workers who are paid bonuses based on exceeding a certain number of pieces in a given time period. The calculations could be off by 60 minutes or 1 hour.

Data Synchronization Batch Jobs Suppose one data center is scheduled to synchronize data at a given local time, say 2 am, and another data center is normally completing its batch jobs prior to that so that the synched data center has current information -- or at least they should have, but the foreign data center does not know that it is synchronizing to data that has not yet updated because of the time change. Since it is a batch job that has not completed, the information could be off by a complete 24 hours or more. Any reports generated against that information, or supply chain orders dependent on that information, could be seriously off.

Planes Will Not Fall Out of the Sky I talked to my colleagues about this and they reminded me that planes will not fall out of the sky. But it is worth considering now, whether any of your applications are dependent on accurate update of daylight savings time.

The New Report Generator

2007-02-05T22:00:00.000-08:00

Important: The New Report Generator is Here

1. What is it good for?

Many years ago eDeveloper (then named Magic) used to come bundled with a report generator. This was an amazing tool, basically allowing end users to create their own reports by letting them run existing reports, create new reports, delete reports, duplicate reports, load reports created by others, view the results of an existing report, or print a report, based on warehouse type views created by developers. Some of you may have missed the new report generator that was slipped into eDeveloper V10.1. It sort of snuck in the side door with the 10.1 version and very little noise has been made about it to date. So let's correct that now: the report generator is back and its more powerful than ever. There are two other ways to deal with report generation that are documented in the Help files for eDeveloper. But the new Report Generator has its own help files from which I will summarize.

2. So, how do I use it?

2.1. Loading

Create a component and then zoom to select the ReportingGenerator.eci application from the Add_On directory.

In the task you want to work with, set the Print Data property in the Options tab of the Task Properties dialog box to Yes.

Run the program that you want to print data from.

Press CTRL+P to open the Report Generator. The Select Report screen opens.

2.2. Using the Generator
The Select Report screen helps you manage reports with the following options (available as buttons or options in the File menu):

New - Opens the Report Creation wizard where you can create a new report.

Edit - Lets you edit the report that you have selected.

Delete - Deletes the report that you have selected.

Duplicate - Copies the report that you have selected.

Load - Lets you use reports created by others for the same eDeveloper program. You do this by moving reports to a visible place on your computer and then clicking the Load icon. This enables you to select the required report. This option is in the File menu.

Preview - Provides a preview of the report that you have selected.

Print - Prints the report that you have selected.

2.2.1. Report Creation Wizard

The Report Generator is equipped with a wizard that helps you create your report easily, step by step. Click New in the Select Report screen to activate the Report Creation wizard.
The Report Creation wizard contains six simple steps, but you do not have to complete all six steps to create a report. You may complete your report and exit the wizard at any time by clicking Finish or Close.
If you click Finish, the wizard closes, the Design screen opens, and the information you have entered in the wizard screens is automatically saved.
If you click Close, the wizard closes, the Design screen opens, but the information you have entered will not be saved unless you click Save.
The six steps of the Report Generation Wizard are:

2.2.1.1. Setting

The Setting step lets you define your report name and layout.
The report default name is the name of the eDeveloper program where the Report Generator is activated

2.2.1.2. Columns

The Columns step lets you select the variables you want to display, and their order, in the report table.
The left part of the screen shows the available columns, which includes all the fields selected in the eDeveloper program. The right part of the screen shows the columns you selected to be included in your report.
On the Columns screen you can perform the operations listed below:

Rename a column by clicking on the column, and then clicking the button. Enter a new name in the Column Properties dialog box and click OK.Note: This only changes the column name for the current report.

Change the Date Format by marking a Date column you would like to change and pressing the button. You can edit the column name and change its date format in the Column Properties dialog box and click OK.Note: The default format for Date columns is dd/mm/yyyy.

Select all columns by pressing the button.

Select a variable by using one of the following methods:
Drag a variable from the Available Items list to the Selected Items list.
Select a variable and click the button.
Double-click on a variable in the Available Items list.

Unselect all columns by pressing the button.

Unselect a column by marking the column and pressing the button.

Move a column up by marking it and clicking the button.

Move a column down by marking it and clicking the button

2.2.1.3. Sections

The Sections step lets you divide your report into subsections that are similar to the grouping in eDeveloper.
On the Sections screen you can perform the operations listed below:

Define Section Properties – Click on the section whose properties you want to define, and then click the button to:
- Change the title of a section.
- Choose if you want to start the section on a new page.
- Choose if you want to print the section title on every page.

Select a column by using one of the following methods:
- Drag a variable from the Available Items list to the Selected Items list.
- Select a variable and click the button.
- Double-click on a variable in the Available Items list.

Unselect all columns by pressing the button.

Unselect a column by marking the column and pressing the button.

Move a column up by marking it and clicking the button.

Move a column down by marking it and clicking the button.

2.2.1.4. Sorting
The Sorting step lets you define the sort order of the report.
On the Sorting screen you can perform the operations listed below:

Change the Sort order by selecting a column and pressing the button to open the Sort Properties dialog box and select the change.Note: The default sort order of a column is ascending.

Select the columns by using one of the following methods:
- Drag a column from the Available Items list to the Selected Items list.
- Select a column and click the button.
- Double-click on a column in the Available items list.

Unselect all columns by pressing the button.

Unselect a column by marking the column and pressing the button.

Move a column up by marking it and clicking the button.

Move a column down by marking it and clicking the button.

2.2.1.5. Filtering

The Filtering step lets you define an expression that will filter the report result.
Create a filtering expression by dragging and dropping Functions, Operations, or Variables (variable names are preceded by ~) from the right list to the left working area.
Click Test to check if the expression you created is valid.

2.2.1.6. Accumulators

The Accumulators step lets you create Accumulators for your report, such as the total salaries amount or employee count.
Create a new Accumulator by selecting a column from the Available Items list on the left and moving it to the Selected Items list on the right.
On the Accumulators screen you can perform the operations listed below:

Define the Accumulator type by selecting an accumulator and clicking the button.Note: The default type for numeric data is SUM, and the default type for all other data is Count.

Select the Accumulators by using one of the following methods:
- Drag a column from the Available Items list to the Selected Items list.
- Select a column and click the button.
- Double-click on a column in the Available items list.

Unselect all Accumulators by pressing the button.

Unselect an Accumulator by marking the column and pressing the button.

Move an Accumulator up by marking it and clicking the button.

Move an Accumulator down by marking it and clicking the button.

2.2.2. The Design Screen
The main screen of the Report Generator is the design screen, which lets you graphically design and save the report.
To help you create a better report with less effort, the Design screen contains the tools listed below:

2.2.2.1. Drawing Aids Palette
The Drawing Aids palette helps you arrange the Elements and Variables you have added to the report. The buttons on this palette identify the available operations, and a ToolTip describes each operation.

2.2.2.2. Elements List Palette
The Elements List palette lets you add elements to your report. There are three types of Elements:

Variables – All the fields you selected in the invoking eDeveloper program with the names you gave them.

Added Variables – The variables you added to the report using the Variables Management Tool.

Internal Elements that help you design your report properly, including:
Rectangle
Image
Line
Simple Text
Report Title
Date
Page Number

2.2.2.3. Report Generation Design Toolbar
The Report Generator Design toolbar lets you perform the operations needed to create your report. The toolbar buttons include:

Saves your report with the changes you made.

Displays the report you created.

Print the report.

Similar to the Wizard’s Setting screen.

See Variables Management Tool.

Similar to the Wizard’s Columns screen.

Similar to the Wizard’s Sections screen.

Similar to the Wizard’s Sorting screen.

Similar to the Wizard’s Filtering screen.

Similar to the Wizard’s Accumulators screen.

Lets you redesign the screen according to the default values. When you press this button, all the changes you made will be lost

Displays the Elements List Palette.

Displays the Drawing Aides Palette.

2.2.2.4. Variables Management Tool
Click on the Report Generator Design Toolbar to add and remove Variables and User Questions to your report.
Adding Variables:

To add a new variable, press the Add Variable button, enter the variable name, select the variable type, and click OK to open a Column Properties dialog box.

Create an expression by dragging and dropping Functions, Operations, or Variables (variable names are preceded by ~) from the right list to the left working area.

Click Test to check if the expression you created is valid.

Click OK to complete the new variable creation.

Adding User Questions
The User Questions mechanism lets you ask the user who will run the report questions that will influence the report result data. Click the Add User Question button, enter the Name and Question type in the Add New Variable dialog box, and click OK to continue. You can later find your question by this name in the Expression Editor.
In the User Question dialog box, enter the question you want the user to see and the default value of the answer.

Removing Variables and User Questions
To remove a variable or user question you added to the report, select the variable you want to remove, and click the Remove variable button.

The Remove variable button is only applicable for variables and user questions you created in the Report Generator.

2.3. Summary

No more simple reports hustle. The new report generator allows developers to create a view using main application entities linked to each other. The column names can be changed to user friendly names in the Dataview tab. Users can then create simple reports based on that view, allowing developers to concentrate on what they do best.

Quote of the Day -- David James

2007-01-30T10:20:00.000-08:00

"eDeveloper V10 does a great job in handling XML, parallel processing, debugging, and web services. It's a straight forward tool that helps us save time and money, while reacting quickly to our customers' changing business needs."

David James
Senior Developer,
Warren-Board

Windows Vista

2007-01-30T10:14:00.000-08:00

The much delayed Windows Vista operating system is now shipping from Microsoft.

The official statement from Magic Software Enteprises is that

"eDeveloper 10.1 SP2 and higher will be supported for "Windows Vista".

Previous releases of Magic (including 9.4) are not supported and were never qualified."

New eDeveloper V10 OS Releases Announced

2007-01-22T12:16:00.000-08:00

Magic Software has added new operating system versions of eDeveloper V10 to the Downloads Area. These are available for download by customers with an eService account at http://downloads.magicsoftware.com

The new versions posted last week are:

eDeveloper Server 10.1 SP1 for IBM AIX

eDeveloper Server 10.1 SP1 for Sun Solaris

eDeveloper Server 10.1 SP1 for Linux

Quote of the Day -- David Schmukler

2007-01-22T12:11:00.000-08:00

XML enhancements and an upgraded RAD

"...as an IT professional I am very impressed with eDeveloper 10's XML enhancements and the upgraded RAD. As to user experience, eDeveloper 10 allows multiple contacts, permitting two active windows to be open at the same time. This is a significant improvement to the user experience".

David Schmukler
Chief Technology Officer,
New Era Solutions

My Magical Christmas Wish List

2006-12-21T12:58:00.000-08:00

A Christmas Wish List Powered By Magic Software

So many wonderful things are backed up behind the scenes by Magic Software. Here are ten things I'd love to get in my Christmas stocking that are "powered by Magic."

1. Lakers Tickets – The Staples Center uses ABI MasterMind, an application written in eDeveloper. So my number one wish is for Lakers Tickets.
2. A Subscription to the Orange County Register. – The Orange County Register uses Burt Technologies software for newspaper insert management, so I'd like a subscription to the paper, please.
3. Dinner at Outback Steakhouse. – Wow, this is already becoming the greatest Christmas Stocking ever and I'm only at number 3.
4. Weekend Rental of a Chrysler Sebring Convertible from Advantage Rent A Car. – Nothing like a weekend cruising Pacific Coast Highway.
5. Casino Upgrades at the Orleans Casino. – That's right. Orleans Casino is one of 16 casinos operated by Boyd Gaming, a Magic customer.
6. A Bottle of Kenneth Cole Signature, Men's Fragrance. – One of many designer brands carried by Coty, another Magic customer.
7. A Pair of adidas Climawarm Herm shoes, Size 13. – OK, I know my Christmas Stocking is getting full, but it’s a big stocking. :)
8. Club Med Vacation – Uh huh, Club Meds worldwide are powered by Magic applications.
9. World Peace I can too get World Peace delivered by a Magic application for Christmas! You see, the United Nations General Assembly wrote a special Magic application to manage its resolutions and amendments in the five official languages of the UN (English, French, Chinese, Russian and Arabic). Pretty cool, huh?
10. A Lump of Coal Unfortunately, I may only get and deserve this last item, which could be delivered by Magic customer Wabush Mines up in Quebec and Labrador, Canada.

Here's hoping you all get the things that you are wishing for next year. Please join me in adding number 9 to your list. Happy Hanukkah! Merry Christmas! Happy New Year!

WS-* At Your Service With eDeveloper V10

2006-11-29T16:30:00.000-08:00

A Little Magic for Web Services

The World Wide Web Consortium (W3C) defines a Web service as "a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards."

eDeveloper V10 provides powerful capabilities for creating and integrating applications that utilize Web services. Internally, eDeveloper V10 uses the Systinet Web Services framework (specifically "Systinet Server for Java") for providing and consuming Web Services. Fortunately, you don't have to do any Java programming in order to develop programs that take advantage of this foundation.

The WS standards supported by eDeveloper include SOAP 1.1 and SOAP 1.2; WSDL 1.1; SOAP Attachments; WS-I conformance; transport level security; and WS-Security for authentication, encryption and digital signing of SOAP messages. For reference, SOAP is Simple Object Access Protocol, WSDL is Web Services Description Language, UDDI is Universal Description Discovery and Integration, and WS signifies Web Services. WS-* refers to any of several enhancements or extensions to the basic SOAP, WSDL and UDDI standards, including WS-Interoperability and WS-Security.

I like to think of Web services as shared application logic (and associated data). For example, a Web service might be used to provide access to changing data such as stock ticker symbols (companies are listed and delisted). A service is said to be finely grained when it performs a narrow function, for example, a service that returns the range between the minimum and maximum value in a series of numbers. A coarsely grained web service might contain fairly complex functionality, such as a Web service that processes an order, calculates shipping charges and sends confirmation emails – in a single web service. The object of the game is to create fine grained services, but not too finely grained, so as to avoid the inflexibility of coarsely grained services on the one hand and the complex orchestration of finely grained services on the other.

To use eDeveloper as a Web Services consumer you can either use the Web Service Composite Generator or the Invoke Web Service operation.

To use eDeveloper as a Web Services provider, you should generate a service using the Web Service Interface Builder. To deploy and use the service you should make sure the following Windows OS service is started – “Systinet Server for Java”.
For information about how eDeveloper V10 deals with migration of Web Services from eDeveloper 9.4 applications, see Conversion Process Modifications.

The Web Service Composite Generator is a wizard used to generate a component that accesses a Web Service.

The How-to is fairly straightforward. First, you access the composite generators by following the Main Wizard Module steps. In the Web Service Location screen, click the WSDL URL or UDDI Search option. If you selected WSDL URL, enter the location of the WSDL. You can enter up to 256 characters in the WSDL URL field. You can click the Browse button to search for the WSDL file on the disk. The you click Next and eDeveloper will access and parse the WSDL file. If a WSDL file is not found or if the WSDL file is invalid, an error message will appear.

If you selected the UDDI Search option, the UDDI Server and Search String screen will appear. If you selected the WSDL URL option, the Operation Selection screen will appear. But we won't get into those details here (you can find more information in the documentation).

To see what happens once you finish using the Web Service wizard, see the Generated Web Service Component topic in the documentation.

Invoke Web Service lets you call a Web Service by using the SOAP protocol. When you select the Invoke Web S (Service) operation, you select a service that has been defined in the Service repository as a SOAP type. Zoom from the space to the right of Web S to open the Web Service dialog box, where you can define the Service, Operation, and Fault properties.

The Web Service Interface Builder lets you provide Web Services using eDeveloper by exposing public batch programs. The builder will generate a service JAR file and optionally deploy it on a Systinet™ server (which is installed as part of the eDeveloper installation, identified as a Web Services framework).

To successfully generate and deploy the Web Service, you should make sure that the following Windows service is started: "Systinet Server for Java". The Web Service Interface Builder is not available in the eDeveloper Discovery version.

With eDeveloper V10, you can also easily see the available Web services that you have created. The Available Web Services screen is a list of previously created Web Services as well as additional details. You can view and delete the available Web Services from the list, but you cannot modify the data in this screen.
As those who have published and subscribed to Web Services in eDeveloper 9.4 will tell you, this is a much more elegant and straightforward implementation and has the great advantage of being compliant with WS-Interoperability and WS-Security : two more great reasons to upgrade to eDeveloper V10. For all the details, see the user documentation online at www.magicsoftware.com.

eDeveloper and SNMP: Part Two – Making it Happen

2006-11-07T09:54:00.000-08:00

Using eDeveloper and SNMP
eDeveloper applications and various components or modules can send trap messages to a pre-configured Network Management Station (NMS), also referred to as an SNMP monitor, which lets the system administrator query and control the eDeveloper application or module when alarms, failures, or other exceptional events occur.

The SNMP DLL
Needless to say, the SNMP agent must be present on the operating system and the eDeveloper SNMP extension, the Mgsnmp.dll file, must be placed in the eDeveloper root during installation.

The MIB files
eDeveloper supplies two Management Information Base (MIB) files, Magic.mib and Magic_trap.mib. These are located in the eDeveloper Support directory. The MIB files are compiled according to the NMS version installed. You should copy the MIB files to the NMS server.

Overview of SNMP Use in Magic
You can set various values for the SNMP parameters, defined in the Mgreq.ini and Mgrb.ini files, to specify when the Magic Requester and Magic Requester Broker will send trap messages.

The SNMPNotify function is utilized to issue SNMP messages with the available parameters of message, severity.

When an alarm or error occurs outside of the application development process, SNMP trap messages are sent to the Network Management Station (NMS).

Examples of the types of trap messages sent are:

A thread crash or fatal error of eDeveloper or the eDeveloper gateway.

Termination due to the license limit.

Unable to connect to a specified DBMS.

Database connection threshold exceeded.

An enterprise server was stopped and started. The trap message contains the address of the enterprise server.

An enterprise server aborted its connection to the Magic Request Broker. The trap message contains the address of the enterprise server.

Anyway, this is an overview of SNMP and eDeveloper. If you are not familiar with SNMP applications, such as IBM Tivoli, then some of this discussion may seem like a foreign language discussion. For more information on SNMP, try the official Internet Engineering Task Force website for official information contained in the Request for Comments (RFC) documents. But for those familiar with SNMP for application monitoring, you can see from this overview that eDeveloper "plays well" with SNMP application monitors and other SNMP oriented software.

SNMP and eDeveloper: Part 1 – Theory and Use

2006-11-06T11:09:00.000-08:00

eDeveloper supports Simple Network Management Protocol (SNMP) and works with Microsoft Windows SNMP Agent, the Net-SNMP Agent in UNIX environments, and the Native SNMP Agent in the i5OS (OS/400) environment for IBM System i (iSeries).

SNMP is a standard in the application layer of the Internet protocol suite for management of various nodes on an IP network. SNMP enables network administrators to manage network performance, find and solve network problems, and plan for network growth. For developers, SNMP is the standard that you can use to communicate with application monitoring and other monitoring tools.

The SNMP architectural model involves a set of network management stations and network elements. The purpose of the network management stations is to host management applications that control and monitor network elements. The network elements are devices that serve as gateways, hosts, terminal servers, etc. These various network elements have management agents that execute management functions requested by the network management stations. SNMP, as a protocol, includes the message format used to communicate between the stations and the elements.

In general, application monitoring can be applied for any of these five broad requirements:

Fault
The most obvious use of application monitoring is to detect faults which can be major errors related to one or more elements within the architecture. eDeveloper can be configured to send only specific error codes to the monitor, or the entire range of errors. Normally, you would want to report only significant error conditions that affect the operational integrity of the application or quality of the users' application experience.

Performance
External monitors may want to track application performance. Performance monitoring is useful in detecting sub-optimal software performance, as measured by average wait time, number of pending requests, number of currently processing requests, and so on. Performance problems usually correlate to increased user requests. When the load outstrips the ability of the application and systems to perform the required function within expected response times, a degraded quality of user experience occurs. Application monitoring can provide us with useful metrics for performance optimization related to both applications and the network itself.

Security
You may want to employ SNMP for certain types of security monitoring such as authentication failures.

Configuration
By monitoring certain configuration settings, you can ensure that key configuration variables affecting application performance and stability stay within specified limits. For example, if the Maximum Connection property is set to 10 for a specified DBMS and the SNMP Database Connections Utilization Threshold is set to 50, eDeveloper sends a trap message to the Network Management Station (NMS) when 5 connections (50% of 10) to the DBMS have been opened.

Accounting
Another application for application monitoring is accounting, for administration of things like usage fees and maintenance fees. SNMP is used when a third party application tracking these fees utilizes SNMP to monitor the activity to be accounted for. Since an eDeveloper can easily track these elements within the application itself or through another eDeveloper application, SNMP is only likely to be used in rare instances where an enterprise wide IT policy has introduced SNMP as an accounting standard, especially in environments where there is a mix of eDeveloper and non-eDeveloper applications being accounted for.

Application monitoring via SNMP can be implemented using applications such as IBM Tivoli. For example, IBM Tivoli Business Application Management (BAM) products help ensure the availability and performance of your business-critical applications, including portal and Service Oriented Architecture (SOA)-based technologies. In Part Two, we'll look at some of the how-to required to support SNMP monitoring of an eDeveloper application.

Quote of the Day -- Mark Bailey

2006-11-03T09:56:00.000-08:00

As seen on the Magic List at Yahoo! Groups.

"I am currently converting ALL of my apps to eDeveloper V10.

Everything I have converted so far works and the extra effort I am putting in is just to take advantage of the new features.

The more I use it, the more I love it. Never ceases to amaze me how many programs I have with no logic and it takes a bit of getting used to, opening a program and not seeing the Task or Record levels sitting there empty.

And, man o man. The Subforms and User Functions are Brilliant!!!!"

Mark Bailey, Australia

Thanks, Mark! Glad to hear it. I'll have to buy you a Foster's at the next MIUG in Vegas. [emphasis added].

What's in the Kitchen Sink, Anyway?

2006-11-02T18:12:00.000-08:00

With eDeveloper V10, the feature list goes on an on. 51 reasons clearly are not enough as this review misses major enhancements like full Unicode support, superior XML handling, the new report writer and much more. But before we look at the bonuses and extras not included in Magic's list of reasons, let's look at the general enhancements they do mention in the list of 51.

In the list of 51 reasons to upgrade to eDeveloper V10, reasons 47 through 51 are dedicated to an assortment of improvements, this where Magic's R&D department has "thrown in the kitchen sink" and now I get to describe it. No snoring! There actually is some good stuff in here!

47. Preload View – Have every data-view fully loaded upon task execution for improved scrolling and for retrieval full view related information.

I think this advantage could have been expressed more clearly. Have you ever loaded a really large file and noticed that your scrollbar slider adjusted its size to the number of records. Well that's what we're talking about here. Now eDeveloper programmers don't have to come up with tricks and schemes to size the thumb on the scrollbar slider, it's built-in.

The scrollbar thumb reflects the size of the table content according to the number of records that are fetched while the task is running. When opening a task, the table reads the first set of records and the thumb size is based on that first set. Then, as an end-user scrolls through the records, the thumb is progressively updated.

48. Dynamic Menus – Construct modular menu structures based on menu subsets that can be automatically added or removed from the pulldown menu.

eDeveloper V10's new menu-related functions let you dynamically add and remove menus to the menu structure. The functions allowed are MnuAdd and MnuRemove which enable the programmer to dynamically add or remove a menu structure to the current runtime pulldown menu structure. There is also a MnuReset function that restores the default pulldown menu structure. This gives you some very sophisticated contextual control over the user experience that can streamline and enhance the user experience.

49. Windows Menu – Easily set the application menu system to cascade all selected open windows for easier end-user window navigation.

To quote on of my favorite lines from the movie Joe Versus the Volcano, "I have no response to that."

50. DateTime Support – Simplify the retrieval and storage of DateTime data types by letting the Magic Rules Engine automatically map them into simplified and separated Date and Time units.

While many of you may have developed workarounds for this in the past, I am sure it will be nice to have automated conversion between DateTime and Date and Time.

51. Standard Keyboard Mapping – Easily adopt a new Keyboard mapping scheme that corresponds to the accepted keyboard mapping standards.

Keyboard shortcut standards seem to change all the time. I've also found that certain user communities have differing expectations. eDeveloper users expect F5 to "zoom" of course, but what if your end users have a completely different map in their head because of some other application pervasive throughout their organization? Wouldn't it be better to change the keyboard mapping used in your eDeveloper application, rather than try to force all your users to learn a new set of keystrokes? Probably, so eDeveloper V10 gives you that option. You can map eDeveloper's studio keyboard map as well as the map used in your application at runtime.

The Keyboard Mapping settings you edit are kept in a special file. The file eDeveloper uses is named in the Keyboard Mapping File setting in the Options/Settings/Environment dialog box. By default this file is ACT_STD.ENG. You can create and use different mapping files. On conclusion of an editing session of the Keyboard Mapping repository, eDeveloper prompts you to save the changes with the File Save dialog box. You can save these changes to a file different from the one currently used by eDeveloper, by specifying a different name in the Save As... property.

This concludes our analysis of the original list of 51 "numerous reasons to migrate to eDeveloper V10." But don't worry, here in blogland, we've come up with some important reasons of our own. So stay tuned.

Parallel Parking and Other eDeveloper V10 Tricks

2006-11-01T09:29:00.000-08:00

The eDeveloper enterprise server supports parallel execution of tasks or multithreading. Whether your tasks are truly executed in parallel or are conducted in pseudo-parallel mode through a technique called time slicing is dependent on your hardware and operating system. With traditional programming tools, the programmer must carefully design the program in such a way that all the threads can run at the same time without interfering with each other. With eDeveloper, multiple contexts are maintained automatically and controlling contexts is simplified tremendously compared to unnecessarily complex 4GL and 3GL development systems.

And the good news, no the great news, is that multiple document interface (MDI) and single document interface support is now built-in to eDeveloper, further simplifying development of applications that meet the needs and demands of your users.

In the list of 51 reasons to upgrade to eDeveloper V10, reasons 42 through 46 are dedicated to parallel execution, i.e., multithreading. Let's take a closer look at each claim to better understand what's behind it.

42. Concurrent Task Execution – Provide a greater application productivity level by enabling the end-user to run several processes - online and batch - simultaneously.

In eDeveloper v9.x, multithreading was available for background processing only. Now with eDeveloper V10, background enterprise servers and Online programs are multi-threaded. This gives you the ability to have parallel task execution in your projects for both batch and online tasks.

Each thread accesses a different Runtime context, and does not interact with other threads, in other words, it is stateless.

To work with multiple threads in Online programs, eDeveloper V10 provides you with powerful new Multiple Document Interface (MDI) and Single Document Interface (SDI) functionality.

43. Single Instance – Easily control concurrently running tasks to keep a single instance for proper implementation of console screens, palettes, and property sheets.

When you are using parallel tasks, and you call a program again, a new instance of the program opens. To better illustrate what we mean, consider what happens with a well-known application like Internet Explorer. The first time you open Internet Explorer, one instance of it opens to your default home page. When that instance is open and you open Internet Explorer again, a second instance opens to the default home page regardless of the context, i.e., the current URL of the already open browser window. However, sometimes you want the same context to open, such as when you use the "New Window" option in Internet Explorer and you get a second window with the same context as the previous window. A third option is that you do not want multiple windows and contexts. You want the new instance with its new URL to open in the already open window. Internet Explorer allows the user or the developer to control this kind of functionality.

eDeveloper V10 now supports both multiple document interfaces and single document interfaces and gives you as the developer, control over the way contexts are handled. In those situations where you want the second call to return to the original instance, this is what eDeveloper's Single Instance task property does. When you select this property, when a program is called for a second time, the focus will be set on the already running instance. However, there will be no initialization steps (such as preparing the data view).

44. Event Posting – Enable full interaction between all concurrent processes using the inter-context event posting mechanism.

Most of the time, you will probably want instances to execute independently, but there are some events that may require you to enable events to be sent between contexts. Using eDeveloper V10's event posting functionality is accomplished via the Destination Context Name property of the Raise Event operation. The mechanism allows for synchronous and asynchronous events. If a synchronous event was raised, the context waits until the receiving handler ends. I like the fact that eDeveloper V10 gives the developer all of these options and doesn't restrict the developer to stateless contexts without interaction.

45. Single & Multiple Document Interface – You now have the freedom to choose the layout by which your parallel tasks will be presented. You can have a parallel task be displayed as yet another MDI child window or an independent SDI window.

This is another new eDeveloper V10 feature that standing completely on its own will justify the upgrade in the minds of many developers. eDeveloper lets you define a Multiple Document Interface (MDI) as well as a Single Document Interface (SDI).

In the most basic of terms: the MDI and SDI functionality allows an application to open and concurrently run several tasks. That is, it enables a program to be opened concurrently without the need to open a new instance of eDeveloper.
The eDeveloper engine can maintain multiple concurrent instances, executing programs within the same application and within the same eDeveloper instance.
In eDeveloper, concurrent execution is implemented using contexts. When a program is run concurrently and a new context is opened, the new context will have its own Main Program. This Main Program and context are independent of the other contexts running under this process. Read up on the MDI and start using it, your users will applaud.

46. Window Focus Management – Using a simple set of functions and events eDeveloper gives you a full control over the focus management of all your windows. Easily handle lost-focus events and easily instruct a window to get focus.

The default behavior for contect management is pretty much as you would expect: When focusing on a window in a different context, eDeveloper will not lose track of the control in the current context. In this fashion, when focus is passed back to this original window, it will pass back to the same control. Similarly, if there is a window that is not in focus, and a dialog box appears, such as a Verify operation or the window's own form with a Window Type property of Modal, the focus will pass to the dialog box. If a different context opens a window, the focus will pass to that window. Using the expression editor, you can utlilize the SetWindowFocus function to determine the particular window in the Window list that will be in focus. During runtime, if the window does not exist (the name does not exist or the name is blank or Null), focus will remain on the current window and the function will return False.

So all in all, parallel execution is another home run for eDeveloper V10, if you will forgive the baseball metaphor. The multi-threaded architecture of eDeveloper can now be enjoyed in both online and batch mode. Just in time, I think, as duo core and quad core processors are becoming commonplace on client desktops. You'd better get ready now as the world of parallel processing has entered the mind of the everyday user and they will demand the functionality that eDeveloper V10 delivers.

Fewer Bugs and Better Bug Spray

2006-10-31T16:15:00.000-08:00

Terrence Parr, a University of San Francisco Professor of Computer Science, suggests that there are six essential elements in the debugging process:

Reproduce the error. By finding a way to reproduce an error, you can often see the cause of the error. Parr says, "A bug that appears randomly is essentially unsolvable unless you have a leap of insight."

Reduce problems to their essence. Once you have discovered how to reproduce a problem, you should attempt to isolate an error to its smallest constituents. Parr suggest slicing data inputs, for example, to see which part of a file causes the problem.

Use your powers of deduction to find causality. This involves forming a hypothesis that can be tested. Follow the path of the data and watch for factors that can contribute to an error.

Test your hypothesis. Change various elements in the environment, the data and the logic to test your hypothesis.

Draw on experience. If you are an experienced developer, you will look for problems similar to those you have seen before in like situations. If you are a new developer, then you may want to consult another developer (Magic eDeveloper discussions are available on Yahoo! groups at magicu-l, for example.
Never give up. By taking a systematic approach, you will first test the hypotheses that seem most likely based on logic and past experience. Be patient, communicate with others and the solutions will become apparent.

Never give up. Parr sees tenacity as the final essential ingredient.Fortunately for users of eDeveloper V10, a new debugger has been introduced that makes extermination of bugs much easier than before.

Let's continue our review of Magic Software's 51 reasons to upgrade to eDeveloper V10. Reasons 36 through 41 all deal with enhancements to the debugger:

36. Visual Debugging – Follow the exact logic definition within the studio as you progress step-by-step in debug mode.

This feature can help you pinpoint problems that you are having in an application by stepping through an application with pauses at pre-defined breakpoints.

When you are in Debug mode (you selected Debug Mode from the Debug menu), you can run a program in Runtime mode and the Debugger will "park" on the Studio read-only screen at the exact location of where you are in the program (when a breakpoint is reached).

37. Manageable Break Points – Have full control on every break point defined in the application using the fully functional break points palette.

Obviously, breakpoints are a helpful tool for debugging. As Parr suggests in his point regarding the use of deduction, you need to follow the path of your data through an application in order to deduce any flaws in your logic. Breakpoints allow you to pause the logic at any point and determine exactly where things stand. Breakpoints let you halt execution of the program at a specific location in the Studio screen, so the debugger parallels the design of your program, which also gives you a clearer ability to see where problems may be introducuing themselves.

The how-to of breakpoints is quite straightforward, when you select Breakpoints from the View menu, the Breakpoint repository appears. You should remember that when you add a breakpoint to the Logic Editor, the default Condition is Always.

38. Conditional Break Points – Reduce your debugging efforts by conditioning your set breakpoints for accurate and focus debugging.

Within the Debugger, you can define a conditional breakpoint if the Enable check box is selected. The condition will be evaluated each time the breakpoint is reached. If the condition evaluates to False, the breakpoint will be ignored.

The valid options for breakpoint conditions are Always, Count and Condition. With count, the breakpoint is only activated once the specified count has been reached. And of course, with a condition, the breakpoint will only be executed if the condition is True.

Condition: Execution will break only when the condition evaluates to True. This option is only enabled if the task in which the condition is defined is in focus. You can use variables from the current task tree.

39. Watch points – Easily collect all variables that require your attention in the debugging process for efficient monitoring over the progress of your logic.

The watch points are very handy and make it easy to focus in on the variables that your experience suggests are most important. The Watch Variable list displays the variables currently being watched. This allows you to see how the value of the watched variable changes. You control which variables are displayed on the Watch variable list from the Variable list itself and the Variable declaration(s).

40. Modifiable Variables – Manipulate the execution of a debugged execution by directly modifying the value of any variable.

The context menu gives you control over modification of variables in the debugging process. This is useful in pursuing various "what-if" scenarios as you test various hypotheses. The context menu allows you to add and delete variables from the watch list, go to the source for the variable, edit the current value of the data in the variable, set the variable value to NULL, and expand or collapse the index size of vector variables with a cell index >0.

41. Call Stack View – Get clear information pertaining the exact stack of calls at any given time.

As you might expect, the Runtime Call Stack repository displays the state of the programs that are in the current runtime task tree and the handler (aka logic unit) that called the new program. You can get to this repository by selecting Call Stack from the View menu. Naturally, the tasks are displayed in the order in which they were executed. In other words, the Main Program of the host application will be the first task in the list and the current task will be the last one listed.

The information in the Runtime Call Stack repository is displayed in five columns.
The indicator column simply shows the current line. The module column will display the component name, if any. The task column shows the task name and the handler column show the Handler (logic unit) in that task. Finally, the line column shows the line number of the current operation.

Keep in mind that you can also view the flow of the logic within your eDeveloper application from the Activity Monitor. A whole article could be dedicated to this. It is also important to note that while you can only debug one context at a time, you can switch between contexts while debugging. You can also now dynamically change what information gets entered into the log with the dynamic logging function. You can change the logging filter on the fly, and this does not require a change to the magic.ini file. Sweet.

All in all, the new eDeveloper debugger is a huge improvement and benefit to the developer that just makes your life easier. Here again, it is worth the price of admission.

In the past, eDeveloper was known as an IDE that generally produced programs with fewer bugs and less need for debugging. But the debugging procedures available were weak in the past. With eDeveloper V10, you now have both advantages: fewer bugs and a faster way to isolate them and test your hypotheses.

Express Yourself With eDeveloper V10

2006-10-19T20:21:00.000-07:00

Developers express themselves with logic, and that is what the expression editor is all about. eDeveloper has always been strong when it comes to creating the logic that comprises your business rules. Some have even gone so far as to call eDeveloper a business rules engine. Who besides Magic, you ask? Well, Gartner, for one.

There have been a few improvements worth noting, which Magic did in reasons 32 to 35 of the reasons to upgrade to eDeveloper V10. Let's take a look at each claim and see what's under the hood.

32. Quick Expressions – rapidly set expressions on spot by directly typing the expression syntax in the expression placeholder.

This quick editor provides a quick way to enter simple expressions without opening the Expression Editor. Sometimes when things get big and powerful, they get a little clunky. So this brings us back to the lightweight feeling of the early RAD days, so to speak. How, you ask? Well, when you park on a property in the Logic or Data View editors that require an expression (such as the Init or Cnd properties), you can press the equal sign (=), which opens a text box where you can enter an expression. Then you just enter your expression, no fuss, no muss.

You need to press ENTER to save your expression and close the Quick Expression Editor. Esc or F2 closes the Quick Expression Editor without saving the expression. Any other navigation action (such as arrows, tabbing, paging up or down, mouse clicks outside the edit box) saves the entered expression. So, in this reason to upgrade, less is more.

33. Auto Complete – Have eDeveloper automatically complete function names in the expression editor by requesting its automatic completion.

This is another one of those really nice improvements that is just designed as a timesaver. Function Auto Complete is available for functions and operators that begin with a letter. How does it work> Simply type the function or operator prefix and then press CTRL+Space. For example, if you enter ab, the function list opens and the cursor parks on the ABS () function.

When there is only one matching option, the text will be completed automatically.
If there is more than one matching option, a list box with the matching options is displayed. Click to select.

You won't find this Auto Completion Cheat Sheet in the manual. Now, if I could only find a way to auto complete my blog…

34. Expression Formatting – Freely format your expression and make them more readable.

White space? Wrapping? Multiple lines? Oh my.

35. Colored Display – Enjoy the enhanced expression editor full display highlighting each element of the expression in customizable colors.

To customize colors in the studio, access the Color Settings from the Options/Settings/Colors menu option and then choose the Studio tab to modify the colors used for any of the listed color uses.

Go ahead. Express Yourself as Madonna would say.

As for me, I'll have to wait till the next blog entry for that.

Auto Complete Cheat Sheet

2006-10-19T18:46:00.000-07:00

ABS
ACOS
AddDate
AddDateTime
AddTime
ANSI2OEM
AppName
ASCIIChr
ASCIIVal
ASIN
AStr
ATAN
Blb2File
Blob2Req
BlobFromBase64
BlobSize
BlobToBase64
BOM
BOY
BufGetAlpha
BufGetBit
BufGetBlob
BufGetDate
BufGetLog
BufGetNum
BufGetTime
BufGetUnicode
BufGetVariant
BufGetVector
BufSetAlpha
BufSetBit
BufSetBlob
BufSetDate
BufSetLog
BufSetNum
BufSetTime
BufSetUnicode
BufSetVariant
BufSetVector
CallDLL
CallDLLF
CallDLLS
CallJS
CallOBJ
CallProg
CallProgURL
CallURL
CaretPosGet
CASE
CDOW
CHeight
ChkDgt
Cipher
CLeft
CLeftMDI
ClickCX
ClickCY
ClickWX
ClickWY
ClientCertificateAdd
ClientCertificateDiscard
ClipAdd
ClipRead
ClipWrite
ClrCache
CMonth
CndRange
CodePage
COMError
COMHandleGet
COMHandleSet
COMObjCreate
COMObjRelease
COS
Counter
CRC
CTop
CTopMDI
CtrlGoto
CtrlHWND
CtxClose
CtxGetAllNames
CtxGetId
CtxGetName
CtxKill
CtxLstUse
CtxNum
CtxProg
CtxSetName
CtxSize
CtxStat
CurRow
CurrPosition
CWidth
DataViewToHTML
DataViewToText
DataViewToXML
DataViewVars
Date
Day
DbCache
DbCopy
DbDel
DbDiscnt
DbERR
DbExist
DbName
DbRecs
DbReload
DbRound
DbSize
DbViewRowIdx
DbViewSize
DbXmlMixedGet
DbXmlMixedSet
DDEBegin
DDEEnd
DDEGet
DDEPoke
DDERR
DDExec
DeCipher
Del
Delay
DifDateTime
DirDlg
DiscSrvr
DOW
DragSetCrsr
DragSetData
DropFormat
DropGetData
DropMouseX
DropMouseY
DStr
DVal
EditGet
EditSet
EJBCreate
EJBExplore
EncryptionError
EOF
EOM
EOP
EOY
ErrDatabaseName
ErrDbmsCode
ErrDbmsMessage
ErrMagicName
ErrPosition
ErrTableName
EvalStr
EvalStrInfo
EXP
ExpCalc
File2Blb
File2Ole
File2Req
FileCopy
FileDelete
FileDlg
FileExist
FileListGet
FileRename
FileSize
Fill
Fix
Flip
Flow
FlwMtr
FlwMtrVars
FormStateClear
GetComponentName
GetGUID
GetLang
GetParam
GroupAdd
HandledCtrl
HitZOrdr
Hour
HStr
HTTPGet
HTTPLastHeader
HTTPPost
HVal
Idle
IF
IN
INIGet
INIGetLn
INIPut
Ins
InStr
InTrans
IOCurr
IsComponent
IsDefault
IsFirstRecordCycle
ISNULL
JCall
JCallStatic
JCreate
JException
JExceptionOccurred
JExceptionText
JExplore
JGet
JGetStatic
JInstanceOf
JSet
JSetStatic
KbGet
KbPut
LastClicked
LastPark
LDAPError
LDAPGet
Left
Len
Level
LIKE
Line
LMChkIn
LMChkOut
LMUVStr
LMVStr
Lock
LOG
Logging
Logical
Logon
LoopCounter
Lower
LTrim
MailBoxSet
MailConnect
MailDisconnect
MailError
MailFileSave
MailLastRC
MailMsgBCC
MailMsgCC
MailMsgDate
MailMsgDel
MailMsgFile
MailMsgFiles
MailMsgFrom
MailMsgHeader
MailMsgId
MailMsgReplyTo
MailMsgSubj
MailMsgText
MailMsgTo
MailSend
MainDisplay
MainLevel
MarkedTextGet
MarkedTextSet
MarkText
MAX
MDate
Menu
MenuIdx
MID
MIN
Minute
MlsTrans
MMClear
MMCount
MMCurr
MMStop
MnuAdd
MnuCheck
MnuEnabl
MnuName
MnuRemove
MnuReset
MnuShow
Month
MStr
MTblGet
MTblSet
mTime
mTStr
mTVal
MVal
NDOW
NMonth
NULL
OEM2ANSI
OSEnvGet
OSEnvSet
Owner
Page
ParamsPack
ParamsUnPack
PPD
Prog
ProgIdx
ProjectDir
RAND
Range
Rep
RepStr
Right
RightAdd
Rights
Rollback
Round
RqCtxInf
RqCtxTrm
RqExe
RqHTTPHeader
RqLoad
RqQueDel
RqQueLst
RqQuePri
RqReqInf
RqReqLst
RqRtApp
RqRtApps
RqRtCtx
RqRtCtxs
RqRtInf
RqRts
RqRtTrm
RqRtTrmEx
RqStat
RqTrmTimeout
RTrim
RunMode
Second
SetBufCnvParam
SetContextFocus
SetCrsr
SetLang
SetParam
SetWindowFocus
SharedValGet
SharedValPack
SharedValSet
SharedValUnpack
SIN
SNMPNotify
SoundX
SplitterOffset
Stat
Str
StrBuild
StrToken
StrTokenCnt
StrTokenIdx
SubformExecMode
TAN
TDepth
Term
Text
THIS
Time
Translate
TranslateNR
TransMode
TreeLevel
TreeNodeGoto
TreeValue
Trim
TStr
TVal
UDF
UDFF
UDFS
UnicodeChr
UnicodeFromANSI
UnicodeToANSI
UnicodeVal
UnLock
Upper
User
UserAdd
UserDel
UTF8FromAnsi
UTF8ToAnsi
Val
VarAttr
VarCurr
VarCurrN
VarDbName
VariantAttr
VariantCreate
VariantGet
VariantGetVector
VariantType
VarIndex
VarInp
VarMod
VarName
VarPic
VarPrev
VarSet
VecCellAttr
VecGet
VecSet
VecSize
ViewMod
Visual
WinBox
WinHelp
WinHWND
WinMaximize
WinMinimize
WinRestore
WSConsumerAttachmentAdd
WSConsumerAttachmentGet
WSProviderAttachmentAdd
WSProviderAttachmentGet
WsSetIdentity
XMLBlobGet
XMLCnt
XMLDelete
XMLExist
XMLFind
XMLGet
XMLGetAlias
XMLGetEncoding
XMLInsert
XMLModify
XMLSetEncoding
XMLSetNS
XMLStr
XMLVal
XMLValidate
XMLValidationError
Year

ab
ac

adddatet
addt
an
ap
asciic
asciiv
asi
ast
at
blb
blob2
blobf
blobs
blobt
bom
boy
bufgeta
bufgetbi
bufgetbl
bufgetd
bufgetl
bufgetn
bufgett
bufgetu
bufgetva
bufgetve
bufseta
bufsetbi
bufsetbl
bufsetd
bufsetl
bufsetn
bufsett
bufsetu
bufsetva
bufsetve

calldllf
calldlls
callj
callo

callprogu
callu
car
cas
cd
che
chk
ci

cleftm
clickcx
clickcy
clickwx
clickwy
clientcertificatea
clientcertificated
clipa
clipr
clipw
clr
cm
cn
cod
come
comhandleg
comhandles
comobjc
comobjr
cos
cou
cr

ctopm
ctrlg
ctrlh
ctxc
ctxgeta
ctxgeti
ctxgetn
ctxk
ctxl
ctxn
ctxp
ctxse
ctxsi
ctxst
curro
currp
cw
dataviewtoh
dataviewtot
dataviewtox
dataviewv
date
day
dbca
dbco
dbde
dbdi
dber
dbex
dbn
dbrec
dbrel
dbro
dbs
dbviewr
dbviews
dbxmlmixedg
dbxmlmixeds
ddbe
ddee
ddeg
ddep
dder
ddex
dec

dela
dif
dir
dis
do
dragsetc
dragsetd
dropf
dropg
dropmousex
dropmousey
ds
dv
editg
edits
ejbc
ejbe
en
eof
eom
eop
eoy
errda
errdbmsc
errdbmsm
errm
errp
errt

evalstri

expc
file2b
file2o
file2r
filec
filede
filedl
filee
filel
filer
files
fill
fix
fli
flo

flwmtrv
fo
getc
getg
getl
getp
gr
ha
hi
ho
hs
httpg
httpl
httpp
hv
id
if

inigetl
inip

inst
int
io
isc
isd
isf
isn

jcalls
jc

jexceptiono
jexceptiont
jexp

jgets
ji

jsets
kbg
kbp
lastc
lastp
ldape
ldapg
lef
len
lev
lik
lin
lmchki
lmchko
lmu
lmv
loc

logg
logi
logo
loo
low
lt
mailb
mailc
maild
maile
mailf
maill
mailmsgb
mailmsgc
mailmsgda
mailmsgde

mailmsgfiles
mailmsgfr
mailmsgh
mailmsgi
mailmsgr
mailmsgs
mailmsgt
mailmsgt
mails
maind
mainl
markedtextg
markedtexts
markt
max
md

menul
mid

minu
ml
mmcl
mmco
mmcu
mms
mnua
mnuc
mnue
mnun
mnurem
mnures
mnus
mo
ms
mtblg
mtbls
mti
mts
mtv
mv
nd
nm
nu
oe
oseenvg
oseenvs
ow
pag
paramsp
paramsu
pp

progi
proj
rand
rang

reps

righta
rights
rol
rou
rqctxl
rqctxt
rqe
rqh
rql
rqqued
rqquel
rqquep
rqreqi
rqreql

rqrtapps

rqrtctxs
rqrti
rgrts

rqrttrme
rqs
rqt
rt
ru
sec
setb
setco
setcr
setl
setp
setw
sharedvalg
sharedvalp
sharedvals
sharedvalu
si
sn
so
sp
sta

strb

strtokenc
strtokeni
su
ta
td
ter
tex
th
ti

translaten
transm
treel
treen
treev
tri
ts
tv

udff
udfs
unicodec
unicodef
unicodet
unicodev
unl
up

usera
userd
utf8f
utf8t
val
vara

varcurrn
vard
varianta
variantc

variantgetv
variantt
varind
varinp
narm
varn
varp
varpr
vars
vecc
vecg
vecse
vecsi
vie
vis
winb
winhe
winhw
winma
winmi
winr
wsconsumerattachmenta
wsconsumerattachmentg
wsproviderattachmenta
wsproviderattachmentg
wss
xmlb
xmlc
xmld
xmle
xmlf

xmlgeta
xmlgete
xmli
xmlm
xmlsete
xmlsetn
xmlst

xmlvalidate
xmlvalidati
y

Is eDeveloper V10 Up to the Task?

2006-10-19T16:14:00.000-07:00

The newly refreshed developers toolkit in eDeveloper V10 presents a very fresh, clean development interface with an easy-to-use task editor and powerful expression editor. In our continuing series evaluating the 51 reasons to upgrade to eDeveloper V10, we will now focus on fourteen enhancements made to the task editor.

17. Task Layers – Easily distinguish between Data View, Logic, and Forms definitions using the clear separation between these three main pillars of a task.

I know some of you who are currently using eDeveloper are worried about replacing Record Main. But the migration process preserves your Record Main logic as is. You don't have to change things over unless you want to – and, you can do it incrementally (which is recommended). So once you get past the usual resistance to change that comes with any minor shift in a paradigm, you will actually grow to love the new layout of your application and its visibility in the three layers of the task editor: the Data View Editor, the Logic Editor, and the Form Editor.

The Data View Editor lets you define the task's data view interface as part of the task definition. The Data View elements include source tables, fields, and range. This window replaces the Record Main and DB Table repositories from previous eDeveloper versions.

You can enter Header Rows and Detail Rows in the Data View. The Header Row data view lets you specify the data source type, define links to the data source, and declare a data source open. The property sheet shows the properties for each of these options.

Then the detail row displays the Remark, Column (when a main source is selected), Virtual and Parameter. So it provides a fairly compact view that is human readable.

The Logic Editor is used to define the task’s logical segments. Keep in mind that the header line is basically a handler and the detail line is an operation. Again very clean and compact.

The Form Editor populates an initial entry automatically for each specific task. New entries are entered automatically for each subtask. Forms let the end-user interact with the application. They contain controls that either display data options or let the end-user enter data. The Form Editor displays the form’s frame and content. You can then easily design a form by assigning form properties and selecting controls and defining their properties.

So all in all, the three layer approach to Data, Logic and Presentation (Forms) is quite coherent and neat. I like it and hears a tip: you can press CTRL+TAB to move between the three editors (but you won't be able to leave the editor if you haven't created a valid entry.

18. Hierarchical Display – Easily navigate through the data-view and logic definitions of every task using the clear hierarchical display of the new task editor.

Part of the ease-of-use then comes from the hierarchical display of your logic. Use + to expand a hierarchy and – to collapse it. You can also use the "Go To Match" function which is pretty nifty and is explained here.

19. Task Properties – View and handle all properties of a task from a single task properties dialog.

Remember, the Task Properties dialog box is going to open automatically when you first zoom into a task and can be opened again later with CTRL+P while in the Task Editor. They've packed tons of power and control in here, so spend some time to re-familiarize yourself with all the available properties settings. They are organized into these tabs: General, Behavior, Interface, Data, Options and Advanced.

20. Relevant Only Information – For efficient reading of data-view and logic the task editor hides trivial information to maintain the information relevant and concise.

Rather than just listing all information in columns, the detailed information for a row is shown when you are parked on that row. In some cases this means a combo box type of display and in others it just means the column information is only displayed when selected. This allows you to navigate based on the important identifiers and then see the details when you want them. It really unclutters the data view and logic view allowing you to work more efficiently.

21. Range Settings – Obtain a full overview of all the Range criteria defined for the task's data-view from a single Range\Locate dialog.

The range window allows you to choose from a standard eDeveloper range, a SQL Where Clause and Range Expressions.

22. Default Logic Units – Customize your studio to automatically create basic logic units for every new task.

This is an .ini setting that can save you loads of time, so pay attention. This environment setting lets you automatically create a default schema, such as Task Prefix and Suffix, Record Prefix or Suffix.

Specifically, the values for this are set in the Magic.ini with the Command Line Name: AutoCreateTaskLogicUnits The available settings are:
No (which is the default), Task (Task Prefix and Suffix logic units are entered), Record (Record Prefix and Suffix logic units are entered), or Task and Record (Task Prefix and Suffix, and Record Prefix and Suffix logic units are entered). So this is a great way to jump start the logic units in the task editor.

23. Save Program – Instantly save changes of any program while editing the program.

Nice. Can you think of a time when you really, really wanted that? How about when the nasty Microsoft Updates dialog rears its ugly head to tell you your machine will reboot in 5 minutes? I hate that.

24. Developer Functions – Create your own functions to implement simple or complex procedures that involve composite resources. These function logic units will be available to you throughout the project as a built-in function.

I think the Magic International User Group should sponsor a contest for the most creative user defined function.

25. Flexible Control Handling – Handle controls by name and achieve greater flexibility by defining the control specific logic units before the form design, utilizing the same logic unit for a control in various forms and setting global control specific logic units.

One of the control's properties is its name. This enables a robust method to refer to controls in a Class 0 form, and to refer to them in functions. The LastClicked function will return the control name. Keep in mind that the Control Name property is limited to 30 characters and trailing blanks are not allowed. Duplicate control names are not allowed, so the Copy operation for controls in the Form Editor does not copy this property.

26. Variable Change – Set super responsive logic that can respond to any manual or automatic modification of any variable in a task.

The Variable Change logic unit lets you handle the change of a variable's value. And of course it is triggered whenever the variable value is changed. You can define a Variable Change logic unit for BLOBs, vectors, and ActiveXs, but not, incidentally, for OLEs. Don't ask why. I don't know. Some things just are, right?

27. Event Parameters – Improve handling and raising events by clearly declaring the parameters that are expected by the event.

In each task you can define events to be handled in your project whenever they occur. For example, you can define an event called ‘Add Customer’. Events have
Descriptions, Trigger Types, Triggers, Parameters, Force Exit and in a Main Program they have Public Name and Expose settings. There are four parameters available: Name, Model, Attribute, and Picture.

28. Post Record Update Force Level – Easily define event handlers to be executed only after all modifications of a record are updated within a transaction.

This makes it easier to ensure transactional integrity.

29. Direct Logic Access – Quickly access and create control level logic directly from any control defined in the form editor of a task.

Simply right click on the control and choose the option to create logic. Nice.

30. Tabbing order – Set the tabbing order of controls independently from the order of the fields in the data view definition. The value of each element can be set as fixed or dynamic.

Okay, you may begin the applause. Whenever Magic shows this, developers get very happy. It's the little things in life that make the difference, you know.

31. Subforms – Implement Parent-Child displays quickly and easily at the click of a button by simply declaring the participating child task on the parent's form using the new Subform control.

One thing to remember here is that a Subform control works only with an online program, which means that the Subform will not be active for a Main or Batch program.

With that in mind, you can use the Subform control to integrate a task form into the form of another task, while maintaining the subform‘s task data handling and record cycle activities independently from the parent task. But you cannot define a Control logic unit or an Event logic unit for a Subform control.

Nevertheless, a subform offers several advantages: 1) you can park on the line of a parent task and see the details from the subtask, for a one-to-many task relation, 2) eDeveloper automatically refreshes the Subform data view according to the parent task only when passing parameters, 3) eDeveloper retains your last position in the Subform data view when you leave and reenter., and 4) a tab cycle is provided for the Subform task.

Okay, well that is probably about as much Joy of eDeveloper V10 as you can process in one sitting. So we will blog on about eDeveloper V10 in our next entry, where we will evaluate the improvements to the expression editor.

Go! Team! Go!

2006-10-17T13:26:00.000-07:00

The next set of enhancements that Magic Software Enterprises talks about for eDeveloper V10 relate to Version Control, which is important for team development. Team development maintains concurrency among developers when working in a multi-developer environment. It allows you to be able to synchronize the developers work, keep track of changes made to the project, and be able to retrieve previous versions of the project. In eDeveloper V10, team development is made possible by the Version Control feature.

10. Version Control Facilitator of Your Choice - eDeveloper supports any version control product that implements the SCC API V1.01, such as Visual SourceSafe® and PVCS®. You can add to this list IBM Rational ClearCase and numerous other source code control programs compliant with .scc extensions. Please keep in mind that you will be able to access the version control features from within eDeveloper V10. Some aspects of the presentation may vary depending on which source code control system you are utilizing.

11. Out-Of-The-Box Version Control Software - You can immediately start working using a complementary version control software available as part of the eDeveloper installation. The included software is CVSNT. You can get more information at http://www.cvsnt.org including the online manual at http://www.cvsnt.org/manual/html Keep in mind, this is complimentary software. I don't know if the aphorism, "you get what you pay for applies," but there have been at least some reports that getting it to work with very large numbers of programs may be extremely resource intensive. So if you have an industrial-strength code base, you may want to utilize a third-party version control system.

12. Integrated Support - Utilize every version control activity directly from the eDeveloper Studio. This is a great convenience to be able to access the features of the enterprise version control system from within eDeveloper V10 itself. So even though you are working with a SCC tool in the background, it is fairly transparent after installation.

13. Rollback Support - Revert to a previous checked-in version of any atomic project module by rolling back to a selected version. In fact, you have a wide variety of features allowing you to: Check objects in and out, undo object checkout, get the latest version, get the latest project version, see the differences between versions, see a history of revisions, see a list of objects that have been checked out, add items to the version control server, exclude projects from version control, work offline with objects, and see a list of objects that are being worked with offline.

14. Revisions History - Easily view the history of all modifications done to every atomic project module. Not all SCC applications support the ability to see the revisions history. PVCS and Visual SourceSafe do provide that capability. It is from within the history, that you can click to see the differences.

15. Offline Development - You can keep on developing your version controlled projects even if you are disconnected from the version control server. When you do this, a backup copy is created. When you go back online, you then have the ability to compare the different versions.

16. Conflict Resolving - Get a clear and concise view of potential conflicts deriving from external or offline modifications. The list simply shows you which objects have been changed. However, by clicking on the object history button, you will be able to see the history and select to see differences between versions.

So there you have it: online and offline source code control that tracks revisions in a team development environment using industry standard SCC 1.01 compliant software. Due to the built-in efficiency of the eDeveloper paradigm, programming teams will tend to be smaller than with other IDEs for older language based coding paradigms such as C++, PHP5, or RPGIV. Nevertheless, the use of revision control methodologies is a great aid to team development in eDeveloper V10 by managing revisions and source code for each element of a project.

WYSIBTB: What You See Is Better Than Before

2006-10-16T12:41:00.000-07:00

OK, you've been asking about the new features in eDeveloper V10. So I'll start with the GUI improvements. Future posts will get into the nitty gritty of other aspects of the latest version.

1. Windows XP Style - Provide your end-users a standard-looking application that adheres to the Windows XP style. For most developers, this single enhancement is worth the price of admission to the whole eDeveloper V10 upgrade show. Let's face it, a well designed, fresh looking user interface is 90% of the battle in user satisfaction and user acceptance.

2. Shifting Table Columns - Enable your end user to freely re-order the columns of any table style display. This is a runtime feature and I love it. Just click, drag release and the column is moved. As a developer, you can disable it if you want to, but in most cases this is just grease. Love it.

3. Improved Tab Control - The new Tab control style enables you to set as many tabs as you need to be easily viewed using a vertical scroll or using multi line display. And let's not forget, customize the tab order. That's been a pretty highly requested feature and should make most magicians very happy.

4. Tab, Radio, and Check Box Icons - Enrich your application's UI by adding a relevant icon for every tab in a tab control, for every option in a radio button, and for check boxes. These new icons are clean and easy to use. The GUI editor is, well, really a GUI editor now. Cool.

5. Manageable Radio Buttons - Get better control on Radio Buttons option by freely laying out any Radio Button option. And this means you can put the radio button where you want it for best use of application white space, etc.

6. 3 States Check Box - Provide a proper visualization for NULL values of logical fields by using the 3 State support of the Check box control. The NULL value is the indeterminate state and it looks like a square filling the check box. Basically letting the user know that in this instant, the check box is not relevant to be checked or unchecked.

7. Box Style for Radio button and Check box - You can choose between common display of radio button options & check boxes and a button style of appearance. Some people prefer this box around the radio buttons and check boxes, I personally think it makes the user interface a bit too busy and less Web-like. But hey, one of these days the CEO is gonna say, "Can't you put a box around that?" and it will be nice to be able to do it in a second rather than writing some ActiveX or whatnot.

8. Automatic Wide Mode - Set edit controls to automatically open the Wide view screen whenever the end-user reaches the end of the edit control. Is anybody using this yet? If so, please comment.

9. Form State Persistency - Easily configure each screen to keep the end-user's customizable state. So we also end on a "wroth the price of admission" type feature. Do you remember what kind of machinations we used to have to go through to retain all this? Sure is easy now. Check. Done.

10. Report Generator - Does this qualify as a user interface improvement? Not sure. I'll save this one for another post. Blog you later.

Welcome to The Magic of eDeveloper

2006-10-16T12:09:00.000-07:00

Welcome to the Magic of eDeveloper, a blog for anyone who wants more information, more tutorials, more tips and more news related to Magic Software Enterprises eDeveloper V10 -- a great tool for building, compositing and integrating application software. Since there is a fair amount of material on prior versions of eDeveloper, I will of course focus on eDeveloper V10. Check here for comments on new features, tutorial information, and pretty much anything else that I can think of, borrow or umm, "steal with permission" from the R&D teams to make available to you here.

I hope that you find this both useful and enjoyable.