r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!REBOL3 Host Kit]

Pekr
10-Dec-2010
[1023]
I found out, that Genesi is now sponsoring Linaro Linux, which tries 
to unify distros for ARM target. They gave away 50 smartbooks:

http://bbrv.blogspot.com/2010/12/momentum-is-building.html
http://www.genesi-usa.com/products/smartbook


From past month's discussion with BBRV, I believe they are able to 
send us a machine to port R3. And now again - this is not my port-it-for-me 
request, just a note, to eventually start a discussion, how do we 
get ourselves on ARMs. Carl could have one smartbook to port Core, 
and someone willing to play with the HostKit port could have another 
one. In the case someone is interested, I could try to negotiate 
it with BBRV.


Of course - ARM is a broad term. I never heard of Linaro. We have 
some TI hardware, and I know there are some embedded systems for 
such stuff, mostly commercial and expensive, and Linaro might be 
an answer here. Another HW option is BeagleBoard (cheaper, more OSes 
supported, even QNX, Android):

http://beagleboard.org/
Aloysius
10-Dec-2010
[1024]
Pekr- thanks for the help, sorry my internet was so slow I didn't 
notice all the other chats until it was loaded just now. Thanks again 
for the quick response!
Kaj
10-Dec-2010
[1025x2]
Porting R3 to an ARM netbook Linux would be a good start. The binary 
R3 library may then even work on Android
However, the Android cross-compiling SDK with its emulator is also 
a good development environment
Andreas
10-Dec-2010
[1027x3]
Agreed.
Porting to a mainstream Linux ARM will hardly be any work at all.
Mostly a matter of either setting up a system to do the compile, 
or setting up a cross-compilation toolchain.
Kaj
10-Dec-2010
[1030]
There will be some source changes, but probably not many
Andreas
10-Dec-2010
[1031x2]
Talking about the hostkit side.
I imagine that some areas in the library, such as floating point 
support, may encounter some minor difficulties.
Kaj
10-Dec-2010
[1033]
Me too. ARM is not a PC architecture, so there may be differences 
in the device drivers
Aloysius
11-Dec-2010
[1034]
Is there any plan to implement the serial port? I wanted to communicate 
with GSM modem via serial port for sending AT-commands. Thx.
Kaj
11-Dec-2010
[1035x2]
Haven't heard anything about it, but I'm sure eventually someone 
will be interested in it
For such things it would probably be best to wait for the implementation 
of the devices interface, though
Pekr
11-Dec-2010
[1037]
I was just recently thinking about serial port too, we will need 
it for kiosks. Maybe Carl could release R2 serial interface sources 
as a starter?
Oldes
12-Dec-2010
[1038]
Let's say that I have a C++ application and would like to use R3.dll 
in it. Is there someone who is able to create a minimal example which 
would init R3.dll, send a string to it and get, for example, reversed 
output? I'm sure that such and example would help with R3 adoption.
Kaj
12-Dec-2010
[1039]
I'll get to that when I start porting View to the Syllable GUI, but 
that project is still a bit in the future
Andreas
12-Dec-2010
[1040x3]
Starting with literally just the dll is probably a unnecessarily 
complicated way to approach this.
The easier approach is to reshape the hostkit to embed it in another 
application.
The current "main" (src/os/host-main.c) is a good demonstration of 
what is necessary to init libr3 and eval strings.
Kaj
12-Dec-2010
[1043]
Yes, of course
Oldes
23-Dec-2010
[1044]
Any idea why we do not receive key up events? It should be supported 
according the source code.
Pekr
28-Dec-2010
[1045]
Not directly related to R3, but an example how MorphOS guys aproach 
using LUA as a system language extension (AREXX replacement). It 
might be interesting to compare for those, who plan to integrate 
R3 to other systems - http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=32945&forum=28
Oldes
2-Jan-2011
[1046x3]
When I build R3A110 and use text in view, the text is invalid. It's 
valid only if I provide it as UCS2, like:  g_text: make gob! [size: 
100x20 text: "^(41)^(00)^(42)^(00)"]

Does anybody (except Cyphre, who is not here) know, what can be wrong? 
I build it with CodeBlocks.
The problem is related to the graphics part only as I can use text, 
even with czech chars, correctly in the console.
I wonder how much differ the RM-assets' host-kit from the latest 
Carl's one.
PeterWood
2-Jan-2011
[1049]
Has Unicode support been added to R3 Graphics yet?
Oldes
2-Jan-2011
[1050]
It is in the Rm's binary release.
PeterWood
2-Jan-2011
[1051]
That's great news.
Oldes
2-Jan-2011
[1052]
If RM want more people to join the GUI development, they should sync 
the host-kit with Carl.
Robert
2-Jan-2011
[1053x2]
Our release is more advanced as the official one from Carl. As our 
changes are merged into the offical version from time to time. We 
move forward with our branch.
advanced WRT to the graphics & GUI stuff.
Oldes
2-Jan-2011
[1055]
Isn't it possible to provide your version as well?
Robert
2-Jan-2011
[1056]
It's available from www.rm-asset.com
Oldes
2-Jan-2011
[1057x3]
I mean the source of course.
fine... I've found that the text must be bound to the text extension 
context.. this works:
ext-text: import 'text
g_text: make gob! [size: 100x20 ]
g_text/text: bind [
	;bold true
	text "AB"
] ext-text


The question is, what is changed in RM's version that it works without 
such a hack.... I have no problem to hack just the official A110 
version so far as I'm trying to understand how the internals work, 
but I really think that we need synced source repository ASAP.
Is there a way how to force REBCHR to be in multibyte format? Because 
the problem for the above issue is at this line:

https://github.com/rebolsource/r3-hostkit/blob/f331c6a46947e6e5afedc90f3d375bcd3f7ad8a1/src/agg/agg_truetype_text.cpp#L305
Kaj
2-Jan-2011
[1060]
You can define it when you create a REBSER string, but a character, 
I don't know
BrianH
2-Jan-2011
[1061]
Doesn't REBCHR refer to an internal format?
Kaj
2-Jan-2011
[1062x2]
Yeah, I don't think I've seen it anywhere
The extensions use u32 for a character
Oldes
2-Jan-2011
[1064]
Yes... but AGG requires multibyte. Probably. At least I can display 
gob with non ansi string like:
	g_text: make gob! [size: 100x20 text: "èøž"]
but not:
	g_text: make gob! [size: 100x20 text: "crz"]
Kaj
2-Jan-2011
[1065x2]
If text is needed in a different format, you have to convert it somehow
Multibyte will always need to be multibyte. The question is what 
sort of multibyte
Oldes
2-Jan-2011
[1067]
AB
 = "^(41)^(00)^(42)^(00)"
BrianH
2-Jan-2011
[1068]
As Kaj says, that just means that there needs to be a conversion 
step in there somewhere. R3's internal character format is supposed 
to switch amond UCS-1, UCS-2 and UCS-4 in theory, but in practice 
might just be UCS-2 all the time (haven't checked lately).
Oldes
2-Jan-2011
[1069]
There must be easy way... for example to check the RMA's source :)
Kaj
2-Jan-2011
[1070x2]
Sounds like it's configured for Windows UCS-2
I'd be surprised if AGG couldn't work with UTF-8, and that wouldn't 
be the default on Unix
BrianH
2-Jan-2011
[1072]
I can only test on Windows at the moment, so I don't know how it 
behaves on other platforms.