Rebug Team needs your feedback about the inclusion of webMAN/webMAN-MOD In future CFW releases

Would you prefer the next Rebug release to include...

  • Total voters
    66
  • Poll closed .
lol too funny

yeah I guess you're right...just wishful thinking , and I didn't realize about the whole collection thing.

im sure whatever comes out will be fine PLUS we already have the 4.81 with 7.5 that have wMM so people can just use that to get their wMM in a cfw fix if they need to
 
I voted for webman mod. But after reading the replies. It makes sense if it wasn't included, because of it getting updated so much. But really it is not hard to run the installer, either way.
 
bguerville said:
I suggest you learn how to use webMAN-MOD's features. Read the OP of the wMM General Information thread in this forum.
Ps3netsrv is supported by all wMM editions except light edition. Also there are options to configure in the setup page of course, you cannot expect wMM to automatically detect & list your ps3netsrv games without first enabling the feature, providing the ps3netsrv ip address & used port!
WMM is not AI! Lol
Click to expand...
Really, did I say anywhere that I expected it to just work or being an AI, lol. I have read the tutorials several times went step by step set it up on the "setup page" enabled it put my ip address in several times, pointed it to my shared folder, tried changing addresses, wifi and wired connections, uninstalled multiman, tried different versions of WM, and so on, but for some reason, that might be something I'm doing or not doing, it doesn't work!
 
I would keep them separate. leave it to the homebrew dev's to keep it compatible to yours and others cfw.
 
williams1978 said:
Really, did I say anywhere that I expected it to just work or being an AI, lol. I have read the tutorials several times went step by step set it up on the "setup page" enabled it put my ip address in several times, pointed it to my shared folder, tried changing addresses, wifi and wired connections, uninstalled multiman, tried different versions of WM, and so on, but for some reason, that might be something I'm doing or not doing, it doesn't work!
Click to expand...
If you want to continue this conversation or get help, post in either the wMM or ps3netsrv support thread. You must be doing something wrong otherwise the forum would be full of posts similar to yours! In the past 6 months I only remember 2 or 3 guys with ps3netsrv issues, it turned out the users did something wrong everytime...
 
I vote for webMAN-MOD. Whatever the latest build is at the time of Rebug's release will suffice..
Then we could just run the updater pkg if we want. It's not like we have to update it but more options is a beautiful thing.
So including my other vote at the Cobra poll. It would be Cobra enabled, WMM enabled by Default.
I never had a problem with the fan control and use it religiously..
My ps3 slim is about 11 years old and I believe fan control contributed to it's longevity.
 
This poll i did not place a vote as my option is not there.

Have a system that can install support all plugin slots. or no plugins at all.(but i like to see all plugin slots supported.) (i know i already stated that one in this thread ;p )

To add: I think with at least Rebug CFW with toolbox it could be much simpler for plugins for users. Would also think it could be cool to have 2 modes on rebug toolbox (@Joonie & @habib). Maybe like Normal & Advance modes, (like how in MM there is multiMAN mode and mmCM mode for example.) Where the advanced options are hidden until activated. I think sometimes people jus get overwhelmed by the amount of options and the amount they do not understand. having a simple mode i think could help people understand the basic better and they can go from there, instead of wondering what is basic and what is advanced (as a noob will not know in reality)
 
STLcardsWS said:
This poll i did not place a vote as my option is not there.

Have a system that can install support all plugin slots. or no plugins at all.(but i like to see all plugin slots supported.) (i know i already stated that one in this thread ;p )

To add: I think with at least Rebug CFW with toolbox it could be much simpler for plugins for users. Would also think it could be cool to have 2 modes on rebug toolbox (@Joonie & @habib). Maybe like Normal & Advance modes, (like how in MM there is multiMAN mode and mmCM mode for example.) Where the advanced options are hidden until activated. I think sometimes people jus get overwhelmed by the amount of options and the amount they do not understand. having a simple mode i think could help people understand the basic better and they can go from there, instead of wondering what is basic and what is advanced (as a noob will not know in reality)
Click to expand...

So about your plugin manager, you're basically asking to see if we can include all public vsh plugins and let users to install them individually on demand without having it manually by adding it to the boot_plugins.txt or pkg (like vsh menu and wMM) to install?

Slot0 is reserved for back up managers so it's better to leave it empty.

However 1-6 are all available and currently I use slot1 for the integrated webMAN MOD


Sent from my iPhone using Tapatalk
 
Joonie said:
So about your plugin manager, you're basically asking to see if we can include all public vsh plugins and let users to install them individually on demand without having it manually by adding it to the boot_plugins.txt or pkg (like vsh menu and wMM) to install?

Slot0 is reserved for back up managers so it's better to leave it empty.

However 1-6 are all available and currently I use slot1 for the integrated webMAN MOD


Sent from my iPhone using Tapatalk
Click to expand...

Including all plugins itself might not be the most ideal.

I would think the easiest and i think the most effective would just be allowing rebug toolbox to read and write to boot_plugin.txt

If these plugins are active.
hdd0/plugins/psnpatch.sprx
hdd0/plugins/ps3lock.sprx

Then Rebug Toolbox shows
Slot 1 - psnpatch.sprx (reading the end file name from the txt file)
Slot 2: ps3lock.sprx
Slot 3: Empty
Slot 4: Empty
Slot 5: Empty
Slot 6: Empty

(then for Empty slots, have an option when plugins are placed in a "plugin folder" they will then show the file names and you can activate/deactivate those plugin into a slot.)
 
I imagine something like Buttons in the toolbox with static links to the latest versions of each plugin. This way they are not exactly included but they are always available to be enabled. The file at the end of each static link could be controlled by the dev of that particular plugin. So the onus is on the dev of the plugin to make/keep the available file compatible with the latest FW rather that the other way around. I know its a lot to expect, just dreaming :distant:
 
STLcardsWS said:
Including all plugins itself might not be the most ideal.

I would think the easiest and i think the most effective would just be allowing rebug toolbox to read and write to boot_plugin.txt

If these plugins are active.
hdd0/plugins/psnpatch.sprx
hdd0/plugins/ps3lock.sprx

Then Rebug Toolbox shows
Slot 1 - psnpatch.sprx (reading the end file name from the txt file)
Slot 2: ps3lock.sprx
Slot 3: Empty
Slot 4: Empty
Slot 5: Empty
Slot 6: Empty

(then for Empty slots, have an option when plugins are placed in a "plugin folder" they will then show the file names and you can activate/deactivate those plugin into a slot.)
Click to expand...

So in order to do that, we have to add a column with the detection for *.sprx to show the list of sprx files located in the plugin folder and a side menu for slot sections so every time you select the plugin you want to add, it will pull sidemenu for available unused slots to use.

And after assigning the plugin to the slot then let it reboot when exiting so it would apply the newly added plugins
Sounds like doable.


Sent from my iPhone using Tapatalk
 
Joonie said:
So in order to do that, we have to add a column with the detection for *.sprx to show the list of sprx files located in the plugin folder and a side menu for slot sections so every time you select the plugin you want to add, it will pull sidemenu for available unused slots to use.

And after assigning the plugin to the slot then let it reboot when exiting so it would apply the newly added plugins
Sounds like doable.


Sent from my iPhone using Tapatalk
Click to expand...
Just a couple of picky details probably you thought in them but anyway...

It could happen that the user has a path in boot_plugins.txt for a .sprx file that doesnt exists
To solve this problem you can delete its path before doing anything else... after checking for the .sprx files you need to compare them with the paths in boot_plugins.txt and if the problem im mentioning is detected then delete the incorrect path

Also, because you have to prepare some kind of menu to display all slots, and the user could add plugins, then remove, then he is not happy and deletes them again to reorder them etc...
Are so many changes... so to avoid rewriting the file boot_plugins.txt lot of times is better to add at bottom of the menu something like "save changes and exit", this way the file boot_plugins.txt is written only 1 time

At coding i think could be made by using an string array with the 8 cobra slots and store in it the paths temporally until the user clicks in the "save and exit" button then you save the array in the boot_plugins.txt

Edit:
Hmmm, if you are not going to display the contents of the original boot_plugins.txt then there is no need to make the comparison at beginning
Is easyer to rewrite the contents of boot_plugins.txt completlly (never minds what there was inside it)
Only scenario where could be needed a check to avoid unneeded writes is if the resulting list is the same than the original
Lets say an user enters in the menu... does lot of changes and at some point he forgets how it was originally but he is configuring it exactlly as like the original (without noticing) and he clicks in the "save and exit"
Then the comparison could come in handy because is not needed to modify the file boot_plugins.txt

Also... is the same scenario if an users enters in the menu... doesnt changes anything... and clicks in the button "save and exit"... in this case there is no need to rewrite boot_plugins.txt

Dunno, i think this way is better, but this comparison is not much needed anyway, im just being picky
 
Last edited:
I just remember time ago @Zar was talking about a plugin selector menu he was going to add in managunz, im quoting him to join the conversation, maybe he wrote it already


*Another annoying scenario (for display purposes) is if the user has more .sprx files than the cobra slots... lets say 10 .sprx files
 
Last edited:
sandungas said:
I just remember time ago @Zar was talking about a plugin selector menu he was going to add in managunz, im quoting him to join the conversation, maybe he wrote it already


*Another annoying scenario (for display purposes) is if the user has more .sprx files than the cobra slots... lets say 10 .sprx files
Click to expand...
wm_vsh_menu.sprx already has a plugin manager. Not sure if it does exactly what you have in mind but here is the code anyway..
Main algorithm begins line 1558
https://github.com/aldostools/webMAN-MOD/blob/master/_Projects_/vsh_menu/main.c
And a screenshot
0e560ce3a71af7b0c9b95ac7a697399a.jpg

The only thing I would add to it obviously is the slot related information but it's a trivial addition to make....
After that, It can be modified to suit other needs but the main elements are already in place in any case...
 
Last edited:
I was thinking in something like the web interface of webman, like a table with the cobra slots as the rows of the table and to select the .sprx file with left/right
next-->next--->next--->next--->next--->nothing
An option for "nothing" and the others to show the .sprx files alphabetically
 
A bit like the sprx management in the PS3MAPI pages but with extra functionalities?
Like this part
12e2f55a94a4a2511e97279638bb9cca.jpg

And this page
185fec40761c5321aa7b45e765437621.jpg

I suppose those "test" pages don't get much attention & could be vastly improved...
 
Last edited:
@sandungas
Yeah, i want to do it. But it's not done yet, it will be probably in global menu.
Here how it will work. It will list all sprx present inside the folder "/dev_hdd0/plugins" then it will check the txt file to display if the plugin is enabled or disabled. The user will be able to enable / disable it.
If the folder doesn't exist it won't display this menu. It's up to the users to create it.

Other plugins that are outside this folder but inside the txt file won't be supported by this interface.
But the user still have the possiblity to manage them through the FileManager. You can add/remove an sprx in the option when you select a sprx file, this option is already included.
 
You must log in or register to reply here.

Similar threads

Back
Top