I don't think this is a conflict - it's more of a choice. While with K (as
I
know it from a couple of years ago; first, I admit I'm not quite up to
date) you
can present your results in a fast but DECENT view, with Dyalog (and
others) you
may really compose Windows GUI applications in a PROFESSIONAL view,
properly
balanced between the underlying language for data processing and the GUI.
For instance, for major applications from a users point of view I'd pick
Dyalog
with Causeway, an unmatched combination! (less pain than one would think;
maybe
a steep learning curve, but that pays off)
"Morten Kromberg" <mkrom@[EMAIL PROTECTED]
> wrote in message
news:6b5c0afe-2f8b-48d9-b563-69e541058094@[EMAIL PROTECTED]
Jan 17, 6:16 pm, "Jan Karman" <*a...@[EMAIL PROTECTED]
> wrote:
> "aleph0" <apl68...@[EMAIL PROTECTED]
> wrote in message
>
>
news:c212ce0a-7acb-4714-b81f-d7f0a3755d63@[EMAIL PROTECTED]
>
> > Thx Jan, I am aware of that. It is simply that I prefer to reduce the
> > amount of work involving the GUI rather than increasing it. i.e. A
> > working BCol on "Push" would have sufficed , rather than having to add
> > and maintain bitmaps etc.
>
> then, use K
There are some interesting conflicts here:
1) You want to do as little as possible, but
2) Have access to high level widgets provided by the platform, like
Windows TabControls, yet
3) Have complete control over colours etc (although the high level
widgets use "Themes" and explicitly try to deny you access to low
level control - changing the colour of individual elements of a
TabContol would be considered VERY BAD UI by the "experts")
Well, you can't have it all at once... :-)
And, while I think K is a really cool and ultra fast "reduced
instruction set" APL, expecially if you want to work with large
quantities of inverted data, I don't think it would be my choice of
GUI programming platform. Besides which, I believe that recent
versions of K no longer include the GUI, as it did not satisfy clients
well enough to be worth the effort (most customers have other
requirements for GUI than doing as little as possible). Today, I think
the Kx folks recommend using K for the computational engine and
something else like Java, VB, or Dyalog (I was invited to present at
the Kx User Meeting last year) for the frontend.
Morten
|
