Re: [Jsynthlib-devel] First step towards support for the Yamaha SY85

[Daniel R. <dr....@co...>]

> Link for QT would be
>
> http://www.qtsoftware.com/products/appdev/programming-language-support
>
> but it's true that the QT effort for Java looks quite dead or dy ing.
>
> Anyway, regarding your questions:
>
>
> On Sun, Aug 9, 2009 at 10:45 PM, Peter Geirnaert <
> pet...@gm...> wrote:
>
>> Hi Daniel, all ...
>>
>>
>>> I do NOT use (nor believe in, but I could be convinced) any Swing
>>> designers.
>>> I wrote all of my Swing code by hand, using the designer in JBuilder
>>> (still
>>> out there somewhere) to figure out how to do certain things layout-wise.
>>
>>
>> I too believe after some study work, it must be possible for a coder to
>> write by hand.
>> After all, you had to write library support first, so you have to be able
>> to write UI code by hand.
>>
>>
>>> I don't know the state-of-the-art regarding Swing designers (nor have I
>>> ever
>>> looked at Netbeans for anything but straight code/refactoring/SVN), but
>>> my
>>> opinion from what I've seen is that it's hard going. Real code always
>>> causes
>>> designers to break.
>>
>>
>> So what would it do to musicians ? Anyway, if someone wants to get his
>> hands dirty on System Exclusive, there must be some coders-spirit already.
>> Just make a switch from design-mode to code-mode in the little grey cells
>> ...
>>
>
> Yes, but this is unfortunate: UI work is mostly repetitive and
> pattern-based. One of the main problems with Swing is always the layouts. Of
> course, there are tons of articles and books on that. Also, you'll have to
> learn the Adapter/Adaptee structure for firing methods from controls. It's
> simple, but it's a structure that needs to be copied (learned).
>
>>
>>
>>> (Irrelevant but noteworthy: .Net winforms designer in
>>> VS2005 or 2008 is great, and can handle your code moving forward).
>>
>>
>> How do you mean "can handle your code forward" ?
>> Do you mean like JSynthLib is "stuck" in an old way of coding software ?
>>
>>
>
> No, sorry, I was referring to Java IDEs. JSynthlib looked fine to me.
>
>
>>
>> Out of curiosity: what is wrong with the initComponent? It's probably
>>> called
>>> by the constructor, and if not, you can always make it public...
>>
>>
>> Hm, thanks for the tip, I'll investigate it because I didn't know why it
>> would be wrong.
>> I simply didn't see it used in other editors, and jumped to conclusions
>> ...
>> (I still have to test my first patchEditor)
>>
>
> Yeah, if I remember correctly, you always put your stuff in an init method
> (arbitrary name) because it has to be called after the form has been created
> (or some event like that: this is all standard stuff to be copied).
>
>
>>
>>
>>> That said, if I were to do any Java projects right now, I would take a
>>> serious look at whether the UI could be done with QT or something. *Not
>>> sure
>>> if that would jive with the Swing stuff that JSynth is already using.*
>>
>>
>> Well, that looks interesting, I found this project on Sourceforge:
>> QtJava <http://sourceforge.net/projects/qtjava/> but it's like no longer
>> supported or developed.
>>
>> I guess I'm having enough extra work already 'blogging' about writing a
>> driver,
>> it's probably best if I just do it the traditional JSynthLib way.
>>
>> BTW, I have some troubles opening the preferences window in JSynthLib, but
>> I'll write about that under another subject title, tomorrow, maybe ...
>>
>> Happy summertime ;-)
>> Peter
>>
>
> Cool, enjoy and good luck.
>