Re: [xwiki-users] What would be a simple way to display a Masonry view in XWiki ?
Hi, Thanks ! Totem seems pretty intersting. Theorically "ImageOnTop" should do the job. I created a section with ImageOnTop display. In "edit elements of this section" / advanced, I added the autocompleted class reference : Myapp.Code.MyappClass. This display a dynamic list of pages. What is missing is the image "on top". I tried to add some pieces of code from reference application in "image" fied to get the first image attached but I couldn't get it working with Reference and I'm not even sure if this is supposed to work like this. What would be the right way to display an image from an object ? Regards Le dim. 10 avr. 2016 à 14:11, Vincent Massol <vinc...@massol.net> a écrit : > Hi Thibaut, > > > On 10 Apr 2016, at 10:41, Thibaut DEVERAUX <thibaut.dever...@gmail.com> > wrote: > > > > Dear, > > > > I'm looking in a way to display a Masonry style page in XWiki for blog or > > application. > > > > The masonry style (often called "grid") is something like this : > > http://mariustheme.tumblr.com/ > > Looks a bit similar to what the Totem application does: > http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication > > > // Why ? > > > > In termes of ergonomics it show it full potential when images speak > better > > than text. This is why Google images and Pinterest use it. > > > > Typical applications for XWiki could be : > > - Physicial products database : the image help finding the product quicly > > when not sure of the name. > > - Designs database : not just an image, a design goes with some > description > > and data so it is usefull to link to a page. > > - Physicial defects database : in industry, to quicly caracterise a > defect > > that appears visually on a part. > > - ... > > > > My need is for a nice looking collaborative product designs database. > > This database would be one app in a Wiki that has other uses. > > > > > > // The question : > > > > What would be a simple way to make it in XWiki with a minimum coding ? > > The way I’d approach it: > > 1) Try the totem app and see if it matches your need > 2) If not, see if would make sense to include a masonry style option in > the totem app > 3) if not, investigate using a library like http://masonry.desandro.com/. > Use a JSX to enable it for a page. That shouldn’t take longer than 1 hour > of work > 4) If you want to go further, consider creation a masonry app for XWiki > that would allow creating masonry-style pages similar to what the totem app > does. You could do this using AWM as a starter place. > > Thanks > -Vincent > > > // My current search state and ideas : > > > > I already searched the plugin database and couldn't find someting already > > build. But I could have missed something. > > > > Then, I thinked in making an app with App Within Minuts and modifing > > LiveTable. > > > > First step would be to edit the code to display only the first > attachement > > as a bigguer image. > > > > It could be a quick fix waiting for the second step, more complex, to > > display the LiveTable as a masonry view. There is already existing code > > that could be adapted. However this would be at the limit of my few > > programming skills and then taking a lot of time. > > > > Also I'm not sure if LiveTable can be modified on the context of one > > application only (not modifiing the others applications). > > - If yes, would it still be possible to use Apps Within Minutes to modify > > other parts of the app, not reversing the handmade code modifications ? > > - If not I gess this mean I need a more complex plugin to add a > "massonery > > view" option to LiveTable and another option to Apps Within Minuts to > > display it by default ? > > > > This is only a XWiki beginner ideas so maybe someone has an idea of a > > simpler way to do it ? > > > > Regards > > -- > > Thibaut DEVERAUX > > +33 (0)6 75 51 20 80 > ___ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > -- Thibaut DEVERAUX +33 (0)6 75 51 20 80 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] What would be a simple way to display a Masonry view in XWiki ?
Dear, I'm looking in a way to display a Masonry style page in XWiki for blog or application. The masonry style (often called "grid") is something like this : http://mariustheme.tumblr.com/ // Why ? In termes of ergonomics it show it full potential when images speak better than text. This is why Google images and Pinterest use it. Typical applications for XWiki could be : - Physicial products database : the image help finding the product quicly when not sure of the name. - Designs database : not just an image, a design goes with some description and data so it is usefull to link to a page. - Physicial defects database : in industry, to quicly caracterise a defect that appears visually on a part. - ... My need is for a nice looking collaborative product designs database. This database would be one app in a Wiki that has other uses. // The question : What would be a simple way to make it in XWiki with a minimum coding ? // My current search state and ideas : I already searched the plugin database and couldn't find someting already build. But I could have missed something. Then, I thinked in making an app with App Within Minuts and modifing LiveTable. First step would be to edit the code to display only the first attachement as a bigguer image. It could be a quick fix waiting for the second step, more complex, to display the LiveTable as a masonry view. There is already existing code that could be adapted. However this would be at the limit of my few programming skills and then taking a lot of time. Also I'm not sure if LiveTable can be modified on the context of one application only (not modifiing the others applications). - If yes, would it still be possible to use Apps Within Minutes to modify other parts of the app, not reversing the handmade code modifications ? - If not I gess this mean I need a more complex plugin to add a "massonery view" option to LiveTable and another option to Apps Within Minuts to display it by default ? This is only a XWiki beginner ideas so maybe someone has an idea of a simpler way to do it ? Regards -- Thibaut DEVERAUX +33 (0)6 75 51 20 80 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [UX] Edit Buttons Order
I'm a little bit worried about the continue.
Continuing can also be to next event in a basic process of editing.
I.e. : see finalized page.
User may think :
Continue where? To what I'm doing? To what I would do after saving ?
To what I would do after editing?
Ho ok, view maybe to view the page finalized so I guess I continue editing
Make the user thinking stop the fluent navigation. An egonome even
named a book don't make me think.
The argument about cancel seems good to me.
Proposals :
[Preview] [Save go to page] [Save] [Cancel] -- (+1)
[Preview] [Save close editor] [Save] [Cancel]
However there is a lot of +1 about see/continue so if people did not
have to think it the first time they came to page it means it's ok.
;-)
2009/9/4 Oana Tabaranu oana.tabar...@xwiki.com:
Ecaterina Valica wrote:
Hi,
Because we want to make a standard from vertical-aligned form, this means
the buttons should be left-ordered with the most important action first.
This should be changed also in Toucan and Albatross skin, not only just in
Colibri.
Right now the Edit Actions are Cancel, Preview, SaveContinue,
SaveView.
What do you think is the right order for them when they are left-aligned?
(A) SaveView, SaveContinue, Preview, Cancel (as it is - just in reverse)
(B) SaveView, Preview, SaveContinue, Cancel
(C) Preview, SaveContinue, SaveView, Cancel
(D) other variation
Remarks:
- Cancel should be *last* because it's a terminal (takes you out of the
editor), no-saving action. This is the least important.
- Save View is also a terminal action (takes you out of the editor) -
having it* first* you have the 2 terminal actions at extremities.
- Preview is the least damaging action in case of accidental submit
(Silvia + Marta) - should be *first*?
- Some people use (Preview + SaveContinue) {many times} + SaveView
{final}
- Other people just use SaveContinue + Save View {final}, never
Preview, etc
I am one of those people, but Preview is useful also when you are a
beginner.
- What is the necessity for the Preview button in a WYSIYWG editor? On the
other hand Preview is very important if you edit in Wiki mode.
- Should Preview separate the two other SAVING actions? (Marta)
- Should SaveContinue separate the two other VIEW actions?
Thanks,
Caty
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
+1 for (C).
Thx,
Oana
___
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] [Proposal] XWiki 2.0 Skin Name
Colibri+1 too. :) 2009/8/19 Vincent Gerris v.j.ger...@hhs.nl: Heron is half of the name of an Ubuntu distro and i like colibri better. So Colibri+1 then. On Wed, 2009-08-19 at 12:27 +0200, Ecaterina Valica wrote: Hi, The two leading names are* colibri* and *heron*. Please cast your final vote. Thanks, Caty Vote: *colibri* +1 Caty, *heron* ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Met vriendelijke groet, Vincent Gerris (SL 2.34) De Haagse Hogeschool Dienst ICT v.j.ger...@hhs.nl Tel: 070 445 7468 ___ 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
