Re: [libreoffice-website] LibreOffice Extensions-Site: Renovation
Hi Andreas, Andreas Mantke wrote (14-02-14 21:17) > I worked on new content types in the meantime and created a first view > for the release content type. I added six fields for file uploads. I > think that would be enough. Thanks, but I'm afraid I have difficulty to get the link with all details that we wrote about before in this thread. So if you can try to explain that (with possibly a next update) : would be appreciated by me :) Regards, Cor -- Cor Nouws GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6 - vrijwilliger http://nl.libreoffice.org - volunteer http://www.libreoffice.org - The Document Foundation Membership Committee Member -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-website] LibreOffice Extensions-Site: Renovation
Hi Cor, all, Am 14.02.2014 19:57, schrieb Cor Nouws: > Andreas Mantke wrote (10-02-14 22:38) >> Hi Cor, >> >> Am 10.02.2014 22:06, schrieb Cor Nouws: (...) How many different extension files are posible for a release? If there is some compiled stuff inside an extension it could run e.g. only on Linux-i586 or -x64. >>> Ah, interesting. Yes of course it's very good to take that onto >>> consideration. Would it be needed to add a limit? >>> Can't it be simple >>> [ upload path ][ for version |V] (list) [ for OS |V] (list)+ >>> >>> where version and OS have 'all' too and that clicking + adds a new line >>> and that at the end the author clicks [Add] or [Submit] ? >> If the site uses an own content type for the file upload you could ad as >> many files as you like. But if the contributor choose the files on the >> release page itself there had to be a field for each file. Otherwise the >> former file would be dropped once the contributor choose a new one. > In my previous message I wrote a IMO simpeler solution. > I worked on new content types in the meantime and created a first view for the release content type. I added six fields for file uploads. I think that would be enough. I worked on a view for that content type. The layout is really bad but a shiny layout was not my goal yet. I've published screenshots from a release with six files and from one without any file on my blog yet: http://amantke.de/blog/2014/02/libreoffice-extensions-repository-draft-of-new-views-part-2/ I try to find some time to work on the view for the project content type next. Regards, Andreas -- ## Developer LibreOffice ## Freie Office-Suite für Linux, Mac, Windows ## http://LibreOffice.org ## Support the Document Foundation (http://documentfoundation.org) ## Meine Seite: http://www.amantke.de -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-website] LibreOffice Extensions-Site: Renovation
Hi Andreas, all, Andreas Mantke wrote (11-02-14 22:18) > after the feedback from Cor I thought of an alternative structure > (hierarchy) of the content types. It would be more flat. > [...] > -- ExtensionsCenter (EC) > -- ExtensionsProject (EP) > -- ExtensionsRelease (ER) > > The EC will contain in the edit view form fields to customize the total > center, e.g. to add LibreOffice versions, categories, licenses. The view > will show a search form with result area, short search links etc. Some late thoughts - not included in my sketch: (.. now that we are looking at the design ;) ) - search in titles of the extensions or in descriptions or in both - (maybe votes ..) - when it comes to different versions for different OS-es, I would say make a different Extension (thus name) for that (since that must be rare occasions and it saves some work on the design and buidling) > The contributor will have to create (or get) an account and start with a > project for each extension. As long as that action is called "New extension" > OK > There will be a edit form where he will be asked for the necessary information > about the extension project. OK > The view of the project will show information about the project, e.g. > category, description and maybe a form to send messages to the project > owner. +1 for the latter idea. > There will also be links to the releases and for the download of the > files (for each public release). Links to the releases and link to download the latest, I guess ? > The release content type will contain the information about the release > and all extensions files of that release with the information about > license and appropriate platform. I had to add about 5 or 6 file fields > to the release content type. I guess the user (the one who downloads) will see the 'content type' ? > It would be possible to add some more information to each content type, > e.g. install instructions, legal information for users, images > (screenshots, logos). I think some of those will be the same for all versions of the extension. So omitting to fill in by the author (and easy link or such) would be helpful. > Does this structure sound more user friendly? Feedback? Additions? For what I realise now (trying to visualise your technical terms) I think it's good. Wonder if others with experience/knowledge of other extensions-sites see some omissions / ideas .. Cheers, Cor -- Cor Nouws GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6 - vrijwilliger http://nl.libreoffice.org - volunteer http://www.libreoffice.org - The Document Foundation Membership Committee Member -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-website] LibreOffice Extensions-Site: Renovation
Andreas Mantke wrote (10-02-14 22:38) > Hi Cor, > > Am 10.02.2014 22:06, schrieb Cor Nouws: >>> I try to summarize what I got from your draft: >>> >>> You want a home page (landing page) that has search box, a listing of >>> search results, the login, a link to information about installing >>> extensions, a link to a bugtracker and a link to an explanation of the >>> purpose of extensions (or a box with a teaser and a link to the long >>> explanation). >>> >>> Did I summarize that correct? >>> >> Yes, that is OK, plus that I would like to have searches for Most >> recent, Most popular, and By category. >> > Should that be search forms or a button/link that trigger a search and > give back the result in the list field on the site? I figure out the latter. Yes .. simple search box. >> And the bugtracker may also info on how/where to report bugs .. > > Hmm. A bugtracker on the site or the upcomming LibreOffice bugtracker? Or a simple form to send a mail to the author (as you suggested in the other mail - from my experience with extensions that is fine. If one wants different, he/she can add an url for feed back in the description) >>> But then I'm a bit lost. The next fields in your spreadsheet are further >>> pages? >>> Are they in a hierarchical order? >> >> OK, I clarified the sketch a bit. >> >> https://wiki.documentfoundation.org/File:ExtensionsSite_IdeasOnContent_CorNouws_20140210.ods >> >>> Do we want to create projects for the extensions? >> >> For a user that would not be interesting, I guess. Only from a technical >> POV that might matter? > > Right. But without a structure the site will be a mess soon. Yes, But I try to look from the user/authors perspective only :) >>> Should there be a release for an extension with information about the >>> LibreOffice version that it works with? >> >> Yes, see the page "New extension" though LibreOffice version is not >> mandatory IMO. > > But it would be a value for users to know which version(s) of > LibreOffice the extension is working with. Thus I prefer to make that > mandatory. This would make it possible to search for extensions that run > with a specific version of LibreOffice. On the other hand it put a > burden on the author, because he had to add new versions of LibreOffice > later. A smart solution seems to have the version "all" And if that's wrong, the author will hear complaints. ;) >>> How many different extension files are posible for a release? >>> If there is some compiled stuff inside an extension it could run e.g. >>> only on Linux-i586 or -x64. >> Ah, interesting. Yes of course it's very good to take that onto >> consideration. Would it be needed to add a limit? >> Can't it be simple >> [ upload path ][ for version |V] (list) [ for OS |V] (list)+ >> >> where version and OS have 'all' too and that clicking + adds a new line >> and that at the end the author clicks [Add] or [Submit] ? > > If the site uses an own content type for the file upload you could ad as > many files as you like. But if the contributor choose the files on the > release page itself there had to be a field for each file. Otherwise the > former file would be dropped once the contributor choose a new one. In my previous message I wrote a IMO simpeler solution. Regards, Cor -- Cor Nouws GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6 - vrijwilliger http://nl.libreoffice.org - volunteer http://www.libreoffice.org - The Document Foundation Membership Committee Member -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
