Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - sent

Pages: [1]
Ideas / Re: Document publication method?
« on: May 19, 2009, 01:04:04 pm »
The most prominent reason is:

I would like to integrate OpenGoo into [at least to cooperate with] my CMS (of choice), ultimately: as part of!


If requested... I could build [and specify and document] an experimental handler (PHP) and the pushable XML document -- PM me.

Ideas / Re: Mindmap / FreeMind
« on: May 09, 2009, 10:02:07 am »
I also second implementing Freemind. It would be wonderfull :D

There are only a few (development) problems:
  • integrating Freemind web based requires a new/altered version: the *.mm should be able to be edited ONLINE.
  • Also it should require the implementation of OpenGoo with a co-operating and secure document exchange layer.

also I would like to see adapted in Freemind:
  • bi-lingual support, for example the Wordpress//qTranslate markup: [:en] QuickTags and the default <!--:en--> Tag
  • authentication
  • version control
  • per-node-based-rights
  • CSS / classes
  • a Legend

and keep in mind:
  • Freemind is single-user/unauthenticated based
  • Freemind has no version support (yet)
  • Freemind is not (yet) able to include external pages, e.g. notes (as a DIV from HTML) or include other mindmaps directly into it's own

Ideas / Document publication method?
« on: May 09, 2009, 09:59:39 am »
I would like to find a way to PUBLISH a document/object from within OpenGoo, by use of a bridge-like-handler-function, into a custom CMS.

for example:
I would like to publish the documentation-project into my favorite CMS (e.g. MediaWiki, Wordpress, ..., or any custom build one). So I would like to use an interface in OpenGoo to select the publication-handler (e.g. FTP, or script with a post-form). After submit, OpenGoo connects to the handler, pushes the document and relevant meta-information. The handler might pop an additional-form for missing information or a error/success-message.

The post-form might contain only the connection-data (handler-account, trusted-secret/password) and an uploaded XML-file (opengoo:username, cached session [cms:credentials; cms:account, cms:password, ...], title, content, language(s), meta-data, cms:target_of_publication, ...)

The connected to handler would not be part of OpenGoo; It should comply to the defined documentation and also carry a meta-xml file to define the requested and cache-able information, so communication and authentication could be automated. E.g. The OpenGoo user only would require to tell its own cms:credentials.

I'm not sure how far the development of these kind of features are.. but if it is already implemented; It would be 'quite easy' for the community to create for any popular CMS a working handler. In that case; where is the documentation?


General Discussion / Re: Promoting OpenGoo. And OpenGoo on Wikipedia
« on: December 19, 2008, 11:34:12 am »
+ Extended the charts within

Nederlands / Re: Dutch translation
« on: December 19, 2008, 11:29:48 am »
and I just sent a mail of offering to that too :-D


Nederlanders zijn gewoon brutaal genoeg om hun eigen vertaling te eisen en te regelen.

Scooby ik wil ook graag de bijna afzijnde versie.

Pages: [1]