vuengine / vuengine-studio Goto Github PK

When opening multiple VUEngine Studio windows, pressing the build button only works properly in one of them (it seems that the last opened one). Closing all but the original window doesn't fix the issue and VES has to be restarted for the building to work again.

Store last x builds, e.g. in build/archive/output_20210910221805.vb.

Also store logs and make those inspectable in build widget.

Add quick links to launch ROMs in emulator.

After a build succeeded, determine the output ROM size and display it in the build widget.

Create a widget to ease working with flash cart configs. Holds a list of flash cart configs with "+" button.

Button to reset to default as well on top.

Aborting builds during preprocessing can lead to an inconsistent state of the build folder, in which builds are no longer possible. Thus, the build folder should be cleaned when a build is aborted during preprocessing. To not unnecessarily clean, and thus increase the build time on next run, it should probably be checked if any files have been actually processed during any of the preprocessing steps.

• Fix filepath issues
• Get build working
• WSL support, include Linux gcc
• Get packaging working
• Fix path problems in "New Project" dialogue
• Test extensively

Add a Virtual Boy themed red and black high contrast theme for teh lulz.

extensions/vuengine-studio-extension/src/build/browser/ves-build-service.ts:124

Add option to include the configured VUEngine-Core, VUEngine-Plugins and user plugin libraries in the workspace, without the need for a workspace file.

Preference should be set to false by default, since this is not neccessarily interesting for regular users.

Allow to filter the build widget by a search word. We should be able to get that feature almost for free by refactoring the build log to be a Tree.

• Rumble Pack Test Tool to test drive effects and effect chains.
• Status bar items when connected, links to test tool
• Additional custom editor for effects, tailored for VUEngine rumble implementation

Hasn't been tested on Linux so far.

• Set up Linux VM for building
• Test extensively

• Add custom editors.
• Generate forms from JSON schema and generate code on save
• Include version numbers in JSON schema files.
• Need a mechanism to automatically update project's config files according to engine's schema files.

• Color code on warnings - Color progress bar yellow once a warning appeared in the log
• Introduce new status "Build successful (with warnings)"?
• Automatically open widget when a build failed

Investigate why build times are much higher in VES than they are when building through the terminal.

Might have to do with file watchers, output parsing or such?

Get VES to compile for, and run in, the browser. So we could potentially offer a web-based version.

Update all included templates.

• VUEngine Barebone
• VUEngine Platformer Demo
• SPONG
• VUE-MASTER

Almost done, although not everything could be removed, yet.

• Remove Preferences->Extensions->Debug (-> bindDebugPreferences)

Implement image conversion via grit using individual image config files.

Include option to specify storage area: "ROM Space" (default) or "Expansion Space".

Auto convert when an image or a .image.json file has been changed.

e.g. trailing line on Mac, none on Windows

Implement system notifications for long running processes like building or flashing.

We don't have a way to generate custom editors from JSON schema files, yet and no code generation mechanisms either. But we'll need to implement something to generate config.make, otherwise the plugins sidebar won't do anything useful.

Check if color variables should be introduced for all custom widgets?

Add screenshot functionality to the emulator that lets you capture the screen and then allow you to crop and annotate the image for faster communication in dev teams.

marker.js?

msys archive is huge, we can pobably shave a lot of unnecessary files from them.

Bring back custom zoom logic from early VUEngine Studio version. Prevent too high or low zoom levels.

• Queueing is not working correctly
• Sometimes ROM is present, but not detected by emulator. In that case, the build starts instead.
• Emulator is not persisting save data
• Focus gets lost when emulator is dragged to sidebar
• Disable toolbar while emulator is loading/starting
• Keys bindings must only trigger when emulator is focused
• Introduce global theia-button::active state (better feedback when clicking a button)
• If the run command is executed when the emulator is already active, it should be opened and reset.

• Use custom WidgetOpenHandler, like plugins widget, to open docs by URI.
• Highlight currently opened doc page in tree
• Add "collapse all" command to tab tool bar

Create a widget to ease adding new custom emulator configurations. Holds a list of emulator configs with "+" button.

Each config has these fields:

• Name: text input, required.
• Path: text input with file select button (like on new project dialog), required
• Args: text input, preset with value "%ROM%"
• Default: checkbox, checking it will uncheck all other config's default checkbox

Name, Path and Args go into emu config, default goes into default emulator config.

On top of list, the Build-In Emulator is listed. It has a default checkbox as well. It cannot be removed.

Shows a notice on top when emulator preferences have changed with a button to resync the widget.

• Change .theia-workspace to a custom name
• Change file dialog (and other) labels accordingly

Note: This ticket is still blocked, because the respective parts of Theia still have to refactored to be changeable via DI.

Offer dialog to create a new plugin based on a barebone plugin.

Can't name the application "VUEngine Studio", or otherwise the build is not working, due to the whitespace.

Likewise, building won't work if the user installs the application to any folder that contains whitespaces. Same problem probably occurs when trying to build a project that's inside a path containing whitespaces.

Implement inline Auto Updates via Electron update service.

• Get code signing and notarizing working on Windows and Mac
• Implement application dialogs
• Tie up Github releases

Folder-scoped preferences (e.g. preferences in [workspaceRoot]/.vuengine/settings.json) do not get recognized by our custom code.

We might have to explicitly factor these in as in: https://github.com/eclipse-theia/theia/blob/d7cdb85c1793ae5e4af8d05da249a2dcea606da2/packages/task/src/browser/task-configuration-manager.ts#L65

• Allow to flash to specific carts (show flash button for each cart if there's more than one)
• Update to latest hfcli and direct-to-flash programming
• Parse HF32 progress
• HF32 and HyperBoy port detection
• Refactor pad function to use FileService instead of fs
• Display warning and skip flashing if cart is too small to hold ROM
• New events for flash start/succeed/fail
• Tabbar decorators for above events + number of connected carts
• Bug: Losing flash progress state when reconnecting any cart
• Generalize parser and expose to flash carts config
• Add support for additional actions. Can be useful for HyperBoy's save/load savegame feature.
• Bug: Not flashing after being queued.
• Bug: If one flash cart fails while another one starts, the overall process breaks
• Allow to select any ROM for flashing

Implement a language server extension (as VSCode extension?) for our custom language.

Resources:

• https://www.eclipsecon.org/2020/sessions/beyond-lsp-getting-your-language-theia-and-vs-code
• https://www.youtube.com/watch?v=ESRk7NmCDFA

Use https://github.com/sourcey/moxygen to convert docs to markdown.

• Verify the "new project" dialog is working fine.
• Adjust new project with custom name, author name and maker code

Add support for language files and create English, German and Spanish translations.

eclipse-theia/theia#10188

When doing more complex code generation, i.e. regenerating all .lang.json files, cache retrieved data to increase performance.

The post processing of "entitySharedTileset" images runs very long when a Binary folder already exists.

• Fix focus
• Fix button remapping
• Backport latest advancements from PVB to VES.
  • Fullscreen
  • Fixed button assignments (toggle slowmotion)
  • EmulatorLoaded event
• Load emulator in iframe via http -> Endpoint class?
• Figure out mapping low battery toggle
• Start vb files in the configured default emulator

Create more game templates, or rather, plugins for GameState and respective entities.

• RPG
• Top-down racing game (based on Formula V code)
• Falling block puzzle
• Shoot'em Up
• Point & Click/Adventure

Might mix them all into a single game template, akin to GB Studio's sample project.