testimony-devel — Mailing list for testimony developers.

Re: [Testimony-devel] Flat Files

[Carlos T. <ct...@gm...>]

Hi Jochen,

Sadly the Testimony project is not being maintained anymore. I known that
with Java 1.4 it was working, but I haven't tried to run it in Java 5 or 6.

I'll try to execute the code in Java6 and fix any crash that I can find.
Anyway I cannot promise you anything right now since right now I'm really
busy, but I will do what I can.

Best Regards,

On 8/21/07, Jochen Garcke <gc...@ga...> wrote:
>
> Hi,
>
> not sure if anyone is still around on this list...
>
> The GCD can import Flat Files again (with a little hand-touching by the
> Editors)
>
> I wanted to test if Testimony still works, it doesn't seem to like Java
> 1.5, it breaks right at the beginning.
>
> If someone is still around and this is easily fixable that would be
> excellent.
>
> Cheers,
> Jochen
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Testimony-devel mailing list
> Tes...@li...
> https://lists.sourceforge.net/lists/listinfo/testimony-devel
>

[Testimony-devel] Flat Files

[Jochen G. <gc...@ga...>]

Hi,

not sure if anyone is still around on this list...

The GCD can import Flat Files again (with a little hand-touching by the 
Editors)

I wanted to test if Testimony still works, it doesn't seem to like Java 
1.5, it breaks right at the beginning.

If someone is still around and this is easily fixable that would be 
excellent.

Cheers,
Jochen

[Testimony-devel] Testimony v1.2 Released

[Carlos T. <ct...@te...>]

Hi Peter,
 
Today I've released the v1.2. Please test it and tell me what do you think
 
I tried to do the distribution with the buil.xml, but the upload task needs
a password, and I don't see how to configure it :(
 
Regards,
Carlos.

[Testimony-devel] Import fixed

[Carlos T. <ct...@te...>]

Hi Peter,
 
Finally I've found a better, and I hope, definitive solution. Instead of
using an external library, I've used the Java API for HTML parsing. I think
that future updates will be easier, because now we're ignoring tags and
getting directly the info from the HTML.
 
I've done some fast tests and seems that works fine.
 
Regards,
Carlos.

[Testimony-devel] Testimony issue info import from GCD site

[Carlos T. <ct...@te...>]

Hi Peter,
 
I've done some research and I think that I've found what we need. Take a
look to http://htmlparser.sourceforge.net it's a java parser library. Can be
used in a lot of ways, even to send info. I've done some quick tests and
seems that cover our needs, but would mean to insert and external library
dependency in our code. What do you think? The way the HTML code is now is
quite difficult to parse without external help.
 
I'm looking forward to hearing from you.
 
Regards,
Carlos.

[Testimony-devel] Fixes

[Carlos T. <ct...@te...>]

Hi Peter,
 
I've just commited some minor changes.
 
- Fixed build.xml bug that corrupted the binary files while copying them to
the build folder
- Fixed some javadoc errors
- Fixed dummy error importing series
 
I'm testing the application and I've found a new problem. Since the OI is
active again, the issue webpage structure has been changed, and now is more
difficult to read the info. Do you think you have enough time to fix it? If
not, please answer ASAP and I'll see what can I do, but I'm a bit short of
time and I was working in other problems (progressbars and other bugs
fixings) I would like to release the 1.2 version next weekend, but we cannot
do that without fixing that.
 
Regards,
Carlos.

RE: [Testimony-devel] About the latest commits

[Carlos T. <ct...@te...>]

Hi Peter,

Don't worry, I'm also quite busy these last weeks. I'll try to test that in
the next few days. With a little bit of luck, if everything works fine I'll
finish the progressBars code in the next week and then I'll do the 1.2
release finally.

On the other hand I go on vacations August,6th and I'll not come back until
22, so I don't think that I'll be able to work in the code until end of
August. I wish that after that I'll have some free time again to continue
with the same strenght than the last months :)

Regards,
Carlos.

> -----Mensaje original-----
> De: tes...@li... 
> [mailto:tes...@li...] En 
> nombre de Petter Wintzell
> Enviado el: viernes, 16 de julio de 2004 17:09
> Para: Testimony devel
> Asunto: Re: [Testimony-devel] About the latest commits
> 
> Hi Carlos,
> 
> Sorry for not answering your mail sooner! I've had a lot on 
> my mind, I've had a hell of a busy time at work the past few 
> weeks... Unfortunately, I'll be away for the next three weeks 
> and won't be able to contribute anything during that time 
> either, and only read mail sproadically.
> 
> Anyway, I've committed some changes that might interest you, 
> related to the home page:
> 
> The home page is now part of the testimony module, under 
> doc/home_page. There is a new Ant task that copies the 
> committed home page (the on in the CVS
> repository) to the SourceForge server so that it becomes 
> visible to end users. Please try this out if you can, it 
> works when run using my user and I think it should work for 
> everyone, but you never know...
> 
> Also, I have removed the crontab entry that automatically 
> updated the home page from CVS every night. That means that 
> when changes are made to the home page, the Ant target has to 
> be run manually.
> 
> I have also added some new properties. You need to define 
> those to run the new task.
> 
> About the properties files: When I add new properties, those 
> are added to the config/testimony.properties.template file. 
> All other users (meaning you at the moment... :) ) Have to 
> apply the same changes to their config/testimony.properties 
> files, or the new tasks won't work. Maybe that's the problem 
> you've been seeing?
> 
> The Ant script should warn if the properties file is newer so 
> that the user is alerted that an update is needed.
> 
> > Yesterday I saw the CheckStyle fixings in the Ant file, that's now 
> > working correctly :) I also saw some new tasks to do the 
> distribution 
> > upload, but I don't see how it works (maybe, is some 
> property missed? 
> > or I forgot to update something?). There is also another strange 
> > problem. For some reason, the New16.gif file is always copied 
> > corrected to the build folder ???
> 
> What kind of problem are you experiencing?
> 
> Examine the testimony.properties.template file and see that 
> all properties are also in your testimony.properties file. 
> Also, they have to be properly defined.
> 
> The create distribution tasks require extra work - a key 
> repository has to be created for instance. It should be 
> explained in the property file and in the Ant script (running 
> the help task will produce info)... If it's not 
> understandable I'll improve the documentation.
> 
> Could your un the task again and mail me the output?
> If there's a bug I'll fix it.
> 
> > I'm testing it as much as I can, but almost everyday I find 
> some minor 
> > bug that needs to be fixed (dummy thinks, almost always 
> related with 
> > the last commits, basically because of the code
> > reorganization) Anyway would be great
> > if you try to use it a little bit to see if I missed something.
> 
> Good idea. I'll try to test some. It's always good if another 
> set of eyes examines the program...
>  
> > Once the Ant file is done, will you be able to do something 
> with the 
> > website? I think that needs and urgent update (new screen shoots, 
> > maybe some redesign, ...) Would be great to launch the 1.2 version 
> > with an updated site, what do you think?
> 
> Would be good, but I don't think I can find the time, 
> sorry... Also, it might be better if the page is updated by 
> you, since you know the changes that's been made during the 
> past months.
> 
> Regards,
> Petter
> 
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
> http://promotions.yahoo.com/new_mail 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop FREE 
> Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Testimony-devel mailing list
> Tes...@li...
> https://lists.sourceforge.net/lists/listinfo/testimony-devel
> 

Re: [Testimony-devel] About the latest commits

[Petter W. <pet...@ya...>]

Hi Carlos,

Sorry for not answering your mail sooner! I've had a
lot on my mind, I've had a hell of a busy time at work
the past few weeks... Unfortunately, I'll be away for
the next three weeks and won't be able to contribute
anything during that time either, and only read mail
sproadically.

Anyway, I've committed some changes that might
interest you, related to the home page:

The home page is now part of the testimony module,
under doc/home_page. There is a new Ant task that
copies the committed home page (the on in the CVS
repository) to the SourceForge server so that it
becomes visible to end users. Please try this out if
you can, it works when run using my user and I think
it should work for everyone, but you never know...

Also, I have removed the crontab entry that
automatically updated the home page from CVS every
night. That means that when changes are made to the
home page, the Ant target has to be run manually.

I have also added some new properties. You need to
define those to run the new task.

About the properties files: When I add new properties,
those are added to the
config/testimony.properties.template file. All other
users (meaning you at the moment... :) ) Have to apply
the same changes to their config/testimony.properties
files, or the new tasks won't work. Maybe that's the
problem you've been seeing?

The Ant script should warn if the properties file is
newer so that the user is alerted that an update is
needed.

> Yesterday I saw the CheckStyle fixings in the Ant
> file, that's now working
> correctly :) I also saw some new tasks to do the
> distribution upload, but I
> don't see how it works (maybe, is some property
> missed? or I forgot to
> update something?). There is also another strange
> problem. For some reason,
> the New16.gif file is always copied corrected to the
> build folder ??? 

What kind of problem are you experiencing?

Examine the testimony.properties.template file and see
that all properties are also in your
testimony.properties file. Also, they have to be
properly defined.

The create distribution tasks require extra work - a
key repository has to be created for instance. It
should be explained in the property file and in the
Ant script (running the help task will produce
info)... If it's not understandable I'll improve the
documentation.

Could your un the task again and mail me the output?
If there's a bug I'll fix it.

> I'm testing it as much as I can, but almost everyday
> I find some minor bug
> that needs to be fixed (dummy thinks, almost always
> related with the last
> commits, basically because of the code
> reorganization) Anyway would be great
> if you try to use it a little bit to see if I missed
> something.

Good idea. I'll try to test some. It's always good if
another set of eyes examines the program...
 
> Once the Ant file is done, will you be able to do
> something with the
> website? I think that needs and urgent update (new
> screen shoots, maybe some
> redesign, ...) Would be great to launch the 1.2
> version with an updated
> site, what do you think?

Would be good, but I don't think I can find the time,
sorry... Also, it might be better if the page is
updated by you, since you know the changes that's been
made during the past months.

Regards,
Petter



		
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 

[Testimony-devel] About the latest commits

[Carlos T. <ct...@te...>]

Hi Peter,

Yesterday I saw the CheckStyle fixings in the Ant file, that's now working
correctly :) I also saw some new tasks to do the distribution upload, but I
don't see how it works (maybe, is some property missed? or I forgot to
update something?). There is also another strange problem. For some reason,
the New16.gif file is always copied corrected to the build folder ??? 

Between yesterday and today I've done some new commits. What I've done is:
- Simplify the MainFrame class. I've splitted all the actions (in their own
package) and the MenuBar and ContextMenu in their own classes.
- Added progress dialog to the sort process
- Added support for specific progress in the progress dialog (that's to show
the exact progress ie: 57%)
- Show correct progress when importing a serie from the GCD site
- Fixed some minor language problems
- Added a minimum documentation to the language files
- Added the Changelog, Report Bugs and Request Features menu options (just
connects to the website)

The next steps will be:
- Correctly show the progress when importing an issue from the GCD site or
the list of issues for a serie
- Correctly show the progress when loading a file
- Only show the ProgressDialog if the process needs more than 2 seconds ?
- Fix the Autocomplete logic to work ignoring case

I'm testing it as much as I can, but almost everyday I find some minor bug
that needs to be fixed (dummy thinks, almost always related with the last
commits, basically because of the code reorganization) Anyway would be great
if you try to use it a little bit to see if I missed something.

Once the Ant file is done, will you be able to do something with the
website? I think that needs and urgent update (new screen shoots, maybe some
redesign, ...) Would be great to launch the 1.2 version with an updated
site, what do you think?

Regards,
Carlos.

RV: [Testimony-devel] Broken Ant script

[Carlos T. <ct...@te...>]

No problem :)

I've just done a commit with some CheckStyle fixings and some minor bugs
(mainly from the previous commit) fixings.

Cheers,
Carlos
> -----Mensaje original-----
> De: tes...@li...
> [mailto:tes...@li...] En nombre de 
> Petter Wintzell Enviado el: jueves, 24 de junio de 2004 17:36
> Para: Testimony devel
> Asunto: RE: [Testimony-devel] Broken Ant script
> 
> Hi Carlos,
> 
> The checkstyle task of the Ant script should work now.
> I've also added tasks for uploading the built releases that's supposed 
> to run using web start.
> 
> I think I'll move the lib file to a subdirectory of tools/CheckStyle 
> if that's OK with you - I think we should try to keep the number of 
> directories (and
> files) in the root to a minimum...
> 
> Regards,
> Petter
> 
> --- Carlos Tasada <ct...@te...> wrote:
> > Already done, I hope :)
> > 
> > > -----Mensaje original-----
> > > De: Petter Wintzell
> > [mailto:pet...@ya...]
> > > Enviado el: jueves, 24 de junio de 2004 9:13
> > > Para: Carlos Tasada
> > > Asunto: RE: [Testimony-devel] Broken Ant script
> > > 
> > > Hi Carlos,
> > > 
> > > I see them now, I misconfigured my CVS client so
> > new
> > > directories were not updated, sorry...
> > > 
> > > Anyway, let me know when you have moved the files
> > around and
> > > I'll take a look at the Ant script.
> > > 
> > > Regards,
> > > Petter
> > > 
> > > --- Carlos Tasada <ct...@te...> wrote:
> > > > Hi Peter,
> > > > 
> > > > Definitively is there. First I looked with the
> > WebCVS and
> > > then I did a
> > > > checkout, anyway I'll try later to commit in the
> > new path,
> > > don't worry
> > > > :)
> > > > 
> > > > Regards,
> > > > Carlos. 
> > > > 
> > > > > -----Mensaje original-----
> > > > > De:
> > tes...@li...
> > > > >
> > > >
> > [mailto:tes...@li...]
> > > > En
> > > > > nombre de Petter Wintzell
> > > > > Enviado el: jueves, 24 de junio de 2004 7:51
> > > > > Para: Testimony devel
> > > > > Asunto: RE: [Testimony-devel] Broken Ant
> > script
> > > > > 
> > > > > Are you sure about that? I did an update just
> > now,
> > > > and I did
> > > > > not get any new files...
> > > > > 
> > > > > Could it be that you made some mistake when
> > adding
> > > > the files,
> > > > > like doing a CVS add but forgetting the
> > commit?
> > > > > 
> > > > > If so, it may not be bad news because we can
> > add
> > > > CheckStyle
> > > > > to a tools directory instead.
> > > > > 
> > > > > If not, there's something weird going on.
> > Could
> > > > you try to do
> > > > > an update of the CVS tree to a different
> > location
> > > > and see if
> > > > > you get the new files?
> > > > > 
> > > > > Regards,
> > > > > Petter
> > > > > 
> > > > > --- Carlos Tasada <ct...@te...>
> > wrote:
> > > > > >  
> > > > > > Hi Peter,
> > > > > > 
> > > > > > The CheckStyle is committed in the CVS (I
> > forgot
> > > > to do that
> > > > > the first
> > > > > > day, but is in the CVS since a couple of
> > days
> > > > ago). On the
> > > > > other hand
> > > > > > I agree with you about the new structure.
> > > > > > 
> > > > > > Regards,
> > > > > > Carlos.
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 		
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! Mail - 50x more storage than other
> > > > providers!
> > > > > http://promotions.yahoo.com/new_mail
> > > > > 
> > > > > 
> > > > >
> > > >
> > >
> >
> -------------------------------------------------------
> > > > > This SF.Net email sponsored by Black Hat
> > Briefings
> > > > & Training.
> > > > > Attend Black Hat Briefings & Training, Las
> > Vegas
> > > > July 24-29 -
> > > > > digital self defense, top technical experts,
> > no
> > > > vendor
> > > > > pitches, unmatched networking opportunities.
> > Visit
> > > > 
> > > > > www.blackhat.com
> > > > _______________________________________________
> > > > > Testimony-devel mailing list
> > > > > Tes...@li...
> > > > >
> > > >
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/testimony-devel
> > > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > 	
> > > 		
> > > __________________________________
> > > Do you Yahoo!?
> > > New and Improved Yahoo! Mail - 100MB free storage!
> > > http://promotions.yahoo.com/new_mail
> > > 
> > 
> > 
> > 
> > 
> >
> -------------------------------------------------------
> > This SF.Net email sponsored by Black Hat Briefings & Training.
> > Attend Black Hat Briefings & Training, Las Vegas July 24-29
> - digital
> > self defense, top technical experts, no vendor pitches, unmatched 
> > networking opportunities. Visit www.blackhat.com 
> > _______________________________________________
> > Testimony-devel mailing list
> > Tes...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/testimony-devel
> > 
> 
> 
> 
> 	
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital 
> self defense, top technical experts, no vendor pitches, unmatched 
> networking opportunities. Visit www.blackhat.com 
> _______________________________________________
> Testimony-devel mailing list
> Tes...@li...
> https://lists.sourceforge.net/lists/listinfo/testimony-devel
> 

RE: [Testimony-devel] Broken Ant script

[Petter W. <pet...@ya...>]

Hi Carlos,

The checkstyle task of the Ant script should work now.
I've also added tasks for uploading the built releases
that's supposed to run using web start.

I think I'll move the lib file to a subdirectory of
tools/CheckStyle if that's OK with you - I think we
should try to keep the number of directories (and
files) in the root to a minimum...

Regards,
Petter

--- Carlos Tasada <ct...@te...> wrote:
> Already done, I hope :) 
> 
> > -----Mensaje original-----
> > De: Petter Wintzell
> [mailto:pet...@ya...] 
> > Enviado el: jueves, 24 de junio de 2004 9:13
> > Para: Carlos Tasada
> > Asunto: RE: [Testimony-devel] Broken Ant script
> > 
> > Hi Carlos,
> > 
> > I see them now, I misconfigured my CVS client so
> new 
> > directories were not updated, sorry...
> > 
> > Anyway, let me know when you have moved the files
> around and 
> > I'll take a look at the Ant script.
> > 
> > Regards,
> > Petter
> > 
> > --- Carlos Tasada <ct...@te...> wrote:
> > > Hi Peter,
> > > 
> > > Definitively is there. First I looked with the
> WebCVS and 
> > then I did a 
> > > checkout, anyway I'll try later to commit in the
> new path, 
> > don't worry 
> > > :)
> > > 
> > > Regards,
> > > Carlos. 
> > > 
> > > > -----Mensaje original-----
> > > > De:
> tes...@li...
> > > >
> > >
> [mailto:tes...@li...]
> > > En
> > > > nombre de Petter Wintzell
> > > > Enviado el: jueves, 24 de junio de 2004 7:51
> > > > Para: Testimony devel
> > > > Asunto: RE: [Testimony-devel] Broken Ant
> script
> > > > 
> > > > Are you sure about that? I did an update just
> now,
> > > and I did
> > > > not get any new files...
> > > > 
> > > > Could it be that you made some mistake when
> adding
> > > the files,
> > > > like doing a CVS add but forgetting the
> commit?
> > > > 
> > > > If so, it may not be bad news because we can
> add
> > > CheckStyle
> > > > to a tools directory instead.
> > > > 
> > > > If not, there's something weird going on.
> Could
> > > you try to do
> > > > an update of the CVS tree to a different
> location
> > > and see if
> > > > you get the new files?
> > > > 
> > > > Regards,
> > > > Petter
> > > > 
> > > > --- Carlos Tasada <ct...@te...>
> wrote:
> > > > >  
> > > > > Hi Peter,
> > > > > 
> > > > > The CheckStyle is committed in the CVS (I
> forgot
> > > to do that
> > > > the first
> > > > > day, but is in the CVS since a couple of
> days
> > > ago). On the
> > > > other hand
> > > > > I agree with you about the new structure.
> > > > > 
> > > > > Regards,
> > > > > Carlos.
> > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > 		
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Mail - 50x more storage than other
> > > providers!
> > > > http://promotions.yahoo.com/new_mail
> > > > 
> > > > 
> > > >
> > >
> >
>
-------------------------------------------------------
> > > > This SF.Net email sponsored by Black Hat
> Briefings
> > > & Training.
> > > > Attend Black Hat Briefings & Training, Las
> Vegas
> > > July 24-29 -
> > > > digital self defense, top technical experts,
> no
> > > vendor
> > > > pitches, unmatched networking opportunities.
> Visit
> > > 
> > > > www.blackhat.com
> > > _______________________________________________
> > > > Testimony-devel mailing list
> > > > Tes...@li...
> > > >
> > >
> >
>
https://lists.sourceforge.net/lists/listinfo/testimony-devel
> > > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 	
> > 		
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - 100MB free storage!
> > http://promotions.yahoo.com/new_mail 
> > 
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings &
> Training.
> Attend Black Hat Briefings & Training, Las Vegas
> July 24-29 - 
> digital self defense, top technical experts, no
> vendor pitches, 
> unmatched networking opportunities. Visit
> www.blackhat.com
> _______________________________________________
> Testimony-devel mailing list
> Tes...@li...
>
https://lists.sourceforge.net/lists/listinfo/testimony-devel
> 



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

RE: [Testimony-devel] Broken Ant script

[Carlos T. <ct...@te...>]

Already done, I hope :) 

> -----Mensaje original-----
> De: Petter Wintzell [mailto:pet...@ya...] 
> Enviado el: jueves, 24 de junio de 2004 9:13
> Para: Carlos Tasada
> Asunto: RE: [Testimony-devel] Broken Ant script
> 
> Hi Carlos,
> 
> I see them now, I misconfigured my CVS client so new 
> directories were not updated, sorry...
> 
> Anyway, let me know when you have moved the files around and 
> I'll take a look at the Ant script.
> 
> Regards,
> Petter
> 
> --- Carlos Tasada <ct...@te...> wrote:
> > Hi Peter,
> > 
> > Definitively is there. First I looked with the WebCVS and 
> then I did a 
> > checkout, anyway I'll try later to commit in the new path, 
> don't worry 
> > :)
> > 
> > Regards,
> > Carlos. 
> > 
> > > -----Mensaje original-----
> > > De: tes...@li...
> > >
> > [mailto:tes...@li...]
> > En
> > > nombre de Petter Wintzell
> > > Enviado el: jueves, 24 de junio de 2004 7:51
> > > Para: Testimony devel
> > > Asunto: RE: [Testimony-devel] Broken Ant script
> > > 
> > > Are you sure about that? I did an update just now,
> > and I did
> > > not get any new files...
> > > 
> > > Could it be that you made some mistake when adding
> > the files,
> > > like doing a CVS add but forgetting the commit?
> > > 
> > > If so, it may not be bad news because we can add
> > CheckStyle
> > > to a tools directory instead.
> > > 
> > > If not, there's something weird going on. Could
> > you try to do
> > > an update of the CVS tree to a different location
> > and see if
> > > you get the new files?
> > > 
> > > Regards,
> > > Petter
> > > 
> > > --- Carlos Tasada <ct...@te...> wrote:
> > > >  
> > > > Hi Peter,
> > > > 
> > > > The CheckStyle is committed in the CVS (I forgot
> > to do that
> > > the first
> > > > day, but is in the CVS since a couple of days
> > ago). On the
> > > other hand
> > > > I agree with you about the new structure.
> > > > 
> > > > Regards,
> > > > Carlos.
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > 		
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail - 50x more storage than other
> > providers!
> > > http://promotions.yahoo.com/new_mail
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This SF.Net email sponsored by Black Hat Briefings
> > & Training.
> > > Attend Black Hat Briefings & Training, Las Vegas
> > July 24-29 -
> > > digital self defense, top technical experts, no
> > vendor
> > > pitches, unmatched networking opportunities. Visit
> > 
> > > www.blackhat.com
> > _______________________________________________
> > > Testimony-devel mailing list
> > > Tes...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/testimony-devel
> > > 
> > 
> > 
> > 
> 
> 
> 
> 	
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail 
> 

[Testimony-devel] Ant build script

[Petter W. <pet...@ya...>]

Hi Carlos,

I've committed some improvements in the Ant build
script. News is that it is now possible to build
distributions ready for deployment using the script.
The next step is to move the home page code into the
testimony CVS tree and add targets for uploading stuff
to the server - releases and home page content.

The build script contains instructions on how to build
and create releases and so on so I won't say more
about how it works here... It's supposed to be
self-explanatory, and if it isn't I'll improve the
documentation... :)

One thing: I have added a resource file
version.properties which contains information about
which version of Testimony that is built. This is used
to create the name of the distribution zip file. I was
thinking that it would be a good idea if the Java code
reads its version information from that properties
file also. Unless you have objections, I'll make that
change.

It's good to do some contributions to the project
again. The build script work is of a nature that it
can be done a little at a time - five minutes here and
five minutes there - so I'm able to do some work while
waiting for long compiles at work... :)

Regards,
Petter

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

RE: [Testimony-devel] Broken Ant script

[Petter W. <pet...@ya...>]

Are you sure about that? I did an update just now, and
I did not get any new files...

Could it be that you made some mistake when adding the
files, like doing a CVS add but forgetting the commit?

If so, it may not be bad news because we can add
CheckStyle to a tools directory instead.

If not, there's something weird going on. Could you
try to do an update of the CVS tree to a different
location and see if you get the new files?

Regards,
Petter

--- Carlos Tasada <ct...@te...> wrote:
>  
> Hi Peter,
> 
> The CheckStyle is committed in the CVS (I forgot to
> do that the first day,
> but is in the CVS since a couple of days ago). On
> the other hand I agree
> with you about the new structure.
> 
> Regards,
> Carlos.
> 
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

[Testimony-devel] Broken Ant script

[Petter W. <pet...@ya...>]

Hi Carlos,

> PS: By the way, the new Ant file is not working
> correctly doing the
> CheckStyle task.

I have never run the CheckStyle task, so it's quite
possible that I've broken it while restructuring the
Ant file...

I do not have CheckStyle installed on my computer.
Where can I find it, how should it be set up?

The CheckStyle Ant task uses files placed in to
directories, lib and xml. These directories have not
been committed to CVS, so I cannot see them...

Anyway, I wanted to comment on the directory
structure. I think the "xml" directory name is not so
intuitive, and for understandability reasons I think
we should be careful with introducing new directories
on the root level. What do you think about creating a
tools directory, something like this:

tools
  CheckStyle
    lib
      checkstyle-all-3.4.jar (perhaps not part of our
CVS tree)
    config
      sun_checks.xml
      checkstyle-simple.xsl
  Other future tools go here...

What do you think about this?

If you send me the CheckStyle files, including the xml
files (or perhaps they can be downloaded from
somewhere), I will fix the broken Ant script. Sorry
for messing it up...

Regards,
Petter


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

RV: [Testimony-devel] Testimony: v 1.2 status and ideas for the future versions

[Carlos T. <ct...@te...>]

Hi Peter,

> Seems like we agree on almost all points! :)

I'm happy about that :)

> > That's really a big modification (I think could go for the version 2).
> > The idea is use Testimony as something more than and offline 
> > indexing tool, but also as a Comic Organizer/DataBase. I think that 
> > that should be configurable and the user should be able to select if 
> > wants to work in "indexing mode" or "collector mode". As I say it's 
> > a big change and I want to talk about that before doing anything. 
> > But again, that should go for version 2 :)
>
> This is a massive change... I am a little bit hesistant to change the 
> main use case of the application. It could be that I'm just a coward, 
> though :) - at least I think we agree that this would need 
> considerable discussion.

OK, will turn to that when the time comes :)

> Also, I think that if the OI should come up during this time, we 
> should wait with the features on the list and do the submittal of 
> indexes.

Seems that will come up at June 26th (we'll see). Once the OI is correctly
working, I think will be the time to aproach to Jon again about the SQL
access, but I also think that the Testimony project should be a bit more
alive before asking Jon to commit to that :)

> > About the 1.2.5 version: I think that's not really a version, but 
> > only some intermediate point to finish, fixing and enhancing some 
> > allready existing features. That remembers me that we've not touch 
> > the possibility to do new versions more often. I think that, for 
> > example we could go with something like 1.2.1 (finish the progress 
> > bar work);
> > 1.2.2 (finish the error system); ..... and so on. That will be the 
> > same for other versions, were we could go incrementing versions as 
> > we finish new features or fixings. In that way we remove the beta
status.
>
> I agree that we could do more and smaller releases.
> This will also make it easier to get out bug fixes quickly. Once the 
> build file is ready, it will be easier to do the release I hope. I' 
> hoping that I'll be able to do some work on it this week.

Perfect. I'll try to finish with all the small fixings that I'm doing now
AFAP

Regards,
Carlos.

PS: By the way, the new Ant file is not working correctly doing the
CheckStyle task.

Re: RV: [Testimony-devel] Testimony: v 1.2 status and ideas for the future versions

[Petter W. <pet...@ya...>]

Hi Carlos,

Seems like we agree on almost all points! :)

Some comments:

> The local search is also low priority and very
> related with other points
> (see later). On the other hand I think that the
> search is the GCD site is
> important. If the user can search from inside the
> tool for the serie or
> issue that he wants to import, I think will be more
> confortable and
> intuitive than not looking for some kind of code in
> the url.

I agree with you. Good point, you have convinced me...

> That's really a big modification (I think could go
> for the version 2). The
> idea is use Testimony as something more than and
> offline indexing tool, but
> also as a Comic Organizer/DataBase. I think that
> that should be configurable
> and the user should be able to select if wants to
> work in "indexing mode" or
> "collector mode". As I say it's a big change and I
> want to talk about that
> before doing anything. But again, that should go for
> version 2 :)

This is a massive change... I am a little bit
hesistant to change the main use case of the
application. It could be that I'm just a coward,
though :) - at least I think we agree that this would
need considerable discussion.

> > > - Undo option ???
> >
> > Very good idea. There are standard solutions for
> implementing undo I 
> > think.
> > This one is a really nice feature that, in my
> opinion, should be in 
> > every serious application... Not crucial, but
> nice.
> 
> I'm not sure that's not crucial. If you're indexing
> a serie and by mistake
> you delete that.... I known that we're asking for
> confirmation, but anyway I
> think that we should increment the security in that
> part. Not only and undo
> feature, but maybe somekind of autosave every x
> minutos in a temp file or
> something like that would be good. But I really have
> no idea how to do the
> undo think. I'll try to find documentation about
> that.

Again, good point. You have convinced me again.

> So, after all that discussion, here is a more
> explicit version prevision. I
> think that should be something like that:
<snip>
> What do you think? I'll go on developing by myself,
> but if you, or Mark,
> have enough free time at some time to do some of the
> new features, tell me
> and I'll be more than happy :)

I think it's a nice list of features, and a good plan.
I think the priorities are right.

Also, I think that if the OI should come up during
this time, we should wait with the features on the
list and do the submittal of indexes.

> About the 1.2.5 version: I think that's not really a
> version, but only some
> intermediate point to finish, fixing and enhancing
> some allready existing
> features. That remembers me that we've not touch the
> possibility to do new
> versions more often. I think that, for example we
> could go with something
> like 1.2.1 (finish the progress bar work); 1.2.2
> (finish the error system);
> ..... and so on. That will be the same for other
> versions, were we could go
> incrementing versions as we finish new features or
> fixings. In that way we
> remove the beta status.

I agree that we could do more and smaller releases.
This will also make it easier to get out bug fixes
quickly. Once the build file is ready, it will be
easier to do the release I hope. I' hoping that I'll
be able to do some work on it this week.

Regards,
Petter



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

RV: [Testimony-devel] Testimony: v 1.2 status and ideas for the future versions

[Carlos T. <ct...@te...>]

Hi Peter,

Here are my comments:

> > #PENDING BUGS#
> > - (Major)The ? simbol is not correctly recognised in the ISO-8859-1
> >   - GCD standard is ISO-88958-1 (ASCII). That coding doesn't 
> > supports the ?
> > simbol
> >   - ISO-8859-15 or UTF-8 should be used
>
> The actual symbol that was not part of the encoding was filtered away 
> somewhere before the mail reached me. What was it? Euro symbol?

Yes, it's the Euro symbol. I already asked in the Tech list some weeks ago,
and they said the same. That the format should be UTF-8 or ISO-8859-15. They
also pointed another option, that's convert directly the unknown symbol in
the euro.

> I think the application should be used in the following way: When 
> editing indices and saving them to the local hard drive, XML format 
> should be used.
> That format should handle all Unicode characters (I believe it does). 
> The more restrictive submission format should olnly be used when 
> exporting indices for submitting.

That's a good idea, I'll take a look at the code to see if that's what we're
doing now, if not I'll change that to use XML by default.

> > Version 1.3 - 1.5
>
> Here are some opinions on your idea for future improvements. I haven't 
> indexed in a long time, so I'm a little out of the loop, but here goes 
> anyway :)
>
> First of all, I still think that the most crucial functionality is to 
> be able to automatically submit indexed comics. That is of course hard 
> to code without some support from the GCDB coders (Jon and others), or 
> at least the OI up and running. But having said that, I think it's 
> important to remember that that is the "killer functionality" that 
> would make the Testimony application actually be used by more people.

I completelly agree with you, but until the OI is finished I don't think
that Jon will have enough time to give us support.

> > - Support to import/export/store covers
>
> This is a cool idea I think. Any ideas on how to solve it, 
> design-wise, in the application?

I've a couple ideas, we can discuss them when we arrive to that point.
Basically I've think to show the cover in the Issue Dialog and configure
what cover size do you want to download (if you want to do it). Another
feature would be some kind of cover gallery, but I think that will be
another feature.

> > - ProgressBar:
> >   + Show ProgressBar in all time consuming events (sort & import) ???
> >   + ProgressBar must show the correct progression when available
>
> Good idea.

First in the list :)

> > - XML:
> >   + Rewrite XML export code. Needs a better control in the code 
> > conversion
> > (?)
> >   + Detect if the information is valid when importing from an XML
> > - Detect when a series/issue is already imported
> >   + Show that issue different in the IssueSelectDialog
> >   + Show a warning before overwrite it (delete and import the new 
> > one or just overwrite ???)
>
> > - Error System:
> >   + More information. Add field support (redirect to the field and 
> > show some kind of warning in the field)
> >   + Redirect System.err to the errors table
> >     * Config a debug option. Show some information only if debug 
> > enabled.
> >     * Needs to implement a new tab for text information
> >     * Remove all the System.err and use the Error system
> >   + Add contextual menu to the errors panel
>
> I like the idea with an error system very much.
>
> Why bother with the system.err at all? I think a good approach would 
> be to remove all references to system.err and use the error system 
> throughout instead, if that is possible. But, like I said, I'm out of 
> the loop and might have forgotten something about how it works...
>
> The error system has great potential, I think. One thing that I missed 
> when I test-ran the application was the possibility to click on an 
> error and go to the location where the error is. This can be tricky of 
> course because there are a lot of different "locations" to go to - 
> fields etc. in the application but also text files and HTML pages 
> being imported...
>
> Also, I noted that errors that are the result of a failed import never 
> goes away. There should perhaps be a way of clearing the error list, 
> or better yet, some smart way of it being cleared automatically?

