[Portfolio] Question about editor in forms for OSP

[Nate Angell]

Thanks Sean!

So Brian, based on this list, I'm thinking your portfolio experience may be
diminished by moving to the global version of FCKEditor unless these changes
are carried over. Maybe add this whole thread to the rSmart issue ticket to
make sure we are aware of it?

Wondering if someone from UMich might weigh in on how they handle
this...Noah?

- Nate

On Thu, Jul 29, 2010 at 5:59 PM, Sean Keesler
<sean.keesler at threecanoes.com>wrote:

> What I meant to say was....
>
> The editor config changes are in the custom richText-field template in
> formCreate-wysiwyg.xsl in authoring/xsl.
>
> Some changes I see:
>
> The editor is displayed a little bigger (600px x 460px)
> There are custom skins that style the editor content based on the selection
> of theme field on the form
> The content is periodically autosaved on the client side
> There is a custom toolbar to hide/show the Sakai tool menu and maximize the
> size of the editor
> The editor is the focus (cursor placed in that field)
>
> There is a custom config.js and portfolio.js file  that are used as well.
>
> Sean Keesler
> 130 Academy Street
> Manlius, NY 13104
> 315-682-0830
> sean.keesler at threecanoes.com
>
>
>
> On Thu, Jul 29, 2010 at 8:43 PM, Sean Keesler <
> sean.keesler at threecanoes.com> wrote:
>
>>
>> Sean Keesler
>> 130 Academy Street
>> Manlius, NY 13104
>> 315-682-0830
>> sean.keesler at threecanoes.com
>>
>>
>>
>> On Thu, Jul 29, 2010 at 8:03 PM, Nate Angell <nangell at rsmart.com> wrote:
>>
>>> Sean:
>>>
>>> Is there a good place to learn more about these custom config options of
>>> Michigan's? I'm not seeing them in the Page Composer wiki:
>>>
>>> http://confluence.sakaiproject.org/display/OSP/Michigan+Scaffolded+Portfolio+Authoring+Work
>>>
>>> - Nate
>>>
>>>
>>> On Thu, Jul 29, 2010 at 4:29 PM, Sean Keesler <
>>> sean.keesler at threecanoes.com> wrote:
>>>
>>>> The OSP implementation at Marist is derived from the 2.5 Page Composer
>>>> release.
>>>> The custom form renderers use the FCK editor that came with that
>>>> distribution.
>>>>
>>>> As Hongbo mentions, you can swap that FCK editor out if you are not
>>>> using Michigan's custom config options, you can swap it out.
>>>>
>>>>
>>>> Sean Keesler
>>>> 130 Academy Street
>>>> Manlius, NY 13104
>>>> 315-682-0830
>>>> sean.keesler at threecanoes.com
>>>>
>>>>
>>>> On Thu, Jul 29, 2010 at 3:30 PM, hongbo zhang <hbzhang at vt.edu> wrote:
>>>>
>>>>>   In the PortfolioAdmin site, under the system directory, there is a
>>>>> file called formCreate.xslt.
>>>>>
>>>>>
>>>>>
>>>>> In line 38,  you can find this:
>>>>>
>>>>>
>>>>>
>>>>> <script type="text/javascript" language="JavaScript"
>>>>> src="/library/editor/FCKeditor/fckeditor.js"> // empty block </script>
>>>>>
>>>>>
>>>>>
>>>>> If you use either customized render or the default render formCreate.xslt,
>>>>> you need to make sure it calls the fckeditor.js under the
>>>>>
>>>>>
>>>>>
>>>>> /library/editor/FCKeditor/fckeditor.js
>>>>>
>>>>>
>>>>>
>>>>> The fckeditor.js under that path should be the one for your 2.6.4.1 FCK
>>>>> editor. Any other path may not point to the Sakai instance FCK editor js.
>>>>>
>>>>>
>>>>>
>>>>> I am not exactly sure this can help. It is just I had similar
>>>>> experiences before, I found this is a small trick for me to resolve the
>>>>> problem I had.
>>>>>
>>>>>
>>>>>
>>>>> hongbo
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From:* portfolio-bounces at collab.sakaiproject.org [mailto:
>>>>> portfolio-bounces at collab.sakaiproject.org] *On Behalf Of *Brian Dashew
>>>>> *Sent:* Thursday, July 29, 2010 2:35 PM
>>>>> *To:* osp
>>>>> *Subject:* [Portfolio] Question about editor in forms for OSP
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Hello:
>>>>>
>>>>> As we were investigating a problem some users were experiencing getting
>>>>> content into a form containing an FCK Editor field, we discovered that our
>>>>> instance of OSP was for some reason using an old version of the editor
>>>>> (2.4.1, while the rest of our instance of Sakai is running 2.6.4.1). We
>>>>> aren't sure if that's an institutional oversight or an intentional feature
>>>>> of the tool. Is there a reason we would not want to include an updated
>>>>> version of the editor in our forms for OSP? And does anybody have
>>>>> documentation for how to change this old version out for the version running
>>>>> in other tools?
>>>>>
>>>>> Thank you,
>>>>> Brian
>>>>>
>>>>>  ---------------------
>>>>> Brian Dashew
>>>>> Instructional Designer, Academic Technology & eLearning
>>>>> Marist College
>>>>> Library 317
>>>>> Poughkeepsie, NY 12601
>>>>> (845) 575-3303
>>>>> Email: Brian.Dashew at marist.edu
>>>>>
>>>>> _______________________________________________
>>>>> portfolio mailing list
>>>>> portfolio at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/portfolio
>>>>>
>>>>> TO UNSUBSCRIBE: send email to
>>>>> portfolio-unsubscribe at collab.sakaiproject.org with a subject of
>>>>> "unsubscribe"
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> portfolio mailing list
>>>> portfolio at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/portfolio
>>>>
>>>> TO UNSUBSCRIBE: send email to
>>>> portfolio-unsubscribe at collab.sakaiproject.org with a subject of
>>>> "unsubscribe"
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/portfolio/attachments/20100729/4b472c79/attachment.html