Chris,
If you (and others) are serious about that, then there
needs to be a formal structure for doing so. Someone
(ideally you) would need to be a project manager to
approve additions to the WorldVista-Fileman project.
I wonder if we could use CVS technology as well.
I don't have enough experience to do anything other
than small changes here and there. But I think it is
time for the community to step forward on this issue.
Kevin
--- Chris Richardson <[EMAIL PROTECTED]> wrote:
> Kevin;
>
> Who wants to extend Fileman? WorldVistA is
> interested in doing that and
> more. We are interested in re-engineering and
> modernizing Fileman and
> Kernel. WorldVista is interested in helping to
> improve and advance the
> technology, modernizing the architecture to improve
> the reusability,
> functionality, and speed of the whole emerging VistA
> technology.
>
> Best wishes; Chris
>
> ----- Original Message -----
> From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> To: <hardhats-members@lists.sourceforge.net>
> Sent: Tuesday, February 01, 2005 3:55 PM
> Subject: Re: [Hardhats-members] Template Question
>
>
> > I have read of others making changes to Fileman
> and
> > submitting them to the VA, only to have them
> shelved
> > because FM is in a stasis state right now.
> >
> > Would it be worth it for the community to extend
> > Fileman outside of the VA?
> >
> > Kevin
> >
> >
> >
> > > As I understand it, there is frustration from
> some
> > > developers in the VA
> > > because the VA has long ago chosen to put these
> > > infrastructure
> > > components on maintenance. For instance, the
> last
> > > FM release was v22 in
> > > the mid-90s. While some patches add new
> > > functionality, these are not
> > > typically the source of large changes. So, yes,
> > > there are some things
> > > that many would like to see addressed in FM, but
> > > that isn't the
> > > direction the VA is going. I am not arguing for
> or
> > > against the current
> > > status quo, just pointing out factors that might
> > > explain partially why
> > > things are as they are.
> > >
> > > >Kevi
> > > >
> > > >--- Greg Kreis <[EMAIL PROTECTED]>
> wrote:
> > > >
> > > >
> > > >
> > > >>This is a good example of the danger of
> multiples
> > > in
> > > >>FM. They can create
> > > >>non-normalized databases, forcing folks to
> stand
> > > on
> > > >>their head to get
> > > >>some results. It is much easier, when
> reporting,
> > > to
> > > >>deal with files
> > > >>that have pointers that link the records.
> Having
> > > >>said that, these
> > > >>pointed files can be a pain in templates for
> > > >>editing.
> > > >>
> > > >>Bob Beckley wrote:
> > > >>
> > > >>
> > > >>
> > > >>>Greg,
> > > >>>
> > > >>>I finally ended up with this, and it seems to
> do
> > > >>>
> > > >>>
> > > >>the trick when I tie it to
> > > >>
> > > >>
> > > >>>a print-type menu option. I want to report
> just
> > > >>>
> > > >>>
> > > >>instances of where one
> > > >>
> > > >>
> > > >>>sub-field equals another sub-sub-field. Any
> > > >>>
> > > >>>
> > > >>additional comments are
> > > >>
> > > >>
> > > >>>certainly welcome.
> > > >>>
> > > >>>TST>D Q^DI
> > > >>>
> > > >>>VA FileMan 22.0
> > > >>>
> > > >>>Select OPTION: PRINT FILE ENTRIES
> > > >>>
> > > >>>OUTPUT FROM WHAT FILE: PRINT TEMPLATE// 458
> TIME
> > > &
> > > >>>
> > > >>>
> > > >>ATTENDANCE RECORDS
> > > >>
> > > >>
> > > >>> (281
> > > >>>
> > > >>>
> > > >>entries)
> > > >>
> > > >>
> > > >>>SORT BY: PAY PERIOD//
> > > >>>START WITH PAY PERIOD: FIRST// 04-12
> > > >>>GO TO PAY PERIOD: LAST// 04-12
> > > >>> WITHIN PAY PERIOD, SORT BY: 1 EMPLOYEE
> > > >>>
> > > >>>
> > > >>(multiple)
> > > >>
> > > >>
> > > >>> EMPLOYEE SUB-FIELD: 10 DAY # (multiple)
> > > >>> DAY # SUB-FIELD: APP. SUPERVISOR=TIMEKEEPER
> > > >>>
> > > >>>
> > > >>POSTING
> > > >>
> > > >>
> > > >>> WITHIN APP. SUPERVISOR=TIMEKEEPER POSTING,
> > > SORT
> > > >>>
> > > >>>
> > > >>BY:
> > > >>
> > > >>
> > > >>>STORE IN 'SORT' TEMPLATE: ZZBBSEARCH1
> > > >>> Are you adding 'ZZBBSEARCH1' as a new SORT
> > > >>>
> > > >>>
> > > >>TEMPLATE? No// Y (Yes)
> > > >>
> > > >>
> > > >>>DESCRIPTION:
> > > >>> No existing text
> > > >>> Edit? NO// YES
> > > >>>
> > > >>>==[ WRAP ]==[ INSERT ]=============<
> DESCRIPTION
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>>===========[ <PF1>H=Help ]====
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>Search template for APP. SUPERVISOR =
> TIMEKEEPER
> > > >>>
> > > >>>
> > > >>POSTING fields in T&A
> > > >>
> > > >>
> > > >>>file.
> > > >>>
> > > >>>
> > > >>>
> > >
> >
>
>><=======T=======T=======T=======T=======T=======T=======T=======T=======T>
> ==
> > > >>
> > > >>
> > > >>>====
> > > >>>
> > > >>>SHOULD TEMPLATE USER BE ASKED 'FROM'-'TO'
> RANGE
> > > FOR
> > > >>>
> > > >>>
> > > >>'PAY PERIOD'? NO// y
> > > >>
> > > >>
>
=== message truncated ===
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
