Personally I don't mind the menus under the top bar (I'm a FF user and am very accustomed to those).

Of course finding a way to eliminate that fat side-bar (in whatever way) is something I think we should not even point out (I'm sure "some way or another" it will not be in the final build...)

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

@ Rogue

Quote:

AmigaOS menus have quite a number of constraints

Yes, the menu system is another hot candidate for a rewrite - it hasn't changed since 2.0 times. When programming menus you suddenly find yourself in real stone age, especially if you need dynamic menu content that reacts to the current state of your app's functions.

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition

Quote:

I've been compelled to throw a further donation on the pile over at Amigabounty I hope others feel the same way.

Oh go on then! Another donation made.

TrevorD

_________________
No, I don't need no reason, I'm just breezin'

i dontated to, this is worth every penny

Quote:

Yes, the menu system is another hot candidate for a rewrite - it hasn't changed since 2.0 times. When programming menus you suddenly find yourself in real stone age, especially if you need dynamic menu content that reacts to the current state of your app's functions.

Indeed, but if you use MUI and its class for menu you can dev menu in a more modern way that gadtools gives you, you can add dinamically menus, changing them when you want ecc... (obvious that into MUI sources menu are programmed in the same way a gadtools devs does, but a 3th part dev using MUI develops a menu in a more modern way)... Has Reaction a proper menu class OOP programmable?

Last edited by ShInKurO on 08-Nov-2009 at 01:28 PM.

Quote:

IIRC This is BitStream Vera. We will try to make the menus AmigaOS-menus; I am not sure however that this will be possible, mostly because AmigaOS menus have quite a number of constraints that might be too much for Gecko's menus - MacOS Firefox has MacOS style menus too, but they have a generally more powerful user interface anyway.

As alternative you can always ask to mason to build an Amiga skin for FF because FF has its entire GUI written in XUL, so it's totally reconfigurable from this POW I dislike that GTK/Windows skin on AOS

Ok. The Friedens brothers are on my "todo" list to give a ride on this Vette as in Avatar and Sauna etc. at summerdays night when the sun never goes down. (If wanted)

Play

propilkki

game while waiting!

If we get a virus free fast starting system with all net capabilities I would say:

Kiitos

Thank You

Gracias

Spaciba

and thats where my skills end..

The overclocked AmigaOne is waiting;)

Edit: Trying to donate 100¤ as a respect to the Amiga spirit seems impossible with a Mastercard from here. I give up. Hopefully the other Mozilla bounties go there then..
There are my 10 cents then...

Last edited by PR on 08-Nov-2009 at 02:10 PM.

@Rogue

Thanks for the update. And the port!

Quote:

There had been ideas on how to replace th gadget with something that does not require the window border to be used up. It's mostly a matter of time.

I hate to mention it but I think the old Windows way where the sizer was the bottom corner of the window frame would be a good idea. So for us the sizing gadget could be the same thickness as the frame. Bit smaller though, would that work?

@Rogue

Quote:

Quote: It's ugly because the scroll bar should be in there. We hope to be able to put the scroll bar into the window border. I am not sure, though, whether that is possible.

Yes but everytime there isn't a scroll bar in the righthand side?
There must be a way to have it change dynamically to be as thin as the lefthand side?


Quote:

Quote: The menu fonts look nice but AmigaOS doesn't have menus below the titlebar, we have them hidden IIRC This is BitStream Vera. We will try to make the menus AmigaOS-menus; I am not sure however that this will be possible, mostly because AmigaOS menus have quite a number of constraints that might be too much for Gecko's menus - MacOS Firefox has MacOS style menus too, but they have a generally more powerful user interface anyway.

What's so advanced with gecko's menus? In the users perspective it looks about the
same as Amiga?!? Other than being visable all the time rather than being hidden like the
Amiga's is. What about hide the Firefox menus and then slide them into the Timberwolf screen when a user press right mousebutton? This might be semi Amiga way of doing
things which would be way better than having the menus appear in the top of the screen
IMHO.


Quote:

Quote: The ugly border frame is a result of needing to fit that sizing gadget in. There had been ideas on how to replace th gadget with something that does not require the window border to be used up. It's mostly a matter of time.

Yes, I hope this will be done. I have always thought this to really ugly, even when I used
classic Amigas with OS2+.

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!

@Samwel

AmigaOS menus only support three levels of menu and there are limits on how many menu items you can have at each level.

The exact limits are:
max 31 menus
max 63 menu items per menu
max 31 sub items per menu item

The horisontal lines (NM_BARLABEL) that are sometimes put between menu items also count towards these limits.

Looking very impressive!

_________________
Probably Pegasos 2 G4 1Ghz 1GB DDR-system, ATI Radeon 9250, ESI@Juli PCi-soundcard, all running
AmigaOS 4.1 with latest updates, or a new powerful
Amiga! Fingers crossed!

Yeah! I'm shall waiting this browser for my Sam.
Congratulations for your work.

@ShInKurO

Quote:

Has Reaction a proper menu class OOP programmable?

Surprisingly, no - I guess it shouldn't be too hard to wrap BOOPSI code around the Intuition menu system. So that structure data is supplied/accessed via tags, and things like ticking or disabling menu items are done through methods.

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition

Looking forward to getting to play with a Beta of this... even an Alpha would be nice

_________________
A600 OS3.1 ACA620 | '030 A1200 OS3.5 | µA1-C 750GX OS4.1 | SAM460 OS4.1 | '040 A3000 OS2.1 | Christian Aid |

Quote:

Surprisingly, no - I guess it shouldn't be too hard to wrap BOOPSI code around the Intuition menu system. So that structure data is supplied/accessed via tags, and things like ticking or disabling menu items are done through methods.

I can't live without MUIC_Menu# classes, even if many MUI devs use GadTools menu programming in their sources, I don't understand why

I hope to see soon a Reaction menu class :)

Quote:

I hate to mention it but I think the old Windows way where the sizer was the bottom corner of the window frame would be a good idea.

Clicking on a thin little window frame doesn't appeal to an old guy with poor vision (like me).
It looks like we're making a big issue over something that can be controlled by GUI prefs. If you open GUI Preferences and change "Borders-Preferred Sizing gadget placement" to "Bottom Border" the right border will be small like the left border and the bottom border will be expanded to accomodate the sizing gadget. If the sizing gadget isn't embedded in a border it would make it difficult for a program to determine the amount how much display space is available. The system would need to tell a program that the window display area is "X pixels wide" by "Y pixels high" except at the bottom right hand corner where the display area is "X pixels - Sizing gadget width" by "Y pixels - Sizing gadget height". Of course the program would need to know that only applies if there there are no window scrollers; in which case the right hand corner has the same display dimensions as the main display area.
Setting your GUI prefs to display the Sizing gadget in the bottom border is a good compromise since the bottom border width then balances the window titlebar (dragbar) height. I can't believe people are nit-picking the window shape when we are on the verge of having a fully functional Internet browser. Personally, I'm a lot less concerned about the window shape that the contents of the window.

_________________
X1000 with 2GB memory & OS4.1FE

@all

I second and agree Xenic's comment fully.

One idea is putting resizing gadget into the title bar ! (Nobody thought that ever.)

@Friedens
Keep up the good work !

Last edited by Tomppeli on 08-Nov-2009 at 06:51 PM.

_________________
Rock lobster bit me. My Workbench has always preferences. X1000 + AmigaOS4.1 FE
"Anyone can build a fast CPU. The trick is to build a fast system." -Seymour Cray

@Thomas & Hans-Joerg

Nice screenshots to see, glad to see the good prgress!

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@Tompelli

Quote:

One idea is putting resizing gadget into the title bar ! (Nobody thought that ever.)

That feels very counter intuitive to me, how do you imagine that would work?

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Quote:

That feels very counter intuitive to me, how do you imagine that would work?

Why not ? Other gadgets are there too.

_________________
Rock lobster bit me. My Workbench has always preferences. X1000 + AmigaOS4.1 FE
"Anyone can build a fast CPU. The trick is to build a fast system." -Seymour Cray