Yeah, I'm not sure how this would work either.
>From a high level I would expect this behavior from the build:
1. Package lmms built without wine dependencies
2. Package lmm-vst built with wine dependencies, requires package lmms,
but only replaces the libraries that are linked to wine
What I'
I have been working on trying to get things closer since the time I
posted that. So I will try to do more to fix this. I think that I will
have to have different make scripts or something, because all the
package depends are predetermined. I may be able to override it and
tell the lmms packa
@Israel,
So I'm a bit confused about this new lmms-vst package...
I added lmms-vst-test and wasn't sure whether to install "lmms" or
"lmms-vst"
First I typed "sudo apt-get install lmms" but it listed Wine in the
dependencies, so I canceled it not knowing if that was the right package or
not.
So
On 03/19/2014 08:50 PM, Johannes Lorenz wrote:
>> We also need to ensure that these changes don't break any existing UI
>> elements. So if we make changes to how widgets are initialized, then all
>> the parts of the UI using that widget need to be adapted to those changes.
> Yes, though the number
Continuing the conversation in a separate thread... Originated from the Qt
Designer UI elements discussion...
On Wed, Mar 19, 2014 at 3:48 PM, Lukas W. wrote:
> Qt Designer has nothing to with any bundled libraries or the OS you're
> building on.
Right, and this is the part I'm trying to under
Tres, to be honest, I don't understand what you are suggesting here.
Qt Designer has nothing to with any bundled libraries or the OS you're
building on.
Qt is cross-platform, it supports Mac natively. How is there a need
for MacPorts?
Also, this is off topic, we should continue discussing your ide
>
> If it is just about library dependencies, CMake should be able to do the
> same.
>
Asking more questions here... doesn't QT Designer come bundled with the
proper libraries for this? The reason I ask is because the MacPorts
approach looks like a -- pardon my language here -- a bloated mess. We
> I know we spoke briefly about qmake and I don't understand enough to speak
> on it's behalf, but from what I've read QT Designer can tremendously help
> with creating OSX builds.
You can use both Qt Designer, Qt Creator and qmake independently. So we can
use Qt Designer without switching to qmak
> We also need to ensure that these changes don't break any existing UI
> elements. So if we make changes to how widgets are initialized, then all
> the parts of the UI using that widget need to be adapted to those changes.
Yes, though the number of changes will be very small (existing code will ju
On 03/19/2014 07:51 PM, Tres Finocchiaro wrote:
> Would QT Designer modeling potentially move GUI development into an IDE?
Well, optionally at least. I guess it's up to each developer which tools
they want to use.
--
Lear
Would QT Designer modeling potentially move GUI development into an IDE?
I know we spoke briefly about qmake and I don't understand enough to speak
on it's behalf, but from what I've read QT Designer can tremendously help
with creating OSX builds.
Again, this is speculative on my part, but from w
I would tend to agree with Vesa here on both points (consistancy, contrast).
If the contrast is not high enough, we may wish to work with the background
color of that dialog.
I'm not opposed to using black for text in the interface (I actually prefer
it) but at this point, even the volume knob ar
On 03/19/2014 07:05 PM, giakk...@hotmail.it wrote:
> [left: how I'd like it was | right: how it is now]
>
> I just edited a screenshot and made that part Negative (since the
> background color is 128,128,128, the negative is the same).
> So doing it by changing the font color may look a bit differe
On 03/19/2014 06:37 PM, Johannes Lorenz wrote:
> Hi again,
>
> so you'd suggest to simply add
>
> overloaded ctors with less parameters +
> setter functions +
> properties using these setters?
>
> If yes, I could do that.
>
>
We also need to ensure that these changes don't break any ex
Yes, that would be the most straight forward design. Thanks in advance!
Toby
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications.
Hi again,
so you'd suggest to simply add
overloaded ctors with less parameters +
setter functions +
properties using these setters?
If yes, I could do that.
- Johannes
> Hi,
>
> yes properties are better than value templates as the latter one lead
> to massive bloat, at least if
Hi,
yes properties are better than value templates as the latter one lead
to massive bloat, at least if you do not move the existing class to a
non-templated parent class. I guess however that using
template-classes is rather inconvenient, especially in Qt Designer
even though I admit that paramet
> It doesn't have to. Knob pixmap initialization etc. could be moved
> into a setter function for the knob type property. As long as the knob
> type is not set, the background is not drawn.
While I understand what you mean, I don't think it's good. A good example is
probably the lcd widget: There
Hi,
Here is the ppa:
https://launchpad.net/~israeldahl/+archive/lmms-vst-test/+packages
I am not sure if this will work. However, it did build (finally).
So, Tres if you could check and see if you can somehow install lmms-vst
that would be great.
I am not finding it in the repos so I am no
I think the easiest way to get documentation from our code for all involved
from seasoned lmms devs to those who are new and want to contribute doxygen
is the way to go.
On Wed, Mar 19, 2014 at 9:43 AM, Vesa wrote:
> On 03/19/2014 10:37 AM, Jonathan Aquilina wrote:
> > Out of curiosity, any c
On 03/19/2014 10:37 AM, Jonathan Aquilina wrote:
> Out of curiosity, any changes we are making are people using doxygen
> comments so we can generate documentation with them?
I try to remember to use them but I don't always.
We should probably write up some more comprehensive style guidelines...
Out of curiosity, any changes we are making are people using doxygen
comments so we can generate documentation with them?
--
Jonathan Aquilina
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is th
The concept is the same, or very close to it.
You make a fork on github commit your changes to the forked repo that you
have then file a pull request to have your stuff merged to the main lmms
repo.
On Wed, Mar 19, 2014 at 3:06 AM, Israel wrote:
> On 03/18/2014 08:28 PM, Vesa wrote:
>
> On 03
On 03/19/2014 05:37 AM, Tres Finocchiaro wrote:
>
> If the MDI can be worked out sure! I'd like it to get in!
>
>
> I finally found it! http://i.imgur.com/737JlhJ.png
>
> QT_X11_NO_NATIVE_MENUBAR=1 lmms
>
>
> To add it to a shortcut:
>
> gedit lmms.desktop
>
>
> Make "Exec" look like t
Marked for 1.0 milestone.
On Wed, Mar 19, 2014 at 5:01 AM, Tres Finocchiaro <
tres.finocchi...@gmail.com> wrote:
> Bug opened for the MDI/Unity/rogue toolbar bug:
> https://github.com/LMMS/lmms/issues/488
>
> Please post any testing results there using the QT_X11_NO_NATIVE_MENUBAR=1
> lmms comma
25 matches
Mail list logo
