Loading Profile...
Recent activity
Subscribe to this feed
ms0815 replied on May 16, 2008 19:55 to the question "script support in 2.0 and upgrade mandatory?" in PBwiki:
I know the trick with the plugin, but if javascript is considered as a security risk, then it's also a security risk in a gadget, so it's only a matter of time, until it will get forbidden there also.
@Casey Greene: is that an official statement that javascript will never be available in a free 2.0?
When the security issues are fixed, what's the reason to not enable the feature for all wikis, since it is available in all free 1.0 wikis since quite some time.
Don't take me wrong, I know that your company needs some mony for providing this systems.
And I would instantly pay 10$ (I'm european, so it's cheap at the monent anyway ^^) for enabling javascript on my prvate wiki onetime.
But 100$ per year is a lot of money for just enabling javascript, since I don't need any of the other additional features.
PS: Whats with the other questions, upgrade to 2.0 mandatory at some point? When?-
ms0815 replied on May 16, 2008 19:39 to the question "Is the Classic Editor supported in PBwiki 2.0?" in PBwiki:
I'm also loving the classic editor, especially creating links is extremely fast.
I use a private wiki with over 100 pages and over 1000 links, links are the core of my wiki and beeing forced to use the new editor would be really a problem.
It's not only the time you need more when using the mouse for links (even shortcuts are much slower and more intricate than classic editor) - the problem is the bad feeling everytime you make a link that it was much easier in the past and that is now called "improvement".
I know there is a problem that the classic formatting gets "destroyed" when someone uses the new editor once - so you can't relly switch back anymore then.
But why don't you make the new editor default and an option in the wiki settings to enable also classic editor which the wikiadmin can turn on and set write permissions to pages so that someones "classic" pages don't get broken.
At least on a private wiki classic editor should be available ! -
ms0815 asked a question in PBwiki on May 16, 2008 18:58:
script support in 2.0 and upgrade mandatory?I have a private 1.0 PBwiki (with over 150 pages) where I use some javascript and a test with
https://forumdemo.pbwiki.com/FrontPage
tells me that non of my code works in 2.0 anymore.
That's a big problem, the html and javascript support was the main reason I've chosen PBwiki!
I copied the core of my Sidebar code here, that you can see what I'm talking about:
http://testwk.pbwiki.com/FrontPage
So the Question is how I get something like that to work in 2.0?
I know there are Browsers which have such quick search features, but I have many different computers at home and work, with different browsers and don't want to configure them all when something changes.
I know the thread: http://getsatisfaction.com/pbwiki/top... but from the answers there I don't have much hope to see javascript in 2.0 soon.
My suggestions / questions to PBwiki:
1. Make a HUGE warning for everybody who even thinks about upgrading to 2.0 that during the "upgrade" all javascript is deleted and cannot be added back. Especially since you can't go back to 1.0 once you've upgraded.
2. Allow javascript in private wikis.
3. Allow javascript in Sidebar and make it editable admin only. or something similar.
4. How do I make sure that my 1.0 wiki does NOT get "upgrade" to 2.0?
5. Will javascript in 2.0 be available before we are forced to upgrade to 2.0, will there be an option to _never_ upgrade to 2.0 if you don't allow javascript for it? -
ms0815 started following the question "Is Javascript supported in PBwiki 2.0?" in PBwiki.
-
ms0815 started following the idea "Moving the sidebar above the "In Folder" block" in PBwiki.
