Jump to content
IGNORED

New GUI for the Atari 8-bit


flashjazzcat

Recommended Posts

I wonder if perhaps you are letting Windows "get in the way", so to speak. You've already named the thing "Task Manager", which matches Windows. And now, you've outlined a design that will basically replicate the analogous tool on Windows; right down to everything being named the same. I'm not saying this is a mistake, but understanding your own assumptions as such might give you pause for thought toward a different design.

 

Jon's got more than enough material to pause for thought for the next 15 years. He's just had his head in the wringer for months working on the new multi-tasking system and getting things transferred over to cart. It would be nice if he could throw something like this together using whatever he feels like at the moment, as a basis, without having it scrutinized. It's not like this is something that is being finalized for release. Give him some breathing room.

Link to comment
Share on other sites

This GUI is really impressive. I would not have believed it was possible to do this on the Atari if you'd showed it to me back in the 80s.

 

The discussion of the CPU cost of drawing the pointer reminded me of something: In OS X, the pointer disappears when you're typing into a text field (to prevent it from interfering with your view of what you're typing), and only reappears when you move the mouse.

 

Borrowing this feature would let people turn the pointer off just by hitting a key. Worth a try? :)

 

Link to comment
Share on other sites

EDIT: I must say, your design looks damned cool:

 

I like the graph type you were using at first too. But I think that type works better visually when there is more space for drawing the peaks and valleys, and maybe even having the consecutive drawto points spaced by at least 2 pixels horizontally, so there's less crowding. I think you're keeping it compact in order to have room for the list of processes though, eh?

Link to comment
Share on other sites

FJC did a major step and demonstrated that real preemptive multitasking now finally really works on the 6502/A8 including visualisation inside the new GUI. Thats so impressive. Quite funny that people are more interested in the name of the Task Manager and the way how the graph is beeing displayed :P Maybe I am too technical oriented without any marketing abilities :D

Edited by Prodatron
  • Like 3
Link to comment
Share on other sites

FJC did a major step and demonstrated that real preemptive multitasking now finally really works on the 6502/A8 including visualisation inside the new GUI. Thats so impressive. Quite funny that people are more interested in the name of the Task Manager and the way how the graph is beeing displayed :P

 

Actually I'm more interested and impressed by what Jon has accomplished, by a long-shot. But... it's my job to pay attention to how things look, as much as Jon will tolerate me. :D

  • Like 1
Link to comment
Share on other sites

Jon's got more than enough material to pause for thought for the next 15 years. He's just had his head in the wringer for months working on the new multi-tasking system and getting things transferred over to cart. It would be nice if he could throw something like this together using whatever he feels like at the moment, as a basis, without having it scrutinized. It's not like this is something that is being finalized for release. Give him some breathing room.

Are you saying that my message was scrutinizing or that it encroached on FJC's "breathing room"?

Link to comment
Share on other sites

Quite funny that people are more interested in the name of the Task Manager and the way how the graph is beeing displayed :P Maybe I am too technical oriented without any marketing abilities :D

If by "people" you mean me, I would say that I could care less about "Task Manager" as a name for the thing. I was merely cautioning against allowing the overwhelming proliferation of Microsoft Windows to give rise to the assumption that this tool with similar function should be a clone of the Windows Task Manager.

Edited by pixelmischief
Link to comment
Share on other sites

@pixelmischief: For me the achievement is so huge from a technical point of view, that political stuff currently isn't interesting at all :D But of course I understand! The A8Gui is Mac related regarding the design, so maybe the apps should be called like on the Mac.

Edited by Prodatron
Link to comment
Share on other sites

Pretty much.

He's a big boy, Mr. Fish. Let the man speak for himself. If FJC feels at all judged or pressured by my statements, he should let me know. I'm an admirer and a fan, and would be happy to stfu if my opinion on the project is unwelcome. And inasmuch as I was not talking to you in the first place, you might do the same.

Link to comment
Share on other sites

He's a big boy, Mr. Fish. Let the man speak for himself. If FJC feels at all judged or pressured by my statements, he should let me know. I'm an admirer and a fan, and would be happy to stfu if my opinion on the project is unwelcome. And inasmuch as I was not talking to you in the first place, you might do the same.

 

If you're talking about the project you're talking to me as well. We welcome opinions, but it's a good idea be considerate of things you may not know much about.

Link to comment
Share on other sites

The discussion of the CPU cost of drawing the pointer reminded me of something: In OS X, the pointer disappears when you're typing into a text field (to prevent it from interfering with your view of what you're typing), and only reappears when you move the mouse.

 

Borrowing this feature would let people turn the pointer off just by hitting a key. Worth a try? :)

Sounds good to me. This would work well in a text editor, where window refresh will be about the biggest strain on performance in any area of the UI.

 

"Activity Monitor" since its profiling and eventually have tasks. One wonders how hard it would be to graph SIO usage.

Perfectly descriptive. SIO usage should be measurable in just the same way as with any other activity, since the SIO routines will be built into the OS. I had another idea, too, which I think would be invaluable for developers and - again - is found in OS X: the ability to create a logged snapshot of a task's supervisor calls and messaging activity.

 

As for the other points: simmer down folks. I didn't take offence at pixelmischief's remarks (and I trust this is evident from my response), so there's no real reason for anyone else to get upset either: after all, most of the UI elements in question haven't even been coded up yet. And pixelmischief isn't the first person to intercede with observations on UI design when I am up to my neck in machine code: this being a GUI, it's hard to clearly separate what's on the screen from what's going on underneath.

 

If I need unlimited breathing space, I can just keep away from the thread. But I like to post frequent updates when I put together something I find exciting (and which I think may be of interest to others), and I like to acknowledge the responses. This can take a bit of time, and it can be distracting, but given how off-topic this thread has gone in the past, I find nothing objectionable about a query on UI design which was (hopefully) answered with a couple of friendly sentences. I would claim the monopoly on being ratty for myself at the moment, anyway, after slogging away for about eight weeks straight. :D

Edited by flashjazzcat
  • Like 1
Link to comment
Share on other sites

I like the graph type you were using at first too. But I think that type works better visually when there is more space for drawing the peaks and valleys, and maybe even having the consecutive drawto points spaced by at least 2 pixels horizontally, so there's less crowding. I think you're keeping it compact in order to have room for the list of processes though, eh?

The list of processes will go on a different tab. If you check out the SymbOS task manager (which I'm using as a template for now, since it's good-looking and functional), the lower half of the performance tab is taken up with "Totals". The graphs could still be a bit bigger, though: they're currently the size they are to minimize the bitmap storage overhead (100 bytes per graph). In truth, they'll probably have to be bigger once the titled frames are added.

Link to comment
Share on other sites

The list of processes will go on a different tab. If you check out the SymbOS task manager (which I'm using as a template for now, since it's good-looking and functional), the lower half of the performance tab is taken up with "Totals". The graphs could still be a bit bigger, though: they're currently the size they are to minimize the bitmap storage overhead (100 bytes per graph). In truth, they'll probably have to be bigger once the titled frames are added.

 

Yeah, I know how Windows and SymbOS' task managers are setup. I thought you might be putting something a little bit more abbreviated together to start with. I'll try not to interject too much. I know you like to play around with designs some yourself.

Link to comment
Share on other sites

what makes me confident is that nowadays there are so many new devices and expansions so an new OS can fully take advantage... (RAM, RAM carts etc)... maybe I missed important notes in the thread (I am more into Fractals right now so more game/demo mode and not OS ;)) what will be the min. system specs to run this?

Link to comment
Share on other sites

Of course the wait prior to erasing (until VCOUNT has ticked over eight times since the NMI fired) could be used to perform other useful work, I guess.

 

Thanks for the explanation! Thought a little about the constraints and had no better idea instantly. (Only such crude things like copying the screen lines under mouse pointer to an other buffer, putting the mouse on it and display that buffer by LMS changes in display list, so original screen data isn't touched. When reducing output frequency, this could go on cycles on par... ;) ).

Regarding the VCOUNT wait: Since graphical output is forbidden, wouldn't that be a good place to prepare some work for the scheduler?

Link to comment
Share on other sites

Yeah, I know how Windows and SymbOS' task managers are setup. I thought you might be putting something a little bit more abbreviated together to start with. I'll try not to interject too much. I know you like to play around with designs some yourself.

Well, I'd be interested to see the MrFish visualisation of an activity monitor containing the same functional elements as the SymbOS Task Manager. :) The salient point about the graph is that its height should optimally be a factor of 100 - i.e. 25 or 50 lines. If the graph is 25 lines high, we convert the percentage value into the peak value thus:

 

LSR @

LSR @

 

No need for any fancy division routines. I think when the right graph has "Memory" written above it, the graph will need to be at least forty pixels wide otherwise it'll look unbalanced. So that's 40 by 25 (125 bytes), or forty by fifty (250 bytes). The latter (nearly a page) is probably the optimal size for the graph, and offers a good level of detail.

 

...what will be the min. system specs to run this?

I expect the minimum specs to realistically be XL/XE, 128KB, mouse, disk drive.

 

Regarding the VCOUNT wait: Since graphical output is forbidden, wouldn't that be a good place to prepare some work for the scheduler?

I was thinking the same thing, although the mouse pointer NMI is "elastic", unlike the scheduler IRQ which happens at a fixed position in every frame. But it's a really appealing idea!

Edited by flashjazzcat
Link to comment
Share on other sites

Frames and string controls done, tabs next:

 

post-21964-0-41322200-1409517852_thumb.png

 

Note: I make no presumptions about this being a finalised design for the activity monitor, especially since I've yet to see what kind of visualisations MrFish is cooking up. I think the size of the dialog box font will be up for discussion. I'll get my hand slapped for using the icon font here, but it does seem to strike a nice balance between readability and compactness. Regardless of whether this particular dialog ends up looking this way, good use of limited space is always going to be a prime concern.

 

Probably exacerbated by uncertainty about general design guidelines and font choice (and thus control spacing), but boy I am already hankering after a resource editor. :)

 

  • Like 6
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...