Comments (10)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 doctorhung commented Permalink

What is the difference between IBM EGL Community Edition and Eclipse EGL Web Developer Tools ? Will IBM continue to enhance IBM EGL Community Edition ? Or should we turn to Eclipse EGL Web Developer Tools.

2 will.smythe commented Permalink

EGL CE and Eclipse EGL Web Developer Tools ( EWDT) are very similar, functionally. Both are designed to support web app development (EGL-generated JavaScript for the front-end and EGL-generated Java for the back-end). EWDT, however, is open source, whereas CE was not (IBM did not provide the source for it). CE also does not include many of the features that were introduced in RBD version 8 (e.g. grid layout). EWDT can also be extended much more easily by other vendors than CE. I *definitely* recommend you use EWDT over CE at this point. In the near future, we will discontinue CE and point people to EWDT ...

3 Thorbjoern commented Permalink

One of the selling points of EGL seen from the Cobol and RPG world is that it can generate that kind of code too. Could you add a note or two on how these fit together? <div>&nbsp;</div> My first thought would be that we could blurr the current great divide between the Java world and the ILE world with this, but I'd like some pointers. Thanks

4 will.smythe commented Permalink

IBM did not contribute the EGL COBOL generator to Eclipse because it was not something we viewed as widely applicable as Java/JavaScript (to the general development community). It will continue just shipping in the IBM tools. Of course, plans can change. The good news (for a lot of reasons): because the EGL compiler and generator framework is open source, anybody (with the right skills) could build an RPG or COBOL generator. <div>&nbsp;</div> In the very near future (possibly 0.8), support for calling RPG programs will be added to the Eclipse EWDT. This will enable i shops to call existing RPG logic from an EGL service or web UI. Of course, if you already have RPG (or COBOL) logic exposed as an XML or JSON service, you can drive this with the tools in version 0.7 already. <br />

5 JeanMik commented Permalink

what do you mean by "existing RPG logic"? Existing RPG programs are persistent and a controller is needed to manage the persistence. For example if I have a subfile which calls a form etc...How to get Web interfaces from EGL? The BIG problem is that 80% of business applications are persistent. The IBM i can manage multitenancy and persistence natively, you just need to compile the programs. I had a conversation on that subject with Steve Will and Aaron Bartell: <br /> http://ibmsystemsmag.blogs.com/you_and_i/2011/11/four-quarters-of-growth-for-ibm-i.html#comments

6 will.smythe commented Permalink

The assumption is that the RPG logic has been reworked/rearchtected such that it can be invoked programatically (either statefully or stateless). The logic is wrapped in a web service and then invoked from an EGL RUI (or whatever) front-end. I am not suggesting this is an easy process, but the end result is a much more flexible architecture that better enables you for the future, whatever front-end technology you decide to use ..

7 JeanMik commented Permalink

Aaron is speaking about EGL specifications embeded into our display files *DSPF in order to be tightly integreted with existing RPG programs. <br /> You know, IBM i clients are leaving the platform i one after the other because they don't have native GUI interfaces for stateful 5250 programs. So the clients say that IBM don't care of the life cycle of its OS. <br /> I thought that Rational was working for existing clients to make modern interfaces by adapting the existing EGL designer for our needs. <br /> So you have any project to help us directly? We will have to extract and rewrite into pieces etc... or leave the platform i? Is that the future for us?

8 JeanMik commented Permalink

Just one more thing. <br /> Excuse me but I need to understand: Do you think that 200 000 companies all over the word using IBM i are wrong and you are right? Do you know that your clients leaving the IBM i are the more profitable companies? They are wrong to want native HTML interfaces for persistent business applications and you are right? Where are the Websphere/Java and EGL customers? As I know some big multi-os ISVs? and you are working for free for them because you think that 20 000 faithful IBM i companies are wrong? Do I understand well?

9 will.smythe commented Permalink

"Do you think that 200 000 companies all over the word using IBM i are wrong and you are right? " ... answer: no. I am describing the approach we have for modernizing applications and an approach that, in general, is viewed as providing the most flexibility going forward. An approach like the one you are describing (i.e. a native gateway that extends 5250 applications to the web) is something we have talked about building, but have not because of other priorities like the open project (which, by the way, would be a great place for the i community to help us build a solution like this). So, I think it's a good requirement, and one that you should consider opening as an RFE (against RDi SOA or RBD), or as an enhancement against EDT.

10 JeanMik commented Permalink

« or an enhancement against EDT » I suppose EDT stands for Emerging Display Technology or something like that ? (I am French). <br /> Well… about Emerging Technology, you have several architechtures : <br /> Fist step : Client/Server <br /> Second step : Thin Client with Virtual Desktop Infrastructure. In that way you need a middleware over like VMWARE, CITRIX etc… <br /> Third step : Thin Client with Google App Engine Over Linux in order to manage multitenancy in which one instance of an application, running on a remote server, serves many client organizations (also known as tenants). With multitenancy, data base and programs are shared with multi users. <br /> As I know, Will Smythe, IBM i operating system is the only one OS in the world able to mange NATIVELY mutitenancy. I say NATIVELY because you just have to compile a program in a library (schema) and the operating system does the job for you : programs and database are automatically shared without doing anything. <br /> In other words : the S/38 was build thirty years ago for the Cloud Computing as multitenancy is THE condition of Cloud Computing as 80% of business applications are persistent. <br /> I am trying to convince you, Will Smythe, to invest in that space because native HTML5 interfaces are still missing for persistent applications. <br /> When you say « or an enhancement against EDT » you are right if you think that the IBM i operating system beats Google App Engine which is a software over Linux because we are NATIVELY mutitenant. <br /> Just thoughts <br />