Code of Our Lives

Building a Menu Bar with Formspider

2012-01-27T13:03:00.004+02:00

This tutorial explains how to build and use menu bar in a Formspider application.

Web Session Management in PL/SQL with Formspider

2012-01-06T18:30:00.001+02:00

This tutorial explains how to benefit from web session variables with PL/SQL in a Formspider application. You will discover how to define, store and destroy session variables. Click here to continue reading.

Is Foursqaure in trouble?

2012-01-04T18:20:00.003+02:00

When Forrester CEO George Colony, thrashed Foursquare as nonsense, Fred Wilson posted his talk on his web site and commented that “it shows he doesn’t use the product and has no idea what they are about and where they are headed”, when I asked him about his take on Mr. Colony’s view.

However, Mr. Colony might have a point, although he was unnecessarily harsh making it. After several months spending time on Foursquare, I sadly realized that I can get better value out of other web sites.

There were three ways that I hoped to get value.

Click here to continue reading the article.

Amazing Charts with PL/SQL

2011-12-22T18:18:00.002+02:00

Formspider, the Web 2.0 for PL/SQL developers, enables you to create gorgeous charts declaratively. Creating charts has never been easier for PL/SQL developers. Moreover, Formspider charts are implemented 100% in JavaScript. There is no Flash at all. So the charts you create with Formspider, work perfectly on mobile devices that do not support Flash, as well. Make sure you check out the demo and the tutorial.

Managing Screen Navigation in Formspider Applications

2011-12-19T14:47:00.003+02:00

Click here to find out how we manage screen navigation in Formspider, the Web 2.0 framework for PL/SQL developers.

Data Types and Format Masks in Formspider

2011-12-13T12:15:00.002+02:00

Formspider enables PL/SQL Developers build Web 2.0 applications just as easily as they were creating Forms applications. Click here to find out how we handle data types and format masks in Formspider.

Formspider surpasses 300 Installations

2011-11-23T15:00:00.001+02:00

Our product Formspider, the Web 2.0 framework for Oracle PL/SQL developers has surpassed 300 installations worldwide. Read more about Formspider here.

Apple’s strategy leaked in a video…from 1988

2011-11-04T09:30:00.000+02:00

I cannot help but share this video made by Apple…in 1988. The vision was always there. Now they are executing.

Siri; The Artificial Intelligence Revolution has begun

2011-10-17T07:59:00.001+02:00

In her interview with Fred Wilson, Carlota Perez, who inspired him greatly in forming his investment strategy, talks about five technological revolutions:

1) The Industrial Revolution (Machines and Canals)
2) Railways and The Steam Engine
3) Heavy Engineering using Cheap Steal
4) The Automobile, The Assembly Line and Mass Production of Electrical Appliances
5) The Information Revolution

On October 4 2011, with the introduction of Siri in iPhone 4S, a new technological revolution has begun.

Continue reading at Yalim's Lodge

Steve Jobs’ best is yet to come

2011-10-07T12:58:00.002+02:00

Did you really think that he left the stage without one more thing?

On Wearing a Suit

2011-09-15T16:40:00.002+02:00

Here are five reasons why it might be a good idea wearing a suit to a business meeting with people you’ve never met before. Continue reading at Yalim's Lodge

Don't Require a Credit Card for Trials

2011-09-12T13:44:00.001+02:00

I ran into a question at StackExchange. It came from a founder of a B2B Internet startup, who is tired of following up with unqualified leads. He believes that the low barrier free trial his company is offering is the culprit for their low quality. As a solution, he is contemplating asking for credit card information before the beginning of the free trial and automatically charging his users when the trial ends. He is asking the SE community if this is a good idea.

Hmmm…Let me be really clear:

Only porn sites should do this.

Continue reading at Yalim's Lodge

The Star Trek Secret to Happiness

2011-09-05T07:33:00.002+02:00

For people who glance at blog posts for 10 seconds and move on to the next one: The Star Trek secret to happiness in life, is to never let McCoy to the bridge.

What the heck does that mean? Interested? Good. Read on.

Steve Jobs lighted our way

2011-08-25T22:57:00.000+02:00

My father lives as if it is 1975.

He refuses to interact with a computer.

To put things in perspective, every member of the family owns at least one computer and presented the advantages of owning one to him repeatedly. He never even touched a computer and seemed genuinely offended by the presence of one.

Continue reading the story here.

How we build Web 2.0 apps with PL/SQL

2011-08-24T19:57:00.000+02:00

PL/SQL has never run on client machines and never will. This unchangeable, indisputable fact that seems like the most obvious disadvantage of PL/SQL is in an ironic way its biggest advantage. This very fact is the reason Oracle Forms was a platform independent application development framework.

Continue reading here.

Free advice to the remaining PC Makers

2011-08-20T09:39:00.000+02:00

I’ve prepared a list of the shortcomings of PC-Laptops (for lack of a better term) that made me jump ship and buy a MacBook Air. The items in the list will seem as clear as daylight to you. That’s because you are a consumer not an executive in the PC business. Continue reading at Yalim's Lodge

-1 for Google +1 Part 2

2011-08-20T09:37:00.000+02:00

My blog post -1 for Google +1, in which I argued that no one is using +1 because there is no benefit a user gets from +1’ing anything, generated a lot of comments here at this blog and at Hacker News. I would like to thank everyone who contributed. The comments really helped me to form a better opinion. In this post, I want to do a round up of the discussion we had. It seems to me that it all boils down to these three points:

Continue reading at Yalim's Lodge

-1 for Google +1

2011-08-20T09:35:00.000+02:00

While I was browsing through news stories at MSNBC.com, I could not help but notice the vast difference between the number of people recommended a story on Facebook and +1’ed it on Google. Here are some examples:...

Continue reading at Yalim's Lodge

Seedcamp Event Guidelines for Newbies

2011-07-18T15:49:00.001+02:00

Last week I participated as a mentor at Seedcamp Ljubljana. For those who don’t know’ Seedcamp is an early stage micro seed investment fund and mentoring programme. They organize daily events across Europe where mentors and startups get together.

This was my first time at a Seedcamp event or any event regarding startups. I am literally blown away. The buzz around the place is incredible. Everybody is candid, supportive and unpretentious. They are willing to help and probably more importantly receive help.

The other incredible thing is that none of this buzz and excitement is about money. Yes, Seedcamp wants to invest in companies and eventually make money off of these investments but overall at a Seedcamp event, money takes a back seat to the culture of collaboration. The power of community, collaboration and willingness to receive help are the lessons I am taking home with me from Seedcamp Ljubljana.

Over the next few days, I will write about the startups I’ve met and my two cents that I shared with them.

Having my feedback in a written form will help the startups. During the day, they were swamped with feedback often not in a very organized manner. We were jumping from topic to topic and I caught myself changing positions in the middle of arguments, all expected because we were in the middle of a 45 minute brainstorming bonanza. They were taking notes but given the tempo of
the day the notes might be difficult to comprehend in the aftermath.

This exercise will help me as well. I want to stay in touch with the startups I connected with. However, most of the thinking I have done with them is bound to be forgotten in the coming weeks. If I write it all down, the blog posts will quickly remind me the discussions we had. I am also curious if my two cents will be any good to the people I talked to. In the future, I want to compare the current state of the startups with the blog posts I wrote and have a good laugh with them.

Before I start talking about each startup, there is some generic feedback I would like to give to Seedcamp, mentors and the startups. So here we go…

To Seedcamp

Inform the mentors
The PDF that Seedcamp sent prior to the event was great. It had every information I needed to get to know the startups. However, I wish they told me which startups I am to work with in advance so that I could focus on them more. With 25 startups attending, it was difficult for me to do due diligence on all of them to hold a 45 minute discussion. Had I known the five I will talk to, I could focus on them and be better prepared.

It is a small issue but, I’d rather a web page instead of a PDF. Web pages are more mobile friendly and the links on a PDF are not clickable unless specifically made so. I was mostly reading the PDF on an iPad or an iPhone and going back and forth between pages and the browser made working with the information more difficult.

Mentor the mentors
I think Seedcamp can be a little more active in showing mentors how to mentor the right way. Most of the ones I talked to, including me, were doing this the first time. Maybe some guidelines about how the 45 minute meeting should be structured can be helpful. A video or a set of videos of high quality mentoring sessions can’t hurt either.
Additionally, if I’d knew who the other two mentors in my group were in advance, I could contact them prior to the event and we could get organized a little better. As it turned out, I was extremely lucky and ended up with two great mentors who I really enjoyed spending the day with but if we had a little heads up, I am sure we as a group could use it.

To Mentors

Do your homework
The startups are there to receive feedback, not to explain what they do for 45 minutes. I think mentors should do their homework and understand the business as well as they can prior to the meeting. I think it is completely OK and valuable to have the startups explain what they do, but the meeting should not turn into an interview about what they do. Every mentor simply must go over the booklet Seedcamp provids and visit the web sites of the startups. I understand that this is a little overwhelming right now because there are 25 of them and a mentor does not know which startups she will talk to but do the best you can.

Avoid Feature Suggestion Fest
The startups are also not there to hear your feature ideas. They probably thought them all. Members of the startups are usually software developers and given that they have been thinking about the problem longer than you have, it is very likely that they thought of the very cool feature you just came up with. In other words, don’t just suggest a feature because you think it will make you look cool. Please remember that we are talking about two people shops here and their time is very valuable. Working on features that don’t bring in customers will hurt them. Since most of the entrepreneurs are software developers they are already more eager about feature development than they should. If you really want to recommend that they should implement a feature, try to tie it to a business case and explain why you think it is important from a business perspective.

Skip the “Atta Boy!”. Play the devils advocate
Try not to turn the meeting to a feel good event. Having a positive attitude and wishing them well is certainly the correct behavior. However, patronizing them, giving them false sense of hope and not telling them what you think will eventually hurt them. Most startups fail. The entrepreneurs you meet at Seedcamp will most likely fail. It is better if they hear the cold reality about their errors now than after spending a year of their lives. If you have legitimate worries about their work, tell them openly and honestly. This doesn’t mean you have to be rude or mean to them. If you can’t tell someone how concerned you are about their well being without starting a fight, maybe you should not be mentoring. You will be surprised how well the entrepreneurs receive constructive criticism. It is what they are there for. Play the devils advocate. Openly tell them that you are doing so. Try to corner them, force them to come up with numbers, facts and justifications. If they are well prepared, they will easily tackle all of your challenges. If they are not, they will be grateful to go through this experience now in front of you as opposed to in front of someone they are asking a million dollars from. Don’t think they will hate you. On the contrary, they will thank you. The entrepreneur I worried about the most turned out to be the guy I hanged out with the most after the event was over.

Introduce yourself
Probably the best thing we did as a mentor group was to introduce ourselves to the entrepreneurs. This way the entrepreneurs have an idea of who you are and what kind of help they can expect from you. This also helps you build credibility in their eyes and you stop being the jackass who just entered the room and started talking shit about their beloved company.

Take notes during the pitches
At the beginning of the day each startup gives a five minute presentation to introduce itself. Mentors should take notes during these presentations. Some of the questions I had were answered during the pitches and I had some new questions. Write them down so that you can bring them up during your meeting with the startup. Otherwise you will just forget them.

Talk to everyone
Just because a startup wasn’t in your schedule, doesn’t mean that you should ignore them. Be proactive, go and talk to them. Don’t be shy. You are there to give your two cents and the more you give the better. I pulled every entrepreneur I can get my hands on to a corner and talked to them about their business. Some of the best conversations I held were during these side meetings.

To Startups

Make your software more accessible to mentors
I made an effort to use the software of the 25 startups before I showed up at the event. Unfortunately, most of the startups were in private beta. I had to ask for an invite. Since the event was only a day away, I wasn’t able to access most of the sites. Maybe it is my fault that I waited until the last day. However, I feel like the startups could be more proactive and send invitations to mentors. I think Seedcamp can actively participate in this and make sure that every mentor has access to the software the startup has developed prior to the event. The few sites that I was able to use, helped me a lot in forming an opinion.

No video during the pitch
Some startups showed a one or two minute video during their pitch. The presenter stopped talking, pointed us to the screen and together we all watched a video. Don’t ever do this. This is a terrible way of pitching. We are there to listen to you, to engage with you, to get amazed by you, to get interested in you. We are not there to watch a video.

Talk to everyone
Similar to mentors, you should also make a conscious effort to talk to everyone. Go over the bio of the mentors. Start with the ones you think are most interesting. Don’t be shy. Go even talk to other startups. Share experiences.

To Everyone

Follow Up
Don’t let it all end with the event. Mentors should continue to work with the startups they are most connected with. Try their software and provide feedback, explore business opportunities, help spread the word, be available to be approached by the entrepreneurs and encourage them to do so. Startups should pick the mentors who they think can provide the best input in the long run and stick with them. They should find ways to engage the mentors with their product and company. Simply bring in the mentors to solve actual business problems you have, have meetings, discussion or whatever. If you are doing it by the book, you need an advisory board, remember?

Provide feedback
Just because an event is over, it shouldn’t be all forgotten and back to business as usual again. Take the time, provide written feedback to all the participants. The discussions in the meetings will be forgotten but the comments you make in written form will stay. This way they will be more beneficial to past, current and future participants of Seedcamp events.

Enjoy it
Take it all seriously, prepare well but don’t be uptight, defensive or cocky. Everyone is there with the best intentions. The meetings are only half of the story. The day continues until very late at night. The line between the entrepreneurs and mentors blur after the meetings are over. In the evening, entrepreneurs were giving me trash about my company. It was awesome. My final advice is that enjoy the event while you can, seize the moment because it only lasts for one day.

Yalim K. Gerger

Let’s meet at Oracle OpenWorld

2011-06-10T08:37:00.003+02:00

This year, Formspider team applied to present at the Oracle OpenWorld via Oracle Mix. We submitted the presentation “Forms Modernization: The PL/SQL Way”.

We believe Oracle Forms modernization is an important topic for many Oracle customers. We would like to share our experience and knowledge in how organizations can protect their Forms and PL/SQL investment. If you are interested in seeing this presentation at Oracle OpenWorld please vote for it on the Oracle Suggest-A-Session page.

Admittedly, the process to vote is a little tedious. If you don’t have an Oracle account, you have to sign up and then vote for at least three presentations in order for your vote to be valid. However, we promise the presentation will be totally worth your effort. :-)

Vote for Forms Modernization: The PL/SQL Way now.

JavaScript vs. JavaFX

2011-05-27T23:22:00.000+02:00

We built the XML Editor for the Formspider IDE in Java, because the original Formspider IDE was a Java Application. When we were preparing the Formspider Online IDE for the Web, we also had to move the XML Editor to the Web. In one of the brilliant moments of my career I told the team “Hey, we have a working editor in Java. Why don’t we convert it to JavaFX and be done with it?” This should be simple right? Right…After months of work, we finally got the editor working in JavaFX. The fact that we converted from Java to JavaFX, did not help as much as we hoped it would.

We went live with the Formspider Online IDE and started observing user behavior. Something was not right. People were signing up but not really doing anything. A quick investigation revealed that we were having problems with the XML Editor. It was failing for more than 50% of our users. Some people didn’t have Java on their machines, some had the open SDK that did not support JavaFX and some had problems we could not figure out.

Formspider IDE was not a joyride for the lucky few who was able to run the editor either. On average, a user had to wait about two minutes before the IDE was ready for input. The 1.5 MB jar was downloaded quickly enough but it took ages for the computer to install the jar and getting it ready to run. The security alert that kept popping up was also very annoying from the user’s perspective.The state we were in with the Online IDE was clearly unacceptable.

JavaScript came to the rescue. We were actually smart enough to sponsor a coding contest for a JavaScript editor while we were working on the JavaFX one. The team of Bilal Gültekin and Bahattin Tozyılmaz were the winners. In the picture below you see Bilal receiving their bounty, a teddy bear filled with $2600 dollars. We are also looking forward to host both Bilal and Bahattin as our interns this summer.

After the contest was over, Öskan took over the code base for the XML Editor in JavaScript and prepared it for production use. After several weeks of work, the editor was ready for beta testing. However, the problem was so severe that even a partially working editor written in JavaScript was better than a thoroughly tested editor written in JavaFX. So we skipped the beta pretty quickly. We were already annoying pretty much every user, how much worse could we really get?

After a few quick iterations, we were incredibly happy with the results. Now our new XML Editor written entirely in JavaScript loads instantly and runs for our every user. Most importantly, our users started to engage with the Online IDE. I see them creating panels, text fields and windows everyday.

If you used the Formspider Online IDE before and you did not have a pleasant experience at all, I apologize and kindly invite you to give it another try. If this is going to be your first time with the Online IDE, nevermind… It all works just fine.

Hoşgeldin

2011-04-20T13:14:00.001+02:00

Bir stüdyoda kaydettiğim ilk bestem.

Şarkıyı aşağıdaki linkten indirebilirsiniz.

http://goo.gl/OSmXq

Eğer şarkıyı beğendiyseniz, paylaşırsanız çok sevinirim. Yok eğer beğenmediyseniz, yine de paylaşın. Belki arkadaşlarınızın zevki sizinkinden farklıdır.

Hoşgeldin

gerçek mi cesaret mi
yalnızlık mı esaret mi
kemiğe dayandığında
mutsuzluk mu ihanet mi

çocuk mu çocukluk mu
oyun mu huysuzluk mu
kemiğe dayandığında
ölüm mü yoksulluk mu

gönlümü buldum
orda bir taht kurdum
onu oturttum

kalbimde değilsin
kalbime en yakın yerdesin
hoşgeldin

korkmak mı sığınak mı
yağmur mu sağanak mı
kemiğe dayandığında
kırmak mı kırılmak mı

yollar mı duvarlar mı
sırlar mı anılar mı
kemiğe dayandığında
değişmek mi inkar mı

hassas mıyım yoksa hasta mı
sarhoş muyum yoksa bir hoş mu
elime dayandığında
başıboş musun, başın boş mu?

Söz-Müzik: Yalım K. Gerger
Düzenleme: Hasan Çakırsoy

Bana kendimi hep evimde hissettiren Stüdyo Smart’a ve Serdar Kılıç’a sonsuz teşekkürlerle.

My First StackExchange Question

2011-04-18T23:05:00.001+02:00

I have always wondered why people bother giving advice to other companies. Now I know…

I have a product proposal for StackExchange. Let me describe the business problem first:

My company has recently launched a product. Obviously, we needed a place to answer user questions. We hate old fashioned forums as much as anybody on this site. So, we wanted to integrate a Q&A site to our domain. We tried a few SO clones, picked one and after some effort it was all up and running.

Our product is new and has only a handful users. However, it is a software product that is used by programmers. Every question about our product is a perfect fit for SO. However, it is not mainstream enough, so nobody would ever ask a question about it on SO.

In short, my business problem is that my company ended up, installing and maintaining its own Q&A site. We don’t want to do that. This is not our line of business. We don’t care. We just want to take something and plug it in. We want somebody else do all the hard work for us.

So, this got me thinking…We are not the only company in this situation. There are many small business, start-ups with products out there that fit into one of the SE sites be it software, photography or cooking. Wouldn’t it be nice if SE provided a widget/plugin or whatever, that I could just add to my site and have my own Q&A site for my product? The questions would be tagged with my product name. All SE users could easily login. It would just be a mini-SE site running on the small business web site. The questions would certainly enrich the related SE site, since they would be on topic. Any abuse or low quality input, can also be moderated just like any other stuff on the SE network. Small businesses would not have to hassle with installing and maintaining open source alternatives. Both the start-ups and SE community users would benefit from the exposure on the SE sites. Start-ups could reach the passionate users in the area they are in and the SE users would be informed about new products about a topic they are deeply interested in.

I think this product/feature would make the Internet a better place. My guess is that SE is already working on something like this.

Now below this line I am full of my self:

If this doesn’t lend me an offer for SE Product Director, nothing will.

You may follow the conversation on StackOverflow Meta from the URL below:

http://meta.stackoverflow.com/questions/87627/mini-se-plugin-for-small-products

Yalım K. Gerger

Caching Dynamically Generated Scripts

2011-03-23T21:05:00.000+02:00

If static JavaScript or CSS files are served from the application server, we take it for granted that they are going to be cached by the browsers. However, dynamically generated content (Javascript and CSS in particular) could also be cached as if it is static and sent from the server only when it is changed. Nevertheless, application servers provide no support for this at all. So, the responsibility rests on the shoulders of the server-side code which generates dynamic content.

I looked all over the Internet but was unable to find a solution, so I wrote my own code. It's written for a Java Servlet but the same logic can be applied to other languages too. The servlet below sends a piece of JavaScript to the client that it builds dynamically and adds the necessary headers to the response so that the browser can cache it.

Here's the code that gets the job done:

public class TestServlet extends HttpServlet {
    private static final String CONTENT_TYPE = "application/x-javascript";

    public void init(ServletConfig config) throws ServletException {
        super.init(config);
    }

