i dont like the windows like x'es (red/green) either. Also the macintosh rounden are like someone said ..looks like a candyshop. ugly. too strong colours making the gui ugly. it should be something more that melts in to the background. nothing strong.

@all

And how you all think we should change "close button" while all of you have tons of different opinions ?:) And what about gui buttons at all ? How it possible to "cover" all the need of _every_ user in terms of looks of gui and design ? My answer is - unpossible. So some default "fine for us" crap, and then everyone can choice all what he want and replace.

Last edited by kas1e on 24-Feb-2011 at 08:51 PM.
Last edited by kas1e on 24-Feb-2011 at 08:50 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@all

far out guys... you are discussing close buttons, even OWB-MUI is not even done.... Wouldn't mind having a Windows like close button, if this speeds up release date ...

_________________
Geomarketing at
www.geobiz.de
www.gebietsplanung.net
www.geomarketing-consultant.de

@imagodespira

What about making one more skin for us ? I mean all those buttons, images, icons, transfer animations, etc ?

Quote:

@Topic: Nice work, hope for a Reaction based Version (dislike MUI ;) )

Dunno what you mean here. We already have reaction version done by joerg. That version on which we works, its Mui version of OWB on which works Fab on morphos (where is no reaction).

And we port mui version because its already have tons of features and all the options which user need (we port it, we not write it from scratch). So there if for sure unpossible to have Reaction version from Fab.

Maybe if Joerg someday will give sources to someone (with all necessary files for compiling) then it possible to works on RA-owb as well.

Last edited by kas1e on 24-Feb-2011 at 08:59 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

I mean features of this morphoes/Mui version in a reaction OWB ;)

skin: I don´t have much time, working on some projects. I also think if you need buttons, Images and icons that Mason is the right person to ask.

_________________
www.amiboing.de - www.entwickler-x.de

@imagodespira

Quote:

I mean features of this morphoes/Mui version in a reaction OWB ;)

If only someone will get full sources with all necessary files for compiling from Joerg, and will start to update that version more.

Quote:

skin: I don´t have much time, working on some projects. I also think if you need buttons, Images and icons that Mason is the right person to ask.

That ones which we use now, already done by Mason (and for me they looks good enough, but as i understand most of users not like it).

Last edited by kas1e on 24-Feb-2011 at 09:30 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

Why are we already discussing themes anyways?? I thought it would be more important to get the bugs and features fixed.

@kas1e

Quote:

How it possible to "cover" all the need of _every_ user in terms of looks of gui and design ? My answer is - unpossible. So some default "fine for us" crap, and then everyone can choice all what he want and replace.

haha yeah some of these guys are never happy its like a bunch of "soccer moms' sitting at starbucks complaining.

we are lucky to have this version coming out period. Who cares wtf the buttons look like?

@DAX Quote:

Let Hyperion show a few designs (including ImagoDespira one, perfectly shown in your last screen-shot or HERE) and let people vote.

While I kinda like ImagoDespira's theme (*), I would be worried about leaving it to a vote... We might end-up with the OS equivalent of the car designed by Himer Simpson:


i.e. Something which people think would (in theory) be great to use or look at, but which in actual practice is terrible to use (or look at for a long time).

A better solution might be for Hyperion to pick a few "great" themes, and then offer the user the choice after installing OS4.

(* = I still prefer OS4's default theme, except for the scroll arrow buttons, where ImagoDespira's non-raised buttons look more elegant IMHO.)

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

Quote:

"soccer moms' sitting at starbucks complaining.

As an English citizen, I object to that sentence more than any browser theme, lol.

Seriously, let the devs get on with producing a working product for now.
Cosmetics can come later.

_________________
If your nose runs and your feet smell, you're upside down.

@DAX Quote:

Great! this must be the fastest progressing development ever!

Ports are a lot easier to do than writing something from scratch. Particularly when porting from another Amiga-like OS.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@all

All of you are right, theme isn't important at this stage of development, we can discuss about it later, anyone can write his preferred theme

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@ChrisH

mui-owb for sure not "easy port". And there is tons of problems which i can't call "lot easer".

I even see on amiga-ng, that someone say "but its just a port ! almost no work! its only rewrite mui4 to mui3, and that all ! all the other apis are the same !" . Like its so easy .. that 1 day of work, no problems at all. No work, just some kind of one more port. ./configure and make ! no problems ! (strange why then no one do it before, if all that so easy).

Its ####ing hard really, i myself loose already 2 motnhs of everyday worring about. And deniil works on it every. And slash start to works on it as well.

We write new classes, new wrappers, new code. We fight with tons of bugs, whcih i see just first time. We fight with problems with compilers, with libs, with bugs in our mui3, with all of this, what was done by Fab & co for _2 years_ and all that code not our. We sometime just do not know what and where handles (because code are really huge) and we need to ask Fab where that and that.

Its can't be call as "just a port" for sure. And words about "ports a lot easiers than writing something from scratch" its not about mui-owb for sure.

Even more : that port, its even harder than writing something from scratch. The only pluse that its of course progressing faster , and better loose 2-3 months for porting, than 2-3 years for developing.

But its far away for calling "easy port because all the api the same". And even API which are not mui related , are different in some places. I not saying about problems with MUI rewriting, which are heavy enough.

Last edited by kas1e on 24-Feb-2011 at 10:29 PM.
Last edited by kas1e on 24-Feb-2011 at 10:19 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@ChrisH

I will certainly give you that it should (and hopefully will) be Hyperion to drive the improvements with leadership and good taste.
I turst they will take the best course of action.

@kas1e
I know those ones were made by Mason but how many years ago? (or were they made recently?) Maybe he can make newer ones?

_________________
SamFlex Complete 800Mhz System + AmigaOS 4.1 Update 4
Amiga 2000 DKB 2MB ChipRam GVP G-Force040 Picasso 2 OS3.9 BB2
AmigaCD 32

@samo79
And yes, you are quite right this theme thing is getting too big (my fault too), better leave kas concentrating on more important stuff as you say.

_________________
SamFlex Complete 800Mhz System + AmigaOS 4.1 Update 4
Amiga 2000 DKB 2MB ChipRam GVP G-Force040 Picasso 2 OS3.9 BB2
AmigaCD 32

@DAX
Quote:

I know those ones were made by Mason but how many years ago? (or were they made recently?) Maybe he can make newer ones?

Few days ago. What exactly you dislike ? button for navigation ? Its just buttons from AISS (to make looks of browser "amigaos4ish").

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@DAX

You mean this Mason theme for OWB MUI ?
It' only 1 week old !

@Kas1e

Yeah, i believe you 100% as i see you fighting everyday with this monster, and there are also Denill and Slash into this battle !

Last edited by samo79 on 24-Feb-2011 at 10:42 PM.

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@kas1e Quote:

mui-owb for sure not "easy port". And there is tons of problems which i can't call "lot easer".

I did not say it was easy: But rather that it is easier than writing something from scratch... at least if you have some understanding of the elements involved.

If ports were HARDER than writing from scratch, then we would see rather less ports, and rather more "native" programs... surely? I mean, you wouldn't be porting MUI-OWB, if you thought writing Reaction-OWB (from scratch) with same features would be easier, right?

Ports mean: A lot of head scratching to get stuff to work. But a port also means: Not having to spend ages designing, implementing, experimenting, going back to the drawing board, refactoring, improving, iterating, getting conflicting suggestions from users, tracking down algorithmic bugs & design errors, etc.

So usually the headscratching effort is a lot less effort, unless the porting requires that you effectively rewrite the half program. (Which in the case of (say) the more complex Windows programs might well be the case.)

Quote:

The only pluse that its of course progressing faster , and better loose 2-3 months for porting, than 2-3 years for developing.

You actually seem to agree with me

Last edited by ChrisH on 24-Feb-2011 at 10:52 PM.
Last edited by ChrisH on 24-Feb-2011 at 10:51 PM.
Last edited by ChrisH on 24-Feb-2011 at 10:49 PM.
Last edited by ChrisH on 24-Feb-2011 at 10:48 PM.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@ChrisH

Quote:

If ports were HARDER than writing from scratch, then we would see rather less ports, and rather more "native" programs... surely? I mean, you wouldn't be porting MUI-OWB, if you thought writing Reaction-OWB with same features would be easier, right?

Nope.

If i know 2 months ago, how much its all requred to make a normal port of mui-owb, and if i will be good programmer (i am not), i will start one more from scratch. All the other usuall ports always much-much easy, because they mostly SDL/OpenGL + c/c++ , what mean totally "the same api" in most cases.

As you remember maybe, all of this starts because Joerg can't give to anyone normally full sources, for updating RA-OWB (but starting writing one more RA-OWB its just a mess), and because of it, we start all that mess.

But yes, i still think that better spend 2-3 month for porting (even if it hard porting, and all the hard stuff in the past already), in compare with recreating the wheel and make the same as Fab do for 2 years.

Last edited by kas1e on 24-Feb-2011 at 11:09 PM.
Last edited by kas1e on 24-Feb-2011 at 10:57 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Btw I was reading your crashlog posted to Amigans.net while ago.

Quote:

Dump of context at 0x020991F0 Trap type: ISI exception Machine State (raw): 0x1200F030 Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on] Instruction pointer: 0xDEADF00C Crashed process: owb (0x669E3BA0) ISI verbose error description: Instruction fetch in non-execute segment 0: 68C1E0CC 65381060 DEADBEEF 68C1E128 68C1E13C 6288AB9C FFFFFFFF 00000000 8: 00000000 00010000 11CE4A80 6FDD67CC DEADF00D 654AEAD0 00000000 00000000 16: 668FB380 7E9D2298 00000000 6205B59C 00000000 653817D9 640A84D8 61ECB418 24: 00000000 FFFFFFFF 68C1E090 68673A30 68AD0000 653810D8 6288AB9C 68C1E13C CR: 59533E95 XER: E000BE6F CTR: DEADF00D LR: 7FFF690C

It looks like OWB is trying to branch into illegal address which is result of using uninitialized memory somewhere. In Mungwall, 0xDEADF00D is used to mark allocated but unitialized memory and in OS4 it is probably same.

You probably should check if LR (0x7fff690c) is pointing to a program code. Is there SegTracker functionality in OS4?

You should also try to retrieve stack dump. This does not look it was a buffer under/overflow situation.

Side effects are quite interesting:
Quote:

Trap type: DSI exception Machine State (raw): 0x0200F030 Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on] Instruction pointer: 0x7FFFB060 Crashed process: DigiClock (0x665E0550) DSI verbose error description: Access not found in hash or BAT (page fault) Access was a load operation

(Having slow day at the work today... and it is raining...)

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook