Will the real Paralax Forum please standup? Now it shows up on my Chrome screen with everything on the left hand side. Also I am not all convinced that this editor works. It seems to be an ordinary text box rather than a true editor.
Looking into it, I think it wouldn't be too difficult to write Spin/Spin2 definitions for highlight.js. Since Spin is kinda odd, I think the autodetection would identify it fairly reliably. I'll try my hand, I guess
Font- I've not added that yet, but will do that @Wuerfel_21 . Your diagram looks great !
---
This is one of those "rock and hard place" situations. The old editors don't work well (at all) with this new Vanilla version, and this new "Rich" editor seems like the only one Vanilla are supporting moving forward.
The plan is to use all standard features in this forum, so that we can keep it up-to-date moving forward.
So far this update achieves that, using a stock template and only a few CSS overrides.
We are now on Vanilla 3.3. Version 4.0 is due for release in Q1, and that will bring a huge number of improvements since the 3.3 release (which was over a year ago).
Tables and other markdown extras aside (which I don't think were available in the previous editor either?).... we have to use what's available for now, knowing the path to progress is available again, now that we took the leap off the ancient bunch of code and plugins that no-one dared update for so many years.
Moving forward....
It seems to me the main thing that is annoying with this new text editor is that inside code blocks, the cursor jumps around after a pause in typing. In the short term I suppose we could all use copy/paste to enter code.
And if we are keeping this editor, I'd probably patch/fix the jumping cursor issue anyway. Plus add an instruction tooltip and/or FAQ link which shows how to enter code in this new editor box. We have the feature to add "FAQ" and information pages now. Another bonus!
BTW... someone asked about the P1/P2 graphic. That will be for some Parallax images/information/ads, so it's a placeholder for now.
The Search feature has a few options added too, which hopefully will improve that experience!
Looking into it, I think it wouldn't be too difficult to write Spin/Spin2 definitions for highlight.js. Since Spin is kinda odd, I think the autodetection would identify it fairly reliably. I'll try my hand, I guess
Yes please! If you can write it, I'll make sure it's added.
Whilst experimenting, the vb parser seemed reasonable, but just not quite 100% 🤪
Yet again, the "Preview" button is missing... I guess wizzywig is the default, but code editing is still awkward with extra spaces at the bottom, jumpy cursor, weird results deleting characters.
Would like the full menu of edit options or a link to Rich Editor options (a pop-up of options?)
So things are improving a lot, however one thing went backwards this morning, it got narrower again. You went the wrong way, it was super narrow, you got it to like 75% of where it should be, but today it went back to around 60% width. Please make it fill the full width of the window.
I think the error under each of @dgately 's posts is actually from rendering his signature.
Anyways, here's the first version of the Spin plugin for highlight.js. This should be called "spin.js" and be loaded in... Somewhere... I guess... After highlight.js but before the code that initializes it? I'm not exactly a javascript buff. Currently Spin1 only (and will actively reject code that it knows is Spin2. This will help with detection when the Spin2 support is in.)
I think the error under each of @dgately 's posts is actually from rendering his signature.
Yes... I can't edit my signature, though it states that my signature is 279 characters too long... And, I don't have any editable content in my signature... May take forum admin to fix that!
I think the error under each of @dgately 's posts is actually from rendering his signature.
Yes... I can't edit my signature, though it states that my signature is 279 characters too long... And, I don't have any editable content in my signature... May take forum admin to fix that!
And here's with Spin2 support. Had to switch to attaching it because Spin2 just has too many symbols.
While we're at messing with the forum, can we please get rid of the file type limitation? It's very annoying and I don't think it does much good (especially since the spicy ones like EXE are allowed, anyways).
And here's with Spin2 support. Had to switch to attaching it because Spin2 just has too many symbols.
While we're at messing with the forum, can we please get rid of the file type limitation? It's very annoying and I don't think it does much good (especially since the spicy ones like EXE are allowed, anyways).
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Comments
Do we really want the poster info bar translucent so the post text is overlayed as in the attached picture.
Trying to cover all the feedback with this refresh.
Some things in progress:
line spacing in the editor boxuploading images current not workingFixedsocial icons and emoicons too small :)comments pane could be wider on larger displays.user icons could get darker background so white-icons show better.add woff Parallax fontadd FAQ / tooltip on new editorcertain signatures are not compatible with forum updateattempt to prevent the cursor jump in editor / fix the system slowdownincrease editor buffer to prevent browser waits with large messages.allow spin/svg files to be attached.avatars in mobile viewpostnum adjustmentsshade the announcements in the recents page, so the first post is obvious.add the top-title bar with useful buttons (Sign-Out, Parallax shop, Learn, .... and maybe repeat the socials up there too.)Looking great! Thanks for the updates. I feel much better with the return of my favored "Mark All Viewed" button :D
Aaand we're back.
Hello!
Will the real Paralax Forum please standup? Now it shows up on my Chrome screen with everything on the left hand side. Also I am not all convinced that this editor works. It seems to be an ordinary text box rather than a true editor.
-----
Mascot back, but is on strike.
AAAA I figured it out!
This fixes the washing-out of everything:
.Frame-body { opacity: 1; }IDK why this has non-1 opacity to begin with.
Also, typing code into the rich editor is super duper ultra broken, keeps resetting the cursor to the beginning
Tables in the old post are still there (and still have broken CSS), but does the rich editor do them?
| A | B | C| D | E|
|---|---|---|---|---|
| something | | | | |
| | or | | | |
| | | rather | | |
| | idk | | | |
| tables | r |cool | right | ?|
yeah, no
These are the supported tags at the moment : https://success.vanillaforums.com/kb/articles/13-rich-editor
'' Voice architecture: Parameters: (10 bytes) '' ┌─────┐ - volume 0..255 '' ┌──────┐ ┌───┐ │ Env │ - panorama 0..127 '' │ Osc2 ├──┤├─┬────┐ └──┬──┘ pl - semitone osc1 0..255 '' └──────┘ └───┘ │ ┌──┴──┐ ┌── L DAC - semitone osc2 0..255 '' pm┌──├─┘ (+)──┤ DCA ├─┬──┤ - detune osc2 0..255 '' ┌──────┐ ┌───┐ └─────┘ │ └── R DAC - PhaseMod intensity 7..0 '' │ Osc1 ├(+)─┤├───┴─┐pm │ pr - Feedback intensity 7..0 '' └──────┘ └───┘ │ - Envelope Attack 0..255 '' └─────├─────(+)──────┘ - Envelope Decay&Release 0..255 '' fb - Envelope Sustain 0..255 '' ''Legend: = SawtoothTriangle Shaper, (+) = Mixer, ├ = 2^n Attenuator (shifts) '' Osc = Sawtooth Oscillator (DDS) '' Env = Envelope Generator (A D/R S) '' DCA = Digital Attenuator (mult 8*32)Code block test...
RE: code blocks
Looking into it, I think it wouldn't be too difficult to write Spin/Spin2 definitions for highlight.js. Since Spin is kinda odd, I think the autodetection would identify it fairly reliably. I'll try my hand, I guess
Font- I've not added that yet, but will do that @Wuerfel_21 . Your diagram looks great !
---
This is one of those "rock and hard place" situations. The old editors don't work well (at all) with this new Vanilla version, and this new "Rich" editor seems like the only one Vanilla are supporting moving forward.
The plan is to use all standard features in this forum, so that we can keep it up-to-date moving forward.
So far this update achieves that, using a stock template and only a few CSS overrides.
We are now on Vanilla 3.3. Version 4.0 is due for release in Q1, and that will bring a huge number of improvements since the 3.3 release (which was over a year ago).
Tables and other markdown extras aside (which I don't think were available in the previous editor either?).... we have to use what's available for now, knowing the path to progress is available again, now that we took the leap off the ancient bunch of code and plugins that no-one dared update for so many years.
Moving forward....
It seems to me the main thing that is annoying with this new text editor is that inside code blocks, the cursor jumps around after a pause in typing. In the short term I suppose we could all use copy/paste to enter code.
And if we are keeping this editor, I'd probably patch/fix the jumping cursor issue anyway. Plus add an instruction tooltip and/or FAQ link which shows how to enter code in this new editor box. We have the feature to add "FAQ" and information pages now. Another bonus!
BTW... someone asked about the P1/P2 graphic. That will be for some Parallax images/information/ads, so it's a placeholder for now.
The Search feature has a few options added too, which hopefully will improve that experience!
Yes please! If you can write it, I'll make sure it's added.
Whilst experimenting, the vb parser seemed reasonable, but just not quite 100% 🤪
I'm already on it!
Black, with blue, "yeah, you clicked it" works better. Thanks. The blue links were a trigger. Now the "new" badge seems to make more sense.
Just a test (my prior posts all claim an error: " There was an error rendering this rich post.")... This one does, as well (arg!)
Also:
pub main |x,y repeat x := y++dgately
So things are improving a lot, however one thing went backwards this morning, it got narrower again. You went the wrong way, it was super narrow, you got it to like 75% of where it should be, but today it went back to around 60% width. Please make it fill the full width of the window.
Yet another test, posting from Google Chrome as opposed to posting from Safari...
Will this result in another 'rich post' error? It does!
Posting from a macOS system (Safari & Google Chrome) appears to result in " There was an error rendering this rich post."...
Ah, macOS could be a thing. I'll get hold of a mac and see what looks different. Maybe some encoding mismatch.
Possibly something like:
Cannot get Rich Editor to work in embedded comments
https://open.vanillaforums.com/discussion/37538/cannot-get-rich-editor-to-work-in-embedded-commentsI think the error under each of @dgately 's posts is actually from rendering his signature.
Anyways, here's the first version of the Spin plugin for highlight.js. This should be called "spin.js" and be loaded in... Somewhere... I guess... After highlight.js but before the code that initializes it? I'm not exactly a javascript buff. Currently Spin1 only (and will actively reject code that it knows is Spin2. This will help with detection when the Spin2 support is in.)
/* Language: Spin Author: Ada Gottensträter Description: language definition for Spin files Category: config */ "use strict"; { const COMMENT_MODE = hljs.COMMENT('\'', '$'); const DOCCOMMENT_MODE = hljs.COMMENT('\'\'', '$'); const BLOCKCOMMENT_MODE = hljs.COMMENT('{', '}'); const BLOCKDOCCOMMENT_MODE = hljs.COMMENT('{{', '}}'); const BLOCKTYPES = 'con obj var pub pri dat '; const SPECIAL_CONS = '_CLKMODE _XINFREQ _CLKFREQ _FREE _STACK '; const WIDTHS = 'byte word long '; const SPIN_KEYWORDS = 'if ifnot else elseif elseifnot repeat from to step while until case return abort result '; // Keywords valid in Spin code (PUB/PRI blocks) const PASM_KEYWORDS = 'wc wz wr nr org res fit '+ 'if_a if_ae if_always if_b if_be if_c if_c_and_nz if_c_and_z if_c_eq_z if_c_ne_z if_c_or_nz if_c_or_z if_e '+ 'if_nc if_nc_and_nz if_nc_and_z if_nc_or_nz if_nc_or_z if_ne if_never if_nz if_nz if_nz_and_c if_nz_and_nc if_nz_or_c if_nz_or_nc '+ 'if_z if_z_and_c if_z_and_nc if_z_eq_c if_z_ne_c if_z_or_c if_z_or_nc '; const GENERIC_BUILTINS = 'float trunc round and or not '; // builtins valid everywhere const SPIN_BUILTINS = ' bytefill wordfill longfill bytemove wordmove longmove strsize strcomp waitcnt waitpeq waitpne waitvid cogid coginit cognew cogstop lockclr locknew lockret lockset clkfreq clkmode '; // Spin builtin functions const SPIN_BUILTINS_SPECIAL = 'constant string '; // special builtins const LITERALS = 'true false posx negx xtal1 xtal2 xtal3 xinput rcfast rcslow pll1x pll2x pll4x pll8x pll16x '; const P1_REGISTERS = 'par cnt ina inb outa outb dira dirb ctra ctrb frqa frqb phsa phsb vcfg vscl '; // Registers for P8X32A const P1_MNEMONICS = 'abs absneg add addabs adds addsx addx and andn call clkset cmp cmps cmpsub cmpsx cmpx cogid coginit cogstop djnz hubop jmp jmpret '+ 'lockclr locknew lockret lockset max maxs min mins mov movd movi movs muxc muxnc muxz muxnz neg negc negnc negz negnz nop or '+ 'rcl rcr rdbyte rdword rdlong ret rev rol ror sar shl shr sub subabs subs subsx subx sumc sumnc sumz sumnz test testn tjnz tjz '+ 'waitcnt waitpeq waitpne waitvid wrbyte wrlong wrword xor '; const STRINGS = { className: 'string', begin: '"', end: '"' } const PREPROCESSOR = { className: 'meta', begin: /^\s*#[a-z]+\b/, end: /$/, keywords: { 'meta-keyword': 'if else elif endif define undef warning error line print region end ' + 'pragma ifdef ifndef elseifdef elseifndef include ' }, contains: [ { begin: /\\\n/, relevance: 0 }, hljs.inherit(STRINGS, { className: 'meta-string' }), { className: 'meta-string', begin: /<.*?>/, end: /$/, illegal: '\\n' }, COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE ] }; const NUMBERS = { className: 'number', variants: [ { // base 2 begin: /(?<!\w)\%[01_]+(?!\w)/ }, { // base 4 begin: /(?<!\w)\%%[0123_]+(?!\w)/, relevance: 10, // Rather unique spin-ism }, { // base 16 begin: /(?<!\w)\$[0-9A-Fa-f_]+(?!\w)/ }, { // base 10 begin: /(?<!\w)[0-9_]+(?!\w)/ }, ], }; const FUNCTIONS = { className: 'function', begin: /^\s*(pub|pri)\s+/i, end: /$/, keywords: BLOCKTYPES, contains: [ { className: 'title', begin: /(?<=^\s*(pub|pri)\s+)/i, end: /(?!\w)/, contains: [COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE], }, { className: 'params', begin: /(?<=^\s*(pub|pri)\s+\w+)\((?!\))/i, // Does not match Spin2-style "PUB name()" !!! end: /\)/, illegal: /[{}]/, contains: [COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE], }, { className: 'resultvar', begin: /(?<=^\s*(pub|pri)\s+\w+(\(.+\))?\s*\:\s*)\w/i, end: /($|\w(?![\w,]))/, contains: [COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE], }, { className: 'locals', begin: /(?<=^\s*(pub|pri)\s+\w+(\(.+\))?\s*(:.*)?\|\s*)\w/i, end: /($|\w(?![\w,]))/, illegal: /(byte|word|long)/, contains: [COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE], }, COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE, ], illegal: /\(\)/, } hljs.registerLanguage("spin",function(hljs){return{ aliases: ["spin"], case_insensitive: true, keywords: { // Initial block is CON... keyword: BLOCKTYPES + SPECIAL_CONS + WIDTHS + SPIN_KEYWORDS + PASM_KEYWORDS + P1_REGISTERS, built_in: GENERIC_BUILTINS + SPIN_BUILTINS + SPIN_BUILTINS_SPECIAL + P1_MNEMONICS, literal: LITERALS, }, contains: [COMMENT_MODE,DOCCOMMENT_MODE,BLOCKCOMMENT_MODE,BLOCKDOCCOMMENT_MODE,PREPROCESSOR,STRINGS,NUMBERS,FUNCTIONS], }}); }The prior post is yet another argument for restoring the vertical scrollbar to code blocks.
-Phil
Wuerfel_21
I think the error under each of @dgately 's posts is actually from rendering his signature.
Yes... I can't edit my signature, though it states that my signature is 279 characters too long... And, I don't have any editable content in my signature... May take forum admin to fix that!
😉
Will get the signatures fixed up shortly.
Yay! thank you VonSzarvas for fixing the narrow thing! It's beautiful now!
Now my only strong wish is for a dark mode theme, but I think you mentioned that already.
And here's with Spin2 support. Had to switch to attaching it because Spin2 just has too many symbols.
While we're at messing with the forum, can we please get rid of the file type limitation? It's very annoying and I don't think it does much good (especially since the spicy ones like EXE are allowed, anyways).
Test for when it's added in:
Spin1:
CON _clkmode = xtal1 + pll16x _xinfreq = 5_000_000 _stack = 128 OBJ pst: "Parallax Serial Terminal" PUB main pst.start(115_200) repeat 20 pst.str(string("Hello World!",13))Spin2:
CON APINS = 5 addpins 3 PUB main() | n pinstart(APINS,P_DAC_DITHER_RND,50_80,$8000) repeat do_stuff(n++) PRI do_stuff(n) wypin(APINS,n.word[0] SCA $FF00)Is David not a man of many words or is something afoot?
Awesome job @Wuerfel_21
I'll get the highlighting uploaded in the morning, and add some file suffixes too!
Svg, spin, spin2, bin and eeprom should all be included.