Re: stack design with externals?
Hallo Tiemo, I hope I understood your question: I have the experience, that 1) the runrev standalone always expects the Externals in the subfolder of the defaultfolder, which is normaly the folder where the standalone is located and this location is expected by other stacks also which start from the same standalone (not relational to the location of any rev-stack), and 2) you can set the External location of any stack in the externals of stack xyz, if you use to change the defaultfolder during the program: 1) if you make a standalone teachit.exe with all the externals these are located in the subfolder /External: teachit.exe ssleay32.dll libeay32.dll External/revbrowser.dll External/rev... External/database_drivers/dbmysql.dll ... The standalone can go to other rev stacks even on webserver etc. but my experience is that the externals always will be found in the subdir /External. You can use in the standalone.exe go stack teachA.rev in window (the windowID of this stack) AND/OR go stack URL http://myserver/stack.rev in a new window if these stacks need externals and they are present in the subfolder of the stack where the standalone is located, it works. = Therefore I once have prepared a start.exe with all externals I have, which in the openstack script automatically loads an stack with the same name, but rev at the end. I rename this start.exe as project1.exe, put project1.rev in the same folder with the dlls and the External folder and it works. I only make a new standalone, if a new runrev version is published and I need it. In the normal case I just copy my start.exe as a loader to the actual project.rev. And they always find the revBrowser External ... therefore I guess this also the case with Valentina. 2) doku external Examples: set the externals of stack Apps to field Executables Use the externals property to use the externals in the specified files. Value: The externals of a stack reports a list of file paths, one per line. Comments: Each line of the externals specifies the name and location of a file containing external commands and external functions. If you specify a name but not a location, the file is assumed to be in the defaultFolder. Regards und freundliche Grüße, Franz Franz Böhmisch [EMAIL PROTECTED] http://www.animabit.de GF Animabit Multimedia Software GmbH Am Sonnenhang 22 D-94136 Thyrnau Tel +49 (0)8501-8538 Fax +49 (0)8501-8537 ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
AW: stack design with externals?
Hello Franz, very comprehensive explanation! I will follow that Thank you Tiemo -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:use-revolution- [EMAIL PROTECTED] Im Auftrag von [EMAIL PROTECTED] Gesendet: Dienstag, 21. Oktober 2008 13:32 An: use-revolution@lists.runrev.com Betreff: Re: stack design with externals? Hallo Tiemo, I hope I understood your question: I have the experience, that 1) the runrev standalone always expects the Externals in the subfolder of the defaultfolder, which is normaly the folder where the standalone is located and this location is expected by other stacks also which start from the same standalone (not relational to the location of any rev-stack), and 2) you can set the External location of any stack in the externals of stack xyz, if you use to change the defaultfolder during the program: 1) if you make a standalone teachit.exe with all the externals these are located in the subfolder /External: teachit.exe ssleay32.dll libeay32.dll External/revbrowser.dll External/rev... External/database_drivers/dbmysql.dll ... The standalone can go to other rev stacks even on webserver etc. but my experience is that the externals always will be found in the subdir /External. You can use in the standalone.exe go stack teachA.rev in window (the windowID of this stack) AND/OR go stack URL http://myserver/stack.rev in a new window if these stacks need externals and they are present in the subfolder of the stack where the standalone is located, it works. = Therefore I once have prepared a start.exe with all externals I have, which in the openstack script automatically loads an stack with the same name, but rev at the end. I rename this start.exe as project1.exe, put project1.rev in the same folder with the dlls and the External folder and it works. I only make a new standalone, if a new runrev version is published and I need it. In the normal case I just copy my start.exe as a loader to the actual project.rev. And they always find the revBrowser External ... therefore I guess this also the case with Valentina. 2) doku external Examples: set the externals of stack Apps to field Executables Use the externals property to use the externals in the specified files. Value: The externals of a stack reports a list of file paths, one per line. Comments: Each line of the externals specifies the name and location of a file containing external commands and external functions. If you specify a name but not a location, the file is assumed to be in the defaultFolder. Regards und freundliche Grüße, Franz Franz Böhmisch [EMAIL PROTECTED] http://www.animabit.de GF Animabit Multimedia Software GmbH Am Sonnenhang 22 D-94136 Thyrnau Tel +49 (0)8501-8538 Fax +49 (0)8501-8537 ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
AW: stack design with externals?
Hello, Hmm no answers - did I asked the wrong questions or was my explanation too complicated? The main question is, where to assign externals when using a splash stack, which becomes the executable (but doesn't needs the externals) and a main stack which stays a .rev and needs the externals. Is it enough just to put them into the properties\externals of the called main stack (rev-file) and I don't need the binding functionality for the externals, when building the standalone of the splash stack? Any hint welcome :) Tiemo -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:use-revolution- [EMAIL PROTECTED] Im Auftrag von Tiemo Hollmann TB Gesendet: Freitag, 17. Oktober 2008 09:11 An: 'How to use Revolution' Betreff: stack design with externals? Hello, just making my first project with externals (valentina in this case), I started the project with a main stack, which carries most of the functionality and some substacks. I added the valentina externals to the main stack, build the standalone of my main stack and everything works so far. If I now would change the design of my project with building a separate splash stack (app/exe), which calls after start my main stack file (rev), this splash stack would get the standalone app and my main stack is only a standard stack file, where I can't assign anymore any externals. In this scenario I had to assign the externals to the splash stack, because that's the one I build the standalone of. But probably my main stack couldn't find the externals anymore, after the splash stack is closed and the main stack is open. (didn't tested it yet). And anyway I would have wanted the splash stack as small as possible and not with bound externals. Now I am puzzled. Is my approach with a separate splash stack not possible with externals and a splash stack can only be the main stack in a standalone and my current main stack has to get a substack? Or am I on the wrong lane at all and don't have to care where to assign the externals and runrev will find them anyway? Thanks for enlightening Tiemo ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: AW: stack design with externals?
Hi Tiemo, The easiest way probably is to build your standalone with all needed externals. As far as I know, the externals stay available after the splash stack that is used to build the standalone closes. If in doubt, set the destroyStack property of the splash stack to false. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering http://economy-x-talk.com http://www.salery.biz Dutch forum: http://runrev.info/rrforum/ Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html for more info. On 20 okt 2008, at 09:08, Tiemo Hollmann TB wrote: Hello, Hmm no answers - did I asked the wrong questions or was my explanation too complicated? The main question is, where to assign externals when using a splash stack, which becomes the executable (but doesn't needs the externals) and a main stack which stays a .rev and needs the externals. Is it enough just to put them into the properties\externals of the called main stack (rev-file) and I don't need the binding functionality for the externals, when building the standalone of the splash stack? Any hint welcome :) Tiemo ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
AW: AW: stack design with externals?
Hi Mark, I didn't though about not to use destroyStack, good idea Thanks Tiemo -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:use-revolution- [EMAIL PROTECTED] Im Auftrag von Mark Schonewille Gesendet: Montag, 20. Oktober 2008 09:15 An: How to use Revolution Betreff: Re: AW: stack design with externals? Hi Tiemo, The easiest way probably is to build your standalone with all needed externals. As far as I know, the externals stay available after the splash stack that is used to build the standalone closes. If in doubt, set the destroyStack property of the splash stack to false. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering http://economy-x-talk.com http://www.salery.biz Dutch forum: http://runrev.info/rrforum/ Benefit from our inexpensive hosting services. See http://economy-x- talk.com/server.html for more info. On 20 okt 2008, at 09:08, Tiemo Hollmann TB wrote: Hello, Hmm no answers - did I asked the wrong questions or was my explanation too complicated? The main question is, where to assign externals when using a splash stack, which becomes the executable (but doesn't needs the externals) and a main stack which stays a .rev and needs the externals. Is it enough just to put them into the properties\externals of the called main stack (rev-file) and I don't need the binding functionality for the externals, when building the standalone of the splash stack? Any hint welcome :) Tiemo ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
stack design with externals?
Hello, just making my first project with externals (valentina in this case), I started the project with a main stack, which carries most of the functionality and some substacks. I added the valentina externals to the main stack, build the standalone of my main stack and everything works so far. If I now would change the design of my project with building a separate splash stack (app/exe), which calls after start my main stack file (rev), this splash stack would get the standalone app and my main stack is only a standard stack file, where I can't assign anymore any externals. In this scenario I had to assign the externals to the splash stack, because that's the one I build the standalone of. But probably my main stack couldn't find the externals anymore, after the splash stack is closed and the main stack is open. (didn't tested it yet). And anyway I would have wanted the splash stack as small as possible and not with bound externals. Now I am puzzled. Is my approach with a separate splash stack not possible with externals and a splash stack can only be the main stack in a standalone and my current main stack has to get a substack? Or am I on the wrong lane at all and don't have to care where to assign the externals and runrev will find them anyway? Thanks for enlightening Tiemo ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