    public void doGet(HttpServletRequest request, 
                      HttpServletResponse response) throws ServletException, IOException {
        
        Calendar c1 = Calendar.getInstance();
        c1.clear();
        c1.set(2011,2,22,13,12);
        long lastModifiedDate = c1.getTimeInMillis();
        
        response.setContentType(CONTENT_TYPE);
        response.addDateHeader("Last-Modified",lastModifiedDate);
        
        PrintWriter out = response.getWriter();
    
        long lastFetchedDate = request.getDateHeader("If-Modified-Since");
        boolean notModified = false;
        if (lastFetchedDate>-1){
            if (lastModifiedDate<=lastFetchedDate){
                response.setStatus(HttpServletResponse.SC_NOT_MODIFIED);
                notModified = true;
            }
        }
        if (!notModified){
            System.out.println("test");
            out.println("var test = {};");
            out.println("test['a']='b';");
            out.println("alert(test['a']);");
        }
        
    }

    public void doPost(HttpServletRequest request, 
                       HttpServletResponse response) throws ServletException, IOException {
        doGet(request, response);
    }
}

To keep the example simple, I used a static date for the last modified date.

Here is how you can include this servlet in an html document as a javascript file:

<html>
    <head>
    <script type="text/javascript" src="http://localhost/test/testservlet"></script>
    </head>
    <body>
    </body>
</html>

When you run this from an application server, the first time you access the page you will see the message "test" in application server console, meaning that the servlet did the necessary work and generated the JavaScript code. The next time you access the page, the JavaScript will already be cached by the browser. Therefore, even the alert still pops up when the page is accessed, you will not the see message "test" in the server console. Since the dynamically created JavaScript is already cached in the browser and the headers were set up correctly, the server did not bother to generate the code all over again and responded much faster just like it would if the JavaScript was actually in a static file.

M. Serdar Biçer

True Cross Browser Web Applications

2011-03-22T13:45:00.002+02:00

Having a truly cross browser web application is like being truly happy. The moment you get there, someone is going to bring you up to date and ruin everything. And like happiness, you will never attain it if you chase it. And like happiness, it is a byproduct of devoting yourself to something that you are passionate about.

Developers tend to believe that the moment they start using a JavaScript library that works across browsers, they are immune to the problem. Nothing can be further from the truth. If you use such a library, this only means that the code inside the library is compatible with many different browsers. It does not automatically follow that any new line of code you will write for your application is going to work the same way across browsers. This is a hugely misunderstood concept.

With your first line of Javascript or HTML you are in cross browser hell. Let me repeat this. With your first line of Javascript or HTML you are in cross browser hell. Virtually in every project browser compatibility of the application is the responsibility of the development team. Ensuring that web applications work in all the major browser brands and their versions is an important, time consuming and difficult task. Most teams just give up and let it all flap in the breeze. Even the smallest attempt for browser compatibility crashes and burns with the first update to Firefox or Chrome and the team is back to square one again. I’ve seen IT departments that force their users to use one particular browser to access their applications. This is ridiculous and yet it is happening every day. How can it not happen? There are many nuances that needs to be mastered for true browser compatibility. Development teams are not focused on technical details of browsers and their implementations of JavaScript and HTML. They are focused on implementing business rules in code and delivering applications and rightfully so. That’s what they are supposed to do. They should not be punished because a few industry giants could not get their act together and created the worst standards in the most important platform ever created: the web browser. It is a classic example but I’ve got to repeat it here at the risk of being banal. Can you imagine that some TV sets working with some shows but not with others? Can you imagine watching House M.D. on a Sony but having to switch to a Samsung to watch Entourage?

In Formspider, browser compatibility is our responsibility. You can focus on what you are passionate about; building the best health care system, HR software or public finance application. Browser compatibility will be the byproduct of using Formspider. We take care of the platform problems. This is our job. It is what we do everyday.

Formspider applications are truly happy. It is not just the Formspider JavaScript library that works across browsers. Every application that you develop with Formspider works across browsers by default, because you only code in PL/SQL. Formspider has a very simple intuitive XML notation that helps you design your screens. It eliminates the need to be an HTML/DOM expert. We test Formspider with every major browser out there so that you can focus on your business problems knowing that once you code them all in PL/SQL, they will work on any platform.

Platform independence was one of the greatest benefits of Oracle Forms. The principle is up and alive in Formspider.

Yalım K. Gerger