Re: [Columba-devel] Mambo suggestions

[Frederik D. <ma...@fr...>]

>
> Hi, no, I actually put it on hold when I stumbled upon those issues with
> the class loaders. I went on vacation and since I got back to work
> things have been a bit hectic because I have a release to deliver by the
> end of the month, so I must confess I have been avoiding to code after
> work (need to get some rest eheh).

Man, I know *exactly* what you mean. Its really hard to design/code
software all day at work and then coming home and working on Columba!

>
> But I'm going to get back to it ASAP since I'm using it as a testbed to
> check what is possible to do with a real-world application, what issues
> arise, etc.
>
> Since you all have done a lot of work I should probably merge the
> branches again. You'll certainly be notified when I get back to it :-)
>

Definitly. I really recommend this to you. The plugin-system is much
cleaner now. Especially, the concept of a plugin, extension, extension
point, menu extensions is much cleaner now. Additionally, the menu code is
decoupled from the plugin system. So, it should be working nicely with
your scripting ideas.

> Thursday sounds great to me. Let me know of what time you're thinking
> for this telco. If it isn't much to ask and if you're creating an
> appointment on your calendar send it to me, that way I certainly won't
> forget :-)
>

If I would use Outlook, I'd send you an appointment ;-) What about 7 or
8pm on Thursday then?

I'd especially like to talk to you about the basic concept of writing
scripts. Are we writing scripts which contain basically the same code as
plugins? Or do we write special types of plugins, for example menu
extensions, listeners for selection changes, commands, etc. I'd say we
probably start with the first point, but move over quickly to the second
suggestions, because this would speed up script development a lot.
Additionally, do we need metadata which accompany scripts?

Cheers,
-Frederik