From: "Yuri Prokushev" <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Date sent: Thu, 01 Aug 2002 16:35:04 -0400 (EDT)
Priority: Normal
Subject: Re: [Sibyl] NLS
Send reply to: [EMAIL PROTECTED]
> > Not really. I'm talking about something else in fact. You can create
> >a unit containing array of messages, and possibly a function
> >returning individual messages. That unit could be compiled into a
> >DLL, and such a DLL could be linked in dynamically then.
> Oh, no. Such method good and easy for developer, but not for user.
What kind of user do you mean here? A user of an IDE (i.e. developer
as well as ourselves), or a user of the created application (i.e.
somebody who'll meet the possibly localized messages)? If you mean a
real end user, I don't see any difference for him.
> >> Also, msgcompiler can be included to LanguageManager of program, so
> >> no any additional external unils will be required. I consider this
> >> is best solution.
> > OK. Graphical programming is not really my domain. Do it as you
> >think.
> This is not graphical depened thing. Problem is: Any Sibyl's program
> will use SPCC.
Most programs created with Sibyl _will_ be graphical programs
(because people don't need Sibyl to create console apps).
> So, we must select such nls method which can be easely
> used for any program. If SPCC uses one NLS method and program uses
> another then too many problems with localication. (This is like
> WarpIN. Strings in *.tmf file and in resources. And *.wpi files.
And
> during install showed messages as from one as from another places)
Clearly true. I still don't know any reason, why a method different
from that one chosen for SPCC should be used on the program side,
however. You'll give the programmer tools for creating his
application together with some documention how it works / is supposed
to work. He can still choose a different solution, of course, but
this can't be avoided regardless of the chosen solution.
> >> BTW, I prefer to use cross-compiler tools for cross-compiler
> >> libs/programs, but not for native. Cross-compilation limits in
> >> developing and, in most cases, cross-platform things slowly. This
> >> is
> > I'm talking about cross-compilation here, i.e. possibility to
> >compile native OS/2 executables e.g. on Linux, etc.
> Oh... This is impossible for good-coded PM/SOM applications. For pure
> PM it is possible. But not for SOM/WPS.
I don't believe there'll be so many SOM/WPS applications created
with Sibyl.
.
.
> > This is something I consider quite important on a platform lacking
> > much software (I've
> >tried to find an OS/2 DVD video player to no avail now for example).
> Try WarpVision/WarpVisionGUI (BTW, this is good example of mix native
> code and cross-platform code)
I'm getting off-topic here, but I suspect WarpVision can only be
used to play DivX avi files, not real DVD films. At least this is
true for the version I have here (0.0.12).
Getting back on-topic - most have been said in this discussion
already, I guess. I won't really work with SPCC (neither help with
development, nor use it afterwards) myself most probably, so this is
really out of my domain. I just wanted to present my point of view. I
don't consider this question crucial, so I don't feel a need to
continue with this discussion for myself. Decide for yourself.
Tomas
-----------
To unsubscribe yourself from this list, send the following message
to [EMAIL PROTECTED]
unsubscribe sibyl
end
