Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 01 2018 17:34
    @greggirwin banned @BIjeuca_twitter
  • Dec 03 2017 05:53
    @PeterWAWood banned @matrixbot
  • Sep 28 2016 12:20
    @PeterWAWood banned @TimeSeriesLord
BeardPower
@BeardPower
Don't get me wrong, I appreciate all your efforts :)
I'm just thinking, that it would speed up the project, if existing code would be merged. As I don't have insights into the project, I can, of course, be totally wrong.
Petr Krenzelok
@pekr
If random existing code would be merged, we would soon end-up in the multiple megabyte territory along with messy architecture :-) OTOH, noone is preventing us to use such code in terms of libraries or simply special solutions ...
BeardPower
@BeardPower
Sure, but I think that would only be a problem, if the code would not be following the project and architectural guidelines.
Nenad Rakocevic
@dockimbel

@BeardPower

I see. But isn't implementing the same feature twice a waste of precious resources?
As I don't have insights into the project, I can, of course, be totally wrong.

Your last assertion is correct. ;-) Red "full I/O" will rely on an async I/O engine.

BeardPower
@BeardPower
@dockimbel :+1:
geekyi
@geekyi
@BeardPower existing code helps, because we'd then have something to compare and improve upon! And we'd learn from the mistakes and know what to use. SO in the end, the code that gets merged would be pretty high quality..
Gregg Irwin
@greggirwin
All code and examples are helpful, even if they don't directly make it into the official mainline. As @geekyi said, and also because people can learn from them and build things they need which may not match what Red makes standard. e.g., @Oldes' code may be extremely useful to some people, and even end up as an extension, for some circumstances.
They can also save Team Red research time. As long as Team Red knows they exist, they can leverage them as well.
BeardPower
@BeardPower
@geekyi A very good point :)
@greggirwin Yeah, having all these resources available is really great for learning Red. Thanks to everyone for providing them :+1:
Abdullah Yiğiterol
@abdllhygt
Hİ!
How to convert integer to string?
Boleslav Březovský
@rebolek
>> form 123
== "123"
Abdullah Yiğiterol
@abdllhygt
thank you!
Boleslav Březovský
@rebolek
You're welcome! There are other ways, like to string!, but I prefer form.
dimsum
@KimRoach143_twitter
@rebolek hello I am still learning red code just wondering how can I lock the file or folder and open it only with system or administrator in read only mode
any file related documentation might help
Abdullah Yiğiterol
@abdllhygt
@rebolek this doesn't work on gui :/
Boleslav Březovský
@rebolek
@KimRoach143_twitter Hi! Red currently supports only basic file operations, full I/O will come with 0.7.0, but if it will include file locking is something I honestly can’t answer.
@abdllhygt Do you have an example of non-working code?
Abdullah Yiğiterol
@abdllhygt
'''
"Kasa " [
text form 123
]
'''
"Kasa " [
text form 123
]
dimsum
@KimRoach143_twitter
@rebolek dang it, I knew it could not find in any doc :wink:
do we have MDI (Multiple document interface)with gui?? If yes any example
Boleslav Březovský
@rebolek
@abdllhygt I see, you can’t put the code there directly, use something like
compose [text (form 123)]
Abdullah Yiğiterol
@abdllhygt
doesn't work, "Script Error: VID - invalid syntax at: [(form 100)]"
BeardPower
@BeardPower
Which version are you using? Works on 0.6.3
Abdullah Yiğiterol
@abdllhygt
yes, 0.6.3
BeardPower
@BeardPower
>> compose [text (form 123)]
== [text "123"]
dimsum
@KimRoach143_twitter
yep works for me too
Vladimir Vasilyev
@9214
@abdllhygt I bet you forgot compose
Abdullah Yiğiterol
@abdllhygt
@9214 no, i did use
Boleslav Březovský
@rebolek
This works: view compose [text (form "123")]
Vladimir Vasilyev
@9214
can you show full code snippet?
Abdullah Yiğiterol
@abdllhygt
"Kasa " [
            compose [text (form 120)]
                ; "Kasa" is tab-panel
        ]
My full code is long
error message: Script Error: VID - invalid syntax at: [compose [text (form 120)]] Where: do
* Stack: view layout layout layout cause-error
Vladimir Vasilyev
@9214
@abdllhygt
view compose/deep [text-list data [(form 1) (form 2) (form 3)]]
Abdullah Yiğiterol
@abdllhygt
yes :D
thank you @9214 haha
Abdullah Yiğiterol
@abdllhygt
i develop a commercial app with red
dimsum
@KimRoach143_twitter
@abdllhygt can you please share last code because it still gives me same error
Abdullah Yiğiterol
@abdllhygt
@KimRoach143_twitter i add near view "compose/deep"
view compose/deep [
;your code
]
dimsum
@KimRoach143_twitter
thanks @abdllhygt
Abdullah Yiğiterol
@abdllhygt
you're welcome
GiuseppeChillemi
@GiuseppeChillemi
Hi, I am still having problems understanding why a: "" or a: [] does not reset the content of A
From you comments at the end of april I have realized the "code is data" concept.
In this example:
red>> do code
== func [input /local s][s: "hello world" append s input]
red>> test "x"
== "hello worldx"
red>> body-of :test
== [s: "hello worldx" append s input]
I have realized that you are directly modifing the data/code structure.
But why a: "" or a: [] lead to nothing ? Aren't we linking a: to an empty block or are "" and [] "non existant", so it is like doing nothing ?
Vladimir Vasilyev
@9214
@GiuseppeChillemi for "how" - use copy or copy/deep, for "why" - series! values are passed as pointers to some memory location, then you say something like word: [], it means "allocate some space for series, initiate it with some content (no content in this case) and make word point to that storage space" . So, in fact,word from that moment is always bound to static memory address, while content of that address could be changed and extended freely.
GiuseppeChillemi
@GiuseppeChillemi
but if you a: "abcdef" and later a: "" why it is still "abcdef" ? shouldn't "a:" get linked to another memory region ?