Re: [orca-list] IMPORTANT - README - FLAG DAY

[hackingKK <hackingkk gmail com>]

Hi joanie,

I just had a few questions which I had sent you privately.
firstly, I had tryed to hack orca long time back.
But writing foss based financial web applications is my day job.
That is not a heavy work for me because I have a good team which is well 
payed full-time for this work. so I rarely have to directly write a lot 
of code.

Another interesting thing is that regarding documentation.
I can get some funding for this work provided I start to understand 
scripting and the entire scripting architecture to start with.

Now to my questions.
It has been a long time and I don't know the insides of orca.
Can you tell me how to generate the debug streem for orca as you had 
suggested?
Secondly, which orca module should I absolutely understand before diving 
into code?
I am a python programmer with 3 + years of experience so this might be a 
good approach for me to start with.

These wer the questions I had asked you privately.

Happy hacking.
Krishnakant.
On Sunday 09 May 2010 06:26 PM, Joanmarie Diggs wrote:
> Hi Krishnakant:
>
>    
> > But I thought I might be too stupid to ask on this list because all
> > contributers would find it so basic that it was too obvious to answer.
> >      
> Gosh, I don't think we have that sort of culture here. From what I've
> seen, we all help each other out. If you have a question about Orca,
> especially its code, you should ask here.
>
>    
> > Joanie, I had sent you a private mail for asking some specific help on
> > getting started with hacking orca.
> >      
> I just went through my Inbox again and I'm not seeing it. Sorry! Sleep
> deprivation and/or that silly tracker bot could be to blame.
>
> Regardless, in terms of getting started, I'd suggest you just dive in.
> Just like Josà did the other day: He wanted Orca to speak the line to
> which the caret had moved. So he:
>
> 1. Captured a debug.out
>
> 2. Looked at all the events in his debug.out to see what we were getting
> and what we were responding to and how we were responding
>
> 3. Thought about what the solution would look like
>
> 4. Asked on the list for confirmation of his analysis of the relevant
> portion of the debug.out
>
> 5. Started in on a script, but couldn't quite get it working
>
> 6. Asked on the list
>
> Etc., etc.
>
> I'm afraid we do not have a "Beginner's Guide to Creating Custom Scripts
> in Orca" written. I'm afraid I do not have time to write such a guide.
> Your humble project lead/maintainer is a volunteer who has a DayJob. If
> other humble volunteers feel like writing such a guide, I would be more
> than happy to give feedback and edits as time permitted. If someone had
> funding to write such documentation, that would be great too.
>
> Until we have such a guide, I'm afraid you'll have to roll up your
> sleeves and dig into Orca. As I've said time and time again, debug.out's
> contain a wealth of information and you just have to get used to reading
> them and pulling out the relevant details. There's nothing else I have
> or can suggest at the moment. My apologies.
>
> Take care.
> --joanie
>
>
>