scm branch cleanup

// January 14th, 2012 // Uncategorized

So now that 1.3.1 is out of the way, we’ve cleaned up the branches in git.

There are now two main development branches available:

1.3
The branch formerly known as 1.3.1. This branch will be the base for an eventual 1.3.2 release. Mostly bugfixes should go in there but maybe some improvements will find their way into this as well.

master
The main branch and the base for any 1.4 development. This will be an unstable version (1.4.0-SNAPSHOT) for a while but all the new nifty things will be in there.

While speaking of 1.4 there is not yet a final plan for it. We’ll need to sort out all of the bug and feature requests first. Please feel free to suggest other things you’d like to see in the comments or on the forum.

Both branches are available at sf.net and at github. Synchronizing both repos is a manual process at the moment but works pretty good thanks to git!

Ah and one final word about the git repository at sf.net: Unfortunately the sf.net “code / git” menu lists the wrong repository. I’ve talked to their tech support on IRC and this can’t be changed at the moment :/

The “develop” menu has the correct URL which is:

git clone git://nifty-gui.git.sourceforge.net/gitroot/nifty-gui/nifty

So the correct URL ends with “nifty” and not with “nifty-gui”! Sorry about this =)

void

3 Responses to “scm branch cleanup”

  1. cghislai says:
    January 16, 2012 at 3:10 pm

    Hi!

    It would be great for 1.4 to see a more java-friendly API.
    - The java builders are great, but I often found myself building the whole tree then parsing it to get some Element/Controller pointers.
    Something like
    Screen screen = new Screen(“main”);
    Layer layer = new Layer(“layer”);
    layer.childLayoutVertical();
    screen.addLayer(layer);
    ScreenController ctrl = screen.getController();

    Or even better,
    screen.addLayer(new Layer() {
    initParam() {
    childLayoutVertical();
    }
    });
    - Concerning the findControl methods, why do we have to pass the class? Can’t we just get the interface and cast it ourselves if necessary?
    - In the control builder, one can pass a Controller instance ( controller(myControllerInstance); ). This is total useless as only the class name is taken into account. It would be nice to be able to pass a real controller instance that will be bound when the elemtn will be built.
    - When a new element is built, is it cached in any way? I use a windowed interface, and i notice a delay upon each window creation. It would be nice if i could create one once, then clone it if i need more instance. Somethinglike
    private static MyWindow instance = new MyWindow();
    //
    MyWindow newWindow = instance.cloneElement();
    newWindow.setController(new MyWindowController(Object someparam));
    myDroppableArea.add(newWindow);

    I mainly use java to build ui, and I often find some possible improvement. I should write them down as its quickly forgotten.

    Anyway, many thanks for this piece of code! You are doing a great job!

    Reply
  2. Polygnom says:
    January 19, 2012 at 10:41 am

    Wow, very nice you’re on GitHub now ;) GitHub is simply awesome :D

    Reply
  3. Luiz Felipe says:
    February 15, 2012 at 3:34 pm

    Hey, I am gonna use nifty-gui for my project and I think it’s very awesome what you’re doing!

    Please when possible update the wiki. I notice that with the simplest tutorials that are completely different and even use deprecated classes on the examples :)

    As soon as I get very familiarized with it, I’ll update it too. But right now, in the learning curve, the wiki is making me learn the wrong (old) stuff.

    Thanks again for the great library !

    Reply

Leave a Reply