LiveCode Forums.

Didn't see anything about this anywhere else- guessed on this forum.
I put up a simple little program I use at some registrations for some wrestling events (for the weighins particularly). No need to discuss the functionality but I pull up various cards from various substacks throughout the program. The on-rev version would not pop up those cards. I tried IE and Firefox and neither told me it was holding up a pop-up or anything like that.
Any thoughts from anyone?
The closest thing I saw anywhere here was someone suggesting something about setting the default stack to the file but I couldn't get that to do anything either.

I don't think currently on-rev supports sub-stacks per se.
There is the "include" keyword to include other irev files.

Also you might find more information at the on-rev forums.
http://forums.on-rev.com/

Now if you mean serving up stacks and substacks as a revlet, well
that's a completely different issue.

-Shawn

sfitzjava wrote:I don't think currently on-rev supports sub-stacks per se.
There is the "include" keyword to include other irev files.

Also you might find more information at the on-rev forums.
http://forums.on-rev.com/

Now if you mean serving up stacks and substacks as a revlet, well
that's a completely different issue.

-Shawn

No, I meant normal substacks.
Didn't realize there was a separate forum for on-rev.

Thanks.

Hi gimpeltf,

maybe you are mixing "Revlets" (stacks in a browser) with "on-rev" ( a server side scripting engine)?

Klaus wrote:Hi gimpeltf,

maybe you are mixing "Revlets" (stacks in a browser) with "on-rev" ( a server side scripting engine)?

I don't follow.
I have no experience here (this forum or using on-rev) so I'll just try to better explain what I did.

I had a small program that included a main stack and a series of substacks that works quite well on my pc. For the heck of it, I thought I'd see how it would work on-line since we got our on-rev last spring and hadn't used it for this purpose yet.
I recompiled using web. I uploaded the revlet and the test.html and tried it. The initial page worked, but any of the buttons geared towards pulling up cards on substacks did not work. The other gentleman here suggests that currently on-rev doesn't support substacks. If that's the case, I'll wait. I assume that will be forthcoming. I suppose I could also regear the program to multiple cards in the same stack and try that.

The subject of the different web technologies coming out of the RunRev stable has just been dealt with on the use- list (thread starts here : http://lists.runrev.com/pipermail/use-r ... 30412.html)
Some of the best explanations I've copied here:

Jacqueline Landman Gay wrote:There are two new web technologies. One is client-based and the other is
server-based.

1. On-rev (irev): This is the server-based technology. It allows you to
write web pages (called "irev" pages) using RevTalk. This works exactly
like PHP, and you can mix HTML and irev scripts together in your web
page code. The scripts are interpreted by software on the server, which
then sends the final HTML output to the user's browser. You need an
account with On-Rev right now if you want to use this, because only the
RR server has the software to interpret irev scripting. Eventually RR
plans to release the software for installation on any server, but that
isn't ready yet.

2. Revlets: This is the client-based technology. The user downloads a
browser plug-in which allows stacks to run inside a browser window, much
like Flash or QT does. Because the plug-in is on the user's hard drive,
revlets can run from anywhere. You can place your revlet on any server,
just like you can store QT movies on any server. The plug-in downloads
the file and does all the work inside the browser.

--
Jacqueline Landman Gay

Sarah Reichelt wrote:iRev allows you to script dynamic web pages that just work without
your viewers having to download or install any plugins.
You can think of it as a replacement for PHP & CGI scripts, but not
JavaScript as it is server-side scripting, not client-side.
You can change the page that is sent to a browser as it is requested,
but you cannot change a page in response to a user interaction without
using JavaScript too.

Have a look at the examples on my On-Rev page to see some of the
things you can do <http://www.troz.net/onrev/>.
My whole site is now built using On-Rev scripting which takes text
files listing stacks or revlets or web links and builds it all as
requested.

Basically, revlets allow you to put stacks on a web page. iRev
scripting allows you to build dynamic web pages without a plugin.

Cheers,
Sarah

Having an account for on-Rev means that you are given web hosting space which is enabled with the server-side scripting interpreter that you can use to make dynamic pages with irev syntax you are familiar with. You don't have to make your pages that way - the on-Rev hosting account can be used any way you like - with php available (although it's more than a tad tricky to mix irev and php on the same page, but as a separate page, no bother at all), or just plain html, with or without any other technologies like flash, javascript, etc.
So you can use an on-Rev account to host a revlet just as you would host a revlet anywhere on another host.
The thing about revlets is that they do not allow for multiple window spaces. There was mention of "native windows" to come at some point in the revlet roadmap but I'm not sure how feasible that is, or how close if so. You should be able to switch to a substack within a revlet, but not one that opens in its own window id, I believe. Only the ask/answer dialogs have been dealt with to open over the browser layer at present, I believe.

HTH
SparkOut

