Joe,
Your suggestion for adding a keydown handler works beautifully.
My function ev_command_enter_ajax(ts) is quite complicated, but I think
your idea will work well.
I'll have to work on the details, though.
Thanks for those great ideas.
On Mon, Mar 17, 2014 at 9:13 PM, Joe Bogner wrote:
Raul,
I have now created 2 similar files -- console.ijs and console.html -- to
produce a 3-frame browser page. Both files are used in a similar way by the
user. Both require that first the user creates a jijx window and in that
window executes one of the following two commands (or uses menus to
ac
We definitely could use more documentation and/or examples.
If you feel comfortable writing some (perhaps in a blog post - then let us
know where you have posted it? Or on the jwiki?), that would be great.
(And, it should be relatively easy to add the NB. shortcuts to the jhs
editor. Conceptually
Much cleaner than my earlier suggestion.
Nice!
Thanks,
--
Raul
On Mon, Mar 17, 2014 at 9:13 PM, Joe Bogner wrote:
> On Mon, Mar 17, 2014 at 12:51 PM, Brian Schott
> wrote:
>
> Hi Brian - I tried out the demo and it looks like a fun way to play
> with webgl. I am looking forward to seeing
It's good to learn 2!:0 works. can you also try the following
(beware line wrapping), that is what basically browse_j_
2!:0 'which am'
2!:0 'am start -a android.intent.action.VIEW -d "http://www.google.com"; -t
text/html'
2!:0 'am start -a android.intent.action.EDIT -d "http://www.google.com";
On Mon, Mar 17, 2014 at 12:51 PM, Brian Schott wrote:
Hi Brian - I tried out the demo and it looks like a fun way to play
with webgl. I am looking forward to seeing where it goes
> For example is there a way to ignore the arrow key that is used in the
> graphic while the focus is in the text fie
Your request fails.
2!:0'uname -a'
|interface error
| 2!:0'uname -a'
Shell commands like ls work.
2!:0'pwd'
/storage/emulated/0
On Mar 17, 2014 5:50 PM, "bill lam" wrote:
> The installpath looks ok to me. Can you also test whether
> 2!:0 work or not, eg.
>
> 2!:0'uname -a'
>
> Пн, 17
The installpath looks ok to me. Can you also test whether
2!:0 work or not, eg.
2!:0'uname -a'
Пн, 17 мар 2014, Paul Jackson писал(а):
> Uninstalled, downloaded 16 Mar .apk, installed. Results are unchanged;
> only the About sub menu of
> Help has a visible response, essentially the same as the
Uninstalled, downloaded 16 Mar .apk, installed. Results are unchanged;
only the About sub menu of
Help has a visible response, essentially the same as the following:
JVERSION
Engine: j701/2011-02-23/15:25
Library: 8.01.023
Qt IDE: 1.0.25s/5.2.0
Platform: Android 32
Installer: j801 install
Inst
I see two different "locale" issues here. There's cocurrent (which is
independent of the browser window you are interacting with), and there's
the locale being used to handle http requests from javascript (which is
determined by the url - jijx urls will be handled by the jijx locale). I
guess I am
> I've been having problems with this, and there has been talk about
> decomissioning the j801 instance of the J debugger because of my problems.
Just to clarify: this refers to the GUI debugger, not the 13!:x primitives.
There were known problems with the GUI debugger from some time back, and it
Paul,
Can you try remove the app, download the latest apk and install again? do not
install docs/help addon until it can work with the remote help.
please also post the new JVERSION.
18.03.2014, в 0:32, Paul Jackson написал(а):
> It appears the problem I'm having with the Help menu and QT v
Raul,
Thank you for your thoughtful response, as always.
Let's start with (1). I am pretty sure I do want to change the locale in
jijx, unless there is a better way. At least changing the locale there has
been my current practice: cocurrent'tgsj'. The reason I have needed to do
that is that there
13!:19 is supposed to cut back the stack during debugging.
I've been having problems with this, and there has been talk about
decomissioning the j801 instance of the J debugger because of my problems.
Here's an illustration of these problems which (a) does not involve the
ide, and (b) does not in
That sounds plausible.
And that's basically what these tests were testing before.
Ideally, whenever we find a bug, or whenever we add a feature, we add tests
which illustrate the bug or the absence of the feature. These do not need
to be huge - simple is good. Good tests help draw attention to th
The only thing I can think of is
monad=: $:
dyad =: $:
ambi =: $:
Any other ideas?
On Mon, Mar 17, 2014 at 2:22 PM, Thomas Costigliola wrote:
> Perhaps
>
>s=. $:
>ss=. $: 103!:0
>
>>:@s f.
> >:@($: (103!:0))
>
>>:@ss f.
> >:@($: (103!:0) (103!:0))
>
> NB. A bug or a gnat?
>
>
Perhaps
s=. $:
ss=. $: 103!:0
>:@s f.
>:@($: (103!:0))
>:@ss f.
>:@($: (103!:0) (103!:0))
NB. A bug or a gnat?
So we are reduced to
s=: $:
f=.>:@s
g=.>:@($: 103!:0)
f=.f f.
(5!:1 <'f') -: 5!:1 <'g'
1
We are basically just telling ourselves that the feature is turn
In that case, these tests should not be deleted, and these tests should not
be disabled.
Instead, ambi, monad and dyad should be defined appropriately.
If that's not possible, either (a) the patch should be updated so that it
is possible, or (b) we should talk about why that hasn't happened.
Tha
I would not worry about efficiency, preserveDrawingBuffer has warnings on
it - that it is notoriously inefficient. (It's just an easy way of copying
content forward from previous renders.)
And I suspect that your vanishing turtles problem is also a result of
misplaced concerns about efficiency.
M
They will fail and should actually be removed instead of commented out.
Those tests were just checking that verbs containing $: that are fixed are
being properly wrapped in explicit definitions. They weren't executing the
verbs.
Since verbs with $: that are fixed are no longer wrapped in explicit
I was referring to the line in recursion-scope-word-from-linear.patch which
reads:
+BORK=.0 : 0 NB. This stuff is obsoleted by 103!:
This disables tests involving f. and $:
I think this merits discussion.
Thanks,
--
Raul
p.s. here's the tests which get disabled:
s=: $:
cap =: [:
monad
In this thread in its original post (to which I am replying here), I was
not able to view old turtle path lines when new lines were added. Raul
correctly pointed out a property of canvas, preserveDrawingBuffer (pDB),
that preserves the old lines and shows the new lines, too.
However, because ther
Raul, are you referring to the fact that it says "UNTESTED" next to the
downloads?
They should pass the standard test suite. If I have time I will try to
confirm that. If anyone else can confirm, that would be nice too. That was
put there more for an extra disclaimer so that when your computer exp
It appears the problem I'm having with the Help menu and QT versions on
Android is related to the OS release level. I have a tablet and a phone
which are at 4.2.2 and both of them fail. Two older tablets at 4.1 and 4.0
both work. The ones that work first show a dialog asking how I want the
reque
Hello,
After seeing Martin Saurer's video on web applications I have looked into the
qjide and set it up successfully on my hosting provider site. It is really
impressive to code and run J apps on the browser from anywhere with the
features available in qjide :) So first of all congratulations
25 matches
Mail list logo
