For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 55 replies, 10 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
@support-rkalla wrote:
This is a support forum, if the developers choose to reply to non-support issues its really up to them. The team worked clear through the weekend to get 3.8 GA ready for this week, cut them some slack.
I will! 🙂 I wasn’t fully aware of the hectic situation that must be going on right now. Naturally, for me, there is no haste in getting an answer at all. Whenever you guys are ready for it, I would say.
Keep up the good work!
Now that the GA build has been released, is there already anyone who cares to comment on the status of JFaceDbc/sqlexplorer relating to the myeclipse db plug-in?
Has genuitec obtained the rights to use the JFacdeDbc code-base commercially, or will changes be put back into the open-source scene? If the last is true, who will the changes be given to, as there does not seem to be any active maintainer of the open source code base.
As I understand it, Henk, JFaceDBC is no longer open source. The original developer(s) took it commercial. The SQLExplorer folks forked the code to continue the open source development of the code base. Genuitec has established a relationship with the SQLExplorer developers that will be maturing with future releases. If you have an issue with the SQLExplorer project, please take it up with them (or better yet, contribute!). If you have a problem with MyEclipse use of SQLExplorer code, take it up with Genuitec, not the support forum.
@support-jeff wrote:
As I understand it, Henk, JFaceDBC is no longer open source. The original developer(s) took it commercial. The SQLExplorer folks forked the code to continue the open source development of the code base.
This is a known fact, but the last released open source version from JFaceDBc can be forked by anyone, right? Why would you specifically need to go through the SQLExplorer folks?
Genuitec has established a relationship with the SQLExplorer developers that will be maturing with future releases.
Like some other people, I care about the stability of the plug-ins that make up myeclipse. Of course, I have a special extra interest (like I mentioned before), but even if I didn’t had that, I might be wondering about the situation. The SQL developers have done very little yet. They just took some existing source, made some small modifications, and have been very quiet since then. How do you know they are indeed going to make further contributions to the project?
If you have an issue with the SQLExplorer project, please take it up with them (or better yet, contribute!).
I would love to contribute, honestly! But the development is extremely quiet, nothing happens on the project boards, the associated forum seems to be dead and there is no reaction to questions. This does not seem to be a healthy base to send contributions to.
Just look at all the activity that is going on for the rival QuantumDB plug-in. There are releases, tons of messages on the project page each day, real developpers who really respond to questions, etc.
Also, I don’t know where I can download the source of the sqlexplorer version as modified by genuitec (which I consider the latest version). Contributing code for the older release might not be very useful.
I’m sorry if this is the wrong forum to post in. Which one would you suggest instead?
Just for the record, I’m a very happy user of myeclipse. I personally introduced it in the company I work for, and we bought multiple licenses. Everyone is very happy with your *great* product, but just wondering about this situation.
I almost don’t dare to ask this again. The last thing I want to do is upset the developers of this fine product, but would anyone from Genuitec care to comment on the previously asked questions?
Maybe the information regarding sqlexplorer is confidental? If so, maybe you guys could just say that and close this thread. FYI, I have been looking at the sqlexplorer forum today. Still no sign of live there. There is a question asking whether development is still going on, but no reply on that ever came.
henk,
There’s nothing confidential here. Jeff answered several questions above, is there something else specifically that you’re looking for?
Myself, and some other people I read about in this forum, have asked where the source for the enhanced JfaceDbc/sqlexplorer code can be downloaded.
There was never an answer to that question (or maybe there was, and I overlooked it, my apologizes in advance if that is the case).
There was also never an answer to the question why the myeclipse team had to depend on sqlexplorer and not fork JfaceDbc themselves.
there isn’t source code for jfacedbc – it is comercial now
sqlexplorer is on http://sqlexplorer.dev.java.net
(source is on dev.net cvs)
regards@snpe wrote:
there isn’t source code for jfacedbc – it is comercial now
sqlexplorer is on http://sqlexplorer.dev.java.net
(source is on dev.net cvs)
regardsOfcourse I meant the fork from Jfacedbc called sqlexplorer. The fact that JfaceDbc is commercial now has been mentioned several times already. And you are wrong about saying there isn’t any source code for jfacedbc. It is still at http://sourceforge.net/projects/jfacedbc and I still wonder why the myeclipse team didn’t use this code base instead.
At the mentioned sqlexplorer URL there’s only the slightly updated version from Jul 19.
If myeclipse is building on sqlexplorer, shouldn’t they make these changes available? Naturally, I understand that there can be some delay between making these changes public.
So, if I rephrase the question:
“Can I already download the sourcecode changes the myeclipse team made to sqlexplorer?”
Arjan,
There was also never an answer to the question why the myeclipse team had to depend on sqlexplorer and not fork JfaceDbc themselves.
It’s not a matter of had to, it’s simply that the sqlexplorer fork had already been ported to Eclipse 3.0, which was our target platform. So it was simply a matter of saving time by not reproducing work that was already done in open soure in an effort to be efficient with our development resources.
If myeclipse is building on sqlexplorer, shouldn’t they make these changes available? Naturally, I understand that there can be some delay between making these changes public.
I know we’ve got some sort of management conversation going on with the sqlexplorer team to evaluate their interest in working with us. However, a lot of our changes were deep integration changes to rebuild large portions of the codebase on top of the MyEclipse infrastructure. As a result, the code as it is now can’t really be run on its own anymore, so it’s possible that most of it isn’t of interest to the original team.
“Can I already download the sourcecode changes the myeclipse team made to sqlexplorer?”
Not right now is about the best answer I have on this one. Are you a plugin developer that is interested in making additional enhancements?
@support-scott wrote:
Arjan,
So it was simply a matter of saving time by not reproducing work that was already done in open soure in an effort to be efficient with our development resources.Well it sounds reasonable. I haven’t counted the differences really, but from what I heard they were rather minor. Oh, well I don’t think this is such a big issue that it’s worth spending more time on. 😉
However, a lot of our changes were deep integration changes to rebuild large portions of the codebase on top of the MyEclipse infrastructure. As a result, the code as it is now can’t really be run on its own anymore, so it’s possible that most of it isn’t of interest to the original team.
I can believe that. Do you have some sort of plan to integrate possible future changes made in sqlexplorer back into DB Explorer? I guess that if the code base diverges too much it will be hard to benefit in both ways (i.e. the original team can’t benifit from you, and you can’t benifit from them).
Scott,
Thank you for your answers, I think they make the matter a lot clearer now.
@support-scott wrote:
Not right now is about the best answer I have on this one. Are you a plugin developer that is interested in making additional enhancements?
Sort-of. The company I work for is planning to build a kind of application architecture targetting J2EE application servers. It will be used for rendering (SQL generated) tables where the interaction between these is rigidly defined using an XML dialect.
For working with this system, we have planned to build a series of Eclipse plug-ins. One of them will be based on the sqlexplorer code.
The ‘enhancements’ we have add for our proto-type are support for parameterized SQL queries and ‘includes’ in SQL text. The SQL query itself is stored in a custom XML format, so we added support for reading this format.
Basically, this entails the following changes in SQLEditor.java:
1) setting a custom document provider in init with a call to setDocumentProvider().
2) Adding a small amount of code to getSQLToBeExecuted()
3) Adding some widgets to the editor in createSourceViewer
4) Extending SQLTextViewer to provide support for delagating cut/copy/paste events to our own widgets and setting the editor’s dirty state.This SQL format may be usefull in and by ityself, but we don’t like to release a complete new fork of sqlexplorer just to add parameterized SQL. Therefore we’re looking into standardizing some plug-in interfaces, so we can release our ‘enhancements’ as an extension. Until this far cilquirm (Aadi Deshpande) has not been very responsive, buy maybe he’s just very bussy.
There is definitely a bug in the DB Explorer Table View when you click on the Foreign Key tab. This will be addressed in an upcoming release, just not sure if it will be 3.8.3 or 3.9.
