SQuirreL SQL Client

On 5/28/07, pjsong <pjsong3101@...> wrote:
> File StringManagerFactory has a member s_mgrs , i know it's a collection of StringManager objects keyed by javapackage name, but i don't know when this HashMap was initialized. when the key and it's value was added.

The StringManager for a given package is initialized when the first
class in that package is statically initialized if the class has a
class variable declared such as :

private static final StringManager s_stringMgr =
StringManagerFactory.getStringManager(<class>)

Search the source code for the variable named s_stringMgr - you will
find many examples.

Rob

It's ok.  Each class in a package will make this call, but only the
first class that is loaded in a given package will cause the key to be
stored for a new StringManager for that package.  Every class in that
package after the first will see that the key is already in the map,
so no new StringManager is created.  My guess is that somehow your
breakpoint occurred after the first class in the package made the call
- so the key you were looking was in the map already.

Rob

On 5/28/07, pjsong <pjsong3101@...> wrote:
> Sorry i don't get the idea very much. When debugging I have traced from code in class Application
>
> private static final StringManager s_stringMgr =
>   StringManagerFactory.getStringManager(<class>)
>
> to code in class StringManagerFactory
>
> StringManagerFactory.getStringManager(clazz){}
>
> Through Watch,  I noticed that Map s_mgrs has got its key-value upon debug's entering this call. But there has no one line been executed yet.  how s_mgrs get its value?
> Thank you very much !
>
>
> ----- Original Message -----
> From: "Robert Manning" <robert.m.manning@...>
> To: "pjsong" <pjsong3101@...>
> Cc: <squirrel-sql-develop@...>
> Sent: Monday, May 28, 2007 10:33 PM
> Subject: (????-??????????)Re: [Squirrel-sql-develop] question about StringManagerFactory's Map
>
>
> > On 5/28/07, pjsong <pjsong3101@...> wrote:
> > > File StringManagerFactory has a member s_mgrs , i know it's a collection of StringManager objects keyed by javapackage name, but i don't know when this HashMap was initialized. when the key and it's value was added.
> >
> > The StringManager for a given package is initialized when the first
> > class in that package is statically initialized if the class has a
> > class variable declared such as :
> >
> > private static final StringManager s_stringMgr =
> > StringManagerFactory.getStringManager(<class>)
> >
> > Search the source code for the variable named s_stringMgr - you will
> > find many examples.
> >
> > Rob
> >

On 5/28/07, pjsong <pjsong3101@...> wrote:
> My breakpoint is set at the very beginning of  the main function of  the main  class .
> The first class is Application, is it right ?
> Would you accept a screen-copy for  more detailed information?
> thx a lot.
>

That is not quite correct; the first class that loads a StringManager
is Version.java at line 46 in Main.java.  Version is the class that is
putting the "...client" package as a key into the s_mgrs map.  Set
your breakpoints at Main:46 and StringManagerFactory:84.  When you hit
the one in main, resume and the hit the next one.  Then inspect the
s_mgrs HashMap - it should be empty at this point.

Rob

Dieter Engelhardt wrote:
> I have added an new TabPanel to the via addMainTab().
> 
> How do i set this new tab to be selected?
addMainTab() returns an int. Call selectMainTab(int) with that int as parameter.

Gerd


> 
> Thanx
> Dieter
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

Hi Gerd,
this is what i expected, but the returnvalue of adMainTab is void:
 void addMainTab(IMainPanelTab tab);
Has this changed in the actual source? And what should i use instead?

Dieter

Gerd Wagner schrieb:
> Dieter Engelhardt wrote:
>   
>> I have added an new TabPanel to the via addMainTab().
>>
>> How do i set this new tab to be selected?
>>     
> addMainTab() returns an int. Call selectMainTab(int) with that int as parameter.
>
> Gerd
>
>
>   
>> Thanx
>> Dieter
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Squirrel-sql-develop mailing list
>> Squirrel-sql-develop@...
>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>>
>>     
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
>

Session.java (and the interface ISession.java) swallows the return
value of SessionPanel.addMainTab(IMainPanelTab tab), at line 604 of
Session.java

   public void addMainTab(IMainPanelTab tab)
   {
      _sessionSheet.addMainTab(tab);
   }

So, modify the interface for ISession and Session to return the value as in :

   public void addMainTab(IMainPanelTab tab)
   {
      return _sessionSheet.addMainTab(tab);
   }

I would do it, but at the moment CVS access at SF is unavailable - I
get connection refused.  I'll try to check it in later if no one else
gets to it first.

Rob

On 5/24/07, Dieter Engelhardt <Dieter@...> wrote:
>
>  Hi Gerd,
>  this is what i expected, but the returnvalue of adMainTab is void:
>   void addMainTab(IMainPanelTab tab);
>  Has this changed in the actual source? And what should i use instead?
>
>  Dieter
>
>  Gerd Wagner schrieb:
>  Dieter Engelhardt wrote:
>
>
>  I have added an new TabPanel to the via addMainTab().
>
> How do i set this new tab to be selected?
>
>  addMainTab() returns an int. Call selectMainTab(int) with that int as
> parameter.
>
> Gerd
>
>
>
>
>  Thanx
> Dieter
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
>

Sorry, the return type is not void, but rather int :)

    public int addMainTab(IMainPanelTab tab)
    {
       return _sessionSheet.addMainTab(tab);
    }

Rob

On 5/24/07, Robert Manning <robert.m.manning@...> wrote:
> Session.java (and the interface ISession.java) swallows the return
> value of SessionPanel.addMainTab(IMainPanelTab tab), at line 604 of
> Session.java
>
>    public void addMainTab(IMainPanelTab tab)
>    {
>       _sessionSheet.addMainTab(tab);
>    }
>
> So, modify the interface for ISession and Session to return the value as in :
>
>    public void addMainTab(IMainPanelTab tab)
>    {
>       return _sessionSheet.addMainTab(tab);
>    }
>
> I would do it, but at the moment CVS access at SF is unavailable - I
> get connection refused.  I'll try to check it in later if no one else
> gets to it first.
>
> Rob
>
> On 5/24/07, Dieter Engelhardt <Dieter@...> wrote:
> >
> >  Hi Gerd,
> >  this is what i expected, but the returnvalue of adMainTab is void:
> >   void addMainTab(IMainPanelTab tab);
> >  Has this changed in the actual source? And what should i use instead?
> >
> >  Dieter
> >
> >  Gerd Wagner schrieb:
> >  Dieter Engelhardt wrote:
> >
> >
> >  I have added an new TabPanel to the via addMainTab().
> >
> > How do i set this new tab to be selected?
> >
> >  addMainTab() returns an int. Call selectMainTab(int) with that int as
> > parameter.
> >
> > Gerd
> >
> >
> >
> >
> >  Thanx
> > Dieter
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squirrel-sql-develop@...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squirrel-sql-develop@...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squirrel-sql-develop@...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> >
> >
>

On 5/27/07, Gerd Wagner <birgit-und-gerd@...> wrote:
> Sorry for late response.
>
> Of course I missed that only SessionPanel.addMainTab() but not
> ISession.addMainTab() returned the index. Thanks for taking care, Rob. :-)
>

Dieter,

Yes, there was a big window of opportunity for CVS access yesterday
and I took advantage of it :)  Forgot to followup and let you know
that it has been fixed in CVS.  Let us know if you have any other
troubles.

Rob

On 5/18/07, Dieter Engelhardt <Dieter@...> wrote:
> Hi,
> i need help getting started to develop a plugin for squirrel.
>
> Right now im am developing a Eclipse RPC application whitch parses a
> sql-script and builds a graphical representation as a tree.
>
> I'm now trying to integrate this into squirrel.
> What would be the best environment within eclipse to develop the plugin.
> Do i need to copy everything in the squirrel-plugin directory, or is it
> posible to have a own project within eclipse.
> How do i start?

1. Checkout the source and create a new Java project in Eclipse rooted
at "sql12".

2. Create a new directory under sql12/plugins and copy the
plugin_build.xml from the example plugin.

3. Edit plugin_build.xml, replacing example with the name of your
plugin (short name).

4. Edit build.xml to add your plugin to the compile_plugins target and
be sure to add an entry for your plugin in build.xml.

5. Your plugin source code should live in
net.sourceforge.squirrel_sql.plugins.<pluginname>

Let us know if you have any other questions.

Rob

On 5/18/07, Dieter Engelhardt <Dieter@...> wrote:
>
>  Thanx Rob,
>  i already read this on the website and i finaly created a working set for
> that. But now im looking for an API-Documentation.
>
>  I'd like to  ad an icon to the SQLPanel to start the parsing of the
> sqlstatements.
>  Could you give me a hint for that?

The OraclePlugin.addActions() does this.  For example:

      session.addToToolbar(coll.get(NewDBOutputWorksheetAction.class));

Rob

On 5/5/07, Nathan Voxland <Nathan.Voxland@...> wrote:
> Hi, I'm the developer of LiquiBase, a database refactoring manager
> (www.liquibase.org).  I am looking to start making IDE plug-in front-ends to
> it and am thinking of starting with a SQuirreL plugin.  I've gotten a good
> start on it already and am impressed with how easy it is to develop and
> integrate.
>
> My question is if you would be interested in having me contribute it
> directly to SQuirreL, or if I should keep it independent?  I see you already
> have a refactoring plugin, but it appears to be just partially done (version
> 0.2 if I remember right) but I don't know what future ideas you have for
> that plug-in.
>
> I'd be fine keeping it independent, but thought I would offer it as a way to
> improve the existing refactoring plugin, or as a different refactoring
> option bundled with SQuirreL
>
Nathan,

The current refactoring plugin doesn't support all of the refactoring
options that LiquiBase does. However it has been tested against ~20
different databases (See
sql12/fw/src/net/sourceforge/squirrel_sql/fw/dialects/*).  In my mind,
neither one appears to have a clear advantage.  I'm ok with having
another Refactoring plugin (although we need a different name - maybe
LiquiBase Refactoring Plugin?).  Since LiquiBase is licensed under
LGPL, it seems fine to me to distribute it along with SQuirreL.

It seems that your goal (from this page:
http://www.liquibase.org/refactoring_ide/index.html) is to build it in
such a way that it is able to be included as a plugin in different
IDEs.  Might I suggest a third option to the two you gave?  Perhaps
you could maintain the core refactoring functionality in a library
that gets included by the plugin in SQuirreL or whatever other IDE you
write a plugin for.  That way, you would have the source code for core
functionality in just one place - your existing source code
repository.  Having the code in two places and maintaining both gets
old pretty quick.  We could then get you a SourceForge account to
allow you maintain the SQuirreL plugin code that depends on the
library.  Does that sound workable to you?

Rob

I forgot to hit "reply all" on this.

________________________________

From: Nathan Voxland
Sent: Sun 5/6/2007 9:22 AM
To: Robert Manning
Subject: RE: [Squirrel-sql-develop] Refactoring Plugin


You're right about the difference in the number of databases supported.  =
I'm hoping to support more eventually, but am just focusing on those =
four for version 1.0.   Because of that, I think you're right that =
having both plug-ins is a good idea. =20
=20
I think you are thinking along the same lines as I was if LiquiBase =
plugin code was included with SQuirreL.  I designed LiquiBase to have a =
core migrator jar that has no dependencies and contains just the =
refactoring engine.  As I build IDE plugins, I was going to keep the =
code from them distributed independently of the core.  I'm not sure how =
much (if any) code can be shared between plug-ins that isn't part of the =
LiquiBase core. I've started plug-ins for Eclipse and NetBeans, and they =
abstract their UI components and actions enough that there may not be a =
lot of commonality, we'll have to just see.  Neither have a =
well-developed, extendable database interface so I am planning on =
focusing SQuirreL first, then see what I can abstract out.   If there is =
common plug-in classes, I'll keep those in my repository along with the =
LiquiBase core. =20
=20
What you were suggesting is for me to keep the SQuirreL LiquiBase =
plug-in code in my repository as well, and commit the compiled plug-in =
jars to SQuirreL as new versions are completed.  Is that right, or were =
you suggesting I keep the SQuirreL-specific code in the SQuirreL =
repository?  I think either option would be fine.  Keeping the SQuirreL =
code in the SQuirreL repository may make it easier for other SQuirreL =
developers to find bugs and hopefully make improvements, but keeping it =
the SQuirreL code in the same repository as the base plug-in code may be =
easier in the long run.  I'm just looking for what would best allow us =
to help improve each other's projects.
=20
Nathan

________________________________

From: Robert Manning [mailto:robert.m.manning@...]
Sent: Sat 5/5/2007 12:57 PM
To: Nathan Voxland
Cc: squirrel-sql-develop@...
Subject: Re: [Squirrel-sql-develop] Refactoring Plugin



On 5/5/07, Nathan Voxland <Nathan.Voxland@...> wrote:
> Hi, I'm the developer of LiquiBase, a database refactoring manager
> (www.liquibase.org).  I am looking to start making IDE plug-in =
front-ends to
> it and am thinking of starting with a SQuirreL plugin.  I've gotten a =
good
> start on it already and am impressed with how easy it is to develop =
and
> integrate.
>
> My question is if you would be interested in having me contribute it
> directly to SQuirreL, or if I should keep it independent?  I see you =
already
> have a refactoring plugin, but it appears to be just partially done =
(version
> 0.2 if I remember right) but I don't know what future ideas you have =
for
> that plug-in.
>
> I'd be fine keeping it independent, but thought I would offer it as a =
way to
> improve the existing refactoring plugin, or as a different refactoring
> option bundled with SQuirreL
>
Nathan,

The current refactoring plugin doesn't support all of the refactoring
options that LiquiBase does. However it has been tested against ~20
different databases (See
sql12/fw/src/net/sourceforge/squirrel_sql/fw/dialects/*).  In my mind,
neither one appears to have a clear advantage.  I'm ok with having
another Refactoring plugin (although we need a different name - maybe
LiquiBase Refactoring Plugin?).  Since LiquiBase is licensed under
LGPL, it seems fine to me to distribute it along with SQuirreL.

It seems that your goal (from this page:
http://www.liquibase.org/refactoring_ide/index.html) is to build it in
such a way that it is able to be included as a plugin in different
IDEs.  Might I suggest a third option to the two you gave?  Perhaps
you could maintain the core refactoring functionality in a library
that gets included by the plugin in SQuirreL or whatever other IDE you
write a plugin for.  That way, you would have the source code for core
functionality in just one place - your existing source code
repository.  Having the code in two places and maintaining both gets
old pretty quick.  We could then get you a SourceForge account to
allow you maintain the SQuirreL plugin code that depends on the
library.  Does that sound workable to you?

Rob

Still forgetting "Reply to all"...

-----Original Message-----
From: Nathan Voxland=20
Sent: Monday, May 07, 2007 10:32 AM
To: 'Robert Manning'
Subject: RE: [Squirrel-sql-develop] Refactoring Plugin

I think it would be best to keep the SQuirreL-specific code in the
SQuirreL repository.  Anything that would be in there should be fairly
SQuirreL-specific and it would work best with your build and install
scripts.  When it comes time to create the real NetBeans and Eclipse
plug-ins, I may keep them in separate repositories anyway. =20

I have a question on what you prefer for laying out the UI.  I use
IntelliJ, so their built-in visual editor is the easiest for me, but
would not be as easy for non-intelliJ users to work with.  Would you
rather have me use jform or NetBean's Matisse, or is the IntelliJ one
fine?

Nathan

-----Original Message-----
From: Robert Manning [mailto:robert.m.manning@...
Sent: Sunday, May 06, 2007 11:52 AM
To: Nathan Voxland
Subject: Re: [Squirrel-sql-develop] Refactoring Plugin

On 5/6/07, Nathan Voxland <Nathan.Voxland@...> wrote:
> I think you are thinking along the same lines as I was if LiquiBase
plugin
> code was included with SQuirreL.  I designed LiquiBase to have a core
> migrator jar that has no dependencies and contains just the
refactoring
> engine.  As I build IDE plugins, I was going to keep the code from
them
> distributed independently of the core.  I'm not sure how much (if any)
code
> can be shared between plug-ins that isn't part of the LiquiBase core.
I've
> started plug-ins for Eclipse and NetBeans, and they abstract their UI
> components and actions enough that there may not be a lot of
commonality,
> we'll have to just see.  Neither have a well-developed, extendable
database
> interface so I am planning on focusing SQuirreL first, then see what I
can
> abstract out.   If there is common plug-in classes, I'll keep those in
my
> repository along with the LiquiBase core.

That sounds very reasonable.

>
> What you were suggesting is for me to keep the SQuirreL LiquiBase
plug-in
> code in my repository as well, and commit the compiled plug-in jars to
> SQuirreL as new versions are completed.  Is that right, or were you
> suggesting I keep the SQuirreL-specific code in the SQuirreL
repository?  I
> think either option would be fine.  Keeping the SQuirreL code in the
> SQuirreL repository may make it easier for other SQuirreL developers
to find
> bugs and hopefully make improvements, but keeping it the SQuirreL code
in
> the same repository as the base plug-in code may be easier in the long
run.
> I'm just looking for what would best allow us to help improve each
other's
> projects.

I was thinking you might include the compiled jar(s) that represent
the core refactoring functionality as a library that the SQuirreL
plugin code would use.  From my perspective, the SQuirreL plugin code
would naturally be best kept in the SQuirreL repository.  It would
allow us to build our installer and archives including it, so users
wouldn't need to go find it and download it separately.  But the
choice is yours, obviously, you will be maintaining it primarily, so
if it's more convenient to keep it all in one place, that is fine.  I
imagine you'll already have the NetBeans and Eclipse plugins' source
code in the same repository, so I could see the reasoning behind
keeping the SQuirreL plugin code there as well.  The only thing I
would advise you not to do, is to (attempt to) keep the same source
code in two different repositories.  I've done this before and
realized that time is precious, and I didn't need to spend it keeping
repositories in sync.

Rob

On 5/7/07, Nathan Voxland <Nathan.Voxland@...> wrote:
> I think it would be best to keep the SQuirreL-specific code in the
> SQuirreL repository.  Anything that would be in there should be fairly
> SQuirreL-specific and it would work best with your build and install
> scripts.  When it comes time to create the real NetBeans and Eclipse
> plug-ins, I may keep them in separate repositories anyway.
>
> I have a question on what you prefer for laying out the UI.  I use
> IntelliJ, so their built-in visual editor is the easiest for me, but
> would not be as easy for non-intelliJ users to work with.  Would you
> rather have me use jform or NetBean's Matisse, or is the IntelliJ one
> fine?
>

I looked at Matisse a little while back, but it required GroupLayout
which seemed NetBeans-specific at the time.  However, now it's in the
JDK (not sure if it's 1.5 or 1.6), so maybe it's time to look again.
I would say, as long as the UI code that is generated is mostly
self-contained and integrates well with the existing Swing code, I
wouldn't be against it.  I'm definitely thumbs down on integrating a
UI framework that requires re-writing the existing UI code :)

Rob

The IntelliJ layout manager has its own library it depends on, but is
self-contained.  I'll see what Matisse requires now and if it doesn't
require anything, I'll use that.  If it still adds dependencies, I'll
probably use IntelliJ for now, and after the UI stabilizes a bit, I may
look at laying the controls out in a more standard way.=20

-----Original Message-----
From: Robert Manning [mailto:robert.m.manning@...
Sent: Monday, May 07, 2007 4:59 PM
To: Nathan Voxland
Cc: squirrel-sql-develop
Subject: Re: [Squirrel-sql-develop] Refactoring Plugin

On 5/7/07, Nathan Voxland <Nathan.Voxland@...> wrote:
> I think it would be best to keep the SQuirreL-specific code in the
> SQuirreL repository.  Anything that would be in there should be fairly
> SQuirreL-specific and it would work best with your build and install
> scripts.  When it comes time to create the real NetBeans and Eclipse
> plug-ins, I may keep them in separate repositories anyway.
>
> I have a question on what you prefer for laying out the UI.  I use
> IntelliJ, so their built-in visual editor is the easiest for me, but
> would not be as easy for non-intelliJ users to work with.  Would you
> rather have me use jform or NetBean's Matisse, or is the IntelliJ one
> fine?
>

I looked at Matisse a little while back, but it required GroupLayout
which seemed NetBeans-specific at the time.  However, now it's in the
JDK (not sure if it's 1.5 or 1.6), so maybe it's time to look again.
I would say, as long as the UI code that is generated is mostly
self-contained and integrates well with the existing Swing code, I
wouldn't be against it.  I'm definitely thumbs down on integrating a
UI framework that requires re-writing the existing UI code :)

Rob

I have just checked it: Matisse requires a GroupLayout, which is not 
part of stand. API of java 1.5 (it is freely distributable), but has 
become part of Swing in 1.6.

-- Stan Berka

Nathan Voxland wrote:
> The IntelliJ layout manager has its own library it depends on, but is
> self-contained.  I'll see what Matisse requires now and if it doesn't
> require anything, I'll use that.  If it still adds dependencies, I'll
> probably use IntelliJ for now, and after the UI stabilizes a bit, I may
> look at laying the controls out in a more standard way. 
>
> -----Original Message-----
> From: Robert Manning [mailto:robert.m.manning@...] 
> Sent: Monday, May 07, 2007 4:59 PM
> To: Nathan Voxland
> Cc: squirrel-sql-develop
> Subject: Re: [Squirrel-sql-develop] Refactoring Plugin
>
> On 5/7/07, Nathan Voxland <Nathan.Voxland@...> wrote:
>   
>> I think it would be best to keep the SQuirreL-specific code in the
>> SQuirreL repository.  Anything that would be in there should be fairly
>> SQuirreL-specific and it would work best with your build and install
>> scripts.  When it comes time to create the real NetBeans and Eclipse
>> plug-ins, I may keep them in separate repositories anyway.
>>
>> I have a question on what you prefer for laying out the UI.  I use
>> IntelliJ, so their built-in visual editor is the easiest for me, but
>> would not be as easy for non-intelliJ users to work with.  Would you
>> rather have me use jform or NetBean's Matisse, or is the IntelliJ one
>> fine?
>>
>>     
>
> I looked at Matisse a little while back, but it required GroupLayout
> which seemed NetBeans-specific at the time.  However, now it's in the
> JDK (not sure if it's 1.5 or 1.6), so maybe it's time to look again.
> I would say, as long as the UI code that is generated is mostly
> self-contained and integrates well with the existing Swing code, I
> wouldn't be against it.  I'm definitely thumbs down on integrating a
> UI framework that requires re-writing the existing UI code :)
>
> Rob
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
>

Then I'll start out trying to stick with standard swing APIs without
using a layout tool.  I'm not envisioning a lot of complex UIs, so that
may not be too bad.

I'll get a more fully working code-base and then look at moving it into
the SQuirreL repository.  I'll send along the code when I'm ready.

Nathan=20

-----Original Message-----
From: squirrel-sql-develop-bounces@...
[mailto:squirrel-sql-develop-bounces@...] On Behalf Of
Stan Berka
Sent: Tuesday, May 08, 2007 11:55 AM
To: squirrel-sql-develop
Subject: Re: [Squirrel-sql-develop] Refactoring Plugin

I have just checked it: Matisse requires a GroupLayout, which is not=20
part of stand. API of java 1.5 (it is freely distributable), but has=20
become part of Swing in 1.6.

-- Stan Berka

Nathan Voxland wrote:
> The IntelliJ layout manager has its own library it depends on, but is
> self-contained.  I'll see what Matisse requires now and if it doesn't
> require anything, I'll use that.  If it still adds dependencies, I'll
> probably use IntelliJ for now, and after the UI stabilizes a bit, I
may
> look at laying the controls out in a more standard way.=20
>
> -----Original Message-----
> From: Robert Manning [mailto:robert.m.manning@...
> Sent: Monday, May 07, 2007 4:59 PM
> To: Nathan Voxland
> Cc: squirrel-sql-develop
> Subject: Re: [Squirrel-sql-develop] Refactoring Plugin
>
> On 5/7/07, Nathan Voxland <Nathan.Voxland@...> wrote:
>  =20
>> I think it would be best to keep the SQuirreL-specific code in the
>> SQuirreL repository.  Anything that would be in there should be
fairly
>> SQuirreL-specific and it would work best with your build and install
>> scripts.  When it comes time to create the real NetBeans and Eclipse
>> plug-ins, I may keep them in separate repositories anyway.
>>
>> I have a question on what you prefer for laying out the UI.  I use
>> IntelliJ, so their built-in visual editor is the easiest for me, but
>> would not be as easy for non-intelliJ users to work with.  Would you
>> rather have me use jform or NetBean's Matisse, or is the IntelliJ one
>> fine?
>>
>>    =20
>
> I looked at Matisse a little while back, but it required GroupLayout
> which seemed NetBeans-specific at the time.  However, now it's in the
> JDK (not sure if it's 1.5 or 1.6), so maybe it's time to look again.
> I would say, as long as the UI code that is generated is mostly
> self-contained and integrates well with the existing Swing code, I
> wouldn't be against it.  I'm definitely thumbs down on integrating a
> UI framework that requires re-writing the existing UI code :)
>
> Rob
>
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squirrel-sql-develop@...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
>  =20

------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Squirrel-sql-develop mailing list
Squirrel-sql-develop@...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop