Two quick comments...

[John Esak]

I don't think you/we will be getting "graphical" screens... if the screen
area is changed... it will change, that's all. I do not believe the screens
will somehow magically start being graphical. I'm under the impression
(possibly mistaken) that the font will still have to be mono-spaced, and I
don't see any way to implement any kind of graphical button.

As for fpXML... if it is what I think it should be, it will immediately help
everyone with regard to most of the EDI applications out there. I'm hoping
there will be a simple way to map filePro fields through the XML stuff to
the fields in the various EDI applications and forms. I understand that you
need bigger screens... for me, I need this more.  This is where FP Tech will
have to count up the votes.

John


> -----Original Message-----
> From: Transpower [mailto:transpower at aol.com]
> Sent: Wednesday, February 08, 2006 10:52 AM
> To: john at valar.com
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Two quick comments...
>
>
> John:
>
> fpXML would be nice, but I don't see it as much of a priority as
> graphical screen and report layouts.  Setting up an XML transfer between
> two applications can take a lot of time, even with an intermediating
> matching utility.
>
> fileProGI just didn't work out because it lacks graphical screen
> layouts.  What most of us want is the ability to design buttons and
> attach processing tables to the buttons for mouse operation.  The
> automatic processing would still run before a record is displayed.  The
> input processing would run after a record is committed.  The @wef and
> @wlf functions could be attached to the individual fields.  Output
> process tables would be run by button selection.
>
> Regards,
> Ron Satz
> Transpower Corporation, www.transpowercorp.com, transpower at aol.com
>
>
>
>
> John Esak wrote on 2/7/2006, 6:34 PM:
>
>  > I've started a new thread to make two comments to Bud's description of
>  > what's in store for filePro.  First of all thanks. Now.
>  >
>  > 1) Of everything I've heard, the fpXML sounds like the most
> important new
>  > advancement for filePro. (In my opinion, of course) When considering
>  > *any*
>  > other feature, including all the screen stuff which is currently
>  > garnering
>  > great favor... keep this XML project at the very top. Why? Because, it
>  > will
>  > make filePro more interoperable with *everything* elese... and that is
>  > critical for *everyone*. All other features should take a back seat to
>  > this.
>  > (Except, finishing the MEMO function so that it will print an entire
>  > memo.)
>  >
>  > 2) Don't think in terms of years anymore. I know you can't give a
>  > guideline
>  > or time line. It's not fair to you. But, then in the same token, don't
>  > say
>  > fpXML will be out maybe in 2007....  Wh?  Because that is a !year!
>  > away from
>  > now... and if there is some enhancement to filePro that will take your
>  > programmers a !year! to write... there is something askew, and it
>  > makes it
>  > sound like there is something wrong. Nothing should take a year...
>  > with the
>  > exception of absolutely gigantic projects like server-side
> ODBC and other
>  > huge things like that. A full dtd/schema supporting XML interface
>  > should in
>  > no way take a !year!.  In my humble opniion, if you are going
> to do that
>  > one, to say it won't be here some time this year, is to say it will
>  > never be
>  > here quick enough for anyone wanting it.
>  >
>  > That's it. Only two cents. Hope you don't mind. I see that you
> are taking
>  > the usual beatings and bashings of many from this list. All I
> can say is,
>  > good luck. Evaluate it all, and do what you can.
>  >
>  > --
>  > John Esak
>  > (570) 384-2444
>  >
>  > Author of:
>  > The filePro Survivor Series
>  > Complete Video Training For filePro On CD
>  > See samples at: www.valar.com
>  >
>  > _______________________________________________
>  > Filepro-list mailing list
>  > Filepro-list at lists.celestial.com
>  > http://mailman.celestial.com/mailman/listinfo/filepro-list
>