Re: [xwiki-users] Resize images and keep aspect ratio
On 06/22/2010 07:19 AM, Caleb James DeLisle wrote: If think if you specify the image width and not the height, it will scale maintaining ratio. It is scaling in the browser not on the server. [[image:myImg.png||width=800px]] You can also use the 'class' or 'style' attributes to apply CSS properties like max-height or max-width: [[image:myImg.png||class=limitedWidth]] [[image:myImg.png||style=max-width:500px]] Marius Caleb Abel Solórzano Astorga wrote: Hi, I am currently working with big images on my xwiki site. Is there a way to make the images auto-scale to the width of the xWiki page content if the image is too big? In order to avoid the horizontal scroll bar that appears on the page and adjust the images to the width of the xWiki page content. I am using the colibri skin. To make my question more general, What is the best way to dynamically resize images on xwiki? or set a max size for the images maintaining the aspect ratio. Thanks, Abel ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] [Idea] Modern skin for modern browsers
Hi, When the CSS3 fever began, Raluca Stavro came to me and asked me what I think about making a HTML5+CSS3 skin. My first answer was that is not gonna happen. We invest very much in making our skins have cross-browser support (especially old versions of IE). This is one of our strengths, but also the reason we limit ourselves from innovation. When I'm talking about a modern skin I'm not only referring about HTML, JS, CSS (having transparency, corners, multiple backgrounds, shadows without having to triple the code and the number of hacks), but it's about all cool/experimentation features, that boosts productivity, minimize code lines, etc. but lack all/old browser support (SVG, location awareness, CSS3 calc etc). So, in my opinion this would be an experimentation/shiny skin that by comparison would make old browsers supporters and lovers to quit their old behaviors and embrace the future :) :p So, the questions I have are: 1) would this be possible? would anyone want to do this sort of thing? I know the biggest problem is gonna be the maintenance, but could bring lots of innovation and productivity. 2) what feature/improvement/thing do you think it would be the most needed for a new modern skin (the topic somehow go beyond the skin boundaries)? Thanks, Caty ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Templates Provider
On 06/21/2010 10:44 PM, Adriana Escamilla wrote: Also, I have a little problem with the Import of Documents in OpenOfficeServer, I tried to set up a OOffice in a Linux Server, but i cant to make it a service D=!!! I was looking for a tip of How to make OpenOffice a Service in Linux and what i found doesnt work =(. My server details are: - SO: OpenSuse 10, Server - XWiki: Enterprise 2.3 - OpenOffice: 3.2 http://www.artofsolving.com/node/10 Basically, you need to executed this line: soffice -headless -accept=socket,host=127.0.0.1,port=8100;urp; -nofirststartwizard Starting things automatically at boot requires that you write an init script, which depends on the operating system. For OpenSuse, I think you can look in /etc/init.d/ for an example. http://en.opensuse.org/Packaging/SUSE_Package_Conventions/Init_Scripts provides more documentation. -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] [Idea] Modern skin for modern browsers
- Ecaterina Valica vali...@gmail.com wrote: Hi, When the CSS3 fever began, Raluca Stavro came to me and asked me what I think about making a HTML5+CSS3 skin. My first answer was that is not gonna happen. We invest very much in making our skins have cross-browser support (especially old versions of IE). This is one of our strengths, but also the reason we limit ourselves from innovation. When I'm talking about a modern skin I'm not only referring about HTML, JS, CSS (having transparency, corners, multiple backgrounds, shadows without having to triple the code and the number of hacks), but it's about all cool/experimentation features, that boosts productivity, minimize code lines, etc. but lack all/old browser support (SVG, location awareness, CSS3 calc etc). So, in my opinion this would be an experimentation/shiny skin that by comparison would make old browsers supporters and lovers to quit their old behaviors and embrace the future :) :p So, the questions I have are: 1) would this be possible? would anyone want to do this sort of thing? I know the biggest problem is gonna be the maintenance, but could bring lots of innovation and productivity. For lot of cases (that is at least everything that includes JS, and maybe more) we should be able to add such new features on top of the existing UI, i.e. without the need to create a dedicated skin. Take for example attachment Drag Drop in the attachment footer tab. We just detect the feature and offer it if supported (do nothing if not). 2) what feature/improvement/thing do you think it would be the most needed for a new modern skin (the topic somehow go beyond the skin boundaries)? Right now I think of - attachments DD - upload with progress bar - growl-like client notifications (w/ WebSocket) - local drafts (with localStorage) - a profile picture sizing/cropping tool using canvas - ... I'm sure a lot more :) Jerome. Thanks, Caty ___ devs mailing list d...@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [Idea] Modern skin for modern browsers
On 06/22/2010 10:19 AM, Ecaterina Valica wrote: Hi, When the CSS3 fever began, Raluca Stavro came to me and asked me what I think about making a HTML5+CSS3 skin. My first answer was that is not gonna happen. We invest very much in making our skins have cross-browser support (especially old versions of IE). This is one of our strengths, but also the reason we limit ourselves from innovation. When I'm talking about a modern skin I'm not only referring about HTML, JS, CSS (having transparency, corners, multiple backgrounds, shadows without having to triple the code and the number of hacks), but it's about all cool/experimentation features, that boosts productivity, minimize code lines, etc. but lack all/old browser support (SVG, location awareness, CSS3 calc etc). Very nice, I was thinking the same a while back. So, in my opinion this would be an experimentation/shiny skin that by comparison would make old browsers supporters and lovers to quit their old behaviors and embrace the future :) :p We need to seriously define our commitment to such a skin, if we decide to do it. A nice but not important skin will quickly get out of sync with the main skin, and start lacking features. So, the questions I have are: 1) would this be possible? would anyone want to do this sort of thing? I know the biggest problem is gonna be the maintenance, but could bring lots of innovation and productivity. Possible. Me. Good code works well across skins without any maintenance needed. 2) what feature/improvement/thing do you think it would be the most needed for a new modern skin (the topic somehow go beyond the skin boundaries)? One cool but big feature would be offline access. Another would be SVG images/backgrounds, which can be styled with velocity (think color-themed gradients and special effects on buttons). A nicer font(s) to be used as default. DragDrop attachment upload. Most of these would fit well in the existing skins as well, as progressive enhancements. -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] [Proposal] Selective Export UI
Hi Caty, I really apologize in advance for looking at this so late and also for my upcoming comments do not feel hurt please, but I do not feel that this interface will provide the nice export functionality we expect. First, here is a resume of my main remarks: - You need a big, large screen to see it properly, and at the same time, everything is small and concentrate. - There are too many choices at the same time, and this cause a real excess of complexity - Navigation in the list of document, and filtering, are absolutely different to what the user is accustomed to with LiveTable - Scalability issue increase the complexity in the document list, and choice of export format will not scale easily - Some export options (in the format box) change the list of document that will be exported after your initial choice Let me now review this in more details. 1) Screen size and complexity Putting together the 3 parts of this interface (full list, selected list and export options) make it complex and cluttered. IMO, there isn't several way to solve this. Each part should be in a separate screen. This will both decrease complexity, and allow more flexibility for composing each screen. These screens could than be linked together in a wizard like interface (Back/Next), and a direct access could also be provided using tabs or similar control. These tabs should also show the normal path of actions. 2) List of documents and scalability IMO, we should inspire the list of document from the livetable (not the tree) actually in AllDocs. We need to have it improved (also in AllDocs), but keeping the same look and feel between both of them will obviously helps both users and developers. The livetable in AllDocs already solve the scalability problem nicely, and users will be accustomed to it. What should be improved (in both place) ? - Allow filters on document contents or using the tagcloud. This will provide a mix with the search feature and the tag feature, but in a filter way (without sorting by relevance) - Allow customizing columns, since we might want to choose document based on creation date, modification date, authors, creators, presence of attachements, ... and not all of them could be proposed at once - Allow displaying hidden documents - Allow small popup document preview ? What should be added for export ? - A display of the selection status, probably near the name, on the left. - To allow user to select whole Space, why not list them in there own row, next to the documents, and provide a type filter to list only spaces, document or both. For spaces, the selection box could be three states, showing partially selected space. - Add/remove all displayed item, add/remove the whole filtered list, should be proposed for easy large selection/deselection. An undo option could be nice to have. 3) List of selected documents / Spaces To stay simple, this list should be very similar to the previous one (and influenced by the column customarily displayed in the previous step by the user). This is in fact a filtered view on the selection status. I would not mix it with the previous one, to provide a clear step by step way and a slightly different interface : - The selection status should be replace by a removal button. - Some external button should allow: - Add Children which will add one level of children of all selected page to the list - Add All Children which will add all children of selected page recursively to the list - Add Linked Pages which will add pages linked from currently selected page to the list - Add All Linked Page which will add pages linked from currently selected page recursively to the list - Undo last addition using one of the previous buttons which will return the list to its previous state - Save current selection which will allow saving the current selection for later use/reuse If the export contains unselected children pages, or unselected linked pages. It may be useful to warn the user of that situation on this screen. 4) Export options This last screen should allow the selection of the export format from a free list. After a deep refactoring, we should be able to easily implement new export format (using components) and this list of format should be dynamic. Obviously, the format options will be displayed depending of the chosen format (including custom interface by custom formats). But, these options should not change the list of exported pages in any way, this is confusing. 5) What about the hierarchical views IMO, we should stay away from them as much as we can since trees of large sets have a serious scalability issue (I means for the user, not only the computer). I have already provide some hints on how to provide children and link inclusion, but may be we can go one step further with reasonable complexity. For each rows of both table describe above, we may have several expanding box (a small lightbox), that shows: - the list of direct children of
Re: [xwiki-users] HTML Export - how to apply skin ?
The diff is available under http://www.computer42.org/~dirk/tmp/skin.diff.txt http://www.computer42.org/%7Edirk/tmp/skin.diff.txt Am 20.06.2010 00:08, schrieb Sergiu Dumitriu: On 06/19/2010 10:44 PM, H.-Dirk Schmitt wrote: Hi Vincent, it works in one space, but in the other it is broken. I attached a diff of the both exports skins directories. Most attachments are not allowed on the list, better put the code on pastebin or another text sharing tool. Any hint? Best regards, H.-Dirk Schmitt Am 11.05.2010 21:59, schrieb Vincent Massol: Hi, On May 11, 2010, at 9:26 PM, H.-Dirk Schmitt wrote: Hi! I have exported a whole space to html and found it great. If I deploy this export I can provide it at static content via plain http without authentication and for editing the links shows to the live xwiki instance. Really nice! But I have one problem - the skin from the live version isn't applied to the html-export. How can I add the skin to the exported static content ? The skin is supposed to be exported. If you're using the Colibri skin we used to have a bug where the colibri skin wasn't exported. It was fixed in XE 2.2M2 and 2.1.2, see http://jira.xwiki.org/jira/browse/XWIKI-4615 What version of XE are you running? Thanks -Vincent -- * H.-Dirk Schmitt http://www.computer42.org * Dipl. Math. eMail:/dirk.schm...@computer42.org/ mobile:/+49 177 616 8564/ phone: /+49 2642 99 41 10/ fax: /+49 2642 99 41 15/ Kripper Str. 35, D-53489 Sinzig ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] HTML Export - how to apply skin ?
On 06/22/2010 10:26 PM, H.-Dirk Schmitt wrote: The diff is available under http://www.computer42.org/~dirk/tmp/skin.diff.txt http://www.computer42.org/%7Edirk/tmp/skin.diff.txt Looks like only the colors are different, as if those two spaces were using two different color themes. Am 20.06.2010 00:08, schrieb Sergiu Dumitriu: On 06/19/2010 10:44 PM, H.-Dirk Schmitt wrote: Hi Vincent, it works in one space, but in the other it is broken. What do you mean by broken? From your diff looks like the broken export uses just different colors. Are those two spaces you have exported using the same skin / color theme? Hope this helps, Marius I attached a diff of the both exports skins directories. Most attachments are not allowed on the list, better put the code on pastebin or another text sharing tool. Any hint? Best regards, H.-Dirk Schmitt Am 11.05.2010 21:59, schrieb Vincent Massol: Hi, On May 11, 2010, at 9:26 PM, H.-Dirk Schmitt wrote: Hi! I have exported a whole space to html and found it great. If I deploy this export I can provide it at static content via plain http without authentication and for editing the links shows to the live xwiki instance. Really nice! But I have one problem - the skin from the live version isn't applied to the html-export. How can I add the skin to the exported static content ? The skin is supposed to be exported. If you're using the Colibri skin we used to have a bug where the colibri skin wasn't exported. It was fixed in XE 2.2M2 and 2.1.2, see http://jira.xwiki.org/jira/browse/XWIKI-4615 What version of XE are you running? Thanks -Vincent ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Lucene Search engine failure
Hi Friends, In my fresh installed Xwiki (ver. 2.3.28602), I've configured the Lucene search plugin accordingly to the described in http://code.xwiki.org/xwiki/bin/view/Plugins/LucenePlugin But when I try to search any keyword, it returns only the following result: Failed to execute macro: HTML And no information appears on the log. How can I fix this? Regards, Ramon Gomes Brandão ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Resize images and keep aspect ratio
Thanks for the help. I just did it and it mantains aspect ratio. On Tue, Jun 22, 2010 at 12:38 AM, Marius Dumitru Florea mariusdumitru.flo...@xwiki.com wrote: On 06/22/2010 07:19 AM, Caleb James DeLisle wrote: If think if you specify the image width and not the height, it will scale maintaining ratio. It is scaling in the browser not on the server. [[image:myImg.png||width=800px]] You can also use the 'class' or 'style' attributes to apply CSS properties like max-height or max-width: [[image:myImg.png||class=limitedWidth]] [[image:myImg.png||style=max-width:500px]] Marius Caleb Abel Solórzano Astorga wrote: Hi, I am currently working with big images on my xwiki site. Is there a way to make the images auto-scale to the width of the xWiki page content if the image is too big? In order to avoid the horizontal scroll bar that appears on the page and adjust the images to the width of the xWiki page content. I am using the colibri skin. To make my question more general, What is the best way to dynamically resize images on xwiki? or set a max size for the images maintaining the aspect ratio. Thanks, Abel ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Lucene Search engine failure
On 06/23/2010 12:11 AM, Ramon Gomes Brandão - SERINT wrote:
Hi Friends,
In my fresh installed Xwiki (ver. 2.3.28602), I've configured the Lucene
search plugin accordingly to the described in
http://code.xwiki.org/xwiki/bin/view/Plugins/LucenePlugin
But when I try to search any keyword, it returns only the following result:
Failed to execute macro: HTML
And no information appears on the log. How can I fix this?
http://jira.xwiki.org/jira/browse/XE-636 seems to be fixed in 2.3. Can
you check the source code of the Main.LuceneSearch page to see if there
are empty lines before {{html}} and {{include}} macros?
Hope this helps,
Marius
Regards,
Ramon Gomes Brandão
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Altering Access Rights from REST Api
Hi Manish, On 06/23/2010 12:13 AM, xManish wrote: Hello, I was able to create a wiki page through API. Now I wanted to restrict some of the access rights for certain users to that particular wikipage through REST Api. For example, How can we restrict a certain user from viewing a particular wiki page through REST Api? In XWiki, this could be achieved by logging in as an administrator - Click on a wiki Page - Click on the 'Access Rights' from 'Edit' dropdown menu - and then checkmarking the rights to specific user or group. How can we achieve this from REST Api? I don't know much about the REST API, but if you edit with the object editor the page you just set access rights on you'll see that it has an object of class XWiki.XWikiRights attached. In other words, access rights are controlled with XWiki objects. So you just have to add/update/remove objects of class XWiki.XWikiRights to your page with the REST API. Hope this helps, Marius Any help would be really appreciated. Thanks, Manish ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Lucene Search engine failure
2010/6/22 Ramon Gomes Brandão - SERINT ramon.bran...@tjdft.jus.br: Hi Friends, In my fresh installed Xwiki (ver. 2.3.28602), I've configured the Lucene search plugin accordingly to the described in http://code.xwiki.org/xwiki/bin/view/Plugins/LucenePlugin But when I try to search any keyword, it returns only the following result: Failed to execute macro: HTML And no information appears on the log. How can I fix this? That should be fixed in 2.3.1. See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise231#HMigrationNotes Regards, Ramon Gomes Brandão ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Thomas Mortagne ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] How to add a page with contents in xwiki through Rest api???
I think I will have to apologize the original creator of this thread for using it to discuss my issue. Jerome, could you please join me in the another thread that I've created for this issue. Its 'Create User in XWiki from REST Api' under XWiki-Dev. THankyou, manish -- View this message in context: http://xwiki.475771.n2.nabble.com/How-to-add-a-page-with-contents-in-xwiki-through-Rest-api-tp4520594p5211253.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
