The way to fix 'openamiga'...

[iamaboringperson]

 :-)
Hi, everybody!

@Karlos:
I agree with this. MUI is not being developed outside of AROS and MOS. Hyperion are providing it as a "crippled shareware" version only so that people can run their older stuff; they would rather ppl use Reaction on new programs. The AROS/MOS crowd have spent way too much time and energy to give up on their effort, so I believe that the only way for the largest number of people to be able to use any given program is if that program has been written to use some sort of GUI abstraction layer. The user would decide what GUI toolkit to use, not the coder. If this abstraction layer happens to be one of the Linux APIs like Qt, wxWindows or GTK, so much the better; it will make porting many Linux programs a lot easier, and also help attract Linux coders because they won't need to learn yet another GUI API.

This is something that is definitely needed, but it's too big for a weekend coder. We need a determined team who has the respect and credibility of all three sides (AROS, MOS and Hyperion), because they will need to work closely with all three. In my opinion this project is a lot more important than getting an office suite, because we need anything and everything that will prevent people from thinking that writing programs for the Amiga is too much of a hassle. What good is an office suite if that's the only program you have?

@The OpenAmiga crew: if you're looking for a good cause to back, consider backing this one!

i quite agree!
a good standard called BOOPSI came out with 2.x
this is very a very good start for a gui toolkit, i believe reaction is based on this
a good use of the opensource model would be to produce a range of (opensource) gadgets/images that are compatable with all the common BOOPSI gadgets(which might include reaction ones)
just simple boopsi classes at first, then various authors can write new ones that are 100% source compatable, but have all the customization features in the world
and a standardized OOP C++ set of libraries could be added(and that

a problem with chosing MUI, and (AFAIK) AHI, and some of those others, especialy cybergraphics, is that if this is ment to be for opensource/non propritety OS's as well,
since not every OS out there can get cybergraphics for it, and AmigaOS 4.0 is ment to come with Piccaso anyway
there need to be other abstraction models
and a way to write software that will work on more than just cybergraphics.library

IMHO listing a whole bunch of apps aint going to help!

and more people/groups need to be involved

[iamaboringperson]

8bit bitplane modes are DEAD !! No one sensible codes SW anymore that needs them, and
since Openamiga is more targeted at "modern" Amiga I would even say noone really uses them anymore.

i wouldnt say that
for backwards compatability with OS3.1 graphics.library, 8 bit support is needed, and doesnt cause much harm
all gui's support 8-bit for some very good reasons

even if the 8-bit functions were used as an indirect way to call the hi/true color functions
or perhaps even if implemented as macros in the includes

i know its nice to have all modern tech. and no legacy stuff, but 8-bit color is still usefull

[iamaboringperson]

OT: I had sex with my wife to be last night you boring twat. you have a nice wank loser?

i never ment the intro. to sound so negative, nor to get people upset
but if this is your attitude, ill leave it with you and/or you psychologist to deal with
no use me flaming back, with more irrelevant nonsense

i would rather talk about the technical side of things i.e. programming

[iamaboringperson]

If the flamefest continues, I'll lock the thread. Try to be just a little more mature guys. These forums are not a vent for raging testosterone.

so what made you lock the thread??

all i saw was one flame, and it was pretty harmles IMO

 :-)

[iamaboringperson]

mdma

I'd rather do the actual programming as opposed to talking about it. Do you want to help?

id like to help(without being abused), however if its about listing programs, id say there is not much more that needs to be done,

if its about creating specifications for libraries and ABI's etc... i would certainly like to help
but what should be posted on the site, for now are the types of executable/ABI's that each OS(AOS/MOS/AROS)uses, that would be very helpful

and as somebody else suggested, an OOP GUI abstraction library, to help with better portability between GUI systems, so that each OS or user may chose their own GUI and programs will still be easily portable
that idea to get QT stuff from other platforms ported sounds good... if its possible

[iamaboringperson]

whoosh777

GCC i dont care so much for, but its a matter of personal choice IMO
i would probably prefer a comercial compiler, and including GCC as standard would only discourage other third party compiler producers - OK for AROS, probably not for AOS/MOS but thats just my opinion

MEMACS definintly should be made standard :-P

[iamaboringperson]

Karlos, i agree...

it would be especially nice with C++ interfaces for all of these

more choice of GUI for the programmer... the OS developer... and the end user...

plus it would be easier and more like other platforms(like borland c++ builder) to develop on

what i would really like is a dev. system like borland C++ builder
that would really help software development on the amiga
just do long as it is MUI/gadtools/reaction independant

[iamaboringperson]

And no, ReAction is not based on BOOPSI, but on ClassAct.

ReAction is just another name for ClassAct

and im still pretty sure they are based on BOOPSI
having '.class' '.gadget' and '.image' extentions (am i right here? its been a while since ive used my miggy)

and being opend like libraries, just like boopsi classes can be

[iamaboringperson]

Kronos wrote:
@boring
http://ftp.uni-paderborn.de/aminet/aminet/dev/mui/MUIPlusPlus.readme

Maybe something like that ?

(haven't tried it myself, but looks interesting)

Remember that not everybody likes MUI, and saying that we should all just use it and shutup, is pure arrogance
people should have the choice

there are other GUI OOP abstraction kits on aminet

what needs to be done, is that all of these should be studied, and the common features/components of each could be included into one cross-gui version
so that it is similar to whats out there already

lets face it: all gui's have similar features, just a slightly different way of implementing and programming for them

so why not produce a standard set of libraries that will work for reaction/classact, mui, and plain intuition boopsi & gadtools

so that it is about choice, and not: "thou shalt use MUI..."

[iamaboringperson]

Kronos

i understand that MUI and reaction work very differently
but a C++ set of includes would be a way around all of that
you(the application programmer) wouldnt be using the same functions, you would create an object, such as a button, asign some attributes to it, and get the input in some other OOP way...
the MUI/gadtools/reaction interfaces would be completly invisible to the programmer

[iamaboringperson]

http://aminet.net/aminet.cgi?string=C%2B%2B+GUI
i like the look of this CIT.lha...

[iamaboringperson]

I see no process for RFCs and therefore no means by which to get agreement. Its a fait accompli.

well, thats right - i would like to see a #### load of disscusion before any so called standards are posted on the web site

a list of programs just wont do it