Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #16308 > unrolled thread
| Started by | Patricia Shanahan <pats@acm.org> |
|---|---|
| First post | 2012-10-01 22:49 -0700 |
| Last post | 2012-10-03 19:54 -0700 |
| Articles | 4 on this page of 44 — 11 participants |
Back to article view | Back to comp.lang.javascript
Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-01 22:49 -0700
Re: Sending email with attachments Scott Sauyet <scott.sauyet@gmail.com> - 2012-10-02 04:20 -0700
Re: Sending email with attachments Scott Sauyet <scott.sauyet@gmail.com> - 2012-10-02 05:16 -0700
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-02 07:10 -0700
Re: Sending email with attachments Scott Sauyet <scott.sauyet@gmail.com> - 2012-10-02 10:57 -0700
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-02 07:03 -0700
Re: Sending email with attachments Scott Sauyet <scott.sauyet@gmail.com> - 2012-10-02 10:50 -0700
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-02 11:16 -0700
Re: Sending email with attachments dann90038@gmail.com - 2012-10-02 12:15 -0700
Re: Sending email with attachments "Tom de Neef" <tdeneef@qolor.nl> - 2012-10-02 21:28 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-02 12:59 -0700
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-02 22:26 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-03 20:04 +0100
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-06 02:07 +0100
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-06 08:48 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-06 20:29 +0100
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-06 21:49 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-07 08:13 +0100
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-07 14:28 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 00:43 +0100
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-08 03:26 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 07:18 +0100
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-08 11:13 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 18:57 +0100
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 09:46 +0100
Re: Sending email with attachments Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-10-08 12:01 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 19:16 +0100
Re: Sending email with attachments Gene Wirchenko <genew@ocis.net> - 2012-10-08 09:28 -0700
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 18:34 +0100
Re: Sending email with attachments Stefan Weiss <krewecherl@gmail.com> - 2012-10-07 12:46 +0200
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-07 18:55 +0200
Re: Sending email with attachments Stefan Weiss <krewecherl@gmail.com> - 2012-10-07 20:06 +0200
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-07 22:12 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-07 19:54 +0100
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 01:09 +0100
Re: Sending email with attachments Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-10-08 13:10 +0200
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-08 19:20 +0100
OT: Mac vs PC for development (Was: Sending email with attachments) Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-10-08 08:38 -0700
Re: Sending email with attachments Dr J R Stockton <reply1240@merlyn.demon.co.uk.invalid> - 2012-10-03 19:49 +0100
Re: Sending email with attachments Eli the Bearded <*@eli.users.panix.com> - 2012-10-03 23:08 +0000
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-04 02:46 +0100
Re: Sending email with attachments Scott Sauyet <scott.sauyet@gmail.com> - 2012-10-03 19:42 -0700
Re: Sending email with attachments Patricia Shanahan <pats@acm.org> - 2012-10-04 02:43 +0100
Re: Sending email with attachments Scott Sauyet <scott.sauyet@gmail.com> - 2012-10-03 19:54 -0700
Page 3 of 3 — ← Prev page 1 2 [3]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-10-04 02:46 +0100 |
| Message-ID | <A6qdnaDO28X6d_HNnZ2dnUVZ_i2dnZ2d@earthlink.com> |
| In reply to | #16368 |
Eli the Bearded wrote: > In comp.lang.javascript, > Dr J R Stockton <reply1240@merlyn.demon.co.uk.invalid> wrote: >> You can display the data, and the address, etc., and invite the user to >> copy'n'paste into their ordinary E-mail system. Ensure that the data >> fits in 72 characters per line, with newlines between, and uses only >> 7-bit characters, and has a data delimiter before and after, and it >> should be possible to extract it reliably from a received E-mail. That >> should all be easy for you to arrange. > > If the poster does go down that route, be aware that whitespace > get mangled in email often, so not making whitespace significant > will help to reliably extract the message. (Or make all whitespace > interchangable: one newline is as good as two spaces, etc.) > > Really the simple way to do this, is format the data however you > want, then apply the standard base64 encoding to it, and add headers. > The message will look a lot like a raw mail attachment, or a PGP > encypted block, or a SSL certificate, or ... The whitespace issue is a good point against sending the data unencoded. The data is spreadsheet-like, and needs to end up in a spreadsheet, so csv is the obvious text format, but newlines are significant. Breaking a long line into two shorter lines would create two spreadsheet rows where there should be one. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-10-03 19:42 -0700 |
| Message-ID | <276fe871-cb56-47a3-9377-fdc4d7e5de84@j14g2000yqb.googlegroups.com> |
| In reply to | #16376 |
Patricia Shanahan wrote: > The data is spreadsheet-like, and needs to end up in a spreadsheet, so > csv is the obvious text format, but newlines are significant. Breaking a > long line into two shorter lines would create two spreadsheet rows where > there should be one. For this and other similar reasons, the body of an email is almost certainly a terrible transport medium for the data you describe. You could use email attachments, but as already discussed, that probably won't be possible with client-side Javascript. -- Scott
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-10-04 02:43 +0100 |
| Message-ID | <ksGdnUosk_wudPHNnZ2dnUVZ_ridnZ2d@earthlink.com> |
| In reply to | #16364 |
Dr J R Stockton wrote: ... > But, as "someone new to JavaScript", your first thought should be to > find a confederate who already knows the language. Advertise in your > village magazine; look for scripted web pages that are local to your > town; employ a local firm who knows about such things, or whatever. I think "new to JavaScript" may have been ambiguous. I am not new to programming, or to learning programming languages, just to JavaScript. I have over 30 years professional programming experience and a doctorate in computer science. I have studied many programming languages, starting with Fortran in 1967. Usually, when I decide a program I want to write should be in a language I don't already know my first thought is to get reading and writing. I read books, tutorials, specifications, newsgroups, newsgroup FAQs, and existing code. I write short practice programs, starting with the basics, but after a couple of weeks of learning JavaScript I'm on to experimenting with some of the difficulties I need to solve. Is JavaScript especially difficult to learn? It does combine a lot of features, but I have not yet encountered a completely new feature, as distinct from variations on ideas I already understand. Even the browser incompatibility issue reminds me of the state of Fortran in the early 1980's. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-10-03 19:54 -0700 |
| Message-ID | <9e24e7d2-e63e-4903-a2ed-4d8f89f6b8e4@x14g2000yqh.googlegroups.com> |
| In reply to | #16375 |
Patricia Shanahan wrote: > I think "new to JavaScript" may have been ambiguous. I am not new to > programming, or to learning programming languages, just to JavaScript. I > have over 30 years professional programming experience and a doctorate > in computer science. I have studied many programming languages, starting > with Fortran in 1967. > > [ ... ] > > Is JavaScript especially difficult to learn? No it is not. There are difficulties in browser-scripting because of the incompatibilities, but there is nothing particularly challenging about the language. But, if you're familiar with C-style languages, it's easy to expect this one to act more like those than it does just because of syntactic similarity. Assuming you have experience with a language that has functional aspect, whether pure functional like ML or Haskell, or ones that have major functional techniques like LISP or Scheme, then you should be able to quickly grasp a big part of how the language differs from ones like Java or C#. The only other really unusual major aspect of the language is is prototypal inheritance. -- Scott
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | comp.lang.javascript
csiph-web