9 Sep 2010 04:29
24 Sep 2010 19:31
Re: [Laszlo-dev] Reference TOC organization
I would look for the word "Custom" in the documentation.
For example:
Custom Language
Custom Tag
Custom Structure
Just my $0.02
Pete
On 9/24/2010 8:28 AM, P T Withington wrote:
> [Adding laszlo-user: Users: what would you look for if you were looking for documentation on how to add
your own tag to the language?]
>
> I'm thinking that maybe this needs to be split into several pieces.
>
> The original title 'Structure' probably referred to canvas, import, include, and library, which are how
you organize your program structure.
>
> There is another set of things I call 'meta tags' that are the tags you use to create your own new tags: class,
mixin, interface, attribute, method (missing), event, handler, setter (missing). Lisp calls these
'special forms' because they are processed specially by the compiler, but I'm thinking a title like
"Language" is better.
>
> splash* and contextmenu* seem out of place in both these lists. They are neither about structure nor
language, they just seem like components, no different than window, menu, etc.
>
> On 2010-09-24, at 10:17, Lou Iorio wrote:
(Continue reading)
28 Sep 2010 17:54
Re: [Laszlo-dev] Reference TOC organization
I like that. Norm suggested maybe we need to use more than one word for the category names. If we were starting from scratch, I might suggest taking an approach from Laszlo-Explorer and ordering the TOC by the way you might introduce the language: Language Basics canvas, view, text, inputtext, attribute Extending Behavior attribute, setter, method, handler Defining New Tags class, mixin, interface Basic (built-in) Tags view, text, inputtext, ... Organizing Programs import, include, library Advanced (built-in) Tags animator, context menu, splash ... Standard Extensions the components, probably broken out in more detail But perhaps that is a project with a longer-term focus. On 2010-09-28, at 10:31, Lou Iorio wrote: > I think this is simple and makes the most sense, but I'll leave the > discussion > open for another day or two... > > Structure > * <canvas>(Continue reading)
1 Oct 2010 14:23
Hello all, I have the following scenario: an OL UI filling in an XML. This XML has to be sent to the server who generates a PDF out of the content and returns this PDF to the client. The browser opens the PDF with its native capabilities (asking for saving or opening in system pdf viewer). My question is very simple: how to do that? I was trying to use a dataset but it doesn't seem to be able to handle non-xml responses. Right? Anyway how can I interface then with the browser? I also tried to write a Javascript that does this via an Ajax request and the "loadJS-ing" it through lz.Browser's interface. But here I fail against the limit of characters imposed by the API. I'm pretty out of ideas now .... any suggestions? Thanks, M.
1 Oct 2010 15:18
Re: PDF
You want to use the POST request type, so you do not run into any data size limit.
XML can contain arbitrary data, as long as it is escaped properly, so I don't
understand what you mean by non-xml responses. Can you give an example
of the code and data that causes the problem, maybe there is a bug in the encoding
of the data into the dataset.
On Fri, Oct 1, 2010 at 8:23 AM, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:
Hello all,
I have the following scenario: an OL UI filling in an XML. This XML has to be sent to the server who generates a PDF out of the content and returns this PDF to the client. The browser opens the PDF with its native capabilities (asking for saving or opening in system pdf viewer).
My question is very simple: how to do that?
I was trying to use a dataset but it doesn't seem to be able to handle non-xml responses. Right? Anyway how can I interface then with the browser?
I also tried to write a Javascript that does this via an Ajax request and the "loadJS-ing" it through lz.Browser's interface. But here I fail against the limit of characters imposed by the API.
I'm pretty out of ideas now .... any suggestions?
Thanks,
M.
--
Henry Minsky
Software Architect
hminsky <at> laszlosystems.com
1 Oct 2010 16:00
Re: PDF
Hi Henry,
with non-xml responses I mean that upon sending an XML resource, I get back from the server a PDF with no xml wrapping it.
So actually what I get is an Error: "Error ... client could not parse XML from server " actually because the PDF is a binary and not an XML ....
M.
On 10/01/2010 03:18 PM, Henry Minsky wrote:
with non-xml responses I mean that upon sending an XML resource, I get back from the server a PDF with no xml wrapping it.
So actually what I get is an Error: "Error ... client could not parse XML from server " actually because the PDF is a binary and not an XML ....
M.
On 10/01/2010 03:18 PM, Henry Minsky wrote:
You want to use the POST request type, so you do not run into any data size limit.
XML can contain arbitrary data, as long as it is escaped properly, so I don't
understand what you mean by non-xml responses. Can you give an example
of the code and data that causes the problem, maybe there is a bug in the encoding
of the data into the dataset.On Fri, Oct 1, 2010 at 8:23 AM, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:Hello all,
I have the following scenario: an OL UI filling in an XML. This XML has to be sent to the server who generates a PDF out of the content and returns this PDF to the client. The browser opens the PDF with its native capabilities (asking for saving or opening in system pdf viewer).
My question is very simple: how to do that?
I was trying to use a dataset but it doesn't seem to be able to handle non-xml responses. Right? Anyway how can I interface then with the browser?
I also tried to write a Javascript that does this via an Ajax request and the "loadJS-ing" it through lz.Browser's interface. But here I fail against the limit of characters imposed by the API.
I'm pretty out of ideas now .... any suggestions?
Thanks,
M.
--
Henry Minsky
Software Architect
hminsky-oDN+GTs16Eu/3pe1ocb+swC/G2K4zDHf@public.gmane.org
1 Oct 2010 16:22
Re: PDF
How about having the server return a URL (in an XML response) that your app then opens in a new browser window? Just need a little bookkeeping on the server side to match the URL with the submitted data.
On Oct 1, 2010, at 10:00, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:
On Oct 1, 2010, at 10:00, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:
Hi Henry,
with non-xml responses I mean that upon sending an XML resource, I get back from the server a PDF with no xml wrapping it.
So actually what I get is an Error: "Error ... client could not parse XML from server " actually because the PDF is a binary and not an XML ....
M.
On 10/01/2010 03:18 PM, Henry Minsky wrote:You want to use the POST request type, so you do not run into any data size limit.
XML can contain arbitrary data, as long as it is escaped properly, so I don't
understand what you mean by non-xml responses. Can you give an example
of the code and data that causes the problem, maybe there is a bug in the encoding
of the data into the dataset.On Fri, Oct 1, 2010 at 8:23 AM, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:Hello all,
I have the following scenario: an OL UI filling in an XML. This XML has to be sent to the server who generates a PDF out of the content and returns this PDF to the client. The browser opens the PDF with its native capabilities (asking for saving or opening in system pdf viewer).
My question is very simple: how to do that?
I was trying to use a dataset but it doesn't seem to be able to handle non-xml responses. Right? Anyway how can I interface then with the browser?
I also tried to write a Javascript that does this via an Ajax request and the "loadJS-ing" it through lz.Browser's interface. But here I fail against the limit of characters imposed by the API.
I'm pretty out of ideas now .... any suggestions?
Thanks,
M.
--
Henry Minsky
Software Architect
hminsky-oDN+GTs16Eu/3pe1ocb+swC/G2K4zDHf@public.gmane.org
1 Oct 2010 16:30
Re: PDF
Oh I see, you're talking about the response from the server. Yes, the dataset request does expect an XML response back. It uses XMLHTTPDataRequest in DHTML, and something
equivalent in the Flash runtime, which expects an XML reply.
What you may need to do is have the server send back an XML response with a
token or a URL link which is something that the user can then click to ask the browser actually fetch the PDF file, in a
way that the browser can handle using it's default mime handling capabilities.
There's an API in lz.Browser.loadURL which might be the right way to force the browser to
load a PDF from the server.
On Fri, Oct 1, 2010 at 10:00 AM, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:
Hi Henry,
with non-xml responses I mean that upon sending an XML resource, I get back from the server a PDF with no xml wrapping it.
So actually what I get is an Error: "Error ... client could not parse XML from server " actually because the PDF is a binary and not an XML ....
M.
On 10/01/2010 03:18 PM, Henry Minsky wrote:You want to use the POST request type, so you do not run into any data size limit.
XML can contain arbitrary data, as long as it is escaped properly, so I don't
understand what you mean by non-xml responses. Can you give an example
of the code and data that causes the problem, maybe there is a bug in the encoding
of the data into the dataset.On Fri, Oct 1, 2010 at 8:23 AM, Marco Lettere <m.lettere-FZbngtO8GYVsTGs9JXcMDQ@public.gmane.org> wrote:Hello all,
I have the following scenario: an OL UI filling in an XML. This XML has to be sent to the server who generates a PDF out of the content and returns this PDF to the client. The browser opens the PDF with its native capabilities (asking for saving or opening in system pdf viewer).
My question is very simple: how to do that?
I was trying to use a dataset but it doesn't seem to be able to handle non-xml responses. Right? Anyway how can I interface then with the browser?
I also tried to write a Javascript that does this via an Ajax request and the "loadJS-ing" it through lz.Browser's interface. But here I fail against the limit of characters imposed by the API.
I'm pretty out of ideas now .... any suggestions?
Thanks,
M.
--
Henry Minsky
Software Architect
hminsky <at> laszlosystems.com
--
Henry Minsky
Software Architect
hminsky <at> laszlosystems.com
RSS Feed