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
The goal of the hack is that, when seaside is loaded, the auto-completion will propose the brushes of Seaside when the variable is named html because naming a variable html is a big convention in Seaside.
This is pretty important for the usability of some framework like seaside to do that because brushes do not have a common prefix and it improves a lot the productivity to auto-complete with the brushes.
Since the hack was removed, we should provide a clean way to reproduce the behavior.
The text was updated successfully, but these errors were encountered:
To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. It will be closed in 1 month if no further activity occurs. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.
Imagine, for a moment, that you came upon a bread factory for the first time. At first it just looks like a jumble of incomprehensible machinery with a few people buzzing around. As your eyes adjus…
This issue looks more like a small project than an actionable issue.
I propose we move it to a wiki with potential projects for people to contribute.
Could be a great basis for GSOC.
This PR (#3155) remove a hack used by Seaside.
The goal of the hack is that, when seaside is loaded, the auto-completion will propose the brushes of Seaside when the variable is named
html
because naming a variablehtml
is a big convention in Seaside.This is pretty important for the usability of some framework like seaside to do that because brushes do not have a common prefix and it improves a lot the productivity to auto-complete with the brushes.
Since the hack was removed, we should provide a clean way to reproduce the behavior.
The text was updated successfully, but these errors were encountered: