Using Datagrids with 'stackrunner' like launcher.

Pete pete at mollysrevenge.com
Tue Jun 7 18:24:01 CDT 2011


What are the symptoms you're getting - error message, datagrids don't
display, etc?  Could it be that the datagrid library is looking for things
in the launcher's stack file (like the dg templates) rather than the
launched stack?
Pete
Molly's Revenge <http://www.mollysrevenge.com>




On Tue, Jun 7, 2011 at 4:16 PM, stephen barncard <
stephenREVOLUTION2 at barncard.com> wrote:

> I don't think you fully read my explanation and why this is not what I
> want.
> I don't want to recompile every time and this method is specific to one
> datagrid.  I am not using the 'splash stack' method so much as I am using a
> launcher with all the libraries and engine in one place.
>
> I've read the piece on how to add the datagrid to stacks assembled in the
> > standalone creator,  however this is different.
> > I don't change the splash stack - everything other than the engine and
> > libraries live in the current stack.
>
>
> On 7 June 2011 15:59, Marty Knapp <martyknapp at comcast.net> wrote:
>
> > Stephen,
> >
> > From this lesson:
> >
> >
> http://lessons.runrev.com/spaces/lessons/manuals/datagrid/lessons/7339-What-Do-I-Need-to-Do-To-Deploy-a-Standalone-With-A-Data-Grid-
> >
> > ---
> > "Some developers prefer to use a launcher (or splash) stack technique.
> This
> > technique builds a standalone using a stack with very little code in it.
> In
> > this case the stack used to build the standalone will not have a substack
> > whose name begins with "Data Grid Templates" as no data grids have been
> > added to it.
> >
> > In this case you will need to create a substack that tricks the
> Standalone
> > Builder into adding the necessary stack files. From the File menu, create
> a
> > new substack of your launcher stack (1).
> >
> > Name the substack "Data Grid Templates Dud" and save your launcher stack.
> > Now if you build a standalone application the Standalone Builder will
> > include the necessary data grid stack."
> > --
> >
> > I've used this trick and find it works.
> >
> > Marty Knapp
> >
> >
> >
> >  I have a lot of 'quick' stacks around that are too specific and tiny for
> >> each to have its own engine - what I've been doing is compiling a
> >> standalone
> >> 'Launcher' that looks at a web folder and lists the available stacks.
> >>
> >> i then select one and launch it via the 'go URL' command. Slick.
> Inspired
> >> by
> >> Ken Ray's invention. It can also upload stacks.
> >>
> >> I can then use any of these stacks anywhere with no IDE.  Very nice
> except
> >> I
> >> can't seem to make datagrids work on stacks that are used this way.  I
> was
> >> able to ascertain that indeed the substack with the datagrid template
> was
> >> there. But the datagrid just won't respond.
> >>
> >> I've tried start-using but it seems to have no effect.
> >>
> >> I've read the piece on how to add the datagrid to stacks assembled in
> the
> >> standalone creator,  however this is different.
> >> I don't change the splash stack - everything other than the engine and
> >> libraries live in the current stack.
> >>
> >> How do I connect the datagrid to the substack in this situation?  It's a
> >> drag to have two pieces , but since this is on the same stack file,
> >> shouldn't this just work?
> >>
> >> thanks for any help
> >>
> >> sqb
> >>
> >>
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
>
>
>
> --
>
>
>
> Stephen Barncard
> San Francisco Ca. USA
>
> more about sqb  <http://www.google.com/profiles/sbarncar>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>


More information about the use-livecode mailing list