Properties support...

At a very first analysis the new properties functionality seems to be far inferior than the properties plugin. A couple of questions:

1) is it true or it's me?
2) can I use the properties plugins instead?
3) don't want to generate bad feelings, but wouldn't it be better to concentrate on functionality for which there is no plugin (such as basic tapestry support ;) )?

2 comments
Comment actions Permalink

Hi Davide,

At a very first analysis the new properties
functionality seems to be far inferior than the
properties plugin. A couple of questions:

1) is it true or it's me?

true

2) can I use the properties plugins instead?

It's not supported cause I'm absolutely have no time. Source code is bad organized and not documented at all and that's why it cannot be opened ;)

3) don't want to generate bad feelings, but wouldn't
it be better to concentrate on functionality for
which there is no plugin (such as basic tapestry
support ;) )?

Well may be PE can migrate to new PSI and provided basic support by me or anyone from community but see 2)

Anyway native support of any feature is good but I'm not sure that Tapestry plugin will be provided by JB cause they have Fabrique.

TIA,
Dmitry

0
Comment actions Permalink

At a very first analysis the new properties
functionality seems to be far inferior than the
properties plugin. A couple of questions:
1) is it true or it's me?

true


Sigh.

2) can I use the properties plugins instead?

It's not supported cause I'm absolutely have no time.
Source code is bad organized and not documented at
all and that's why it cannot be opened ;)


So you're basically causing it to die because you're ashamed of code quality?!? It's a pity: it is a great plugin, regardless of how clean the code is. Moreover, even if it is not documented it is always java code: it can't be too difficult (except if you named methods and classes in russian, uhm).

3) don't want to generate bad feelings, but

wouldn't

it be better to concentrate on functionality for
which there is no plugin (such as basic tapestry
support ;) )?

Well may be PE can migrate to new PSI and provided
basic support by me or anyone from community but see
2)


See my answer to 2) ;)

Anyway native support of any feature is good but I'm
not sure that Tapestry plugin will be provided by JB
cause they have Fabrique.


Fabrique is a visual editor: what could be good for tapestry is something that gives integrated features for page definition, ognl, and so on. But I guess I'll have to go with Spindle.

0

Please sign in to leave a comment.