AltME: SDK

Messages

Wednesday 14th November, 2012

Ladislav

22:30reading data files in the application? - you mean to be "in the application"?

22:30(when encapped?)

DocKimbel

22:31Both cases, when run and encapped.

Ladislav

22:31yes, it is always both

DocKimbel

22:32I mean, when encapped, such data file should be encapped too.

Ladislav

22:32I can use either #include-binary or #include-string, etc. directives, or even the #do directive for something different

DocKimbel

22:32When run with DO, it should be just read from disk.

Ladislav

22:35it works using something like

# rebol -s %incl.r "%cheyenne.r"

22:35(see the http://www.rebol.net/wiki/INCLUDE_documentation)

22:37actually, I do not write these #rebol -s %incl.r "...", I just click on the file

22:38and to encap it, I use right-click

22:40...and it does not work just in Windows, the same holds for Linux

DocKimbel

22:43I run all my REBOL scripts using F10 key from my code editor (which launches "rebol -s" on the script), having to use a wrapper script won't fit well my way of working. F11 encaps the current script directly with /Pro, F12 encaps it with /CommandView. :-)

Ladislav

22:43that is not a problem, why there is any problem in using rebol -s %incl instead of rebol -s?

DocKimbel

22:46I guess I shouldn't be able to use %do on any such script from console anymore?

22:46sorry: do instead of %do

Ladislav

22:46just use INCLUDE

22:47(it actually even finds the script for you, as opposed to DO which does not have a search capability)

22:48for example, I write:

include %timblk.r

and do not care where the script is, since INCLUDE finds it for me

DocKimbel

22:49How does it avoid collisions between similar script names in different include folders?

Gregg

22:50It does mean relying on INCLUDE as a normal part of your workflow and approach, but I would have a hard time giving it up now.

Last message posted 125 weeks ago.