How to Save 2+ Stacks as standaloner?

[inselfan]

Holá everybody,

I have one Stack which is "calling" another stack by
go stack "XYZ.rev"

My question is now, how to include both stacks (NOT SubStacks) into one standalone?

thanks for answering, best regards and -of course- enjoy 2009

Horst

[gyroscope]

Hi Horst, if I understand you correctly, then your main stack (app) calls up another main stack (app) and you want to "tie" them together as a standalone.

Personally, I can't see the point: if you are creating multiple apps which "talk" to each other, surely it's better to keep them separate for the user, so that one or the other can be used, or the first can be used which can then launch the second self-contained app? Applications are self-contained units, independant of each other. Also, if you are going down the commercial route, you can sell two apps, with the benefit to the user that if they buy both, one can launch the other.

If you want two separate apps i.e two well-defined separate sets of functions within the same app, and especially if you want more "communication" between them than one opening the other, then making the second app a substack of the main stack is really no problem; when called up by the main stack, it'll look and behave correctly, and only you (and other Revvers) will know that all the controls of the second app live on a stack called a subStack.

Hope I haven't misunderstood you...

[inselfan]

Holá Gyroscope,

yes, you understand correctly :)

The reason why I go this way is, that the app is tooo big, which makes dramatic speed-problems. But I don`t want semarate *.exe-files so I'm looking for a way to put multiple stacks into one Standalone. I know it works, did it long time ago but forgot how :(

If you have a better idea how to put the speed (caling cards) up, please let me know. Waiting 1 minute + to get a simple card is a horror :(

thanks for answering

Horst

[gyroscope]

Waiting 1 minute + to get a simple card is a horror

I'm sure one of the more experienced Revvers will correct me if I'm wrong: that's not right, waiting 1 min + for a card to open...(and you sure have patience waiting!)

There's got to be something that's causing that behaviour, of course, but which is not usual Rev behaviour. Even if you have 10 substacks with 100 cards each, my guess is that "go card 47 of stack 93" would take not much more time (if any) than "go card 2 of stack 1" unless you are asking for a lot of data to be inputted via the on openCard or preOpenCard script. But then that'll be an incredible amount of data to delay the card opening for a whole minute or more...

Or there's different very long scripts for each on on preOpenCard script but even then I can't see how there would be any more delay than a couple of seconds at most.

[Obleo]

inselfan

In the standalone builder under Stacks. There the add Stack Files.

Do not forget to script this in the main stack before using:

start using stack "my stack name"


If the project is currently set up with substacks, they can be move into individual stack files. Under the advanced Options in the standalone builder / stacks card.


---------------------------------------
gyroscope

There a point to breaking up substacks to individual stacks, It has to do with memory allocation. Individual stack files load into memory as you need them. A stack with sub stacks not moved into individual stack files load into memory all at once. Depending what your project does this can be very useful depending on the end users system configuration.

Many end users have barebones systems. I do not know anyone that opens just one program at a time on a CPU. There is a number of apps open at once. Then even the OS is drawing memory with all the daemons and agents running in the background also drawing memory.

[Obleo]

If your waiting a minute to load a card ??? You may want to reference files that are loaded into a stack / card, over embedding them into the stack. That can cut down the overall memory and speed processing issues. I am unsure if that is the problem here. (But kind of sounds like it, me.)

Also there are many development tools available for monitoring memory usage of your program and what process is hogging (or leaking) the system. It can greatly help fix bottleneck slow performance areas in the program.

Just a tip, maybe that could help speed up performance.

[inselfan]

Holá from the old to the new world, which means, holá Obleo :)

Thanks for answering :)

I understand and did:
In the standalone builder under Stacks. There the add Stack Files.

But what do you mean with:
Do not forget to script this in the main stack before using:
start using stack "my stack name"
Do you mean:
on openstack
...
start using stack "X"
start using stack "Y"
start using stack "Z"
... and so on all the Stacks?

I also do not understand:
If the project is currently set up with substacks, they can be move into individual stack files. Under the advanced Options in the standalone builder / stacks card.

This is maybe a problem of translating into my language :(

Pease try to feed (explain) me

General:
the problem with the speed showing cards/stacks is extrem! if I try to open some of them with the Application Browser it can take 5 (!) and more minutes... not a joke, but also not a SONY :) yes, there is much to do inside the pre- and opencard, but that has to be done...

Now, with the many different Staks it works fine and as expected in the Revolution-mode (or how ever it's called) I want now to do the same with the standalone.

Once again, thanks for a new-year-first-aid

Horst

[Obleo]

Holá from the old to the new world, which means, holá Obleo

Thanks for answering

I understand and did:
In the standalone builder under Stacks. There the add Stack Files.

But what do you mean with:
Do not forget to script this in the main stack before using:
start using stack "my stack name"
Do you mean:
on openstack
...
start using stack "X"
start using stack "Y"
start using stack "Z"
... and so on all the Stacks?

Yes that was what I was referring to. I was not total understanding if these where library stacks you where referring to.

I also do not understand:
If the project is currently set up with substacks, they can be move into individual stack files. Under the advanced Options in the standalone builder / stacks card.

This is maybe a problem of translating into my language

Pease try to feed (explain) me

Just incase your revolution project was created using sub-stacks and you wanted to break them up into individual stacks for the standalone build. I did not want to assume anything so I pointed out that you can also do this from the standalone builder just incase this was your question.

That yes you can take a main stack with substacks and make them all into indivual stack files.

I am never sure if I actually explain things correctly in the techie talk lingo, so I try to cover all the bases with my reply hoping it will help in someway.


- ob