|
Author |
Topic: Colossals: Performance Observations and Question (Read 368 times) |
|
mm Guest
|
Colossals: Performance Observations and Question
« on: Jul 23rd, 2004, 7:08pm » |
|
When editing files that are colossal compared to most proce55ing applets, I've noted that opening a second version of processing helps to alleviate the strain put on the editor. To integrate new features and do quicker checks for syntax errors, I suggest using the Export-To-Web feature which returns syntax errors much faster than simply clicking "run" or hitting ctrl-R. not really sure why this is, but it would be great if "run" were as quick as that when editing colossal files. Q: What is a mega bucket?
|
|
|
|
TomC
|
Re: Colossals: Performance Observations and Questi
« Reply #1 on: Jul 24th, 2004, 2:59am » |
|
Could it be that export to applet doesn't update the history file? Run updates the history file, which is really useful because a crashing applet can currently take out the whole IDE, but opening the applet and restoring from the history list can save much lost time/code if that happens. What fry currently refers to as 'megabucket' will hopefully be the next release of Processing. It is the current focus of new features and development, but there might be interim bug-fix releases if it's not ready in time.
|
|
|
|
|