Michaël Michaud wrote:
> Hi Jukka,
> > What do you do with the attributes? Do you discard them all for the whole
> layer or do you give them to features as long as they last and then fill null
> attributes for the remaining orphan features?
> Second option, I fill null attributes for remaining or
hi All,
in the process of adding DB Query from LReeder to PLUS, i started extending the
usage of default-plugins.xml, via additional tags and attributes, in
PluginManager and moving all currently hardcoded plugins from
JumpConfiguration, OJConfiguration over to dewfault-plugins.xml.
result will
The terrific Ede!
That's what I was planning to do, limited to my developing skills. But
you've got it before.
With these modification it is possible to customize whatever type of OJ
usage.
thanks again
Peppe
2013/10/8
> hi All,
>
> in the process of adding DB Query from LReeder to PLUS, i sta
had it on my schedule a long time already. the whole configuartion is so messed
up and missing clear structure that adding/removing or placing menu entries was
a real painful experience.
i tend to cross bridges when i reach them, eventually custom placing DB Query
lead me right to this bridge.
Hi,
>
> What do you do with the attributes? Do you discard them all for the whole
> layer or do you give them to features as long as they last and then fill null
> attributes for the remaining orphan features?
>> Second option, I fill null attributes for remaining orphans. When the dbf
>> exists,
Hi,
> in the process of adding DB Query from LReeder to PLUS, i started extending
> the usage of default-plugins.xml, via additional tags and attributes, in
> PluginManager and moving all currently hardcoded plugins from
> JumpConfiguration, OJConfiguration over to dewfault-plugins.xml.
> result
