At this time that is the case. It is a top priority to remove this prerequisite. The use of these classes is fairly pervasive and will take some effort to remove them. Any suggestions, from anyone, for alternate open sources classes would be very welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you ever look at the RCP (Rich Client Foundation) of eclipse.org. It provide a full framework for fat client java application (menu, toolbar, window, graphical widget, ...), it's free and it's multi-plateform : mac, linux, window, aix, ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I asked our Eclipse expert to look at OWB. He replied:
The architectecture document (Open Workbench Architectural Overview) mentions that the tooling has been designed according to the MVC paradigm. The C++ layer represents the View + Controller. The Java layer represents the Model. The C++ layer uses the Rogue Wave Stingray libraries. In fact, the entire GUI (i.e. View) has been developed using C++ libraries.
When porting the GUI to an open source alternative, like SWT in Eclipse, the entire GUI has to be redesigned and rewritten. Developing GUIs in Java and SWT is extremely easy, but, it's clear that this still will be a comprehensive task! Open Workbench features complex views, that require quite some Java coding to accomplish a decent alternative.
However, Java is already used for a limited UI task: ABTDriverProgressDialog is a Java class that visualises a progress dialog with a progress bar. This Java GUI part uses AWT. Note: AWT and SWT are completely different, however, by using a trick (i.e. the SWT / AWT bridge in SWT) it is possible to combine both window toolkits. It is preferable to choose one direction: either AWT / Swing or either SWT. The combination of AWT / Swing is more powerful (i.e. it features more widgets) than SWT.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By now, you could use QT4 which is usable for OpenSource projects under Windows, Linux and MacOS ! It could replace the MFC dependencies and maybe also dependencies to the Rogue libraries, but I did not check.
For sure, this is quite some work we hope to have an entirely free product !
Thanks for the job you have done,
Pierre-Andr
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm a Chinese student,and I want to translate the language of openworkbench into Chinese.
Of course if I have more free time,I want to participate in the development of the software.
When I tried to compile the source code,I realized that I had to buy some tools of Rogue Wave as "Developer Setup.pdf" said.
The problem is that : Which of the tools listed in http://www.roguewave.com/purchase/estore/
must I get first to compile the source code of OWB?
Thank you very much and I sincerely wait for your reply!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you download the software you will find a document called "Developer Setup.pdf" in workbench\doc. This document states that you need:
- Rogue Wave Objective Toolkit 8.0.3
- Rogue Wave Objective Grid 9.0.3
and some other tools
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes,I have already read the document "Developer Setup.pdf" .But as it listed ,
- Rogue Wave Objective Toolkit 8.0.3
- Rogue Wave Objective Grid 9.0.3
and some other tools
I can't map them to the list on the page
" http://www.roguewave.com/purchase/estore/ "
Our team can't offord all of the tools listed on that page :(
So I just want to know which of the tools listed on the page http://www.roguewave.com/purchase/estore/
are necessary for compiling the source code of
OWB?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, those are the correct products. It should be noted that OWB has not been built or tested with those versions. The good news is that, traditionally, it has not been difficult to update OWB to work with newer versions of the Objective Tools.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SIGH!
There are five errors while I tried the command "ant build.xml" to compile the source code of OWB 1.1.4 as the doc "Developer Setup.pdf" says.
I configed the building environment just as "Developer Setup.pdf" says, and the version of ROGUE WAVE SOFTWARE is 2004.
The only difference between my environment and the doc is that the version of my Sun Java Development kit is 1.4.2_11 but not 1.4.2_01 as the doc says.
These are the general information of the errors:
------ Build started: Project: Views, Configuration: Release Win32 ------
Linking...
LINK : fatal error LNK1104: cannot open file 'og903as.lib'
Build log was saved at "file://c:\workbench\dev\Workbench\Views\Release\BuildLog.htm"
Views - 1 error(s), 0 warning(s)
og903as.lib is a Rogue Wave library with the version number in it. You use a different version (10.0 ?), so you probably have to adapt the filename (something like og1000as.lib). Browse the Rogue wave directory for the correct filename.
René
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The version of OG on my machine is just 903 (which the Rogue Wave Stingray Studio 2004 includes).
In addition,I tried to find out all the files in the format "*.lib" on my C partition where Rogue Wave Stingray Studio 2004 installed, but I didn't find any file like "og*.lib" or "ot*.lib" !(Only a file "OptionsDlg.lib“）
Is it bizarre?
How did you compile the src?
Could you tell me more in detail?
Thank you very much!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It doesn't sound as though the Stingray libraries have actually been built. Once you've followed the Stingray wizard to define the characteristics of the libraries they actually need to be built. I don't recall if Stingray provides batch files for building the libraries but they can be built within the IDE by opening up the Stringray projects the wizard created.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You mentioned that "but they can be built within the IDE by opening up the Stringray projects the wizard created"
How to build the libraries within the IDE?
First ,I configured the OG903 and OT803 according to
the document "workbench\doc\Developer Setup.pdf".
Then I built the file "C:\Stingray Studio\Src\foundation71.sln" ,there's on error.
And then I opened the file "C:\Stingray Studio\Src\toolkit71.sln" with MS visual studio .NET 2003 and builded it,there are 4 errors:
(1)c:\Stingray Studio\Include\Toolkit\ot_agentid.h(59): fatal error C1083: Cannot open type library file: 'agentsvr.exe': No such file or directory
(4)Toolkit 8.03 error PRJ0019: A tool returned an error code from "Performing Makefile project actions"
Then the file "C:\Stingray Studio\Src\grid71.sln",still 4 errors:
(1)c:\Stingray Studio\Src\Grid\Dbe\gxdbteng.cpp(67): fatal error C1083: Cannot open include file: 'rw/db/db.h': No such file or directory
(4)Grid 9.03 error PRJ0019: A tool returned an error code from "Performing Makefile project actions"
SIGH...
I really don't know what is the matter,could you tell me more? Thanks.
Which IRC channel do you usually visit?Could you tell me ?I have some other problems about OWB to
consult you and I want to get the answer soon.
Thanks.
My msn:sun2niang@hotmail.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, you do need stingray. You also need Visual Studio (I can't remember what version though).
Unfortunately, the versions you need (Rogue Wave Object Toolkit 8.0.3, Rogue Wave Objective Grid 9.0.3)are no longer sold. If you speak with your rogue wave representative, they will probably give you copies of the older versions if you buy the latest version.
Cheers,
Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do we need to buy Rogue Wave Stingray Studio for building Open Workbench?
At this time that is the case. It is a top priority to remove this prerequisite. The use of these classes is fairly pervasive and will take some effort to remove them. Any suggestions, from anyone, for alternate open sources classes would be very welcome.
Did you ever look at the RCP (Rich Client Foundation) of eclipse.org. It provide a full framework for fat client java application (menu, toolbar, window, graphical widget, ...), it's free and it's multi-plateform : mac, linux, window, aix, ...
I second taking a look at eclipse -> SWT/JFace would be an excellent choice.
I asked our Eclipse expert to look at OWB. He replied:
The architectecture document (Open Workbench Architectural Overview) mentions that the tooling has been designed according to the MVC paradigm. The C++ layer represents the View + Controller. The Java layer represents the Model. The C++ layer uses the Rogue Wave Stingray libraries. In fact, the entire GUI (i.e. View) has been developed using C++ libraries.
When porting the GUI to an open source alternative, like SWT in Eclipse, the entire GUI has to be redesigned and rewritten. Developing GUIs in Java and SWT is extremely easy, but, it's clear that this still will be a comprehensive task! Open Workbench features complex views, that require quite some Java coding to accomplish a decent alternative.
However, Java is already used for a limited UI task: ABTDriverProgressDialog is a Java class that visualises a progress dialog with a progress bar. This Java GUI part uses AWT. Note: AWT and SWT are completely different, however, by using a trick (i.e. the SWT / AWT bridge in SWT) it is possible to combine both window toolkits. It is preferable to choose one direction: either AWT / Swing or either SWT. The combination of AWT / Swing is more powerful (i.e. it features more widgets) than SWT.
I would like to help porting...
By now, you could use QT4 which is usable for OpenSource projects under Windows, Linux and MacOS ! It could replace the MFC dependencies and maybe also dependencies to the Rogue libraries, but I did not check.
For sure, this is quite some work we hope to have an entirely free product !
Thanks for the job you have done,
Pierre-Andr
I'm a Chinese student,and I want to translate the language of openworkbench into Chinese.
Of course if I have more free time,I want to participate in the development of the software.
When I tried to compile the source code,I realized that I had to buy some tools of Rogue Wave as "Developer Setup.pdf" said.
The problem is that : Which of the tools listed in http://www.roguewave.com/purchase/estore/
must I get first to compile the source code of OWB?
Thank you very much and I sincerely wait for your reply!
If you download the software you will find a document called "Developer Setup.pdf" in workbench\doc. This document states that you need:
- Rogue Wave Objective Toolkit 8.0.3
- Rogue Wave Objective Grid 9.0.3
and some other tools
Yes,I have already read the document "Developer Setup.pdf" .But as it listed ,
- Rogue Wave Objective Toolkit 8.0.3
- Rogue Wave Objective Grid 9.0.3
and some other tools
I can't map them to the list on the page
" http://www.roguewave.com/purchase/estore/ "
Our team can't offord all of the tools listed on that page :(
So I just want to know which of the tools listed on the page http://www.roguewave.com/purchase/estore/
are necessary for compiling the source code of
OWB?
Thanks!
I think you need the first two tools:
Objective Toolkit:Dev License + Basic Support
Version: 9.00 (SKU001602)
Objective Grid: Dev. Lic + Basic Sup with OG.NET
Version: 10.0 (SKU003415)
But I haven't tried it. Maybe you can ask OWB support?
Yes, those are the correct products. It should be noted that OWB has not been built or tested with those versions. The good news is that, traditionally, it has not been difficult to update OWB to work with newer versions of the Objective Tools.
SIGH!
There are five errors while I tried the command "ant build.xml" to compile the source code of OWB 1.1.4 as the doc "Developer Setup.pdf" says.
I configed the building environment just as "Developer Setup.pdf" says, and the version of ROGUE WAVE SOFTWARE is 2004.
The only difference between my environment and the doc is that the version of my Sun Java Development kit is 1.4.2_11 but not 1.4.2_01 as the doc says.
These are the general information of the errors:
------ Build started: Project: Views, Configuration: Release Win32 ------
Linking...
LINK : fatal error LNK1104: cannot open file 'og903as.lib'
Build log was saved at "file://c:\workbench\dev\Workbench\Views\Release\BuildLog.htm"
Views - 1 error(s), 0 warning(s)
------ Build started: Project: UI - German, Configuration: Release Win32 ------
Compiling resources...
C:\Stingray Studio\Include/toolkit\ActvHost\ScriptHost.rc(13) : error RC2135 : file not found: ..\lib\ScriptHost.tlb
Build log was saved at "file://c:\workbench\dev\Workbench\UI - German\Release\BuildLog.htm"
UI - German - 1 error(s), 0 warning(s)
------ Build started: Project: UI - English, Configuration: Release Win32 ------
Compiling resources...
C:\Stingray Studio\Include/toolkit\ActvHost\ScriptHost.rc(13) : error RC2135 : file not found: ..\lib\ScriptHost.tlb
Build log was saved at "file://c:\workbench\dev\Workbench\UI English\Release\BuildLog.htm"
UI - English - 1 error(s), 0 warning(s)
------ Build started: Project: UI - French, Configuration: Release Win32 ------
Compiling resources...
C:\Stingray Studio\Include/toolkit\ActvHost\ScriptHost.rc(13) : error RC2135 : file not found: ..\lib\ScriptHost.tlb
Build log was saved at "file://c:\workbench\dev\Workbench\UI - French\Release\BuildLog.htm"
UI - French - 1 error(s), 0 warning(s)
------ Build started: Project: Main, Configuration: Release Win32 ------
Linking...
LINK : fatal error LNK1181: cannot open input file '\workbench\dev\Workbench\Views\Release\Views.lib'
Build log was saved at "file://c:\workbench\dev\Workbench\Main\Release\BuildLog.htm"
Main - 1 error(s), 65 warning(s)
__________________________________________________
Is there anything wrong while I compiled the src?
Thank you very much!
og903as.lib is a Rogue Wave library with the version number in it. You use a different version (10.0 ?), so you probably have to adapt the filename (something like og1000as.lib). Browse the Rogue wave directory for the correct filename.
René
The version of OG on my machine is just 903 (which the Rogue Wave Stingray Studio 2004 includes).
In addition,I tried to find out all the files in the format "*.lib" on my C partition where Rogue Wave Stingray Studio 2004 installed, but I didn't find any file like "og*.lib" or "ot*.lib" !(Only a file "OptionsDlg.lib“）
Is it bizarre?
How did you compile the src?
Could you tell me more in detail?
Thank you very much!!!
It doesn't sound as though the Stingray libraries have actually been built. Once you've followed the Stingray wizard to define the characteristics of the libraries they actually need to be built. I don't recall if Stingray provides batch files for building the libraries but they can be built within the IDE by opening up the Stringray projects the wizard created.
You mentioned that "but they can be built within the IDE by opening up the Stringray projects the wizard created"
How to build the libraries within the IDE?
First ,I configured the OG903 and OT803 according to
the document "workbench\doc\Developer Setup.pdf".
Then I built the file "C:\Stingray Studio\Src\foundation71.sln" ,there's on error.
And then I opened the file "C:\Stingray Studio\Src\toolkit71.sln" with MS visual studio .NET 2003 and builded it,there are 4 errors:
(1)c:\Stingray Studio\Include\Toolkit\ot_agentid.h(59): fatal error C1083: Cannot open type library file: 'agentsvr.exe': No such file or directory
(2)Toolkit 8.03 fatal error U1077: 'cl.exe' : return code '0x2'
(3)Toolkit 8.03 fatal error U1077: 'nmake.exe' : return code '0x2'
(4)Toolkit 8.03 error PRJ0019: A tool returned an error code from "Performing Makefile project actions"
Then the file "C:\Stingray Studio\Src\grid71.sln",still 4 errors:
(1)c:\Stingray Studio\Src\Grid\Dbe\gxdbteng.cpp(67): fatal error C1083: Cannot open include file: 'rw/db/db.h': No such file or directory
(2)Grid 9.03 fatal error U1077: 'cl.exe' : return code '0x2'
(3)Grid 9.03 fatal error U1077: 'nmake.exe' : return code '0x2'
(4)Grid 9.03 error PRJ0019: A tool returned an error code from "Performing Makefile project actions"
SIGH...
I really don't know what is the matter,could you tell me more? Thanks.
Which IRC channel do you usually visit?Could you tell me ?I have some other problems about OWB to
consult you and I want to get the answer soon.
Thanks.
My msn:sun2niang@hotmail.com
With these errors ,I only generate 9 dlls and 6 jars. The npViews.dll and npWBench.exe can't be generated.
Or is it changed now ?
Thanks
K Seelam
Yes, you do need stingray. You also need Visual Studio (I can't remember what version though).
Unfortunately, the versions you need (Rogue Wave Object Toolkit 8.0.3, Rogue Wave Objective Grid 9.0.3)are no longer sold. If you speak with your rogue wave representative, they will probably give you copies of the older versions if you buy the latest version.
Cheers,
Chris
Oooooooooooooooooh, this Roguewave question seems sensitive.
COuld we take the GUI part of the program pre-compiled and only recompile other parts for the time being ?