AltME groups: search

I've updated the recipe in the Syllable build system to add Red:

In my Syllable build recipe you can see that you can download the 
current state of a branch the same way:

Sorry, it's probably missing from my build recipe

So from that page, I get to https://github.com/mxcl/homebrew/tree/master/Library/Formula

a long list of stuff. Down there, I see gtk+.rb, click it, and I 
get to a page, which seems to be some description (or recipe, as 
you mentioned). Then what?

If you want to compile PicoGL, on Syllable Server or some other Linux 
system, you can use the Syllable build system. Here's the build recipe:


http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/packages/PicoGL/

If Andreas updates the makefile in one of the next commits, my build 
recipe just downloads that. Ah, thanks

I see I penciled in a TO_SYLLABLE parameter here in the Syllable 
overlay of the build recipe:

Anyway, as I said, an unpalatable recipe

TomBon, don't encourage people to use rejoin for SQL queries. Definitely 
use parameterized queries. Building your own queries with rejoin 
is a sure recipe for SQL injection.

anyone got the recipe to enable graphics?

Another recipe how to get a resync: wait for a storm (quite frequent 
here these days) and a blackout while running AltMe. As opposed to 
Sunanda's experince I did not lose the password, just got a resync 
dating back to about 2005.

If so, I don't think that's a recipe for success.

http://www.rebol.net/cookbook/recipes/0026.html


This recipe says that a binary file is being sent.  I wonder how 
this works because the content type is url encoded, but there is 
not url encode function as a mezzanine by default.

BrianH, perhaps it's time for a little cookbook recipe on MAKE. :-)

anyone have a fast  recipe to convert an integer into a tupple?

MESSAGE TO ALL  :-)


I've finally found the way to drastically improve the overzealous 
mouse event handling within the lowest level of view directly without 
causing any noticeable side-effects in the normal face event handling.

its a small patch in view's wake-event function.


the only requirement is that you have at least one face (usually 
the window, if you can) which has a rate set to the response you 
need...  usually around 15 -20 is enough.


this makes face scrolling based on mouse mouse VERY smooth as there 
is no more lag ... which occurs because we can receive 2 to 3 times 
more events than view/AGG can refresh itself.

if you need this, please speak up, I'll gladly offer the recipe.

Hi Gregg -- The cookbook recipe is a good one for reading and processing 
CSV's as input.  My main issue is NOT the CSV part itself.  It is 
pretty simple really.  But as usual MS has some additional formatting 
rules whenever certain characters are embedded, and that is the part 
I'm having trouble with in order for a CSV file to be loaded as a 
spreadsheet. 


You don't happen to have one that lets you write CSV files as output 
for excel (with all the special rules etc)???   :-)

You can get there through the descriptions in the recipe for the 
Syllable build system:

We have a build recipe for PHP, which standardises the procedure, 
but I haven't tried it on Syllable Server yet

You could play the snake, divide the Indians among themselves and 
run the Boa web server. :-) We have a build recipe for it

I've written a build recipe for the Fossil version control system:

Thanks for the help. The recipe from the rebol cookbook show you 
how to upload a file provided the server runs a rebol script too. 
The server I'm uploading a file to doesn't. It expects multipart/form-data. 
Maybe the %cgi.r by Cal Dixon provides a solution. I'll investigate 
further. More hints will be appreciated, as well...

I upgraded the host kit on Syllable Desktop and Syllable Server to 
alpha 110. Here's the build recipe:

I tried the recipe but it's giving invalid port. I have SDK, license 
file, but it's not working.

what is missing is a 100 page book on the subject.  not a reference, 
but a guide to parsing.  In fact what I often feel is missing is 
a reference that outlines not how PARSE commands work, but the different 
typical parsing constructs themselves.


its like explaining algebra as opposed to maths.  they are both fundamentally 
similar, only that algebra has a lot of non-obvious tricks like substitution 
and reduction which can be done.   these things have to be shown 
(usually) to even be noticed, let alone understood.


in a sense, when people start out with parse, they understand the 
concept of matchin a pattern, they just don't undertand how to break 
up and analyse a PARSE pattern, there doesn't seem to be much docs 
in the way of identifiying common PARSE structures, for real world 
patterns.


where are the pattern types listed?... we don't really know them, 
in relation to PARSE, there are no types of pattern we can say apply 
this technique to that pattern.


that is what makes learning PARSE complicated, the *structure* of 
the parse rule is the hidden knowledge which newbies don't "see". 

we can't just say: here is the "recipe" to solve a "quadratic formula"... 
 


There could be a site which has hundreds/thousands of PARSE examples, 
documents, and active forums, just like there are for regexp, this 
is how rich PARSE is... but alas there is not.

Especially the recipe:

http://cvs.sourceforge.net/viewcvs.py/syllable/syllable/system/apps/utils/Builder/packages/orca-current/orca-current.recipe?rev=1.5&view=auto

Here's the recipe from my build system:

http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/packages/Boron--current/Boron--current.recipe?view=markup

I think also that whatever is made, should be documented in a cookbook 
recipe.

I think there is merit for a cookbook recipe which briefly describes 
a table of all block manipulation functions, or we have a way in 
HELP to relate these functions, so they become very visible to beginners. 
The problem is that beginners are not likely to be looking for them, 
because they don't expect them to be there. They were created by 
experienced users who have been coding REBOL for years.

Ammon, BrianH, it's search sucks: Which is why such a document should 
be a cookbook recipe. Easier to find.

About port to other OS, this is the info (in DocBase), I managed 
to get out of it (check history of that page):
http://www.rebol.net/wiki/Porting_Recipe

Ladislav, I'd like to make your article on Identity into a cookbook 
recipe, so it gets an official listing in the cookbooks list, so 
people can find it. Where do you think it would fit on this page:

http://www.rebol.net/cookbooks/

I will ...  with  a nice recipe for disaster as an example  hehehe 
   ;-)

I wrote a Syllable build recipe for Red:

On the one side you have a chaotic Linux ecosystem where most developers 
refuse to care about binary compatibility, on the other hand you 
have an isolated REBOL cave where Carl refuses to deal with outside 
complexity. This is a recipe for disaster. There must be some middle 
ground - as we have proven in Syllable