Re: Unpack When? Part II
- From: "Chandru Murthi" <cmurth_xyz@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 12 Dec 2008 20:40:24 GMT
"Peter McMurray" <excalibur21@xxxxxxxxxxx> wrote in message
news:1Gj_k.127$cu.42@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Chandru
Thanks for looking at it in the spirit that the question was asked. I
made the point that the average user My "JS experience" is pure book work
at the moment and the input of others is very helpful in guiding further
efforts on a new interface. I am bemused as to why Tony got so upset
about dates as their treatment is undoubtedly one of the major business
issues to be decided and a tremendous trap for Pick people used to using
the server date only.
thanks, peter, for clarifying what I was trying to say in my original and
later posts. Indeed, large amounts of data may be transmitted on listings as
well as to data entry screens. It's up to the user.
I am (as you may have guessed) a big fan of javascript. Not because of any
inherent advantage, but because it works for me, the syntax is C-like and
the speed is more than acceptable. There's even a decent debugger. And I
believe in sticking with what's comfortable, even if a new gizmo comes along
that's "better," at least until a major release cycle of critical software
that's subject to endless breakages given typically inadequate testing
dollars, say once every 4 years. In this I may be in the minority, but
remember I'm still with Pick.
General js thoughts:
js has associative arrays;ie Array[stringreference] = 1 ; which allows
sparse arrays (ie not sequentially numbered) which allows cross-referencing
by name which I've found to be very useful for control-related applications.
As with anything else in js, you'll find that not everyting works
consisentenly or always (eg, associative arrays ignore the .join operator
(like MATPARSE) which converts the array to a delimited string, not exactly
documented clearly. So there's a lot of hit-or-miss stuff.
Another nice thing is that you can add an argument to a function and not
change existing calls to it, as the new argument is merely undefined (in
fact, you can use: if( newargument == undefined ) newargument=0; to keep
it clean ).
Also the fact that any non-null string and non-zero number are true and
null, zero, undefined are false is quite useful. This and the fact that
variables are type var (can store anything) makes my Pick BASIC-trained
heart swell. Null and zero are almost always the same (kid you not) so don't
always depend on it; I code if( var==0 || var=='' ). Also, of course, null
(the js reserved word) and '' (null string) are technically not the same,
but are in practice.
I add properties to html objects all the time, both as a way of adding
initial values (ie <input text id='myid' thisiscool="3" > where you can now
get the .thisiscool property value by
x=document.getElementById('myid').thisiscool .) or just to save data, (ie in
an onChange function:
onFocus="this.savebackcolor=this.style.backgroundColor;
this.style.backgroundColor='red'; "
onblur=" this.style.backgroundColor=this.savebackcolor;"
which is an easy way to save/restore the background color in the
onfocus/onblur cycle.
This btw, is frowned upon by purists.
Chandru
Anyway thanks for the input
Peter McMurray
"Chandru Murthi" <cmurth_xyz@xxxxxxxxxxxxxxxxxxx> wrote in message
news:hiZZk.2844$us6.1253@xxxxxxxxxxxxxxxxxxxxxxx
"Kevin Powick" <kpowick@xxxxxxxxx> wrote in message
news:64303a70-ba06-441c-93d0-490f6942b412@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Dec 4, 10:40 am, "Chandru Murthi" <cmurth_xyz@xxxxxxxxxxxxxxxxxxx>
wrote:
"Is it better to just shoot a Pick item down the line and unpack it at
the
user interface or is it better to do all the work in Pick on the server
and
just send the selected result that will need repacking upon return?"
Based on your findings, it may indeed be better for the browser basedapps that *you* are writing to do the matrix manipulation and data
conversion on the client side, but if you ever expect anyone else to
accept data from your MV system, you're better off keeping things on
the server and sending data converted (Date/Time, etc) and transmitted
in a more universal format, such as XML or JSON.
But that's missing the point entirely, or it's a matter of answering a
question I didn't ask, or something. Of course it's "my" application, and
I'm not sending this to some random web page. So there's no issue there.
I
was saying that if one were to develop a web.browser-MV application, this
point should be taken into consideration.
Chandru
--
Kevin Powick
.
- Follow-Ups:
- Re: Unpack When? Part II
- From: Peter McMurray
- Re: Unpack When? Part II
- From: frosty
- Re: Unpack When? Part II
- References:
- Unpack When? Part II
- From: Chandru Murthi
- Re: Unpack When? Part II
- From: Kevin Powick
- Re: Unpack When? Part II
- From: Chandru Murthi
- Re: Unpack When? Part II
- From: Peter McMurray
- Unpack When? Part II
- Prev by Date: Re: Universe NT Web Dev
- Next by Date: Re: Passing PARAMETER<1> to a subroutine
- Previous by thread: Re: Unpack When? Part II
- Next by thread: Re: Unpack When? Part II
- Index(es):
Relevant Pages
|
Loading