* added redirection script when running the built-in newLISP server
* changed recommendations to run ./newlispServer
* added newlispServerWin.bat file provided by m35
* support for PHP-like multi-params by appending [] to the var name
* added documentation for $GET/$POST/$FILES and multiparams to guide
* updated the RSS feed on the example-site for 0.50
All went well and the general awesomeness continues! Thanks again.
I'm still thinking about the business of upgrading from older releases of the framework. When a new release comes along, such as 0.51, I want to incorporate all the new things and fixes that you guys have produced, without overwriting any of the work that I've done on the code and customizations on this side. I'd be tempted to copy over the /dragonfly-framework folder in its entirety, but that's not a good idea because the disposition of the plugins-(in)active folders are different in the example-site folder. Also, there are two plugins in my version which I don't want to be overwritten, one because you don't have it, and the other because I have a later version.
Similarly: I've modified /include/css/screen.css. Perhaps I should have renamed it first?
I wrote a script that compared the two directories (the example-site and my site) to produce a list of files that are both newer and different in the new release. (Some 'newer' files in the release are actually identical just more recently stamped).
I wouldn't recommend trying to rename your own files to something else, leave them as they are.
The important stuff that you want are the 3 files mentioned in the Getting Started guide.
If you don't want to manually drag & drop files you can use a tool like 'rsync' to update your copy of the dragonfly-framework folder with the one from the zip file without overriding any your plugins. For that however I'll refer you to rsync's man page.
Running the example-site on Windows and clicking on the code link gives an error...
We're sorry, but something went wrong.
ERR: invalid function in function set : (parse-date (lookup 'updated entry) "%Y-%m-%dT%H:%M:%SZ")
called from user defined function Dragonfly:read-atom-feed
called from user defined function Dragonfly:eval-template
called from user defined function Route.Static:run
called from user defined function Dragonfly:listener
called from user defined function run
Interesting, thanks for pointing that out. I think the parsing of the atom feed should be done on the client side via javascript/ajax anyway, but 'parse-date' is a pretty useful function, odd that it's not supported for windows. Any chance of that Lutz?
The underlying POSIX function strptime() is not available on MS Windows. Strangely the complement strftime() function is available and used in 'date' formatting. Both are rather complex locale sensitive functions.
Use something like the following and extend it to hours/minutes/seconds: