Hi,
About active essays and writing documentation inside Pharo, I'm trying
to bring some experience on writing using a tree/outliner like interface
for it. Questions are in another thread, but I hope to help with some
kind of "dynabooklets", for the moment using pandoc's markdown, wich
seems
On 30.05.2014 08:50, Joachim Geidel wrote:
> Yes, this page helped, but as you wrote: basic and simple example -
> the more involved stuff remains undocumented. When working on JNIPort,
> I struggled with simple things like de-referencing a pointer to a
> pointer to a struct etc. - I didn’t find d
great point , I think that Pillar already does this but its not exactly
hassle free. I have to say I really like Pillar, very simple syntax, it
generates pdf and hmtl ouput as well latex. Still will be an extra effort
to bring it inside Pharo in a form of an editor. But frankly if you want to
make
kilon alios wrote
> An insane amount of documentation
"insane" may be the key term here. We could be inventing executable active
essays, which is the kind of magic our live environment makes possible,
instead of writing and rewriting paper docs that quickly go stale.
Non-executable docs are a dup
"just to make sure that my message isn’t misunderstood: I am not blaming
Igor for not having written a book about NativeBoost (yet), and I am very
thankful that he wrote NativeBoost in the first place. I know how hard it
is to maintain a piece of software over an extended period of time. You
have t
Hi all,
Am 30.05.2014 um 10:30 schrieb kilon alios :
> he has not provided documentation for Nativeboost that's true, but he never
> left a question unanswered either ;)
just to make sure that my message isn’t misunderstood: I am not blaming Igor
for not having written a book about NativeBoost
he has not provided documentation for Nativeboost that's true, but he never
left a question unanswered either ;)
I think I will come around eventually to adding documentation to
Nativeboost.
Imagine every Pharoer adding 10 lines of documentation every day. Say 100
people . That's 33 pages per day
Hi joachim
could you spend some time and helping us to write a documentation on
nativeboost?
Else it will always stay the same. I cannot systematically try to write
documentation on things I do not have expertise
because it is killing me.
For igor everything is obvious :) but we spent some af
Hello Clément,
Am 29.05.2014 um 17:23 schrieb Clément Bera :
> NativeBoost is clearly the best option because it is the fastest, it is
> mostly implemented in the image so you can look at the code and it is by
> default in the image.
>
> FFI from the VM typically manages much better callbacks,
Hello,
To do what you want, there are 3 options:
- using NativeBoost
- using FFI from the VM
- compiling your dll as part of the vm (VM plugin)
NativeBoost is clearly the best option because it is the fastest, it is
mostly implemented in the image so you can look at the code and it is by
default
For nativeBoost have a look at the tutorial to use NB to bind X11
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/NativeBoost/NativeBoost.pier.html
I'm sorry but if igor does not write documentation, it takes far too
much energy from me to understa
The PharoForTheEnterprise book has a chapter on Nativeboost.
You can find the book here in pdf format
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/
also you can click on the folder to download only the Nativeboost chapter,
but I advice to download
I found an old Smalltalk/V imagine from 2000 and tracked down how I was
able add calls to Windows DLLs and to add my own. It was in the class
DynamicLinkLibrary and its subclasses, e. g., a call to the GDIDLL to
draw a Bezier spline (which I believe I added) was:
bezierTo: hDC lpPoints: anLPPO
13 matches
Mail list logo
