Hi, Tres, all,
2015-06-15 9:30 GMT-03:00 Tres Finocchiaro <tres.finocchi...@gmail.com>: > > Being honest what caught me was the MIDI OS X bug, as it was something I >> sadly experienced. I'll take a look at it. I just need to clean up some >> free space. > > > Great. > I'm setting the development environment on OS X. I'll take a look at it soon. > > > When those mock-ups materialize, LMMS will be outstandingly gorgeous. >> S2 Me gusta S2 > > > *If *they materialize, not when. > It's on our hands. > > > The Java-only idea some people have about Android is a myth. > > > No one said "Java only". Regardless, converting our interface for touch > is the lowest of priorities. I'm not sure why you are pressing this point. > Just a pet peeve. In fact I miss a DAW with such characteristics (portability, availability, power, interoperability, built-in collaboration). Please don't understand what I said as a pressure. But just as something I believe some people would like to have, just like me. If enough people find it useful and desirable, sometime someone will write support to it. I'm aware there's a lot of way more important things to do right now, and maybe I'll be able to help and not just talk. Time will tell. > > > if you don't touch Apple's App Store you're safe. > > > If you don't touch Apple's store, there's no real point in releasing the > software <http://stackoverflow.com/a/982549/3196753>. > Some <http://9to5mac.com/2015/06/10/xcode-7-allows-anyone-to-download-build-and-sideload-ios-apps-for-free/> people <http://www.cultofmac.com/325932/xcode-7-lets-everyone-install-pirated-apps-and-emulators/> may <http://bouk.co/blog/sideload-iphone/> disagree <http://www.pocketgamer.co.uk/r/iPhone/Emulation/news.asp?c=65781> with <http://www.iphonehacks.com/2015/06/xcode-7-allows-people-to-download-build-and-sideload-ios-apps-for-free.html> you <http://www.iphoneincanada.ca/news/how-to-sideload-apps-iphone-xcode7/>. Of course it would not be everyone that could walk the extra mile and compile him/herself, but being able to would be a nice feature, don't you think? > > it would be fantastic to have a good, powerful, usable and free (as in >> freedom) DAW allowing us to create and share seamlessly across all major >> desktop and mobile platforms. But I can dream, can't I? > > > Yes, but if you are a self-proclaimed expert on this topic, dreaming > things that are not logical just causes confusion. > I didn't proclaim anything. I just said that I have working experience with it, so I'm saying what I find logical and feasible according to my knowledge. I'm not saying it will be easy or done in no time, and even less that everybody should ignore their tasks and follow me to Eldorado. I just brought to light some ideas I believe have some positive value, and bringing them and the answers to it help me to better understand LMMS's dev team and how I can fit in. > > Scaling for HiDPI displays will be done in Qt 5.6, and experimental in >> Qt 5.5 (just around the corner). Maybe moving in Qt's direction would be a >> wise choice. > > > QtLinguist already handles this well. > I claim no contest. > > > SVG: Qt Quick/QML already offers support to it. If/when the Big UI >> Overhaul uses it, the SVG, theming and portability issues will be almost >> fixed by themselves, so to say. > > > No, we don't need a GUI overheaul to start this and the decision. We can > use SVGs now. No need to defer and no need to propose (or wait for) the > entire GUI is switched to QML. > Yes, LMMS can use, just as KDE4 used to. My point was using Qt 5 features would allow LMMS to handle such issues in a simpler, clearer, more compatible way. Of course I understand too that rewriting a GUI is having a lot of work and spending a huge amount of time to reach the point you already are, and most times such effort is unjustified. WireShark did switch from GTK+ to Qt because it would help them further, Inkscape sticks to GTK+ because they don't see a real gain in changing UI libraries. LibreOffice is still migrating from Gtk+2 to Gtk+3. You can justify it according to your goals and the effort needed to implement it. Migrating from Qt Widgets to QML has some valid points: - Qt Widgets on Qt 5 is frozen (by Digia's will) and will not receive updates. All the new and improved stuff will be implemented in QML support. - QML has 2D and 3D accelerated rendering support, which lacks on Widgets. Porting to QML, even if it is interpreted, may represent performance gains in UI. I don't have hard, cold data to corroborate it, but Digia claims it's the case. - QML and Qt Widgets can coexist. Porting may be done at a calmer pace, and no loss of functionality or usability would happen. Changes could come gradually. New UI elements should be implemented via QML. - Implementing UI features as SVG support, themeability seems to be done in a simpler fashion with QML. Restructuring all the UI, if some theme writer so wishes, would be feasible. - With the proper MVC implementation and low level platform support in place, porting to other platforms would be a matter of simply writing a theme adapted to the target form factor. But as everybody knows, there are more important issues to be fixed right now. But having some perspective and spotting certain bogeys on radar is healthy. > > In my humble opinion enforcing LMMS to compile against Qt5 will be an >> excellent goal that will allow further development in a faster pace. > > > Then jump in and help. :) > /me jumps doing a "duplo mortal carpado <http://demotu.org/x/daiane/>" (double twist L-shaped jump - "if I don't die on the spot maybe I'll walk again in some years - hopefully"-kind of jump) > > - tres.finocchi...@gmail.com > > On Mon, Jun 15, 2015 at 7:49 AM, Amadeus Folego <amadeusfol...@gmail.com> > wrote: > >> Hi Cláudio, I noticed by your name that you might be Brazilian. >> >> If you are nearby São Paulo let me know that I can help you with a >> hands-on approach. >> >> Thanks, Amadeus. >> > >
------------------------------------------------------------------------------
_______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
