Hi Ariel,
That's what I find useful for *me* with this new feature.
What will be best for the user? Well ... I'm not a user-experience
specialist (this is a Uni.-specialization I'm not interested in)...
I can just speak form my experience as a user, and with other users
Well, don't under estimate your experience, or what you have garnered
from those you have helped and what I has to offer for overall use. The
development group may gain much by seeing how two of us "users" view the
use of the package differently.
better said Castilian - and my
awful-English could have give the wrong impression).
Your English is better then Castilian, the closest I could get would be
Spanglish..
In the last paragraph, I was just pointing my own lack of knowledge on
this topic: I know C/C++/Java (and other programming languages), but
developing software (not just for fun, but in something serious as OOo)
is something completely different and requires other skills I lack off,
That is all I am - just a user that came here uninvited and started
talking...
and OOo has an own team for that (the User Exp. team), all I can say
here is just my experience as user, I can't give a professional view on
this topic.
Nope you can just give your experienced view.. I saw a comment on one of
the mailing lists a while back, regarding something similar. It was in
regards to a feature request, perhaps a specific one or perhaps a
'generic' hypothetical one I don't recall, anyway the comment was that
even if the request had hundreds of votes it really should have someone
with formal HCI training look at it first. ( that is a paraphrase, but I
think it is close enough )
Reminded me of an old joke - The difference between Noah's ark and the
Titanic? - the former was built by a rank amateur and the later by a
team of nautical engineers.
If I could foresee the "future",
Maybe you could help shape it.
If I could foresee the "future", I'd say this will be end: forms will
become useless as soon as the user realizes what he is able to do with a
"DataAwareUnoControlDialog" or whatever name Frank's vision will have,
and as they become "useless" we won't miss macros in forms
Ok, well I can't speak for anyone else, but I really am interested in
your opinion on this - what would you replace these 'macros' with, or do
you just mean they would not be stored in the 'Forum' cum
"DataAwareUnoControlDialog"?
now we all design dialogs in this situation... but are the form-user and
the Basic-dialog-user the same? or the first one is a more "common" one?
he can make a form-doc. work -- a one with a very basic functionality
-- without any macro-programming at all, just "drawing" cantrols .
Again, these are only thoughts, I'm not sure, but they seem to be two
different kind of users.
There are different users needs for sure, for most - just making it
'work' - not a bad thing at all, IMO.
Till later,
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
