#23 UI 4 config proc #1341

thiagofuer · 2022-09-28T17:24:17Z

This is the first part of issue #23 implementation for review and suggestion.
Layout content:
-Home page with logo and options buttons ("Open case" button not implemented yet)
-Config menu (by now it only read properties and do not write)
-New case menu
tab case info: read data but don't save
tab evidences: only "add disk" is missing
tab process options: not implemented yet
-"Start processing" is being implemented now

no internationalization ready (it's in pt-br only)
To test the new UI implementation go to iped.app.home.MainFrame and run main method
you need to setup iped properties location manually (by now its hard coded)

lfcnassif · 2022-09-28T21:09:18Z

Thank you very much @thiagofuer for helping with this! I plan to review this next week.

patrickdalla · 2022-11-01T11:53:15Z

Tasks dependecy/order are not declared in any interface or method. Is this important to order the tasks configuration panel?

thiagofuer · 2022-11-01T17:40:58Z

maybe sort in alphabetical order by default
or a option to sort by click on column name but i believe it is not mandatory now.
I'm planing back to code beginning November 14...

lfcnassif · 2022-11-01T17:51:38Z

Tasks dependecy/order are not declared in any interface or method

This can be found in iped.engine.config.TaskInstallerConfig class.

The user shouldn't be able to change task sorting, since the execution order/task dependency is VERY sensitive.

thiagofuer · 2022-11-01T18:09:39Z

but the task sort could be done only on the config view without reflect on the execution order. It could be only to be easy to user found.

patrickdalla · 2022-11-01T18:44:58Z

"order/task dependency is VERY sensitive"
Yes, but we have to define if the user will be able to disable/enable a task on the config UI, and if so, which other tasks should be included together with the selected task (and the order they will be included) to it function properly.

patrickdalla · 2022-11-01T18:49:18Z

but the task sort could be done only on the config view without reflect on the execution order. It could be only to be easy to user found.

Mainly the dependency structure needed is not for task list visual ordering. I think the best is to to exhibit on the correct execution order. It is to automatically include dependent tasks (in the correct order) when a task is checked to be included in the processing.

lfcnassif · 2022-11-01T18:52:02Z

It could be only to be easy to user found.

I prefer to always display the processing pipeline execution order.

which other tasks should be included together with the selected task

Good point, this is important. Notice this situation can already occur without the configuration UI, only changing config files today. Some modules check their dependencies and, if not met, they abort or disable itself printing a warning message in the Console. This approach could be improved for the UI.

patrickdalla · 2022-11-01T19:29:44Z

@thiagofuer, a specific task can have more than one configurable. For example, ParsingTask has ParsingTaskConfig, CategoryToExpand, Parsers and ExternalParsers configurables.

Maybe a Tree instead of table can be more suitable. Something like this (pardon for the bad UI of the tree, you can improve later):

patrickdalla · 2022-11-01T19:36:35Z

Or the table could be kept, and each configurable of the task could be presented as a TAB in the corresponding Task config UI dialog.

lfcnassif · 2022-11-01T19:39:54Z

Or the table could be kept, and each configurable of the task could be presented as a TAB in the corresponding Task config UI dialog.

This is exactly how I thought about it. I think this is more user friendly.

thiagofuer · 2022-11-01T19:52:24Z

@thiagofuer, a specific task can have more than one configurable. For example, ParsingTask has ParsingTaskConfig, CategoryToExpand, Parsers and ExternalParsers configurables.

Maybe a Tree instead of table can be more suitable. Something like this (pardon for the bad UI of the tree, you can improve later):

To use a tree certainly is the easy way to show tasks config, but i think that could not be the best solution for unexperienced user.

Or the table could be kept, and each configurable of the task could be presented as a TAB in the corresponding Task config UI dialog.

this is the more user friendly UI option. Most of effort spent in this job is to create a interface that can do IPED "easy" to operate.

On my opinion, we should think on how to add all additional tasks configurables on this dialog. Tabs is a good one!!

patrickdalla · 2022-11-01T19:56:44Z

Maybe as Tabbed panels Em ter., 1 de nov. de 2022 15:52, Thiago S. Figueiredo < ***@***.***> escreveu:

…

@thiagofuer <https://github.com/thiagofuer>, a specific task can have more than one configurable. For example, ParsingTask has ParsingTaskConfig, CategoryToExpand, Parsers and ExternalParsers configurables. Maybe a Tree instead of table can be more suitable. Something like this (pardon for the bad UI of the tree, you can improve later): [image: image] <https://user-images.githubusercontent.com/28692427/199321295-d807768f-a723-4611-b0ec-ee3475f249ea.png> To use a tree certainly is the easy way to show tasks config, but i think that could not be the best solution for unexperienced user. Or the table could be kept, and each configurable of the task could be presented as a TAB in the corresponding Task config UI dialog. this is the more user friendly UI option. Most of effort spent in this job is to create a interface that can do IPED "easy" to operate. [image: image] <https://user-images.githubusercontent.com/1029909/199325157-d5d3eb15-7ff1-4b74-86cd-f52f3852da19.png> On my opinion, we should think on how to add all additional tasks configurables on this dialog. Tabs is a good one!! — Reply to this email directly, view it on GitHub <#1341 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG247S4EBXYU6UEVRF6ZTHTWGFYIJANCNFSM6AAAAAAQX73M7A> . You are receiving this because you commented.Message ID: ***@***.***>

lfcnassif · 2022-11-04T13:35:52Z

Sorry, I'm a bit busy now...

@lfcnassif , I could not find a way to identify which Configurable objects are used by each AbstractTask. I think in put it as a static method of class AbstractTask with the signature Set>> getConfigurables(). So we can identify which configurable classes is used to instantiate the Task, and look for this kind of objects in the ConfigurationManager object.

This already exists, but the method is not static. Wouldn't it be enough?

patrickdalla · 2022-11-04T14:09:32Z

yes. I found. it is enough. Em sex., 4 de nov. de 2022 09:36, Luis Filipe Nassif < ***@***.***> escreveu:

…

Sorry, I'm a bit busy now... @lfcnassif <https://github.com/lfcnassif> , I could not find a way to identify which Configurable objects are used by each AbstractTask. I think in put it as a static method of class AbstractTask with the signature Set>> getConfigurables(). So we can identify which configurable classes is used to instantiate the Task, and look for this kind of objects in the ConfigurationManager object. This already exists, but the method is not static. Wouldn't it be enough? — Reply to this email directly, view it on GitHub <#1341 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG247S3DZTNL5TIQGFHAJ2DWGUGMFANCNFSM6AAAAAAQX73M7A> . You are receiving this because you commented.Message ID: ***@***.***>

patrickdalla · 2022-11-04T18:36:38Z

This method (getConfigurables) is implemented in the AbstractTask descendants classes to return empty configurable objects. Not the loaded one from the files.
This should be corrected? The Idea is to return the corresponding object registered in ConfigurableManager, and if none (null), create a new one. What do you think?

Maybe they are implemented in a little different way from what the Config UI may need. Config UI must know which kind of configurable a Task (or other kind of objects) needs, so it can create the appropriate UI.

lfcnassif · 2022-11-04T20:32:12Z

This method (getConfigurables) is implemented in the AbstractTask descendants classes to return empty configurable objects. Not the loaded one from the files. This should be corrected? The Idea is to return the corresponding object registered in ConfigurableManager, and if none (null), create a new one. What do you think?

Maybe they are implemented in a little different way from what the Config UI may need. Config UI must know which kind of configurable a Task (or other kind of objects) needs, so it can create the appropriate UI.

Yes, this should be better. Currently they return a new instance that then is populated by ConfigurationManager. Reusing already existing ones should be better.

patrickdalla · 2022-11-07T11:26:46Z

Although the great majority of current AbstractTask implementations is instanced once, ScriptTask and PythonTask is instanced more than once, one for each script file. Maybe, other future AbstractTasks will permit to be instanced more than once.
So, the UI that exhibits a checkbox to install or uninstall an AbstractTask may not be the best.

@lfcnassif , what do you think? Do we keep the checkbox style task installation on UI, making some kind of exceptions only to script tasks that needs to be installed more than once, or should find another kind of UI?

lfcnassif · 2022-11-07T13:55:38Z

Hi @patrickdalla, this week I'm attending 7th DFEG Interpol Conference, so I may be slow to respond.

@lfcnassif , what do you think?

I think we should keep the checkbox list layout and write custom code to handle ScriptTasks and PythonTasks. Actually each Worker thread creates his own Tasks instances, so all of them are instantiated more than once on most machines. I think we should avoid putting the same Tak twice in the processing pipeline, that could be confusing.

I couldn't think on a more user friendly layout, but I'm open for suggestions.

patrickdalla · 2022-11-07T14:32:30Z

Right

patrickdalla · 2022-11-10T12:19:54Z

@thiagofuer I tried to push my updates to a new branch in your FORK, but it seems I don't have permission.

patrickdalla · 2022-11-10T12:25:24Z

I kept the table UI and created a tabbed panel interfaces to each task. The tabs implements an created abstract ConfigurablePanel class. I have implemented subclasses of this class for UTF8Properties, String and generic Bean objects. I have also implemented profile selection and new profile creation code. Not complete yet, though.

patrickdalla · 2022-11-10T13:11:53Z

Should distributed defined profiles be editable, removable?

lfcnassif · 2022-11-10T13:32:26Z

I kept the table UI and created a tabbed panel interfaces to each task. The tabs implements an created abstract ConfigurablePanel class. I have implemented subclasses of this class for UTF8Properties, String and generic Bean objects. I have also implemented profile selection and new profile creation code. Not complete yet, though.

Great!!! Thank you @patrickdalla! I haven't seen your code yet, but I thought about some dynamic UI to handle common property types automatically (e.g. String -> JTextField, Boolean -> RadioButton, Integer -> ScrollButton, Enum -> JCombobox, etc), so devs wouldn't need to always implement config panels, although they could override them, maybe you have also implemented that too...

Just a final comment (again I haven't seen your code, sorry if this does not fit) AbstractTasks should run on environments without screens, so no Swing or AWT classes should be instantiated from them.

lfcnassif · 2022-11-10T13:34:36Z

Should distributed defined profiles be editable, removable?

I think they should be read only (save button disabled), non removable and new profiles could be created based on existing ones. If anyone disagrees, please let us know.

thiagofuer · 2022-11-10T15:19:38Z

@thiagofuer I tried to push my updates to a new branch in your FORK, but it seems I don't have permission.

i sent you an invite to my repo access.

lfcnassif · 2024-06-18T15:55:51Z

Hi @marcus6n, how are your tests with this PR going?

marcus6n · 2024-06-18T16:02:48Z

Hi @lfcnassif, I'll finish the tests this afternoon and get back to you with the results.

marcus6n · 2024-06-18T19:28:39Z

The error that appeared in the log when running iped.exe no longer occurs.
In addition, the error that appeared when clicking on "Load case data" and then canceling has also been resolved.
Now the cases are being processed correctly, since previously they were stuck in "Starting ParsingTask".
Error in “Add a case to the list”

iped.app.home.newcase.tabs.caseinfo.CaseException: IPED-SearchApp not found.
        at iped.app.home.newcase.tabs.caseinfo.CaseInfoManager.validateCasePath(CaseInfoManager.java:21)
        at iped.app.home.opencase.OpenCasePanel.lambda$createTableButtonsPanel$0(OpenCasePanel.java:92)
        at java.desktop/javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
        at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
        at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
        at java.desktop/javax.swing.DefaultButtonModel.setPressed(Unknown Source)
        at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
        at java.desktop/java.awt.Component.processMouseEvent(Unknown Source)
        at java.desktop/javax.swing.JComponent.processMouseEvent(Unknown Source)
        at java.desktop/java.awt.Component.processEvent(Unknown Source)
        at java.desktop/java.awt.Container.processEvent(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
        at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
        at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

Cause: This error occurs when the system tries to validate the case path and cannot find the IPED-SearchApp application, even though the application is located within the case folder.

The case process is not finished.

iped.app.home.newcase.tabs.caseinfo.CaseException: The case process is not finished
        at iped.app.home.newcase.tabs.caseinfo.CaseInfoManager.validateCasePath(CaseInfoManager.java:23)
        at iped.app.home.opencase.OpenCasePanel.lambda$createTableButtonsPanel$0(OpenCasePanel.java:92)
        at java.desktop/javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
        at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
        at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
        at java.desktop/javax.swing.DefaultButtonModel.setPressed(Unknown Source)
        at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
        at java.desktop/java.awt.Component.processMouseEvent(Unknown Source)
        at java.desktop/javax.swing.JComponent.processMouseEvent(Unknown Source)
        at java.desktop/java.awt.Component.processEvent(Unknown Source)
        at java.desktop/java.awt.Container.processEvent(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
        at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
        at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

Cause: This error occurs when the system tries to validate the case path, but the process associated with the case has already been completed.

PS: @lfcnassif, can you check and confirm these errors I found?

lfcnassif · 2024-06-18T23:35:50Z

Thanks @marcus6n for testing. Unfortunately this week I'm with no available time to work on this. @patrickdalla could you take a look at the errors pointed by @marcus6n?

…he new UI

… to multicase

lfcnassif · 2024-06-29T21:20:22Z

@marcus6n, I just fixed error 5 and other issue when opening multicases. Error 4 didn't happen to me.

lfcnassif · 2024-06-29T21:46:00Z

I would like to discuss with other DEVs the case information fields displayed to the user:

I know just the output folder is required, but I think there are too much fields, making that panel annoying to fill. What would be the minimum fields to display in this step (the user may complement them when creating the report):

Examiner
Case Number (or Name, or ID)

Any others?

wladimirleite · 2024-06-29T21:49:14Z

Examiner and Case ID.

…ning

…g as admin

…ng French

lfcnassif · 2024-06-30T20:52:23Z

Stopping for today. Documenting to don't forget:

Every time a task is enabled or disabled in the main task table selection, a NPE is printed:

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
        at java.desktop/javax.swing.plaf.basic.BasicTableUI$Handler.setValueIsAdjusting(Unknown Source)
        at java.desktop/javax.swing.plaf.basic.BasicTableUI$Handler.mouseReleased(Unknown Source)
        at java.desktop/java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
        at java.desktop/java.awt.Component.processMouseEvent(Unknown Source)
        at java.desktop/javax.swing.JComponent.processMouseEvent(Unknown Source)
        at java.desktop/java.awt.Component.processEvent(Unknown Source)
        at java.desktop/java.awt.Container.processEvent(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
        at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.Component.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
        at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
        at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

If I enable OCR or some other tasks and create a new profile, processing fails at the beginning with:

java.lang.ArithmeticException: / by zero
	at iped.engine.core.Statistics.printSystemInfo(Statistics.java:409) ~[iped-engine-4.2-snapshot.jar:?]
	at iped.engine.core.Manager.process(Manager.java:246) ~[iped-engine-4.2-snapshot.jar:?]
	at iped.app.processing.Main.startManager(Main.java:193) [iped.jar:?]
	at iped.app.processing.Main.execute(Main.java:255) [iped.jar:?]
	at iped.app.processing.Main.main(Main.java:323) [iped.jar:?]

Enabling some tasks and saving a new profile, it sometimes still freezes on ParsingTask initialization

…lternate string for "auto" as is used for parameter num threads for LocalConfig.

patrickdalla · 2024-07-01T21:01:35Z

"Every time a task is enabled or disabled in the main task table selection, a NPE is printed:"
this was solved by commit [b3ef5c9]

patrickdalla · 2024-07-01T21:03:41Z

"If I enable OCR or some other tasks and create a new profile, processing fails at the beginning with:"
This didn't seem to be a problem of OCR config, but of number of threads configured as "default", which wasn't being correctly recognized. If I am right, it was solved by [18711ab].

lfcnassif · 2024-07-01T21:14:14Z

this was solved by commit [b3ef5c9]

Thanks @patrickdalla!

This doesn't seemed to be a problem of OCR config, but of number of threads configured as "default", which wasn't being correctly recognized. If I am right, it was solved by [18711ab].

Yes, it seemed an issue with LocalConfig->numthreads parameter not being handled/saved correctly.

gfd2020 · 2024-07-04T21:05:15Z

I have some suggestions.

Place a parameter in LocalConfig.txt to save the default directory for case output folder when clicking the directory choice button.
Another parameter to save the default directory where the images will be chosen for processing ( Add file/folder button).
I have these two parameters in the custom interface that I use and they are very useful.

Fix buttons with icons without tooltip...

Add the option to choose "portable" processing...

The "Evidence Details" and "Choose the disk to be processed" windows should be modal...

lfcnassif · 2024-07-05T01:11:21Z

I have some suggestions.

Thanks @gfd2020.

Place a parameter in LocalConfig.txt to save the default directory for case output folder when clicking the directory choice button.
Another parameter to save the default directory where the images will be chosen for processing ( Add file/folder button).
I have these two parameters in the custom interface that I use and they are very useful.

Yes, opening the dialogs always in user home directory is annoying, I noticed that. But I would save those last selected folders in a new file in user.home/.iped folder.

Add the option to choose "portable" processing...

This is important.

Unfortunately I'm not sure if I'll have time to implement those enhancements, since I'm becoming the head of the central digital forensic lab in my agency. I'll be on vacation on the next 2 weeks and I will try to finish the very minimum for 4.2.0 version, because it will be impossible to accomplish that during my work hours from now on...

If you have available time to help us finish this PR (we need more tests and more tests, and to finish the UI translation to all 6 supported languages) that would be appreciated very much.

gfd2020 · 2024-07-05T19:56:53Z

If you have available time to help us finish this PR (we need more tests and more tests, and to finish the UI translation to all 6 supported languages) that would be appreciated very much.

hi, @lfcnassif .

I found this GUI test automation tool.
Is it viable to use to test the GUI?

https://github.com/dotxyteam/SwingTestingToolkit

lfcnassif · 2024-07-06T00:35:20Z

hi, @lfcnassif .

I found this GUI test automation tool. Is it viable to use to test the GUI?

https://github.com/dotxyteam/SwingTestingToolkit

Hi @gfd2020. I'm not sure, I never used that project. UI testing is a bit difficult to automate and to cover all user interation possibilities, but what I meant was just doing more manual testing with more features/options combinations.

gfd2020 · 2024-08-26T18:14:56Z

I found more of bugs/suggestions:

Sometimes the action of "Deleting" a profile only deletes it from the profile list but does not delete the ".ipedprofile" file. This causes two bugs. Firstly, it is no longer possible to create a profile with this deleted name and when opening the interface again the deleted profile reappears.
The interface should not allow the creation of a profile with the same name as those that come by default, as the name of the profile will be repeated in the list.
The interface must not allow the creation of a profile with an empty name.
If a profile name is longer than 245 characters, java.io.FileNotFoundException exception occurs.
Characters prohibited for file creation must not be accepted in the profile name, java.nio.file.InvalidPathException exception occurs . Ex.: \ / : * ? ! < > |

lfcnassif mentioned this pull request Oct 31, 2022

Parse BMC cache #1302

Open

This was referenced Nov 3, 2022

Copy embedded JRE to user home and reuse it #1410

Closed

Splash Screen (#1416) #1420

Merged

wladimirleite added a commit that referenced this pull request Nov 4, 2022

'#1416: A third design option, using the icon from PR #1341.

a4b8d5a

lfcnassif added 5 commits June 29, 2024 15:50

Merge branch 'master' into Config_UI

b00e387

'sepinf-inc#23: create a new iped-gui.exe to make users aware about t…

72d9d25

…he new UI

'sepinf-inc#23: update code to accept adding cases from last versions…

d782418

… to multicase

'sepinf-inc#23: don't allow adding cases from iped v3

50ec657

'sepinf-inc#23: fix multicase opening

65578d7

lfcnassif added 6 commits June 29, 2024 21:26

'sepinf-inc#23: removes unnused class

236919f

'sepinf-inc#23: update iped-gui.exe to not open the console while run…

60c3d76

…ning

'sepinf-inc#23: organize imports and code formatting

ed5a187

'sepinf-inc#23: warn and avoid adding physical drives when not runnin…

f9c3594

…g as admin

'sepinf-inc#23: update localization files with missing props, includi…

11c1097

…ng French

'sepinf-inc#23: removes UFD from supported types, add 000 and 001

501c138

patrickdalla added 3 commits July 1, 2024 14:18

'sepinf-inc#1341 Enqueue onChange procedure in Swing thread to avoid NPE

b3ef5c9

'sepinf-inc#1341 Corrects autoCalcSpinner to accept "default" as an a…

18711ab

…lternate string for "auto" as is used for parameter num threads for LocalConfig.

'sepinf-inc#1341 Avoid NPE when JEP is to initialized.

adf72ec

#23 UI 4 config proc #1341

Are you sure you want to change the base?

#23 UI 4 config proc #1341

Conversation

thiagofuer commented Sep 28, 2022

lfcnassif commented Sep 28, 2022

patrickdalla commented Nov 1, 2022 • edited Loading

thiagofuer commented Nov 1, 2022

lfcnassif commented Nov 1, 2022

thiagofuer commented Nov 1, 2022

patrickdalla commented Nov 1, 2022

patrickdalla commented Nov 1, 2022 • edited Loading

lfcnassif commented Nov 1, 2022

patrickdalla commented Nov 1, 2022

patrickdalla commented Nov 1, 2022

lfcnassif commented Nov 1, 2022

thiagofuer commented Nov 1, 2022

patrickdalla commented Nov 1, 2022 via email

lfcnassif commented Nov 4, 2022

patrickdalla commented Nov 4, 2022 via email

patrickdalla commented Nov 4, 2022

lfcnassif commented Nov 4, 2022

patrickdalla commented Nov 7, 2022

lfcnassif commented Nov 7, 2022

patrickdalla commented Nov 7, 2022

patrickdalla commented Nov 10, 2022

patrickdalla commented Nov 10, 2022

patrickdalla commented Nov 10, 2022

lfcnassif commented Nov 10, 2022

lfcnassif commented Nov 10, 2022 • edited Loading

thiagofuer commented Nov 10, 2022

lfcnassif commented Jun 18, 2024

marcus6n commented Jun 18, 2024

marcus6n commented Jun 18, 2024 • edited Loading

lfcnassif commented Jun 18, 2024

lfcnassif commented Jun 29, 2024

lfcnassif commented Jun 29, 2024

wladimirleite commented Jun 29, 2024

lfcnassif commented Jun 30, 2024

patrickdalla commented Jul 1, 2024

patrickdalla commented Jul 1, 2024 • edited Loading

lfcnassif commented Jul 1, 2024

gfd2020 commented Jul 4, 2024

lfcnassif commented Jul 5, 2024

gfd2020 commented Jul 5, 2024

lfcnassif commented Jul 6, 2024

gfd2020 commented Aug 26, 2024

patrickdalla commented Nov 1, 2022 •

edited

Loading

patrickdalla commented Nov 1, 2022 •

edited

Loading

lfcnassif commented Nov 10, 2022 •

edited

Loading

marcus6n commented Jun 18, 2024 •

edited

Loading

patrickdalla commented Jul 1, 2024 •

edited

Loading