On Thu, 12 Nov 2015 22:44:02 +0100
meik michalke wrote:
> it just seems the "select data" of the
> varselector is not being translated?
Indeed. Fixed.
Regards
Thomas
pgpsVBr4tukZD.pgp
Description: OpenPGP digital signature
___
rkward-devel mailing li
Am Donnerstag, 12. November 2015, 21:11:14 schrieb Thomas Friedrichsmeier:
> Looks like I'm about to run out of excuses for not using
> rkwarddev ;-)
:-D
your insisting on those changes pushed the package to a new level. i rewrote
some of the external plugin scripts and must say that the JS code
On Tue, 10 Nov 2015 15:16:48 +0100
meik michalke wrote:
> Am Montag, 2. November 2015, 21:31:18 schrieb Thomas Friedrichsmeier:
> > I'd still like to see an idq(), or something similar.
> > Removing a layer of quotes is a valuable thing, here. For all I
> > care, it would be good enough, if it can
Am Montag, 2. November 2015, 21:31:18 schrieb Thomas Friedrichsmeier:
> I'd still like to see an idq(), or something similar.
> Removing a layer of quotes is a valuable thing, here. For all I care,
> it would be good enough, if it can be used inside id(), only, so
> rk.paste.JS() would not need any
Hi,
On Tue, 27 Oct 2015 11:46:47 +0100
meik michalke wrote:
> > (And will you still give me idq() so I know I can mix
> > your high-level magic with "bare-to-the-bone" JS?)
>
> i think except for the quotes you don't have to wait for it. you
> proposed:
>
> rk.paste.JS ('var x = getString (',
Hi,
On Wed, 28 Oct 2015 16:26:22 +0100
meik michalke wrote:
> Am Mittwoch, 28. Oktober 2015, 14:54:28 schrieb Thomas
> Friedrichsmeier:
> ah, i see. well, yes, this was a bit harder to solve because of the
> differences. however, if someone evaluated the existing JS code files
> for commonly use
hi,
Am Mittwoch, 28. Oktober 2015, 14:54:28 schrieb Thomas Friedrichsmeier:
> meik michalke wrote:
> > i could use a typical use case you have in mind, to optimize this bit.
>
> I was mostly being curious, if you had an idea on this, since, of
> course in this example, the syntactic differences
Hi,
On Tue, 27 Oct 2015 17:02:55 +0100
meik michalke wrote:
> Am Dienstag, 27. Oktober 2015, 08:29:43 schrieb Thomas
> Friedrichsmeier:
> > Will you be able to cover for()-loops, too?
>
> there you go, for loops are now also supported, in a basic way.
>
> i needed to work around the different s
Am Dienstag, 27. Oktober 2015, 08:29:43 schrieb Thomas Friedrichsmeier:
> Will you be able to cover for()-loops, too?
there you go, for loops are now also supported, in a basic way.
i needed to work around the different syntax, so the current solution defines
an empty array first, then pushes th
hi,
Am Dienstag, 27. Oktober 2015, 08:29:43 schrieb Thomas Friedrichsmeier:
> Very cool, indeed. Congrats! This addresses a whole lot of my
> concerns.
to be honest, i don't like using ifelse() either... i always wanted to be able
to use plain "if" conditions in the first place, but back then i
On Mon, 26 Oct 2015 22:45:15 +0100
meik michalke wrote:
> i've just replaced the jo() function with the more powerful js()
> function:
>
> it is now possible to use plain if() conditions (nested as deep as
> you wish...) in rkwarddev to re-generate equivalent JavaScript
> conditions:
[...]
> th
Am Samstag, 24. Oktober 2015, 21:05:08 schrieb Thomas Friedrichsmeier:
> > that is, operators like !=, ==, > etc. are prevented from evaluation
> > by jo() and pasted as-is to the JS code.
>
> Neat hack! But not a path I'd like to go, personally. To be honest,
> those ite()-statements just give me
Hi,
On Sun, 25 Oct 2015 17:23:51 +0100
meik michalke wrote:
> nice discussion, btw ;-)
same here!
[Again a long snip]
> > But why not write JS-code like e.g.
> >
> > rk.paste.JS ("
> > var x = getString ('", id (x), "');
> > if (getBoolean ('", id (narm), "') {
> > x += ', na.rm=TRUE'
hi,
nice discussion, btw ;-)
Am Samstag, 24. Oktober 2015, 21:05:08 schrieb Thomas Friedrichsmeier:
> > all of this would mean some major changes in the workflow of the
> > package, and i'm not convinced yet that this is the right way to go.
> > it would also mean returning to editing several fil
On Sat, 24 Oct 2015 19:02 +0200
meik michalke wrote:
[long snip]
> changing this would mean really deep changes in the package with the
> risk of breaking it. i'm not so sure this is worth it.
Absolutely. My main point was actually: The exact naming of the JS-vars
won't matter too much in the fir
hi,
Am Samstag, 17. Oktober 2015, 10:36:56 schrieb Thomas Friedrichsmeier:
> Yes, clearly not having to worry about the IDs (and getting early
> feedback when you mistype something) is probably the best thing about
> rkwarddev. We wouldn't want to forgo this. OTOH, I'm not sure the
> automatic _va
Hi,
On Fri, 16 Oct 2015 22:51:49 +0200
meik michalke wrote:
> > Perhaps this might be a good opportunity to think about a -
> > slightly - less integrated solution for this, where the JS file
> > could be kept on its own, instead of inline-quoted?
>
> this has always been possible if you remove
hi,
Am Freitag, 16. Oktober 2015, 17:36:23 schrieb Thomas Friedrichsmeier:
> The generation of the JS is still what I like least about rkwarddev.
me too. the JS part has always been the least favourable for me, no matter
how.
> Trying to debug JS code that is all quoted, without syntax highligh
18 matches
Mail list logo
