From fba at arxsys.fr  Tue Jan  4 17:52:05 2011
From: fba at arxsys.fr (=?ISO-8859-1?Q?Fr=E9d=E9ric_Baguelin?=)
Date: Tue, 04 Jan 2011 16:52:05 +0000
Subject: [dff-devel] Patch to avoid changing About string every time
 application version is changed
In-Reply-To: <AANLkTini1atUCF9XYoCBrXYYHKOeH9ShiAicYw7YQErS@mail.gmail.com>
References: <AANLkTini1atUCF9XYoCBrXYYHKOeH9ShiAicYw7YQErS@mail.gmail.com>
Message-ID: <4D235035.9070600@arxsys.fr>

Hi,

It will be merged for the next release ;)

Keep up the good work :)

Thanks.

Pablo Rogina wrote:
> Hi,
> 
> please find attached patch to avoid changing the About string every
> time the application version is changed. It uses %1 and arg() method
> from tr() to dynamically replace text inside the translated string.
> 
> Thanks,
> 
> Pablo
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> dff-devel mailing list
> dff-devel at digital-forensic.org
> http://lists.digital-forensic.org/listinfo/dff-devel


-- 
Fr?d?ric Baguelin    frederic.baguelin at arxsys.fr
ArxSys SAS, Directeur technique
T?l: +33 146 362 522

From christophe.malinge at arxsys.fr  Fri Jan  7 11:58:02 2011
From: christophe.malinge at arxsys.fr (Christophe Malinge)
Date: Fri, 07 Jan 2011 11:58:02 +0100
Subject: [dff-devel] DDF Spanish - first two patchs
In-Reply-To: <AANLkTinKOJ9eGB1etK8ViLG-dSXJHtASY6hQ3CfLn2+x@mail.gmail.com>
References: <AANLkTinKOJ9eGB1etK8ViLG-dSXJHtASY6hQ3CfLn2+x@mail.gmail.com>
Message-ID: <4D26F1BA.8050000@arxsys.fr>

On 12/25/10 19:23, Pablo Rogina wrote:
> Hi,
>
> please find attached compressed patch for my two commit about Spanish
> translations. First one is the initial translation of Dff_es.ts file,

Thanks, '[PATCH 1/2] Initial Spanish translation' has just been commited.

Here is the commit log :

From: Pablo J. Rogina <pablojr at gmail.com>
Date: Wed, 22 Dec 2010 20:25:17 -0300
Subject: [PATCH 1/2] Initial Spanish translation
Based on instructions provided in commit for #84. This is work in progress

Add Spanish translation, thanks to Pablo J. Rogina.
Updated to fit new lines since modification.
Also adds caps to menu in mainwindow.
Keep obsolete translation in Dff_es.ts to be used for future 
translatable string resolve, spanish people should have a look to delete 
it or update unfinished ones.

This commit refs #84.


Please see 
https://tracker.digital-forensic.org/projects/dff/repository/revisions/0dd0f4eac2ecb064a0f69918a7220e733cb9e9d3

-- 
Christophe Malinge
DFF, Core developer, System administrator
ArxSys SAS, Directeur des syst?mes d'information
T?l: +33 1 46 36 25 22


From christophe.malinge at arxsys.fr  Fri Jan  7 12:20:02 2011
From: christophe.malinge at arxsys.fr (Christophe Malinge)
Date: Fri, 07 Jan 2011 12:20:02 +0100
Subject: [dff-devel] DDF Spanish - first two patchs
In-Reply-To: <AANLkTinKOJ9eGB1etK8ViLG-dSXJHtASY6hQ3CfLn2+x@mail.gmail.com>
References: <AANLkTinKOJ9eGB1etK8ViLG-dSXJHtASY6hQ3CfLn2+x@mail.gmail.com>
Message-ID: <4D26F6E2.2050509@arxsys.fr>

On 12/25/10 19:23, Pablo Rogina wrote:
> created based on instructions from commit about issue #84. Then I went
> along and also changed Select Device dialog (it appears when Add
> device(s) option is selected). This changed led to the other


Thanks, '[PATCH 2/2] Select device dialog made translatable' has just 
been commited.

From: Pablo J. Rogina <pablojr at gmail.com>
Date: Sat, 25 Dec 2010 14:38:40 -0300
Subject: [PATCH 2/2] Select device dialog made translatable

