I would very much appreciate a php sugar. It is beyond my ressources at the moment to go into this by myself but I would help testing. The big question is: will Espresso’s preview be able to deal with includes?
at the moment I have very little information about what espresso can and what it can’t do. We will just have to wait for the sugar documentation to mature. One thing I would really want would be Xcode like “parsing” of the document to build an index of functions and variables in documents. So far as the itemizers haven’t been covered in the wiki there is little I can do in this area.
I’ve now added more info on itemizers, and to answer your other questions: Espresso’s preview will not handle .php without a server running; and parsing of the document won’t be possible in 1.0.
Espresso’s preview will not handle .php without a server running.
That is based in the nature of php I guess. What I would need is simple: an easy means (shortcut) to save and upload the file I’m working on and tell Espresso’s preview simply to reload.
and parsing of the document won’t be possible in 1.0
What do you mean by that? No syntax-navigation (like code folding)? No Sugar at all for php? or simply no php-server build in?
That did sound rather vague. I meant document parsing to provide completions from functions in your own classes, for example. Folding and Navigator support is of course perfectly possible.
Any news on this sugar? I’m just a little bit frustrated to not be able to work with PHP in espresso, so I started my own sugar. Just would like to know what you managed to get to work, and which work we might be able to share.
Maybe we should get this sugar under some sort of version control and allowing others to help develop it. It would suck to do twice the amount of work, or rely on one individual to produce a sure to be popular sugar.
I’ll share my work tomorrow when I wake up in the morning (it’s 1am here in Finland) I have been quite busy during these last few days. I have focused on intelligent code sense, meaning that right suggestions are only shown in right context (for example keyword return is only offered inside a function and operator AND only when writing a conditional statement like an if clause). The work hasn’t been very fast since none of the “ready” sugars use this kind of structuring (css is the closest). But by all means I’ll share the code very soon…
@Lassi: Thank you very much Lassi, sounds really great! I’m looking forward your work.
@Derek: I really agree with you. Maybe having a SVN repository with all “public” sugars would be the best. Write protected, with some registered contributors for each one. Could not be so hard to set something like that up. Even updates would be really smooth with this. Any comment from Macrabbit?
I second you… SVN would be the very best solution!
So all the “developers of sugars” can load up the newest codelines “just in time” and “the normal” user has the possibility, to fetch these version from the repository to his Mac only minutes, after upload…
I’ll share my work tomorrow when I wake up in the morning (it’s 1am here in Finland) I have been quite busy during these last few days. I have focused on intelligent code sense, meaning that right suggestions are only shown in right context (for example keyword return is only offered inside a function and operator AND only when writing a conditional statement like an if clause). The work hasn’t been very fast since none of the “ready” sugars use this kind of structuring (css is the closest). But by all means I’ll share the code very soon…
Awesome! I really appreciate the initiative you took with this project. Can’t wait to see what you’ve done. Sounds interesting!
I’d really like to see how CodeSense for PHP turns out. Then it’s bye-bye Coda. :D