[TYPO3-ect] Eclipse Plugin Development

[Martin Ficzel]

Andreas Tschirpke schrieb:

>> i like that idea, just some days ago i posted a proposal for a typo3 rpc
>> interface to the dev list. i wanted to know weather this makes sense and
>> is worth the effort.

> I will have a look at that. What do you think about the existing RPC
> extension?

there are some xmlrpc lib extensions but they are just libaries so no
interface to the core is exposed yet. and there is the jeditvfs
extension. wich imho has some major design problems:

1. is implemented as a pagetype in the fe
	no be-rights can be checked
	no tce-main is used
	no field content checks
	....
2. is focused only on ts not on managing records so not very fexible,
for instance you cannot edit the ts-constants (at least i think you cannot).

3. no file resource management/editing wich is also important

thats why i think that an rpc interface should expose the powerfull
tce-main methods in a generalized way to the world and it should rely on
the typo3 backend right model.

>> i personally thought about the option to use flash editors in be-modules
>>  but a generalized rpc interface would make also your proposed eclipse
>> intergation possible. since i'm usually working with eclipse it would be
>> great to use it for managing typo3 too.

> Yes, an TYPO3 integrated editor, whether Flash, Java, or whatever based,
> will be helpful. But most time when I'm writting PHP code for a Plug-In
> I have to switch to another editor or my browser to edit the TS code. A
> TS editor integrated into Eclipse will make switching useless.

no i did'nt mean a flash ts-editor. thats something eclipse can do much
better. what i thought about is graphic editing with flash for
extensions wich store geometrical informations.

>> how can this be implemented in the typo3 backend?
> As we could access the database directly we don't actually need a
> backend implementation, do we?

when talking about the backend i mean a fully initialized tce-main
system with the typo3 right system in place. thats why i think that the
rpc interface should be implemented as a be-module. i did't mean
anything wich is visible for be users.

>> such a filestructure could be exposed in any rpc manner but i would
>> > suggest to use webDav because that would be useful for other tools
>> > aswell. a litte problem is the dualistic nature of pages because they
>> > are records and folders.
> Yes, couldn't this be solved by treating pages as "virtual" folders
> themselves which contatin virtual and/or real files? I think this
> matches your idea outlined above, doesn't it?

the point is that filesystems differ between collections and files (at
least all filesystems i know do that) and a typo3 page is both(folder
and record). i think the idea of disabling the moving and creating of
records is good since it will avoid a lot of poblems at least at the
beginning and will bring a big benefit to the users aswell.

regards Martin

PS: thinking about your master thesis there are some seperate working areas

- base

  - conceptual work
  - rpc-base
  - webdav acess for records based on rpc-base
    maybe an existing php-webdav lib can be used

- options

  - webdav fileadmin
  - xml-schemes for the different typo3 record types
  - ts-syntax highlighting inside ts xml files in eclipse

the first 3 steps will add a lot of options and flexibility to typo3 the
next 3 steps are nice to have features wich can be excluded from the
first version so you can keep the amount of work under control.