Important: Please read the Qt Code of Conduct -

Black Cat Cutting Studio: Introducing Adaptive Interface Technology

  • Black Cat Cutting Studio aims to be the first implementation of the "Adaptive Interface": technology in a Qt / Qt-Quick environment.

    The development is open to followers and contributors, especially developer that will help the development and testing of this Qt-Quick strategy implementation.

    (informations on the application from the introductory pages)
    Black Cat Cutting Studio is a mix of graphic management and device control. The package works on svg files that can be managed with some essential graphic primitives and can interact with cutting plotters (almost all devices of this kind). Most of the features excluding the basic functionality will be released as plugins that can or can't be activated by the user.

  • Lol, in the page wiki of project there is a label QT.
    QT is QuickTime... this is Qt.

  • :D:D:D

    Great! I hate QT ;)

    Ok, thanks, I remove it immediately.

  • From your description here, but also from the page you link, I still have no clue what this should do, or how it should be accomplished. I find the descriptions very confusing. It seems you are talking about two things:

    an application to control "cutting plotters". Fine, could be fun.

    some kind of framework technology that is being used in 1), should work on all devices with all possible screen resolutions and input methods, and be based on Qt Quick.

    Did I get that right?

  • Exactly. The description is not yet complete, sorry, but it is a work in progress: the documentation will follow the development.

    The application is a real work, and discussing with the client I explained him my reasons and he agreed that "opening" this project is the best thing we can do, sharing with this community.

    In the meanwhile, I experienced that the problem in application interoperability is not mainly the logic of what the program can do itself but the difficulties that you can find to "port" a desktop application on a tablet, or smartphone, or embedded platform. The real differences are not simply the screen resolution:

    bq. The scope is to build a user interface that can work under (almost) all the QT supported platforms: from desktop computers to smartphone and tablets. An in-depth analysis of the user experience on different platforms i.e. touch devices and desktops reveal more than the obvious, well-known differences like the screen resolution or the user interaction adopted method (mouse, pen, touch screen, keyboard etc.).

    Thus I decided to find a way to define objects with adaptive behaviors influenced by screen resolution, interaction methods and other ergonomic parameters.

    As a matter of fact I am working to implement this approach (strategy or technology?) also on other projects, but Black Cutting Studio is where I take a clear track of what this means (as possible), how it can work and all the needed examples. I have the goal that releasing the version 1.0 (at least beta) there is also a sufficient number of informations, examples and tests to have a white paper.
    This will happen not later than the end of next April.

  • So, I gather that this announcement is really a bit premature, as there really is nothing but vague ideas with no clue about a possible direction to take for a real solution?

    Personally, I don't think the idea of creating a single set of components that endlessly support different screen resolutions and interaction patterns is a viable strategy. I think the way to deal with these differences, is to make sure you separate your application logic from your UI logic religiously, and develop different UI's for different platforms on top of on that application logic. I don't see how one set of components is going to support the very different types of interaction that are made possible or feel natural for all the different platforms you target.

  • It's always to discuss with you.

    Andre, this is not a announcement like "I created a new technology!!!", It will be a big fake :)
    And I don't started any thread forum in some appropriate area for the same reason. I put this announcement in this talk section - as suggested by another user - to notify that there is a project active, and all the users that like to contribute are welcome.

    bq. make sure you separate your application logic from your UI logic religiously

    :) This is the first think I have done when I starting to work with "small things" in 2002 when Nokia forum was very very little and Pal OS was one of the great OS for embedded platforms (... nostalgy ...)

    What you tell about the development of different interfaces is partially true, but there are some behaviors that can be "translated" in different environments, taking care of ergonomy and the feel the user will have.

    I don't think to something that compromise a platform against another, I think to an abstraction of some behaviors that take a different interpretation depending by the hardware platform where they "live". It's a principle of the technological ecosystems.

Log in to reply