I can't think of a better title for this, but since I hope this becomes an ongoing series of posts, I want to make sure I stick a number in there. Maybe I should have made this one Number 0, because it's going to be sort of an introductory post, but that's okay.
This blog series will be based on things I find as I'm writing RUI applications. It will range from little things like tips for formatting (using a class to right-adjust grid columns) to major RUI topics such as how to implement services in a modular architecture (the answer is Delegates, but the devil is in the details).
Because of the book, I've already got a list of topics on hand. In fact, as I write the blog posts you'll get more glimpses into the book writing process. But I can give you a few quick previews. For example, I'm becoming pretty proficient at formatting Grids. This is important stuff for those of us in the i community; the Grid is the replacement for the subfile and it's crucial to being able to build applications quickly.
Another thing that comes into play is the fact that all the HTML for a RUI page is generated at runtime. Because of that, it's difficult to see the actual HTML which in turn makes it hard to diagnose CSS issues. I've figured out a way around that. I hope to make a generalized widget available soon, but I will at the very least post some example code. The trick is outerHTML...
Anyway, I'll be back posting more. Let me know if there are areas you need addressed.
The developerWorks Connections Platform is now in read-only mode and content is only available for viewing. No new wiki pages, posts, or messages may be added. Please see our FAQ for more information. The developerWorks Connections platform will officially shut down on March 31, 2020 and content will no longer be available. More details available on our FAQ. (Read in Japanese.)
From archive: September 2008 X
JoePluta 100000KMX3 Tags:  eglcafe i egl application_modernization business_logic rui_tips rui 7,485 Views
JoePluta 100000KMX3 Tags:  i application_modernization business_logic egl rdi eglcafe rpg rbd rui rws 1 Comment 10,335 Views
No, seriously, what I mean is this is the next generation of posts on the RUI topic. A month ago I wrote that some exciting stuff was in the works, and now I can tell you about it. This will actually be a short blog entry - I just want to let you know what's coming.
Briefly, I'm writing a book. The book is going to be about using RDi SOA to build EGL Rich UI applications with the i. EGL Rich UI is the "formal" term for RUI, and if you haven't played with it yet, you should get yourself down to the alphaWorks site and get a copy (and yes I know the page says EGL Rich Web Support, but I have it on good authority that EGL Rich UI is the official name).
The book will show how to build a Rich UI interface using EGL and then connect that to a business logic back end written in RPG. Every step of the way will be written and debugged using Rational tooling.
And those of you who read my blog will get an inside look into the process of writing a book. It may inspire some of you to try your own hand at it. Those of you with clearer heads will run screaming...
Anyway, that's the short version. This ought to be an interesting project...[Read More]
Green IT is all about the IT community being socially responsible with regards to their infrastructure and the applications contained therein.
So you might ask? Is this really important in this pressurized world of hi expectations, and more and more rapid changing business models and faster deliveries.
I believe it is. Green IT can and should be one of the guiding tenants of organizations. We, as both IT professionals and members of a broader global community need to act responsibly with regards to the environment. And just as good. By acting responsibly towards the environment we also can help our organizations meet their goals more effectively.
You might wonder if the business of software really uses environmental resources? Many of us would view that software already limits the environmental impact of business. For example, by teleconferencing instead of travel which uses fossil fuels as an example.
But there is much more we can do
How can we all participate in Green IT?. I'll start with a few examples below:
1. Understand how the hardware your applications run on consume power. The box consumption itself, but also the consumption of the supporting infrastructure around that box and the power usage for that support. For example, the space that the hardware takes up, air conditioning, power the people who support that box use, power the underlying applications and backups, restores, monitoring etc., uses.
2. Build more information into your applications. For example, if more information can be presented with "same" or less file IO's, and other usage of the CPU, we save.
3. Use efficient operating systems and languages. When the running code does more efficent and less processing, the application is more energy efficient. For example, look to use compiled / tuned languages and highly effecient transaction processors. Look for those that do more with less code - both code you write and executables you run.
4. Make performance analysis a critical milestone in your delivery cycles.
5. Reuse code and processing when you can. Less duplication equates to less resources.
6. Make Green a a part of your corporate and IT vision statements. Also make Green a part of requirements review, application design, and maintenance change reviews.
7. Evaluate collaboration possibilities - and software - to improve efficiencies. Less travel, conference calls, etc. can not only help us save but also can make us more productive in focusing us on what we really do. Delivering code that can add profit and cut costs..
8. In the end, write more applications that at least in part can save more of the resources the rest of your companies use. This ultimately might be the biggest impact you can make.
At the end of the day, we all win.