Log in

View Full Version : MeXgui cross platform Megui port in development


Pages : 1 [2]

microchip8
9th May 2014, 17:19
I think the goal of this project is to create a cross-platform (Windows, Linux, OS X, etc) port/rewrite of MeGUI, not specifically a Linux/Unix one ;)

So, ideally, it should run equally well on all supported platforms. And it shouldn't matter which platform is used for development...

Totally forgot about that. Always thought MeXgui was targeted at Linux/UNIX only ;) (maybe because of the X in its name referring to UNIX-like systems)

Excuse my mistake :D

Jeroi
9th May 2014, 17:45
Totally forgot about that. Always thought MeXgui was targeted at Linux/UNIX only ;) (maybe because of the X in its name referring to UNIX-like systems)

Excuse my mistake :D

It stands for:

Mencoder Cross Gui. But I think the Mencoder part is just for legacy reasons.

Jeroi
12th May 2014, 11:07
Here is my current work with Encoder:

http://but.fi/t/2tb (http://but.fi/2tb)

I am doing this as separate dialog atm to debug of my code for it. Atm job's are created manually without SQL fetching and other way it is similar code than in Encoder.cpp will hold. It uses foreach(job c, joblist) and makes dynamic updating to the list. Also I added dynamic combobox to the Status. I will add direct editable options for all values like encoder and outputname.

Also since Qt support translations I am doing code that supports program translating. MeXgui will have option to add translating po files to make it native language for user.

Edit:

Finally got my code to work wiht TreeView. Now the jobs are printed as child also if they belong to group job. Added also by default the colum size is modified as how width is the data in colums. So biggest width rules the treeview colum size.

http://but.fi/t/2tc (http://but.fi/2tc)

Jeroi
12th May 2014, 23:38
I hade some troubles with the queve that there was no easy method to select a job. I found solution at last to add sql Id and subId to the jobQueve and make those columns hidden. Now I can fetch the id and subId from those colums if I want to make SQL joblist edit or delete and encoder worker methods via sql id's. Methods always deletes stuff from sql joblist first and then see if sql delete worked then only removes job from queve. So I am doing all the way dynamic updating to sql table and reading the table to view the jobqueve. ID's makes sql handling so easy.

macromizer
13th May 2014, 02:05
Just so you know since you've misspelled the term both in the GUI text in your screenshots and in your posts the term is queue (http://www.merriam-webster.com/dictionary/queue) not queve.

Jeroi
13th May 2014, 16:12
Just for giggles, playing arround with try catch block and demostartion of sql throw error when there is no sql database available at program root:

http://but.fi/t/2td (http://but.fi/2td)

Jeroi
13th May 2014, 23:10
Compared to MeGUI job handler that has quite bad line handling the MeXgui jobGueue will handle bit differently:

- When using move up, move down the encoder will move whole Job to up or down with all child jobs intact.
- Unlike megui moving child jobs are not allowed. Only toplevel Jobs may be moved up down. It does check if your selected line is child then it choses parent and moves it up or down.
- By default whole job is deleted. This is because normally you will not delete anything on the Job. How ever I may allow audio line removing if there is more that 1 audio tracks in future.

At the moment right control buttons are working. Moving to start threading encoding. First encoding thread is handler that starts child threads that talk with the handler and handler will controll jobQueve signals and slots.

Edit:
I will drop JobX names and add Jobname box to current meXgui input tab. By default it Fetches job name from from sql but user can spesify what ever jobname they want. Till example:

Jobname Naruto10 and jobqueve uses those names as job name. since all jobs have unique id anyway and subId for childs all handling is used with id's anyway.

djcj
28th May 2014, 02:44
AvxSynth and Vapoursynth didn't work very well on Linux when I was testing them, so working with avs2pipemod on OSX and Linux might be more reliable, and you could use exactly the same plugins on all systems. An automated installation could be done by extracting a pre-configured prefix (including plugins and other things) and then use winetricks to install vcrun6:
#!/bin/sh
mkdir -p "$HOME/.local/share/wineprefixes" &&
cp -rf avisynth_260_alpha5 "$HOME/.local/share/wineprefixes" &&
./winetricks prefix=avisynth_260_alpha5 vcrun6sp6

Jeroi
21st January 2022, 16:35
Hi I run softwarer company nowdays and my time has not been in developing this for years.

What should we start change:
Avisynth++

What more? I think source can compile to x64 when written working in qt. How ever megui has improved surely lot...