Re: [fossil-users] Fossil and tinymce integration

2009-10-30 Thread Twylite
Rene de Zwart wrote:
> Twylite wrote
>   
>> Please no!  TinyMCE is a bloated monstrosity and produces _horrible_
>> HTML.  We're struggling to migrate an intranet system from Drupal to
>> PmWiki on account of the terrible markup produced by TinyMCE.
>> 
> Well if you  prefer xyz AND!! it has the same kind of interfacing as
> tinyMCE (e.g. recognizing text areas by name. Because the text areas
> doesn't have ids in fossil.) than the drill is exactly the same.
>   
My apologies -- I had thought there was a requirement to include TinyMCE 
with the fossil distribution (reading "repository" as repository of 
Fossil's own source).  On re-reading in full I was clearly wrong ;)

Regards,
Twylite
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Fossil and tinymce integration

2009-10-29 Thread Rene de Zwart
>
> On 29 Oct 2009, at 14:13, Rene de Zwart wrote:
>
>> Twylite wrote
>>> Rene de Zwart wrote:
 I just finished integrating tiny mce.
 To start with the downside -;( 'You need to make tinyMce part of the
 Repository!'

>>> Please no!  TinyMCE is a bloated monstrosity and produces _horrible_
>>> HTML.  We're struggling to migrate an intranet system from Drupal to
>>> PmWiki on account of the terrible markup produced by TinyMCE.
>>>
>>> If some sort of edit helper is required, please consider MarkItUp
>>> (http://markitup.jaysalvat.com/home/) rather than a WYSIWYG.
>>> MarkItUp
>>> is built on jQuery, which provides the side benefit of giving
>>> Fossil and
>>> excellent JavaScript library for UI enhancement, AJAX features, etc.
>
> I agree with Twylite about TinyMCE generating horrible markup,
> although it does generate code that survives HTML email bodies - the
> most degrading place for CSS as email clients are restrictive and
> inconsistent. I reckon a limited feature WYSIWYG editor would be the
> best idea as it might not be programmers or people familiar with
> markup editing documentation or submitting tickets - users of software
> shouldn't need to learn syntax in order to contribute and communicate
> effectively. In addition to this, having an editor that could get out
> of the way for folk who can write markup would also be a good idea.
>
> Just my £0.02. Your thoughts?
>
> ~ James
Well if you agree with him then you probably want this :-).

mkdir markitup
mkdir markitup/javascript
fossil new markitup.fsl
fossil ui markitup.fsl {configure the project)
download markitup and jquery
unzip in markitup/javascript, cd latest, mv * .., rmdir latest
copy jquery-js to javascript/jquery.js
cd markitup
fossil open ../markitup.fsl
fossil add javascript
fossil commit -m "added markitup an jquery to the project"
fossil ui
select admin/headers add after the  put
  
  

  
  
  

and save
select admin/footer add above the first line


  var m = document.getElementsByTagName('textarea')
  var l = m.length
  var n
 var mySettings = {
nameSpace:   "html", // Useful to prevent multi-instances CSS
conflict
onShiftEnter:{keepDefault:false, replaceWith:'
\n'}, onCtrlEnter: {keepDefault:false, openWith:'\n

', closeWith:'

\n'}, onTab: {keepDefault:false, openWith:' '}, markupSet: [ {name:'Heading 1', key:'1', openWith:'', closeWith:'', placeHolder:'Your title here...' }, {name:'Heading 2', key:'2', openWith:'', closeWith:'', placeHolder:'Your title here...' }, {name:'Heading 3', key:'3', openWith:'', closeWith:'', placeHolder:'Your title here...' }, {name:'Heading 4', key:'4', openWith:'', closeWith:'', placeHolder:'Your title here...' }, {name:'Heading 5', key:'5', openWith:'', closeWith:'', placeHolder:'Your title here...' }, {name:'Heading 6', key:'6', openWith:'', closeWith:'', placeHolder:'Your title here...' }, {name:'Paragraph', openWith:'', closeWith:'

' }, {separator:'---' }, {name:'Bold', key:'B', openWith:'', closeWith:'' }, {name:'Italic', key:'I', openWith:'', closeWith:'' }, {name:'Stroke through', key:'S', openWith:'', closeWith:'' }, {separator:'---' }, {name:'Ul', openWith:'
    \n', closeWith:'
\n' }, {name:'Ol', openWith:'
    \n', closeWith:'
\n' }, {name:'Li', openWith:'
  • ', closeWith:'
  • ' }, {separator:'---' }, {name:'Picture', key:'P', replaceWith:'http://]!]"; alt="[![Alternative text]!]" />' }, {name:'Link', key:'L', openWith:'http://]!]";(!( title="[![Title]!]")!)>', closeWith:'', placeHolder:'Your text to link...' }, {separator:'---' }, {name:'Clean', replaceWith:function(h) { return h.selection.replace(/<(.*?)>/g, "") } }, {name:'Preview', call:'preview', className:'preview' } ] } for(var i=0 ;i < l;i++){ n = m[i].name if( 'comment' == n || 'cmappnd' == n || "w" == n){ m[i].id = n $(document).ready(function() { $("#" + n).markItUp(mySettings); }); } } and save and DONE. Congratulations you have markit in fossil for ticket and wiki. Rene ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

    Re: [fossil-users] Fossil and tinymce integration

    2009-10-29 Thread James Gruessing
    
    On 29 Oct 2009, at 14:13, Rene de Zwart wrote:
    
    > Twylite wrote
    >> Rene de Zwart wrote:
    >>> I just finished integrating tiny mce.
    >>> To start with the downside -;( 'You need to make tinyMce part of the
    >>> Repository!'
    >>>
    >> Please no!  TinyMCE is a bloated monstrosity and produces _horrible_
    >> HTML.  We're struggling to migrate an intranet system from Drupal to
    >> PmWiki on account of the terrible markup produced by TinyMCE.
    >>
    >> If some sort of edit helper is required, please consider MarkItUp
    >> (http://markitup.jaysalvat.com/home/) rather than a WYSIWYG.   
    >> MarkItUp
    >> is built on jQuery, which provides the side benefit of giving  
    >> Fossil and
    >> excellent JavaScript library for UI enhancement, AJAX features, etc.
    
    I agree with Twylite about TinyMCE generating horrible markup,  
    although it does generate code that survives HTML email bodies - the  
    most degrading place for CSS as email clients are restrictive and  
    inconsistent. I reckon a limited feature WYSIWYG editor would be the  
    best idea as it might not be programmers or people familiar with  
    markup editing documentation or submitting tickets - users of software  
    shouldn't need to learn syntax in order to contribute and communicate  
    effectively. In addition to this, having an editor that could get out  
    of the way for folk who can write markup would also be a good idea.
    
    Just my £0.02. Your thoughts?
    
    ~ James
    Lasgo Chrysalis Limited. Registered in England & Wales No. 1380166.
    Part of the Chrysalis Plc. 
    Registered office: The Chrysalis Building, Bramley Road, London W10 6SP
    
    ___
    fossil-users mailing list
    fossil-users@lists.fossil-scm.org
    http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
    
    

    Re: [fossil-users] Fossil and tinymce integration

    2009-10-29 Thread Rene de Zwart
    Twylite wrote
    > Rene de Zwart wrote:
    >> I just finished integrating tiny mce.
    >> To start with the downside -;( 'You need to make tinyMce part of the
    >> Repository!'
    >>
    > Please no!  TinyMCE is a bloated monstrosity and produces _horrible_
    > HTML.  We're struggling to migrate an intranet system from Drupal to
    > PmWiki on account of the terrible markup produced by TinyMCE.
    >
    > If some sort of edit helper is required, please consider MarkItUp
    > (http://markitup.jaysalvat.com/home/) rather than a WYSIWYG.  MarkItUp
    > is built on jQuery, which provides the side benefit of giving Fossil and
    > excellent JavaScript library for UI enhancement, AJAX features, etc.
    
    Well if you  prefer xyz AND!! it has the same kind of interfacing as
    tinyMCE (e.g. recognizing text areas by name. Because the text areas
    doesn't have ids in fossil.) than the drill is exactly the same.
    
    What I did doesn't need to alter fossil. In this way one can test out
    support for wysiwyg html editing and decide if it is worth all the
    trouble.
    
    It does add the xyz javascript library to every page. But that doesn't
    means that fossil is using it. That would require modifying every page.
    Which is a major undertaking and creating a dependency on xyz.
    
    BTW I did a bit of testing and I found 3 areas which allow html
    elements comment,cmappnd (in ticket) and element w (in wikiedit) so it
    makes more sense to test for
    ('comment' == n || 'cmappnd' == n || "w" == n)
    then for
    ('header' != n && 'footer' != n && 'css' != n)
    
    Rene
    
    ___
    fossil-users mailing list
    fossil-users@lists.fossil-scm.org
    http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
    
    

    Re: [fossil-users] Fossil and tinymce integration

    2009-10-29 Thread Twylite
    Hi,
    
    Rene de Zwart wrote:
    > I just finished integrating tiny mce.
    > To start with the downside -;( 'You need to make tinyMce part of the
    > Repository!'
    >   
    Please no!  TinyMCE is a bloated monstrosity and produces _horrible_ 
    HTML.  We're struggling to migrate an intranet system from Drupal to 
    PmWiki on account of the terrible markup produced by TinyMCE. 
    
    If some sort of edit helper is required, please consider MarkItUp 
    (http://markitup.jaysalvat.com/home/) rather than a WYSIWYG.  MarkItUp 
    is built on jQuery, which provides the side benefit of giving Fossil and 
    excellent JavaScript library for UI enhancement, AJAX features, etc.
    
    Regards,
    Twylite
     
    ___
    fossil-users mailing list
    fossil-users@lists.fossil-scm.org
    http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users