Stachu knows what needs to go into a functional GUI, as he's used mine plentyHe just wanted to release it before it was done so he could get some feedback on what IS done.
Stachu knows what needs to go into a functional GUI, as he's used mine plentyHe just wanted to release it before it was done so he could get some feedback on what IS done.
The "ambiguous states" supported by ACube do not seem to merely correspond to cubies with some facelets grayed. I'm not sure if masterofthebass's GUI is an ACube front end or not, but the Heise one certainly is designed to be just that, and has support for the exact same type of ambiguous states that ACube (the old version) supports. It also seems Stachu hadn't explicitly been planning on supporting swapping and twisting/flipping cubies. His response to me doesn't seem to say anything about if swapping will be supported. (By the way, Heise only supported swapping without any orientation change, regardless of which facelets were selected for the swap. That's what I considered "incorrect" about his implementation of swapping.)
As for the input format for "separation" support, I didn't have anything particular in mind, either for GUI or command operation. For command operation, perhaps "UX" for an edge or "UXX" for a corner (actual X letters, or could be a punctuation character like ^ or something) to indicate a cubie that must go into the U layer, with the assumption of possibly being combined with orientation info (@,+,-). As for GUI interface I don't even know what Stachu has in mind for displaying the existing ambiguous cubie types. Will it be like Heise, or something different? Until I know more I think it's premature to suggest something for separation support.
Last edited by cuBerBruce; 07-15-2011 at 03:27 PM.
My GUI is a frontend written in Python that interacts with the ACube jar. Unfortunately, my method of interaction was tied into a python library that isn't very well supported, and it only works to an extent in linux environments. It uses PyGTK and Twisted, and does everything you would need from ACube (full cubestate definitions, full access to turn restrictions). It was inspired a lot by Ryan's frontend, but provided more integration and some minor improvements. If you'd like the source, I can give it, but don't expect it to be very polished
--edit--
With a little bit of fiddling, I got it to run on OS XHere's a screenshot:
![]()
Last edited by masterofthebass; 07-15-2011 at 05:04 PM.
So indeed you seemed to support the ACube ambiguous states in basically the same manner as the Heise front end. And even the same cube manipulation commands as Heise. I don't think I really care for a Python/Linux app, though.
Actually, I was using ACube the other day and was thinking of converting my own C# CubeApp program to be a front end for ACube, given the awkwardness of using the Heise front end. That was before I noticed what Stachu was working on. Now I'll probably wait until ACube4 and/or Stachu's program.
Anyway, here's what my CubeApp looks like. I guess I don't have support for "swap cubies" yet.
I plan to implement all features of acube, both current version and all future ones. I also plan to implemnt *all* of the features provided in Heise's GUI, as well as the features in CubeExplorer. With this, serious work will have to be donr to make sure the GUI isn't too crowded and noisy. Does this answer all questions?![]()
Make it fool proof.
hao 2 fix?
![]()
Some small updates:
-cube starts off with colors filled in rather than blank.
-secret functionalities regarding incomplete cubes finally under way
-fixed a bunch of minor bugs, and reworked code
Next:
-incomplete cube and piece-swapping functionalities.
Again, let me know your thoughts.
Bookmarks