On Wed, 27 Sep 2000, John Levon wrote:
> On Tue, 26 Sep 2000, Dekel Tsur wrote:
>
> > Designing a XForms dialog with fdesign was always a tedious task,
> > which is why there are new features with no GUI support (for example:
> > per-paragraph spacing). With the GUII, the situation is worse, as
john jabbed,
> On Tue, 26 Sep 2000, Dekel Tsur wrote:
> I'm sceptical it would be simple to do this in a way that would suit all
> the frontends. Remember Kaptain is for a specific GUI toolkit.
> And as Lars points out they shouldn't be the same design anyway - the
> environments have different
On Tue, 26 Sep 2000, Dekel Tsur wrote:
> Designing a XForms dialog with fdesign was always a tedious task,
> which is why there are new features with no GUI support (for example:
> per-paragraph spacing). With the GUII, the situation is worse, as the GUI work
> is needed to be repeated 3 times (
> So, I want to suggest a new approach for doing GUII dialogs:
> The dialogs structure and logiv will be defined by in a simple text file,
> and the dialogs will be built in run-time from these files.
If this simple text file resembles Tcl syntax you'll even get a fourth Gui
(Tk) for free ;-)
A
Dekel Tsur <[EMAIL PROTECTED]> writes:
| Designing a XForms dialog with fdesign was always a tedious task,
| which is why there are new features with no GUI support (for example:
| per-paragraph spacing).
That was me beeing afraid that my fdesign would ruin fd files etc.
| With the GUII, the s
Designing a XForms dialog with fdesign was always a tedious task,
which is why there are new features with no GUI support (for example:
per-paragraph spacing). With the GUII, the situation is worse, as the GUI work
is needed to be repeated 3 times (or even more in the future).
So, I want to sugg
