Making a legacy fork

Help
#1

In this topic, I will be showing the status of my fork (Wick editor legacy remastered). However, I may need to ask
questions cause I never really worked with js that much.

Here is the link https://github.com/AOC-9/wick-editor-legacy-remastered

1 Like
#2

I’m currently updating the ui

1 Like
#3

Update: So I decided to make the layout a mix of…
Macromedia flash and Adobe animate (2020 probably).
I’ll be also adding my own elements to it

1 Like
#4

Why fork such an old version? the only person I know who uses this version does so only because he learned it that way somewhere and maybe he didn’t even know about the new version before I told him.

2 Likes
#5

Because it has potential in my opinion. Plus I want this website to feel like Adobe animate/flash and I want to try something different. But the disadvantage is there is no mobile version ):

1 Like
#6

I am confused, when you say mobile, do you mean phones and tablets, or just phones?

#7

Phones (I don’t know about tablets though)

1 Like
#8

They are like the same thing

1 Like
#9

Macromedia flash has a different layout and theme than animate 2020

#11

@Averagewickuser, please save yourself from legacy wick.

I’ve made atleast 5 forks of legacy wick, and they all are deprecated/deleted.

Classic Wick can’t work with Modern Wick, and just because its interface is more like Flash Professional, doesn’t mean it’s better.

Here’s some reasons why:

  1. jQuery vs. React
    1. Even though React is hated as much as Electron, jQuery is an ancient library that is basically dead now.
    2. when using jQuery, everything you need is in the HTML, when React makes the exact HTML you need and expands and takes care of state and such.
  2. Old Engine ≠ New Engine
    1. The old engine uses names like WickPath or WickClip when the new engine uses Wick.Path, Wick.Clip.
    2. The new engine is a thousand times more refined and less buggy.
    3. Any coding thing in the forums after 2018 is NOT GONNA WORK ON IT.
#12

Also, the way Old Wick is coded is a way (ES5) that isn’t the recommended grammar for JS since 2015.

#13

Ok if the fork does not work as expected.
I’m gonna cancel it entirely

#14

I knew this would happen. That’s why I explained the differences and problems of legacy wick.

#15

Main reason a lot of people use legacy is the UI muscle memory, it’s too hard/not worth it to switch over. If you wanted to mess with the UI, just mod the legacy UI into modern or something. (Also if you have projects in legacy, you can transfer them to modern version using wick editor’s official tool for this; there’s no tool to transfer them back, however).

2 Likes
#16

Alright then