|
Post by Malban on Apr 1, 2016 6:40:06 GMT -5
Hehe... since you don't like the options I have given above :-)... I created a Github instance (although sources are not present as of yet, might do that over the weekend), but having a repository allows the use of the github issue tracking... Therefor: github.com/malbanGit/Videas another option as a centralized issue system. If you have any questions - just ask, I will expand the FAQ... Regards Malban
|
|
|
Post by mountaingoat on Apr 1, 2016 16:43:04 GMT -5
Lol, sorry about that.
It is not that I think that this topic or PMs would not work, it is that I don't trust myself of what I mentioned before. Git issue tracking is nice and will be easier (for me) to scan than paging through this topic.
Btw, the more I use Vide the more I like it! I just tried tracki for the first time, it is great!
|
|
|
Post by mountaingoat on Apr 2, 2016 6:48:06 GMT -5
Malban, how do I clear breakpoints in dissi?
|
|
|
Post by Malban on Apr 3, 2016 5:54:39 GMT -5
Hi, Breakpoints: - They tend to nag me too :-)! All breakpoints should be "toggles" setting them again, should "unset" them. - But I noticed that sometimes that does not work - I must debug that at one time more closely - in Dissi there is a command line command "clear breakpoints", I fiddled with it the other day, and have not tested it again - does it not work? Also a small update: VideUpdate (only 5MB, unpack over old installation) - only one of "*.LST" or "*.CNT" is loaded when dissi is started (can be configured) - added "glow" options to display, now e.g. the "endpoints" in the electricity demo can be seen (makes vecxy slower again...) - added "view" for other filetypes in editor - corrected "fullpath" for cartridge starter (to relative path) - added option to fully configure external assembling (but scripting must be done by users for their assembler), an example for windows+AS09 is provided - if a "build" is done for a project, all editors now "autosave" befor building - "save as" implemented in editor - switch to selected editor (when clicked on tree) in vedi - Help file updates with FAQ -> some old serialization won't load... Regards Malban
|
|
|
Post by mountaingoat on Apr 3, 2016 7:48:43 GMT -5
Malban, just tried again toggling the breakpoints, today it works fine. I wish I remembered what I did to make them not turn off - will keep my eye out to see if I can create a reproducible case.
Also, tried 'cb' from the command line - it works! (Very nice help for the command line stuff.)
The link in your post does not work, points back to the thread.
|
|
|
Post by Malban on Apr 3, 2016 8:47:20 GMT -5
|
|
|
Post by mountaingoat on Apr 3, 2016 17:27:05 GMT -5
Malban, upgraded it, thank you!
Can I configure an external editor to be used with vedi?
|
|
|
Post by Malban on Apr 4, 2016 5:14:49 GMT -5
Hm,
What is your goal? What do you want to achieve? To integrate a different editor (exe) into a java application is (if at all possible) very difficult.
Do you want to use the inbuilt assembler with another editor? Do you want to use only the emulator and dissy?
For these to options I could add command line parameters to only startup the required parts.
On the other hand what options in vedi are missing? The "plus-side" of any IDE is that you are working in ONE environment and that each part has a balance with other parts and the parts complement each other.
I would rather enhance vedi so that your required parts are integrated, especially in the light, that vide and the "integration" part is just in its beginnings... (with veccy, ym/mod-songs, image-importing, sample conversion etc yet to come)
Malban
|
|
|
Post by mountaingoat on Apr 4, 2016 5:39:38 GMT -5
Malban, my current workflow is as follows:
1. Edit the software in Notepad++, 2. Compile in commend line 3. Load into vexci 4. Start in vexci. 5. If anything looks incorrect, pause, set breakpoint in dissy, debug, etc 6. GOTO 1
I use Notepad++ for the assembly editing and while having a built-in one would be nice for Vide I think it will be a lot of work to get all the features in and quite frankly the other parts of Vide are so incredibly useful, I'd rather see those enhanced :-)
In Notepad++ I use the hot keys for search / replace / copy-paste all the time, I have to colors, font sizes, syntax highlighting all set up.
Overall I think the quickest solution would be to have a "re-open file" button in the Vide editor. Then I could do:
1. Edit in whichever editor 2. Re-open in vedi 3. Compile and run in vedi 4. Debug in dissy 5. GOTO 1 What do you think?
|
|
|
Post by Malban on Apr 4, 2016 6:09:11 GMT -5
Hm (again :-)),
first, at least some of the things you said, can be done in vedi, like: - search, replace (also multi replace or just in selection) - copy/past - undo/redo - syntax highlighting - you can "jump" to include files with a double click - double "rightclick" on a label or variable tells you where it is defined (and/or jumps to the location) - source beautifier button
I haven't got (yet): - customized syntax coloring - different font (sizes) - any kind of macro programming/support - customized keys
The reload button is already there, shift click on the load button, reloads the current file. - Although there is a dumb bug, I just tested it, after a reload syntax highlighting is garbled, but for your purposes it should work ok
... and for enhancing... Next on my schedule is: - fixing known bugs - than adding "tools", like finishing veccy and the other stuff I mentioned
What I would be interested in - does assembly work in vide, or are there any incompatibilities? If so, what? Sample code etc :-)
Malban
|
|
|
Post by mountaingoat on Apr 4, 2016 7:51:35 GMT -5
Sounds, great, I will try the reload - compile in Vide workflow starting tomorrow!
Again, cannot emphasize enough how great it is to be able to debug with variables, step by step, like a real modern IDE. Helped me tremendously yesterday when I was debugging collision issues with the new goat game I am working on. And I haven't even tried some of the more advanced debugging features with vectors, tweaking the parameters, etc.
|
|
|
Post by mountaingoat on Apr 5, 2016 7:01:01 GMT -5
The new workflow works really nice - edit in whichever editor - shift-click to reload in the Vide editor.
Compile-run with the Vide button.
GOTO 10
|
|
|
Post by Malban on Apr 8, 2016 12:20:29 GMT -5
Hi, updated the update... VideUpdate.zip (now 12 MB) As befor just copy over the complete "install". For a long version (and some nicee shiny pictures) of the update head over to: Malbans VIDE pageFor a short version: - changed some "glow" settings - added "breaki" a breakpoint window - extended the FAQ - added quite some documentation - added breakpoints to variables - variables can be added on the fly to dissi - corrected/clarified undo/redo in dissi emulation - bug where dissi was not updated when new lables were added - bug in dissi, where dissi would not recognize DP-dependend variables (RAM locations) - in dissi added $CA, $CB to DP menu - vedi now saves split screen positions - vecxi emulation correcter, now the last output shift register is “shown” (blank signal) twice, one complete shift takes 18 cycles instead of 16, 2*8 + 2 (thanks for the hints thomas) - assi error implemented, when trying to optimize forward references, this resulted in bad code, option is switched off and generates an error instead! - in order to emulate analog DAC offsets, a vectrex “generation” can now be configured, some dac timings were implemented along the way - ana now displays the “analog” DAC signal rather than VIA_ORA (as usual, analog hardware can be some cycles “off”) - first "additional" tool added: "image to vectrex raster image" - and probably some bugfixes I forgot Regards Malban
|
|
|
Post by gauze on Apr 9, 2016 10:55:26 GMT -5
hey I can't get this to run on windows I get:
java.lang.ClassNotFoundException: de.muntjak.tinylookandfeel.TinyLookAndFeel
using:
$ java -version java version "1.8.0_77" Java(TM) SE Runtime Environment (build 1.8.0_77-b03) Java HotSpot(TM) Client VM (build 25.77-b03, mixed mode)
help?
|
|
|
Post by Malban on Apr 9, 2016 16:00:34 GMT -5
Hi, I would love to help, but I don't know how. On my test windows system I have exactly the the same java installed.
The missing class is from the tinyLookAndFeel. The corresponding jar file should be in the "lib" directory and is called: "tinylaf.jar".
Have you loaded the complete package? The one with about 180MB and than installed the updates? If you only downloaded the updates, than that would be a good reason, since they are not complete.
Just unpacking and double clicking the jar (VIDE.jar) file has allways worked for me under any windows environment (Java 8).
Malban
|
|