Have questions for fP Technologies?

[ernieb]

I was looking at Ken's Excel spreadsheet - not sure if he has all the descriptions.

[Lauren]

ah
no....you'd have to go back to the wishlist to get those, item by item

Can you clean the list up with what is there, and then we get the details on the rest?

or should I bug Howie some more?

[ernieb]

If we're going to use the Excel spreadsheet to narrow the list down - we'd need the complete descriptions to see what has been duplicated (or done).
Howie should be able to export everything into Excel format (CSV file) if it's being stored in filePro.

[Lauren]

yep

he just thought this would be quicker/easier

[kencole]

I will clean out the lines I know need to go, already in a current version, etc and then look at adding the detail of those that are left.  I agree that it would be easier if howie could have dumped the whole lot.

Ken

[kencole]

ah
no....you'd have to go back to the wishlist to get those, item by item

That doesn't work.  Howie's program won't let you get the details without entering an email address and to get the master list you don't enter an email address!

Can you clean the list up with what is there, and then we get the details on the rest?

or should I bug Howie some more?

Time to get Howie I think.

Ken

[Lauren]

I'm sorry, I meant go back out to that log in screen, and use the email address of the person who entered the item (Joe, you were my guinea pig)
Very tedious.

I'll talk to Howie tomorrow and see if he can send something over.

[kencole]

OK,

I have updated the Excel spreadsheet with red and orange shading.

Red=Done
Orange=I think it is done.

Ken

[Joe Chasan]

1) again i question why are we doing all the work when we don't even have fp-tech committing to review/discussion/session dedicated, etc.

2) if we are to continue, ken, a quick review for your update (mostly my wishes)
line #42 - not done
line #57 - not done (buying ODBC and win/dos filepro just to make this happen is overkill and not what i meant)
line #94 - not done - buying laura's screen painter is not what should be required to make this happen
line #146 - not done - lookups are in base fp - asking for solution in fpsql
line #161 - auto-update via the web - what we have now is somewhat convoluted.  most end-users are used to a simple process like click help to see version, the have an option on same screen to check-for-update

line #100 - i think this is done in 5.6 with new command 'dokey'

-joe

[Lauren]

I can officially confirm that there will be a wishlist discussion panel.
It will be Tuesday, after lunch, based on the current, but tentative, agenda

[ernieb]

1) again i question why are we doing all the work when we don't even have fp-tech committing to review/discussion/session dedicated, etc.

2) if we are to continue, ken, a quick review for your update (mostly my wishes)
line #42 - not done
line #57 - not done (buying ODBC and win/dos filepro just to make this happen is overkill and not what i meant)
line #94 - not done - buying laura's screen painter is not what should be required to make this happen
line #146 - not done - lookups are in base fp - asking for solution in fpsql
line #161 - auto-update via the web - what we have now is somewhat convoluted.  most end-users are used to a simple process like click help to see version, the have an option on same screen to check-for-update

line #100 - i think this is done in 5.6 with new command 'dokey'

-joe

And I know that # 226 is not done.
Also - I have made some requests through the forum that are not listed on the spreadsheet.

[kencole]

1) again i question why are we doing all the work when we don't even have fp-tech committing to review/discussion/session dedicated, etc.

2) if we are to continue, ken, a quick review for your update (mostly my wishes)
line #42 - not done
line #57 - not done (buying ODBC and win/dos filepro just to make this happen is overkill and not what i meant)
line #94 - not done - buying laura's screen painter is not what should be required to make this happen
line #146 - not done - lookups are in base fp - asking for solution in fpsql
line #161 - auto-update via the web - what we have now is somewhat convoluted.  most end-users are used to a simple process like click help to see version, the have an option on same screen to check-for-update

line #100 - i think this is done in 5.6 with new command 'dokey'

-joe

Joe,

I have updated the spreadsheet accordingly with you comments.  I marked line #100 orange as a "maybe".

Ken

[kencole]

And I know that # 226 is not done.

226 was not marked as done or maybe done!

Also - I have made some requests through the forum that are not listed on the spreadsheet.

This is a list of what is in the forum's wish list and what I think needs adding:

ernieb - expanded @CD - same as line 47 on spreadsheet.
ernieb - fully functional fpsql - same as line 226 (extracted two other items from thread and added as lines 249 & 250)
ernieb - F8 save from cabe and over writing existing files - add as line 251
ernieb - locked record problem on SuSE - added as line 252
john esak - F8 load options to pick file and processing - added as line 253 (there was an F8 save request same as ernieb above)
ernieb - map array to import and do imp(ct) - added as line 254
joe chasen - creation password features - already in list lines 38 and 241
lauren - record tagging - added as line 255
lauren - referential integrity - added as line 256
joe chasen - input with timeout - already in list on line 28
erineb - rebuilding ALL indexes, dxmaint with "*" option - already in list on line 120
nlpalmquist - better error reporting - coverd by existing items 30, 166, 214
ray hoover - screen size - already in list on line 614 & 223
bill randall - browse features - added as as line 257
tim barr - fpsql support qulaifiers - already in list on line 228
jcrespi - compiler - already in list on line 67
ernieb - intellisense - added as line 258
ernieb - search and replace - already in list on line 16 (added as line 259 fix cross reference to work with long variables)

Ken

[Joe Chasan]

a list this large can't possibly be gone through item by item during a conference session.
can we agree on what the next steps are to whittle it down some, or do we intend to distribute it as-is?

my opinion is that the session should focus on the BIG ideas.  we need to tell Bud that features X, Y, and Z are worth resources to put in because they are features that will sell filePro 6.0 - some of these might be on the list already, but some of them may come out just from having a good bunch of minds together in one room discussing it.  a good chunk of the items on the list are annoyances, however big, and not in the category of major new features, which is probably a better use of our time.

-joe

[Lauren]

We are, at this point, planning to do a panel discussion, with Ken, Ron, and Bud.

I wish I could do more here to help, but I just don't know enough about programming or filePro development to give input on the items.

I would suggest, based on my discussions with Ken, Ron, and Bud, that the list be as focused as possible on items that will benefit the most number of people. Basically what you just said, Joe

Then there can be a good discussion of items as being something they planned to address either on its own or as a part of something else, a direction they do not see filePro going,  or something the would love to do, but just isn't time effective.

Those seem to be the most common responses to things I've tossed at them