That's also in the high priority list. My planning is to recode all the
control errors part with a Logger and from that point  increment the
control. Now is possible to go directly to the sequence where the error is
detected, but I'm not happy with the way it's implemented.

> > - Menu:
> >   + Add changelog file and menu options to report errors, ask 
> > features,
>
> This one I like! A first implementation (that might very well prove 
> sufficient even in the long run) would be to use the BrowserLauncher 
> (or whatever it's
> called) to go to the Testimony bug report page.
>
> Later, we could perhaps add functionality for automatically attaching 
> logs, screen shots, etc. that would make our work easier. At the 
> moment, we do not generate such information, but we could make an 
> effort there.
>
> I think this feature is not so important yet, but will prove valuable 
> when people start to use the application.

Again I agree with you. I think that a first implementation would be to add
some menuitems that opens the internet browser to the correct page (as you
point). Maybe later I'll add a local changelog (Testimony should stay
offline as much as possible)

> > ......
> >   + Add validate option
> >     * Menu item
> >     * Config if validate info automatically before saving to file
> >     * Input info validation should be done in the Series, Issue and 
> > Sequence classes (Interface ?).
>
> This is a feature I think is quite important for Testimony, here we 
> could have an advantage over the traditional OI.

That's also a very important feature, but I think it should wait until the
error system is completelly done. We should also think what's the better way
to do it, and we're should be the validation code. Also it's very important
to define what kind of thinks will be validated and if they should be
configurable or not.

>
> >   + Add Print option
> >     * Options: full collection, current series, current issue, 
> > current sequence
> >     * Config internally as HTML.
> >     * Possibility to support style sheets to config the way the info 
> > is show
>
> This is not so important in my opinion. Maybe for printing out data 
> for review before submitting... But I think these feature can wait a bit.

That's low priority and very related with other points (see later)

> >   + Add search menu option
> >     * Search in the local database
> >     * Search in internet
>
> Cool idea, but necessary? The Internet DB is already searchable 
> through the GCD home page... I think we should maintain the interfaces 
> to the DB at a minimum so that we have as little to maintain as 
> possible if the online DB interface changes unexpectedly. At least 
> until we can get a stable, well specified interface to the online DB, 
> I think this could wait.
>
> Searching the local DB is interesting, not so useful at least not for 
> the way I would use it. I would not keep a lot of data in the local 
> DB, just the comic I'm currently indexing. After submitting it, I 
> would not use the local DB for a searchable database. Maybe you see a 
> different use case?

The local search is also low priority and very related with other points
(see later). On the other hand I think that the search is the GCD site is
important. If the user can search from inside the tool for the serie or
issue that he wants to import, I think will be more confortable and
intuitive than not looking for some kind of code in the url.

> > - GUI enhancements:
> >   + Autocomplete comboboxes:
> >     * Should be possible to indicate case sensitive or not case 
> > sensitive
>
> Here's an idea: Auto-completion could recognize text case-unsensitive, 
> but complete it case-sensitive, if you understand what I mean... If I 
> enter "stan", the auto completion could suggest "Stan Lee", and if I 
> select that option "Stan Lee" should be entered, not "stan Lee".
>
> Even though I write large parts of the auto-completion, I don't 
> remember how it works today.

That's exactly what I meant. I would like to do that for the next release.

> >   + Generate keydate from the date info (and viceversa). If doesn't 
> > match show error.
>
> The "If doesn't match show error" part seems like an idea for the 
> validation I think...

I agree that the error part should be in the validation system. The idea is
that should be enought writing only one info (cover date or key date) and
the system will create the other.

> >   + Add theme support for the Metal Look & Feel
> >     * See support in Java 1.5
> >     * See how to add possibility to be configured by the user (store 
> > in registry or config file ???)
> >
> > Other ideas
> > - Increment the functionality to support user collection
> >   + Comic state, location, number of copies, valoration, user notes, 
> > ...
>
> Here you are definitely thinking of a different use case. I've mostly 
> been thinking that Testimony would be used for indexing, period. Not 
> keeping a local database.
>
> If we want to use Testimony for keeping a local database, I think we 
> would have to improve the way data is stored to disk. Perhaps it would 
> make more sense to use a proper SQL-enable DB engine instead of the 
> current flora of storage formats...

That's really a big modification (I think could go for the version 2). The
idea is use Testimony as something more than and offline indexing tool, but
also as a Comic Organizer/DataBase. I think that that should be configurable
and the user should be able to select if wants to work in "indexing mode" or
"collector mode". As I say it's a big change and I want to talk about that
before doing anything. But again, that should go for version 2 :)

> > - Multilanguage sequence type ???
> > - Support Distribution format ???
>
> Not sure I understand these two...

With Multilanguage sequence type I'm talking about the possibility to show
the sequence genre in the local language. The distribution format is
something that is talked about in the GCD documentation, but I cannot really
remember where.

> > - A help system where it would be possible to get quotes from the 
> > format file about
> >   what should go into the various database fields
>
> I like this one a lot. Has been up for discussion before if I remember 
> correctly. Could be connected to the error and the validation systems, 
> so that the user can get instant feedback on his mistakes from the 
> official documents.
>
> > - Multilanguage tooltips for fields
> > - Include help as an HTML frame browser
> >   + Will need translation
>
> Good point with the translation. Makes it more complex...

Really complex, that's because I'm delaying it :)

> > - Undo option ???
>
> Very good idea. There are standard solutions for implementing undo I 
> think.
> This one is a really nice feature that, in my opinion, should be in 
> every serious application... Not crucial, but nice.

I'm not sure that's not crucial. If you're indexing a serie and by mistake
you delete that.... I known that we're asking for confirmation, but anyway I
think that we should increment the security in that part. Not only and undo
feature, but maybe somekind of autosave every x minutos in a temp file or
something like that would be good. But I really have no idea how to do the
undo think. I'll try to find documentation about that.

So, after all that discussion, here is a more explicit version prevision. I
think that should be something like that:

Version 1.2 (TODO) [Middle July]
- Finish code reorganization
- Put home page in the new module
- Better icons for the series, issue and sequences nodes
- Code CheckStyle
- Finish buil.xml
- (Test)Bug with Sort/Collapse options

Version 1.2.5 [October]
- ProgressBar (needs code reestructuration):
  + Show ProgressBar in all time consuming events (sort & import) ???
  + ProgressBar must show the correct progression when available
- Rewrite the import code (site and XML) to support:
  + Detect when a series/issue is already imported
    - Show that issue different in the IssueSelectDialog
    - Show a warning before overwrite it (delete and import the new one or
just overwrite ???)
- Error System:
  + More information. Add field support (redirect to the field and show some
kind of warning in the field)
  + Redirect System.err to the errors table
    - Config a debug option. Show some information only if debug enabled.
    - Needs to implement a new tab for text information
    - Remove all the System.err and use the Error system
  + Add contextual menu to the errors panel
- Preferences Dialog:
  + Possibility to reset to default values
- GCDSiteIssueFormatReader: Modify code to use patterns
- GUI enhancements:
  + Autocomplete comboboxes:
    - Should be possible to indicate case sensitive or not case sensitive
  + Generate keydate from the date info (and viceversa). If doesn't match
show error.

Version 1.3 [January]
- Menu:
  + Undo option
  + Add validate option
    - Menu item
    - Config if validate info automatically before saving to file
    - Input info validation should be done in the Series, Issue and Sequence
classes (Interface ?).
    - Detect if the information is valid when importing from an XML, TXT or
GCD
  + Add changelog file and menu options to report errors, ask features,
......
- Support to import/export/store covers
  + Config is you want to import the cover
  + Config the importing cover size by default
(Small(x1)/Medium(4x)/High(16x) Resolution)
  + Cover can be show in the Issue information
  + Support for multiple/variant covers (GCD would do it in the future)
  + Internal cover gallery
- Sequence genre in local language

Version 1.4 [Easter 2005]
- Menu:
  + Add search menu option
    - Search in the local database
    - Search in internet
  + Add Print option
    - Options: full collection, current series, current issue, current
sequence
    - Config internally as HTML.
    - Possibility to support style sheets to config the way the info is show
  + Add HTML Export option (use the same code to print)
- GUI enhancements:
  + Add theme support for the Metal Look & Feel
    - See support in Java 1.5
    - See how to add possibility to be configured by the user (store in
registry or config file ???)
  + New Themes with Java 1.5
    - Ocean
    - XAWT (Only X11)
- Help system (firstly only in english but thinking it'll by multilanguage):
  + A help system where it would be possible to get quotes from the format
file about what should go into the various database fields
  + Multilanguage tooltips for fields
  + Include help as an HTML frame browser

Version 2.0 [Summer 2005?]
- Increment the functionality to support user collection
  + Comic state, location, number of copies, valoration, user notes, ...

What do you think? I'll go on developing by myself, but if you, or Mark,
have enough free time at some time to do some of the new features, tell me
and I'll be more than happy :)

About the 1.2.5 version: I think that's not really a version, but only some
intermediate point to finish, fixing and enhancing some allready existing
features. That remembers me that we've not touch the possibility to do new
versions more often. I think that, for example we could go with something
like 1.2.1 (finish the progress bar work); 1.2.2 (finish the error system);
.... and so on. That will be the same for other versions, were we could go
incrementing versions as we finish new features or fixings. In that way we
remove the beta status.

Regards,
Carlos.

Re: [Testimony-devel] Testimony: v 1.2 status and ideas for the future versions

[Petter W. <pet...@ya...>]

Hi Carlos,

Great work with the application! I see there's quite a
long list of future ideas, here are some opinions on
some of them:

> #PENDING BUGS#
> - (Major)The ? simbol is not correctly recognised in
> the ISO-8859-1
>   - GCD standard is ISO-88958-1 (ASCII). That coding
> doesn't supports the ?
> simbol
>   - ISO-8859-15 or UTF-8 should be used

The actual symbol that was not part of the encoding
was filtered away somewhere before the mail reached
me. What was it? Euro symbol?

Anyway, personally I think it's a shame that the
submission format uses the ISO-8859-1 encoding. It
should be UTF-8 or UCS-2, that way comics from all
over the world could be indexed. But that's not really
our decision to make, the submission format uses
ISO-8859-1, and that's it.

If I'm not completely remembering wrong, it's only
when you try to save your indexed comics in the
submission format that Testimony forces you to use
ISO-8859-1 characters. If you save in XML or something
else, Testimony let's you use whatever characters you
want, and also include newline and tab characters in
the texts.

I think that is a reasonable approach, and that we
should not change anything. However, we could very
well argue in the Tech forum for a change, that the
submission format should use UCS-2 or UTF-8. I know
that we've both done that on different occasions, but
nothing has happened of course.

I think the application should be used in the
following way: When editing indices and saving them to
the local hard drive, XML format should be used. That
format should handle all Unicode characters (I believe
it does). The more restrictive submission format
should olnly be used when exporting indices for
submitting.

I think this is good because the different formats
puts different restrictions on the data.

> Version 1.3 - 1.5

Here are some opinions on your idea for future
improvements. I haven't indexed in a long time, so I'm
a little out of the loop, but here goes anyway :)

First of all, I still think that the most crucial
functionality is to be able to automatically submit
indexed comics. That is of course hard to code without
some support from the GCDB coders (Jon and others), or
at least the OI up and running. But having said that,
I think it's important to remember that that is the
"killer functionality" that would make the Testimony
application actually be used by more people.

> - Support to import/export/store covers

This is a cool idea I think. Any ideas on how to solve
it, design-wise, in the application?

> - ProgressBar:
>   + Show ProgressBar in all time consuming events
> (sort & import) ???
>   + ProgressBar must show the correct progression
> when available

Good idea.

> - XML:
>   + Rewrite XML export code. Needs a better control
> in the code conversion
> (?)
>   + Detect if the information is valid when
> importing from an XML
> - Detect when a series/issue is already imported
>   + Show that issue different in the
> IssueSelectDialog
>   + Show a warning before overwrite it (delete and
> import the new one or
> just overwrite ???)

> - Error System:
>   + More information. Add field support (redirect to
> the field and show some
> kind of warning in the field)
>   + Redirect System.err to the errors table
>     * Config a debug option. Show some information
> only if debug enabled.
>     * Needs to implement a new tab for text
> information
>     * Remove all the System.err and use the Error
> system
>   + Add contextual menu to the errors panel

I like the idea with an error system very much.

Why bother with the system.err at all? I think a good
approach would be to remove all references to
system.err and use the error system throughout
instead, if that is possible. But, like I said, I'm
out of the loop and might have forgotten something
about how it works...

The error system has great potential, I think. One
thing that I missed when I test-ran the application
was the possibility to click on an error and go to the
location where the error is. This can be tricky of
course because there are a lot of different
"locations" to go to - fields etc. in the application
but also text files and HTML pages being imported...

Also, I noted that errors that are the result of a
failed import never goes away. There should perhaps be
a way of clearing the error list, or better yet, some
smart way of it being cleared automatically?

> - Menu:
>   + Add changelog file and menu options to report
> errors, ask features,

This one I like! A first implementation (that might
very well prove sufficient even in the long run) would
be to use the BrowserLauncher (or whatever it's
called) to go to the Testimony bug report page.

Later, we could perhaps add functionality for
automatically attaching logs, screen shots, etc. that
would make our work easier. At the moment, we do not
generate such information, but we could make an effort
there.

I think this feature is not so important yet, but will
prove valuable when people start to use the
application.

> ......
>   + Add validate option
>     * Menu item
>     * Config if validate info automatically before
> saving to file
>     * Input info validation should be done in the
> Series, Issue and Sequence
> classes (Interface ?).

This is a feature I think is quite important for
Testimony, here we could have an advantage over the
traditional OI.

No one knows really what the OI will look like if it
comes online again, but if we compare with the old OI
there was (in my opinion) very large problems with
data validation. There was none built in, and instead
there was the system with reviews by editors. Editors
had not read the formatting rules careful enough, and
being only human, missed mistakes in the indices,
causing a lot of unnecessary errors to be entered into
the DB...

We should instead have a system where the editing
tools enforces the formatting rules that we have. The
OI has no such support built in, and i doubt that Jon
and the others will ever find time to write it. But
Testimony could have it, and it could be added quite
easily.

The editing tool could enforce the formatting rules,
pointing out the most common mistakes, and the editors
could concentrate on reviewing the actual data being
put into the system...

>   + Add Print option
>     * Options: full collection, current series,
> current issue, current
> sequence
>     * Config internally as HTML.
>     * Possibility to support style sheets to config
> the way the info is show

This is not so important in my opinion. Maybe for
printing out data for review before submitting... But
I think these feature can wait a bit.

>   + Add search menu option
>     * Search in the local database
>     * Search in internet

Cool idea, but necessary? The Internet DB is already
searchable through the GCD home page... I think we
should maintain the interfaces to the DB at a minimum
so that we have as little to maintain as possible if
the online DB interface changes unexpectedly. At least
until we can get a stable, well specified interface to
the online DB, I think this could wait.

Searching the local DB is interesting, not so useful
at least not for the way I would use it. I would not
keep a lot of data in the local DB, just the comic I'm
currently indexing. After submitting it, I would not
use the local DB for a searchable database. Maybe you
see a different use case?

> - GUI enhancements:
>   + Autocomplete comboboxes:
>     * Should be possible to indicate case sensitive
> or not case sensitive

Here's an idea: Auto-completion could recognize text
case-unsensitive, but complete it case-sensitive, if
you understand what I mean... If I enter "stan", the
auto completion could suggest "Stan Lee", and if I
select that option "Stan Lee" should be entered, not
"stan Lee".

Even though I write large parts of the
auto-completion, I don't remember how it works today.

>   + Generate keydate from the date info (and
> viceversa). If doesn't match
> show error.

The "If doesn't match show error" part seems like an
idea for the validation I think...

>   + Add theme support for the Metal Look & Feel
>     * See support in Java 1.5
>     * See how to add possibility to be configured by
> the user (store in
> registry or config file ???)
> 
> Other ideas
> - Increment the functionality to support user
> collection
>   + Comic state, location, number of copies,
> valoration, user notes, ...

Here you are definitely thinking of a different use
case. I've mostly been thinking that Testimony would
be used for indexing, period. Not keeping a local
database.

If we want to use Testimony for keeping a local
database, I think we would have to improve the way
data is stored to disk. Perhaps it would make more
sense to use a proper SQL-enable DB engine instead of
the current flora of storage formats...

> - Multilanguage sequence type ???
> - Support Distribution format ???

Not sure I understand these two...

> - A help system where it would be possible to get
> quotes from the format
> file about
>   what should go into the various database fields

I like this one a lot. Has been up for discussion
before if I remember correctly. Could be connected to
the error and the validation systems, so that the user
can get instant feedback on his mistakes from the
official documents.

> - Multilanguage tooltips for fields
> - Include help as an HTML frame browser
>   + Will need translation

Good point with the translation. Makes it more
complex...

> - Undo option ???

Very good idea. There are standard solutions for
implementing undo I think. This one is a really nice
feature that, in my opinion, should be in every
serious application... Not crucial, but nice.

Regards,
Petter


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Testimony-devel] Re: CheckStyle and build.xml

[Petter W. <pet...@ya...>]

Hi Carlos,

--- Carlos Tasada <ct...@te...> wrote:
> Hi Peter,
> 
> I've just done a big commit (near 1,000 CheckStyle
> fixings). I've added a
> new target to the build.xml to do the checking, so
> you should be able to use
> it without problems.

Maybe you could add a comment to the build file about
where to obtain the program and where it should be
installed? I guess a libdir has to be created and a
jar file downloaded and put there. Since I'm not doing
any coding at the moment, I guess I won't use this
target. But I agree that's it's a very good idea,
especially if the checking tool is good. What kind of
errors are detected by checkstyle?

> On the other hand I have a couple of questions about
> the ant file:
> - Why have you changed some action names? I mean
> compile -> -compile, ....
> - The -compile action is working? I cannot execute
> it, but the build action
> works fine ????

The reason for that was to distinguish intermediate,
internal tasks from tasks that are intended to be run
from the command line. I read in the Ant manual that
prefixing tasks with a - is one way of making such a
distinction, and I was hoping that an intelligent IDE
would present such tasks in a different way. The goal
was to make it easier for the developer.

However, such tasks can not be run from the command
line because Ant interprets it as an option instead of
a task. Maybe it was stupid to change the name,
sometimes one wants to run the compile task... I think
maybe a good idea would be to change the name back and
write better documentation instead.

> 
> I'll continue with the fixings.
> 
> One last thing. Is the code reestructuration
> finished?

Yes, most of it. The part that is left is to break up
the huge classes into smaller parts. The IDE I'm using
can do it quite easily, so I was planning on doing it.
But if you're in a hurry, feel free to do it yourself,
because I don't know when I can get around to it.

Also, I wanted to improve the build file and add
targets for building, signing and uploading the
distribution, uploading the HTML content, etc. That is
not done yet either.

But the basic moving around of files is done.

Regards,
Petter



		
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo 

RE: [Testimony-devel] Resources and other things

[Petter W. <pet...@ya...>]

Hi Carlos,

The resource files ahs now been added, and I have
updated the build file.

I also had to modify some of the UI classes, it seems
that the titles of some borders where modified before
the borders where created...

Please try it out! I think it should work now.

Regards,
Petter



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

Re: [Testimony-devel] Resources and other things

[Petter W. <pet...@ya...>]

Hi Carlos,

Lots of interesting points there, being at work I can
not adress all of them in detail, I'll get back to you
later. However, the resource file issue seems quite
important...

I think it would be safe for the application to assume
that the English resource file can be found. If it can
not, there is some problem with the installation of
the application, files are missing, and I think we
should not try to deal with that kind of problem. We
don't try to deal with missing class files, right?

Like you say, dealing with missing English resource
file is quite expensive, and would mean that we
duplicate the work with the English texts.

So, what we should do is to make sure that when the
application is built, the resource files are placed in
the correct locations. Also, when the jar file is
built, the resource files should be included in the
right place. Same thing goes for the icons.

This should be handled by the Ant script. Basically,
when compiling, all java files are compiled into class
files and all resource files are copied. Perhaps
something else is done as well.

Now, if we keep the resource files outside of the
source directory, like I still think is the best
option, we have locked ourselves to the Ant script. If
the developer wants to have a working application, he
or she has to build the application through the Ant
script, to make sure everything works.

As long as the user uses the Ant script, we can keep
the resource files in any location we want to. It does
not really matter if they are in the scr dir or in
another dir. However, keeping them separate would make
the Ant script (a little bit) easier to write, and as
more resources are added (icons and stuff) it will be,
in my opinion, a cleaner structure where pictures and
language files and java source code are not mixed.

Could you try the following: When building, use the
Ant script but copy the resource files by hand to the
right location in the build directory. The jar file is
not completely done yet, so skip that one for now.
Does that work OK for you? If it does, I think we
should keep the resource files separate and extend the
Ant script so that they are copied to their right
location... I can do that quite easily, it just takes
a few minutes, I can do it next week if we have
decided where the resource files go...

This mail was written very quickly, so if it's not
understandable, that is why... Have to get back to
work now... :(

Regards,
Petter

--- Carlos Tasada <ct...@te...> wrote:
> Hi Peter,
> 
> I'm testing the new code and I've found some
> important problems with the
> resource files.
> 
> 1.- Where should be the properties files? In the old
> structure they were in
> the resource directory, but now? I think they should
> stay with the
> resources, but if we put the resources out of the
> src/ folder, will be
> possible to access to them at all? (That's more or
> less what you talk about
> in your mail, we saw the same thing)
> 
> 2.- The same question goes for the icons.
> 
> 3.- Testing the code as it's now, I've found a lot
> of errors in the location
> code. In some classes we didn't control correctly
> the situation of a null
> resourceBundle, in others we ignored it. As a result
> of that the code didn't
> work at all. I've fixed a lot of that problems
> (maybe I've missed some), but
> as come to me that in the way that it's solved
> (hardcoding default strings),
> we're duplicating the work of maintaing the texts in
> english. I think that
> the testimony.properties file should be inside the
> src/ with the rest of the
> code, and only the localized properties files should
> go to the resource
> folder.
> 
> What do you think? Makes sense to consider that the
> resourceBundle is not
> found?
> 
> Talking about other things, I'm planing to complete
> the error system,
> showing all the errors in internal panels
> (Exceptions, parsing problems,
> ...) To do that I'm looking into the
> java.util.logging package. I'm still
> planning it, because I've found some problems that
> I'm not sure how to
> solve. Anyway it will go for that intermediate
> version that I told you
> yesterday (1.2.5). When I've a full vision of how to
> implement it we'll
> discuss that, but if you known some better way to do
> that or you have some
> information about that package I'd be great :)
> 
> I'm also looking to modify the way we're using the
> progressBar, and I'm
> thinking to remove that and implement a
> ProgressMonitor. I think that we
> simplify code in that way and, at the same time, we
> obtain more control.
> 
> I'm also looking for the best IDE to develop
> Testimony. I known that we had
> a discussion about that near a year ago, but I would
> like to talk about that
> again. JBuilder seems like a good option (even in
> the free version), but I
> think that Eclipse is even better. I enumerate here
> some pros and contras
> 
> 				Eclipse		JBuilder
> Free				YES			Some features
> Multiplataform		YES			YES
> Ant import			YES			YES
> Ant export			YES/?			Only in Enterprise
> Visual Development	As a plugin		YES
> Optimize Suit		As a plugin		Only in Enterprise
> UML				As a plugin		Only in Enterprise
> CVS support			YES			YES
> CheckStyle			As a plugin		NO
> Code checking		YES			NO/?
> 
> Some notes about that comparation.
> - It's only a fast comparation about the points that
> really interest us.
> - Do we really need a visual development feature?
> We've some code directly
> related with JBuilder, but other things cannot be
> done with JBuilder (or at
> least I've no idea how to do them)
> - The CheckStyle: It's a very interesting feature.
> In that way we can
> maintain a perfectly good looking code and avoid
> some sintaxis problems.
> - Optimize suit: Just before releasing the 1.2.5
> version, I want to do a
> complete code optimization (now we're just
> reestructuring) and a feature
> like that is really interesting.
> - Code checking: It's only a way to describe how
> configurable is the code
> checking when compiling. Eclipse can configure
> absolutely everythink you
> want (unused variables, hardcoded strings, ....). I
> haven't found anything
> like that in JBuilder.
> 
> I'm not saying that we MUST use Eclipse, but I think
> is a good IDE. Once all
> the code reestructuration is done, I'll try to write
> some documentation
> related with the way to use that tools with
> Testimony
> 
> About the copyright, I'll revise the code. There is
> no problem using it,
> because is under GPL or similar licenses, but you're
> right about the
> inclusion of our copyright headers. As I've said,
> I'll revise the code and
> fix the license thing.
> 
> Finally I want to tell you that I'm very impressed
> with the possibilities of
> the build.xml file. I've just tested it with the
> JBuilder (I'll do that
> later with Eclipse) and its great :). I'm ansious to
> see how will work
> everything once you finish :D
> 
> Cheers,
> Carlos.
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by the new
> InstallShield X.
> From Windows to Linux, servers to mobile,
> InstallShield X is the
> one installation-authoring solution that does it
> all. Learn more and
> evaluate today!
> http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Testimony-devel mailing list
> Tes...@li...
>
https://lists.sourceforge.net/lists/listinfo/testimony-devel



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

[Testimony-devel] Resources and other things

[Carlos T. <ct...@te...>]

Hi Peter,

I'm testing the new code and I've found some important problems with the
resource files.

1.- Where should be the properties files? In the old structure they were in
the resource directory, but now? I think they should stay with the
resources, but if we put the resources out of the src/ folder, will be
possible to access to them at all? (That's more or less what you talk about
in your mail, we saw the same thing)

2.- The same question goes for the icons.

3.- Testing the code as it's now, I've found a lot of errors in the location
code. In some classes we didn't control correctly the situation of a null
resourceBundle, in others we ignored it. As a result of that the code didn't
work at all. I've fixed a lot of that problems (maybe I've missed some), but
as come to me that in the way that it's solved (hardcoding default strings),
we're duplicating the work of maintaing the texts in english. I think that
the testimony.properties file should be inside the src/ with the rest of the
code, and only the localized properties files should go to the resource
folder.

What do you think? Makes sense to consider that the resourceBundle is not
found?

Talking about other things, I'm planing to complete the error system,
showing all the errors in internal panels (Exceptions, parsing problems,
...) To do that I'm looking into the java.util.logging package. I'm still
planning it, because I've found some problems that I'm not sure how to
solve. Anyway it will go for that intermediate version that I told you
yesterday (1.2.5). When I've a full vision of how to implement it we'll
discuss that, but if you known some better way to do that or you have some
information about that package I'd be great :)

I'm also looking to modify the way we're using the progressBar, and I'm
thinking to remove that and implement a ProgressMonitor. I think that we
simplify code in that way and, at the same time, we obtain more control.

I'm also looking for the best IDE to develop Testimony. I known that we had
a discussion about that near a year ago, but I would like to talk about that
again. JBuilder seems like a good option (even in the free version), but I
think that Eclipse is even better. I enumerate here some pros and contras

				Eclipse		JBuilder
Free				YES			Some features
Multiplataform		YES			YES
Ant import			YES			YES
Ant export			YES/?			Only in Enterprise
Visual Development	As a plugin		YES
Optimize Suit		As a plugin		Only in Enterprise
UML				As a plugin		Only in Enterprise
CVS support			YES			YES
CheckStyle			As a plugin		NO
Code checking		YES			NO/?

Some notes about that comparation.
- It's only a fast comparation about the points that really interest us.
- Do we really need a visual development feature? We've some code directly
related with JBuilder, but other things cannot be done with JBuilder (or at
least I've no idea how to do them)
- The CheckStyle: It's a very interesting feature. In that way we can
maintain a perfectly good looking code and avoid some sintaxis problems.
- Optimize suit: Just before releasing the 1.2.5 version, I want to do a
complete code optimization (now we're just reestructuring) and a feature
like that is really interesting.
- Code checking: It's only a way to describe how configurable is the code
checking when compiling. Eclipse can configure absolutely everythink you
want (unused variables, hardcoded strings, ....). I haven't found anything
like that in JBuilder.

I'm not saying that we MUST use Eclipse, but I think is a good IDE. Once all
the code reestructuration is done, I'll try to write some documentation
related with the way to use that tools with Testimony

About the copyright, I'll revise the code. There is no problem using it,
because is under GPL or similar licenses, but you're right about the
inclusion of our copyright headers. As I've said, I'll revise the code and
fix the license thing.

Finally I want to tell you that I'm very impressed with the possibilities of
the build.xml file. I've just tested it with the JBuilder (I'll do that
later with Eclipse) and its great :). I'm ansious to see how will work
everything once you finish :D

Cheers,
Carlos.

RE: [Testimony-devel] Restructure complete (almost)

[Petter W. <pet...@ya...>]

Hi Carlos,

I take it from your mail that you are happy with the
result of the restructuring! What do you think we
should do with the old source code, should we keep it
in CVS or should we remove it? Removing it would be
for making things easier to understand, but we would
lose some of our history.

Good about the agreement on the resources! I will put
them in today and update the build file accordingly...
I think I'll be able to do that today. By the way,
where should the resources be placed when running the
application from the classes dir and where should they
be placed in the jar file?

I like to work with the restructuring and I enjoy
writing Ant scripts, so this is great fun for me, but
I really have a hard time finding the time for it. I
completely agree to your idea of moving classes out of
the big class files, and if you want to I can try to
do it sometime next week. If that is OK with you, I
can do it.

Also, I have been writing on a reply to your list of
features. I feel a little bit out of the loop since I
have not been indexing or worked with Testimony for
quite some time, so don't expect too much... I will
try to get the mail ready next week. In my opinion,
the most important thing is the availability to submit
index, but I guess that can not be worked upon until
the OI is back up, if it ever is. There also was some
issues regarding encoding of data (UCS2/UTF-8 vs.
ISO-8859-1) that I may have some input on that could
be quite important.

One more thing that I remembered just now: We have
some classes that we have imported from other sources,
like the UCS2-reader and the browser window opener. I
guess this is OK, if they are released under a kind of
license that makes it OK for us to include them in our
distribution. But what we absolutely can not do is
claim copyright to these files. I'm thinking about for
instance the SwingWorker. Carlos, you have been
originally including these files I think, do you have
control that the copyright statements, etc. are okay?
This is important because:
1. We could get into a lot of trouble if we steal
other people's work and claim copyright, and it might
endanger the entire project - other people can claim
that Testimony must not be freely distributable. This
is mostly a theoretical possibility but still
important.
2. We should not claim that we have created other
people's work, credit where credit is due so to speak.

Do you have any thoughts on this?

Regards,
Petter

--- Carlos Tasada <ct...@te...> wrote:
> Hi Peter,
> 
> That was a fast job :)
> 
> I agree with the structure and with the position for
> the resource files.
> 
> Only one question, do you plan to simplify the
> classes? I think would be
> good to have simpler classes and not the big and
> complex classes that we've
> now. If you don't have time to do it, tell me.
> 
> On the other hand I would like to heard your opinion
> about the new features
> and to way to continue with the project. I was
> thinking to release the new
> version as it is (just test that everything works)
> and then do a new
> intermediate release finishing some pending work,
> basically something like:
> 
> Version 1.2.5
> - ProgressBar (needs code reestructuration):
>   + Show ProgressBar in all time consuming events
> (sort & import) ???
>   + ProgressBar must show the correct progression
> when available
> - Rewrite the import code (site and XML) to support:
>   + Detect when a series/issue is already imported
>     - Show that issue different in the
> IssueSelectDialog
>     - Show a warning before overwrite it (delete and
> import the new one or
> just overwrite ???)
> - Error System:
>   + More information. Add field support (redirect to
> the field and show some
> kind of warning in the field)
>   + Redirect System.err to the errors table
>     - Config a debug option. Show some information
> only if debug enabled.
>     - Needs to implement a new tab for text
> information
>     - Remove all the System.err and use the Error
> system
>   + Add contextual menu to the errors panel
> - Preferences Dialog:
>   + Possibility to reset to default values
> 
> Most of that things where listed in the previous
> list of future features,
> but I think that they're just features that are not
> finished or correctly
> done, so they've higher priority that new features.
> What do you think?
> 
> By the way, great job restructuring the code :D
> 
> Regards,
> Carlos.
> 
> > -----Mensaje original-----
> > De: tes...@li... 
> >
> [mailto:tes...@li...]
> En 
> > nombre de Petter Wintzell
> > Enviado el: miércoles, 09 de junio de 2004 20:42
> > Para: Testimony devel
> > Asunto: [Testimony-devel] Restructure complete
> (almost)
> > 
> > Hi,
> > 
> > I have now completed the restructuring work. A few
> > things:
> > 
> > - Some of the files where not in your design,
> Carlos.
> > I added them where I thought they fitted...
> > 
> > - I have not added the resources to the tree yet,
> so don't 
> > delete your old files just yet... I don't think it
> was fully 
> > decided where they should be placed (see below).
> > 
> > Carlos, could you please take a look at the new
> structure and 
> > see if you like it? The module is called
> testimony, as we 
> > agreed. If there's anything that you want to have
> changed, 
> > it's probably easiest to fix it right away, and
> create a new 
> > module again.
> > 
> > About the resources:
> > 
> > In my opinion, the src directory should contain
> Java source 
> > code files, and nothing else. This makes it easier
> to write 
> > tools that work on the directory structure, for
> instance, the 
> > Ant script I'm planning to do. Also, I think it
> makes the 
> > directory structure cleaner.
> > 
> > I think the best way to go is to have a resources
> folder on 
> > the same level as the src folder. The Ant build
> script will 
> > compile the Java sources from the src folder into
> a build 
> > folder and copy the resources there so that the
> application 
> > can be run. It will also create jar files etc.
> > 
> > Any opinions on this? Once we agree on this, I
> will add the 
> > home page files and create the Ant build file.
> > 
> > Regards,
> > Petter
> > 
> > 
> > 	
> > 		
> > __________________________________
> > Do you Yahoo!?
> > Friends.  Fun.  Try the all-new Yahoo! Messenger.
> > http://messenger.yahoo.com/ 
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email is sponsored by: GNOME
> Foundation Hackers 
> > Unite!  GUADEC: The world's #1 Open Source Desktop
> Event.
> > GNOME Users and Developers European Conference,
> 28-30th June 
> > in Norway http://2004/guadec.org 
> > _______________________________________________
> > Testimony-devel mailing list
> > Tes...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/testimony-devel
> > 
> 
> 



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

[Testimony-devel] Ant build file

[Petter W. <pet...@ya...>]

Hi,

Having some time over, I created a very simple Ant
build file for the project. This will be extended
later once everything with the restructuring fall into
place.

Regards,
Petter


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/