SparkOut wrote:The subject of the different web technologies coming out of the RunRev stable has just been dealt with on the use- list (thread starts here : http://lists.runrev.com/pipermail/use-r ... 30412.html)
Some of the best explanations I've copied here:

Jacqueline Landman Gay wrote:There are two new web technologies. One is client-based and the other is
server-based.

1. On-rev (irev): This is the server-based technology. It allows you to
write web pages (called "irev" pages) using RevTalk. This works exactly
like PHP, and you can mix HTML and irev scripts together in your web
page code. The scripts are interpreted by software on the server, which
then sends the final HTML output to the user's browser. You need an
account with On-Rev right now if you want to use this, because only the
RR server has the software to interpret irev scripting. Eventually RR
plans to release the software for installation on any server, but that
isn't ready yet.

2. Revlets: This is the client-based technology. The user downloads a
browser plug-in which allows stacks to run inside a browser window, much
like Flash or QT does. Because the plug-in is on the user's hard drive,
revlets can run from anywhere. You can place your revlet on any server,
just like you can store QT movies on any server. The plug-in downloads
the file and does all the work inside the browser.

--
Jacqueline Landman Gay

Sarah Reichelt wrote:iRev allows you to script dynamic web pages that just work without
your viewers having to download or install any plugins.
You can think of it as a replacement for PHP & CGI scripts, but not
JavaScript as it is server-side scripting, not client-side.
You can change the page that is sent to a browser as it is requested,
but you cannot change a page in response to a user interaction without
using JavaScript too.

Have a look at the examples on my On-Rev page to see some of the
things you can do <http://www.troz.net/onrev/>.
My whole site is now built using On-Rev scripting which takes text
files listing stacks or revlets or web links and builds it all as
requested.

Basically, revlets allow you to put stacks on a web page. iRev
scripting allows you to build dynamic web pages without a plugin.

Cheers,
Sarah

Having an account for on-Rev means that you are given web hosting space which is enabled with the server-side scripting interpreter that you can use to make dynamic pages with irev syntax you are familiar with. You don't have to make your pages that way - the on-Rev hosting account can be used any way you like - with php available (although it's more than a tad tricky to mix irev and php on the same page, but as a separate page, no bother at all), or just plain html, with or without any other technologies like flash, javascript, etc.
So you can use an on-Rev account to host a revlet just as you would host a revlet anywhere on another host.
The thing about revlets is that they do not allow for multiple window spaces. There was mention of "native windows" to come at some point in the revlet roadmap but I'm not sure how feasible that is, or how close if so. You should be able to switch to a substack within a revlet, but not one that opens in its own window id, I believe. Only the ask/answer dialogs have been dealt with to open over the browser layer at present, I believe.

HTH
SparkOut

Thanks.
I hadn't realized they had server side also or that the revlets could be hosted anywhere. (Not that I anticipate hosting them elsewhere) I just went to the Save As Standalone command and did what it said (clicking on web). Didn't see anything there about server side. I'll keep looking.
I have begun to move the cards from substacks into the main stack and things work just fine.

The ability to open new native windows from a revlet was unfortunately not ready for the release time. But rather than moving everything from your substacks to the mainstack, you can also use the go to stack in window format to display the substack in the revlet space. HTH,

Jan Schenkel.

Janschenkel wrote:The ability to open new native windows from a revlet was unfortunately not ready for the release time. But rather than moving everything from your substacks to the mainstack, you can also use the go to stack in window format to display the substack in the revlet space.

Code: Select all

on mouseUp
  go card 2 of stack "MySubstack" in the window of this stack
end mouseUp

HTH,

Jan Schenkel.

Thanks Jan.

In The Window!

There is one substack I'd like to have separate so I can show it in a separate monitor eventually. The rest are fine as cards in the main stack.

If I can just check my understanding here- I gather it is not possible to use the “paletteâ€

There is an official list of known limitatons at the Troubleshooting section of the revMedia website - but this is not exhaustive. Better to keep an eye out for revlet-specific issues in the Quality Control Center.
The advantage of the decoupling between the editor and the web browser plug-in, is that the runrev crew can quickly update the revweb plug-in when needed, squishing runtime bugs faster.

It is indeed not possible to open separate native windows (palettes, dialogs, toplevel windows,...) from a revlet. But you can have two revlets on the same webpage, sharing a single revlet environment - look at the Sketch sample on the revMedia site.
Combining that with the go in the window of this stack command, should get you by until the runrev team can add support for native windows.

Jan Schenkel.

Thanks so much for pointing me in the right direction, on several points. I see the value in decoupling the editor from the web browser plug-in ... ideally, the plug-in will have the same capabilities as currently in desktop stacks and there will be no differences to document, but this will take a little time. In fact, what I still find surprising is how much already works as a revlet, and the excellent performance. The sites you mentioned are a good way to keep up with developments. A side-thought about revTalk- clearly, because it is close to natural language, it is easily learnt, hence people can become productive very quickly. Equally important, I think, is that it is also highly communicable, enabling forums such as this to act effectively as a “knowledge multiplierâ€