Added several tr() calls for existing UI strings along missing dialog title.

Thanks to Pablo J. Rogina, this patch as been added.
As in previous commit ; 'Keep obsolete translation in Dff_es.ts to be 
used for future translatable string resolve, spanish people should have 
a look to delete it or update unfinished ones.'


Please see 
https://tracker.digital-forensic.org/projects/dff/repository/revisions/edaafbdcc6688f5228591001e0b2a57d39c8e63a

> translation files changed as well (since new strings were found). I
> didn't translate the French file (I cannot do it...) but I'm including
> the .ts files in the patch.

This file is now updated.

> I also tried to modify the Modules option in main window, but I'll
> comment about that in a separate mail...

Will fix it as soon as possible.

-- 
Christophe Malinge
DFF, Core developer, System administrator
ArxSys SAS, Directeur des syst?mes d'information
T?l: +33 1 46 36 25 22


From christophe.malinge at arxsys.fr  Fri Jan  7 12:30:14 2011
From: christophe.malinge at arxsys.fr (Christophe Malinge)
Date: Fri, 07 Jan 2011 12:30:14 +0100
Subject: [dff-devel] Patch to avoid changing About string every time
 application version is changed
In-Reply-To: <4D235035.9070600@arxsys.fr>
References: <AANLkTini1atUCF9XYoCBrXYYHKOeH9ShiAicYw7YQErS@mail.gmail.com>
	<4D235035.9070600@arxsys.fr>
Message-ID: <4D26F946.3070708@arxsys.fr>

On 01/04/11 17:52, Fr?d?ric Baguelin wrote:
> Hi,
>
> It will be merged for the next release ;)

Which is on the way ! Merge ok for it.

> Pablo Rogina wrote:
>> Hi,
>>
>> please find attached patch to avoid changing the About string every
>> time the application version is changed. It uses %1 and arg() method
>> from tr() to dynamically replace text inside the translated string.
>>
>> Thanks,
>>
>> Pablo

'[PATCH 3/3] Changed About string to include version number as argument' 
has just been commited.

Here is the commit log :
From: Pablo J. Rogina <pablojr at gmail.com>
Date: Mon, 27 Dec 2010 19:45:58 -0300
Subject: [PATCH 3/3] Changed About string to include version number as 
argument

To avoid changing the string every time the version is changed,
it now uses .arg() to dynamically replace the variable text

Thanks again Pablo ! It works well.

Please see 
https://tracker.digital-forensic.org/projects/dff/repository/revisions/a8c7604c73f6514b43100580d79299c057a95583

-- 
Christophe Malinge
DFF, Core developer, System administrator
ArxSys SAS, Directeur des syst?mes d'information
T?l: +33 1 46 36 25 22


From project at digital-forensic.org  Mon Jan 10 16:00:24 2011
From: project at digital-forensic.org (Digital Forensics Framework)
Date: Mon, 10 Jan 2011 16:00:24 +0100
Subject: [dff-devel] DFF 0.9 released
Message-ID: <4D2B1F08.4090404@digital-forensic.org>

DFF 0.9 has just been released and can be downloaded at:
http://www.digital-forensic.org/download

This release includes major bug fixes improving the stability of the
framework on some platforms, and also lots of new features.

First of all, we would like to thank two new contributors:
- Pablo J. Rogina who has done the Spanish translation and has provided 
patches and feedback.
- Johannes Stuettgen who is developing a module providing support to 
AFF4 that will be certainly included in 1.0 release.


New Features:
-------------

* Lib EWF support:
      The LibEWF [1], developed by Joachim Metz, has been included as a
connector.
      It provides support for Encase(R) file format (E01/S01 format).

* Bookmarks:
      It is now possible to bookmark interesting nodes and sort them by 
categories. The aim is to gather relevant files when performing analysis.
      Bookmarked nodes can then be used by other modules and also extracted.

* Advanced Hexadecimal viewer:
      Features used to resolve the DFRWS 2010 challenge [2] have been
included.
      This upgraded version of the hexadecimal viewer provides three new 
visualization modes:
      - A pixel view that renders dumps in a graphical manner. It 
permits to recognize structures in a visual way. Several options are 
provided for rendering the view (8bits, RGB, resolution, ...)
      - A block mode view providing a simple way to see a dump in block 
