Hi,
Currently, OOo uses boost 1.34.1 for platforms with a GCC =4, and boost
1.30.2 + a separated spirit 1.6.1 for all other platforms (see
boost/download in the source tree).
For various reasons, we'd like to clean up this mess, and move to a
single version (containing spirit).
This could be
Hi Christian,
Frank Schönheit - Sun Microsystems Germany wrote:
How to clear output trees? I'm a dummy concerning building.
In cygwin, something like
cd $SRC_ROOT
find . -maxdepth 2 -name wntmsci12* | xargs rm -rf
should do.
nitpickthe * is not protected against expansion from
Hi Regina,
ERROR: The following files could not be found:
ERROR: File not found: emboleobj.dll
ERROR: File not found: emsermi.dll
ERROR: File not found: oleautobridge.uno.dll
Sounds like some OLE-related module has not been built (correctly).
According to trunk, emboleobj is built in module
Hi Christian,
Because at least /me usually works in an environment where this doesn't
work (no complete source tree) :)
Doesn't dmake clean still work?
If the question was: Should it work in an OOo env? I suppose it should.
If the question was: Doesn't it work in the env you mentioned? No,
Hi Regina,
Searching with OpenGrok I see, that the file nametree.hxx is contained
in DEV300_m49 but no longer in DEV300_m50. A file object.hxx exists but
in store/source/ not in store/inc/store. Suggestions?
If you did not clear your output trees after updating to the new
milestone, a dmake
Hi Ivo,
I guess that for building a language pack the OOo source tree would not
be needed anymore, except maybe a few modules, is still a wish for the
far future?
MBA had the idea to move also all resource source files into a own
module but we first need to discuss this a bit further
Hi Regina,
How to clear output trees? I'm a dummy concerning building.
In cygwin, something like
cd $SRC_ROOT
find . -maxdepth 2 -name wntmsci12* | xargs rm -rf
should do.
Alternatively,
cd instsetoo_native
build --from solenv --prepare
should also do what you need, and also clear
the DEV300 m51 milestones contains the cws l10ncleanup04 that moves
all the translations that are spread over the office code to the new
module l10n.
Hey, wow, finally, well done! :-)
Good news; not only for translators, but also for developers because now
a recursive grep for some
Hi Caolán,
Who should maintain the data included in the script?
Developers themselves?
Ideally I guess the developers who maintain/don't actually maintain a
given module would update it themselves as owner there.
That won't work. Most developers do not even know this list, and even if
we
Hi Caolán,
I generally use
http://qa.openoffice.org/issue_handling/submission_gateway.html
as my launch page for submitting bugs.
Where do the default owners for patches there get filled in from ? Is
it simply hardcoded into the html of that page ? i.e. I wonder if that
page has fallen
Hi Malte,
Wrt the wish to automatically remove entries where the document is no
longer available: This is not so obvious for me.
I sometimes open documents from encrypted containers or network shares
which I mount on demand only, or from USB devices, so opening the menu
in the wrong time
Hi Rich,
and maybe checking for unavailable files when the menu is opened, and
making them visually different (either disabled, or coloured differently).
threaded, of course, so that it does not block the menu, but updates it
in the background, even while it is open :)
Given that this is
Hi Dan,
Using the tutorials in the wiki, I now know how to load, modify, and
save writer docs using the API. However, we are writing a desktop app
that we will distribute and would like to avoid distributing the open
office executables (just the api libraries, would be preferable).
All I
Hi Martin,
From my perspective one reason for the high amount of regression is the
high amount of integrated child workspaces short before a feature
freeze. In the moment the ITeam (the QA representative) does the
nomination before feature freeze. As an immediate action (for the
Hi Mathias et. al.,
The problem is ...
Seeing many different explanations in this thread, and suggested
solutions ... I wonder if we should collect some data about the concrete
regressions, before we start speculating 'bout the larger picture.
Oliver's table with the introduced in and found in
Hi Ingrid,
Two problems here. The worst one is that you cannot control that this
new rule is applied. Who decides that a code change is too huge to risk
it for the next release in two months or so? You won't count lines,
don't you - that would be stupid. Those who are willing to act
Hi Thorsten,
The problem is a bit more complex. The testers and test script writers
do not have any time for writing new test cases for new functionality,
they do not have time to check fixed issues in master, they do not have
time to check code changes in a CWS as much as they should and at
Hi Shuang,
I notice there is a qa sub-module under each module, for example sw/qa,
sd/qa.. but there is also a qadevOOo.
Who can tell me the relation ship of these qa related modules? Does
automation test of qadevOOo depend on qa of each module? How to build
these /qa ?
module/qa
Hi Ingrid,
that now bite us, most of them have been found by users or testers
*working* with the program. Adding more CWS test runs and so shortening
the time for real-life testing will not help us but make things worse.
I don't agree. Preventing the integration of bugs earlier in the
Hi Ingrid,
There are more than the VCLTestTool tests. We have the performance tests
and the UNO API test and the convwatch test. All those are in the
responsibility of the developers. I think only convwatch is not mandatory.
As far as I know, confwatch is mandatory, too. In theory, at
Hi Thorsten,
Writing good test scripts isn't an easy tasks you are right. This is
status for all software products. Writing test code costs more time
than writing other code. Try it out with UNIT tests ;-)
I know for sure. Writing complex test cases for my UNO API
implementations usually
Hi Max,
I just thought there is a higher chance of getting support for cygwin in
the near time than having these automated tests in EIS.
As far as I know, there's a group working on this. It would still leave
us with the reliability problem (sometimes a test simply gives you bogus
results,
Hi Max,
Do you know, how often a CWS returns back to development because of
broken functionality, not fixed issues or process violation?
of course in regards to process violation, nothing would change. I am
talking about e.g crashing issues. If the developer tried it and it does
not
Hi Rich,
summary - while release early, release often is very important, stable
dev snapshots are as important.
Yes, but how to reach that? In theory, trunk is always stable, since
every CWS has undergone tests (before integration) which ensure that it
doesn't break anything. Okay, enough
Hi Max,
yes, this is true, so would you say we could skip the step from going
from verified to closed, doing this verification again?
I'd say this gives the least pain/loss.
(Though my experience with dba31g, whose issues were not fixed at all in
the milestone which the CWS was integrated
Hi Christian,
Maybe in the cvs days. Now with svn there have been a couple of failed
integrations, quite a number of changes that were reverted by other
cws.
Using the verified-closed step to find broken
tooling/SVN/integrations/builds sounds weird, doesn't it? So, this
shouldn't be a
Hello KP,
Promoting QA in community is not enough - you have to retain people. In
order to retain people project needs to fix their issues, which inspires
people to use milestones in daily work.
Many of developers do not know how great it feels when issue you are
interested in gets fixed
Hi Thorsten,
The time to master isn't a problem currently, I think.
That's not remotely my experience.
See dba31g
(http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=7708OpenOnly=falseSection=History)
for a recent example of a CWS which needed 36 days from ready for QA
to integrated state
Hi Mechtilde,
So more testing on CWS is also welcome!
Yes Full ACK to last sentence.
And this is not only a task for the Sun people. The persons who are
interested at a CWS must be able to test a CWS. And this also if they
aren't able to build OOo on their own.
I think especially we in
Hello Kirill,
Uhm, I doubt that. What you're saying here is that we should sacrifice
quality to more fixes. I believe this would be bad for OOo's overall
reputation.
What I mean to say is that we could sacrifice quality of snapshots to
bring in features faster and to motivate QA
Hi Mathias,
I don't see a lot of sense in making tests mandatory just because we
have them. If a test probably can help to find problems in areas where
we know that we have them, fine. So when tests are defined it's
necessary to see which problems they can catch and if that's what we need.
Hi Mechtilde,
I don't think that the developer have to upload each CWS build. I prefer
that the possible tester are able to pick up the CWS builds they want
beside the normal test scenario.
Ah, you're right, that would be most helpful ...
Ciao
Frank
--
- Frank Schönheit, Software Engineer
Hi Mathias,
However a reasonable error handling would look like, IMO carefully
re-designing UNO to add more exceptions specifications to (a lot of)
methods is a must-have.
+1
Just to play the devil's advocate: without careful considerations that
would end in adding throws
Hi Rainman,
After a period of time of developing with URE, I find the C++ UNO
class Reference is not very comfortable for use sometime.
The problem is, when I have a reference of base interface XA and a
reference of derived interface XB, I can't make xA = xB directly.
Instead I have to query
Hi Eike,
OTOH designing exceptions right is very hard and often needs a lot of
thinking. So I don't expect that we can fix that in a big bang
release, we will need quite some time to fix that.
I would be happy if we would allow for such fixing. I don't want to fix
all of those at the same
Hi Rainman,
I have another ideal, it is better and safer than the last one I mentioned.
I add a conversion operator to Reference, instead of a constructor, here is
it:
template class base_interface_type
inline SAL_CALL operator const Reference base_interface_type ()
const
Hi Stephan,
The only problem I see is that classes implementing the respective
interface need to be adjusted, too, which of course is error prone. If
this adjustment is not made, implementations throwing the new exception
might crash (at least on platforms where the compiler respects the
Hi Rony,
*The former: it is just frustrating to have a program bomb and get a
message like exception occurred. (Yielding the message: go, figure...)*
which nicely fits into the original thread :)
Fixing those exceptions (which I consider buggy in the current
messageless-shape) to carry a
Hi T. J.,
May I agree, wholeheartedly?
From my own long years of dealing with users (some of them very angry),
I conclude that the *error* is what bothers them, not the error
*message*. They just want to get their work done. A little techno-babble
is only a small point.
...
Consider
Okay, I see your point here. I am still not convinced that transporting
the information via css.Exception.Message is the best idea ever, and
won't cause problems later on, but I definitely see your point.
See my other mail in response to Stephan's comment, which I saw after I
wrote the above
Hi Stephan,
For one, end-user oriented exception messages simply do not work in
general (think about the category of unchecked or runtime or
programmer made a coding mistake exceptions---what use is it for the
end user to see a localized Index i=7 was out of bounds of array
Hi Mathias,
When we talk about seldom, hard to reproduce errors, then let's
introduce a logger which is permanently switched ON, or at least
switched ON for log levels = LogLevel.SEVERE. (by default, loggers are
OFF, i.e. do not log any event, regardless of the LogLevel.)
Everything that
Without having the bigger picture how good error handling should look
like
while we are at it, and mentioned UNO incompatibility already ...
I just came across (yet) another issue where a severe error was silenced
instead of propagated to the caller (and thus caused document
corruption),
Hi Mathias,
I think that exception messages are not made for end users.
As already said, this might be the fundamental point of disagreement
between us :)
Usually
errors and exceptions in programs must be interpreted, put into a
context and translated before they can be presented to users.
Hi Mikhail,
My intention was to allow user provide the developer with information
that identifies the source of the error.
That's understood.
It would be useful in case of
problems that appear once a year, and look to be mysterious from the
first view.
Ugly is a taste-related comment,
Hi Stephan,
Even if there happen to be exception instances where the exception
message is designed to be meaningfully presented to an end user (do you
indeed use localized exception messages?)
(yes, indeed, we do)
this is not true for the
majority of exception instances (where the
Hi Roman,
Max already have you some pointers, but one note on the following:
I using
VisualStidio 2005, so could you help me to get started?
As far as I know, VS2005's compiler is not supported for the current
code line anymore. You should get an Express edition of Visual Studio
(it's for
Hi Pavel,
We might have a communication problem. In my understanding, changing
resources so that the effective strings stay the same, but maybe
identifiers change, or strings are moved within files, or such, is an
alloed change.
string is and ordered set of: { actual string, identifier }.
Hi Ause,
in the current scenario, there is only one active patch per source
tarball which has to contain all required changes for the build. as
discussed in issue 40246, this may lead to duplication and hard to
maintain patches.
with the changes done in the cws ause099, each change now
Hi Oliver,
can one give me a hint, why i get warnings for the following *.idl files ??
...
module bw {
module stv {
module tvs {
module structedit {
module tool {
interface
Hi Bernd,
Well the fine grained control suggestes by you Frank is not as easy to
implement as it might first look like: there´s lot of places where
different kinds of changes to data in EIS is being made and each one
would have to be reviewed and decided upon wether and what kind of mail
Hi Bjoern,
As an (ugly, very ugly) workaround for now, we might need a command in
the cws tool that registers the moved files by their old name (the
name it is known as on the master) somewhere. This could be either in a
svn property (on trunk??) or in a administrative file somewhere. It
Hi Heiner,
I wouldn't call for a complete ban but it looks like one has to be extra
careful. Restructuring should be done in CWS which lives only a very
short time. Best, say, opened on one milestone and integrated in the
next (as first CWS) this would minimize the potential for data loss.
Hi Ariel,
I'd like to keep truck of some CWS activities in EIS (well, mostly when
they get integrated), are there RSS channels to this kind of info? I've
been searching with no luck, so I guess there is none, but...
I'd love to have some kind of CC functionality to EIS. That is, you
can
Hi Ariel,
I'd like to keep truck of some CWS activities in EIS (well, mostly when
they get integrated), are there RSS channels to this kind of info? I've
been searching with no luck, so I guess there is none, but...
I'd love to have some kind of CC functionality to EIS. That is, you
can
Hi Stephan,
So, back to good old manual merging: Remember which files you moved
in your CWS, and after every rebase, check whether they miss any
changes to the original files. Sigh.
With the additional hurdle that nobody will warn you about the lost
changes. If the compiler finds them,
Hi Eike,
Looks like connectivity/prj/build.lst needs a dependency on qadevOOo, or
am I mistaken?
You aren't, /me thinks. Feel free to write me a P1 issue, so we can fix
this in the next build.
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems
Hi Rene,
Looks like connectivity/prj/build.lst needs a dependency on qadevOOo, or
am I mistaken?
You aren't, /me thinks. Feel free to write me a P1 issue, so we can fix
this in the next build.
but please guard this with an ENABLE_QADEVOOO or however it is caled variable
so that it doesn't
I find it very abnormal that the person who shoots an issue can't close it.
abnormal is a somewhat strong word :), but yes.
I suppose the ability to resolve/close issues is bound to the
canconfirm privilege - which users don't initially have, instead they
need to apply for it.
Sadly, we don't
Hi,
modifying a .cxx file on Windows, and committing it to SVN, followed by
a svn diff -r PREV file, shows me that *the complete* file changed
with the commit. Doing a svn diff -r PREV -x --ignore-eol-style file
shows me only the changes which I just did.
Conclusion: We have a problem with our
Hi Heiner,
Let me hear your thoughts. Should we go to svn:eol-style native? For
which file types? Or should we stay with Unix and require that people
use editors which preserve the line end conventions? Is that even
possible for the more popular editors (I use vim, so I wouldn't know).
This
Hi Björn,
Given that pre- and postcommit hooks are basically working the same,
using this precommit hooks as a base to create a postcommit hook should
be easy.
See issue 95199 for my currently prepared (and already implemented)
solution, though a post-commit hook also sounds interesting.
Hi Bjoern,
I just tried to add an svn:ignored dir. That works.
Sure - svn:ignore is just for ignoring the item in status and recursive
commits.
If someone does a svn diff in a module, and sees:
? source/somenewfile.cxx
? source/somenewfile.hxx
he might be tempted to do a 'svn add *; svn ci
Hi,
now that we start working with SVN-based CWSes, those module output
trees (common[.pro], unxlngi6[.pro], wntmsci12[.pro] etc.) become
somewhat inconvenient, as they clutter your svn status output, for example.
http://wiki.services.openoffice.org/wiki/OOo_and_Subversion#Ignoring_output_trees
Hi Heiner,
On 10/16/08 11:00, Malte Timmermann wrote:
In short: Can we please add the platform-dependent output tree names
as svn:ignore property to all modules?
+1
+1
-1
I tried to explain why I think the property-approach is better, please
also elaborate why you think it isn't. Just
Hi Heiner,
Well, this +1 or -1 one in s a kind of vote and you normally don't have
to explain your votes. Note that I didn't say We will not do this, I'm
the maintainer of this stuff, basta! :-) Just a vote.
Ah, okay ;)
These are roughly 50 platforms times 191 top level dirs, about 9550
Hi Heiner,
[...]
Well, you probably already noticed that I'm somehow not very
enthusiastic about maintaining these 1 entries. Remember, you'll
have to add the properties every time someone invents a new top level
directory, which means with most milestones.
We have 191 modules so far,
Hi Thorsten,
I know that developers want to start it from the command line.
Well, developers want a way to easily judge the quality of their work. I
don't care whether testtool can be run from command line, it's just the
environment I'm used to ... If you give us a possiblity to run testtool
Hi Heiner,
Yes, this can (and should) be done by RE, if we decide drop the VCS
keywords. Most probably not m33, but at some time in the near future.
would be good.
Another huge change which could be done in the same milestone is to
convert tabs to 4 spaces, something I know Kendy and some
Hi Heiner,
'svn merge -x -b' is your friend ...
You mean ... I really should go reading this Handbuch? :)
Could be done, and the earlier the better I guess.
As long as we still have CVS-based CWS'es, which need to be migrated ...
not sure. Finally, migration will probably usually happen by
Hi Heiner,
As long as we still have CVS-based CWS'es, which need to be migrated ...
not sure. Finally, migration will probably usually happen by create a
CWS in SVN, based on the latest milestone, and *patch* in the changes of
the CVS-CWS. In this case, svn merge is of no help. Instead, it
+1 for the proposal
+1
Is this something which can/should be done by release engineering, for
instance with the switch from m32 to m33, globally?
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems
Hi Andrey,
I am writing an OO.org extension that is a thin wrapper around a C++
library, which is compiled externally.
I think the latter is the problem - you need to compile the library
within the same environment as you compile OOo, in particular against
STLPort.
Note that that's a
Hi Christian,
What I am looking for is a volunteer who could do the Windows build the
CWS moz2seamonkey, including the Mozilla-build (i.e. without the
above-mentioned configure-time switches which effectively disable it).
If this said volunteer could work with Pierre/me to solve any problems
Hi Rene,
(I admit I had hope that some of the people saying please replace the
stone-aged Mozilla code with something new would step in :)
Not on windows, no :)
:)
We're glad about any help on the other platforms as well. Currently,
Pierre does Linux, and Eric builds on Mac (and /me has to
Hi Juergen,
Hoping to see your marcos soon~ hehe.
i am not fan of macros and the skeletonmaker can be already used for
both (declaration and forwarding).
I think it is no real overhead and changes are not so often.
Which is merely wrong - in case we're talking about API which is
currently
Hi Juergen,
This is also what you said last time I brought up this idea/request :)
really, maybe you should submit a feature request ;-)
Ah, you caught me, Go visit IssueZilla! is usually the response *I*
give to *others*, not the other way round :)
Ciao
Frank
--
- Frank Schönheit, Software
Hi,
just noticed that in m18, deliver isn't as gossipy as before: doing a
deliver in a module just prints
deliver -- version 1.127
Module 'module' delivered successfully. x files copied, y files
unchanged.
While this is nice in contexts where you are not interested in *what*
got actually
Hi Caolan,
deliver -verbose also works
That's the one I was looking for ... well, I could have thought of this,
couldn't I?
Thanks Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems http://www.sun.com/staroffice -
-
Hi Jan,
I assumed it would live in cws_dev300_sb83, but I get
cvs -d :pserver:[EMAIL PROTECTED]:/cvs co -r cws_dev300_sb83
framework/desktop
cvs [checkout aborted]: no such tag cws_dev300_sb83
How do I find the right tag to generate the patch?
The CWS sb83 was created on SRC680,
There was some resistance to nominating this for 3.0 because ChristianL
wanted to re-do the translation work to use Java Properties instead of
the new transex tool we wrote that translated complete XML files
per-lang.
This is bogus, I discussed with Jan that in my opinion it is a
Jacek,
I have been testing OO.o 3.0.0 since DEV m3. I noticed that starting
from m10 installation program does not register file extension in the
system and it is impossible to open any document file just by
double-clicking on it. The same applies to both BEA m1 and m2
versions.
Somebody
Hi Caolan,
See http://people.redhat.com/caolanm/callcatcher/DEV300_m10/ for full
list. Top three offenders are...
sorry for the dumb question, but what are uncallable methods?
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems
Hi Stephan,
And all this weird code in except.cxx is only necessary because our C++
UNO exceptions do not make plain C++ RTTI available (see Frank's post)!
This got me thinking: What about actually changing the C++ UNO
binding, conditionally for _MSC_VER = 1500 only, for OOo 3.0, by
Hi Stephan,
I do not see any elegant solution for this problem. Potential but ugly
solutions would include:
All are ugly, aren't they ...
Judging from myself: I first got introduced to
::cppu::getCaughtException when I tried to dynamically determine the
type of the caught exception in an
Hi Thorsten,
Frank Schönheit - Sun Microsystems Germany schrieb:
I'm all in for somebody else doing work :), and I do not doubt that it
is *reasonable* to remove external include guards /in general/.
I only suspect that the minor gain we get from this is not worth the
potential medium or big
Hi Thorsten,
With dbaccess as well?
Yes.
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems http://www.sun.com/staroffice -
- OpenOffice.org Base http://dba.openoffice.org -
- - - - - - - - - - - - - -
Hello Jianhua,
Create a uno control in Calc, and make it invisible by Basic,
Save the docuemnt, and then reload it, the uno control still
visible.
This because ODF do not support this property.
does we have any plan for supporting this feature?
No plans.
Note that for consistency, one
Hi Hubert,
I don't know if you have noticed, but they are been several request from
people to have OOo ported to embedded devices like Maemo and iPhone, for
which Java is likely to be an even bigger problem.
Come on. When we ever port OOo to one of those platforms, Java is one of
our smallest
Hi Thorsten,
I cannot imagine changes to OOo code that do not potentially cause
pain someone somewhere. The thing is, it's a change for the better,
removes a ton of unnecessary, fragile hard to maintain code, and there
simply won't be a better time for this.
Sure. Again: The question is
Hi Nikolai,
The uglyness IMHO is not subjective, and a defect. Maintainability is
a major problem in any project as huge as OOo,
Sure.
- unnecessary code
Which is true for a lot of other places, too. I usually fix those
incrementally :)
- a potential cause for difficult to find errors,
Hi Thorsten,
kendy and me now intend to execute the once-postponed plan to remove
external header guards (that #ifndef STUFF #include STUFF #endif
ugliness). A bit more background:
http://blog.thebehrens.net/2008/02/05/obsolete-external-header-guards/
We already discusses this a little bit
Hi Mathias,
Sounds like the decision to remove the box was perhaps ... premature?
No, just the way it was done is wrong. We should do it the following
way: if the file name contains something that looks like an extension,
leave it alone. If it doesn't contain a dot, add the extension. This
Hi Bernd,
Well yes it´s a rather simple algorithm and well normally your
expectation would be right that in this case the text from the first
paragraph of the abstract would be used. But well here it´s special. The
spec document has been changed in a way that the abstract can not be
Hi Bernd,
Looking into the allfeatures mailing list (did I already say kudos to
you for working around collab.net's bug, so this list now works,
again?), of the last 10 feature mails, 8 contained a specification link,
where 5 referred to older-and-extended specs (including the broken one).
Means
Hi Bernd,
Just have a look at
http://development.openoffice.org/releases/2.3.0.html to get an
impression, these are the actucal release notes for the 2.3.0 user Release.
And that´s the result of what we currently semi-automatically generated
for the 2.0.3 Release by parsing (or not
Hi Philipp,
while I`d generally agree, there is the infamous Solarmutex of vcl which
is a derivative of the vos::IMutex interface and needs that to do
refcounting. I don`t think sal`s Mutex class has virtual methods.
Of course you could move that interface out of vos to vcl, if the
Hi Mathias,
Perhaps we should follow up on this elsewhere.
You're right, issue 81309 is not the proper place. [EMAIL PROTECTED] might be
better.
The problem is when people use code without asking its owner (if someone used
so3 without asking me or mav that would be the case)
Come on. We
side note: If the man who did
ResMgr* SoDll::GetResMgr()
{
// resources are in the default res mgr (OFA)
return NULL;
}
would have done this change - from an own SoDll::pResMgr to the OFA res
mgr - *properly*, and would have removed this function, together with
all - unused
Hello Du Yunfen,
one thing beforehand: Great to see you think I'm the right person for
this kind of problem :), but actually this touches code areas which I
barely know. Thus, I think this discussion is best continued at
[EMAIL PROTECTED] I send this mail to the list, and would like to ask
you to
1 - 100 of 112 matches
Mail list logo
