From: Antonio <aaa...@gm...> - 2010-02-03 02:10:01
|
I know Semantic Forms supports the fckeditor/mw-extension on the free-text field in the forms. I don't know if there's some technical reason on why it's not supported on text type properties' fields, since wiki syntax is accepted on them (and fckeditor/mw-extension from what I understand does generate plain wiki syntax). I also read that fckeditor/mw-extension can have several instances working in the same page. So: 1) do you know (and can say) the reason why it's not yet supported? 2) can you give me some starting hints/clues on how to hack Semantic Forms in order to accomplish that? (eventually, just a few buttons would be enough, e.g. bold and italic text). Thanks, -- Antonio |
From: Yaron K. <ya...@gm...> - 2010-02-03 04:58:47
|
Hi, There's no good reason why FCKeditor isn't supported for normal textareas in Semantic Forms; as you say, it's doable. If someone wanted to write the patch to add support for it, I'd gladly add it to the code. -Yaron On Tue, Feb 2, 2010 at 8:42 PM, Antonio <aaa...@gm...> wrote: > I know Semantic Forms supports the fckeditor/mw-extension on the free-text > field in the forms. > > I don't know if there's some technical reason on why it's not supported on > text type properties' fields, since wiki syntax is accepted on them (and > fckeditor/mw-extension from what I understand does generate plain wiki > syntax). I also read that fckeditor/mw-extension can have several > instances working in the same page. So: > > 1) do you know (and can say) the reason why it's not yet supported? > > 2) can you give me some starting hints/clues on how to hack Semantic Forms > in order to accomplish that? (eventually, just a few buttons would be > enough, e.g. bold and italic text). > > Thanks, > > -- > Antonio > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Antonio O. <an...@li...> - 2010-02-21 17:30:10
|
Bump. Since no one seems going to jump into this, I'm not the best one that could make it but nevertheless I would like to try, because I think it's really important. As I'm a bit lost in the code, some clues on where I should focus into SF files would be very appreciated and useful. To be honest, I'd prefer something like Wymeditor [1] instead of FCK, but I can't get MeanEditor extension [2] to work, so I'll go with FCK for Mediawiki which seems working almost fine. Btw anytime feel free to send me your solution. [1] http://www.wymeditor.org/ [2] http://www.mediawiki.org/wiki/Extension:MeanEditor -- Antonio > Hi, > > There's no good reason why FCKeditor isn't supported for normal > textareas in > Semantic Forms; as you say, it's doable. If someone wanted to write the > patch to add support for it, I'd gladly add it to the code. > > -Yaron > > On Tue, Feb 2, 2010 at 8:42 PM, Antonio <aaa...@gm...> wrote: > >> I know Semantic Forms supports the fckeditor/mw-extension on the >> free-text >> field in the forms. >> >> I don't know if there's some technical reason on why it's not supported >> on >> text type properties' fields, since wiki syntax is accepted on them (and >> fckeditor/mw-extension from what I understand does generate plain wiki >> syntax). I also read that fckeditor/mw-extension can have several >> instances working in the same page. So: >> >> 1) do you know (and can say) the reason why it's not yet supported? >> >> 2) can you give me some starting hints/clues on how to hack Semantic >> Forms >> in order to accomplish that? (eventually, just a few buttons would be >> enough, e.g. bold and italic text). >> >> Thanks, >> >> -- >> Antonio |
From: Yaron K. <ya...@gm...> - 2010-02-22 05:23:49
|
Hi, I wouldn't really call this a bump, more a belated reply... in any case, see /includes/SF_FormPrinter.inc in the SF code for most (or all) of the code handling the FCKeditor extension. I assume you would need something like this code, but within the textAreaHTML() function in the file /includes/SF_FormInputs.inc. -Yaron On Sun, Feb 21, 2010 at 12:29 PM, Antonio Orlando <an...@li...> wrote: > Bump. > > Since no one seems going to jump into this, I'm not the best one that > could make it but nevertheless I would like to try, because I think it's > really important. As I'm a bit lost in the code, some clues on where I > should focus into SF files would be very appreciated and useful. To be > honest, I'd prefer something like Wymeditor [1] instead of FCK, but I > can't get MeanEditor extension [2] to work, so I'll go with FCK for > Mediawiki which seems working almost fine. > > Btw anytime feel free to send me your solution. > > [1] http://www.wymeditor.org/ > [2] http://www.mediawiki.org/wiki/Extension:MeanEditor > > -- > Antonio > > > > Hi, > > > > There's no good reason why FCKeditor isn't supported for normal > > textareas in > > Semantic Forms; as you say, it's doable. If someone wanted to write the > > patch to add support for it, I'd gladly add it to the code. > > > > -Yaron > > > > On Tue, Feb 2, 2010 at 8:42 PM, Antonio <aaa...@gm...> wrote: > > > >> I know Semantic Forms supports the fckeditor/mw-extension on the > >> free-text > >> field in the forms. > >> > >> I don't know if there's some technical reason on why it's not supported > >> on > >> text type properties' fields, since wiki syntax is accepted on them (and > >> fckeditor/mw-extension from what I understand does generate plain wiki > >> syntax). I also read that fckeditor/mw-extension can have several > >> instances working in the same page. So: > >> > >> 1) do you know (and can say) the reason why it's not yet supported? > >> > >> 2) can you give me some starting hints/clues on how to hack Semantic > >> Forms > >> in order to accomplish that? (eventually, just a few buttons would be > >> enough, e.g. bold and italic text). > >> > >> Thanks, > >> > >> -- > >> Antonio > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Antonio O. <an...@li...> - 2010-02-22 13:07:07
|
Thanks, while waiting for some reply I was already looking into those files and integrating FCK seems to me quite a bit of a mess; I'm trying to integrate Xinha [1], which seems more doable, even if it means losing the wiki markup functionality that FCK for MediaWiki offers. [1] http://xinha.webfactional.com/ By the way I have to underline the word "seem", for both my previous sentences. -- Antonio > Hi, > > I wouldn't really call this a bump, more a belated reply... in any case, > see > /includes/SF_FormPrinter.inc in the SF code for most (or all) of the code > handling the FCKeditor extension. I assume you would need something like > this code, but within the textAreaHTML() function in the file > /includes/SF_FormInputs.inc. > > -Yaron |
From: Krabina B. <kr...@kd...> - 2010-02-22 14:13:44
|
My preference would be to make the standard MediaWiki editor available in the free text fields of SF (and maybe in other text/textarea fields). This editor is easy to use and users know it from editing regular mediawiki pages. Having a more powerful external editor makes things more complex and is not always needed. I wish someone could come up with a solution for that. bye, Bernhard ----- "Antonio Orlando" <an...@li...> schrieb: > Thanks, while waiting for some reply I was already looking into those > > files and integrating FCK seems to me quite a bit of a mess; I'm > trying to > integrate Xinha [1], which seems more doable, even if it means losing > the > wiki markup functionality that FCK for MediaWiki offers. > > [1] http://xinha.webfactional.com/ > > By the way I have to underline the word "seem", for both my previous > > sentences. > > -- > Antonio > > > > Hi, > > > > I wouldn't really call this a bump, more a belated reply... in any > case, > > see > > /includes/SF_FormPrinter.inc in the SF code for most (or all) of the > code > > handling the FCKeditor extension. I assume you would need something > like > > this code, but within the textAreaHTML() function in the file > > /includes/SF_FormInputs.inc. > > > > -Yaron > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user |
From: Antonio O. <an...@li...> - 2010-02-23 01:25:13
|
Long story short (straight question mode): ========================================== If I build variable $foo into a function of "extensions\SemanticForms\includes\SF_FormInputs.inc" (textAreaHTML), how can I echo its content into the <head></head> section of the page? Long story (no need to read it, the short story is enough): =========================================================== I'm trying to integrate the Xinha wysiwyg editor into the textarea fields of Semantic Forms. I've almost succeeded, but I need help on a thing. I have a Xinha.php script included in LocalSettings.php, which does $wgOut->addscript of the Xinha javascript stuff we have to include in the page for Xinha to do its job; but I need one row of this js code to be a list of the ids of the non-autocomplete SF textareas appearing in the page when "editing with form": so I'm building this list into the function "textAreaHTML" in "extensions\SemanticForms\includes\SF_FormInputs.inc" (variable "$sfgWysiwygTextAreas"). But, I don't know how to let "extensions\Xinha\Xinha.php" know the value of that variable "$sfgWysiwygTextAreas" built into SF_FormInputs.inc. How can I do that, or achieve my purpose in some similar way? Said in a simpler way, if in the Form there are <textarea id="input_2"...>, <textarea id="input_3"...>, <textarea id="input_4"...>, I build into "SF_FormInputs.inc" the variable $sfgWysiwygTextAreas = "'input_2', 'input_3', 'input_4'". Then, I need this variable content available into the script "extensions\Xinha\Xinha.php", so that I can put it into the javascript code that needs to be written into the page to let Xinha wysiwyg editor appear on textarea fields with id "input_2", "input_3" and "input_4". Someone can help? -- Antonio > Bump. > > Since no one seems going to jump into this, I'm not the best one that > could make it but nevertheless I would like to try, because I think it's > really important. As I'm a bit lost in the code, some clues on where I > should focus into SF files would be very appreciated and useful. To be > honest, I'd prefer something like Wymeditor [1] instead of FCK, but I > can't get MeanEditor extension [2] to work, so I'll go with FCK for > Mediawiki which seems working almost fine. > > Btw anytime feel free to send me your solution. > > [1] http://www.wymeditor.org/ > [2] http://www.mediawiki.org/wiki/Extension:MeanEditor > |
From: Yaron K. <ya...@gm...> - 2010-02-23 02:30:28
|
Hi, I didn't read the long story, :) but to answer your question, you just need to call: global $wgOut; [if it wasn't declared already] $wgOut->addStyle("...text here..."); -Yaron On Mon, Feb 22, 2010 at 8:25 PM, Antonio Orlando <an...@li...> wrote: > Long story short (straight question mode): > ========================================== > If I build variable $foo into a function of > "extensions\SemanticForms\includes\SF_FormInputs.inc" (textAreaHTML), how > can I echo its content into the <head></head> section of the page? > > > Long story (no need to read it, the short story is enough): > =========================================================== > I'm trying to integrate the Xinha wysiwyg editor into the textarea fields > of Semantic Forms. I've almost succeeded, but I need help on a thing. I > have a Xinha.php script included in LocalSettings.php, which does > $wgOut->addscript of the Xinha javascript stuff we have to include in the > page for Xinha to do its job; but I need one row of this js code to be a > list of the ids of the non-autocomplete SF textareas appearing in the page > when "editing with form": so I'm building this list into the function > "textAreaHTML" in "extensions\SemanticForms\includes\SF_FormInputs.inc" > (variable "$sfgWysiwygTextAreas"). But, I don't know how to let > "extensions\Xinha\Xinha.php" know the value of that variable > "$sfgWysiwygTextAreas" built into SF_FormInputs.inc. How can I do that, or > achieve my purpose in some similar way? > > Said in a simpler way, if in the Form there are <textarea > id="input_2"...>, <textarea id="input_3"...>, <textarea id="input_4"...>, > I build into "SF_FormInputs.inc" the variable $sfgWysiwygTextAreas = > "'input_2', 'input_3', 'input_4'". Then, I need this variable content > available into the script "extensions\Xinha\Xinha.php", so that I can put > it into the javascript code that needs to be written into the page to let > Xinha wysiwyg editor appear on textarea fields with id "input_2", > "input_3" and "input_4". Someone can help? > > -- > Antonio > > > > > Bump. > > > > Since no one seems going to jump into this, I'm not the best one that > > could make it but nevertheless I would like to try, because I think it's > > really important. As I'm a bit lost in the code, some clues on where I > > should focus into SF files would be very appreciated and useful. To be > > honest, I'd prefer something like Wymeditor [1] instead of FCK, but I > > can't get MeanEditor extension [2] to work, so I'll go with FCK for > > Mediawiki which seems working almost fine. > > > > Btw anytime feel free to send me your solution. > > > > [1] http://www.wymeditor.org/ > > [2] http://www.mediawiki.org/wiki/Extension:MeanEditor > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Antonio O. <an...@li...> - 2010-02-23 02:32:22
|
Solved, putting the command "global $sfgWysiwygTextAreas;" into: - LocalSettings.php - function textAreaHTML in "extensions\SemanticForms\includes\SF_FormInputs.inc" - "extensions\Xinha\Xinha.php"" -- Antonio > Long story short (straight question mode): > ========================================== > If I build variable $foo into a function of > "extensions\SemanticForms\includes\SF_FormInputs.inc" (textAreaHTML), > how can I echo its content into the <head></head> section of the page? > Long story (no need to read it, the short story is enough): > =========================================================== > I'm trying to integrate the Xinha wysiwyg editor into the textarea > fields of Semantic Forms. I've almost succeeded, but I need help on a > thing. I have a Xinha.php script included in LocalSettings.php, which > does $wgOut->addscript of the Xinha javascript stuff we have to include > in the page for Xinha to do its job; but I need one row of this js code > to be a list of the ids of the non-autocomplete SF textareas appearing > in the page when "editing with form": so I'm building this list into the > function "textAreaHTML" in > "extensions\SemanticForms\includes\SF_FormInputs.inc" (variable > "$sfgWysiwygTextAreas"). But, I don't know how to let " know the value > of that variable "$sfgWysiwygTextAreas" built into SF_FormInputs.inc. > How can I do that, or achieve my purpose in some similar way? > Said in a simpler way, if in the Form there are <textarea > id="input_2"...>, <textarea id="input_3"...>, <textarea > id="input_4"...>, I build into "SF_FormInputs.inc" the variable > $sfgWysiwygTextAreas = "'input_2', 'input_3', 'input_4'". Then, I need > this variable content available into the script > "extensions\Xinha\Xinha.php", so that I can put it into the javascript > code that needs to be written into the page to let Xinha wysiwyg editor > appear on textarea fields with id "input_2", "input_3" and "input_4". > Someone can help? > -- > Antonio > |
From: Antonio O. <an...@li...> - 2010-02-23 02:37:12
|
Sorry no: still not solved. I thought it was solved by adding the global command in LocalSettings.php but it didn't, I forgot to comment a test line. -- Antonio > Solved, putting the command "global $sfgWysiwygTextAreas;" into: > - LocalSettings.php > - function textAreaHTML in > "extensions\SemanticForms\includes\SF_FormInputs.inc" > - "extensions\Xinha\Xinha.php"" > -- > Antonio > >> Long story short (straight question mode): >> ========================================== >> If I build variable $foo into a function of > >> "extensions\SemanticForms\includes\SF_FormInputs.inc" (textAreaHTML), > >> how can I echo its content into the <head></head> section of the page? >> Long story (no need to read it, the short story is enough): >> =========================================================== >> I'm trying to integrate the Xinha wysiwyg editor into the textarea > >> fields of Semantic Forms. I've almost succeeded, but I need help on a > >> thing. I have a Xinha.php script included in LocalSettings.php, which > >> does $wgOut->addscript of the Xinha javascript stuff we have to include >> > in the page for Xinha to do its job; but I need one row of this js >> code > to be a list of the ids of the non-autocomplete SF textareas >> appearing > in the page when "editing with form": so I'm building this >> list into the > function "textAreaHTML" in > >> "extensions\SemanticForms\includes\SF_FormInputs.inc" (variable > >> "$sfgWysiwygTextAreas"). But, I don't know how to let " know the value >> > of that variable "$sfgWysiwygTextAreas" built into SF_FormInputs.inc. >> > How can I do that, or achieve my purpose in some similar way? >> Said in a simpler way, if in the Form there are <textarea > >> id="input_2"...>, <textarea id="input_3"...>, <textarea > >> id="input_4"...>, I build into "SF_FormInputs.inc" the variable > >> $sfgWysiwygTextAreas = "'input_2', 'input_3', 'input_4'". Then, I need >> > this variable content available into the script > >> "extensions\Xinha\Xinha.php", so that I can put it into the javascript >> > code that needs to be written into the page to let Xinha wysiwyg >> editor > appear on textarea fields with id "input_2", "input_3" and >> "input_4". > Someone can help? >> -- >> Antonio |