mode. Size of blocks can be chosen in the corresponding option panel.
      - A streamed string view which renders printable characters.

      These features are very useful when studying unknown data 
structures or performing advanced files analysis.

* NTFS ADS:
      The NTFS module now supports ADS streams. With ADS, several data 
streams belong to one file entry, each data stream is provided as a node 
which simplifies analysis.

* Windows Devices:
      Devices on Windows can now be directly opened and used in DFF. It 
enables Live Forensics analysis in an easy way. It also provides a way 
to dump devices by extracting the corresponding nodes.

* Virtual modification of nodes (aka files):
      Two new modules have been added to modify nodes virtually (i.e. in 
memory, without writing on disk):
      - Cut module create a new node from a part of a file by providing 
a start offset and a size.
      - Merge module allows to merge two files in a new one.

      These two modules are very useful when working with large files.

* Loader and API versioning:
      Each component of the API now has its own version number. Modules 
and scripts can now provide specific API component dependency and will 
be checked when loaded. Loader retro-compatibility is maintained as it 
actually loads modules and scripts using old manner.

* Inline documentation:
      An inline documentation has been directly incorporated in the 
Framework.
      It is now possible to browse the documentation directly in the 
software and in a disconnected environment.

* Execution times:
      Each process in the task manager now displays time of execution.

* Enhanced GUI ergonomy;
      Several parts of the GUI have been enhanced to provide a better 
look and feel to the user:
      - Dialog window used to provide arguments to modules has been 
redesigned.
      - Easier selection of input files and / or directories
      - Enhanced dialog to select devices
      - Right click has been re-factored. Some categories have been renamed.

* Languages pack:
      Using --lang switch when starting DFF in command line provides a 
way to select the language to use in the Graphical User Interface.
      Translations are provided for three different languages: English, 
Spanish and French. Contribution to support other languages are welcomed.

* Debug switch
      A new switch (-d) enables to output all prints to the console 
without modifying lines of code.


Bug fixes:
----------

* GUI proxy model issues:
      A major bug in the node browser conducting to crashes on some 
architecture has been fixed. It was related to the refresh events on 
Nodes and the way signals where sent between views and model.

* Exceptions:
      Exceptions were not correctly handled in 0.8 version. There is now 
a generic exceptions handler used for each wrapped methods. This 
significantly reduces crashes and provides more user friendly messages 
when errors have been encountered in modules.

* NTFS :
      Attributes parsing on huge file-system has been improved.
      DFF attributes conversion from int to string has been removed. It 
was used to show both decimal and hexadecimal views. It has to be
managed by graphical view itself.
      MFT and Indexes decoding mode have been fixed (entries starting 
with FILE or INDX). It is useful for deep analysis.

* EXTFS:
      The error management is made properly. Default values and 
behaviors for some options have been modified in order to start the 
module without modifying the default configuration.

* Argument:
      Fixed issues with integer type and optional arguments generated by 
the GUI in 0.8.

* Picture viewer:
      Exif information are no longer editable


And of course, Happy New Year !


[1] http://sourceforge.net/projects/libewf/
[2] http://www.dfrws.org/2010/challenge/index.shtml

-- 
contact at digital-forensic.org
Main website: http://www.digital-forensic.org
Documentation wiki: http://wiki.digital-forensic.org
Project tracker: https://tracker.digital-forensic.org

From pablojr at gmail.com  Thu Jan 13 17:11:02 2011
From: pablojr at gmail.com (Pablo Rogina)
Date: Thu, 13 Jan 2011 13:11:02 -0300
Subject: [dff-devel] Use of Qt Designer and .ui files for GUI
Message-ID: <AANLkTik0qzntNgUsje-E2fK5R-GiiOocb-7Q5vdc6_jX@mail.gmail.com>

Hi,

while I was working on the Spanish translations, I realized that
project DFF is not using .ui files from Qt for designing the GUI.

The team may have a good reason about doing so (please let me know if
yes), but since I'm so used to Qt Designer to "draw" dialogs, windows,
etc. in a graphical way instead of laying out all the components by
code I went and tried a little PoC (proof of concept) using the Select
Devices dialog as example.

Please find attach a patch that comprises several changes. What the
patch doesn't do is remove the selectdevices.py file (it will no
longer be required) and it also doesn't run pyuic4 in order to create
Python code from the .ui file (xml) every time the UI component layout
is changed using Qt Designer.

