Build 9 has the beginnings of a GUI

Build 9 has the beginnings of a graphical interface.

Up till now, when Mojo started, it assaulted your eyes with a screenful of programmerish gobbledygook.

The new opening screen is (I hope) less scary. It displays pictures of your computers.. They are color coded to indicate Mojo's connection status. Blue means fully connected, gold means partly connected, and black means unconnected.

The old screen with the gobbledygook is still in the program, but you have to press a button now if you want to see it.

There are a few other small changes in the build, but that's the big one.

The main thing to test is whether colors change correctly as copies of Mojo start and stop on the network.


http://mojoware.org/art/build-9.gif

Mojo is coming along nicely.
It is interesting to see the process, from build to build.

Very nice! Love the progress so far. Keep it up!! :D

From the explanation of the earlier build, I took that majo is different from HKN because the focus window gets all keycodes allways.

Things I liked in HKN was the possibility to have:
- inputkeys eaten by HKN (like the keys i usd for PIP switching, or the keys used for internal processing or the keys used for formation)
- inputkeys send only to activeindows (like / starting the chat and keeping all keys private till Enter)
- inputkeys eaten for the active window but send to target windows (either by modifier key or by clicking in the PIP window, making it the active window) (for example to trigger a spell only by one character)

One thing I am investigating with HKN, but I can only do with modifier key (or perhaps using something like Clique)

Quote:

---

Originally Posted by Ualaa

Mojo is coming along nicely.
It is interesting to see the process, from build to build.

---

Quote:

---

Originally Posted by TheFallenOne

Very nice! Love the progress so far. Keep it up!! :D

---

Thanks for the encouragement! I appreciate it. :)

It's interesting to me too, because I have only a vague idea where I'm headed with the GUI. :) I'm going to put more screens with pictures in the program today in hopes of getting feedback and suggestions from people here.

Quote:

---

Originally Posted by papounet

From the explanation of the earlier build, I took that majo is different from HKN because the focus window gets all keycodes allways.

---

Mojo will do everything that HotkeyNet does, and much more.

When you look at a Mojo build today, you are seeing only a tiny fraction of the features that Mojo will have. This will be true for a long time.

Mojo is only a baby. Babies can't walk or run, but when they grow up, they will walk, run, jump, and maybe even go to the moon.

http://en.wikipedia.org/wiki/Iterati...al_development

Is it supposed to stop broadcasting if mouseover is on? Both buttons were lit up green (on), but I only get broadcasting with mouseover off.

[Edit: found an explanation in the previous thread:

Quote:

---

I deliberately kept broadcast and mouseover somewhat separate in this build because potentially they can interact in bad ways and I'd like to get them both debugged first.

---

so I guess thats's the reason, sorry.]


Also, since it knows I only have one Mojo'd computer, should it grey out the Mouseover button?

Freddie, this is looking nice, I will have to try very hard over Christmas not to be tempted into a second PC :p

Quote:

---

Originally Posted by Flekkie

Is it supposed to stop broadcasting if mouseover is on? Both buttons were lit up green (on), but I only get broadcasting with mouseover off.

---

By the way I'm sorry I haven't gotten back to you about the scrolling messages. You did a huge amount of work and believe me, I haven't forgotten.

I don't have a strong opinion yet but I'm inclined to think that the local PC should stop broadcasting outward when its mouse is moused over to a remote.PC. I may be mixed up but think the earlier question was about something else, whether the remote PC should broadcast outward when the local PC's mouse is on the remote's screen and the user is typing on the local keyboard.. The second case (broadcasting at a remove, as it were) could get pretty confusing for people.

What do you think?

Quote:

---

Also, since it knows I only have one Mojo'd computer, should it grey out the Mouseover button?

---

Hmmm.

I think it depends on how Mojo knows you have only one. If it knows because you checked "one PC" on settings, then I think maybe that button should become invisible rather than grayed out. (However I'm thinking of removing that setting from the program to make it as simple as possible.)

If, however, Mojo knows because it hasn't found any PCs to connect to, I think the button should remain working because people who *do* want to mouseover but only have one Mojo running at the moment might want to see if the button is "pushed" or not.

If the button turns gray for two different reasons, (1) the user "unpushed" it and (2) the program did it automatically because no Mojo's are seen at the moment, I think that's bad interface design. A visual indicator should mean one and only one thing imho.

Another issue is inbound mouseover vs. outbound mouseover. Inevitably, some people will want to fine tune it like that. But I don't want to put six buttons on window. Andit could be eight buttons, because eventually I'll probably implement both "broadcast to windows" and "broadcast to PCs."

What do you think?

Quote:

---

Freddie, this is looking nice, I will have to try very hard over Christmas not to be tempted into a second PC :p

---

Hehe well if you want an excuse to wait, Intel is coming out with new 32 nm cpu's in January. That might be worth waiting for. :)

Quote:

---

Originally Posted by Freddie

Hehe well if you want an excuse to wait, Intel is coming out with new 32 nm cpu's in January. That might be worth waiting for. :)

---

Sounds expensive :p

Quote:

---

Originally Posted by Maxion

Sounds expensive :p

---

Probably, but wouldn't that hopefully drive the cost of current CPUs down?