Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

workspace's debugging features

6 posts in General Discussion Last posting was on 2008-05-21 01:43:56.0Z
Ivo Teubner Posted on 2008-04-24 23:01:17.0Z
From: Ivo Teubner <it@swisslab.de>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
Subject: workspace's debugging features
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4811113d@forums-1-dub>
Date: 24 Apr 2008 16:01:17 -0700
X-Trace: forums-1-dub 1209078077 10.22.241.152 (24 Apr 2008 16:01:17 -0700)
X-Original-Trace: 24 Apr 2008 16:01:17 -0700, vip152.sybase.com
Lines: 80
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:690
Article PK: 1088372

Hello!

We spent some time lately to check out workspace and its debugging
features for StoredProcedures together with its editing functionalities.
The first impressions are quite good, nevertheless we cannot use it in
the way we hoped.

So maybe some of the below mentioned points are easy to resolve or just
are a question if changing some preferences, but here are the points we
struggled with. It would be nice to share some opinions on that.

*Debug-mode
Parameter values
A KO criteria for us is the following:
While debugging the SP only the internal variables are displayed within
the "variables" section.
The Parameters are not. You can only see them in the upper left "Debug"
Window where the procedure call is shown.
However the line where the SP and its parameters are displayed simply
gets cut if the parameters are too may,
which is quite frustrating.

How should the parameters be handled within the debug window?
Our suggestion:
- show them together with the variables in the "variable"-Tab or in an
extra Tab of the debug view
- allow sorting to that grid-list
- allow mouse-over which works great for the variables

sortable parameter list
When starting a SP for debugging workspace opens up a mask where you can
enter values for the SP's parameters. It would be good if this list
would be sortable (by name)
in order to find the needed parameter more easily.

debug complete SP-call
As an replacement for setting each single parameter in the above
mentioned way, it would be good
if one could just copy and paste the SP with its paramaters into a
single textfield. (maybe in the same mask
where one can set the single parameters)
e.g. : exec PR_spampleproc @par1='ok', @par2=12345, @par3='XYZ'
The idea behind this: we often take a whole SP call from the debug
window of our application, it would
then be more comfortable to debug it within workspace instead of setting
each single parameter manually

temptable problem1
I already saw that in the forum as a topic, but same problem here:
in some SPs the created and used temptables are not recognized and
displayed by workspace

temptable problem2
Another problem that occured with temptables is, that those are
recognized(calculated) and displayed within the debug window
under referenced tables, but a click on them does not show there values.
The list just stays empty. If
you doubleclick on the table workspace asked for the columns that should
be selected and so on...those column names
are exactly the ones that are used within the #temptable but their
content is not displayed.

*Development-view
Syntax checking
Syntax checking seems to have problems with large SPs, as syntax error
are only
displayed at the beginning of the SP's code.

Code-Folding
As already mentioned here in the forums:
Would be very nice. At least for "begin ... end" structures.

Lost line focus after saving
If you refresh from the server or save an edited SP the line foucs
gets lost. Even if the SP in the DB differs from the SP that is
currently opened/edited,
the editor should try to go back to the line the user was.

Best regards
Ivo Teubner


mpeppler Posted on 2008-04-25 06:53:01.0Z
Sender: 4f57.480dbf05.1804289383@sybase.com
From: mpeppler@peppler.org
Newsgroups: sybase.public.workspace.general
Subject: Re: workspace's debugging features
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48117fcd.4e8e.1681692777@sybase.com>
References: <4811113d@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 24 Apr 2008 23:53:01 -0700
X-Trace: forums-1-dub 1209106381 10.22.241.41 (24 Apr 2008 23:53:01 -0700)
X-Original-Trace: 24 Apr 2008 23:53:01 -0700, 10.22.241.41
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:691
Article PK: 1088370


> debug complete SP-call
> As an replacement for setting each single parameter in the
> above mentioned way, it would be good
> if one could just copy and paste the SP with its
> paramaters into a single textfield. (maybe in the same
> mask where one can set the single parameters)
> e.g. : exec PR_spampleproc @par1='ok', @par2=12345,
> @par3='XYZ' The idea behind this: we often take a whole SP
> call from the debug window of our application, it would
> then be more comfortable to debug it within workspace
> instead of setting each single parameter manually

I think that you can do this through the Debug dialog.

> *Development-view
> Syntax checking
> Syntax checking seems to have problems with large SPs, as
> syntax error are only
> displayed at the beginning of the SP's code.

Check the properties of the editor - the syntax
coloring/checking is limited to x number of lines.

Michael


Daniel Huang Posted on 2008-04-29 04:34:20.0Z
Reply-To: "Daniel Huang" <lihuang@sybase.com>
From: "Daniel Huang" <lihuang@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <4811113d@forums-1-dub> <48117fcd.4e8e.1681692777@sybase.com>
Subject: Re: workspace's debugging features
Lines: 185
Organization: Sybase
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4816a54c@forums-1-dub>
Date: 28 Apr 2008 21:34:20 -0700
X-Trace: forums-1-dub 1209443660 10.22.241.152 (28 Apr 2008 21:34:20 -0700)
X-Original-Trace: 28 Apr 2008 21:34:20 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:694
Article PK: 1088368

Hi, Ivo:

Please see inline comments:



---------------------------------------------------------------------
We spent some time lately to check out workspace and its debugging
features for StoredProcedures together with its editing functionalities.
The first impressions are quite good, nevertheless we cannot use it in
the way we hoped.
<lihuang>Thank you for evaluating our product! We really appreciate your
good suggestions and will enhance our WorkSpace based on your feedback.
BTW, could you let us know your company name and what version of WorkSpace
you're evaluating/using? And what database server do you use WorkSpace for?


So maybe some of the below mentioned points are easy to resolve or just
are a question if changing some preferences, but here are the points we
struggled with. It would be nice to share some opinions on that.

*Debug-mode
Parameter values
A KO criteria for us is the following:
While debugging the SP only the internal variables are displayed within
the "variables" section.
The Parameters are not. You can only see them in the upper left "Debug"
Window where the procedure call is shown.
However the line where the SP and its parameters are displayed simply
gets cut if the parameters are too may,
which is quite frustrating.

<lihuang>
In WorkSpace 2.0.1, there is a workaround to show parameters. Right click in
SQL Editor and select 'Dump Variable & Table Data'. In dialog, select
'Dumping variables'. Then open 'Console' view from 'Windows'->'Show
View'->'Others'.
When a stored procedure is being debugged, all parameters will be shown in
console view.
If you don't install WorkSpace 2.0.1, please update to 2.0.1 to get this
feature.



And what is your requirements? Is it enough to show parameters in
'Variables' view as readonly or you'd like to change parameter values while
debugging?
If you only want to show parameters as readonly in 'Variables' view, we can
support this feature in WorkSpace 2.1.
Considering parameter change depends on ASE database debugger API support,
we can't guarantee it will be released in WorkSpace 2.1.

In Debug view, the length of character display should not be limited.

How should the parameters be handled within the debug window?
Our suggestion:
- show them together with the variables in the "variable"-Tab or in an
extra Tab of the debug view
- allow sorting to that grid-list
- allow mouse-over which works great for the variables
<lihuang> Thank your for your suggestion. We will consider these suggestions
in WorkSpace 2.1.


sortable parameter list
When starting a SP for debugging workspace opens up a mask where you can
enter values for the SP's parameters. It would be good if this list
would be sortable (by name)
in order to find the needed parameter more easily.
<lihuang> CR499556 is created for this requirement and will be done in
WorkSpace 2.1.


debug complete SP-call
As an replacement for setting each single parameter in the above
mentioned way, it would be good
if one could just copy and paste the SP with its paramaters into a
single textfield. (maybe in the same mask
where one can set the single parameters)
e.g. : exec PR_spampleproc @par1='ok', @par2=12345, @par3='XYZ'
The idea behind this: we often take a whole SP call from the debug
window of our application, it would
then be more comfortable to debug it within workspace instead of setting
each single parameter manually
<lihuang> To avoid setting each single parameter each time is to use an
existing feature by saving them as a configuration in Configure Parameters
dialog.
Each time you run or debug a stored procedure with parameters, a dialog
'Configure Parameters' is always shown. After you fill values, you can save
as a configuration so next time you just need to select that saved
configuration instead of filling each value repeatedly.



temptable problem1
I already saw that in the forum as a topic, but same problem here:
in some SPs the created and used temptables are not recognized and
displayed by workspace
<lihuang> Can you provide the detailed repo. steps so we cab look into it?


temptable problem2
Another problem that occured with temptables is, that those are
recognized(calculated) and displayed within the debug window
under referenced tables, but a click on them does not show there values.
The list just stays empty. If
you doubleclick on the table workspace asked for the columns that should
be selected and so on...those column names
are exactly the ones that are used within the #temptable but their
content is not displayed.
<lihuang> If a temptable is updated, you need to refresh that temptable in
Refreenced Tables view and then see the updated temptable.
Due to performance considerations, WorkSpace does not refresh the tables in
References Tables view automatically when you step to debug a stored
procedure.


*Development-view
Syntax checking
Syntax checking seems to have problems with large SPs, as syntax error
are only
displayed at the beginning of the SP's code.
<lihuang> Can you provide the detailed repo. steps?

Code-Folding
As already mentioned here in the forums:
Would be very nice. At least for "begin ... end" structures.
<lihuang> Thank you for your suggestion. This is one of those things that
are known to us but we haven't been
able to get to it. I created CR499588 for this new feature and will consider
to support it in WorkSpace2.1.


Lost line focus after saving
If you refresh from the server or save an edited SP the line foucs
gets lost. Even if the SP in the DB differs from the SP that is
currently opened/edited,
the editor should try to go back to the line the user was.
<lihuang> Thank you for your suggestion. CR499560 is created for this
requirement and will be done in WorkSpace 2.1.



--
Thanks and regards,

Daniel Huang

Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Email: lihuang@sybase.com

<mpeppler@peppler.org> wrote in message
news:48117fcd.4e8e.1681692777@sybase.com...
>
>> debug complete SP-call
>> As an replacement for setting each single parameter in the
>> above mentioned way, it would be good
>> if one could just copy and paste the SP with its
>> paramaters into a single textfield. (maybe in the same
>> mask where one can set the single parameters)
>> e.g. : exec PR_spampleproc @par1='ok', @par2=12345,
>> @par3='XYZ' The idea behind this: we often take a whole SP
>> call from the debug window of our application, it would
>> then be more comfortable to debug it within workspace
>> instead of setting each single parameter manually
>
> I think that you can do this through the Debug dialog.
>
>> *Development-view
>> Syntax checking
>> Syntax checking seems to have problems with large SPs, as
>> syntax error are only
>> displayed at the beginning of the SP's code.
>
> Check the properties of the editor - the syntax
> coloring/checking is limited to x number of lines.
>
> Michael


Ivo Teubner Posted on 2008-05-14 15:01:01.0Z
From: Ivo Teubner <teubner@swisslab.de>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
Subject: Re: workspace's debugging features
References: <4811113d@forums-1-dub> <48117fcd.4e8e.1681692777@sybase.com> <4816a54c@forums-1-dub>
In-Reply-To: <4816a54c@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <482afead@forums-1-dub>
Date: 14 May 2008 08:01:01 -0700
X-Trace: forums-1-dub 1210777261 10.22.241.152 (14 May 2008 08:01:01 -0700)
X-Original-Trace: 14 May 2008 08:01:01 -0700, vip152.sybase.com
Lines: 67
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:704
Article PK: 1088396

Hello Daniel,

thank you for your answers and hints.

We are a software producer developing a laboratory information system
(LIS) which is widely used in Germany, mainly by medical university
laboratories. (www.swisslab.eu)

Our current DB-Version is ASE 12.5.3 with the latest EBF, after I read
your message, i also did an upgrade to Workspace 2.0.1.

-->Parameter values
I tried your workaround for 2.0.1 and it worked. However it does not
seem to show the parameter values corresponding to the debug-breakpoint.
It instead only shows the initial/call values.

<lihuang> And what is your requirements? Is it enough to show parameters
in 'Variables' view as readonly or you'd like to change parameter values
while debugging? If you only want to show parameters as readonly in
'Variables' view, we can support this feature in WorkSpace 2.1.
--> GREAT! For our purposes it would fully suffice to "see" the values
of the parameters. This, of course, according to the chosen breakpoint,
as the parameters often change their values within our SPs.

sortable parameter list
<lihuang> CR499556 is created for this requirement and will be done in
WorkSpace 2.1.
--> This is quite more comfortable. :)

debug complete SP-call
-->The saving function helps for developing purposes and is very useful.
However our scenario to find an actual problem is a little bit
different, as described within my last mail. We usually get a complete
SP call from our service team were "this or that " is not
working/shown/selected. As those calls differ very much: a simple text
field where we could just copy+paste the SP call would be very handy.

temptable problems
--> I will try to reproduce the errors as I do not want to post the
whole SP here.
My second temptable problem: The table is shown on the upper right
window, but its empty. There are no columns nor rows or fields.
Neither A refresh nor a new select with specified columns helps to
really show its content. I will also try to reproduce the error in an
exemplary SP.

*Development-view
Syntax checking
Syntax checking seems to have problems with large SPs, as syntax error
are only
displayed at the beginning of the SP's code.
<lihuang> Can you provide the detailed repo. steps?
--> It's just as simple as open a SP in the development view (procedural
editor) which is very long. E.g. 3000 lines. Syntax checking will then
not work anymore.
The syntax checking option "disable if more then x lines" is not active.


My last question concerning the Workspace Development is: Is there a
websites that deals with the ongoing Workspace development?
What i am trying to ask is: Is there a public roadmap or change request
(CR) list? What date is WS 2.1 scheduled?


Thanks in advance and
best regards
Ivo Teubner


Daniel Huang Posted on 2008-05-20 05:10:32.0Z
Reply-To: "Daniel Huang" <lihuang@sybase.com>
From: "Daniel Huang" <lihuang@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <4811113d@forums-1-dub> <48117fcd.4e8e.1681692777@sybase.com> <4816a54c@forums-1-dub> <482afead@forums-1-dub>
Subject: Re: workspace's debugging features
Lines: 109
Organization: Sybase
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48325d48@forums-1-dub>
Date: 19 May 2008 22:10:32 -0700
X-Trace: forums-1-dub 1211260232 10.22.241.152 (19 May 2008 22:10:32 -0700)
X-Original-Trace: 19 May 2008 22:10:32 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:708
Article PK: 1088383

Hi, Ivo:

Please see inline comments below and let me know if you have questions.

-->Parameter values
<Daniel> If you check 'Dumping variables' in Dump Variables & Table Data
dialog, all parameters and values should be shown in Console view. Can you
give us the detaled repo. steps so that we can look into it?


debug complete SP-call
<Daniel> Yes, it is very handy to copy+paste the SP call. And it is also
supported by WorkSpace. From workbench menu, select Run->Open Run/Debug
Dialog...-->Eclipse Data Tools. You can check 'Adhoc SQL' and paste your SP
call into Run field. It should meet your requirement.

Syntax checking
<Daniel> I created a stored procedure which has over 3000 lines and cannot
reproduce it.
You can go to Window --> Preferences --> Sybase, Inc --> Database
Development -->SQL Editor and see if the option 'Enable syntax validation'
is disable. And you can click Restore Defaults to get the default setting
for syntax validation.


--
Thanks and regards,

Daniel Huang

Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Email: lihuang@sybase.com

"Ivo Teubner" <teubner@swisslab.de> wrote in message
news:482afead@forums-1-dub...
> Hello Daniel,
>
> thank you for your answers and hints.
>
> We are a software producer developing a laboratory information system
> (LIS) which is widely used in Germany, mainly by medical university
> laboratories. (www.swisslab.eu)
>
> Our current DB-Version is ASE 12.5.3 with the latest EBF, after I read
> your message, i also did an upgrade to Workspace 2.0.1.
>
> -->Parameter values
> I tried your workaround for 2.0.1 and it worked. However it does not seem
> to show the parameter values corresponding to the debug-breakpoint. It
> instead only shows the initial/call values.
>
> <lihuang> And what is your requirements? Is it enough to show parameters
> in 'Variables' view as readonly or you'd like to change parameter values
> while debugging? If you only want to show parameters as readonly in
> 'Variables' view, we can support this feature in WorkSpace 2.1.
> --> GREAT! For our purposes it would fully suffice to "see" the values of
> the parameters. This, of course, according to the chosen breakpoint, as
> the parameters often change their values within our SPs.
>
> sortable parameter list
> <lihuang> CR499556 is created for this requirement and will be done in
> WorkSpace 2.1.
> --> This is quite more comfortable. :)
>
> debug complete SP-call
> -->The saving function helps for developing purposes and is very useful.
> However our scenario to find an actual problem is a little bit different,
> as described within my last mail. We usually get a complete SP call from
> our service team were "this or that " is not working/shown/selected. As
> those calls differ very much: a simple text field where we could just
> copy+paste the SP call would be very handy.
>
> temptable problems
> --> I will try to reproduce the errors as I do not want to post the whole
> SP here.
> My second temptable problem: The table is shown on the upper right window,
> but its empty. There are no columns nor rows or fields.
> Neither A refresh nor a new select with specified columns helps to really
> show its content. I will also try to reproduce the error in an exemplary
> SP.
>
> *Development-view
> Syntax checking
> Syntax checking seems to have problems with large SPs, as syntax error
> are only
> displayed at the beginning of the SP's code.
> <lihuang> Can you provide the detailed repo. steps?
> --> It's just as simple as open a SP in the development view (procedural
> editor) which is very long. E.g. 3000 lines. Syntax checking will then not
> work anymore.
> The syntax checking option "disable if more then x lines" is not active.
>
>
> My last question concerning the Workspace Development is: Is there a
> websites that deals with the ongoing Workspace development?
> What i am trying to ask is: Is there a public roadmap or change request
> (CR) list? What date is WS 2.1 scheduled?
>
>
> Thanks in advance and
> best regards
> Ivo Teubner


Daniel Huang Posted on 2008-05-21 01:43:56.0Z
Reply-To: "Daniel Huang" <lihuang@sybase.com>
From: "Daniel Huang" <lihuang@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <4811113d@forums-1-dub> <48117fcd.4e8e.1681692777@sybase.com> <4816a54c@forums-1-dub> <482afead@forums-1-dub>
Subject: Re: workspace's debugging features
Lines: 89
Organization: Sybase
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48337e5c@forums-1-dub>
Date: 20 May 2008 18:43:56 -0700
X-Trace: forums-1-dub 1211334236 10.22.241.152 (20 May 2008 18:43:56 -0700)
X-Original-Trace: 20 May 2008 18:43:56 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:710
Article PK: 1088385

Hi, Ivo:

BTW, we have announced a Q4 release for WS 2.1 to the field.


--
Thanks and regards,

Daniel Huang

Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Email: lihuang@sybase.com

"Ivo Teubner" <teubner@swisslab.de> wrote in message
news:482afead@forums-1-dub...
> Hello Daniel,
>
> thank you for your answers and hints.
>
> We are a software producer developing a laboratory information system
> (LIS) which is widely used in Germany, mainly by medical university
> laboratories. (www.swisslab.eu)
>
> Our current DB-Version is ASE 12.5.3 with the latest EBF, after I read
> your message, i also did an upgrade to Workspace 2.0.1.
>
> -->Parameter values
> I tried your workaround for 2.0.1 and it worked. However it does not seem
> to show the parameter values corresponding to the debug-breakpoint. It
> instead only shows the initial/call values.
>
> <lihuang> And what is your requirements? Is it enough to show parameters
> in 'Variables' view as readonly or you'd like to change parameter values
> while debugging? If you only want to show parameters as readonly in
> 'Variables' view, we can support this feature in WorkSpace 2.1.
> --> GREAT! For our purposes it would fully suffice to "see" the values of
> the parameters. This, of course, according to the chosen breakpoint, as
> the parameters often change their values within our SPs.
>
> sortable parameter list
> <lihuang> CR499556 is created for this requirement and will be done in
> WorkSpace 2.1.
> --> This is quite more comfortable. :)
>
> debug complete SP-call
> -->The saving function helps for developing purposes and is very useful.
> However our scenario to find an actual problem is a little bit different,
> as described within my last mail. We usually get a complete SP call from
> our service team were "this or that " is not working/shown/selected. As
> those calls differ very much: a simple text field where we could just
> copy+paste the SP call would be very handy.
>
> temptable problems
> --> I will try to reproduce the errors as I do not want to post the whole
> SP here.
> My second temptable problem: The table is shown on the upper right window,
> but its empty. There are no columns nor rows or fields.
> Neither A refresh nor a new select with specified columns helps to really
> show its content. I will also try to reproduce the error in an exemplary
> SP.
>
> *Development-view
> Syntax checking
> Syntax checking seems to have problems with large SPs, as syntax error
> are only
> displayed at the beginning of the SP's code.
> <lihuang> Can you provide the detailed repo. steps?
> --> It's just as simple as open a SP in the development view (procedural
> editor) which is very long. E.g. 3000 lines. Syntax checking will then not
> work anymore.
> The syntax checking option "disable if more then x lines" is not active.
>
>
> My last question concerning the Workspace Development is: Is there a
> websites that deals with the ongoing Workspace development?
> What i am trying to ask is: Is there a public roadmap or change request
> (CR) list? What date is WS 2.1 scheduled?
>
>
> Thanks in advance and
> best regards
> Ivo Teubner