This will now at least load. Looks like there is still a js error which is completely beyond me.
@Fedik @dgt41 any help appreciated

A couple notes:

Because of an architectural decision in 2013, the remote server is rendering the markup shown in the backend UI. Without re-engineering things, markup for the 4.0 template will need to be added to that repo and we'll need to use something to communicate the right markup to render (we already send the Joomla version so we can probably use that).

All other media assets (CSS/JS) are self contained in the plugin. So feel free to do what you please with those.

Thanks @mbabker

For now I would just like to be able to get rid of the javascript errors

@brianteeman I pushed ec441a5 onto this PR doing a round of updates for the plugin (tried to do it as a PR to your branch but GitHub kept 404'ing on the save action).

@brianteeman Check brianteeman#69 as that merges @dgt41 initial JavaScript with me debugging things to get it working. It ain't pretty but it doesn't have any JS errors now.

Years ago I re-wrote the plugin, but it couldn't be used because the JED API wasn't able to handle request as needed. It was and it is a stupid idea to render markup on the remote server. We shouldn't do this misstake again.

@mbabker -thanks. I get those 404 sometimes as well never tracked it down

@rdeutz I remember as I tested it for you. As far as I know the JED API hasnt changed. For now I just want to get it working as is and then its in a working position and people can improve upon it

@dgt41 thanks for your JS and thanks @mbabker for converting it into a PR

So now it seems to be working and we just have markup issues to resolve. I am not too familiar with the IFW server and what is the most sensible way forward now. Any suggestions?
[ ] Convert markup served by IFW server to bs4?
[ ] Add bs2 css to the plugin and keep the server code the same?

I started https://github.com/joomla-extensions/install-from-web-server/compare/j4-support to deal with the UI changes (the plugin already sends the CMS version information with each request, I'm just using that to make decisions on which templates to load now). The grid views are functional, need to work on the list views and single extension view next. I'm basically doing a quick and dirty BS2 -> BS3 -> BS4 type migration to get the markup sorted with default elements, someone with an eye for design can make things prettier later.

@mbabker ok thats great - in that case this can probably be merged for now and then improved upon when that work is completed?

We shouldn't do this misstake again.

@rdeutz I think when we are in a state where we can rewrite the architecture, we should update everything all at once (the standalone plugin for 3.x and the core plugin in 4.x). Let's not work ourselves into a point where we're maintaining two versions of the architecture for the next 3 years. So for now, the "easiest" thing is to keep using the same architecture (with good and bad decisions involved in it) and adapt for the new major version.

@brianteeman For now I would call this a "ready to merge" state as the plugin itself is now fully functional and any further changes are just part of the rest of the refactoring of the CMS codebase for 4.x (i.e. the JavaScript decoupling from jQuery) or the work is happening outside the CMS and doesn't block work here.

thanks for minifying the script - it was on my todo list but i forgot after drowning my sorrows as a result of a meeting tonight

Check and merge brianteeman#70 please. Does a lot of the cleanup stuff that needed to happen anyway (I finished the server side layouts then figured I'd do another round of effort on the plugin to get it up to spec).

thanks @mbabker all merged and crossed of my todo list for tomorrow

Shooting from the hip, the only real work left here before things are "clean":

• Get the rest of the initialization JavaScript out of the document head and into the client.js file
• @dgt41 favorite framework decoupling
• Handing the server side layouts over to the UI team for improvements (https://github.com/joomla-extensions/install-from-web-server/compare/j4-support is feature complete as far as migrating to support both 3.x and 4.x goes and having all layouts in place (minus the unused advanced search layout), the server generated markup is almost exclusively BS4 at this point without any additional styling that the 3.x version has with the client.css file though).

Then at some point whenever JED supports it we should probably update the server's API queries into the JED to filter out extensions that aren't compatible with whatever major version is in use.

my 2c would be to merge now and do further improvements later

Agree wholly. I'll merge up the layout work to the live server after this PR is merged too so it's not completely busted.

thanks - i plan to check the server stuff tomorrow

@mbabker I started to update the css but then saw you hadnt finished with the layouts/markup on the server so I wont do anymore until thats finished

@wilsonge Can you merge this please. Its very hard to test unless you create your own IFW server and it will help to make the testing of the IFW changes if this is merged - thanks

I just pushed up the work for the layout changes. So now with this PR applied you should get the J4 optimized UI.

Thanks @mbabker

Tomorrow I will try and push some fixes I have locally for the server.

Merged as requested :)

Thanks!!