I took the approach of using one .ui file (i.e. devicesdialog.ui) that
gets converted into Python code by tool pyuic4 (ui_devicesdialog.py)
which is a class for the entire UI and it's overwritten every time the
.ui file changes and the pyuic4 tool is run again and then another
class (hand written) where most of the actions and methods regarding
what the dialog will do is placed. This separate class uses the UI
class.

I think using Qt Designer and .ui files will benefit the project since
it's easier to layout a UI component visually, and at the same time,
the same .ui file could be used to generate C++ given the need to
write or run the application (or at least the GUI part) in C++

Please let me know what you think about all this.

Thanks,

Pablo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Proof-of-concept-to-use-Qt-Designer-and-.ui-files-fo.patch
Type: text/x-patch
Size: 9440 bytes
Desc: not available
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110113/67d08b62/attachment.bin>

From pablojr at gmail.com  Fri Jan 14 03:11:46 2011
From: pablojr at gmail.com (Pablo Rogina)
Date: Thu, 13 Jan 2011 23:11:46 -0300
Subject: [dff-devel] Updated Spanish translation file
Message-ID: <AANLkTin6r1hbzPF8YQ9EZpii_xT+5W4RVmKDOgfC81x_@mail.gmail.com>

Please find attached patch with up to date Spanish .ts file

Thanks,

Pablo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-Spanish-translation-file.patch
Type: text/x-patch
Size: 4919 bytes
Desc: not available
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110113/710adf90/attachment-0001.bin>

From pablojr at gmail.com  Fri Jan 14 03:24:38 2011
From: pablojr at gmail.com (Pablo Rogina)
Date: Thu, 13 Jan 2011 23:24:38 -0300
Subject: [dff-devel] Please don't commit files with commented code
Message-ID: <AANLkTimHscyZa8j4RuFmUpX2ChaBBhS+x0hDo8HX5YjL@mail.gmail.com>

Please don't take this as criticism but as a suggestion based on
software development practices implemented by lot of projects all
around.

I found a lot of places/files with commented code. Don't commit
commented source code into the repository. It's Ok to comment some
pieces of code while you?re working on your local development
environment, just to quickly try a new feature or a fix, but the
moment you find that the commented piece of code isn't really
required, go and effectively removed it from the source code before
committing your changes.

Since we're using a VCS (Version Control System) to track changes to
source code, let the VCS do the work of showing a developer what was
removed or added since previous version. Sometimes it's hard to figure
out why the commented code is in such state or if it should be
replaced back. Even the developer commenting the code may doubt when
he/she is back there let's say 6 month after the comments.

Just my 2 cents...

Thanks,

Pablo

From solal.jacob at ArxSys.fr  Fri Jan 14 13:10:39 2011
From: solal.jacob at ArxSys.fr (Solal Jacob)
Date: Fri, 14 Jan 2011 12:10:39 +0000
Subject: [dff-devel] Use of Qt Designer and .ui files for GUI
In-Reply-To: <AANLkTik0qzntNgUsje-E2fK5R-GiiOocb-7Q5vdc6_jX@mail.gmail.com>
References: <AANLkTik0qzntNgUsje-E2fK5R-GiiOocb-7Q5vdc6_jX@mail.gmail.com>
Message-ID: <4D303D3F.3020502@ArxSys.fr>

Hi,

We used it some time ago but we thought it could cause problems with
some dynamic widget,
and that it could be less clear to have to change xml files than
directly modify code.
It's certainly wrong and will certainly improve the interfaces and be
easier to use QtDesigner,
I will test that and try to change my bad habits. (I personnaly don't
like  much to develop with
a graphical environement). Also when I create widget they're most of the
time ugly, so it could
certainly help me made them have a better look.

Thank for the advise.



On 01/13/11 16:11, Pablo Rogina wrote:
> Hi,
>
> while I was working on the Spanish translations, I realized that
> project DFF is not using .ui files from Qt for designing the GUI.
>
> The team may have a good reason about doing so (please let me know if
> yes), but since I'm so used to Qt Designer to "draw" dialogs, windows,
> etc. in a graphical way instead of laying out all the components by
> code I went and tried a little PoC (proof of concept) using the Select
> Devices dialog as example.
>
> Please find attach a patch that comprises several changes. What the
> patch doesn't do is remove the selectdevices.py file (it will no
> longer be required) and it also doesn't run pyuic4 in order to create
> Python code from the .ui file (xml) every time the UI component layout
> is changed using Qt Designer.
>
> I took the approach of using one .ui file (i.e. devicesdialog.ui) that
> gets converted into Python code by tool pyuic4 (ui_devicesdialog.py)
> which is a class for the entire UI and it's overwritten every time the
> .ui file changes and the pyuic4 tool is run again and then another
> class (hand written) where most of the actions and methods regarding
> what the dialog will do is placed. This separate class uses the UI
> class.
>
> I think using Qt Designer and .ui files will benefit the project since
> it's easier to layout a UI component visually, and at the same time,
> the same .ui file could be used to generate C++ given the need to
> write or run the application (or at least the GUI part) in C++
>
> Please let me know what you think about all this.
>
> Thanks,
>
> Pablo
>   
>
>
> _______________________________________________
> dff-devel mailing list
> dff-devel at digital-forensic.org
> http://lists.digital-forensic.org/listinfo/dff-devel
>   


-- 
Solal Jacob 		   solal.jacob at arxsys.fr
ArxSys, Riposte Num?rique
14-16, Rue du Soleilet 75020 Paris
T?l: +33 1 46 36 25 22 
www.arxsys.fr           www.digital-forensic.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110114/c15a2eb4/attachment.html>

From rbe at arxsys.fr  Fri Jan 14 11:28:19 2011
From: rbe at arxsys.fr (romain)
Date: Fri, 14 Jan 2011 11:28:19 +0100
Subject: [dff-devel] Please don't commit files with commented code
In-Reply-To: <AANLkTimHscyZa8j4RuFmUpX2ChaBBhS+x0hDo8HX5YjL@mail.gmail.com>
References: <AANLkTimHscyZa8j4RuFmUpX2ChaBBhS+x0hDo8HX5YjL@mail.gmail.com>
Message-ID: <4D302543.4090903@arxsys.fr>

Hi,

You are right on that point, commented code should not be commited. This 
is a bad habit, and we will try not to do it again in the future.

Btw, we do not take any piece of advice as criticism, on the contrary, 
it helps us making the development more structured.

Thanks for the advice (and for the 2 cents :) )

Pablo Rogina wrote:
> Please don't take this as criticism but as a suggestion based on
> software development practices implemented by lot of projects all
> around.
> 
> I found a lot of places/files with commented code. Don't commit
> commented source code into the repository. It's Ok to comment some
> pieces of code while you?re working on your local development
> environment, just to quickly try a new feature or a fix, but the
> moment you find that the commented piece of code isn't really
> required, go and effectively removed it from the source code before
> committing your changes.
> 
> Since we're using a VCS (Version Control System) to track changes to
> source code, let the VCS do the work of showing a developer what was
> removed or added since previous version. Sometimes it's hard to figure
> out why the commented code is in such state or if it should be
> replaced back. Even the developer commenting the code may doubt when
> he/she is back there let's say 6 month after the comments.
> 
> Just my 2 cents...
> 
> Thanks,
> 
> Pablo
> _______________________________________________
> dff-devel mailing list
> dff-devel at digital-forensic.org
> http://lists.digital-forensic.org/listinfo/dff-devel
> 


-- 
Romain

From solal.jacob at ArxSys.fr  Fri Jan 14 14:09:11 2011
From: solal.jacob at ArxSys.fr (Solal Jacob)
Date: Fri, 14 Jan 2011 13:09:11 +0000
Subject: [dff-devel] Please don't commit files with commented code
In-Reply-To: <AANLkTimHscyZa8j4RuFmUpX2ChaBBhS+x0hDo8HX5YjL@mail.gmail.com>
References: <AANLkTimHscyZa8j4RuFmUpX2ChaBBhS+x0hDo8HX5YjL@mail.gmail.com>
Message-ID: <4D304AF7.7080806@ArxSys.fr>

Hi Pablo,

I totally agree with you.
I take care of that some time ago, but I don't know why I stopped and
now lot of my code is full of commentary that I forget to remove,
even worse some line of comment are in french and some other in english
(not very understandable more over).
It seems you already have contributed in lot of open-source project,
so it's great for us to have your advises.

Thanks,

Solal.


On 01/14/11 02:24, Pablo Rogina wrote:
> Please don't take this as criticism but as a suggestion based on
> software development practices implemented by lot of projects all
> around.
>
> I found a lot of places/files with commented code. Don't commit
> commented source code into the repository. It's Ok to comment some
> pieces of code while you?re working on your local development
> environment, just to quickly try a new feature or a fix, but the
> moment you find that the commented piece of code isn't really
> required, go and effectively removed it from the source code before
> committing your changes.
>
> Since we're using a VCS (Version Control System) to track changes to
> source code, let the VCS do the work of showing a developer what was
> removed or added since previous version. Sometimes it's hard to figure
> out why the commented code is in such state or if it should be
> replaced back. Even the developer commenting the code may doubt when
> he/she is back there let's say 6 month after the comments.
>
> Just my 2 cents...
>
> Thanks,
>
> Pablo
> _______________________________________________
> dff-devel mailing list
> dff-devel at digital-forensic.org
> http://lists.digital-forensic.org/listinfo/dff-devel
>   


-- 
Solal Jacob 		   solal.jacob at arxsys.fr
ArxSys, Riposte Num?rique
14-16, Rue du Soleilet 75020 Paris
T?l: +33 1 46 36 25 22 
www.arxsys.fr           www.digital-forensic.org


From solal.jacob at ArxSys.fr  Fri Jan 14 19:35:22 2011
From: solal.jacob at ArxSys.fr (Solal Jacob)
Date: Fri, 14 Jan 2011 18:35:22 +0000
Subject: [dff-devel] Patch to disable QtHelp
Message-ID: <4D30976A.7030302@ArxSys.fr>

Hi all,

This patch is for disabling the in-line help for those who doesn't have
compiled PyQt with QtAssistant & QtHelp.

Solal.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dff-disable-help-if-PyQt-without-assistant-and-webkit.patch
Type: text/x-patch
Size: 2003 bytes
Desc: not available
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110114/f2a0fa87/attachment.bin>

From pablojr at gmail.com  Mon Jan 17 18:48:49 2011
From: pablojr at gmail.com (Pablo Rogina)
Date: Mon, 17 Jan 2011 14:48:49 -0300
Subject: [dff-devel] Patch to make NodeViewBox translatable
Message-ID: <AANLkTim0PVNOZATeRO-S9t0Gv_Crh8oYC+dGx_1Xp6b-@mail.gmail.com>

Please find attached patch to make NodeViewBox translatable. Provided
also updated Spanish translations for those new strings in .ts files

Thanks,

Pablo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-NodeViewBox-to-make-it-translatable.patch
Type: text/x-patch
Size: 29504 bytes
Desc: not available
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110117/e9e8d6a5/attachment-0001.bin>

From christophe.malinge at arxsys.fr  Tue Jan 18 12:34:24 2011
From: christophe.malinge at arxsys.fr (Christophe Malinge)
Date: Tue, 18 Jan 2011 12:34:24 +0100
Subject: [dff-devel] Patch to make NodeViewBox translatable
In-Reply-To: <AANLkTim0PVNOZATeRO-S9t0Gv_Crh8oYC+dGx_1Xp6b-@mail.gmail.com>
References: <AANLkTim0PVNOZATeRO-S9t0Gv_Crh8oYC+dGx_1Xp6b-@mail.gmail.com>
Message-ID: <4D357AC0.9070407@arxsys.fr>

On 01/17/11 18:48, Pablo Rogina wrote:
> Please find attached patch to make NodeViewBox translatable. Provided
> also updated Spanish translations for those new strings in .ts files
>
> Thanks,
>
> Pablo
>

Hello Pablo, thanks for it !

It has just been added to the master tree.

Here is the commit log:
From: Pablo J. Rogina <pablojr at gmail.com>
Date: Mon, 17 Jan 2011 14:45:07 -0300
Subject: [PATCH] Updated NodeViewBox to make it translatable

Added missing tr() calls along with adding Python files into the list of 
translatable files and updated Spanish .ts file

Thanks to Pablo J. Rogina for this patch. Also update:
- French .ts file for new translatable files.
- Other .ts files to be updated : Deutsch and Dutch

This commit references #92 : Translate every files.

Please see 
https://tracker.digital-forensic.org/projects/dff/repository/revisions/157ad432ba42f6f24155027e62c747f0664302c0

Thanks again.

Christophe

-- 
Christophe Malinge
DFF, Core developer, System administrator
ArxSys SAS, Directeur des syst?mes d'information
T?l: +33 1 46 36 25 22


From jmo at arxsys.fr  Wed Jan 19 10:30:19 2011
From: jmo at arxsys.fr (=?ISO-8859-1?Q?J=E9r=E9my_MOUNIER?=)
Date: Wed, 19 Jan 2011 10:30:19 +0100
Subject: [dff-devel] Use of Qt Designer and .ui files for GUI
In-Reply-To: <AANLkTik0qzntNgUsje-E2fK5R-GiiOocb-7Q5vdc6_jX@mail.gmail.com>
References: <AANLkTik0qzntNgUsje-E2fK5R-GiiOocb-7Q5vdc6_jX@mail.gmail.com>
Message-ID: <4D36AF2B.2040300@arxsys.fr>

Hi pablo,

I'm one of the GUI developer and want first to thank you for your 
precious tips and help.
First of all, concerning Qt Designer i'm not very familiar with this 
tool, but Christophe is working hard and I think it will be interesting 
to use it for some parts.

I want to have your advice concerning one thing. When i read QMainWindow 
documentation, i saw that it's mandatory to use a centralWidget. Do you 
think that we can integrate a system composed by only dockwidgets ? This 
kind of system will be less restrictive and will enable some interesting 
functionnalities.

Another question, you suggest in the tracker to use a TabWidget in order 
to display module's arguments and parameters, i tried this but as I said 
in the Issue, when a module (like ExtFS) has too many arguments, the 
system is not very clear because names of arguments are not very 
readable. I decided to use a liswidget combinated to QStackedWidget, 
what do you think about that ?

Thank you again,

J?r?my

On 01/13/2011 05:11 PM, Pablo Rogina wrote:
> Hi,
>
> while I was working on the Spanish translations, I realized that
> project DFF is not using .ui files from Qt for designing the GUI.
>
> The team may have a good reason about doing so (please let me know if
> yes), but since I'm so used to Qt Designer to "draw" dialogs, windows,
> etc. in a graphical way instead of laying out all the components by
> code I went and tried a little PoC (proof of concept) using the Select
> Devices dialog as example.
>
> Please find attach a patch that comprises several changes. What the
> patch doesn't do is remove the selectdevices.py file (it will no
> longer be required) and it also doesn't run pyuic4 in order to create
> Python code from the .ui file (xml) every time the UI component layout
> is changed using Qt Designer.
>
> I took the approach of using one .ui file (i.e. devicesdialog.ui) that
> gets converted into Python code by tool pyuic4 (ui_devicesdialog.py)
> which is a class for the entire UI and it's overwritten every time the
> .ui file changes and the pyuic4 tool is run again and then another
> class (hand written) where most of the actions and methods regarding
> what the dialog will do is placed. This separate class uses the UI
> class.
>
> I think using Qt Designer and .ui files will benefit the project since
> it's easier to layout a UI component visually, and at the same time,
> the same .ui file could be used to generate C++ given the need to
> write or run the application (or at least the GUI part) in C++
>
> Please let me know what you think about all this.
>
> Thanks,
>
> Pablo
>    
>
>
> _______________________________________________
> dff-devel mailing list
> dff-devel at digital-forensic.org
> http://lists.digital-forensic.org/listinfo/dff-devel
>    


-- 
J?r?my MOUNIER - jeremy.mounier at arxsys.fr
ArxSys - Solutions logicielles de m?decine l?gale num?rique
14 rue Soleillet, 75020 PARIS
T?l: +33 1 46 36 25 22
www.arxsys.fr - www.digital-forensic.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110119/49fd53f5/attachment.html>

From dschreiber at gmx.de  Thu Jan 20 18:24:57 2011
From: dschreiber at gmx.de (D. Schreiber)
Date: Thu, 20 Jan 2011 18:24:57 +0100
Subject: [dff-devel] german translation
Message-ID: <4D386FE9.6010403@gmx.de>

updated german translation file attached
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Dff_de.ts.tar.gz
Type: application/x-gzip
Size: 4239 bytes
Desc: not available
URL: <http://lists.digital-forensic.org/pipermail/dff-devel/attachments/20110120/0ae6807c/attachment.bin>