Build 9 has the beginnings of a GUI

[Freddie]

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.

[Ualaa]

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

[Freddie]

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!!

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.

[TheFallenOne]

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

[papounet]

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)

[Freddie]

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

[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.

[Edit: found an explanation in the previous thread:

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

[Freddie]

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?

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?

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

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.

[Maxion]

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

[Flekkie]

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.

No worries - it's not exactly the core function of the program, and prolly too early to do more than start thinking about it. I just jotted it all down in a lazy moment in front of the TV, it wasn't a huge effort. I'll throw in some lol speak next time so it doesn't come out so formal

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?

If I was sat at PC1 and moused onto PC2's monitor, then intuitively I might expect all keyboard actions to be exactly as if on PC2's local keyboard - is that what you mean? So if the Mojo settings on PC2 were not to broadcast then potential for confusion?

Trying to clarify before I go off on one

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.

ATM, the button is green background + solid letters for on and no background + solid letters for off. I meant to suggest no background + grey letters for not applicable, as a way to indicate the function is there but does not apply to current setup.

Similar to Firefox, click the History button on the top menu bar, and the Forward option is greyed out unless there is an actual web page to go to.

But just not showing it at all unless needed is a nice idea to keep all confusion to minimum. Would someone who was used to seeing it there be confused if it disappeared?

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."

Here is where I can't really give feedback without a second PC to see how it currently works. Do you mean there are potentially 2 mouse pointers, say PC1 and PC2 again, and an option for either or both to be on a given window? I had assumed toggling mouseover from PC1 on would automatically toggle mouseover from PC2 off, and vice versa.
Or just the option of allowing mouseover from PC1 to PC2 but not from PC2 to PC1?

But for any devious permutations, could you have an option in a settings menu somewhere to switch to advanced mode where the buttons work differently? EG toggling between more than two options, or acting like drop boxes? Or else a separate advanced settings screen to define what exactly each option means.


i can do lol speak nao? So u doht think i tryed too hard ^_^