Perhaps it needs to be said here that I can simply forget the problems

regarding IV and PV and simply code my way along your suggestions

regardless of where they come from. =]



As Neil said: A balance requires to be kept. But then again, I don't

need to know. =]



"Harold P. Boushell" wrote:

> From: Harold P. Boushell                   30DEC20001

> Subject:  ICI Software:

> Date: Sun, 30 Dec 2001 15:10:07 +0100

> 

> The "LOOK AND FEEL" of the INSTALL program is:

> 

>           "WORLD CLASS COMMERCIAL GRADE MATERIAL"

> 

> JOB WELL DONE.

> 

> I trust "WE/YOU" can move to the SCREEN splitting of

> the ICI in this level of:

> 

> 1) INTUITIVE SIMPLICITY.    100% :o). HPB

> 2) 6,7,8 BUTTONS "ACTION/SELECTION" SIMPLISTIC.



It is not always as obvious, you will have to comment at what I make to

get the desired effect.



> 3) NICE GRAPHIC INTRODUCTION, SLOW FADE 4 SEC TO

>     A SMALLER GRAPHIC, AND OR A SPLASH TO FADE,

>     What you have is just a little big, but right

>     on target for OBJECTIVES.  Foot note INITIAL

>     SPLASH FADE, if re-entered same small GRAPHIC.



I have directly followed the graphical look of the Visual Studio 6.0

installer and of course took in your wishes as a priority. 



The immediate product (what you have drawn) appeared a bit to small and

compressed, definitely not something one would want as an installer, so

the first thing I did was that I expanded the installer window to the

maximum, filled the empty space and refited the window to the content.



I agree to the point that the graphic perhaps would need to be refited

to a square (because it contains a circle). The graphics is actualy an

imported JPEG (which I made using an external program), so fading it to

anything isn't as easy unless I was to use a series of JPEGs, which

would mean a file-size suecide. However, there is a chance for the

resizing: VB supports a pixel resize. The pixel resize is ugly when

sizing up, so the only thing I could do professionaly enough would be to

size it up from an innitialy reduced state.



> 4) HELP, is a common default on all screens.

>     "HELP" should be like you have done.  "HELP"

>     should be a "toggle switch" such that

>     when "ON" the mouse pointer when placed

>     over a "BUTTON" will activate an out-put

>     to the screen telling the "END USER" what

>     that "BUTTON" doze. The <F1> key is always

>     active and "CONTEXT DRIVEN" see other e-mail

>     with F0$ reference.



That's the method I dared not to implent as I supposed it a bit

primitive and ugly, but if *you* say so... =] 

ToolTipText is an interesting variation. Known from standard Microsoft

apps, if you hold a mouse cursor over an object, you will get a floating

describtion box next to the mouse cursor. This is supported by Visual

Basic, which means it is extemely simple to implent.



Now, state priority with priority reference (meaning: Tell me where on

my priority list should this be placed. Reference = Before or after the

installer). This priority setting is required, so I can create an entry

in my priority list, protecting your valuable contribution from the

leaks in my memory (reference: "Forgot to write the code for it" ;).



> Very good job:

> 

> Now let's see what can be done for the ICI "desk top".



All checked, but I'll need the "priority with priority reference" info

before I can put it all into my priority list.



>     Security up-date:

> 

>     Ready to enter "LOGON" testing phase between local computers.

> 

>     The "WGLOB000.CFG" file can not be completed until a

>     response is received from other team members.  However,

>     this should not effect my immediate software effort.



Posibly unrelated question about the Installer: It is not hard for me to

implent requests for all diffirent information and save it all to a

general ICI file for other programs to use. Standard database format

will be in use. What information should the Installer output?



> (((BERRIED IN THIS SUBTERFUGE IS THE FACT DOING THIS

> (((WILL DOCUMENT "SOURCE CODE" FOR IT'S TRUE FUNCTIONS.

> (((IT IS EITHER THIS OR MAJOR "BOOK PUBLISHING EFFORT"

> (((TO MAKE USER MANUALS WHICH NO ONE READ'S ANY HOW,

> (((TODAY.  :o).  HPB

> 

>     How about a context sensitive HTML manual that is loaded

>     by an ICI function? =]

> 

>     With your current work-load respectfully "NO".

>

>     I have done manuals before that's 6-9 months long.

>     The problem is a FACTORIAL one with all modes of

>     operation.  Just for now "NO".  Not to mention

>     "WE" are not done with "DEVELOPMENT".



Checked.



Hint: HTML includes #targets, that can be used for context sensitivity.



>     PS: Cooper can handle the imposable question

>         you might have about WINDOWS his e-mail is

>         < coop@epix.net >.  He is notorious for

>         not looking at his e-mail for days at a time.



Checked.



--



Don't feel bad about asking/telling me anything, I will always gladly

reply.



Digging for info? Try AI Meta Search:

Http://WWW.AIMetaSearch.Com



MesonAI -- If nobody else wants to do it, why shouldn't we?(TM)

Http://WWW.MesonAI.Com

