Hi, This message about the way qooxdoo handles private and protected variables in the Class system.
These variables are of course obfuscated but it doesn't mean at all they are private or protected in a pure OO sense because it 's still possible to access it (sometimes I debug the build version of my app when I'm not in front of my own computer and thus don't have access to the source). However, it's possible to partially mimic these behaviors thanks to scopes ( this page <http://www.codeproject.com/Articles/133118/Safe-Factory-Pattern-Private-instance-state-in-Jav> gives good examples about this topic). Any chance to see a new explicit declaration in the class definitions in a the future ? Best, Benoît. PS: Note that it's not a "real" problem but sometimes you really want to avoid people hacking your javascript at runtime. -- View this message in context: http://qooxdoo.678.n2.nabble.com/privates-vs-scoped-variables-tp7582654.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
