-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve UI #12
Comments
Lets try to show only the meaningful options for the respective target. |
Maybe we could implement some kind of profile base on the default settings eg, config/defaults/*.h |
Hey man I've been using your tool for some time and I love it. Do you mind if I reimplement the UI using a UI framework like Bootstrap or Foundation? If you agree, I can work on it when I go home. Bootstrap plays nicely on different screen sizes and has a very "familiar" look to a lot of users: http://getbootstrap.com/ |
You can surely do. I did not used any UI framework to make it simple. A few ideas:
I can surely help. |
I started the bootstrap redesign branch. Have a look at let me know what you think so far: https://github.com/avindra/ipxe-buildweb/commit/fb45d4c46eab8329fb6b26edbc9d844fa6a2fb23 edit: btw, I couldn't test much with the PHP stuff. I was having trouble getting the apache config right |
Looks nice! |
Check out the latest changes, if you like I'll make a PR |
The UI is now using bootstrap but there is no other improvement. |
It was a misunderstanding on my side. I thought that PXE image support could be added to ipxe.efi (in a way that also the PXE functionality which exists in non-UEFI BIOSes would be added to ipxe.efi) so that the new UEFI-only box can boot the same way as all our other existing non-UEFI BIOS boxes. My misunderstanding was encouraged by the fact that https://rom-o-matic.eu/ has select buttons for PXE stack/menu support AND for PXE image support also for the output format "EFI PXE bootstrap 64-bin (.efi)".
Thus (in case I want to use iPXE for the UEFI-only box) I have to always change the (automatically created pxelinux based) DRBL configuration (DHCP server config, ipxe.conf script...) whenever I change the DRBL setup (e.g. adding/removing DRBL client...)
I guess for simplicity the select boxes are the same for all build targets (even if they do not make sense for some of them) which allows to have only one static page for all targets. Showing only the meaningful options for the respective target would mean to implement a context depending dynamically created web page which would update whenever another build target is selected.
So I would not call it an error but rather a "nice-to-have" feature.
The text was updated successfully, but these errors were encountered: