🚀 go-pugleaf

I have done some work with 4D (Fourth Dimension) for the Mac and found some
features/bugs and suggestions for improvement. I think this database handler
is excellent, but there are still a few things to fix...

(By the way, I have version 1.0.4, and use it on MacII/SE/+ machines with 1
meg RAM under system release 5.0)



1. Included layouts. Database structure: I have one file with two or more sub-
files. Application: I want to display two different included layouts from two
different subfiles in one parent layout. This is not possible. 4D will only
show the layout and its data for the currently selected included layout. The
other included layouts on the parent layout are all erased from data and even
erased from the layout itself. Only a blank rectangular space gives you a
painful reminder that there should have been more data on the screen then is
actually displayed...

I don't like this. It can be considered a bug or a feature but I would really
like to have it fixed. I can't see any reason for displaying only one included
layout at a time. Limitations in programs annoy me, and limitations in develop-
ers packages gives me an *outburst* of anger.

Perhaps is it possible to solve the problem by changing the structure of the
database and use linked fields, but as I said, I hate limitations.



2. Speed of picture handling. It's PAINFULLY slow! Is this going to be speeded
up? I sure hope so, because just to move a reasonably sized picture in a picture
data field takes some 1 sec (!!!) between screen updates even on a MacII.



3. Memory limitations. On the MacII I have noticed that if you set the mapping
of your colour screen to 256 bits, every now and then you get "Memory Almost 
Full, Please Quit As Soon As Possible" messages. This is fixed if you turn the
mapping to 2 bits. Why is this? Bug to correct?

I have also noticed that this memory problem occurs with a few other programs,
and what bothers me is that I don't understand it. The picture memory is 
separate from the 1 meg RAM - right? (The capsules for the screen memory is
on the video card.) So why does a larger screen bit mapping cause RAM memory
problems? My intuition tells me that perhaps is some data (that grows larger 
with the number of colours to display) needed to be stored in the 1meg RAM to
"configure" the video card. (Excuase my somewhat unclear "model" for the pheno-
menon) - Can anyone comment on this?



4. Global Procedures (speed of). Can thay be made to run faster? Optimizations?
One solution is of course to use external procedures, but life sure would be 
simpler if this was unneccessary. My major problem, is to read data files with 
"4D-Talk" (4D's programming language) and this is really slow. (I have enorm-
ousely large data files, and many of them too...)



5. Importing pictures to 4D. How is this done in a smart way? Say that I have
some 20 picures to store in my database. I don't want to cut and past in all
these pictures manually via the clipboard. So what do I do? Has anyone done
anything about this problem? Perhaps written an extarnal procedure that reads
pictures form the clipboard or a file and puts them into picture fields in some
predefined 4D-database? Postings please!?!



    * * * * *     And NOW to some serious FLWAS in 4D!       * * * * *
    * * * * *     Saving the best part to the end, eh?       * * * * *



6. Text fields. Really annoying in one of my applications! You cannot use more
then one font at a time with text field data. (Defined in your output layout)
But I HAVE to enter/store/display more then one type of font in a text field,
and furtermore I have to be able to itlicize, boldface, (and preferably even
shift up and down) parts of the text. In other words do some basic(?) word
processing with the text and then store it with all its "features" in a 4D-text
field.

(Yes, I want all text in one text field without having to add mark-characters 
for italics e.t.c. for words or characters that are supposed to have these
"features".) and then do a lot of text 4D-Talk processing/displaying in the
layout. It should be (made) possible to do this without having to do tons of
work, don't you agree? I mean we're really talking Mac here, WYSIWYG, The Human
Interface e.t.c. You should be able to create database applications that are so
similar to ordianary Mac programs that the end user couldn't see any difference.


I really NEED this. Perhaps can it for some sordid reason not be done with
"normal" text fields? But then, perhaps is it time to create a new field type
in 4D for this purpose? Why not an EDIT-field or a WORDPROC-field?

Can this perhaps be implemented in an update? (How about it Laurent Ribardiere
ACIUS?) Any suggestions to circumvent this problem until then?


         * * * * *     This item concerns not only 4D     * * * * *


7. Run-Time modules. Why stick to this "by one at a time" model? Can one get
an unlimited Run-Time Module licence for 4D? Whitout paying MegaBucks? I think 
the cost for a module is ridiculously high here in Sweden. Some +100$ a piece.
Far too high. I believe in selling reasonably priced software. An application 
should not have to cost more then maximum some 100$ even if it is complex, and 
100$ - 100$ = 0$ (No profit = I starve to Death)

If the prices are too high, pirate copying will flourish. That's my view of
realities.

Can one get a Free licence for distribution of non profit scientific databases
using 4D?



________________________________________________________________________________
   ____    . Olle Nilsson
  /   /    . Dept. of Molecular Biology, University of Stockholm, Sweden
 /___/ o   . OLLE@ISAGEL.SUNET.SE (@SEKTH.BITNET)
________________________________________________________________________________