Whether the generation HTML-pages "on fly" with watching of changes in properties of form's controls (TEXT, _LIST_ etc.) is possible?

]

Ok Dmitry I'll have a go !

If you mean can you generate HTML pages automatically based upon the changing values of specific controls in an OI form then the answer is YES. The CHANGED or CHAR event for example will be fired as the text is entered into an edit control. You can then pick this up and do anything i.e. write out HTML page, fire Excel, load VB ! whatever you like.

If you are refering to data entered onto an existing HTML form by a users web browser then OI will only be notified when a request is passed through the OICGI i.e. went the user clicks the 'submit' button on the HTML form.

Hope this helps.

Tony.

Thax, Tony.

]If you are refering to data entered onto an existing HTML form by a ]users web browser then OI will only be notified when a request is ]passed through the OICGI i.e. went the user clicks the 'submit' ]button on the HTML form.

That is OI in the WEB-apps processes only event SUBMIT?

Ok, Whereas to be in such situation - I adjust properties LIST for LISTBOX/COMBOBOX in event CREATE for the form. This form is compiled by the OI HTML Publisher. How I can load this form? FORMLOAD does not work properly - tags do not vary.

Dmitry,

What you do in the CREATE handler will not translate to the web version of the form.

But what kind of data have you got in the list? What is it you want to display in your list or combo box? A list of possible values for a field? A list of legal values or can the user also key in her own value (combo)? Many or few values? The solution might depend on your answer to these and other questions.

