I am activating this thread and others like it
with the same prfix to solve some real problems.
Likely someone (hint) will capture these for the knowledge base.
What will follow on this thread set are
pieces of functionality I am taking advantage of
in some other language or some other real-world app.
I code in lots of things.
You should expect to see stuff on this thread
in C, squeak, expect, python plus a few more
as I am the custodian of at least 2 other rare languages.
what kinds of questions/problems/issues?
Here is what I am looking for...
Sometimes it is just that one-thing that keeps
me from rewriting the app in Rebol or from using
a Rebol dialect to 'getitdone'.
Some of the issues I will bring forward
I have been using in some non-rebol-ian language
on the mirror site.
rebol-org-mirror-site: [
{place/website where we are prototyping a
better rebol.org for all to use.}
]
These 'issues' will need to be replaced to have a site
powered entirely by rebol.
I am also posting on the general list
because some of the issues have no or little
effect on the future rebol.org and instead
are probably real hinderances to adoption of Rebol
in other shops. Thus in creatively solving
my ? on this thread you should also be knocking
down roadblocks at other companies.
In some cases the answer will be
"wait for rebol/(fill-in-name-here)".
Please do not send a reply of that type.
You do not have to answer that to any
of the threads I post here until the
(fill-in-name-here) product can be downloaded
easily by all readers of your reply.
" An unsolved issue in business remains unsolved
quite well on its own without [your] vapors to spoil
long term plans. Tangible/attainable solutions
turn heads - even if ineffcient. Scaleable solutions
cause checkwriting to happen - again, even if inefficient! "
The issues I will bring up
may have an astonishing range.
They may sound stupid and strange
coming from someone like me.
Consider that you are helping me make a convincing
argument to adopt rebol and that this 'nit
from some other department is resisting and shooting down
my idea because his 'wit tells him rebol cant zzzz .
Otherwise, it may be that it is not me who is asking.
Maybe the solution is obvious, or rather, I already have
one way to solve it using some (unmentionable language)
as glue and doing so doesn't really aid adoption.
Finally, some of the questions will have been
answered before. It is fine refer me/readers to a particular
message already on the list that has both question and answer
using the {X-SELMA: [REBOL] dddddd} number.
And No, it is not a good idea to say 'someone already covered that
a while back...' unless you have the actual reference.
(I have a separate discourse on "incompleteSearchCriteria
as gumption-trap/sabotage" going on already.)
Isn't all of this already part of what a/this mailing list is for?
I am trying an in-situ experiment
to make a limited number of threads
very focused. [ challenge: if you can't stay
on-thread with these then everybody loses
cause adoption takes longer].
Remember to move or rename when appropriate
in my honor. Being the originator of
subj: { [REBOL] rebol.org purpose (was "archive" ) }
was fun but not something I am going
to write (now email) my mom about.
Th results will be captured
to initialize a section on
"winning mgmt over via real solutions"
_and_ also used I can more quickly help convert
some apps in that very site.
Since I _am_ busy helping to set up a better rebol.org,
I will probably only have time to reply or monitor this
particular thread (or threads that have "How do I" in the subj).
I will continue to collect all threads but
mark them 'already-read' otherwise.
{-----}
[EMAIL PROTECTED]
