We'd like to get there eventually. Phan populates a sqlite database when analyzing code (if run with the -s flag). This allows fast runs on single file changes or patches. We're hoping to use this for things like auto-complete and finding callers for a class/method/whatever eventually.
That's awesome. If a PR was opened that added autocomplete and/or finding callers and/or refactoring (and assuming that the code is good), would you guys be open to merging it? Or would it be delayed so that the core functionality can be focused on?
We currently store method/function callers in the sqlite database (see https://github.com/etsy/phan/blob/master/src/Phan/Analyze/Br...), but aren't yet exposing an interface for getting callers. We'll want to store callers for constants, classes, properties and global variables as well.
Meanwhile, have you checked padawan ? https://github.com/mkusher/padawan.php it's a server made to be used by editors for autocompletion of PHP code (like jedi for python) it works pretty well with vim AFAIK
Just ran out of time, so mkusher did his own thing. I disagree with his direction and I think it's overly complex from a user's standpoint, but he disagrees and isn't willing to change it, so I lost interest in that project too.
Using the actual AST from the PHP interpreter is going to be a) much faster and b) much more accurate.
Analysis takes a lot of CPU and we're not doing any parallel processing. Phan itself is about 30k lines of code and takes about 1.5s for a clean run.
That being said, you should take a look at the '-s' flag for saving state to a sqlite database. After the initial run the stored state can be used to only scan changed files. For a patch with a few files changed it should be about 0.5s to run the analysis.
Phan does not attempt to make sense of things like `$class_name->$function_name()` or `$$v`. I'd be happy to see a pull request that could handle simple strings, but otherwise I imagine the best we can do is emit a warning.
I'm not sure what SIMD refers to. Can you clarify that?
> I'm not sure what SIMD refers to. Can you clarify that?
With a name like "asm" that comes as a surprise... Single Instruction Multiple Data[0] refers to low level processor instructions that are able to work across a range of data, e.g. video cards working on changing the values in a framebuffer with one instruction mapping across an entire buffer in parallel.
I'm not sure. PHP7 is pretty new so package maintainers may not have had a chance to put binary releases together. You may need to compile it yourself from https://github.com/nikic/php-ast.
We used construction paper to black out the back around the tablet. My guess is that the paper wouldn't like the humidity but the rest would be fine. Perhaps you could swap in some black plastic material that would work with spray adhesive.
The rectangle of light isn't noticeable at all in normal light if you adjust the brightness on the tablet well. In a dark room it can be noticeable, though.
Unfortunately, the touch screen doesn't work through the mirror, however, we're using reusable sticky stuff to attach the mirror to the tablet, so its easy to remove if needed.
That you're asking about keeping it unguessable makes me think that it feels like too few. Its actually only 5 bytes of random (the first character is always zero). 2^40 is a pretty large number and I don't expect to get high coverage over that space any time soon. That being said, perception is important, so I should probably up it.
As for hot-linking; I have no business plan and just wanted to make something useful. I should probably figure that stuff out.
I'd just put up a nice, flat lock somewhere when uploading. If it's locked, pop up a text box where the user can enter a password. If it's open, just do what you do right now.
I personally think a freemium kind of model will work best for a service like this. Allow locking only for logged in users, and give each person 30 locks for free monthly (1 per day on average). For additional locks, either charge a small fee out of the user account (something under a dollar), or charge a given amount monthly for flatrate locks. You should allow people to deposit money into their user account in order to pay for these things. They'll most likely consider it playmoney, and that lowers inhibitions when it comes to buying premium features.
