You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have wandered for a long time about create svg at the browser server end.
first, the javascript plugs or tools can all be used with "require" in the nodejs and phatomjs environment.
it seems that the differences are the balance of client and server , used cpu time and memory used.
but i have forget the important thing: if put it to server end, i should coding at the server side (the create logic and fetch my data from dbms) and refresh my brower then check my svg .
it is not Humanization, create code at server side and debug at the client, it become more diffcult.
The text was updated successfully, but these errors were encountered:
According to my experience debugging server-generated svg is no more complex than debugging server-generated html.
And also do not forget that there is no need to have a separate remote machine for tests, you can everything try locally even with livereload
i have wandered for a long time about create svg at the browser server end.
first, the javascript plugs or tools can all be used with "require" in the nodejs and phatomjs environment.
it seems that the differences are the balance of client and server , used cpu time and memory used.
but i have forget the important thing: if put it to server end, i should coding at the server side (the create logic and fetch my data from dbms) and refresh my brower then check my svg .
it is not Humanization, create code at server side and debug at the client, it become more diffcult.
The text was updated successfully, but these errors were encountered: