Andrey,
Does an apology for delayed response help any for a 3 month delay?
If so, apologies for the late response.
I did, though, just want to say thanks for interest and offer, and we are still interested in this type of
verification of our mixed content API, but as you might have guessed, don't
anticipate much availability on our end until our current
multiple steams and main stream requirements are more predictable.
In the mean time, if you make in progress or have suggestions, please
let us know.
I would anticipate, though, that PHP integration with our DOM Model
and parsers would make the same basic assumptions we do for JSP
-- that is, that most JSP content is roughly well formed DOM content as
well (though not, strictly speaking, required to be by the runtime
oriented JSP spec).
In your experience, is this assumption not true for PHP?
Is source code like
<<?= $flag ? "tag1" : "tag2" ?> attr="value"/>
common in PHP world?
Thanks again,
| Andrey Platov <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 05/21/2005 07:07 AM
|
|
Hello Phillip,
Thank you very much for quick reply.
As a developers of full-featured Eclipse-based PHP IDE (http://www.xored.com/trustudio) we're tracking WTP project from its start and anxiously waiting for API clearance and SSE readiness.
Ideally, and due to PHP nature, document partitions out of PHP code can have any structure, which is not limited to widely used in practice HTML/XML/plain_text. Also PHP programer can break structure easy with something like <<?= $flag ? "tag1" : "tag2" ?> attr="value"/> or more strange things when PHP partitions overlaps outer document structure.
So main goals of our contribution could be:
1) Design & API Verification and completeness for our/others needs.
2) Clear example for community, interested in different SSE-based editors.
According to above we need to find balance between goal (1) and (2): focuse on (1) will add more complexity to example and decrease goal (2) value. Opposite, limiting use cases or having some assumptions like well-formed XML only for example, we will not reach goal (1).
So the question is in balance and please could you prioritize directions most interested to SSE team? From our side extending WST HTML editor with PHP partitions could be an interesting task as well.
Thanks and
Kind Regards,
Andrey
Phillip Avery wrote:
Hi Andry,
That's great!
I think that would be an extremely useful contribution.
If you're just getting started, I can try to point you to a couple places to start looking (to see what editor features you may want to contribute)
A good place to start looking is the how the cheat sheet editor (another sample editor) extends XML Editor.
It's located in the webtools repository under "wst/components/xml/examples/cheat-sheet-editor".
You'll probably want to look at overriding the StructuredTextViewerConfigurationXML so you can supply things like content assist, hover, highligher, etc...
We are currently still working on cleaning up our APIs, but sample editors like this help us determine what clients really need.
Let us know what type of work you'd like to do for this, or if you have any questions.
Thanks,
Phil
--- - - - - -
Phillip Avery
Structured Source Editor
919 254 8063
[EMAIL PROTECTED]
| Andrey Platov <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 05/20/2005 03:49 AM
|
|
We'd like to help with the item: Sample PHP Editor
Sincerely,
Andrey Platov
xored software
http://www.xored.com
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
