Jesse Gumm
Jesse Gumm
As I begin implementing the testing suite into my larger applications, I'm finding things that would come in handy: 1) "Watching" for the creation of a DOM element as the...
Right now, the plugin system autoimports the Erlang headers from each Nitrogen plugin, and it does _copy_ the static resources, but it would be nice if it was intelligent enough...
The plugin system should be able to autostart dependent applications if necessary, as specified in each plugin's nitrogen.plugin file (or perhaps rename to plugin.config, or even nitrogen-plugin.config).
This is more of a reminder than anything, but simple_bridge 2.0 should also provide an HTTPS configuration abstractions similar to how it abstracts away other parts of the underlying server...
Something to simplify retrieving values, where `wf:q` pulls from POST and GET, being able to specify the source explicit without dropping into `simple_bridge` to do it. This would also warrant...
From a user: Hope this finds fine. I am of a view if Nitrogen comes up with a Google Map element which when given Latitude and Longitude values can automatically...
Regarding these line: https://github.com/nitrogen/nitrogen_core/blob/master/src/lib/wf_render_actions.erl#L184-L189 wf:temp_id() returns a value like "temp12345", which is handled specifically by the above lines. This highlights a bit of a wart of Nitrogen, in that the...
https://groups.google.com/forum/#!topic/nitrogenweb/nV1jZv8n1K0 But also rework it to use RECAPTCHA 2.0 before implementing this.
Referenced conversation: https://groups.google.com/forum/#!topic/nitrogenweb/3BNqZ1hwRJg
This would allow for doing some custom things with the state after the handlers have run, but before a page's main() function is executed.