Hi
In case nobody ran into this so far I just wanted to make sure everybody knows that 3827:
http://jira.xwiki.org/jira/browse/XWIKI-3827
is still or again broken in 1.9.2. The fix from David mentioned at the end of the comments did do the trick for me:
wiki/resources/js/xwiki/wysiwyg/xwe/stylesheets/RichTextArea.css:
change: background-image: none;
to: background-image: none !important;
I cannot change the status of this JIRA report to reopen it so please could someone do it or just apply the fix.
Thanks
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Here I go. My own public blog is now upgraded to 2.0 Syntax using the attached XAR file. The entry discusses the other changes that needed to be done in order to make it work well:
http://madplanet.com/xwiki/bin/view/Blog/
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
On Monday, July 27, 2009, at 05:13PM, "Andreas Schaefer" <schaefera(a)me.com> wrote:
>Sorry but I forgot to mention the JIRA report I attached the draft to:
>
>http://jira.xwiki.org/jira/browse/XABLOG-50
>
>Cheers - Andy
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
>
>
Hi
Currently our company is using Magnolia (magnolia.info) as the CMS for our website. Because our website is not very dynamic, big or complex using Magnolia is often a little bit of an overkill and keeping it up to date is not easy. So I was wondering if I could use XWiki to create a simple application that would enable the creation and maintenance of a website.
Today the Blog is a list of Blog Document building up the blog page. Breaking up the page into a header, left and right side bar (or using the panels) and columns for the content it should be possible to define a web page. The parts of a page a defined by classes and the content is provided by objects. The application just provides the code that displays the web site and additional elements to create, edit and remove parts of the document (paragraphs) when the user is in edit mode.
The application would provide a simple web site but also the framework to create a custom web site by extending the application.
What do you think?
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Hi fellow XWikiers,
While celebrating XWiki's 5th birthday last week, we spent a couple days
brainstorming with the full team about where XWiki stands today and what its
future holds. We came up with a long list of features and ideas and we'd
love to get community feedback before deciding in which direction we're
going to move forward once our 2.0 release is out.
To this aim, we've built a survey that we'd like our users and developers to
take. It's a bit long though definitely worth the pain. We're eagerly
waiting for your feedback to start working on new and existing features.
You can access and fill the survey at the following address:
http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures
Thanks a lot for your time,
Guillaume on behalf of the XWiki Team
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
XWiki had always had some nice feedback about its interface. But things are
not that honey pink, we have many inconsistencies in our user interface,
some of them caused by the fact that we're developing in an open source
environment.
Our goal is to improve the user experience of XWiki and we'd like you to get
involved. We need to improve the usability of the XWiki platform and we
would be very happy if the community got involved in helping us making this
happen.
All the decisions we make directly imply and affect our community which is
why we're eager to get your feedback before we start working further on
these topics.
- We would like to know what are your main usability problems when using
XWiki - we badly want to fix them ;-)
- We would be super-happy to receive bold and creative ideas that we
might be able to incorporate into XWiki's look and feel.
Want to get involved? Yay! We’d love to have you aboard! It doesn't matter
whether you're a developer who’s interested in participating, an UX person
or someone with an eye for design as long as you come up with great ideas.
You can add your mockups and videos to our Flickr group
http://www.flickr.com/groups/xwikiux/ or to our Vimeo group
http://www.vimeo.com/groups/xwikiux . These groups can be used to show off
your ideas or just to point the problems you had using XWiki.
Let’s make XWiki amazing !!
On Tue, Jul 28, 2009 at 13:09, Thomas Mortagne<thomas.mortagne(a)xwiki.com> wrote:
> Hi,
>
> Use <scope>test</scope> for test dependencies instead of <scope>provided</scope>
>
--
Thomas Mortagne
Hi,
I am currently using XWiki for the website of an hotel which is essentially
practical for its i18n management (the website is available in English,
French, Japanse and Italian). I easily managed to upgrade the PhotoAlbum
application in order to be i18n (titles are i18n keys and body use $msg.get
calls). I really need to have a similar functionnality on the Blog
application. I was wondering how complicated this task is... I tought I
could copy every document in the Blog space to a fresh new I18nBlog which I
could modify. What do you think about it ?
Concerning the way I plan to eventually internationalized the Blog
application is to link each BlogPost to a page that could be translated,
through a dedicated class member. I also noticed that the BlogParameters and
BlogCode should be my first look for adapting the application. Please tell
me if I'm right.
At last, I was wondering about the availability of macros for managing
translations when I plan to adapt the sheet. What also about the edition of
a specific document in the sheet of another one, is it possible ?
Thanks for your help.
--
Hoani CROSS
Globotraders Tahiti Founder [http://globotraders-tahiti.com]
http://code.google.com/appengine/docs/whatisgoogleappengine.html
Java is supported via Java 6 JVM and standard libs:
http://code.google.com/appengine/docs/java/gettingstarted/
My biggest question w/r/t Xwiki is AppEngine's database support:
> The Datastore
>
> App Engine provides a powerful distributed data storage service that
> features a query engine and transactions. Just as the distributed web server
> grows with your traffic, the distributed datastore grows with your data.
>
> The App Engine datastore is not like a traditional relational database.
> Data objects, or "entities," have a kind and a set of properties. Queries
> can retrieve entities of a given kind filtered and sorted by the values of
> the properties. Property values can be of any of the supported property
> value types<http://code.google.com/appengine/docs/python/datastore/typesandpropertyclas…>
> .
>
> Datastore entities are "schemaless." The structure of data entities is
> provided by and enforced by your application code. The Java JDO/JPA
> interfaces and the Python datastore interface include features for applying
> and enforcing structure within your app. Your app can also access the
> datastore directly to apply as much or as little structure as it needs.
>
> The datastore is strongly consistent<http://en.wikipedia.org/wiki/Consistency_model>and uses optimistic
> concurrency control<http://en.wikipedia.org/wiki/Optimistic_concurrency_control>.
> An update of a entity occurs in a transaction that is retried a fixed number
> of times if other processes are trying to update the same entity
> simultaneously. Your application can execute multiple datastore operations
> in a single transaction which either all succeed or all fail, ensuring the
> integrity of your data.
>
> The datastore implements transactions across its distributed network using
> "entity groups." A transaction manipulates entities within a single group.
> Entities of the same group are stored together for efficient execution of
> transactions. Your application can assign entities to groups when the
> entities are created.
>
http://code.google.com/appengine/docs/java/gettingstarted/usingdatastore.ht…
> App Engine includes support for two different API standards for the
> datastore: Java Data Objects <http://java.sun.com/jdo/index.jsp> (JDO) and
> Java Persistence API<http://java.sun.com/developer/technicalArticles/J2EE/jpa/>(JPA). These interfaces are provided by DataNucleus
> Access Platform <http://www.datanucleus.org/>, an open source
> implementation of several Java persistence standards, with an adapter for
> the App Engine datastore.
>
..............
Question:
What would it take to make Xwiki work on Google App-engine? Is the
"datastore" google provides compatible with xwiki's database needs?
What other Java-hosting services "out there" support Xwiki? Database and
java "hosting" issues for Xwiki can be problematic, even though it makes
more sense, to public-host using a language like Java.
I think for my own situation, I would end up "hosting" Xwiki myself, as a
$500.00 box can run a few Xwiki-based sites just fine. However, for
people/customers wanting an Xwiki-based site that don't know about system
administration, JVM's, apache, etc, it would be nice if there was an easier
path to managed hosting in an "open market." This needn't limit xwiki.com's
hosting market, as much as it would open-up xwiki for wider deployment and
use, and make it competitive in situations where Php or RoR might have
easier buy-in, such as in the USA....
Imagine if in the future, one of the installers Xwiki.org offered worked
directly with http://appengine.google.com/ so that people would
actually have their own live, public xwiki sites hosted for them. There's
plenty of sites that would be happy with this level of free
service ( http://code.google.com/appengine/docs/quotas.html ):
Resource Free Default Quota Billing Enabled Quota Daily Limit Maximum
Rate Daily
Limit Maximum Rate Requests 1,300,000 requests 7,400 requests/minute
43,000,000
requests 30,000 requests/minute Outgoing Bandwidth
(billable<http://code.google.com/appengine/docs/quotas.html#Billable_Quotas_and_Fixed…>,
includes HTTPS) 1 gigabyte 56 megabytes/minute 1 gigabyte free; 1,046
gigabytes maximum 740 megabytes/minute Incoming Bandwidth
(billable<http://code.google.com/appengine/docs/quotas.html#Billable_Quotas_and_Fixed…>,
includes HTTPS) 1 gigabyte 56 megabytes/minute 1 gigabyte free; 1,046
gigabytes maximum 740 megabytes/minute CPU Time
(billable<http://code.google.com/appengine/docs/quotas.html#Billable_Quotas_and_Fixed…>
) 6.5 CPU-hours 15 CPU-minutes/minute 6.5 CPU-hours free; 1,729 CPU-hours
maximum 72 CPU-minutes/minuteNiels
http://nielsmayer.com
PS: although at 1 gigabyte outgoing bandwidth, and some of the sizable
javascript libraries these days... you probably want to use
http://webmuch.com/how-why-you-should-use-google-cdn/ alongside :-)
Hi
I just recently started to use the Import / Export Application and run in some unexpected problems. The most severe is the one that I cannot export HIDDEN documents because the searchDocuments() method it is using does not return any hidden documents. That makes the tool less useful and it is a pitfall for inexperienced users.
So I would suggest to use a checkbox to determine if hidden documents should be listed or not. Any idea BTW how hidden documents can be found in XWiki.
After checking out JIRA: http://jira.xwiki.org/jira/browse/XWIKI-3660 I see there is a need to improve the import / export application. I will have a look into how to improve it.
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com