Re: [cowiki-dev] Releasing coWiki with the "working" parser

Paul Hanchett <[email protected]> Mon, 11 Jul 2005 12:38:00 -0700
Newsgroups gmane.comp.php.cowiki.devel
Message-ID <[email protected]>
The feature(s) I want are to be able to embed images and (html) 
documents in a coWiki page without needing "special" access to the 
server coWiki resides on. 

I am also thinking more and more that the wiki language should be 
*totally* hidden from the user in a WYSIWYG editor on the front end.  
That would be a huge improvement in "quick" and "easy to use".  I would 
not go far beyond some basic formatting, at least at first.

Paul

Archie Campbell wrote:

> Give up? I've a couple of unresolved issues, and I'm snowed under at 
> the moment. I'll try to get on top after next weekend (17th). Sorry.
>
> The HTML & especially the images & multimedia are things I'd like to 
> tackle.
>
> I don't care if my stuff (just the parser at present) takes a while to 
> be aired.
>
> Regards,
>
> Archie
>
> Daniel T. Gorski wrote:
>
>>On 07 Jul 23:58, Paul Hanchett wrote:
>>
>>  
>>
>>>Daniel T. Gorski wrote:
>>>    
>>>
>>>>What do you think about releasing Fullerene with the old working parser
>>>>and the new features so far? [...]
>>>>      
>>>>
>>>I will consider this Daniel.  I do not think that the changes we have 
>>>made thus far constitute a major release-- What user visible changes are 
>>>there, aside from the installer (which admittedly is a very nice 
>>>feature...)?
>>>    
>>>
>>Do not forget the migration to InnoDB, respectively ACID transactions and
>>addition of MySQLi persistance layer.
>>  
>>
>>>The major weakness in coWiki is that there is no way to integrate HTML 
>>>documents or images from other systems into the wiki display. [...]
>>>    
>>>
>>
>>Hopefully we see results in this case. What about a RC (a release candiate)
>>with the old parser?
>>
>>Did Archie give up?
>>
>>regards dtg
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [email protected]
>>For additional commands, e-mail: [email protected]
>>  
>>