Maarten ter Huurne wrote:
> > I meant different toolkits for different systems. Yes,
> > it may be a waste of time, but may happen anyway. `:)
> If different people start working on different implementations, there is a
> smaller chance that there will be a complete toolkit available for the
> system you use.
If different toolkits could use the same data
(e.g., even importing final game data), we can
address some specific tool's weakness with some
external utility. I'm almost sure I'd do it,
although I can only program in Basic. Yet, I
acknowledge a lot of people couldn't use my
tools, even if they turn out to be useful. :(
> A nice game toolkit would need things like menus, file open/save dialogs,
> multiple windows, cut and paste etc.
I agree, but I'd like to work with uncomplete
tools anyway. As long as we can do SOMETHING... :)
Multiple undo's are a nice touch, but they
shouldn't be top priority. It would be better
to release a tool without that feature, if
it could help game designers.
> > I wasn't thinking on a GUI. Does Java's GUI
> > implementation is consistent across platforms?
> Java AWT adapts itself to the platform it runs on. So for example radio
> buttons on Windows look like Windows radio buttons and radio buttons on
> Unix look like Motif radio buttons.
That sounds nice. I'd like to see it in Mac too. `:)
(...)
> However, my experience with Swing is that its responsiveness is poor. For
> example: it takes about half a second for a menu to appear. Since
> responsiveness is one of the most important aspects of a GUI (along with
> consistency), I think the current Swing implementations are useless.
Sounds ugly. Let's forget it. I'm almost buying your
Java idea... Which Java development environment would
you recommend -- for Linux or Windows? :)
> Java AWT, if used properly, will look pretty much like the OS you're using
> it under.
Very nice. Is it fast enough? :)
> I don't think there are much, but there will be a few. And if they can use
> the toolkit, that's a bonus.
You're right. I'm just sorry because I can't contribute
for a Java toolkit... <:)
> > But I'm not a (good) programmer anyway.
> I really like Java. It saved me from those horrible pointers. It saved me
(...)
> parallellism).
Is it really fast and stable? What kind of running
environment we must have?
> > I really hate Cobol. `:)))
> Can't comment to that, I've never programmed Cobol.
If you can, take a look at a listing. It's UGLY! <:)
When microinformatics started blooming in Brazil, a
lot of minicourses appeared. This was the base cur-
riculum:
- IPD (introduction to data processing -- DOS)
- Basic (GWBasic)
- Cobol (can't remember... Cobol80?)
- dBase (dBase II?)
- WordStar
- Lotus 1-2-3
Thank God, I never needed Cobol.
> I think QuickBASIC is the ugliest language I've used. I used to love it,
> because it was like MSX BASIC, but now I think it's horrible.
I like it. However, I can only program in Basic
flavours... Maybe Pascal. `:)
> MCCW is made with Java tools. They are command line tools that generate the
> HTML code, so they are not present in the web pages. But they are very good
Command line tools? How? I'd like to have
something like that! :)
> tools (applications, not applets, I'm not sure which one you meant with
> "app." :).
I meant tools. I changed my words to reflect
my thoughts... `:) But really, I never saw a
Java tool.
Thank you very much, guys, this conversation is
really interesting for me. <:)
[]s,
----- Parn (ICQ#1693182)
/| | | |\
\| ___ |/ http://parn.cjb.net/
\/ ----- \/ Parn's Music Station
| | Game Music XMs and more!
-- -- Izati Abamehinam Etokafe Nan
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