(I warn you I might not be equipped to answer your questions. I've worked some time with a web interface to my app, but I suppose from a different angle - I have no data entry forms because the users are only allowed to query and browse data, I use forms just for queries, I use hand-coded and programatically generated html instead of HTML Publisher, etc.)

- Oystein -

Thanx, Oystein.

Some conclusions.

There are no tools(components/functions) for adjustment of HTML-forms registered in repository. And the creation of the web-application based on the existing application is not so simple as written in advertising. And I should itself write the program for mapping the forms to web-clients.

It so?

Dmitry,

…not so simple as written in advertising…

It's difficult to transfer one's app to the web. The web is so different from a normal GUI on a PC. I have no plans whatsoever to port my own app (a cataloguing system for museums and collections of cultural and social history) to the web. An interface for querying and browsing databases - yes. Rebuild all the functionality of the app on the web - no!

With OI and HTML Publisher it is easy to get something on the air very quickly. But then it can take some effort to get the rest to work.

But at least I think it's been very interesting, and mostly fun, to develop a web interface to an OI database!

- Oystein -

Here's another option for you.

I attended the "Rev it up" seminar yesterday in which Kurt Baker previewed the planned release of the jRev beta product at the end of this month. I was very impressed. He showed a demo of a Golf Shop Equiptment sales web site written with jRev tied to an Oracle database. This data entry and retrieval is "On the Fly." You can see this at www.livewater.com.

The jRev form design builder is similar but different from OI and I do not believe there is a utility to directly convert your existing OI forms to the jRev forms but I could be wrong. If I am correct you will have to redo the forms in jRev. What is really neat is that EditTables can be constructed in jRev WHICH IS NOT POSSIBLE IN HTML. (There is an XLM facility that is currently NOT supported by OI or jRev that does allow establishing an EditTable object.)

One problem is that the October 30th release will not support Linear Hashed (i.e. OI) files. The code to do this has already been written and tested and can be downloaded from the Revelation Web Site but for some reason it is not being included officially in the prerelease of jRev. I implication here is that you can make it work with some help. Another problem is that jRev does not support BASIC+ language and will not for probably 1.5 years. At that time OI and jRev will merge into one product.

We at Sprezz have working Edit Tables in HTML/JavaScript complete with check boxes and drop downs. We've got a whole host of other tools which make AREV to the Web a lot less painful too. I suspect thatthe complaint is that the HTML generator for OiWins isn't exactly comprehensive.

However I agree that jRev does look like a cool product.

amcauley@sprezzatura.com

Sprezzatura Group

World Leaders in all things RevSoft

Edit Tables are also possible in IE DHTML with/without IE scriptlets - We've just done this for a client and it works great ( more functionality than an OI Edit Table too )!

Watch out for some examples to hit our web-site soon!

Carl Pates

Sprezzatura Group

www.sprezzatura.com

BTW could you give us an URL for this demo at the LiveWater site? i can't seem to find it.

amcauley@sprezzatura.com

Sprezzatura Group

World Leaders in all things RevSoft

Well, how about that! They don't have a link on the main page. At any rate the demo is at: www.livewater.com/livewater

I'm glad you enjoyed the "Rev It Up" seminar. Indeed, we have not published a link to the LiveWater demo from the web site for the following reasons:

1. There has been no commercialization work done on the demo (such as providing documentation, etc.). As such, just looking at the sample application will not tell you what was generated by LiveWater and what the value was that LiveWater delivered.

2. There has been no stress testing on the web server. We are still in the process of that piece of the QA work.

While we greatly appreciate (and encourage) your enthusiasm, please bear with us while we do the work necessary to providing you with a robust and valuable demo. If you are anxious to experience the demo now, please contact Revelation and we will schedule a one-on-one walkthrough.

We appreciate your understanding and restraint.

CT Savell,

The jRev form design builder is similar but different from OI …

There is a Graphical Layout tool (an early revision) in jRev. We are still working on some long-term design issues regarding both graphical components (such as how to support all LayoutManager implementations) and non-graphical components that could be graphically designed using this tool. At any rate, the next preview will contain this tool.

… I do not believe there is a utility to directly convert your existing OI forms to the jRev forms but I could be wrong. If I am correct you will have to redo the forms in jRev.

At this point, there are no OpenInsight-to-jRev conversion tools. We will not being these tools until we have something solid and commercial to convert to. We are very concerned with and focused on getting the right set of base technologies and features into the product first, and having an extremely high level of quality, and thus having a stable base product to "map" the OpenInsight features onto. At that point, we will be able to make much better use of the jRev technologies (such as inheritance) to facilitate conversions. For example, on the topic of windows, we could create a JFrame (a Java Swing window) that has the functionality of the Semantic Logic Layer and Form I/O modules (stored procedures in OpenInsight that make OpenInsight forms act the way they do) so that any window converted from OpenInsight would automatically inherit that functionality, just like event-chaining provides in OpenInsight.

What is really neat is that EditTables can be constructed in jRev …

I guess Kurt gave the drag-and-drop-the-columns demo .

One problem is that the October 30th release will not support Linear Hashed (i.e. OI) files. The code to do this has already been written and tested and can be downloaded from the Revelation Web Site but for some reason it is not being included officially in the prerelease of jRev. I implication here is that you can make it work with some help.

The Component Data Model (jRev's manner of accessing data) is not complete yet, but it is designed in such a way that different types of data sources, such as Linear Hash, could be efficiently supported. Our first implementation of the Data Model is for JDBC, which is a standard API for accessing databases in Java.

Another problem is that jRev does not support BASIC+ language and will not for probably 1.5 years. At that time OI and jRev will merge into one product.

One of the best aspects of the jRev architecture is its modularity. For example, script compilers (such as BASIC+) can be added without modifying the toolset. The first compiler we created was a Java script (scripting using the Java language) compiler. The next one planned will be a JavaScript script compiler. It will probably share a code-base with the planned BASIC+ compiler, since the languages are relatively similar.

Similarly, tools and components that we create to facilitate OpenInsight conversions can be "plugged into" jRev, all without changing the underlying tools and technologies.

None of this is accidental … we knew that there were a lot of companies that would need customizable Java tools, and many of these companies have their own Windows (and other) systems to convert, often with their own proprietary scripting languages or behavior. These companies can "OEM" the base product, and extend and tailor it to their needs, much like several large packaged application developers did with Advanced Revelation and OpenInsight.

Cameron Purdy

Revelation Software

Cameron,

First of all, I really liked what I saw and do appreciate the care you all are taking to make this a quality product. As for BASIC+ versus java script I understand the decision process and don't disagree at all. I just wish things would happen sooner as I am sure you do as well.

To your comment: "There is a Graphical Layout tool (an early revision) in jRev. We are still working on some long-term design issues regarding both graphical components (such as how to support all LayoutManager implementations) and non-graphical components that could be graphically designed using this tool. At any rate, the next preview will contain this tool."

I assume this is tool that Kurt used in the demo. Correct? And this is the tool that will be included in the October 30th release?

CT Savell,

I assume this is tool that Kurt used in the demo. Correct? And this is the tool that will be included in the October 30th release?

If he showed jRev with a "form design" tool, then yes, that is the tool, and yes, I expect that tool to be part of the next preview, and yes (even though you did not ask , as with all of the tools, it was built completely in jRev.

Cameron Purdy

Revelation Software

View this thread on the forum...